Cannot deploy code

[rellimcire]

Kind of covered this, but thought I'd add a data point.

Our main code computer is a laptop running Windows Vista. We use LabVIEW. We also get sporadic disconnections and other network issues.

Particularly we get the stop waiting and disconnect panel while running or deploying. Usually it goes away after several minutes. Perhaps you need to wait longer.

Others have had good ideas, just thought I'd throw out a possibility.

[BrianFarrell]

We have been having this problem a lot lately as well. We tried the following:

- power cycle power
- reset cRIO
- restart LabView
- reboot the computer

On a hunch we checked for services. We restarted the services and power cycled the robot. This seems to be an effective work around for the problem. I am attaching a simple batch file you can run to restart the services.

NOTE: You will need to rename the batch file to remove the .txt extension.

I hope this works for you as well.

[Joe Ross]

Originally Posted by Noamr

We had the exact same problem (it would get stuck deploying the lvproj).
At first we could solve it by building and deploying the code (after that it ran fine).
At some point that also stopped working. Someone told us it might be because our flash code gets stuck doing some process. Anyway, we formatted, re-imaged the controller, ran super-simple code on it and now it's fine.
I think it might have gotten stuck because the enable vision was on and the camera wasn't connected. If I find out more about this I will post it here.

Hope this helps...Good luck!

This sounds like it could be the problem I reported here: http://www.chiefdelphi.com/forums/sh...ad.php?t=92533

[moc601]

After working successfully for a few weeks, I could not deploy code.
I re-imaged the CRIO and it would deploy once and then the robot code would never load in the dashboard.

Using wireshark to capture packets I could see that all the CRIO would do was to send an RST (reset) packet back to the driver station.

Looking at the netconsole CRIO app (Must be selected when re-imaging CRIO)
I saw a whole bunch of memory allocation errors about 10 seconds after CRIO reboot.

Startup Application: /c/ni-rt/startup/startup.rtexe
0xb75698 (Main Application Thread): memPartAlloc: block too big 108 bytes (0x8 aligned) in partition 0x32ddf8
0xb75698 (Main Application Thread): memPartAlloc: block too big 580 bytes (0x8 aligned) in partition 0x32ddf8
0xb75698 (Main Application Thread): memPartAlloc: block too big 108 bytes (0x8 aligned) in partition 0x32ddf8
0x80a7d8 (Exception Handler Thread): memPartAlloc: block too big 80 bytes (0x8 aligned) in partition 0x32ddf8
0x80a7d8 (Exception Handler Thread): memPartAlloc: block too big 80 bytes (0x8 aligned) in partition 0x32ddf8
0x80a7d8 (Exception Handler Thread): memPartAlloc: block too big 1024 bytes (0x8 aligned) in partition 0x32ddf8
0x80a7d8 (Exception Handler Thread): memPartAlloc: block too big 84 bytes (0x8 aligned) in partition 0x32ddf8


Turned out to be an FTP session that I started in the begin.vi was the issue.
It somehow used up the heap, still looking into it.