LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

DataSocket Read.vi returns constant timestamp

I'm using DataSocket Read.vi to collect data periodically from a PLC.  The sample period is about 1s but the timestamp output on the vi is constant for multiple reads seemingly changing only when the channel value changes.  I'm guessing that the timestamp represents the time at which the last channel value was established and that, if the value does not change, the timestamp doesn't either.  Can anyone help me understand this better?

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

The behavior you are describing sounds reasonable, but your question would probably be better directed to the PLC provider.

 

From what you describe, DataSocket is working. 

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

1) I agree with Philip.

 

I tsounds like yo uare looking at one or two possible reasons.

 

Deadband

 

Deadbands are used in process control to keep the I/O down. The value has to change by the deadband amount before it will be updated. Depending the OPC server this is often configurable on a channle by channel basis.

 

Update rate

 

Default is low or "on change" in the case of booleans.

 

So I would start poking at a configurtion screen for the OPC server to see if I could twaek any of those values to get a better update rate.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 3 of 3
(2,378 Views)