cRIO Drops connection after deploy

[DominickC]

I'm developing the project that is currently being used on the cRIO with the same computer that is connecting to said cRIO.

The cRIO has had code deployed and set as startup, however in the context of this issue, I am running RobotMain.

I remember looking at the cRIO LED's today when it was dropping comms, but I completely forgot what they were flashing. I believe the User1 LED was doing something funky. I can verify tomorrow.

When I run RobotMain initially (run button), the code will deploy properly and function as expected. However, when stopped to edit small details and then redeployed (run button), we encounter an issue. The code will deploy properly, and the grid on the front panel of RobotMain will disappear as if it were running properly. When I then switch to the Driver Station, the Robot Code light remains red, and the Communications light turns from green to red. RobotMain will then echo an error, "Communication with realtime target lost".

EDIT: The cRIO has code built and deployed as startup on it, if that has any bearing in the matter.

[Greg McKaskle]

I would suggest connecting up a serial cable or running netconsole to see what is going to the console. That sounds like your cRIO may be crashing either during deploy or shortly after.

Greg McKaskle

[DominickC]

Originally Posted by Greg McKaskle

I would suggest connecting up a serial cable or running netconsole to see what is going to the console. That sounds like your cRIO may be crashing either during deploy or shortly after.

Greg McKaskle

And what would I be looking for?

Alan -

I've tried both using the large "FINISH" button on the front panel of RobotMain, as well as the stop icon next to the run icon in the LabVIEW toolbar above the VI.

When I say "switch to the Driver Station", I am referring to the application. I switch from RobotMain to the 2013 Driver Station.

I have not tried waiting before switching, but I will try tomorrow.

[Greg McKaskle]

If you look at the console during boot, it is similar to what you'll see on a linux console or a DOS console. The stream of text will tell you that is is booting, some components and some version numbers, and at some point will stop changing.

Then if you have an error at the driver or OS level, it will print out details about the error -- very useful.

If it crashes, it will often tell you the library name, maybe an address or reason for the crash -- also very useful.

Sometimes it crashes and doesn't tell you anything, but you see the boot sequence and know for certain that it crashed.

Greg McKaskle

[DominickC]

I assume I have to reformat the cRIO to enable the NetConsole?

[Mark McLeod]

If you didn't make that selection when you first imaged the cRIO, then yes you have to go back and click the box so the netconsole part of the image gets downloaded to the cRIO.

[Alan Anderson]

Enabling NetConsole doesn't require reformatting the cRIO. You just have to run the Imaging Tool and apply the appropriate selection.

[DominickC]

Ah, gotcha. I'll have to do this Tuesday/Wednesday...we were just given the chassis to populate with various electronic components and wires.

Dom

[Alan Anderson]

Originally Posted by DominickC

I'm developing the project that is currently being used on the cRIO with the same computer that is connecting to said cRIO.

It doesn't seem reasonable to do otherwise (i.e. to do development on a computer but not connect that computer to the cRIO), so it's likely that I don't understand what you mean.

When I run RobotMain initially (run button), the code will deploy properly and function as expected. However, when stopped to edit small details and then redeployed (run button), we encounter an issue. The code will deploy properly, and the grid on the front panel of RobotMain will disappear as if it were running properly.

I'm going to accept your statement about "deploy properly" without asking you to describe exactly what is happening, but if we find out later that there's something going wrong that you think is normal you're going to feel very silly.

How are you stopping execution? Are you clicking the big "Finish" button, or are you using the "stop" icon in the Robot Main window's toolbar?

The "run" arrow should tell you whether it's running or not. If it turns from white to black with "motion" lines, it's running.

When I then switch to the Driver Station,

What does "switch to the Driver Station" mean, exactly?

the Robot Code light remains red, and the Communications light turns from green to red. RobotMain will then echo an error, "Communication with realtime target lost".

Does the error occur only after switching to the Driver Station? If you wait before switching, does the error happen later?