Waiting to connect to OTA command server

[drakesword]

How are you deploying code as in how is your laptop hooked to the robot?

The 1/10 mentioned above was that a programmer tried to deploy code via the router over a long distance via wireless to the router.

[vinnie]

I was previously (before v27) able to download code wirelessly, now it doesn't even work downloading over the robot bridge or even hardwired to the cRio.

[michael714]

If I recall correctly, this could even be a Classmate issue. Reboot the driver station if you haven't already. Also, triple check all IP addresses and all subnet masks. Are you able to ping from developer PC to Classmate, bridge, robot?

When you image, make sure you're using the correct team number. Double check the team number on the Classmate too.

Reboot, reboot, reboot.

[drakesword]

With the checking of the IP make sure you hit the advanced button. Sometimes you will have a listing of multiple IP addresses to use if one is not available.

[eddie12390]

Try sticking something into the Reset place on the cRIO while downloading code.

[derekwhite]

Hey Vinnie,

The output looks a bit curious. It doesn't look like the 2011.6 release at all, but it didn't warn about a cRIO image mismatch either.

Double-check that the netbeans plugin version is 2011.6, and if needed, update them from the WPI update center or download and install from http://firstforge.wpi.edu/sf/projects/wpilib

[12mrsaturns]

This morning I had the same problem, but it started working after I reformatted the cRIO. Don't know why, probably some serious voodoo.

[dcarr]

We eventually got this working after making sure the CRIO was running version 28 and fully deleting all FRC plugins from netbeans, including the sunspotfrcsdk folder, and then reinstalling the newest plugins.

We did have to manually edit the update.xml file because it was looking for version 27 and we had 28. But after that it worked.

CRIO can be darn frustrating at times =P

The weird thing is that we thought we had fully updated plugins/latest firmware the whole time yet it required a particular sequence of events to make everything work correctly.