show the entry list
WinCC -- Configuring alarms and messages -- Configuring Alarm Logging
How do you calculate the memory requirement of a server or central archive server (CAS)?
How can I create a message in WinCC if, when backing up an archive, the backup path is not available, cannot be reached or the data medium is full?
How can you switch off the message 1000915 "Terminal adapter <MAC-address> disconnect"?
How can I avoid the whole screen being filled when I open a picture using the OpenPicture function via LoopInAlarm?
How can you increase the timeout for starting and terminating Alarm Logging / Tag Logging?
What do the error messages "Transfer buffer too small", "TagQueue overflow" and "Messages are lost" mean?
Which functions do the different variable types have for the individual messages?
How can you get specific messages to flash in the alarm list until the user has acknowledged them?
What format is best suited for defining the AlarmLogging-event variables?
What do you do if alarms are not displayed at Runtime?
How can you assign the functions of the toolbar buttons of WinCC Alarm Logging OCX to external buttons?
How can I delete individual messages from a group message?
When are alarms initiated by the limit monitoring in WinCC if the limit values are supplied indirectly?
What should I watch out for when assigning the names of message types, message classes and group messages?
Why isn’t there display of the "Comment" toolbar button of the Alarm Logging Control in Runtime?
How can you display process values formatted in an Alarm Logging message line?
How can I change the state texts of the message classes from +, -, * to actual text of my own?
How can you check the configuration of the Alarm Logging to see whether there is multiple use of message, status and acknowledge tags or whether the message tags are not configured?
At Runtime, how can you determine the message texts or process-associated values when a message appears in the associated, user-specific action "GMsgFunction()"?
How do you display and operate alarms in Runtime?
What is the structure of the format instruction for displaying the contents of WinCC tag values at Runtime in the user text blocks of a message?
How can you create messages whose message texts consist of a fixed part and a variable part?
What do the statuses of the status and acknowledge tags look like in the Alarm Logging?
What statuses can a message go through at Runtime?
How can I use the limit-value monitoring function of Alarm Logging to monitor the free drive space of a hard disk?
Why after WinCC Runtime starts is a message displayed with the text "..... already used"?
How can you configure user-defined message classes?
How can you change the acquisition cycle of the WinCC Alarm Logging?
How can you use the status tag of a message?
What should you watch out for in particular with the "Loop in Alarm" function?
How can you export, change and then reimport message texts?
How can you assign the functions of the toolbar buttons of WinCC Alarm Logging OCX to external buttons?
Part number:

Description:
You can assign the functions of the toolbar buttons of WinCC Alarm Logging OCX to external buttons as follows:

Using the new Alarm Control as from WinCC V7:

If you do not want to operate WinCC Alarm Control in Runtime via the toolbar buttons, you have the option of using the "SetPropDouble" or "SetPropWord" C function to assign the functionality of a toolbar button to an external button. This function can also be implemented via a VB script. Details can be found in the WinCC Online Help in these paths:

Example:
Switch to the short-term archive using the "SetPropDouble" C function
 
No. Procedure
1 Note the object ID of the desired button (in the example, the button for calling the short-term archive). The object ID of the button is in the Configuration dialog in the "Toolbar" tab. The importance of the "ID" can also be found in the WinCC Online Help under the path "Working with WinCC > Setting up a Message System > Display of Messages during Runtime > Operation during Runtime > Operation of the Alarm Control in Runtime".


Fig. 01

2 In the desired picture, you create a button that is to be assigned the function of the toolbar button.
3 Select the "Event" tab in the "Object Properties" of the button.
4 Under "Mouse > Mouse Click > C action" configure the following action.
5 Select the function in the following path: "Internal Functions > graphics > set > property > SetPropDouble".


Fig. 02

6 Parameterize this function with the relevant values as shown in the screenshot:
  • lpszPictureName: name of the picture if, unlike the example, the button has been created in the same picture as the control.
  • lpszObjectName: name of your control (in the example: "Control1").
  • lpszPropertyName: name of the property that you want to change (in this case "ToolbarButtonClick" of the control).
  • dValue: Object ID of the button (here you enter the object ID noted in Step 1, which has the value 4 in the example).


Fig. 03

Using the old Alarm Control as from WinCC V6 (designated as Alarm Control (Classic) in the Graphics Designer as from WinCC V7)

If you do not want to operate WinCC Alarm Control in Runtime via the toolbar buttons, you have the option of using the "SetPropDouble" function to assign the functionality of a toolbar button to an external button.

Example:
Switch to the short-term archive
 
No. Procedure
1 Note the object ID of the desired button (in the example, the button for calling the short-term archive). The object ID of the button is in the Help under "Button Command - Property".


Fig. 04

2 In the desired picture, you create a button that is to be assigned the function of the toolbar button.
3 Select the "Event" tab in the "Object Properties" of the button.
4 Under "Mouse > Mouse Click > C action" configure the following action.
5 Select the function in the following path: "Internal Functions > graphics > set > property > SetPropDouble".


Fig. 05

6 Parameterize this function with the relevant values as shown in the screenshot:
  • lpszPictureName: name of the picture if, unlike the example, the button has been created in the same picture as the control.
  • lpszObjectName: name of your control (in the example: "Control1").
  • lpszPropertyName: name of the property that you want to change (in this case "ButtonCommand" of the control).
  • dValue: Object ID of the button (here you enter the object ID noted in Step 1, which has the value 2 in the example).


Fig. 06

Classic procedure for up to and including WinCC V6

If you do not want to operate WinCC Alarm Control in Runtime via the toolbar buttons, you have a number of functions available in the Global Script Editor under "Standard functions > Alarm".

More information is available in the WinCC Online Help in this path:

Example:
Switch to the short-term archive
 
No. Procedure
1 Create a button in the desired picture.
2 Select the "Event" tab in the "Object Properties" of the button.
3 Under "Mouse > Mouse Click > C action" configure the following action.
4 From "Standard functions > Alarm" select the "AXC_OnBtnArcShort" function with a double-click.
5 Parameterization of the function selected above:
lpszPictureName: this specifies the name of the picture in which the Alarm Control is located. This is only necessary if the Alarm Control is located in a picture window, i.e. in a different picture to the one the button is in.
lpszObjectName: the name of the Alarm Control is selected from the menu here. The object name of the control is also in the Properties of the Alarm Control.


Fig. 07


Fig. 08


Fig. 09

6 Compile to complete parameterization of the function.


Fig. 10

Now, when you click this button, the short-term archive is displayed in the Alarm Control.

 Entry ID:11769423   Date:2011-07-11 
I regard this article....as helpfulas not helpful                                 
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour