Robot Laser Final Version

[RobotEyes]

Goodmorning everyone


The Beta version of RobotLaser has finished its cycle, and will no longer be managed, nor issued license after its expiry.


Before January 20 two versions will be available:
1)   RobotLaser FREE, which is derived from the last beta version (0.6)
2)   RobotLaser Standard, currently v.1.0.0


The FREE version will continue to be available for free, but no new features will be implemented. It will remain frozen as is.
To use it you will need to make a new registration of a duration of one year (of course always free)


The standard version will be available for purchasing.
There is a trial period of 15 days (instead of 10 as the beta) after which, will need to buy it.
In case of necessity, the test may be extended for another 15 or 30 days,
Please contact RobotLaser@robot-eyes.com with the reasons for the request of the extension.
It will be possible only one extension of the test period.


The Standard license will be entitled to free download updates for all 2017.


The license, as usual, will be tied to disk on which RobotLaser is installed when requesting the activation code.
If you think you want to use RobotLaser on multiple PCs (one at a time)
we recommend you install on removable media (eg USB Key)
In this case, moving the key from one PC you can always use the same activation key that will be valid on all PCs.


If instead it is necessary to install the product on multiple PCs that operate simultaneously
an additional license (50% of the first) will be purchased.
For more than 3 licenses, contact me and we will find a solution.


Within one / two months, PRO version (with new features) and the Enterprise version will be availables.
Enterprise version enable to have RobotLaser installed and operational on all PCs of a company (max 25)


At the moment the license fee for RobotLaser Standard (with 1 year updates) is fixed at
promotional value of € 30.00
For payment please click on the "Buy Now" button on the information page ([?] Button on the main menu)
From here you will be redirected to the PayPal payment page.


For any other types of payment, please contact me.


Last Note.
Those who have made donations for the Beta version, are entitled to a discount on the the license fees.
Please contact me for instructions on how to get the discount.


Have a nice day
Carlo

[sapeur3873]

hello,

i download and try to work with your software,
it seems very not so bad.

but i try to do some grayscale picture, and the result was very not good.

i already try some different setting with no succes.

please, do you have some picture to show us about somethig that you already done in gray? (original picture and grey print)
and some setting about it???
thank you..

[RobotEyes]

Normally the grayscale provides acceptable results only after an accurate calibration.
It depends greatly on the linearity of power of the laser and the sensitivity of the etched material.
For example, if I make a 256 mm long line, and change the power of the laser of units each mm, in theory I should have a line that goes from white to black in a gradual way,
Indeed I will have a long white part (the laser did not have enough power to burn the material) followed by a short section in which the stroke darkens (the true linear part) and then a completely burned portion (the laser power was higher than necessary to achieve the "black")


To fully utilize the GrayScale need to match the white (255) to the power just lower than the needed to mark the material and the Black (0) to the power beyond which the material is burned at the maximum.
All this for a particular material, if I change it need to redo everything.
For calibration, adjustment controls of Gamma and Bright  may be used, or better the power curve in configuration.
If it is of interest to more people, I can realize (after February half) a tutorial on how to adjust the power.


For large areas dirthering  can be usd (Dirthering born to compensate for the non-linearity of the rotary press),
but on small dimensions, pitting is very apparent.

[RobotEyes]

Just for information....
The liberation code of version 1.0
will be sent only after receipt of the PayPal  notification of payment.
Thank you for understanding.
Carlo

[sapeur3873]

thank you for answer,

i try to adjust more the accuraccy of grey  scale and arrive to obtain someting not so bad.
about dithering, i think i have to adjust some speed?? which one? (mini speed and maxi speed)

thank you for answer

[skrag]

I too have been testing the Robot Eyes software.  I find it intriguing and has many good options.  I am however having an issue that I would like to solve before deciding to purchase this software.  When I use the manual mode to move the laser, the laser comes on each time.  It does not matter if the box is checked or not that indicates allowing the laser to be on when moving.  My control board is one of the Eleks Mana boards so I am not sure if that has any bearing on the issue or not. It is programmed with GRBL .9.  The laser also does not shut off when moving from place to place when doing a vector outline cut causing a burn line between each letter or object that is part of the design.  What steps can I take to get the laser to come on only when doing a cutting action per design, and not part of the move either manually or as part of a engrave routine?

[RobotEyes]

Hi.
1) are you sure you have configured the board to version 0.9 of GRBL?
    Under the CPU, there is a jumper labeled 0.9 and 0.8.

2) Verify that the laser power curve is correct:  Config -> power curves, press [Linear].

Quite all versions of GRBL 09 has a bug and turn on the laser with minimum power when moving.
Normally this will not be a problem, just a pointer,
but, if the card is set for version 0.8 (which only has ON and OFF),
even minimum power is enough to activate it at full power.


Let me know if you need to investigate more thoroughly.

[ggallant571]

I do not think that GRBL 9 has a bug that turns on the laser when moving. Which command are using? I have my own Linux based application and do not experience this effect.

[RobotEyes]

May be it is not a bug, but it is definitely a fact; noted by many people.
And it is not a RobotLaser, Windows or Linux problem.
To verify:
Open a terminal emulator (eg. Putty, Hyperterminal on Windows - Term, Tilda etc on Linux)
Connect to Eleks board, press enter (sometimes more times).
the card responds:
"Grbl J-Tech Photonics 0.9g ['$' for help]"
write commands:
M5 -> The laser is off.
G1X10Y10F1000 -> The carriage moves in 10:10 WITH LASER ON at minimum.
The laser remains on.
M5 -> the laser remains on.
M3S0
M5 -> the laser switches off.
--------------.
with version 1.1f the laser it does not light up during movement.
--------------.

Since during the movements of the laser is turned on to minimum power, is not a problem;
in these terms it is not a bug, but certainly abnormal operation.

Regards

[Zax]

Does it do the same with rapid move?

Your move did not have any spindle value, perhaps if you add S0 it will remain off.

I did not have this problem using 0.9g J-Tech firmware with T2Laser.

[RobotEyes]

No way.
G0 or G1 does not change anything
however S is a modal group command and MUST remain active until the next change
(Unless it did it .. it would be a serious bug)
In any case, even with the sequence:
M3S0
M5
G1X10Y10F1000S0 or (G0X10Y10F1000S0)
the laser lights in the movements.
and the laser stays on even sending M5 after move.
I have to send
M3S0 (or any S value)
M5
to switch it off.
It's something I noticed at the very beginning,I had talked to someone (I forget who) on the forum
and it was told that it was a known problem.
So I no longer thought about it also because does not create damages.

With GRBL 1.1 the problem no longer occurs, and version 1.1 is definitely recommended;
has greatly improvement (especially on transmission errors).

In addition, I repeat, is not a software problem, it is a firmware problem.
It occurs sending commands by terminal  (Putty or Term)

No layers in the middle .... direct dialog with GRBL.
So.... nothing we can do.... (without entering in GRBL sources, not my job).