VEX Worlds 2022 Control System Bug

All three of our organization’s teams experienced something similar at least once during qualification matches for the same reason I believe. For us, our program worked fine until the driver control period, then the robots would no longer run for the rest of the match. The explanation given to our teams from the field tech support was addressing what you said.

just curious… what kinda of robot performance issues are you referencing?

We helped multiple teams that had issues with their code, these were nothing to do with the new FC system. The V5 brain doesn’t actually know if the new or legacy field control hardware is in use.

I’ll write up some more details when I get back from worlds, but most of what I saw was along the lines of.

incorrect user of event registration, the event handler being called multiple times when a button was pushed.

mis-understanding of how motor setVelocity and spin commands can interact.

mis-understanding how local variables would work if, for example, driver control was called more than once.

No the brain screen went mostly black and froze. There were tiny parts of the screen that we coded to show and the battery was usually 75% or more. It seemed to remain one. Happened twice only while running a match. Is it possible the code just froze?

In addition it could have just been radio drop not being processed, but several times while testing in our pits the brain and remote seemed to show as connected but the robot did not respond to input.

A similar thing happened to our team. After running the autonomous, out robot would act as if it was connected. It would either stay ‘connected’ and not run during driver control, or run for about 30 seconds. After the 30 seconds, there was a red screen on the robot for a few seconds and then the controller would ‘connect’ again and show as connected, but the robot would not move. That costed us a few matches :frowning:. I’ve heard on various other places that this actually happened to a lot of other teams and that it even delayed the Arts Division Final for 30ish minutes and made the teams replay 4+ times. Will this new system be moving to the main stream for Spin Up, and if so will these issues be debugged? I am scared that this might happen again next year.

What’s your team number ? Do you remember which match had issues ? We can lookup the data and see if there’s any indication of radio drops etc.

Robot ? or controller ?

as far as I know there were two replays, but I was in the dome by then. One replay was for white screen, not sure on the other, I’ll ask the field techs,

perhaps send me the code (zip the project and send by DM) and I will take a look next week when I get back to California.

putting a loop that hangs in the initialize function

I know that the code worked perfectly fine before the new OS update. The issue also happened again when we took our robot for a last spin. I can still share the code though.

285Z had some oddities in Autonomous on the Opportunity field. Would be interesting to look at the data if available

We also had this issue in two of our matches. Our auton ran fine, but we could not move the robot once wet entered driver control. If it helps, I know that our partner controller came disconnected from the master during the disabled period before the driver period during one of the games (it was reconnected before the driver period). The field tech volunteer said it was likely a code issue but we could not figure out what we could be doing that would cause this. Any insights that you could provide to help us avoid this in the future would be appreciated @jpearman

The finals were replayed twice. Once for a white screen and once for a field element malfunction.

and I believe the white screen was traced to a bad battery cable/connector, as were most (perhaps all) others at worlds.