[Mr. E]

Shoot. I was hoping it would solve my problems...

We have not been removing files through FTP or manually editing the ni-rt.ini config file on the cRIO. We might have inadvertently done so (we upgraded to the LabView3.0 and deployed some code) but I don't think so.

Reimaging the cRio: The robot was fine in tank drive mode. After updating, the robot became "disabled" (Fast slow blink). Actually, it stays solid for about 10 seconds and then starts its Fast-Slow Blink. Fast-Slow Blink (200ms on / 900ms off) - System disabled either by system watchdog, user watchdog, or Driver's Station set to disabled and low battery (<12 Volts)
Any how, I digress. We reimaged the cRio following 5.1.2, except we did notice that this time (vs the first time we reimaged) there was a "always run deployed code at start up" box that was not there the first time. We checked it and allowed it to reimage.

We do not toggle between C++ and Labview. We only use Labview


To deploy code, we have oscillated from "deploy" and "run as startup"