Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with Shared Variables between LabVIEW and VBAI

I have just started to learn LabVIEW and VBAI about a month ago so my knowledge isn’t the best.

 

Currently I am having an issue with shared variables on my deployment PC which has Windows 7, VBAI 2015 and all the required LabVIEW 2017 installers including NI Variable Engine. I am able to run other executables that do not have shared variables on the PC no problem. The current vi I am creating works fine when I am on the development PC. I am able to read and write all my shared variables to and from VBAI. Once I create the executable and try it out on the deployment PC none of the variables are being shared. I made sure the directories were consistent, the correct installers were selected, all the variables were in the .lvlib, and the executable was allowed past the Firewall. When looking at the VBAI file on the deployment PC I noticed the shared variables were not set to what I had before in the “Set Variable” step. Under the operation column it says “Set to Measurement not available”. I have looked around to find similar issues but most mention the Firewall or NI Variable Engine being the cause. 

 

The problem is probably something as simple as a click but I would appreciate any advice that can help find the solution or catch something that I might have overlooked. Thanks!

0 Kudos
Message 1 of 3
(2,371 Views)

Could you reproduce the issues with a simple VBAI inspection and attach both the VBAI inspection and the VI and LabVIEW project you use to create the executable?

0 Kudos
Message 2 of 3
(2,314 Views)

Christophe C,

 

I was able to get come up with the solution with the help of others. Here is the link to the other discussion. Shared Variables not deploying in executable

 

Thanks!

0 Kudos
Message 3 of 3
(2,307 Views)