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

Add error code descriptions #22

Closed
pavel-kirienko opened this issue Jul 1, 2019 · 1 comment · Fixed by #28
Closed

Add error code descriptions #22

pavel-kirienko opened this issue Jul 1, 2019 · 1 comment · Fixed by #28
Assignees
Milestone

Comments

@pavel-kirienko
Copy link
Member

Currently, whenever the firmware enters the Fault state (in other words, begins execution of the task Fault), Kucher displays the error code and says "elaboration not available". This is not cool. We need to make it display proper error messages as documented in this table: https://kb.zubax.com/display/MAINKB/Error+codes

The firmware has several tasks:

  • Idle
  • Fault
  • Beep
  • Run
  • HardwareTest
  • MotorIdentification
  • LowLevelManipulation

They are indexed starting from zero. Each task may fail; upon failure, it returns an 8-bit error code, where value 0 is reserved to indicate success and hence can't appear among error codes. The error coding is therefore two-dimensional; for example, the error code 2 for the task Idle means "Hardware test failed", and the same code 2 for task Hardware Test means "DC voltage error".

Kucher should contain a YAML resource file listing the textual description of each error code for each task; the file should be read once at startup and used to look-up error descriptions.

@pavel-kirienko
Copy link
Member Author

Paging @dimracer FYI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants