Siemens S7-300 appendix Detailed Information

Communication

3.2 Communication services

The following table provides you with an overview of the system and standard functions for SIMATIC, whose functionality must be implemented by other functions when converting from PROFIBUS DP to PROFINET IO.

Table 3-7	System and Standard Functions in PROFIBUS DP that must be Implemented with
	Different Functions in PROFINET IO
Blocks		PROFINET IO	PROFIBUS DP
SFC55 (write dynamic		No	Yes
parameters)		(implement with SFB53)
SFC56 (write predefined		No	Yes
parameters)		(implement with SFB81 and
		SFB53)
SFC57 (assign parameters to		No	Yes
module)		(implement with SFB81 and
		SFB53)

You cannot use the following SIMATIC system and standard functions with PROFINET IO:

•SFC7 (trigger hardware interrupt on DP master)

•SFC11 (synchronize groups of DP slaves)

•SFC12 (deactivate and activate DP slaves)

•SFC72 (read data from a communication partner within local S7 station)

•SFC73 (write data to a communication partner within local S7 station)

•SFC74 (abort an existing connection to a communication partner within local S7 station)

Comparison of the Organization Blocks of PROFINET IO and PROFIBUS DP

Here, there are changes in OBs 83 and 86 as shown in the table below.

Table 3-8	OBs in PROFINET IO and PROFIBUS DP
Blocks		PROFINET IO	PROFIBUS DP
OB83 (removing and inserting		Also possible with an S7-300,	With an S7-300 not possible
modules and submodules		new error information	Removing and inserting during
during operation)			operation is reported by slaves
			added using a GSD file by
			means of a diagnostic interrupt;
			in other words OB82.
			With S7 slaves, OB86 is called
			due to the station failure.
OB86 (rack failure)		New error information	Unchanged

Detailed Information

For detailed descriptions of the individual blocks, refer to the manual System Software for S7-300/400 System and Standard Functions.

3-22	CPU 31xC and CPU 31x, Technical data
	Manual, Edition 08/2004, A5E00105475-05