The easiest way is to place a trap at the beginning of the m3 macro, which will end the macro without executing it.
You can activate the trap, for example, with a machine parameter:

Now, when you call the command #20=1 from the MDI or gcode line, the M3 macro will be skipped.
To cancel it, use #20=0
The easiest way is to place a trap at the beginning of the m3 macro, which will end the macro without executing it.
You can activate the trap, for example, with a machine parameter:

Now, when you call the command #20=1 from the MDI or gcode line, the M3 macro will be skipped.
To cancel it, use #20=0
jose-gzm has reacted to this post.