IF NEEDING HELP POST HERE!

[DavidGitz]

Originally Posted by J-Mech

Yes we have the IP set up for the cRIO and it is connected to the developer computer with the Ethernet cable. I connected the system to the classmate and it was a communications error(Fast Blink). I have verified that all of the IP addresses are set to what the manual gave for configuring the cRIO.

If I understand what you're doing correctly, that won't work. The cRIO port 1 is the only port that can be used for communication, port 2 is for sensors/other devices. So from what I understand you have setup, you have the development computer connected to the cRIO port 1 (using an ethernet cable, which is wrong, should be a crossover). You also have the classmate connected wirelessly to the Bridge, and the Bridge ethernet cable is connected somewhere it shouldn't be.

The first configuration I would try is connect your development computer with a crossover cable to the cRIO port 1, and using the IP settings I gave earlier. If you can ping it, that means that the cRIO is imaged, I believe. I would stick with the LabView image if you follow my troubleshooting advice, since I don't have working knowledge of WindRiver. Then you should connect to the cRIO using LabView with a default project and build/run as startup to get working code on the cRIO.

After all these steps are completed successfully, I would start with checking out the wireless configuration/communication with the Classmate.

If you are unsure of anything I've said here, refer to these documents:
http://www.usfirst.org/uploadedFiles/Robotics_Programs/FRC/Game_and_Season__Info/2011_Assets/Kit_of_Parts/How_to_Build_and_Load_Programming_in_LabVIEW,_C,_a nd_Java.pdf
http://www.usfirst.org/uploadedFiles...cRIO_Rev_A.pdf

I really wish they would have made the control system instructions in one document this year, so teams knew how to progress through the documents instead of a collection of separate documents. If they would have been consolidated (like last year) I believe that your team would probably not be having this problem.