Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

'non-alarm' alarm logging?

Created by: ranr_mids at: 2/1/2006 11:10 AM (18 Replies)

Rating (0)

Thanks 0

Result pages:: |; 1 | 2; |

19 Entries

Entries per page: 10 | all

2/1/2006 11:10 AM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Greetings. I am attempting to set up a number of event messages in the WinCC alarm system that are triggered by certain operator actions (typically manual control / modification of variables). I have set up messages to log what was changed and by whom, and have used the 'Warning' type for them. So far, I can successfully trigger the messages, but I am experiencing problems :- 1) The values I am attempting to store are"one message late", i.e. no data is stored in the first message, the data associated with the first messageis storedin the second message, and so on. 2) The messages appear in the current message list, but do not appear in the short-term or long-term archives. Any ideas? Thanks.

Suggestion To thank Quote Answer

2/1/2006 11:17 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Regarding point 1: I do not completely get it. Can you explain further? Regarding point 2: Did you amrk the checkbox of the alarm in the alarm control stating "Will be archived"? Cause this checkbox will see to it that it is stored in archive.
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

2/1/2006 11:44 AM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	Point 1: When an operator accepts a manual setpoint change (via a button), script behind that button stores the Tagname, before value, and after value, in memory tags. It then triggers the message, which shows the values in these tags via Process Value Blocks. The values shown, however, are not for the message that was triggered, but for the message that preceeded it. The triggers for these messages are momentary, may that have an impact? Point 2: The archivetick-box for these messages is set.

Suggestion To thank Quote Answer

2/1/2006 11:50 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Hi, Point 1: Maybe Salma can comment on this one, but just an idea: You could also use the Operator Event message to store values, that's what I do. (You have to use ODK for this.) Point 2: Only thing I can think of are the filter settings set up oke for the archive view?
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

2/1/2006 12:03 PM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	For some reason I am not aware of, the messages now appear in the archives. Thanks for your input The only thing I've done is ticked the 'created on a negative edge' tick-box for the messages.

Suggestion To thank Quote Answer

2/1/2006 12:04 PM	Rate (0)
Salma Gold Member Joined: 9/27/2005 Last visit: 11/27/2007 Posts: 1398 Rating: (151)	1) This sounds like a timing issue. WinCC has not finished writing to the internal tags before the alarm is triggered, therefore it's picking up the old value. Introducing a delay between writing to the tags and triggering the alarm just prevent this happening. You can either place the delay in the script, e.g. using a for next loop that takes a second to run, or daisy chain two scripts so that the first writes to the tags and triggers a second script to trigger the alarm. Of course there are other options and these are just two suggestions. Alternatively it may be worth going down the Operator Actions route as lkkezelf suggested. 2) I would deactivate runtime, delete all runtime data using the Reset option in the Alarm Logging Editor, reboot the PC (overkill? well maybe but it won't cause any harm). I would then check that all the databases have been deleted successfully from the ArchiveManager folder. After this I would try starting and activating WinCC. I have found that sometimes a simple reboot fixes the issue (why, I don't know [:(] ) and other times the database files aren't created correctly. The latter is usually caused by version mismatches, permission faults or incorrect regional settings. Regards, Salma

Suggestion To thank Quote Answer

2/1/2006 12:44 PM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	I've just noticed that on my alarm list the User Name field is always blank. I'd never really checked it before, assuming it would be one of those 'System' fields that takes care of itself, like Date and Time. Do I have to set anything up, to display the current login-name in that field?

Suggestion To thank Quote Answer

2/1/2006 1:02 PM	Rate (0)
Nemo Posts: 3149 Rating: (171)	Hi ranr_mids, please check this out: http://support.automation.siemens.com/WW/view/en/22269581 regards, nemo
Nemo Posts: 3149 Rating: (171)
Suggestion To thank Quote Answer

2/1/2006 1:52 PM	Rate (0)
ranr_mids Bronze Member Joined: 12/5/2005 Last visit: 8/9/2021 Posts: 289 Rating: (19)	I've followed the suggestions from the link you posted, and it seems to work OK now. I'm just curious as to why I needed to manually add a Process Variable Block containing the @CurrentUser tag to all of my 1000's of alarms when something that looked like exactly what I needed is provided as standard.

Suggestion To thank Quote Answer

2/1/2006 1:58 PM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Hi, When you export the alarms, you can alter them in excel or notepad/ultraedit. In this way you don't have to change them manually. regards. ikkezelf
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on