• Replies 7 replies
  • Subscribers 582 subscribers
  • Views 650 views
  • Users 0 members are here
Options
Related

Citect Scada 2018 SA - Time Stamped Alarms Not showing correct time in Page

Rune

Hi,

Alarms setup as "Time Stamped Alarm" using Miilisecond Counter from the Controller. 

In the controller I have

Hr = 11

Min = 8

Sec = 39

Millisec = 619

Adding these together the time value sent as Integer to Citect Scada 2018 SA is 40119619 -this value I can display in Citect screen through a numeric value. 

The time stamp in the alarm page is 03:04:33

My Paramter config is set like:

FORMAT ->ALARM: {PriorityAndState,25}{OnDate,80}{OnTime,90}{Name,250}{State,40}{Equipment,220}{Item,160}{Category,60}

I see from help file that {OnMilli,n} might be used but dont know how to add it as the time format comes up like hh:mm:ss.mmm

When I add {OnMilli,n}  it comes as a new column in the alarm page. 

BIG Question! How to get correct time stamp in the alarm page? 

Thanks for any input,

Rune

Parents
  • You could replace {OnDate,80}{OnTime,90} in your format with {LocaltimeDate,170}
    To prevent this time-stamp from changing when acknowledging or resetting the alarm, you can add the following parameters to your project (or Citect.ini):
    [Alarm]SetTimeOnAck=0
    [Alarm]SetTimeOnOff=0
    Be aware that setting these parameters can affect alarm logging (summary and/or SOE) and alarm event queue handling also.

    It would be nice if AVEVA could implement {OnTimeDate}, {AckTimeDdate} and {OffTimeDate} fields as well! (Hint to developers...)

    Regards,

    Patrick
Reply
  • You could replace {OnDate,80}{OnTime,90} in your format with {LocaltimeDate,170}
    To prevent this time-stamp from changing when acknowledging or resetting the alarm, you can add the following parameters to your project (or Citect.ini):
    [Alarm]SetTimeOnAck=0
    [Alarm]SetTimeOnOff=0
    Be aware that setting these parameters can affect alarm logging (summary and/or SOE) and alarm event queue handling also.

    It would be nice if AVEVA could implement {OnTimeDate}, {AckTimeDdate} and {OffTimeDate} fields as well! (Hint to developers...)

    Regards,

    Patrick
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.