This year we want to focus on using SmartDashboard as a tool for the drivers. Logging anything that they don't actively need to drive the robot isn't useful, because we can view the data in AdvantageScope. There are only a couple things that the drivers need:
a LoggedDashboardChooser to select the starting position of the robot
a LoggedDashboardChooser to select the auto we are running
a LoggedDashboardBoolean to stop ArmPID from moving the arm in case the arm encoder is broken
a LoggedDashboardBoolean to reset the arm encoder to the starting position
a LoggedDashboardBoolean to stop the IntakePiece command from turning off when it detects a current spike (the operator instead would have to stop holding down the intake button)
I think that's it?
AdvantageKit docs appear to be harder to find than birds for #17 but all the relevant code is here
This year we want to focus on using SmartDashboard as a tool for the drivers. Logging anything that they don't actively need to drive the robot isn't useful, because we can view the data in AdvantageScope. There are only a couple things that the drivers need:
LoggedDashboardChooserto select the starting position of the robotLoggedDashboardChooserto select the auto we are runningLoggedDashboardBooleanto stopArmPIDfrom moving the arm in case the arm encoder is brokenLoggedDashboardBooleanto reset the arm encoder to the starting positionLoggedDashboardBooleanto stop theIntakePiececommand from turning off when it detects a current spike (the operator instead would have to stop holding down the intake button)AdvantageKit docs appear to be harder to find than birds for #17 but all the relevant code is here