• Replies 1 reply
  • Subscribers 585 subscribers
  • Views 112 views
  • Users 0 members are here
Options
Related

Alarm Off time logged as older than Alarm On time

Patrice

Hello all,

We are encountering a recurring problem.

For some alarms, the when the alarm goes back to normal (OFF), the Off time is displayed as older that the time the alarm occured.

For example, this alarm arrived at 2020-11-13 at 13:32:35 

Once it is Acked and back to normal state, the date and time are displayed as 2020-11-12 23:07:52 instead of the time it went back to normal:

This happens to only a few alarms (about 25 out of 15,000). 

Everytime I force the tag into alarm, when I put it back to normal, the same date and time (2020-11-12 23:07:52) is logged as the Off timestamp.

The effects of this is whenever we restart Citect, some old alarms (from 3 or 4 years ago) are logged in our alarm log device, causing multiple entries of the same alarm event.

We are using CitectSCADA 2016 Update 36 (09 december 2019) with redundant alarm servers.

Any help would be appreciated.

Thanks,

Patrice Jacob

Prosystech inc.

Parents
  • Hi Patrice,

    First thing I thought when I read the article headline was that you might have used an incorrect mix of DATE with ONTIME, or ONDATE with TIME, or similar as field expressions for logging, but I don't think that is what's wrong here.

    Can you explain how your log device is defined (txt, dbf, or other), its period, how many files and what format is used for it?

    Have you set any alarm parameters that could influence the alarm logging behaviour, such as [Alarmlog]Format, [Alarm]SetTimeOnAck / SetTimeOnOff, or similar?

    Are your alarm server clocks synchronized and are they using the same regional settings for location and DST, etc.?

    This might be a case where you have to reach out to Support if you get stuck.

    Regards,
    Patrick
Reply
  • Hi Patrice,

    First thing I thought when I read the article headline was that you might have used an incorrect mix of DATE with ONTIME, or ONDATE with TIME, or similar as field expressions for logging, but I don't think that is what's wrong here.

    Can you explain how your log device is defined (txt, dbf, or other), its period, how many files and what format is used for it?

    Have you set any alarm parameters that could influence the alarm logging behaviour, such as [Alarmlog]Format, [Alarm]SetTimeOnAck / SetTimeOnOff, or similar?

    Are your alarm server clocks synchronized and are they using the same regional settings for location and DST, etc.?

    This might be a case where you have to reach out to Support if you get stuck.

    Regards,
    Patrick
Children
No Data
© 2024 AVEVA Group Limited or its subsidiaries. All Rights Reserved.