search

Team-4536 / Command-Based-2015

0 stars 0 forks source link

Add elevator variables to the SmartDashboard #9

Open stepansubbotin opened 9 years ago

stepansubbotin commented 9 years ago

This would be pretty awesome for troubleshooting and pre-match inspections.

AnonymousAnion commented 9 years ago

It'd maybe be nice to make a command group to print out all the information we would want to print out from our subsystems. I guess that could go in the update command group maybe?

On Thu, Jul 9, 2015 at 11:13 PM, Stepan Subbotin notifications@github.com wrote:

This would be pretty awesome for troubleshooting and pre-match inspections.

  • The three limit switch values.
  • The secondary stick y value.
  • The current elevator height (when the encoder code is implemented)

— Reply to this email directly or view it on GitHub https://github.com/Team-4536/Command-Based-2015/issues/9.

inkling16 commented 9 years ago

Liam: I don't really understand why a command group would be used here, can you explain more what you are envisioning?

I agree that we should print out all of those things, what would also be cool is if the Smart Dashboard told us which command is running on each subsystem. We would just need to have each command print its own name to the the smart dashboard in its constructor.

AnonymousAnion commented 9 years ago

Yea and we could put all those print commands inside a print or update command group to further organize them. All smartdashboard print commands would be in a smartdashboard print command group so that they would all be in one place and we can easily control what prints to the smartdashboard because it's all in one place.