[DavidGitz]

Also posted this on the NI FIRST Community, thought I would give CD a shot too before submitting a ticket to NI.

Ok so here is our problem. We are trying to get our 2010 Robot to play with our nice programming team kids. It was driving fine through the off-season and would pretty much always work when booted up. At our team meeting yesterday we hit a snag trying to download new code onto the cRIO (we hadn't needed to program it since Nationals). After connecting a (unproperly) updated laptop to the router and trying to deploy code onto the cRIO, we got the cRIO Timeout Error. After a couple reboots we still had this issue although we could ping the cRIO from the laptop. So the next step was imaging the cRIO. We had some issues with our laptop (obviously it wasn't updated correctly, even though the firmware listed in the imaging tool is v20, the current version) and the wireless would turn on and connect to the school's internet whenever the LAN connection dropped. So last night I updated the laptop to the most current version of everything (Labview update and DS update) and turned off all the wireless stuff. Came in today and started the firmware update again. Had some issues with it still (yay for Vista) but pushed through and was able to update the firmware successfully. On reboot the Dashboard Laptop shows Communications, No Robot Code and no Voltage (all expected I believe). We can ping the cRIO. There are no crossover's, and we still get the timeout issue. We can ping wired and wirelessly. I can't Connect to the cRIO Target through the Project Explorer, can't Run at Startup and can't deploy Code, all with the FRC cRIO default Code. I didn't try the User App switch but don't think it will matter. Thoughts?