LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can't download to FP2010

I can't download a vi to my FP2010. I get "Failed to download my.vi" It has been running for weeks with a different embedded vi. The only thing that has happened to it is the power on the machine has been cycled possibly once/day.
0 Kudos
Message 1 of 6
(3,443 Views)
"Failed to download" can mean several things, but a couple of things you can quickly check:

Does the new VI you are attempting to download contain a Call Library Node that might not be getting resolved when the target tries to load it?(for example, could the new VI be trying to use a driver that's not installed on the FP2010?)

Is there enough memory left on your target to download the VI completely? (check your target's memory by using Operate>>RT Engine Info to make sure there is roughly 2x the size of the VI still free).
Message 2 of 6
(3,443 Views)
Jack is correct. The error can mean a variety of things. If another VI is able to download and run then I would intially look at the size of the new VI. If there is not enough memory available the VI will fail to download. There is not a perfect method to determine how large file will be when downloaded. If you attach your VI I may be able to do more analysis on it.
0 Kudos
Message 3 of 6
(3,443 Views)
Sorry for long reply been on other projects! I made small vi approx. 16kb to read di330 input channel. It download & ran fine. The file that "fails to download" is approx. 124kb. The RT memory says Total 32,379kb and free 22,240kb. It appears their is lots of mem. left. I wonder what "hdmon.bin" (176306bytes) and ph_exec.exe (636800 bytes) are for??
0 Kudos
Message 4 of 6
(3,443 Views)
You might try doing an Edit>>Find for Call Library Function Nodes (under Functions/Advanced) over the complete hierarchy to see if it is using some DLL that may be failing to load on the target. If you aren't using any DLLs, it might be that the wrong version of a driver is on the target (older version missing a particular function, etc). If you're not certain, it would be good to check if the target has the latest version of the drivers you are using.

Sounds like you are fine on memory--but be sure you are calculating the complete size of the VI including it's sub-VIs. If you ran your VI throught the RT Communication Wizard, for example, it can get pretty big.

btw, which version of LabVIEW RT are you using?

hdmon.bin and ph_exec.exe ar
e part of the Real-Time OS.
0 Kudos
Message 5 of 6
(3,443 Views)
If you can attach your code I can look through and help debug the issue. Also, please let me know what versions of the software you are using (LV ,LV RT, and FP).

Joseph D.
National Instruments
0 Kudos
Message 6 of 6
(3,443 Views)