show the entry list
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?
S7-300 CPU 31x -- Configuring and programming communication -- Using communication blocks
What is the volume of data that you can transfer with function blocks FB34 "GET_E" and FB35 "PUT_E"?
How do you cyclically read out the 8 channels of the FM 350-2 counter module as quickly as possible?
How do you read out the IP address of the S7-300 CPU in the user program at runtime?
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)?
Which security modules can be reached with SOFTNET Security Client V4 over a secure IPsec tunnel connection?
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 do you implement chronological messaging with S7-300 CPUs and WinCC?
How do you program communication blocks FB14 "GET" and FB15 "PUT" for data exchange in the S7 program of an S7-300 CPU?
How can you read out diagnostics data from a SIRIUS 3RK3 modular safety system using a S7-300/400 CPU?
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 configure a specified and an unspecified S7 connection for data exchange between S7-300 and/or S7-400 by way of Industrial Ethernet CPs?
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 communication blocks FB12 "BSEND" and FB13 "BRCV" for data exchange in the S7 program of an S7-300 CPU?
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 establish OPEN MODBUS / TCP communication from a SIMATIC S7 and where can you find further information?
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 does data communication work between S7-300/S7- 400 and S7-200 via MPI using S7 basic communication?
How great is data consistency in the PUT and GET S7 communication functions for the individual S7-300 CPUs and C7 complete devices?
How can you access via PROFIBUS DP another CPU, which is connected to the PROFIBUS DP as a slave, from a DP master using basic communication with SFC72 "I_GET" and SFC73 "I_PUT"?
How can you access consistent data without SFC14/15 as part of the process image?
How do you implement chronological messaging with S7-300 CPUs and WinCC?
Part number:

Instructions:
This entry shows you how to implement chronological messaging with an S7-300 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 sent to the WinCC station. The WinCC station doesn't need to poll the PLC. This significantly reduces the bus load. There are basically two types of message in STEP 7:

  1. Symbol-related messages
  2. Block-related messages

You can configure only block-related messages for an S7-300 CPU. These block-related messages are created by the STEP 7 program with the aid of the system message blocks. 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. The system message blocks SFC17 (ALARM_SQ), SFC18 (ALARM_S), SFC107 (ALARM_DQ) and SFC108 (ALARM_D) can be used in an S7-300 CPU (from CPU 314)for block-related messages. In contrast to ALARM_S/SQ, ALARM_D/DQ offers possibilities for managing your system resources; otherwise, they are identical. The S7-312 and S7-313 CPUs do not support these system message blocks!

More information:

  • Manual "SIMATIC S7-300 CPU 31xC and CPU 31x, Technical Data"
    This provides detailed information about the performance data of the available alarm processes of a CPU - Entry ID 12996906
  • Manual "Operation List CPU 31xC, CPU 31x, IM 151-7 CPU, IM 154-8 CPU, BM 147-1 CPU, BM 147-2 CPU"
    This provides detailed information about available system functions and system function blocks for creating CPU messages - Entry ID 13206730.
  • STEP 7 Online Help
    You can find detailed information about alarm processes, alarm types and system alarm blocks in the STEP 7 Online Help under "Configuring Messages". You can obtain detailed information if you install the block in the program and press F1.

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 is a description of how to configure block-related messaging.  

Configuring block-related messages
Here we present block-related messaging using the
system message block SFC17 (ALARM_SQ). The procedure using the system message block is essentially identical. Two messages are configured in one function block.
 
No. Procedure
1 Copy SFC17 (ALARM_SQ) into the current project
In the SIMATIC Manager you open the standard library via "File > Open... > Standard Library". Select the system message block SFC17 (ALARM_SQ). It is located in the directory "Standard Library > System Function Blocks > Blocks". Copy the system message block SFC17 into the project.
2 Create a message-compatible block
  • Insert a new function block, e.g. "FB1" into the STEP 7 project. The language used is STL.
  • Open the function block "FB1".
  • Create the following input variables:
    EV_ID1 (DWORD)
    EV_ID2 (DWORD)
    SIG1 (BOOL)
    SIG2 (BOOL)
    SD1 (WORD)
    SD2 (WORD)
  • Create the following output variables:
    RET_VAL1 (INT)
    RET_VAL2 (INT)
  • Create the following temporary variable
    RET_iVal (INT)
  • Open the "Object Properties" dialog of input "EV_ID1". Assign the following attributes:
    S7_a_type = alarm_s
    S7_server = alarm_archiv


    Fig. 01
     
     
  • Repeat the procedure of the previous step for input "EV_ID2".
  • Select the system message block SFC17 (ALARM_SQ) in the program part. Connect the parameters of the system message block with the corresponding inputs/outputs of the function block.


    Fig. 02
     

    Note:
    The "ID" parameter is permanently set with the value "W#16#EEEE".
    The SIG parameter triggers the message.
    The EV_ID parameter receives the message number generated by the system.
    With the SD parameter you can configure a message-associated value.
    The RET_VAL parameter contains error information.
     
  • Call SFC17 a second time, because you can only monitor one message variable with this block. Make the relevant settings as described in the point above.
  • Save the function block FB1 and close the editor.
3 Configure standard messages
In the SIMATIC Manager you mark the function block "FB1". In the pop-up menu you call the command "Special Object Properties > Messages...".
The Message Configuration dialog opens.


Fig. 03
 

Specify the message text for the messages EV_ID1 and EV_ID2.

Note:
It is also possible to configure the message texts in multiple languages. The display language currently selected is shown in the "Message Configuration" dialog. You must configure the message texts for all those languages that will be used later for WinCC Runtime. For this you change the standard language in the SIMATIC Manager with the menu command "Options > Display Language..." and repeat message configuration for each language separately.

4 Call message-compatible block in the program
You must call function block FB1 in your program. For this you open the organization block OB1 and enter the following code:


Fig. 04
 

Warning:
The IDs for the messages are generated automatically by STEP 7. You must not change these IDs!

Save the organization block OB1 and close the editor.

5 Configure block-related messages
After incorporating the message-compatible block you can change the message texts. For example, you can extend the message text by adding the actual name of the measuring point. For this you mark the instance data block, e.g. "DB1" in the SIMATIC Manager. In the pop-up menu you call the command "Special Object Properties > Messages...".
The Message Configuration dialog opens. Change the message text accordingly for each relevant language.


Fig. 05
 

6 Load the program into the PLC
Load the program into the PLC.
7 Compile the OS
"OS Compile" creates the messages in WinCC. In earlier versions the procedure was also done with "Mapping" or "AS/OS Connection Data > Transfer".

Requirements:
The PLC's CPU and the OS must be networked. There must be at least one common network connection in NetPro.


Fig. 06
 

Start the OS compilation procedure. In the SIMATIC Manager you select the OS and then in the associated pop-up menu you select "Compile".


Fig. 07
 

A wizard takes you through multiple dialogs. Here you can make various setting for compiling the OS. You must select which PLC program is assigned to which OS and which connection is to be used.

Using the "Back" and "Next" buttons you can navigate in the wizard's settings mask. With the "Finish" button you get a summary of the compilation procedure displayed. Start the compilation procedure with the "Compile" button.

8 Load the OS
Load the program into the OS.
9 Test the messages at WinCC Runtime
Start WinCC Runtime. Trigger the messages using the variables table. The messages are displayed in the alarm window of WinCC and can be acknowledged where necessary. You can diagnose the messages alternatively with the STEP 7 program "CPU Messaging".


Fig. 08
 

This entry has been created with WinCC V6.0 SP4  and STEP 7 V5.3 SP2.

 Entry ID:23730649   Date:2007-09-18 
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