macros wishlist

Anidal

Can you confirm that cancel.g exists?

if cancel.g exist - run cancel.g
if cancel.g not exsist - run stop.g

Is it any docymentation about this hidden behavior?

Phaedrux

@phaedrux said in macros wishlist:
Can you confirm that cancel.g exists?
if cancel.g exist - run cancel.g
if cancel.g not exsist - run stop.g

Is it any docymentation about this hidden behavior?

https://duet3d.dozuki.com/Wiki/Macros#Section_Pause_stop_and_power_fail

Pause, stop and power fail
pause.g is run when you pause a print.
resume.g is run when you resume a print.
cancel.g is optional, but if present is run when you cancel a paused print.
stop.g is optional, but if present is run when a print finishes normally with an M0 command at the end of the print job.
sleep.g If M1 is issued the firmware finishes any moves left in its buffer, then shuts down, the macro file sleep.g is run before all heaters and drives are turned off.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M0_Stop_or_Unconditional_stop

The firmware finishes any moves left in its buffer, then it executes the macro file cancel.g if present, if the axes are homed and if a print is being cancelled. Otherwise stop.g is run before all motors are put into idle mode. If no H1 parameter is present, the heaters are turned off too. See also M1, M112.

Anidal

@phaedrux said in macros wishlist:

The firmware finishes any moves left in its buffer, then it executes the macro file cancel.g if present, if the axes are homed and if a print is being cancelled. Otherwise stop.g is run before all motors are put into idle mode. If no H1 parameter is present, the heaters are turned off too. See also M1, M112.

More new! That is, if you set M0 at the end of the file, then do macros execute cancel.g and stop.g?
At the same time, cancel.g is called when a manual stop occurs, and if not, then stop.g is called?
Why such a complicated macro call system? If one is not, then we call another, etc. And the conditions for calling one and those macros overlap. Isn't it easier for each event to single out 1, the only macro that is called only by it?

dc42

M0 causes stop.g to run; except that if the print is paused at the time, it runs cancel.g (if it exists) in preferences to stop.g.