LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Datasocket write delay

I am using Labview with 2 configured OPC servers, one connected to a Siemens S7 PLC, the other to a PC running a simulation package.

Under normal operation without simulation, when viewing status of individual tags in DSC tag monitor, HMI buttons on all VI panels respond almost immediately when operated (tag update is rapid).

When running simulation, button states can take in excess of a minute to be written to their tags.

What is the cause of this & how can it be rectified ?

Thanks in anticipation of your assistance

Mark


0 Kudos
Message 1 of 4
(6,915 Views)
Hi Mark

Have you had a look at this Knowledgebase article that lists a solution to slow Datasocket activity.

http://digital.ni.com/public.nsf/allkb/2D9C6D73A160537986256B290076456E?OpenDocument

Kindest Regards

Yatin | NIUK & Ireland
0 Kudos
Message 2 of 4
(6,622 Views)
Also this KB shows how to improve the performance of the DSC Engine

http://digital.ni.com/public.nsf/websearch/489D02387DE3A03986256F000066AD47?OpenDocument

Regards

Yatin | NIUK & Ireland
0 Kudos
Message 3 of 4
(6,620 Views)
Thank you very much for your reply, YatinM.

I have seen both of these KB articles.

My problem involves writing to tags (via the datasocket).

E.G. I have a button on the front panel of a VI. The datasocket connection is pointed at tag 'x' and is configured to publish.
        tag 'x' is configured in the DSC as a write only tag.
     
        Other parts of the system are a Siemens S7 PLC and another PC which runs a simulation package (test stand). All items are 
        networked with a Siemens OPC server.

        If the front panel of the VI is running and the button is toggled, the change in status is almost immediate (in the DSC tag
        monitor). If the simulation package is started, toggling the VI front panel button does not result in a rapid change in status when
        the DSC tag monitor is viewed - it can take several minutes for the status to change ! If the simulation package is stopped,
        performance returns to normal (i.e. updating is rapid).

        I did consider that the tag was being overwritten by the simulator via the OPC server, but this particular tag is not configured
        on the simulator and as a "belts and braces" exercise, I changed the datasocket connection for the tag to publish and changed
        the tag itself to write only (see above). In any case, once the tag state changes to match the state of the button, it does not vary.

        The property node for the tag is in a while loop on the VI block diagram. If a probe is placed on the block diagram, it can be seen that
        when the front panel button is pressed, the property node immediately assumes the button status regardless of whether the simulator
        is running or not. The while loop executes at 250mS intervals - this has also been monitored and does not vary.

        I have this problem with several buttons on several VI front panels.

        I'm tearing my hair out and would welcome any further suggestions !!

        Mark Last

0 Kudos
Message 4 of 4
(6,581 Views)