Need A Little Help On How To Make Autonomous Switcher

[Shaif]

Command Based seemed a little intimidating for a rookie team like us with little man power, so we just did what we could with Iterative and we stayed as far away as possible from smart dashboard only because we didn't want to mess up anything that was already functional and not know how to fix it in time for the competition. But maybe now would be a good time to try these features out and learn how to use them to mentor the team for next year.

[virtuald]

Originally Posted by Shaif

Command Based seemed a little intimidating for a rookie team like us with little man power, so we just did what we could with Iterative and we stayed as far away as possible from smart dashboard only because we didn't want to mess up anything that was already functional and not know how to fix it in time for the competition. But maybe now would be a good time to try these features out and learn how to use them to mentor the team for next year.

That's ironic given command based is supposed to be "easier to use".

[gr8dragon]

In the past I know teams to have used the disabled routines in the C++/Java libraries in which they set autonomous state based on joystick button press. If joystick 1 is pressed then autonomous 1 is run and so on. Its simple and doesn't require any new hardware. I do believe this is still legal because you would do this before the MC does the countdown, and autonomous actually starts. Make sure the robot is connected fully to the driver station in order for this to actually work.

[JefferMC]

We have used Sendable Chooser, but had issues with stability with SmartDashboard usage that year and quit using SmartDashboard all together.

Last year, I believe it was, we used the DigitalInput switches on the IO page the DriverStation software as switches to select an autonomous program. But those went away this year. Pity.

We are using Preferences this year, but are having problems with the preference values getting stored in the file when set in SmartDashboard. So... we've been editing the Preferences file on the DS computer, then copying to the Robot with FTP. I'm debating going back to a Sendable Chooser, or using a Sendable chooser to set the Preference.

Before SmartDashboard, et al, we would use a series of switches to select the number of the program we wanted to run.

Anyway, regardles of which of these mechanisms we've used, the chosen routine gets identified at RobotInit or AutonomousInit (depending on the actual mechanism), and executed at the appropriate time.

RE: Command Based robot vs Interative. If your robot needs to do two things at once, Command Based is the way to go. Otherwise, Iterative is okay.

[Shaif]

Originally Posted by JefferMC

We have used Sendable Chooser, but had issues with stability with SmartDashboard usage that year and quit using SmartDashboard all together.

Last year, I believe it was, we used the DigitalInput switches on the IO page the DriverStation software as switches to select an autonomous program. But those went away this year. Pity.

We are using Preferences this year, but are having problems with the preference values getting stored in the file when set in SmartDashboard. So... we've been editing the Preferences file on the DS computer, then copying to the Robot with FTP. I'm debating going back to a Sendable Chooser, or using a Sendable chooser to set the Preference.

Before SmartDashboard, et al, we would use a series of switches to select the number of the program we wanted to run.

Anyway, regardles of which of these mechanisms we've used, the chosen routine gets identified at RobotInit or AutonomousInit (depending on the actual mechanism), and executed at the appropriate time.

RE: Command Based robot vs Interative. If your robot needs to do two things at once, Command Based is the way to go. Otherwise, Iterative is okay.

So what do you think the people in the video that i attached in the original post were doing?