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

Investigate fault-tolerance (FMEA) #1257

Open
4 tasks
dcstraney opened this issue Jun 24, 2022 · 2 comments
Open
4 tasks

Investigate fault-tolerance (FMEA) #1257

dcstraney opened this issue Jun 24, 2022 · 2 comments
Assignees
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

Comments

@dcstraney
Copy link
Contributor

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:

  • Read up on formal FMEA documentation in general, and any details specific to IEC 60601
  • Identify and list potential failures to simulate
  • Do design calculations to predict how system should behave in the case of each fault (for example: predicting DC input current if a power supply is stuck drawing its max. current limit).
  • Test it out on a real prototype to check these predictions

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.

@dcstraney dcstraney added Documentation Improvements or additions to documentation Needs detail An issue that is too vague and needs to be edited for clarity Electrical Assigned to electrical team Mechanical Assigned to mechanical team Pneumatics Assigned to pneumatics team Testing Related to manual or automated testing Software Umbrella: GUI, Controller or CI labels Jun 24, 2022
@dcstraney dcstraney added this to the Indefinite milestone milestone Jun 24, 2022
@dcstraney dcstraney added this to Backlog in Mechanical / pneumatics / manufacturing via automation Jun 24, 2022
@dcstraney dcstraney added this to Backlog in Software via automation Jun 24, 2022
@dcstraney dcstraney added this to Backlog in Electrical / PCB via automation Jun 24, 2022
@martukas
Copy link
Member

This likely supersedes and encompasses #751 ?

@dcstraney
Copy link
Contributor Author

Yes good catch, closed out #751 for that reason but forgot to mention it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants