Skip to content
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

Which limit switch is tripping #239

Closed
komradebob opened this issue Jul 31, 2017 · 2 comments
Closed

Which limit switch is tripping #239

komradebob opened this issue Jul 31, 2017 · 2 comments

Comments

@komradebob
Copy link

Would it be possible to modify the alarm that is tripped when a limit switch is reached to tell the operator which limit switch was hit?

Today it looks like:

ALARM: Hard limit
[Reset to continue]

I would propose something like:

ALARM: Hard limit - X axis
[Reset to continue]

@gerritv
Copy link

gerritv commented Jul 31, 2017

Pn:XYZPDHRS indicates which input pins Grbl has detected as 'triggered'.

Part of the response to '?' request from the GUI. Some GUI's display this, e.g. GrblPanel latches an indicator for the various pins.

@chamnit
Copy link
Contributor

chamnit commented Jul 31, 2017

@komradebob : If the limit switch is still not engaged when a hard limit is triggered (often happens when noise is present), there is no way to tell which one did*. The AVR processor only provides which port experienced a pin change. It does not specify or record which pin on the port triggered.

  • If by chance the limit pins were all placed on different ports AND no other pin with an external interrupt is used on the same port, then you could tell which pin triggered. You can only do that on something like an Arduino Mega2560, where there are enough pins and ports to do something like that.

@chamnit chamnit closed this as completed Jul 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants