Quote:
Originally Posted by ToddF
One of our lessons learned, which we will be implementing next year, is eliminating any reliance on the smart dashboard. We'll be putting our auto mode selection on the robot. We have been burned too many times by a malfunctioning smart dashboard on our control station computer. It always seems to happen at the worst possible time.
I hope to never again have this conversation:
"Why did the robot just sit there in auto?"
"The smart dashboard crashed just before the match, and we didn't have time to restart it."
|
The worst is when, you have one auton you run 70% of the time, but you need a different auton for this match. And THAT's the match where your driver station keeps dropping connection, and you have to use the field's driver station, and SmartDashboard won't load for your robot on that computer, and then you have to go out to the field and move your robot in front of the Sally Port so you can just get two points instead of breaking your arm, and then you don't get the two points anyway. And you lose the match.
Anyhow, not speaking from experience or anything, but consider alternatives for selecting autonomous modes in competition. SmartDashboard is great for practice and development adjustments however.
Coding multiple autons is really easy though. If statements, or switch cases, that call each method depending on the state of a sensor on the robot (e.g. a potentiometer or series of switches), or the state on SmartDashboard.