Code not deploying

[cjl2625]

At the Suffield Shakedown today, we were unable to deploy code to the robot from LabView. When I try to deploy code, I just get a message that says 'waiting for cRIO to respond.' I know the robot is connected; we could drive it with the code that we loaded onto it the night before and it could function during the competition. I don't know why LabView can't connect to the robot correctly; everything else works, but deploying code just doesn't work.

[Garten Haeska]

are you trying to deploy your code with the dashboard open, i know we could deploy with it open for the longest of time.

[josneville]

If you have permanent code on the robot, it won't allow you to put temporary code unless you format the CRIO. That might be it.

[Garten Haeska]

Originally Posted by josneville

If you have permanent code on the robot, it won't allow you to put temporary code unless you format the CRIO. That might be it.

We can still deploy code onto our robot while we have our start up code deployed onto the crio. So I think you are wrong about this one.

[josneville]

Then I guess our robot has something wrong then.

[Greg McKaskle]

The LabVIEW code that shipped at the start of the season handled SmartDashboard connections in a way that the cRIO couldn't abort. This meant that with permanently deployed code and a SmartDashboard client connected, a new connection or deployment would fail to complete.

This was corrected in update 5.1 and there should be no need to reformat the controller for this.

Other things to check are the IP of the computer and even the CPU usage of the cRIO during the deploy.

Greg McKaskle

[Jimmyk]

We are also getting repeated failures to deploy, again. We tried reinstalling the 5.1 Update, but it said the update was already installed.

While trying to deploy we get the dreaded "Cannot connect to real time target" etc. We often see this once, but sometimes it shows up a second time, then we know we're dead.

On at least one occasion closing the Driver's Station helped, but other times it hasn't. This is not the best time of the year for this to happen.

Any help would be much appreciated.

[BenGrapevine]

I just have it drilled into my head to not deploy code unless the driver station is closed. That was what caused connection problems for the first week of our season.

[kenavt]

We are also having this problem with the 5.1 update installed and code permanently deployed. We tried temporarily deploying the robot code without the Dashboard or Driver Station running, without success. Flipping the "No App" switch via the cRIO Imaging Utility and letting the cRIO reboot resulted in temporary deployment success.