3.6.0 beta1 - RC1 - Laser not working

jay_s_uk

@cichaczech can you post a sample gcode file?

cichaczech

;Custom GCode device profile, user origin
;Bounds: X69 Y193 to X105 Y210
G00 G17 G40 G21;Restore metric mode
G54
G90;Restore absolute mode
G0 X-1.001 Y-1.001 
G91;Restore relative mode
;Cut @ 5001 mm/min, 101% power

;
M42 P10 S0 ;Vypni napajeni Laseru
G0 X37 Y1 
;Layer C02
M42 P10 S1 ;Zapni napajeni Laseru
G1 X-37 S254 F5001
G1 Y18 
G1 X37 
G1 Y-18 
;
M42 P10 S0 ;Vypni napajeni Laseru
G90;Restore absolute mode
;

jay_s_uk

@cichaczech that seems to be using M42 to turn on the laser?
I think you need to check the settings in lightburn. you can find some suggested settings here
https://github.com/TeamGloomy/LPC-STM32-RRFUserConfigs/tree/master/K40 CO2 Laser - SKR 2 - ESP - paulg4h#lightburn-settings

cichaczech

@jay_s_uk I am using diode laser and M42 is just switching On/Off power supply to laser module for safety (when handling object inside laser machine). For switching laser output there is S command.

In Lightburn I am using Custom Gcode (experimental) profile to get rid off M3, M5, M7, M8 ... commands.

jay_s_uk

@cichaczech you need M3 and M5 commands

dc42

@cichaczech I only tested it from the console too. Perhaps it only works for isolated moves. I'll look at it again on Friday.

cichaczech

@dc42 , @jay_s_uk I managed to get it work.

In whole Gcode, even in the end script, there cannot be my M42 P10 S0 for disabling power supply to laser module and before first G1 command there must be G4 command.

Examples that not working:

;Custom GCode device profile, user origin
;Bounds: X69 Y193 to X105 Y210

;USER START SCRIPT
M42 P10 S1

;USER START SCRIPT
G00 G17 G40 G21;Restore metric mode
G54
G90;Restore absolute mode
G0 X-1.001 Y-1.001 
G91;Restore relative mode
;Cut @ 5001 mm/min, 21% power

;
;
G0 X1 Y-18 
;Layer C02
G4 P1
G1 X-37 S50 F5001
G1 Y18 
G1 X37 
G1 Y-18 
;
;
G90;Restore absolute mode

;USER END SCRIPT
M42 P10 S0

;USER END SCRIPT

or

;Custom GCode device profile, user origin
;Bounds: X69 Y193 to X105 Y210
G00 G17 G40 G21;Restore metric mode
G54
G90;Restore absolute mode
G0 X-1.001 Y-1.001 
G91;Restore relative mode
;Cut @ 5001 mm/min, 21% power

;
;
G0 X1 Y-18 
;Layer C02
;
G1 X-37 S50 F5001
G1 Y18 
G1 X37 
G1 Y-18 
;
;
G90;Restore absolute mode

And this one works:

;Bounds: X69 Y193 to X105 Y210
G00 G17 G40 G21;Restore metric mode
G54
G90;Restore absolute mode
G0 X-1.001 Y-1.001 
G91;Restore relative mode
;Cut @ 5001 mm/min, 21% power

;
;
G0 X1 Y-18 
;Layer C02
G4 P1
G1 X-37 S50 F5001
G1 Y18 
G1 X37 
G1 Y-18 
;
;
G90;Restore absolute mode
;

or

;Bounds: X69 Y193 to X105 Y210
G00 G17 G40 G21;Restore metric mode
G54
G90;Restore absolute mode
G0 X-1.001 Y-1.001 
G91;Restore relative mode
;Cut @ 5001 mm/min, 21% power

;
M5
G0 X1 Y-18 
;Layer C02
G4 P1
G1 X-37 S50 F5001
G1 Y18 
G1 X37 
G1 Y-18 
;
M5
G90;

with Sticky Laser it fires independently on M3 S0 (M3 S255) before move or M5 after so I choose to run without them, for now.

dc42

@cichaczech the issue appears to be that when a G1 move with parameter S0 is followed immediately by a G1 move with a nonzero S parameter, the laser is not turned on. This occurs even if the moves are sent from the console, e.g. when sending this:

g1 x-10 s0 g1 x50 s255 g1 x0

If I replace the s0 by s10 then it works as expected. I will fix this.

dc42

@cichaczech please try the firmware at https://www.dropbox.com/scl/fo/y03luwmbypirbxncla3rk/AAJFLPFsVdFylemyhkXsAac?rlkey=7cq4svp4rzl2ztdffpzq2ghjk&dl=0.

cichaczech

@dc42 it is working now. Thank you.