• Replies 7 replies
  • Subscribers 582 subscribers
  • Views 655 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
  • Thanks Again,
    Got it working with showng correct time down to millisec, using ALARM Hres is set to 7.
    However there are some funny stuff going on if I restart the Citect Runtime with active alarms in the alarm list. When Runtime is restarted the alarm list only show one alarm even if there are several active in the system.
    And if I create a new alarm this new alarm will replace the alarm present on the alarm list. The acknowledge for the new triggered alarm is not active as well, even though the .ack status is 0.
    The only way to get things back to normal is to stop RunTime once more and then compile the project and then start RunTime.

    This does not happen if I configure my alarms as Digital Alarms, only Time Stamped Alarms. (Not tried Time Stamped Digital Alarms).

    Any suggestions?
    It seems like there is an alarm buffer/databasse/cache or other that is not cleared when you Stop and Start the Runtime.
Reply
  • Thanks Again,
    Got it working with showng correct time down to millisec, using ALARM Hres is set to 7.
    However there are some funny stuff going on if I restart the Citect Runtime with active alarms in the alarm list. When Runtime is restarted the alarm list only show one alarm even if there are several active in the system.
    And if I create a new alarm this new alarm will replace the alarm present on the alarm list. The acknowledge for the new triggered alarm is not active as well, even though the .ack status is 0.
    The only way to get things back to normal is to stop RunTime once more and then compile the project and then start RunTime.

    This does not happen if I configure my alarms as Digital Alarms, only Time Stamped Alarms. (Not tried Time Stamped Digital Alarms).

    Any suggestions?
    It seems like there is an alarm buffer/databasse/cache or other that is not cleared when you Stop and Start the Runtime.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.