It displays a selection of critical information about the state of the DS and robot: Team - The Team number the DS is currently configured for.
#FRC DRIVER STATION APP NOT SELECTING OP MODE CODE#
A safer way to do this would be to run the code on a separate processor like a Raspberry Pi with a simple switch to turn it off and on. The Status Pane of the Driver Station is located on the left side of the display and is always visible regardless of the tab selected.
If you implement this, the only way to stop motors from turning is by physically unplugging their signals or power. In case it wasn’t clear, I want to reiterate that this should ONLY be used for things like benchtop testing setups when there are no moving parts/pinch points. There are many other, more subtle ways teams can break the rules to gain a minor advantage, and they choose not to do so not only because it’s against the rules but it’s also at odds with FRC culture (gracious professionalism). Cheating of this sort has not been a problem to date, and I would hope we have not changed so much culturally that teams would be tempted to break safety protocols to cheat so obviously and egregiously in a high school competition with no prize money at stake. As Carlos mentioned, the ability to do this has existed since the inception of the cRio system in 2009, both at the DS side and the robot side. The primary mechanism for preventing doing something like that is that it’s against the rules, and operating outside the time limits of the match is pretty visually obvious and will get a lot of attention paid to the team/robot very quickly.
Other than “against the rules”, what mechanism is there from preventing a team from starting the robot a second or two before the others, or keeping it going for a bit after the match?
0 kommentar(er)
