MARSProgramming / MARSProgramming/MARS-2020
Setup Dashboard Architecture
@liamhonecker is already working on this.
Since Feb 15, 2020.
- Dominant language
- LabVIEW
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Look at how the 2018 LV dashboard was made, and seek to mimic its behavior in regard to setting calibration values. There are a variety of requirements for the dashboard, a list off the top of my head for now is:
Controls:
-Auto play selection
-ability to change cals(this is the complicated bit, cals must save on the robot(preferably in a text file), and also be displayed back on dash upon boot up, dash must not push cals before an update, or all can become 0s. Work with andrew to think about this logic.)
Cals list:
-Drive PIDFs(same for both sides atm)
-Auto-Target on turret PIDS
-Cardinal points of turret
-turret limits(safeties)
-Magazine speed, intake speed
-Climb PIDs/settings(might be dependent upon zone where you climbed)
Indicators:
-flag/audio for when a ball is serialized
-if automated subsystems are active(targeting, climbing, etc.)
-current position/connection of all encoders(turret, drive, magazine, flywheel)
-if anything is broken/non-functional(related to safety tickets)
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.
Assessment
This issue has not been assessed yet.