|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
"cRIO Unavailable" in FRC driver station
Hello everyone,
We are setting up a "new" driver station so that we can operate two robots at separate events at the same time. The original drive station communicating fine. However, with the "new" driver station we are getting the error "cRIO Unavailable" and the software does not update the robot IP address on the dashboard. We have run through everything that we can think of: * Both stations have the same IP address and mask * The "new" station sees the cRIO fine using the reimage tool * Both stations can ping the cRIO with the IP address that the reimage tool reports * Team number is set correctly (and the same) * Both stations have the "Choose NIC" settings the same - "I will configure my XYZ network manually" * Firewall on the "new" station is turned off. Firewall is turned on with the working station * The lights on the "diagnostic" tab are the same between the two stations (except for the "communications" and "Robot code" lights on the far left). * The messages in the "diagnostics" tab look the same between the two stations. * Both are connected by cable (tethered) * Both are running the latest drive station software "DS 02.12.13.00" One significant difference is that the working station is running Windows 7 and the "new" station is XP (thus the quotes). However, XP "should" work, right? The "new" station is a much older laptop, but, again, that shouldn't make a difference. So, we're stumped. Does anyone have any suggestion of what might be going on? Many thanks, --mark |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|