[URGENT]Unable to connect to crio

[Greg McKaskle]

The Diagnostics robot light shows the results of ping. So it agrees with your command line ping in verifying that the cRIO is up and running its TCP stack and has the ip address set correctly.

The Communications light indicates whether the FRC_Communications library is loaded and running. The ni-rt.ini file lists it in the libraries to load, and either it is crashing on load, or the file no longer exists or has been modified. A null-modem serial cable to a terminal program will help determine what is happening during load.

As for the Robot Code light, it indicates that your robot's code is sending back voltage values. It can't do that if there is no Communication task running.

I'm confused by the VM comment. It sounds as though you have tried to install your own Java VM on the robot? As much difficulty as Sun/Oracle had getting Squawk to run on VxWorks, I'd say that sounds ambitious. Do you have more details?

Greg McKaskle

[jmiller18]

Sorry, by other vm I meant the OTA server, I thought I saw vm but I guess I was wrong.

Can you elaborate on the "null-modem serial to a terminal program"??

[Greg McKaskle]

http://en.wikipedia.org/wiki/Null_modem

You will also need to use the imaging tool to enable the serial console. No need to image, just flip the setting and apply.

You can use any terminal program that supports serial communications. PuTTy is nice, but Hyperterminal can do in a pinch.

Greg McKaskle