bluerobotics / bluerobotics/cockpit
frontend: expose vehicle health and calibrations
- Dominant language
- TypeScript
- Stars
- 198
- Forks
- 63
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 57
Description
### Current behaviour
Sensor calibrations and pre-arm checks can be required by the autopilot before arming is permitted, and for reasonable vehicle performance, but the state of these requirements is not directly exposed to the user, either as indicators or required actions - just as warnings/errors from the autopilot when trying to perform certain actions.
### Expected or desired behaviour
1. Indicate the current calibration state of the connected sensors, or at least notify of any that are unhealthy and/or need to be calibrated before arming is available
- [ ] This could likely by done by exposing the bitmaps from the regular [`SYS_STATUS`](https://mavlink.io/en/messages/common.html#SYS_STATUS) MAVLink messages from the autopilot through the data-lake, and creating one or more mini-widgets that use those to indicate vehicle health
- These could be included as automated checks in a default version of #22
- [ ] To make this actionable, we could include a link to the relevant vehicle setup page(s) in BlueOS, if BlueOS is connected, and otherwise describe what would be needed in some other control station software
- #1051 could be an alternative to linking, but has the caveat that it may be a somewhat jarring interface difference, and it's potentially unnecessary to include a separate interface like that inside a panel when we can link to open the full page in a separate tab / browser window instead
2. Indicate the health of the vehicle position estimate, as a combined indicator that considers GPS, visual odometry, etc
- #1102 would be a relevant action for local positioning systems (e.g. non-GPS based ones)
### Prerequisites
- [x] I have checked to make sure that a similar request has not already been filed or fixed.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how MAVLink SYS_STATUS data reaches the data-lake and how existing frontend mini-widgets consume vehicle state. Define the scope for calibration, pre-arm, and position-estimate indicators, then verify that the resulting widgets expose actionable health information and appropriate BlueOS or control-station guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100