show the entry list
Industrial Ethernet S7-300/400 CPs -- Configuring and programming communication -- Using communication blocks
How do you copy the CFC chart "Modbus" from the sample project for OPEN MODBUS / TCP into your user project?
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?
How is data with variable message length transferred via the TCP protocol and received by an S7-300 station via the Industrial Ethernet CP?
How do you program the function blocks FB14 "GET" and FB15 "PUT" in the S7 program of the S7-300 in order to transfer more than 160 bytes of data?
Where can you find sample programs and documentation for communication from SIMATIC S5 modules to SIMATIC S7 modules via Industrial Ethernet using the UDP protocol?
Where can you find sample programs and documentation for communication from SIMATIC S5 modules to SIMATIC S7 modules via Industrial Ethernet using the TCP protocol?
Where can you find sample programs and documentation for communication from SIMATIC S5 modules to SIMATIC S7 modules via Industrial Ethernet using the ISO transport protocol?
How do you program the FC10 "AG_CNTRL"?
Which commands (CMD) of the FC10 "AG_CNTRL" are supported by the IE CPs?
How many communication jobs may be used simultaneously in an S7-300 CPU for S7 communication via a CP343-1?
Which ports are released for Modbus/TCP communication and how many Modbus clients can communicate with a SIMATIC S7 CPU as Modbus server?
Notes on using an instance for multiple connection IDs
Internal call of FC5 (AG_SEND) with FTP client blocks (FC 40-44) for the CP343-1 IT (6GK7 343-1GX11-0XE0)
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 communication blocks FC11 and FC12 for the PROFINET IO device?
Block calls for communications processors in multiple runtime layers
Changing the input parameter of the user blocks "AG_SEND" and "AG_RECV" during the runtime of a job
What should you watch out for if you transfer variables with the data type "REAL" when calling the communication blocks FC5/50 "AG_SEND/AG_LSEND" and FC6/60 "AG_RCV/AG_LRCV"?
What should you pay attention to when using the communication blocks FC53 "AG_SSEND" and FC63 "AG_SRECV"?
What points do you need to remember when calling communication blocks FC5/50 and FC6/60 in the STEP 7 user program of the CPU?
How do you program communication blocks FC11 and FC12 for the PROFINET IO controller?
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 FC50 and FC60?
Error STATUS "0x7000" on function block FC6 / FC60 (AG_SEND) with Send/Receive communication on the S7-400 controller
How do you program the communication blocks FC5 and FC6?
Sample program: S7 communication with the blocks SFB14 ("GET") and SFB15 ("PUT") with S7-400
Sample Program: S7 Communication with blocks FB14 ("GET") und FB15 ("PUT") of the CPU 317-2PN/DP
How do you program communication blocks FB8 "USEND" and FB9 "URCV" for data exchange on the S7-300?
"STATUS = 27" (0x001B) with the loadable S7 communication on the S7-300
How do you program communication blocks FB14 "GET" and FB15 "PUT" for data exchange in the S7 program of an S7-300 CPU?
How do you program communication blocks FB12 "BSEND" and FB13 "BRCV" for data exchange in the S7 program of an S7-300 CPU?
Repeating the "BSEND" job (SFB12) when the "BRCV" block (SFB13) is in the "disabled" state ("EN_R = 0")
What should you pay attention to when using the communication blocks FC53 "AG_SSEND" and FC63 "AG_SRECV"?
Part number:

Configuration Notes:
The S5-compatible communication is the most frequently used communications service for transferring user data via Industrial Ethernet CPs. In addition, there are communication blocks that have to be called in the S7 program of the CPU.

The communication block FC50 "AG_LSEND" is used for sending data and communication block FC60 "AG_LRECV" is used for receiving data. These communication blocks are used for data exchange via the following connection types:

  • ISO-on-TCP connection (RFC1006)
  • TCP connection
  • UDP connection
  • ISO Transport

From CP443-1EX20 (6GK7443-1EX20-0XE0) onwards that are additional communication blocks for data exchange via the above-mentioned connection types:

  • FC53 "AG_SEND"
  • FC63 "AG_SRECV"

This is a more powerful communications option. Compared with the S5-compatible communication with FC50 "AG_LSEND" and FC60 "AG_LRECV", there is an increase in performance by a factor of up to 3 depending on the plant constellation.

Configuration of the S5-compatible communication with FC53 "AG_SSEND" and FC63 "AG_SRECV":
For S5-compatible communication via Industrial Ethernet, you can use the following operating modes in CP443-1EX20 (6GK7443-1EX20-0XE0) onwards:

  • Send/Recv
  • SPEED Send/Recv
  • Fetch Passive
  • Write Passive

The "Send/Recv" operating mode is enable by default. To use the faster communication with FC53 "AG_SSEND" and FC63 "AG-SRECV" you must select the "SPEED Send/Recv" mode in the "Options" tab of the Properties dialog of the communication connection configured.


Fig. 01: Properties dialog of the communication connect - "Options" tab

Furthermore, in the STEP 7 Hardware Configuration, the extended address range must be enabled in the Properties dialog of the Industrial Ethernet CP. For this you open the Properties dialog of the Industrial Ethernet CP, select the "Addresses" tab and enable the option "Address setting for LOCK/UNLOCK with FETCH/WRITE, SPEED Send/Receive". Now the module occupies 64 peripheral input addresses and 64 output addresses.


Fig. 02: Properties dialog of the Industrial Ethernet CP -> "Addresses" tab

Note:
Operating modes Send/Recv and SPEED Send/Recv use the same resources pool on the IE CP. An IE CP of SIMATIC S7-400 supports 64 connections for S5-compatible communication. You can define how many of these connections are to operated with the Send/Recv and SPEED Send/Recv modes. The only important thing here is that the CPU has enough free S7 connection resources.

Maximum length of the user data to be transferred:
If you are using the SPEED Send/Recv mode, you can transfer a maximum of 1452 bytes of user data. User data transfer with the Send/Recv mode depends on the connection type used.
 
Connection type Data length for Send/Recv with FC50/60 Data length for SPEED Send/Recv with FC53/63
ISO-on-TCP 8192 bytes 1452 bytes
TCP 8192 bytes 1452 bytes
UDP 8192 bytes 1452 bytes
ISO Transport 2048 bytes 1452 bytes

Occupied connection resources:
The communication processors support communication connections always in parallel for S5-compatible communication and S7 communication. For one configured connection, only one resource is occupied in the IE CP for S5-compatible communication. The number of S7 connections supported in the CPU does not depend on this.

This changes if you configure a communication connection with the SPEED Send/Recv mode. In this case, one Send/Recv resource and one S7 connection resource per connection are occupied in the CP IE. In addition, one S7 connection resource is likewise occupied in the CPU.
 
Connection resource Send/Recv mode SPEED Send/Recv mode
Send/Recv connection resource in the IE CP 1 1
S7 connection resource in the IE CP 0 1
S7 connection resource in the CPU 0 1

Length of the data buffer for FC63 "AG_SRECV" with TCP connections:
Die folgende Vorschrift gilt nur für TCP-Verbindungen.
When receiving data packages, the receive buffer must always be called with the maximum data length of 1452 bytes. This rule also applies when you are receiving just a few bytes.

Reason:
In the case of TCP connections with the SPEED Send/Recv mode, the transfer of data packages from the LAN (local area network) to the user program is structured so that always the number of bytes actually available are transferred to the CPU. Therefore, if an IE CP receives a data package of 10 bytes every 5s, for example, the data is first collected in the IE CP. If the user program then calls an FC63 "AG_SRECV" on the relevant connection after 20s, all the bytes collected until then are transferred all at once to the CPU. In the case described, this would be 40 bytes (4 * 10 bytes). In the case of a TCP connection, it is not possible to provide information about how many data packages constitute the data received and where the message limits lie. This can only be achieved by structuring the user data.

 Entry ID:28710236   Date:2008-03-20 
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