Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

WinCC - Retain IED's Timestamp in Alarm log

Created by: cykee at: 2/16/2006 7:21 AM (17 Replies)

Rating (0)

Thanks 0

Result pages:: |; 1 | 2; |

18 Entries

Entries per page: 10 | all

2/16/2006 7:21 AM	Rate (0)
cykee Regular Member Joined: 2/16/2006 Last visit: 5/11/2006 Posts: 25 Rating: (0)	My IED(double pts, with timestamp), treated as BTYE, needs to convert to BINARY in order to report as binary (OPEN/CLOSE) alarm. IED gives: (bit 1, bit 0) 0 0 - undefined 0 1 - open * 1 0 - close * 1 1 - undefined Now in WinCC, I've created an internal tag (INT_CB) to handle the open/close* logic, but the time reported to alarm log is no more the IED's Timestamp, it's taking the WinCC server time, which is undesirable. Anyway to pass the timestamp into the internal tag, so it could be reported as the IED timestamp when the event trigger? Or, Anyway to report an alarm (OPEN/CLOSE) when BYTE format in WinCC, and yet will ignore the condition when the IED is in "Undefined" stage? cykee

Suggestion To thank Quote Answer

2/16/2006 8:20 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi cykee, if you are using a S7-CPU this FAQs may be interesting for you: http://support.automation.siemens.com/WW/view/en/22028441 http://support.automation.siemens.com/WW/view/en/21737406 http://support.automation.siemens.com/WW/view/en/19036812 Nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

2/16/2006 8:38 AM	Rate (0)
cykee Regular Member Joined: 2/16/2006 Last visit: 5/11/2006 Posts: 25 Rating: (0)	Hi, I'm currently using third party OPC server software which converts IEC104 protocol to OPC with Timestamp. So the S7 CPU notes dont seem helpful. anyway to retain the timestamp of external tag when it's converted to internal tag, which later use the internal tagas alarm logging? Or, anyway to take external BYTE tag to trigger Boolean Alarm (OPEN/CLOSE)? Cos, at the Tag Management, I could see the correct timestamp of external tag when my mouse pointer goes to the external tag itself. cykee

Suggestion To thank Quote Answer

2/16/2006 9:13 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi, perhaps using WinCC OPC HDA would be an option for you? http://support.automation.siemens.com/WW/view/en/21320307 in the WinCC online help you can find some additional information as well. triggering an alarm with time stamp by changing a bit-value is of course no problem [:D] nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

2/16/2006 9:52 AM	Rate (0)
cykee Regular Member Joined: 2/16/2006 Last visit: 5/11/2006 Posts: 25 Rating: (0)	Hi, but my IED is using double bit, so in the scenario of (OPEN -> undefined), the alarm will also trigger even it's undefined, not CLOSE. This will create a false alarm to user. IED gives: (bit 1, bit 0) 0 0 - undefined 0 1 - open * 1 0 - close * 1 1 - undefined Anyway to pass the timestamp into the internal tag, so it could be reported as the IED timestamp when the event trigger? Or, Anyway to report an alarm (OPEN/CLOSE) when BYTE format in WinCC, and yet will ignore the condition when the IED is in "Undefined" stage?

Suggestion To thank Quote Answer

2/16/2006 11:15 AM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi Cykee, you could have a try with a"group message" => there you can combine several singular messages (message-bits) to one message. Check your wincc online help for "group message" nemo
Nemo Posts: 3149 Rating: (171)	Last edited by: Nemo at: 2/16/2006 11:15 AM
Suggestion To thank Quote Answer

2/17/2006 9:32 AM	Rate (0)
cykee Regular Member Joined: 2/16/2006 Last visit: 5/11/2006 Posts: 25 Rating: (0)	Hi, Group message only allow to group a number of single messages into one (irregardless) which one trigger it... my alarm trigger needs to look at both bits ( bit1 and bit0 ) at the same time. cykee

Suggestion To thank Quote Answer

2/17/2006 10:39 AM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	An alternative method is to have a Global Action that triggers your alarm when your condition is true. You can find alink toa scriptto trigger an alarm in the thread /tf/WW/en/Posts/2076.Check out the post by Reuben near the end of the thread. Regards, Salma

Suggestion To thank Quote Answer

2/17/2006 11:03 AM	Rate (0)
cykee Regular Member Joined: 2/16/2006 Last visit: 5/11/2006 Posts: 25 Rating: (0)	Hi salma, It's work for the logic of bits, but it cant retain the timestamp of IED. (the timecaptured in the alarm log is theWinCC time).An alternative idea? regards cykee

Suggestion To thank Quote Answer

2/17/2006 11:20 AM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	The script supplied by Reuben uses ODK functions. The functions allow you to pass in the necessary date/time value for the alarm. The sample script uses the current time but you can easily change this by modifying the line: [code]GetLocalTime( &stTime ); [/code] to something like: [code]stTime.wYear = 2006; stTime.wMonth = 02; stTime.wDay = 17; stTime.wHour = 00; stTime.wMinute = 00; stTime.wSecond = 00;[/code] Your only problem would then be to read the timestamp from your IED. I cannot see how to do this in C but it is easy to do in VBS using the .Timestamp property of the HMIRuntime.Tag object. Does anyone know how to read the timestamp ofa tag in C? If not, then I would suggest having a VBS script that writes the IED timestamp to an internal tag. Then use the C project function to read the internal tag and write to the stTime variable and pass this to the alarm. I hope this makes sense ! Salma

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on