More M581 interrupt support

  • Currently it seems that the only emergency response on triggering an endstop is T0 a full reset. While this is useful, as user Appjaws has pointed out it still leaves the hotend burning on the bed in some situations. I add my vote here to getting at least T1 to activate inside a macro if possible, but of course T2 would be great as well. I recognise that a T0 reset is probably substantially easier than manipulating the gcode queue as the other Tx triggers need to do, but it seems like an endstop change is by definition an interrupt event? Apologies if I haven't done enough testing or configuration to make this work with the current firmware.

Log in to reply