M915 stall detection for emergency stop? And emergency stop.

gratgrat27

Hi,

My configuration is a duet2 board with rep-rap 3.3 on a workbeeZ1+.
I'm trying for a while to have an emergency stop that is not waiting for buffered moves to finish, AND offers a resurect file generation (or at least stop index of SD file interupted)

Could M915 does that ? After what I red I understand that it won't be efficient at high speeds, and not necessary reliable, not sure if the stop comes before or after the buffered moves.

More in details, because I sometime run 24h roughings and more for finishings (you can see my creations at BoisEtReliefs on etsy if you like!), I had spindle stop, coal used, wire cutted, etc leading the workbee moving 3mm deep with ½ inch tool not turning... and that for 30 minutes the first time, the nightmare.

I now use a real time current check arduino module with trigger T1 to pause but the buffered moves take sometimes long time before the stop especially for the 1m straight cut of the beginning of some creations, and I recently broke a tool.
So if M915 is instantaneous, and offers a saving point it would be gold for me!
By the way, is it possible to use trigger T0 (instantaneous M112 stop) and create a resurect file, or any restarting point save?

Otherwise I will go for a dedicated relay on power supply associated with the arduino module.

Thanks a lot.
Alex

jay_s_uk

@gratgrat27 add segmentation
M669 S1 T1 or similar. That will break long moves up, allowing you to pause etc a lot quicker

gratgrat27

Oh that's a really good tip thank a lot Jay

gratgrat27

Well I tried adding M669 S0.1 in the user setting file but nothing changed.

T parameter sets the minimum segment length and I want to reduce it so I didn't use it.

gloomyandy

@gratgrat27 Did you try the settings that Jay suggested? Unfortunately I think you need a later version of RRF to have M669 with no parameters to report the current segmentation settings, which would be useful to check what is actually being set.