Laser turns off after following code is sent after M3

nelho

Hi @bishop86 it's possible to send me your program please ?
Thanks

morokolli

Hi,
Any progress on this?
I ran in same situation with following code with Release 2.04 (Duet 2) and 1.25 (Duet 06/085).
Tested also with 3.0beta12 (2019-11-02b1) using M452 C"exp.heater3" Q200.
Config is in attached file.config.g
Seems that heater3 output is turned off.
gcode:
;Project bugbug
; *** START begin ***
G90
G21
M84 S0
G92 X0 Y0 Z0
G00 X0.0000 Y0.0000 Z5.0000

;No. 2: Engraving 1
G00 X25.7569 Y48.9645 Z5.0000
G00 Z0.5000
G01 Z0.0000 F1200
M3 S255
G01 X19.7518 Y30.6457 F750
;bug hits here. previus move is lasered ok, next 2 moves not.
;if run line by line (pasting one by one to console) all works ok.
G01 X1.1829 Y30.6942
G01 X16.1260 Y19.5851
M5
G00 Z5.0000
G00 X0.0000 Y0.0000
M05

dc42

@morokolli, I'll test that when I get time.

Are you able to configure your GCode generator to generate S parameters on the G1 commands instead of using M3? That's the modern way of doing laser engraving, and it benefits from velocity ramping in RRF3.

morokolli

Tested with S parameter -> works like it should.
I had to ask from CAM software developer is it possible. I'm using ESTLcam at moment.
Waiting answer from there also.

morokolli

I did more testing.
While using attached G-Code error hits in even with S255 parameter.
First square is burned ok, then on another part start and goes well until light turns off after couple moves (somewhere around line 30-32) and comes back after next move.
Using Release 3.0beta12
Sample G-code:
[0_1573400684875_peukku.nc](Uploading 100%)

dc42

Did you select sticky laser power in your M452 command?

Your file upload to this forum doesn't appear to have worked. Please try again.

morokolli

Reload of sample and config.g.
config.g.txt
peukku.nc.txt

dc42

@morokolli said in Laser turns off after following code is sent after M3:

Reload of sample and config.g.
config.g.txt
peukku.nc.txt

M452 C"exp.heater5" Q200 ; laser uses heater3 pin, PWM frequency 100Hz

You didn't select sticky laser power. https://duet3d.dozuki.com/Wiki/Gcode#Section_M452_Select_Laser_Printer_Mode

morokolli

Still same thing while using:
M452 C"exp.heater5" Q200 S1
Here's video:
https://www.youtube.com/watch?v=2FMmwe_Vmpk

morokolli

More debug info:
If F value in G1 F300 is more than F1015 All lines are done as they should. If i's lower, piece is missing. And if speed is added over F1200, next line starts to suffer. Hopefully picture explains better:

craigb244

any update on this? im having the same issue.

M452 is set to sticky in the config but (quite randomly) it forgets the Gcode "stickiness" and only restores after it hits the next G1 Sxxx

craigb244

settings in my config file:

M307 H2 A-1 C-1 D-1       ; Disable Heater output on H2
M452 P2 I1 S1 R255 F200         ; Enable Laser mode, on output 2 (heater 2), with max intensity being 255, and a PWM frequency of 200

example of some gcode that causes issues (a simple square being cut)

;
; Operation:    2
; Type:         Laser Cut
; Paths:        1
; Passes:       2
; Cut rate:     5 mm/s
;


; Pass 0

; Pass 0 Path 0
G0 X57.57 Y76.11
; Pass Z Height 5mm (Offset: 0mm)
G0 Z5.00

M3
G1 X7.57 Y76.11 S255.00 F300
G1 X7.57 Y9.42
G1 X57.57 Y9.42
G1 X57.57 Y76.11
G1 X57.57 Y76.11
M5


; Pass 1

; Pass 1 Path 0
G0 X57.57 Y76.11
; Pass Z Height 4.8mm (Offset: 0mm)
G0 Z4.80

M3
G1 X7.57 Y76.11 S255.00 F300
G1 X7.57 Y9.42
G1 X57.57 Y9.42
G1 X57.57 Y76.11
G1 X57.57 Y76.11
M5          ; Disable Laser/Spindle
M106 P2 S0 ;turn off laser power

It seems quite random.
in the above case it did the first two lines of the cut before turning the laser off, restarted on the second pass and completed all 4 lines,

I ran the code again straight away and it did all four lines of the first pass, and turned off after the 3rd line of the second pass.

Im running the latest firmware RC4

Phaedrux

@craigb244 said in Laser turns off after following code is sent after M3:

Im running the latest firmware RC4

The latest full release is 2.04. What RC4 are you using? It's definitely not the latest.

craigb244

@Phaedrux sorry I was half asleep when I wrote that and been playing with a lot of firmwares (on other stuff)

I have the lastest firmware downloaded 2weeks ago, so what ever that is... I'll report back later when I'm home .

dc42

I'll test that square file on 2.05RC2 which is ready to go out. But I recommend RRF3 for laser cutters/engarvers because it implements velocity ramping.

dc42

@craigb244 said in Laser turns off after following code is sent after M3:

;
; Operation: 2
; Type: Laser Cut
; Paths: 1
; Passes: 2
; Cut rate: 5 mm/s
;

; Pass 0

; Pass 0 Path 0
G0 X57.57 Y76.11
; Pass Z Height 5mm (Offset: 0mm)
G0 Z5.00

M3
G1 X7.57 Y76.11 S255.00 F300
G1 X7.57 Y9.42
G1 X57.57 Y9.42
G1 X57.57 Y76.11
G1 X57.57 Y76.11
M5

; Pass 1

; Pass 1 Path 0
G0 X57.57 Y76.11
; Pass Z Height 4.8mm (Offset: 0mm)
G0 Z4.80

M3
G1 X7.57 Y76.11 S255.00 F300
G1 X7.57 Y9.42
G1 X57.57 Y9.42
G1 X57.57 Y76.11
G1 X57.57 Y76.11
M5 ; Disable Laser/Spindle
M106 P2 S0 ;turn off laser power

I just tested that file on 2.05RC2. It runs OK except that it turns the laser off at the start of the 4th side of the 2nd square. I will look into it.

dc42

On further investigation:

You are using both M3/M5 and G1 S parameters, which I wasn't expecting;
If I delete the M3/M5 commands so that it uses just G1 S oarameters, it works correctly
If I delete the G1 S parameters so that it uses just the M3/M5 commands, it fails

So G1 S parameters appear to be wrking correctly. but M3/M5 commands are not.

dc42

I found the issue with M3/M5 in laser mode. I am postponing the 2.05RC2 release until I have fixed it.

craigb244

@dc42 thanks for looking into this and glad my info helped find the issue (even more glad it's not something I've done my end!)

By the way my firmware is 2.04RC4 (2019-10-19b1)

Quick question...
You say "You are using both M3/M5 and G1 S parameters, which I wasn't expecting;"

Is using M3/M5 not the "correct" way to control the laser?

dc42

@craigb244 said in Laser turns off after following code is sent after M3:

You say "You are using both M3/M5 and G1 S parameters, which I wasn't expecting;"
Is using M3/M5 not the "correct" way to control the laser?

I was expecting user to either use M3/M5 to control the laser, or (preferably) use the G1 S parameter.

To fix this, what I plan to do is to make M3 set the default laser power for the start of the next G1 move, but not turn the laser on immediately. Likewise, M5 would set the default laser power to zero for the start of the next G1 move, but not turn the laser off immediately if it is moving. In both cases, an S parameter on that G1 move would override the power set by M3/M5.

Does this sound reasonable? It means that the laser will never be on when the machine is not moving. In one way, this is safe because it avoids accidentally burning a hold in the bed. However, it means you could leave the machine in a state in which the laser has been "primed" by M3, so that it turns on (perhaps unexpectedly) when you next do a G1 move.