To week 1 teams (or anyone with previous experience): has anyone successfully received data from switches connected to the operator console to select autonomous routines? I just want to ensure that the packets are sent and that we don’t run into trouble on practice day with this.
Thanks!
we have our autonomous selector switches on our robot. we read the switches at the beginning of autonomous and select a mode from there. If you don’t have success with switches on the operator console, you can always to this and put them on the robot.
Yeah we’ve typically done the robot switch because we thought it was the only way, but I noticed in the basic LabVIEW framework that they read data from the operator console in the autonomous independent VI. I want to see if teams have used this successfully.
Yes, we have successfully received data from our switches on the I/O Module and have used the switches to select auton routines. We just used the Enhanced IO vi in LabView to use the data.
Last year we did this. We just went into the I/O panel of the DS and and set them in there, rather than hook up the board.
We did it with the joystick throttles last year, and this year we’re putting on a few switches and potentiometers to choose the mode.
Just read the switches and stuff during disabled. It’s probably a good idea to display the information to the dashboard also.
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
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