[kenavt]

Recently, I have been getting problems when deploying LabVIEW code to our practice robot (not permanently deployed, but temporarily, as long as the cRIO is on. I believe this is because the program is saved into RAM memory, but that is not the point of this post).

Specifically, when I attempt to deploy a robot project (from the Robot Main.vi), there springs up a Conflict Resolution window, where a bunch of VIs are unable to be resolved from current dialog, identified as part of a Real-Time Startup Application, and the VIs on the target will have to be closed to proceed. I click OK, and then I move on. Deployment begins and the VIs are pushed to the cRIO. However, they are pushed extraordinarily slow - about one VI every couple of seconds. Meanwhile, I lose comms according to LabVIEW (although the DS shows I still have comms), every once in a while. If I follow through with the whole deployment, I usually get about 85% of the way through, then lose comms permanently. Sometimes, it is before that.

To fix this issue, I have attempted to deploy with the "NO APP" dip switch turned to whatever is not the default position. This did not resolve the issue. Then, a couple of days later, I turned off my firewall, and attempted to deploy. When this failed in the same way as above, I attempted it in conjunction with the "NO APP" dip switch. Still, 'no dice'.

I know my code is fine, as another programmer on my team has deployed the exact same robot project to the same cRIO as it normally should happen, with the exact same ethernet cord (which has been used throughout this experience). This problem recently developed, as I have deployed other code to the cRIO previously (about a month ago). I also have all of the updates installed (LabVIEW, Utilities, and Driver Station).

Frankly, I'm at a loss. I have searched on CD for previous problems, attempted to apply those fixes, and failed. I plan to go to the LabVIEW booth at St. Louis, but until then, do you guys have any clue what's going on?