Homing Alarm 11 Not Asserted Following E-Stop #858
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I encountered an issue when homing required is enabled. It seems that Alarm 11 is never asserted following an e-stop with loss of position, but the machine remains in an Alarm state until the homing cycle is run. There is a message reported that homing is required, however these messages are not always visible (i.e., if I am operating the machine from a pendant / controller that only reports Alarm codes).
I'm thinking instead perhaps it would be better to mirror the handling case where homing is required but only some axes are homed.
core/system.c
Lines 466 to 477 in e272f77