LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

LabVIEW VI does not work as expected on LabVIEW Runtimes

Solved!
Go to solution

 

Hello,

 

I have been running this VI to output a video on our UUT. The first image is starting the asynchronous call, closing the VI (if previously opened) and then outputting a new image that is defined in a path we input in TestStand. The second image is of the VI which is being called in the first VI. This VI takes in the user inputted image path and outputs it to the UUT.

 

When using the development suite, the image outputs perfectly on our UUT. When we call the VI to changes images, it works smoothly. When using the run time, we have noticed that the VI will not change the image in which we input in TestStand.

 

We have tried a Mass Compile and that still did not work. I had an assumption that maybe the VI was not reading the image path, therefore outputting the image that is default (I just am not able to break point into the VI so I can't confirm this). I just do not know why it would work in the development suite and then stop when using LabVIEW runtime.

 

AV 1.PNGFirst VI

 


AV 2.PNGSecond VI, VI that is being called and outputs the image selected

 

Thanks,

Rickyfn2

0 Kudos
Message 1 of 4
(226 Views)
Highlighted
Solution
Accepted by topic author Rickyfn2
04-24-2019 04:26 PM

The issue is with the file path, and specifically the application directory constant.  See the related knowledge base article:

 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019NFfSAM&l=en-CA

NI Alliance Partner
Message 2 of 4
(211 Views)

I will try this out, since we have a new version of LabVIEW- I thought the application VI would work just fine.
Also, these VIs are in a project.

0 Kudos
Message 3 of 4
(200 Views)

CFER_STS,

 

I was able to fix the issue. That link was beneficial and I implemented the case structure for "Development Systems" and "Run Time". The issue wasn't due to the application directory though. I was able to use that, I just had to just strip the extra ".exe" in the Run Time and then input the correct path into teststand.

 

Thanks,

Rickyfn2

0 Kudos
Message 4 of 4
(172 Views)