show the entry list
OS - WinCC -- Configuring Alarm Logging -- Configuring alarms and messages
How can you create operator inputs through user-specific actions in up to and including WinCC V6.0 SP4?
How do you display and operate alarms in Runtime?
What do you do if alarms are not displayed at Runtime?
How can you change the column width of the message blocks with the mouse in WinCC Alarm Control when configuring in the Graphics Designer or in Runtime?
Configuring the system block "PLC/CPU number" in messages
Why are measuring-point-specific messages not displayed in the faceplate (PCS 7 V4.x / V5.x)?
What can you do if no messages are displayed in the overview area of WinCC?
Generating a new time stamp despite identical operator messages
Triggering of the horn with messages that are blocked for specific users
Why are the time stamps of messages struck through or replaced by asterisks in PCS 7?
SIMATIC PCS 7 V5/V6 - non-acknowledgable messages on the message new page
What are the priorities for the display of faults, warnings etc. in the group display?
How can you have a block comment displayed in an operator message?
Why are operator messages shown only on the OS server and not on the OS client?
Why after upgrading from PCS 7 V6.0 SP2 to SP3 isn't the operator who acknowledges a message entered in the operator message?
Why doesn't the operator prompt flash in the group display?
Modification of the printing color in the tag logging
How can I make messages for a certain operator be displayed in WinCC Runtime but cannot be acknowledged?
How can you reconfigure the alarm acknowledgment behavior?
Why isn't the process message displayed in my PCS 7 project?
How do you suppress the process control group messages?
What is the meaning of the process control group messages created during OS compilation?
Which process control group messages are created in the OS?
Which process control group messages are created in the OS?
Part number:


Configuration Notes:
With STEP 7 V5.1 there is a new structure and different behavior of the group messages for the HMI systems. Previously there were seven group messages. There are now 21 group messages in the new version. The seven original messages are contained in three groups of seven. The following table lists the new messages.



AS fault synchronous incoming
AS fault asynchronous incoming
Module fault incoming
Stop/abort fault incoming
H/F system fault incoming
Communications fault incoming
Fault in CP/FM module incoming

Group 1

AS fault synchronous outgoing
AS fault asynchronous outgoing
Module fault outgoing
Stop/abort fault outgoing
H/F system fault outgoing
Communications fault outgoing
Fault in CP/FM module outgoing

Group 2

Message about AS fault synchronous
Message about AS fault asynchronous
Message from module
Stop/abort message
H/F system message
Communications message
Message from CP/FM module

Group 3

The three groups always contain the same messages for the different status options of the message (incoming, outgoing, status unknown).
Because of the properties of the message class "OS Instrumentation and Control Message" the IC messages do not have an "incoming/outgoing" display in the message line. Therefore an extra "incoming" and the "outgoing" message is sent for each individual message.
The message of the type "outgoing" is however only displayed when the message of the type "incoming" has also been acknowledged beforehand. If not, then the message is not displayed again.

Group 3 is needed, because after an update of the message picture or WinCC ON/OFF (struck-out message), a status is no longer available. With this type of message supplementary values are transferred with the event ID and these values contain the status information. Since the message is always of the type "incoming" here, it can only be indicated that a message of this type was here. The user must then look in the diagnostics buffer of the CPU himself to find out the reason for the message.

Below is the assignment of the organization blocks in STEP 7 to the individual group messages. This list does not presume to be complete. It is rather an indication of the possible causes. The user has to find the associated detailed information in the diagnostics buffer of the CPU based on the time stamp of the message concerned.


Detailed information in the CPU

AS fault synchronous

OB121, OB122

AS fault asynchronous

All OB8x

Module fault

OB82, OB83, OB86

Stop/abort fault

Stop and abort events direct

H/F system fault

OB71, OB72

Communications fault


Fault in CP/FM module

CPs and FMs direct to WinCC

BPC, Basic Process Control, Wizard, IC message

 Entry ID:6691096   Date:2005-09-08 
I regard this helpfulas not helpful                                 
My Documentation Manager 
Support Request
To this entry
Create PDF 
Send to a friend
Compatibility tool 
Online Help
Guided Tour