LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

keep vi in memory after stopping on RT target

I built an executable with one startup vi and deployed it on the RT target. The vi doesn't run on startup. I can run the vi once remotely from the host computer but after the vi stops, it is unloaded from the memory so I can't start it again. I have to restart the RT target. Is there any way to keep the vi in memory as long as the system is running?

 

0 Kudos
Message 1 of 7
(3,433 Views)

HI,

 

Did you want the VI to run at startup? What target are you running this on? An when you say you run the VI once remotely, are you using remote front panels or just controlling it from the project?

Regards,
Claire Reid
National Instruments
0 Kudos
Message 2 of 7
(3,406 Views)

No, I don't want to run the vi at startup. I am using a RT Desktop running Labview RT. I am running the vi using Invoke Node from the host machine (after opening up a reference to the vi server application).

 

0 Kudos
Message 3 of 7
(3,393 Views)

Build your VI so that it doesn't stop (easiest is placing all the code in a while loop).

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 4 of 7
(3,390 Views)
In that case, I'll be wasting CPU cycles when I am not doing anything. Isn't there a better way? I thought it wouldn't be too much troubling keeping a vi in the memory without using loops.
0 Kudos
Message 5 of 7
(3,378 Views)
BUMP
0 Kudos
Message 6 of 7
(3,361 Views)

I have been work LV RT apps since LV 6.1 and to the best of my knowledge, Ton's suggestion is the only viable option.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 7 of 7
(3,359 Views)