3.6.0 beta1 - RC1 - Laser not working
-
@cichaczech You should define one tool with M563 and enable it T#. You do seem to have 'sticky' mode enabled with M452 ... S1. Can you test if the laser fires if you have a G1 move with an S parameter, eg
G1 X10 S254
?Ian
-
@cichaczech I confirm that this is a bug. I've just fixed it in the new firmware builds at https://www.dropbox.com/scl/fo/1k4ahhplq0uy8o2668auw/AMhaLPbp66mjnWFMddNJoeI?rlkey=oke461u62k5vbmzkhbr1f7yos&dl=0. Use with care, in particular watch out for the laser misbehaving because the laser control code is not the same as it was in 3.5.x.
-
@dc42 with new firmware RC1+2, it works flawlessly. Thank you for the solution
.
-
undefined gloomyandy referenced this topic
-
@dc42 Ok, yesterday I tried it only from consele via DWC simple G1 command with S parameter and it was working.
Now I am trying to run program from Lightburn via USB and laser not fires again. If I export gcode from Lightburn a go command by command in DWC Console it fires ok, but not from USB or exported .gcode to Job jist in DWC. -
@cichaczech can you post a sample gcode file?
-
;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 ;
-
@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 -
@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.
-
@cichaczech you need M3 and M5 commands
-
@cichaczech I only tested it from the console too. Perhaps it only works for isolated moves. I'll look at it again on Friday.
-
@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.