I have a question from one of my fellow Makers at our MakerSpace.:
When I put material in Lasersaur for cutting, I need to know which lasing power and feed rate to use for it to cut through in optimal time. I know there are tables, but parameters (workpiece height, laser power/focus) may drift in time. So I would like to be able to run a dose test on a coupon of material before starting the real cutting job. Something like this:
The solution I came up with is a ~7x10 cm test cut with "S" value (laser power %) rows and "F" value (feed rate) columns. The problem is, I cannot output it in one job to Lasersaur!
When sending a job to Lasersaur, one should specify the power % and feed rate in the browser app, and this overrides all other values.
So I have a g-code file with all the right S and F commands, but the only way I can output it to Lasersaur is via ssh to BeagleBone (control computer in Lasersaur), and then cat > /dev/ttyO1 . This is hardly convenient, and has issues with buffer overruns...
If this issue of not being able to change lasing power/feed rate while cutting programmatically is confirmed, this means that it is currently impossible to engrave in grayscale (!)
So my question is: how can we fix this?
Option 1: change the (Python?) code of Lasersaur front/backend so that it does not override the S and F values
Option 2: install newer control software (driveboardapp?, something else) which has these bugs ironed out
Option 3: a more clever idea?
Please share your ideas and thoughts.