I started playing with the on_abort.ngc and it might work. I need to play a little more. At this point it does a little more than I want it to. It will trigger it for F2 (what I want), but also triggers it when exiting a running milling file with the escape key (not what I want) and the machine does not enter machine off.
The machine state I'm dealing with is particular about how it is entered and exited. I can't simply turn it on or off without the machine moving, when the M-code is active, it can be turned off without issue when the machine is not enabled (in machine off). So I only want the on_abort sequence to cancel my M-code state when the machine is aborting to machine off. Aborting to a machine on state, such as when aborting a running g-code file, the M-code state needs to be left alone, and the operator will have to clear it themselves (else the machine will shutdown with following error alarms.)
In the remap instructions I read about making some things conditional. I'm going to try to play with that now.
