I have no idea what lead to this because it was functioning before easter, however it seems our cRIO is not starting its code anymore. I can connect to it with Labveiw and deploy code, the imaging program and reprogram and change setting, however each time the light does not flash, and robot does not function. Ive disabled the firewall on our laptop, reset and reconfigured the router and deployed the vanilla version of the code and still nothing. I can also access the web ui and net console. The status light on the cRIO flashes four times no matter what, which i read means the software has crashed, which makes no sense to me.
Do you get the four status light flashes when you boot in Safe Mode or after you’ve reimaged the cRIO using the Imaging Tool?
From your description you seem to be saying that the cRIO takes an image fine, and you can download new code to it without trouble, but as soon as you reboot it with new code it crashes?
Have you watched a netconsole output while the cRIO boots and crashes?
You can also tether up directly to the cRIO serial port for a console dump to get crash information if you have a serial port and a cable.
In the net console it says that Network communication failed to initialize after it started the code and before its says welcome to LabVIEW RealTime.
EDIT: To answer your first question and add what i should have added to the last sentence of my first post, it did it after reformatting, after deploying code, or anything. I played around with it again, mostly with networking stuff because of the error above, and after changing the net mask in the cRIO’s web ui it came back to life. I wasn’t sure that this would fix it and sure enough, after a night of sitting there it went back to refusing to work probably. Except this time the status light doesn’t blink four times in a row, but it still gives the failed Network Initialization.
This error started Monday, (At a Career fair for middle schoolers, a most unfortunate time!), and after trouble shooting it for a while, I reset the bridge and it started working again. It refused to work again after we changed the battery.
I just noticed the error in the start up log, I would post it but i cant figure out how to copy it.
But this is the error:
Invariant FPGA image version error (status=-61018)
A quick Google and this came:
So is it necessary to contact NI?