Stop Macro Arguments

[CthulhuLabs]

So I am converting my Shapeoko CNC from using their GRBL controller to a Duet 3 (running in SBC mode with RRF 3.3rc3). The Gcode files use M0 commands for tool changes like this:

G90
G21
(Advanced....)
M05
M0 ;T102
M03S18000
G0X88.252Y122.935Z12.700
G1Z-0.762F381.0
Y127.648F1143.0
X92.965
X92.186Y127.035
X91.305Y126.271
X90.390Y125.396
X89.603Y124.566
X88.843Y123.688
X88.252Y122.935
...

I can use the stop.g macro to handle this (I think). My question is if the ;T102 that comes after the M0 is passed as an option to the stop.g file. T102 represents the endmill to use and I would like to have the stop.g macro prompt the user to load that tool.

[dc42]

M0 terminates the job, so it makes no sense to have any GCode commands after it.

[CthulhuLabs]

@dc42 well that sucks. Guess Ill have to write a secondary post processor to convert GRBL gcode files to something RRF can process. Most of the software used by Hobby CNCs seem to use M0 for tool changes like this.

[CthulhuLabs]

Woohoo! After playing around with a bunch of settings I was able to get the CAM software to export with M6 commands so all I need to do is implement my own /sys/M6.g macro. No post processing needed.