| mathking |
09-18-2016 09:55 AM |
Re: FRC Robots Aren't Real Robots?
Quote:
Originally Posted by Type
(Post 1607282)
It was awhile ago so I don't remember it all but our default auto didn't work either. I wanna say we weren't connected to the field but it seems like they would have noticed the light. I was just trying to say in a world where everything worked as its supposed to, it would be a good idea but there are times where the field messes up.
|
The problem we, and others, have had is that if you use the dashboard to select an autonomous mode, and the field has to be reset in order to get another robot to connect, you can lose your dashboard selection of autonomous mode. This happened to us at least once this year where when the reset happened we lost the selection and the drive team was unable to get the attention of the field crew to wait.
There are a number of different ways the the FMS to robot interaction can cause problems. (This is not a complaint about the FMS, so please let's not start that discussion in this thread.) Any sort of complicated communication system like that is going to have problems from time to time. I think that punishing a robot for not moving by making it not move for an even longer time is not the way to go. That would make one of the most frustrating situations in FRC, a robot that is unable to move, far more common. It would also disproportionately disadvantage inexperienced teams. Adding incentives to make it worthwhile to move is great. And avoiding game rules, such as we had in 2015, which encourage some teams to tell others not to move as a standard plan is also a good idea. But please let's try to not to increase the number of times robots can't move.
|