No Robot Code!!!

[mikets]

I don't know if you got NetConsole working (I never do), you can do a direct connection to the cRIO's serial port with a NULL modem cable to your PC using 9600,n,8,1 (make sure the console debug DIP switch is enabled accordingly). I found this extremely useful because then you will see all the boot messages from the cRIO. If there is any code loading problem, it will show on your terminal console. There was an excellent thread somewhere talking about different causes of "No Robot Code". I don't remember which forum. You may want to search for it. It contains a lot of useful information.
Good luck.

[masoug]

you can do a direct connection to the cRIO's serial port with a NULL modem cable to your PC using 9600,n,8,1 (make sure the console debug DIP switch is enabled accordingly).

I hope that I am not too weird on this, but could you explain this a little more? I am relatively a beginner. Thanks! -Masoug

[mikets]

On the cRIO, there is a 9-pin D connector. That's a serial port. Right around it, there are 8-bit DIP switches. The 2nd position is labeled "Console Out". Make sure console out is enabled. Here is more info about Console out:
http://digital.ni.com/public.nsf/all...25701B004A77CD

You need a COM port on your PC. Unfortunately, new laptops no longer have COM ports, you may need a desktop PC or you need to get a USB to Serial adapter such as this:
http://www.newegg.com/Product/Produc...-067-_-Product
You also need a Null modem cable (i.e. pin 2 and 3 on both ends are swapped). The one that came with the KOP is not a null modem cable. You may need to get a null modem cable such as this:
http://www.newegg.com/Product/Produc...-034-_-Product
You also need a terminal software. If you are running XP, you can use hyperterm that came with Windows. You need to set the communication protocol to 9600 baud, 8 data bit, no parity bit and 1 stop bit (i.e. 9600, n, 8, 1). Once you have this set up, you should see messages spitting out from the cRIO while it boots. If your code failed to load, there will be an error message telling you why.

[masoug]

Finally, we figured out what the problem was. The WindRiver working directory was just on the desktop, so when WindRiver regenerated the makefiles, all the paths (library paths) didn't correspond correctly, resulting in an undefined symbol error.

Thanks guys for helping me pinpoint the problem, so now we know what to look for when this happens.

-Masoug