DWC - dashboard move buttons: using G1-movements for XYZ-moves?
-
Im using the Duet 3 with the lastest unstable releases in laser mode.
Writing my own programms and using homing-macros works as expected: G0 moves don't turn the laser on, G1s do.
If I move my x,y or z-axis in the Dashboard the movements seem to be G1 movements as the laser fires
- I only noticed this because my z-movement is slow. If i set the speed of movement buttons to 500 - all movements fire.Do i need to invert the pin in Laser mode definition - if so, why do the G0 and G1 movements work as expected?
-
Might this be because of the sticky S setting in laser mode definition?
-
@Royassas said in DWC - dashboard move buttons: using G1-movements for XYZ-moves?:
Might this be because of the sticky S setting in laser mode definition?
Yes. If you set the sticky feature then the S parameter is remembered across G0 moves. This is IMO a dangerous thing to do, but unfortunately it's what the programs that generate GCodes for laser cutters and engravers expect. I'd much rather those programs generated the S parameter on every G1 move that needs the laser on, which would be the safe thing to do.
You can use command G1 S0 at the end of your GCode file (or in your stop.g file, if your program ends with a M0 command) to reset the laser power to zero.
It's occurred to me that the firmware could remember the laser power setting separately for each input channel, so I may implement this in a future firmware version. I'll also change it to reset the remembered laser power to zero automatically at the end of a job, if it doesn't already.
