bluerobotics / bluerobotics/BlueOS
Add tool for troubleshooting common parameter issues
- Dominant language
- Vue
- Stars
- 453
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 174
Description
Now that we have parameters accessible, we can start doing some validation on BlueOS.
My idea is to have a "troubleshooting" page which shows possible issues and displays a "fix it" button for each on them.
This wont hurt users who do weird things on purpose.
- Mavlink LOG Streaming (#1226)
- LOG_DISARMED must be set to 0 for mavlink-router to not freak out
- Navigator-specific:
- LEAK pins
- COMPASS_EXTERN should be set to 0 for ak09915 and mmc
... this list will grow. p
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing BlueOS parameter-access and page entry points; the issue names no files or tests. Review how parameters are exposed, then determine the scope of the troubleshooting page, its listed checks, and the expected behavior of each “fix it” action before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100