Siemens Industry Online Support - Automation Service, Automation Support, Simatic Service, Simatic Support, Technical Support, Technical Consulting

S7-300 CPU 31x -- Configuring and programming communication -- Using communication blocks

	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 Mode 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 can 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 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"?

Part number:

Description
This access is possible with the 31x-2 DP CPUs that can be operated as I slaves. For this you parameterize the 31x-2 DP CPU as an intelligent DP slave and connect it to the PROFIBUS DP. You do this in the Properties of the DP interface.

Fig. 01: Changing the parameters of the DP interface

You then select the "Configuration" tab and configure the I/O configuration for the DP communication.

Examples of how to configure and parameterize a master-slave connection in STEP 7 between two S7 controllers are available in the entries below.

Entry ID: 6518822, if both stations are in the same STEP 7 project.
Entry ID: 19449428, if both stations are in separate STEP 7 projects.

A sample application for S7 basic communication with I_PUT and I_GET is available in Entry ID: 20987910.

Note
The S7 CPU configured as I slave does not necessarily have to be active. It can also be configured as passive node, i.e. the Test, Commissioning, Routing parameter can likewise remain disabled.

When programming, note that you must specify a logical address (diagnostics address or I/O address) for the IOID B#16#54 parameter and for LADDR when calling SFC 72/73.

Entry ID:1020634

Date:2010-12-08

I regard this article....

as helpful

as not helpful

Copy link

Suggestion for the entry

Send to a friend