When even the experts are confused...
 

I have the programming done and yet the cRIO is being frustrating.
Using WindRiver and the latest version of the cRIO imaging tool, I've been able to deploy my program to the cRIO. However, when I open the driver station, it swears there are no Communications and that the Robot Code is absent. Under diagnostics, it says that the 4 Joysticks, the Robot, and the Bridge are all present.
I have had an expert come in and try and help, but he gave up. I now turn to you.

Help me Chief Delhpi, you're my only hope.

Re: When even the experts are confused...
 

In WindRiver check out the target console (or turn on serial debugging and use a terminal app with a cable). It sounds like you may be having a linker error, in which case your program will be unloaded. For best results, start the target console the second that WindRiver connects to the robot in the device view. It's also possible your code is crashing the cRio and causing it to lose comms and unload your program. Try to see if the simple template code works.

We've also had your symptoms occur with a very low battery - the code gets loaded, a motor turns, and the voltage drops so low the cRio resets.

Re: When even the experts are confused...
 

Make sure your Driver Station has the right IP address. That would be 10.23.93.5 (or possibly 10.23.93.9 if you're connecting via wireless). The Classmate sets its address properly by default, but you can confuse it into being incorrect if you insist on configuring it manually.

Re: When even the experts are confused...
 

I'd also suggest turning on the netconsole in the cRio image, starting the netconsole app (as developer) on the drive station, and be logged in as developer as the cRio boots up. We've had several instances where our code had crashed or was generating a runtime error, and this was how we found out what was happening.

Good luck.

Re: When even the experts are confused...
 

Ping 10.23.93.1
if that fails, your robot radio/router/ap/whatever you wish to call it is not configured properly

If above works,
Ping 10.23.93.2
If that fails, you need to reimage your cRIO and ensure you set the team number properly on the first screen. Reimaging also assigns the proper IP to your CRIO.

Re: When even the experts are confused...
 

The Diagnostics tab on the Driver Station does the equivalent of pinging everything. Sev's original post said that the robot (cRIO) and bridge (D-Link) are responding.

Re: When even the experts are confused...
 

one the crio check the dongles and make sure EVERYTHING is off BUT counsel out if safe mode is one it will not accept any code also make sure on the back of the router it is set to AP mode for wireless

Re: When even the experts are confused...
 

If you are using windows 7 you can go to the networking pane and click "diagnose this connection". Sometimes it likes to turn on a firewall, which may have happened if you accidentally told it you were on a public network. It should find the driver station trying to access the robot over the network and allow you to pass it through.