V5 Autonomous Disconnect

ok, one thing to understand.

We switch to a download channel to do a wireless download, the download channel has approximately 8 times the bandwidth of the normal pit or competition channel, however, only a limited number of robots can be using download channels at the same time (22). When the download finishes, if the communications port is closed or the USB cable disconnected from the controller, the V5 will automatically swatch back to a pit channel 10 seconds later. It sounds like that’s what you may be seeing.

VEXcode will usually keep the port open, we keep polling the V5 for debug output.
I think PROS probably closes the port.

Dang. That is probably what we are seeing because it is disconnecting about ten seconds in. Thanks a lot everyone. Hopefully it will work better tomorrow.

This is our fault for not documenting and explaining this enough. We had similar behavior with the cortex, but every development environment uses the download channel capability slightly differently and it’s more obvious that the V5 switches back as usually the screen will go red, switching from download to pit seems to take longer that the other way around.