Deployment Communications Fail

[Greg McKaskle]

When it doesn't resume, you might try a simple cRIO reset, then try again. I'm looking for a process that works that doesn't involve a 20 min formatting for a bunch of flash. It is very unlikely that there is anything wrong with the image that it needs to be flashed.

Greg McKaskle

[flameout]

I'll add that we are having the same problem.

When we deploy, it always fails at that same point. This started occuring a day or two after we updated LabVIEW (i.e. today/yesterday (it's 12:58am.))

I'm waiting right now for it to continue, but it doesn't look like it will.

Thank you for any help.

[jonboy]

Sounds like we are having the same problem. Don't remember exactly but it gets to the project line and posts the waiting message loss connect with the CRIO. Ping works great. If I try to deploy again it says access denied. After about 30 minutes of screwing around with restarting the CRIO and the DS it eventually deploys successfully and then subsequent deploys work well if nothing is shutoff. Haven't found the magic recipe to reliability get it to work. I hope there is a fix to this communication bug soon!

[Rideout]

We had the same problem today on two different cRIOs. A post on NI comunities susggested to try setting the no app on startup dip switch to halt an active program. Will try tomorrow an post results

Team 34 Rockets

[jonboy]

We followed the advice from nathand in the NI.COM FIRST discussions. http://decibel.ni.com/content/thread/6231?tstart=0 We set the CRIO dip switch to "No APP". We were then able to deploy our code from our Laptop wirelessly on the first attempt. It's working great! TNX agn to nathand.