cRIO Does Not Communicate, Yet Can Be Pinged and Re-Imaged

[1951-44U]

Once, we had code working in C++ on the practice base, which could drive around and shift via pneumatics. Then the next day, we tried to download basic encoder initializing code that was based off the working code, and found that the cRIO did not accept the code (aka it showed "No Code" on the Driver Station). Then we shifted from our brick-like Dell laptops to my Thinkpad that I brought in with WindRiver to try out. It worked.

So we got the encoders to output basic values such as period, and closed shop for the day. The next day, when we came back in and re-connected everything to work some more on the encoders, the robot refused to communicate with the rest of the system. The driver station displayed "No Comm". Using my laptop, I could ping all the individual components of the system, the cRIO and the Driver's Station. We tried a direct connection between laptop and cRIO. That did work, but WindRiver would not connect with the "target server" (aka the cRIO). Pings, re-images, all still worked. Then we tried it wirelessly. Pings still worked (we didn't attempt to re-image via WiFi as we feared the time it would take). Driving and the driver station didn't. Then we tried restarting everything without the laptop in the system. That didn't work. Then we re-imaged the cRIO and tried all of the above again. It didn't work.

In addition, the digital input module on the cRIO had LED's that would cascade when everything was in order. It is not cascading now. Also, the signal light does not light up at all (I thought it was an indication that something on the robot, namely the cRIO, had gone awry -- a re-imaging blew that theory). All connections are tight, the batteries are of ample power and voltage.

There were several posts on NI about the "No Code" issue (http://decibel.ni.com/content/thread/2321), which I believe may have been an error in differences of individual updates on our old laptops. However, we did nothing to the robot between closing shop on the day we got it to work and booting it up again the next day, and it now refuses to communicate.


Any ideas on how this may have happened? Thanks in advance for any contributions.