LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Front Panel binding of shared variables very slow initialization / start

Hello @ all,
 
I am using a server running Windows2000 and LV 8 DSC RTS for datalogging. All shared variables are deployed on that server.
I am now facing the problem, that all front panels running on the clients using the network shared variables on the server take very long to sync on startup. First the flags on the controls bind to the shared variables turn red, after up to ten minutes they start to turn green. The panels use up to 40 controls bind to the shared variables.
All firewalls are turned off. I tried to connect the client to the same switch the server is connected to. Same problem. Does anybody have a clue?
Thx for your quick answers.
 
Carsten 
0 Kudos
Message 1 of 5
(5,093 Views)
While I can't offer any solution to your problem, I am having a similar issue running LV8.0 and shared variables on my block diagram (no DSC installed).

When using network published shared variables, it takes anywhere from 30 sec to 4 min from the vi start for any updates to be seen. Given enough time, they will all update normally, however this 4 minute time lag is somewhat troublesome.

I have confirmed the issue to be present when running the shared variable engine on windows and RT platforms, with exactly the same results.

In my case, the worst offenders are a couple of double precision arrays (4 elements each). They will normally exhibit similar "spurty" behavior on startup, and eventually work their way up to continuous and normal update rates. Interestingly enough there are no errors generated by the shared variables on the block diagram.
Greg Sussman
Sr Business Manager A/D/G BU
0 Kudos
Message 2 of 5
(4,986 Views)

Hallo,

I can report the same behaviour in my application that is almost similar: A client with 10 or so analog values and around 5 very small arrays. NI has no clue to it yet. It's really troublesome.

Greetings,

sun@work

0 Kudos
Message 3 of 5
(4,842 Views)
Found the problem!
 
After several hours talking to different support people from NI we found out that DSC does not support two network cards. After deactivating the second network card in the computer (server) Labview returned to normal operation.
 
It´s not a bug, it´s a feature... 😉
 
Carsten
0 Kudos
Message 4 of 5
(4,839 Views)
I'm not sure what you mean by "does not support two network cards".  I have a machine running DSC talking to the plant on one card and I access a DSC OPC client instance on another card.
0 Kudos
Message 5 of 5
(4,570 Views)