You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Every time we have to manually check the shoulder, wrist, arm readings to make sure they are reading the proper values before starting robot operations. It would be useful to have some sort of LED feedback to indicate if anything on the robot is wrong. Also, the human player sometimes has diffculty known if a cone / cube is needed (LEDs can be used to show).
Describe the solution you'd like
Include LEDs signals for:
Game object pick up
Certain robot errors (limelight not connected, CAN / motor controller fault, etc… ) – flash red
Display for auto selected (and / or alliance color)
Vision based checks for if robot is setup correctly in auto (especially if the game needs you not to be pressed up against something)
Battery not changed (voltage low)
Investigate how you can individually address them through AddressableLEDs (see WPILib docs). This will allow, for example, how we can differentiate between a incorrect reading vs. limelight not connected.
Describe alternatives you've considered
Own interface for ease in value display (instead of ShuffleBoard)
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Every time we have to manually check the shoulder, wrist, arm readings to make sure they are reading the proper values before starting robot operations. It would be useful to have some sort of LED feedback to indicate if anything on the robot is wrong. Also, the human player sometimes has diffculty known if a cone / cube is needed (LEDs can be used to show).
Describe the solution you'd like
Include LEDs signals for:
Investigate how you can individually address them through AddressableLEDs (see WPILib docs). This will allow, for example, how we can differentiate between a incorrect reading vs. limelight not connected.
Describe alternatives you've considered
Own interface for ease in value display (instead of ShuffleBoard)
Additional context
The text was updated successfully, but these errors were encountered: