Ok, thanks! Worlds is super unfortunate… I heard you saw some of the matches where at times our teammates got stuck the entirety of the match, some teammates even scored in the opposite goals. We also had to connect our controller to our brain during the start of each match manually becuase of some VEXNet Error. After auton, our controller would just not connect. All four head refs and field techs could not figure out the problem. This caused our robot to not move for 2 matches!
Off topic, but could you elaborate on this. Where was the error ? do you mean you had to tether the controller to the brain each time ?
5 Likes
Jack, I told you guys last season to have me come down for best Cajun and Creole seafood in Mobile 
Will make sure to make plans earlier for next season!
Event listed as Smart Field Controller - so legacy VEXnet control should not be issue … TM logs might provide clarity… even looking at V5 Robot Brain Event log should give some additional information.
Yeah, so we think it may have been the problem of our radio being too low on our robot… We had to manually tether a port from the brain to the controller to connect before each match. This was weird because there has never been a connection problem when testing or even at regionals. The field techs at States promised it was not a field problem, we are still clueless.
1 Like
The best things here to help debug is picture of robot and specifically where your radio is located. That said, does not matter - if you are able to connect to robot and then robot does not respond under match control - then it is likely a coding error.
You are likely to have this problem at US open. So maybe your coach and I can figure out if we can debug… but I would also recommend that you show code here on forum… I suspect competition template not used correctly
1 Like
Tethering the controller to the brain allows an exchange of unique id numbers, each learns what the “unique code” for the other is. The codes are used when the radio connected to the brain and controller need to connect. If you had to do this each time either one end had forgotten the unique code for the other or perhaps the controller has been switched to bluetooth (tethering also allows the brain to set the controller to the correct radio selection).
4 Likes
Before each match, we changed the brain to VEXNet from Bluetooth. When we did that and tethered our controller to the brain, the robot ran fine. Is the ID the team number that we have to put on the code for the field to register?
Split this off into its own topic for relevant discussion
3 Likes
If the brain had been using bluetooth, and you switched it back to VEXnet, then either you also have to switch the controller to VEXnet or, by tethering the controller to the brain, allow the brain to change the controller automatically.
Why was the brains et to bluetooth ? A skills run ?
4 Likes
It was only once that we had to switch from Bluetooth because we did a skills match. The field tech told us to just make sure both the controller and brain were on VexNET before each match so that is why we had to switch them.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.