bluerobotics / bluerobotics/BlueOS
BlueOS 1.5, autopilot not started.
- Dominant language
- Vue
- Stars
- 453
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 174
Description
Symptoms:
- UI atupilot page didn't load
- `/vehicle_type` retunrning a 503 `No board running`
- no mavlink-server
- MCM unable to talk MAVLink
Settings show:
```json
"start_on_boot": false
```
This is a UX bug: just got into this limbo somehow and found no way of solving it from the frontend.
This probably happens in 1.4 as well.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the state with "start_on_boot": false and inspect the autopilot UI page, the /vehicle_type response, and the MAVLink/MCM symptoms described here. Done means the frontend provides a way out of the no-board-running state and the autopilot page loads without leaving the vehicle unusable.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100