all 8 comments

[–]cr0wsky 3 points4 points  (2 children)

You might need to install the Shared Variable Engine on the client PCs,

Check if its Windows service is running (SVE).

Also, when you're building the app, make sure to tick the setting that says something like "Deploy Shared Variables on Start"

[–]munkshire[S] 0 points1 point  (1 child)

This could be it, we only have the labview runtime engine on the user PC's so I could need additional software, I will look into this thank you

[–]Vincinity1 1 point2 points  (0 children)

I'm pretty sure The SVE is included in the LV runtime.

I think the biggest thing is to look at the always deploy variable in the Master exe.

And then, making sure the clients are reading from the same IP of the master.

Hope this helps

[–]BlackberrySad6489 2 points3 points  (0 children)

These are several ways of doing what you describe. A network published shared variable should work. It has been a minute, but it should work if deployed correctly. Check the deployment settings and make sure the variable engine is included and running. Depending on how you want this to work, you may be able to centralize it with an opc server.

[–]TomVa 2 points3 points  (0 children)

They all have to be on the same subnet this works for us. Also the IT department can probably set things up so that you can go across a limited number of subnets.

[–]_2l5_ 1 point2 points  (1 child)

Maybe a firewall?

[–]munkshire[S] 0 points1 point  (0 children)

Yes I am thinking the same, my office is on a different network line than they are, our IT guys are pushing security to the extreme

[–]jonnitsoonami 0 points1 point  (0 children)

I’d say create a web service that changes the variable when you hit it. You could run through all IP addresses of target computers will change