The connection LEDs for the wireless are lit up but the drivers station says no comunication with the robot. However if we turn the DS on and the robot is on the DS reads 0.0 volts until we turn the robot off when it once again reads “No Comms” Windriver also says its downloading fine and we can see both the router and the robot receiver on the computer.
Can you ping the Driver Station and verify that it has the correct IP address corresponding to your team number?
What you’re describing here is the correct behavior. The “No Comms” message means the driver station is not receiving reply packets from the cRIO. If the cRIO is turned off then the DS is expected to display “No Comms”.
There are four general messages you could expect your DS to display:
“No Comms” means it isn’t receiving reply packets from the cRIO
“No Code” means it is receiving reply packets, but the software isn’t updating the battery voltage
“0.0 V” probably means you don’t have power going to the first 9201 module
“X.Y V” where X.Y is the correct battery voltage means everything is working properly
You could have a number of issues…
-
Did you configure your wireless router and wireless gaming adapter to communicate with one another by inserting the CD that came with the router into a computer?
-
Is the Ethernet cable that is running from the router to the DS plugged in the proper locations?
Just because the DS reads the battery voltage as 0.0v, it does not mean that the two are not communicating with one another. In order for the battery voltage indicator to display properly on the DS, port #7 on the analog breakout must be configured properly.
Please try to limit technical issues/discussions to the FIRST Control System Forum.
I can’t double check, but if it says 0.0V then I believe your robot comms are fine and that simply means you haven’t hooked up the voltage reader. Can you get the DS to input and then have the cRIO output something?