Adjust SystemStatusFlags and SystemState to account for critical errors
requested to merge CLUS-711-update-warnings-add-errors-and-the-possibility-to-disable-shutdown-change-critical-state into development
Description
As part of the Safety features implementation project, the statuses of the modules were updated to contain critical temperature errors. Maybe more will be added in the future, buto this suffices for now. Also, the former "CRITICAL" was turned into "RESOLVED", which makes more sense since it refers to past erros that were already resolved.
Type
-
New feature (non-breaking change which adds functionality)
Related MRs
https://gitlab.com/qblox/packages/software/pulsar_src/-/merge_requests/198/diffs#note_1455488735
Testing
Triggering the error and reading the status out, seeing it get parsed properly.
Notes
We should just use JSON objects to pass this information back and forth from/to the firmware. That should be tackled in a different MR though, most likely.
Merge checklist
-
Cleaned up code (correct alligment/spacing/code-style, no dead code, etc). -
Merge request targets development
branch. -
Assigned assignee (you) and reviewers (team-members). -
Merge request has been reviewed by at least one team-members. -
All pipelines pass, including manually triggered ones.
Edited by Edmundo Ferreira