LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Binding shared variable in executable across network

I can't seem to get a shared variable to bind from an executable on another computer back to a source variable on the main machine.

 

I can get the remote variable to change with programmatic access.  Is it possible to have shared variables in an executable bind to a PSP URL on another computer?  This is labview 2011.

 

I can see everything with NI Distributed System Manager, and the programmatic access changes the remote variable, so it's not a network issue.

 

Thanks for any insights.  This just doesn't seem to work the way NI's online white papers say it shoud.

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

sgonzo,

You should be able to have shared variables bind to a PSP URL on another computer, have you followed the steps outlined in this article? - http://zone.ni.com/reference/en-XX/help/371361H-01/lvconcepts/sv_binding_to_existing_sources/
Also, do you have the box titled Deploy shared variable libraries at application execution checked as shown in this article? http://digital.ni.com/public.nsf/websearch/04D9A85B6967EE87862571140065EEC6?OpenDocument

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

What I don't understand is why after binding to a specific URL, the "Shared Variable Deployment" screen of the application builder makes the target "my computer". 

 

I probably could get this to work if I changed the network address of "my computer" in the ini file created in Application Builder?

 

This seem a strange way for this binding process to work.  If the absolute target (for shared variable bound to another variable and referencing "absolute") was retained when the VI goes through the application builder, it would make for sense.

 

I can't get this to work any way with using bound variables.  The only way this works is using programmatic access to shared variables in the built app, and I don't consider this the same thing.

 

My conclusion is that shared variable binding and appropriate absolute references to deployed variable libraries do not survive passing through the application builder with their absolute references intact.

 

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