Good morning,
i have a simple question... the alarm timestamp on the standard alarm panel is the LOCAL PC date & time or it's the PLC Date & TIME?
for example:
Alarm ON PLC date & time 24/09/2015 - 11:55:10:10
The wincc OA driver read the alarm on date & time 24/09/2015 - 11:55:50:15
On the alarm panel i'm going to have the first (plc) timestamp or the second (PC) timestamp ?
If i'm going to have the PC timestamp... can i show the PLC timestamp instead?
Thank you!
ALARMS timestamp. From LOCAL PC or PLC??
- gianluca.bravetti
- Posts:3
- Joined: Tue Feb 17, 2015 10:29 am
ALARMS timestamp. From LOCAL PC or PLC??
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: ALARMS timestamp. From LOCAL PC or PLC??
It depends on the used driver if it can use the timestamp of the plc and if the received timestamp is in the valid timerange.
The '_alert_hdl' config has a '_system_time' attribute, which contains the timestamp of the alert creation.
The '_alert_hdl' config has a '_system_time' attribute, which contains the timestamp of the alert creation.
- gianluca.bravetti
- Posts:3
- Joined: Tue Feb 17, 2015 10:29 am
Re: ALARMS timestamp. From LOCAL PC or PLC??
Thank you. i'm using a S7-TCP/IP driver with a S7-1500 PLC. on the AES TABLE CONFIGURATION when i add a column and choose DPA as the value i cannot see the _system_time attribute on the dropdown list. Maybe the attribute is not supported by the driver?
- gianluca.bravetti
- Posts:3
- Joined: Tue Feb 17, 2015 10:29 am
Re: ALARMS timestamp. From LOCAL PC or PLC??
Problem solved with the TSPP protocol