Write OPC Values Delayed or Conflicting?

[skibum019]

We have Lookout 6.1 and KepWare OPC server.  We have values from a fieldpoint module that we are then writing out to tags on the Kepware OPC server which is connected to a Mitsubishi PLC network.  If the PLC writes a value to the same device we are writing to, the device stays that value for time "X" (seems to be upward of a minute or more) before the fieldpoint value is written to the PLC device again resetting the value to the current actual value.  The OPC device in Lookout is setup as OPC 1.0 (2.0 doesn't seem to work in Lookout), use asynchronous I/O, force refresh after write, reconnect automatically, update rate of 100 ms, deadband of 0.000 percent, no poll device, and no default access.

If we reopen Lookout, then the devices all get updated with the current values from the fieldpoint system.

[Ryan.S]

It looks like correct behaviour from your description.

For example, you have the connection OPClient.xxx.xxx = FieldPoint.xxx.xxx

Whenever the FieldPoint's data changes, it will be written to the Kepware through OPClient object. But it doesn't know if the data on OPC Server is changed by other source. The Lookout data will be output to OPC Server only when it changes in Lookout.

When the PLC writes a value to the same device or same address, Lookout doesn't know that it needs to write or reset the data again because the data source in Lookout doesn't change. 

The problem I think is there are two sources that can write value to a same address. Maybe it's in need sometimes, but the confliction cannot be avoided.

Let me know if I misunderstand your description.