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?
OS - WinCC -- Creating HMI configurations -- Configuring picture changes
What should you watch out for in particular with the "Loop in Alarm" function?
Closing images that the wizard has created upon image change
How can I dynamically adapt the size of the @Top display when I call a picture with the SSMOpenTopField function?
How can you have the current picture continued to be shown when you log out of WinCC Runtime?
What options are there for configuring a picture change between two or more servers and the MultiClient (MC)?
How can you display/hide a layer depending on a variable?
What should you watch out for in particular with the "Loop in Alarm" function?
Part number:

Configuration description:
With the "Loop in Alarm" function, a single message is assigned a C function in Alarm Logging which serves to conduct a picture change or to call a faceplate in Runtime. WinCC uses the "OpenPicture()" standard function as the default picture function.
If your WinCC screen is split into header, footer and working areas by means of the "Basic Process Control" option and if only the picture in the working area is changed during a picture change (i.e. the header and footer areas remain the same), the original form of the standard "OpenPicture()" function is unsuitable for a picture change. The reason for this is that the "OpenPicture()" function performs a picture change for the whole WinCC screen as standard. The opened WinCC picture then fills the whole WinCC screen - the header and footer areas disappear.

Note:
The following figure shows the WinCC standard "OpenPicture()" function. It uses the internal WinCC "SetPictureName()" function to set the "picture name" property for a screen window. The "szPictureName" parameter (third parameter) contains the name of the picture. Since the "lpszPictureName" and "lpszObjectName" parameters (first and second parameters) are configured with "ZERO", the picture change is performed for the entire WinCC screen. This behavior also applies to the internal "SetPropChar()" function for setting the picture name for a screen window.


Fig. 01

Remedy:
Adapt the "OpenPicture()" function in line with your requirements or create a separate picture change function. The picture change function which is specified in "Loop in Alarm" functionality (picture function) expects precisely one "char*"-type parameter and the types "unsigned char", "short int", "long int", "float", "double", "bool" or "void" as the return value.

  • Using Basic Process Control functions for screen management
    If you are working with Basic Process Control, you can use the "SSMRTChangeWorkField()" split screen manager. 


    Fig. 02

  • Using separate functions for screen management
    If you are not using Basic Process Control for screen management, you generally have separate project or standard functions for screen management. Use one of these functions for "Loop In Alarm" functionality or adapt one of these functions.

Note:
The function which is configured for "Loop in Alarm" is only called in Runtime when the "Loop in Alarm" button in the alarm control is clicked if you have specified a precise string (picture name) in the "Picture name / Call parameter" input field. The function is not called if you have not specified a string or if you have specified multiple strings (i.e. the string contains spaces).

There is detailed information available in the WinCC Online Help under:

  • "WinCC Information System > Working with WinCC > Setting Up an Alarm System > Configuring the Message System > Using Single Messages > Linking a Picture to a Single Message"x
  • "WinCC Information System > Options > Options for Process Control > OS Project Editor > Split Screen Manager >The "Loop in Alarm" Function"
 Entry ID:71178   Date:2006-11-27 
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 
Topics
Help
Online Help
Guided Tour