E-stop/alarm issue about stm32f1xx HOT 5 CLOSED

I'll look into this later - I have a busy weeh ahead.

from stm32f1xx.

Thanks Terje - no rush.

Out of curiosity, I tried a few other things on my side:
Reverting to a commit from February 2023 and the issue still happens.
When a program is running, e-stop triggers Alarm 3 and stops the program.
When homing, e-stop triggers Alarm 6, as expected.

Let me know if there is anything else I can do to help troubleshooting.

from stm32f1xx.

E-stop now works as expected and triggers alarm. Thanks for looking into this!

I did look at the fix and, as I understand it, the if statement below is always true:

Not sure this is related, but I also get an error when probing (same as issue 499. The probe now triggers Alarm 4 (and stops moving) just after the first contact.
Looking at the code, I cannot figure out why the changes impacted the probe.

from stm32f1xx.

I did look at the fix and, as I understand it, the if statement below is always true:

My bad, I added the always true when debugging - will fix in the next commit.

The probe now triggers Alarm 4 (and stops moving) just after the first contact.

The retract (latch) distance is too short?

from stm32f1xx.

Thanks a lot, this is brilliant. Everything works fine now.

from stm32f1xx.