Version: Affects all versions, fix version v2.7.0.
Describe the feature you'd like
Right now, our terminal interface throws a fail-fast error on an invalid command. We should consider doing more graceful handling that gives a sign that something went wrong but then continues execution.
Describe alternatives you've considered
N/A
Additional context
Could be a decent early issue. Implementation would be to implement a new static "invalid subcommand" function that turns the LED red and beeps a couple times (or something), and then returns to the terminal loop.
True hardware errors should remain fail-fast e.g. a flash write fail.
You may need to add a status to the status enum for these "invalid subcommand" errors for modules that implement their own subcommand handler internally.
Consider flushing the USB buffer when this is hit.
Points of Contact
FC Rev. 2 Project Lead: @NArmistead
Version: Affects all versions, fix version v2.7.0.
Describe the feature you'd like
Right now, our terminal interface throws a fail-fast error on an invalid command. We should consider doing more graceful handling that gives a sign that something went wrong but then continues execution.
Describe alternatives you've considered
N/A
Additional context
Could be a decent early issue. Implementation would be to implement a new static "invalid subcommand" function that turns the LED red and beeps a couple times (or something), and then returns to the terminal loop.
True hardware errors should remain fail-fast e.g. a flash write fail.
You may need to add a status to the status enum for these "invalid subcommand" errors for modules that implement their own subcommand handler internally.
Consider flushing the USB buffer when this is hit.
Points of Contact
FC Rev. 2 Project Lead: @NArmistead