Abort - delayed response problem

[woofy 12]

UM2.

I have a feeling this has been discussed before but I can't find it.

When aborting a print it takes a few moves before it actually aborts, probably because of some internal buffering. The problem is that the nozzle cooling starts immediately on aborting and is way too cool by the time the abort happens. The extruder has started skipping on the same section of filament.

Could the buffer be flushed on abort so it stops immediately, or if that's not possible could the nozzle temperature be maintained until it does the abort.

 

[Daid 306]

The buffer is 16 moves, but usually these moves are done before the head is cooled.

On the UM-Original this was never a problem, but the UM-Original has more thermal mass in the head.

I tried clearing the buffer, however, I ran into odd synchronization bugs. So I opted to leave the buffer alone on abort.

 

[woofy 12]

I was printing the brim of a box at the time. Those 16 moves amounted to 1.44 meters of travel. At 20mm/sec that's 72 seconds of cooling of the head while still trying to print.

Is keeping the nozzle heated during this time possible?

 

[phil-t 0]

Just to chime in and say this affected me the other day, I aborted in the middle of some long in-fill lines, and the head instantly starts cooling while the buffer is being emptied, resulting in a blocked nozzle..

Obviously you can work around it to some extent by aborting when it's working on smaller moves, but I think it'd be nice if the firmware could make this fool proof!