This Q&A is now read-only
Official Q&A: VEX V5 Robotics Competition 2025-2026: Push Back
2692: T8 & G11 - Legacy Field Control
Hello!
If a team plugs their robot into the field and produces a Legacy Field Control error (so the robot isn't affected by field control and can freely drive around in autonomous / driver control) what should happen?
Neither T8 or G11 explicitly provide guidance on this scenario, the violation note for G11 implies the intent of the rule is to ensure robots abide by commands sent by the TM software (which does not happen when teams have a legacy field control error).
When teams receive this error would it be correct to assume they should be removed from the field / disconnected from field control and taken off the field (and not marked as a no show)? By extension, would this be a failure of robot inspection (R28) if a pin in the controller is broken causing this error?
Generally, what guidance would you give to referees and teams in situations like this?
Thanks!
Rule <GG3> would apply in this scenario. If the "Legacy Field Control Detected" error message cannot be resolved prior to the Match, the affected Robot should be removed from the Field per <GG3c> before the Match begins. The Robot may remain at the Field so that the Team isn't assessed a 'no-show.'
A Team with this issue either has a damaged controller or the field control cable is simply plugged into the wrong controller port—smart cables connect to either the left or right Smart Ports, not the middle Competition Port. The Team should first ensure their controller is properly connected to the Field. If the controller is properly connected and the field control monitor is still displaying the error message, the controller is likely damaged and the Team should swap to a different controller.