Operator Console

[Jogo]

Cool, thanks everyone. Out of curiosity, why does it have to be in disabled, rather than autonomous independent? Also, what is the Enhanced IO vi?

[Matt Krass]

Originally Posted by Jogo

Cool, thanks everyone. Out of curiosity, why does it have to be in disabled, rather than autonomous independent? Also, what is the Enhanced IO vi?

Don't quote me on this, but I believe in disabled mode, the robot still receives live data from the driver station, but can't act on it, and when it transitions in to autonomous, the data from the driver station is 'latched' which means the last values sent when the transition occurred will be re-sent over and over regardless of any changes you make. Theoretically you could set the switches in disabled mode, and have the robot read them in autonomous, as long as they were in the correct position at the transition point. I haven't tested this yet, it was explained that way to me by another mentor, so take it with $0.02 of salt.

Matt

[Greg McKaskle]

Don't quote me on this, but I believe in disabled mode, the robot still receives live data from the driver station, but can't act on it, and when it transitions in to autonomous, the data from the driver station is 'latched' which means the last values sent when the transition occurred will be re-sent over and over regardless of any changes you make.

But since it is accurate, I'll quote it anyway. The only thing I'll add is that this is true of joystick settings and DS I/O. Anything on the DS that could be used to influence or drive the robot during auto is latched. If you don't need to have your hands on it to keep the value, you can manually set the value during disabled and the robot can read it during auto.

The DS compatible I/O can be virtual -- set on the screen -- or via the Cypress board. The enhanced I/O is far more flexible, but is not virtual. You must use the board with enhanced I/O.

Greg McKaskle