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?
Generating a new time stamp despite identical operator messages
Part number:

QUESTION:
Why are identical operator messages generated with a new time stamp?

ANSWER:
You create messages in message class "Operator messages" with the MESSAGE and ALARM_8P blocks. If there is a "HIGH" signal permanently at the message input of the block, the associated message is generated again with a new time stamp as soon as another message input receives a "HIGH" signal. This is a system property of the message class "Operator messages".

The message class "Operator messages" is defined as follows in WinCC:

  • Messages without "gone" state
  • Messages without acknowledgment

WinCC behavior:
Each "HIGH" state of the block is entered in the operator activities log, as soon as a message is sent from the MESSAGE or ALARM_8P block through a 1/0 or 0/1 transition at any block input.

  • A change in WinCC is not possible because of the missing "going" message.
    Example:
    Operation via an I/O field.
  • A change in the AS block is not possible because neither the message class nor the WinCC acknowledgment behavior is known to the block algorithm.

Remedy:
Provide the input concerned with pulses when using the MESSAGE or ALARM_8P block for operator messages. A permanent "HIGH" signal is not permissible in this case.

 Entry ID:822508   Date:1999-04-26 
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