"abort" command disables all heaters?

oozeBot

The abort command is working well for our integration except that it disables all heaters when called. That is not what we want to happen.

Is there another way? If not, we'd ask this be captured as an enhancement.

Thanks

chrishamm

@oozeBot Where do you call abort? When I call abort from a standard macro, it leaves the heaters on on my setup.

oozeBot

@chrishamm hmm - we'll do some more digging to see if we can find the culprit and report back. Glad to hear this was not the intent of the abort command.

OwenD

@oozeBot
I suspect that if you have a print running and you use abort, say in a homing file, the in would shut down heaters.
Personally, I think that is how it should be by default.
I'd be happy to see alternate behaviour by way of a parameter.
Or perhaps introduction of a "halt" command that would cancel any macros and prints, but leave heaters, fans, spindles etc running?

oozeBot

@OwenD That may be what's happening.. we added "abort" to M401 and a few other places. However, since our printers operate in a heated chamber, we have added an option for the printer to "stay hot" as it's an expensive and time consuming process to heat soak the machines. What we are seeing is the "abort" command breaking this functionality..

T3P3Tony

@oozeBot can you compare as @OwenD says, with abort in and outside a print.

Where you are using abort, can you (as a work around) use e.g. break and/or M99 to get out the loop/macro?

oozeBot

Does M99 only break out of scripts called with M98? We are still testing, but if so, it's not going to be the overall solution for our challenge.

Abort with an option to leave the heaters on still seems like the most useful solution. Does Abort do anything other than stop all processes and disable the heaters?

Thanks

dc42

@oozeBot the M99 command will break out of any macro, whether it is called explicitly by M98 or implicitly because it is a system macro such as bed.g.

'abort' will terminate all nested macros and the current job, if any. I don't remember whether it tries to run cancel.g or not when it aborts the current job; but if it does, then the heaters will be turned off if there is no cancel.g file.

oozeBot

@dc42 said in "abort" command disables all heaters?:

I don't remember whether it tries to run cancel.g or not when it aborts the current job; but if it does, then the heaters will be turned off if there is no cancel.g file.

We tried creating cancel.g in hopes that would not disable the heaters, but no luck - they are still disabled when abort is called.

T3P3Tony

@oozeBot is it running cancel.g?