-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E-stop/alarm issue #51
Comments
I'll look into this later - I have a busy weeh ahead. |
Thanks Terje - no rush. Out of curiosity, I tried a few other things on my side: Let me know if there is anything else I can do to help troubleshooting. |
… Ref. issue #51 and core discussion 499.
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: Lines 2094 to 2095 in 0903727
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. |
My bad, I added the always true when debugging - will fix in the next commit.
The retract (latch) distance is too short? |
Thanks a lot, this is brilliant. Everything works fine now. |
Hello,
I am using a reprogrammed Mach3 BOB which works great for my mini mill.
The only issue I found is that when the e-stop is active, I am still able to jog the machine.
The e-stop is detected by grblHAL and reported by ioSender as a red square above the E or the R letter, depending on configuration. The controller does not seem to enter alarm state.
I tried many build configurations with ESTOP_ENABLE set and unset, building with the web interface, PlatformIO and STCube. The issue happens in all cases (e-stop becomes reset when the flag is set to 0, but still no alarm state and I am able to jog the machine).
I also have a Teensy board and the problem does not happen there, despite very similar flag settings/configurations.
The text was updated successfully, but these errors were encountered: