NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Starting to hate that when you switch to runtime the sequence will not work

I am Starting to hate that when you switch to runtime the sequence will not work.  NI should do something about it, yes testand tell you he cannot run the vi but at the same time you cannot troubleshoot it lol because is running on runtime..

 

 

 

CLAD, CTD
0 Kudos
Message 1 of 3
(3,098 Views)

I'm sorry you are frustrated.  I'm having a hard time understanding what is frustrating by your post though?  If you have a suggestion or idea then you can post it on the idea exchange forum:

http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/idb-p/teststandideas

 

This is why the deployment utility is vital to a clean TestStand deployment. Because it is smart enough to relink all your VIs and recompile them so they will run with the runtime engine.

 

Are you using VIs from different versions of LabVIEW?

jigg
CTA, CLA
testeract.com
~Will work for kudos and/or BBQ~
0 Kudos
Message 2 of 3
(3,097 Views)

Everything is the same version...

 

but i have a hardware abstraction layer and every program i make makes call to that framework...  

 

the deployment feature is a nightmare, because if you try to deploy every sequence it will repack my framework everytime.

 

 

 

CLAD, CTD
0 Kudos
Message 3 of 3
(3,087 Views)