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

support sticky and non-sticky faults with FaultReporter #63

Open
gcschmit opened this issue Nov 18, 2023 · 0 comments
Open

support sticky and non-sticky faults with FaultReporter #63

gcschmit opened this issue Nov 18, 2023 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@gcschmit
Copy link
Contributor

For each fault reported by FaultReporter, we need to decide if that fault should be considered "sticky" (i.e., remains reported until the code restarts) or "non-sticky" (i.e., is removed as a fault when addressed). This is worth a discussion since if a fault is resolved, we may wish it to remain sticky so that we are aware it occurred; especially, if we didn't fix it. For example, if a device cannot be found on the CAN bus and then later is found on the CAN bus, do we want that fault to be removed? We may if we plugged in the power to the motor, but we may not if the issue is intermittent and we need to troubleshoot it.

@gcschmit gcschmit added enhancement New feature or request help wanted Extra attention is needed labels Nov 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant