M11 doesn't switch the laser OFF (sometimes)

[richardk]

Hello,
I have a problem that the first M11 command in my code doesn't turn the laser OFF. Plus also one more somewhere towards the end of the code. Please could you check that using attached code? I have fixed that temporary by modifying of my post-processor to generate double M11 (which works).
I am able to reproduce it using version 1.2115 and also 1.2113.
Thanks much,
Richard

tst.zip

(73.65 KiB) Downloaded 335 times

[dezsoe]

You have too many functions defined to some output pins. While it is possible and sometimes useful, don't set anything on the same pin as the laser output. Use the Pin mapping plugin to check your settings. (It works from the profile, so you have to save your settings before you open the plugin or reload the settings.)

[richardk]

Hello Dezsoe,
Thank you for the reply. I've modified my profile to have laser PWM function only on given pin. Unfortunately, I do not see any change: laser is not switched OFF on first M11 in my code. After I double the M11 in the code, laser is switched OFF. Please find the updated profile attached..
Richard

Profile.zip

(18.51 KiB) Downloaded 342 times

[dezsoe]

Hello Richard, We could find the issue and it is fixed in the 1.2116 development release. Also, one of the arcs was wrong using your sample g-code, it's also fixed.

[santiniuk]

Hi,

Just getting some time to test out v1.2116

I'm also experiencing the same issue with the M11 command not turning off my laser when the code is running.

No changes to my hardware, and duplicated all setup pin configurations as v1.2115. This works perfect.

Thanks

Shaun

[muxer]

I had this issue, was driving me mad. In my case M11 did not work before some rapid moves when both X and Y coordinates were changed, but again not every time.

1.2116 works now fine and this issue is not reproduced anymore.

[cncdrive]

Dezsoe, please test this.

[dezsoe]

We could find the issue and it is fixed in the 1.2116 development release. Also, one of the arcs was wrong using your sample g-code, it's also fixed.

[muxer]

So, now I have opposite situation with laser not turning on with 1.2116

I've narrowed it down to a situation where I have only G1 commands and laser is being turned on and off in between. Such patterns are used for raster burning (I use lightburn + minor postprocessing), i.e. in scanning mode.

So code like this

Code: Select all

G91
M3

G0 Y10
M11 Q0
G1 X10 F3000
M10 Q200
G1 X0.311 F3000
M10 Q0
G1 X12.269 F3000
M10 Q200
G1 X0.311 F3000
M10 Q0
G0 X10


does not fire laser at all, however if I change all moves with turned off laser to be with G0 it works as intended.

Code: Select all

G91
M3

G0 Y10
M11 Q0
G0 X10
M10 Q200
G1 X0.311 F3000
M10 Q0
G0 X12.269
M10 Q200
G1 X0.311 F3000
M10 Q0
G0 X10


I have also noticed that if I have first command to turn laser, i.e. M10 Q200 it will stay turned on through all next commands. It looks like some optimization is just ignoring all M10/M11 commands until G1 mode is changed.

When cutting vector shapes this issue does not show up because laser is switched off first and then moved with G0 as a standard practice.

[cncdrive]

Dezsoe, please test this.