Investigate fault-tolerance (FMEA) #1257
Labels
Documentation
Improvements or additions to documentation
Electrical
Assigned to electrical team
Mechanical
Assigned to mechanical team
Needs detail
An issue that is too vague and needs to be edited for clarity
Pneumatics
Assigned to pneumatics team
Software
Umbrella: GUI, Controller or CI
Testing
Related to manual or automated testing
Milestone
At some point we should do some serious systematic analysis and testing of how the design behaves in the case of various faults, and adjust the design as necessary to keep as much functionality as possible in single-failure cases - for example, we'd like the blower to keep running in as many situations as possible, and there should never be a "silent" failure that impairs functionality in some way without an alarm or notification.
It looks like there was a higher-level FMEA done before, which is plenty useful - but to know how good the design is at taking some hits we'll need to drill down further into details.
Subtasks:
Starting points
I'm not really qualified to comment on the mechanical parts, but the electrical failures to test include: over-current/shorts on each power rail, each power supply "failing open", individual external wires broken or entire external connectors unplugged, or input power brownout. Software faults could include an infinite loop in a task.
Feel free to remove labels or split this into multiple issues if this is too much of a kitchen sink.
The text was updated successfully, but these errors were encountered: