|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Operator Console
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! |
|
#2
|
|||||
|
|||||
|
Re: Operator Console
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.
|
|
#3
|
|||
|
|||
|
Re: Operator Console
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.
|
|
#4
|
|||
|
|||
|
Re: Operator Console
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.
|
|
#5
|
||||
|
||||
|
Re: Operator Console
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.
|
|
#6
|
||||
|
||||
|
Re: Operator Console
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. |
|
#7
|
|||
|
|||
|
Re: Operator Console
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?
|
|
#8
|
||||
|
||||
|
Re: Operator Console
Quote:
Matt |
|
#9
|
|||
|
|||
|
Re: Operator Console
Quote:
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 |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|