Weird issue Iām seeing that I think Iāve narrowed down to the handling of the M6 command.
If I send an M6T10
command in a file it throws an āunsupported commandā error.
If the M6 is solo, no error.
If the T10 is commented out with a semicolon, no error.
If the M6 and T10 are not on the same line, no error.
For some reason the M6 is not captured by gSender when followed by the T-word. There seems to be some inconsistency, but I canāt replicate the issues when it allowed the M6Txx right now.
Iāve been talking to Neil over in the Carbide Community forum about this. I submitted a feedback form to the gSender team yesterday. (Including the gcode and Carbide Create file to generate the gcode ) I am not sure what is really happening either other than it seems related to M6 Tool Change and T tool number commands. It is inconsistent, sometimes it works but it usually fails if these commands are in the first gcode file used after loading gSender.
It seems my ID has been promoted so I can now upload files. Here are the files I have been having this issue with.
Lamp1_gSenderTest.nc (26.1 KB)
ModernDeskLamp_SBL.c2d (275.5 KB)
Thanks for noting this guys! Yes this should be a simple fix for how weāre looking out for M6 lines in gSender. Weāll try a fix for it by the next build this coming Friday
Iāll update that 0.7.5 should now be handling this issue. Would you guys be able to confirm working as expected on your end now?
I think Neil now has a couple of macros that now work. He would need to confirm. I have been playing with the āCodeā option in 0.7.5. Itās better, but I still have one issue. If I put a āM0ā pause command in the Tool Change āBefore Change Codeā area, the code in the āAfter Change Codeā is not executed and the prompt for changing the tool does not come up. You only get a pause without a prompt. Hitting resume starts the loaded fileās g-code and not the āAfter Change Codeā commands. If there is no pause command in the āBeforeā commands, everything seems to work.
With this setup, the āAfterā commands do not run. Remove the āM0ā in the āBeforeā and they do.
This should be fixed in the next release.