Final Dashboard Goal
@Helen-42 is already working on this.
Since Jan 26, 2022.
Assessment
This issue has not been assessed yet.
Description
Earl (and I) want many things for the dashboard, I'll probably update this page as Earl gives more requests:
(these will probably be split into different tab controls)
- All calibrations (PIDs, limits, etc.) to be accessible from the dashboard
- Important sensor data to be displayed on the dashboard
- Camera (default stuff for this)
- Climber GUI (will probably become its own sub-project): Earl wants modifiable distances/angles for every step of the climber sequence, and I want a diagram/drawing of each step as it happens so drivers have no way to be confused (I already talked to OPR about this)
Also, calibrations need to be stored locally on the robot, as well as ideally stored on the driver station somewhere in case of failure. The 2020-Dashboard-Standard has some systems in place for this, but it'll need to be modified due to the new system we found on Sunday. I'll work with Helen on designing this.
- Dominant language
- LabVIEW
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MARSProgramming/M15
-
better method/nice to have
Difficulty 4/5 3-5 days Newbie friendliness 30/100
MARSProgramming/M15#17 ·
-
vital
Difficulty 3/5 1-2 days Newbie friendliness 42/100
MARSProgramming/M15#16 ·
-
vital
Difficulty 3/5 1-2 days Newbie friendliness 35/100
MARSProgramming/M15#15 ·
-
vital
Difficulty 3/5 1-2 days Newbie friendliness 25/100
MARSProgramming/M15#14 ·
-
vital
Difficulty 4/5 3-5 days Newbie friendliness 25/100
MARSProgramming/M15#13 ·