Skip to main content
A
AS_144165357-Bedrock
7-Bedrock
December 8, 2025
Solved

Simulator tag not updating via link advance tag

  • December 8, 2025
  • 1 reply
  • 126 views

I have set up a simulator tag that receives its value from the link advance tag. The input of the link advance tag is the value from the ADAM READ-only Register address, and the output of the link advance tag is the simulator tag value. I have configured the link tag as the on interval mode, so that after every 100ms, link tag writes whatever the value is at the register address to the simulator tag. but the question is, even if the value is same after 100ms, is the update counter on the OPC client side should update its value or not ..?

Best answer by pshashipreetham

Hi, 

 

This is expected behaviour. Link Advance checks the source every 100 ms, but Kepware only pushes an OPC update when something actually changes. If the value remains unchanged, the simulator tag does not receive a new timestamp, and the OPC client will not see an update. The update counter only increments when the value, quality, or timestamp changes.

 

If a visible update is required every cycle, enable Always Update on Write on the simulator tag or introduce a small calculated change using an Advanced Tag or expression. Otherwise, nothing is broken. Kepware is suppressing redundant data by design.

 

Thanks,

1 reply

P
18-Opal
pshashipreetham18-OpalAnswer
18-Opal
December 23, 2025

Hi, 

 

This is expected behaviour. Link Advance checks the source every 100 ms, but Kepware only pushes an OPC update when something actually changes. If the value remains unchanged, the simulator tag does not receive a new timestamp, and the OPC client will not see an update. The update counter only increments when the value, quality, or timestamp changes.

 

If a visible update is required every cycle, enable Always Update on Write on the simulator tag or introduce a small calculated change using an Advanced Tag or expression. Otherwise, nothing is broken. Kepware is suppressing redundant data by design.

 

Thanks,

Terms & ConditionsCookie settingsAccessibility statement