LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Network shared variables not binding to local variables

Hi,

 

I have a cRIO system with 3 Ethercat slaves used for data acquisition. The program running on the cRIO writes the input values to network shared variables (NI-PSP) at a rate of 1Hz (and vice versa for the outputs). On the host/server, a Labview library with DSC logging enabled is created with local variables bound to the network variables.

 

This arrangement used to work fine. Recently I added another 9205 module and modified the code on the cRIO accordingly. Since that time, when I create a new library with local variables they won't bind to the network variables and fail to show up in the citadel database. If I add the local variables to a VI for monitoring they all return zeros.

 

When viewing these variables in the VI the PSP LED lights up green, but it says "quality warning on: [local address]" when I hover over it. To see the quality warning I used the VI available here: http://digital.ni.com/public.nsf/websearch/E28D2A41474652E886256E380061D829?OpenDocument 

-When I test a network variable it returns a quality of 0 and the proper data value. So it appears the issue isn't with the network variables.

-When I test a local variable it returns a quality of 0 and a data value of 0. I am not necessarily confident in this result, since the PSP-LED says there is a quality warning- yet none is shown here.

 

The network variables are indeed being published to the network as I can see their correct values updating in Distributed System Manager. Also, I know the library with the local variables is set up properly because when I add a variable that is bound to a different cRIO system's network variable (there are 3 similar systems feeding back to this server) it will show up in the citadel database and return the proper values.

 

I am at a total loss, any help would be greatly appreciated.

 

Labview 2011 SP1

cRIO- 9144 & 9074

 

Thanks,

Kyle

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

If you added the module to one of the 9144 chassis you should power cycle the chassis to make sure the module is detected by the firmware of the chassis.

If you right click the cRIO controller and run the "Compare Project and System" tool from Utilities. Check for differences and follow the instructions to get both equaly configured.

Let me know if that doesn't help.

 

DirkW

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

DirkW

 

Thanks for the suggestions.

 

I've already cycled the power many time in hopes that the issue would correct itself, to no avail.

 

I just ran the "Compare Project and System" as you suggested and there were no discrepancies.

 

The problem isn't with the module I just added, it's with every channel on the system. All the channels, including the one I added, are successfully written to network shared variables which can be read in distributed system manager. The problem arises when trying to bind the network variables to local variables.

 

Kyle

 

 

 

 

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