Abort command in load.g/unload.g doesn't work as expected



  • If an abort command is called when loading or unloading a filament (both with M701 or M702 and with the Duet Web Control), Duet will then change the filament name of the associated tool, as the filament was correctly loaded or unloaded. A very strange behavior happens, instead, when an error (such as G0/G1: insufficient axes homed) is thrown: in this case the filament name is not changed. The problem happens both if the abort command is inside load.g/unload.g file and if it is inside a nested macro called by load.g/unload.g.


Log in to reply