show the entry list
ET 200S (standard modules) -- Configuring and programming communication -- Using communication blocks
How in WinAC MP 2008 do you program data transfer with the ET200S 1SI module for the 4-byte or 8-byte communication type?
Which CPU can you operate as a PROFINET I device?
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?
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 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 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 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?
What should you watch out for when connecting a SIMATIC HMI device configured with WinCC flexible ES to a SIMATIC ET 200 CPU?
"Report System Errors" function can be used with ET 200S CPU from firmware version V2.1
Using the SFB75 (send alarm to the DP master) on an ET 200S CPU
"Report System Errors" function can be used with ET 200S CPU from firmware version V2.1
Part number:

QUESTION:  
Why can't I load the function block (FB49), that has been created with the Report System Errors function, into the ET 200S CPU?

ANSWER:  
In the HW Config, the menu item Options > Report System Errors offers two options for creating a diagnostics block. If OB82 is in the OB Configuration tab, then the resulting FB49 (default setting in the "General" tab) contains SFC13 calls. This FB49 cannot then be loaded into the CPU, because the SFC13 is not in the CPU.

SFC13 "DPNRM_DG" is not included in the delivery package of the system blocks, because the ET 200S CPUs up to and including firmware version V2.0 do not have a DP master functionality.

Therefore you should exclude the OB82 for creating the FB 49. Create a separate block for the diagnostics (OB82) of the central ET 200S modules of the CPU.

Note:
Information on the structure of the diagnostics data is available in chapter 7 "Commissioning and Diagnostics" of the manual "ET 200S IM 151-7 CPU Interface Module" in Entry ID: 12714722.


 Entry ID:19378840   Date:2004-09-01 
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