Shared Variable

[m3nth]

If I am using some shared variables running through an SVE, is there a way (dynamically) to find out the computer name/IP that is running the SVE?  Or alternatively to find out the binding URL for the shared variable?--which will work for me since the SVE is on the same PC that is publishing data to the SV.

Thanks...

[Ankita]

Please see this KB for answer to your question.

Regards,

Ankita

[m3nth]

$2400 for access to a single property node... hmmmm....... lemme think about that one for a second um no.... not gonna happen.  I think if Shared Variables are included with the standard LabVIEW packages then this should be included also.  Shared Variables are (maybe) a good replacement for a standard tcp/udp connection (among other things) but one should be able to set the IP address for the connection without having to pay through the nose for a few property nodes.

[Ankita]

LabVIEW DSC module offers you much more than just a few property nodes. I do understand, however, that if one has no need for the several other neat features of the DSC module, then it is not worthwhile to spend that amount.

Ankita

[m3nth]

> Or alternatively to find out the binding URL for the shared variable?

If anyone else is interested in this post, there are some property nodes available for some of these functions without purchasing the DSC:

Application Method: Library.Open
Library Property: Children[]
{Read the children in a For Loop}
Children Property: Project Item
Project Item Property: Variable Reference
Variable Property: Name and Network.URL

These can be used in conjunction with the outPath string returned by ..\LabVIEW\resource\dialog\variable\VFP Network Source Browser.vi to dynamically load a library with Shared Variables and change their network binding.  That path may very well change for future releases but it's a handy little tool.

[REM1]

---

@m3nth wrote:
> Or alternatively to find out the binding URL for the shared variable?

If anyone else is interested in this post, there are some property nodes available for some of these functions without purchasing the DSC:

Application Method: Library.Open
Library Property: Children[]
{Read the children in a For Loop}
Children Property: Project Item
Project Item Property: Variable Reference
Variable Property: Name and Network.URL

These can be used in conjunction with the outPath string returned by ..\LabVIEW\resource\dialog\variable\VFP Network Source Browser.vi to dynamically load a library with Shared Variables and change their network binding.  That path may very well change for future releases but it's a handy little tool.

---

Attached is a VI to accomplish what you list here.

For those who are interested, the property/method nodes that exist in the absence of DSC affect the library file that contains the configuration of the variable.  If you make any changes you will need to re-deploy the library to have them reflected in the engine.  The DSC-only property/method nodes directly effect the SVE without modifying the configuration file.  2 different ways of accomplishing close to the same thing.