shared variables properties

[viScience]

A few suggestions:

1. Use single quotes on your binding url, Example -

\\192.168.0.2\HPU IO\'PU.CP1_Inlet_Vacuum'

2. Use the error chaining on all NSV static nodes.

3. Enable PSP LED on your bound indicators, they should be green when running.

4. Use the Distributed System Manager to view and verify proper deployment and operation of all NSV's on your network.

[teritask]

1.  they are (I used browse to select them)

2.  not sure what that is, I will check into it

3.  they all have that in my host program

4.  have never used it, will check into it

Just not sure what I'm doing wrong that the Target program has to be running on the development computer for the shared variables to work. I thought I set everything up according to the help items I've reviewed but I'm missing something.

Thanks.

[viScience]

When running on the RT target:

If your host PSP LED's are green then all is well with the NSV binding

If your RT NSV's do not have error on the diagram then they are accepting transactions.

If the DSM can view changing values on the RT NSV's then the RT SVE is working correctly

[teritask · Accepted solution]

After quite a few hours trying to finally upgrade to Labview 2010, including reloading WinXP on my development computer because files became corrupted, I have everything working properly.

Thanks for the help.