You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: