show the entry list
S7-400 CPU 41x -- Configuring and programming communication -- Using communication blocks
How do you enable the ad-hoc mode when you call the TRCV instruction?
How do you use the blocks for MODBUS/TCP communication over the integrated PROFINET interface of the S7-300 and S7-400 CPUs and IM151-8 PN/DP CPU in STEP 7 Professional (TIA Portal)?
How do you establish a redundant MODBUS/TCP communication over the integrated PROFINET interface of a CPU 41x-H in STEP 7 V5.5?
What is the difference between the initialization and runtime parameters on the blocks for Modbus TCP?
Why is the status value A090 (hex) output for Modbus TCP although you have entered the correct license?
What are the differences between the licensed version and the downloadable demo version of the blocks for Modbus TCP?
Why is the value A083 (hex) output permanently at the STATUS output parameter of the block for Modbus TCP when the ENQ_ENR=true input parameter has been set?
Which blocks for Modbus TCP can you rename or re-wire when the block numbers of the Modbus blocks are already being used in the user program?
How can you read out diagnostics data from a SIRIUS 3RK3 modular safety system using a S7-300/400 CPU?
Which communication options are there in SIMATIC S7?
How does data communication work between S7-300/S7- 400 and S7-200 via MPI using S7 basic communication?
Consistent data in S7-400, summary of mechanisms
Which ports are released for Modbus/TCP communication and how many Modbus clients can communicate with a SIMATIC S7 CPU as Modbus server?
How do you implement chronological messaging with S7-400 CPUs and WinCC?
How do you configure a specified and an unspecified S7 connection for data exchange between S7-300 and/or S7-400 by way of Industrial Ethernet CPs?
How can you establish OPEN MODBUS / TCP communication from a SIMATIC S7 and where can you find further information?
How do you use WinCC flexible to transfer a project to an operator panel via S7 routing?
What restrictions are there for active jobs when communicating with SFC 58 / SFC 59 and SFB 52 / SFB 53 via PROFIBUS DP and PROFINET IO?
How do you program the communication blocks FB63 "TSEND", FB64 "TRECV", FB65 "TCON" and FB66 "TDISCON" in order to use the ISO-on-TCP protocol for data exchange by way of the integrated PROFINET interface of a CPU or by way of the CP443-1 Advanced?
How do you program the communication blocks FB63 "TSEND", FB64 "TRCV", FB65 "TCON" and FB66 "TDISCON" in order to use the TCP protocol for data exchange by means of the integrated PROFINET interface of an S7-300 or S7-400 CPU?
How do you program the communication blocks FB67 "TUSEND", FB68 "TURCV", FB65 "TCON" and FB66 "TDISCON" in order to use the UDP protocol for data exchange by means of the integrated PROFINET interface of a CPU?
How can you access consistent data without SFC14/15 as part of the process image?
How great is data consistency in the PUT and GET S7 communication functions for the individual S7-400 CPUs?
WinCC -- Configuring alarms and messages -- Configuring chronologically correct messages
How are message classes used if WinCC is integrated in the STEP 7 project?
How are message texts used if WinCC is integrated in the STEP 7 project?
Why are messages displayed in WinCC offset by one hour (plus 1 hour)?
How do you implement chronological messaging with S7-400 CPUs and WinCC?
How do you implement chronological messaging with S7-300 CPUs and WinCC?
How can you configure the "Report System Error" functionality of an S7 station to be multilingual?
How can you report S7 system errors in WinCC?
Which additional options are required to display the comments of the STEP 7 symbol table for "chronological reporting"?
How should you proceed when "chronological reporting" is to be used, but WinCC has been installed before STEP 7?
How can you influence the assignment of message numbers?
How do you implement chronological messaging with S7-400 CPUs and WinCC?
Part number:

Instructions
This entry shows you how to implement chronological messaging with an S7-400 CPU and WinCC. Chronological messaging means that the messages are sent from the PLC to the WinCC station. When they are created in the PLC, the messages are given a time stamp and then sent to the WinCC station. WinCC does not poll the PLC, which significantly reduces the bus load. The following two basic types of message and their configuration are demonstrated in the attached PDF file:
  1. Symbol-related messages
    Symbol-related messages can only be generated by CPUs of the S7-400 series. The messages are triggered asynchronously to the program.
  2. Block-related messages
    Block-related messages can be generated by CPUs of the S7-300 and S7-400 series.
    The block-related messages are created by the STEP 7 program using the system message blocks (e.g. ALARM_8P). The message is sent as soon as the STEP 7 program calls a system message block and the conditions for sending a message are fulfilled. The messages are triggered synchronously to the program.

More information

  • Reference manual "Programmable Logic Controller S7-400 CPU Data"
    This gives you detailed information on the available message procedures of a CPU. This documentation is part of the documentation package 6ES7498-8AA03-8AA0. The manual is available for downloading in Entry ID 19538001.
  • Manual "Operation List S7-400 CPU 412, 414, 416, 417"
    This gives you detailed information on available system functions and system function blocks for creating CPU messages. This documentation is part of the documentation package 6ES7498-8AA04-8AN0. The manual is available for downloading in Entry ID 1117645.
  • STEP 7 Online Help
    Detailed information on alarm processes, alarm types and system alarm blocks is available in the STEP 7 Online Help.

Requirements

  • The WinCC component "AS-OS Engineering" is installed.
    You can select this component when doing a user-defined setup of WinCC. Please use the following installation sequence:
     
    1. STEP 7
    2. WinCC with the "AS-OS Engineering" component

    Entry ID 22272911 includes a description of how to retro-install the "AS-OS Engineering" component.
     

  • The WinCC project is integrated in the STEP 7 project.
    Entry ID 11841504 contains information on how to integrate a WinCC project in STEP 7.
     
  • The "Alarm Logging Runtime" is enabled in the startup list in the "Computer Properties" dialog of the WinCC project.

Below we show you how to configure symbol-related and block-related messages.

WinCC_ZeitfolgeRichtigMeldenS7400 ( 586 KB )

This entry has been created with WinCC V6.0 SP4 and STEP 7 V5.3 SP2. The entry was also tested with WinCC V7.0 and STEP 7 V5.4 SP4.

Keywords
GMP, Pharma, Life Science, Validation, FDA 21 CFR Part 11

 Entry ID:23730697   Date:2009-01-14 
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