Problems with Driver Station communication on test bench setup

[ajlee]

Our team has constructed the electronic test bench setup according to the 2012 FRC Control System guidelines. On our development pc (not the classmate), we can run a default FRC Robot Project to the cRIO successfully, however, when the driver station is started, there is no communication with the cRIO. How can the pc communicate with the cRIO to download the program, but not recognize the cRIO through the driver station?? Notes: The crossover cable is being used to tether the pc to the cRIO, and the labview, utilities, and driver station updates have been installed. As a further note, when the classmate is tethered to the cRIO instead, the driver station on the classmate DOES establish communication, but no robot code is present.

Thanks for your assistance.

[Kevin_F]

Hey ajlee,

The driver station does have some of its own network configuration that needs to be set up.  On the setup page you will need to set your team number and choose which NIC (if you have multiple) to use to communicate. Can you confirm you have completed that setup on the driver station?

[ajlee]

Thanks Kevin_F for your response. We have entered our team number and the NIC is set to Ethernet adapter Local Area Connection for the wired adapter. The other choice is configuring the connection manually. The Local Dashboard switch is set also, rather than the Remote Dashboard, if this matters any.

[Kevin_F]

Hey ajlee,

The diagnostics page of the driver station will sometimes provide useful information on connection issues. What is the status of the LEDS next to ENET Link, DS Radio, Bridge and Robot?

[ajlee]

The ENET Link and Robot LEDs are constantly lit, while the DS Radio and Bridge LEDs turn on briefly on occasion. The DS is 11.30.11.00, and the cRIO is "unavailable".

[Kevin_F]

I would try going straight through ethernet cable from the development computer to the bridge and bridge straight through to the RIO. Does this setup change any of these status lights?

[sciencewhiz · Accepted solution]

Do you have a firewall on the development computer that is blocking communication from the driver station software?

[ajlee]

sciencewhiz -- Absolutely correct! Changing the Windows Firewall settings for FRC Driver Station did the trick. Thank you all for your assistance!