Back

Topic

[KB794]Change in the criteria used to update alarms on a client

Tags: Multistation

Upgrade issues
9 years ago
By RM
Options
Print
Applies to:

PcVue 10.0 SP1 Update (10.0.16067), 10.0 SP2 Update (10.0.26023), 11.1 Update (11.1.06020)
Summary:

The criteria used to update alarms in a PcVue client has changed from the above versions onwards.

Originator: ND
Details:

Prior to the above versions changes in alarm were only sent to a client when the alarm status changed. A change in the timestamp alone was not sufficient. This method was used originally to keep the network traffic to a minimum. However it can cause discrepancies in the alarm timestamp on different clients under particular circumstances.

  1. An alarm is updated in such a way that its timestamp changes but the status doesn’t. This can only happen under particular conditions –  one example is a user dll (API Manager) doing “setdataset” on an alarm with the same status but a different time stamp (for example alarm was “on – not ack | 6:50” and is now “on – not ack | 6 :51 PM”).
  2. The architecture of the system is such that some clients are not connected all the time. 

From the above version onwards alarms are sent to clients when their timestamp changes even if the alarm status has not changed.

Created on: 09 Jul 2015 Last update: 13 May 2024