Programming With The SEND/RECEIVE Interface: Simatic Net

Programming with the SEND/RECEIVE Interface
SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.1999
File No.: 7E_SRSS.1
Contents Page
SEND-RECEIVE Interface in the CPU...................................................................................... 2

CPU Cycle and Transmission Time.......................................................................................... 3
Data Quantities per Job ....................................................................................................... 4
User Data Area in the CPU....................................................................................................... 5
Programming the SEND/RECEIVE Interface........................................................................... 6
Typical Execution Sequence for the FCs in the CPU Cycle...................................................... 7
The FCs..................................................................................................................................... 8
Entering the FCs in the STEP 7 Library.................................................................................... 9
General Notes on the FCs.......................................................................................................... 10
Reactions to Incorrect Address Entries..................................................................................... 11
FC AG_SEND/AG_LSEND...................................................................................................... 12
Explanation of the Formal Parameters....................................................................................... 13
Operation of the AG_SEND FC.................................................................................................. 15
Condition Codes of AG_SEND.................................................................................................. 16
FC AG_RECV/AG_LRECV ....................................................................................................... 19
Explanation of the Formal Parameters....................................................................................... 20
Operation of the AG_RECV FC.................................................................................................. 21
Condition Codes of AG_RECV.................................................................................................. 23
Job Header ............................................................................................................................... 26
Siemens AG Page 1 SEND/RECEIVE Interface

Training Center
SEND-RECEIVE Interface in the CPU
Ethernet station SIMATIC S7

CPU Ethernet CP
CP
CP
STEP
STEP77 database
user database
userprogram
program
User
Userdata
databuffer
buffer
User
Userdata
data
areas
areas
AG_SEND Send
Communication
connection
AG_RECV Receive
CPU cycle Transmission time

Date: 01.09.1999
File No.: 7E_SRSS.2
FCs The following FCs (functions) are available for handling communication via
configured connections:
• AG_SEND / AG_LSEND
This function passes the user data from the specified user data area
to the Ethernet CP for transmission.
• AG_RECV / AG_LRECV
This function puts the user data received into the user data area
specified in the call.
Note The information given here applies to both AG_SEND and

AG_LSEND and AG_RECV and AG_LRECV unless otherwise stated !
The diagram above illustrates this procedure: The user program uses the FCs
AG_SEND/ AG_LSEND and AG_RECV / AG LRECV to instruct the Ethernet
CP to send or receive data via the configured connection.
Data exchange Data is exchanged between CPU and Ethernet CP as dictated by the
S7 CPU <-> calls to the FCs AG_SEND and AG_RECV in the CPU program.
Ethernet CP
The Ethernet CP processes the Send and Receive jobs independently of the
CPU cycle and the transmission takes a certain amount of time. The interface
with the FCs in the user program is synchronized by means of
acknowledgements. There are two possibilities:
• The CPU cycle is faster than the transmission time.

• The CPU cycle is slower than the transmission time.

Training Center
CPU Cycle and Transmission Time
FC calls faster than the transmission time
FC calls slower than the transmission time

Date: 01.09.1999
File No.: 7E_SRSS.3
FC Calls Faster If an FC is called again in the user program before all the data has been
than the sent or received, the following happens at the FC interface:
Transmission Time
• AG_SEND:
No further job is accepted until the transmission of the data on the
connection has been acknowledged by the Ethernet station. During this
time, the user programm receives the message "job active" until the
Ethernet CP can accept the next job on the same connection.
• AG_RECV:
The job is acknowledged with the message “no data available yet" if
there is no received data on the Ethernet CP. The user program
receives this message in the CPU cycle until the Ethernet CP has
received all the data on the connection.
FC Calls Slower If an FC is called again after the data has been completely transferred or
than the received, the procedure is as follows at the FC interface:
Transmission Time
• AG_SEND:
The job is positively acknowledged. The Ethernet CP is ready to
receive a new send job.
• AG_RECV:
The job is acknowledged with “New data received” when the data has
been transferred to the user program. Following this, the FC call can be
repeated.

Training Center
Data Quantities per Job
The Ethernet CP can transfer the following quantities of
data per job via a connection
ISO ISO-on- TCP UDP

Transport TCP
Send 8192 bytes 8192 bytes 8192 bytes 2048 bytes
Receive 8192 bytes 8192 bytes 8192 bytes 2048 bytes
Note: With TCP you can only use the AG_LSEND and
AG_LRECV functions, regardless of the quantity of data to
be transferred.

Date: 01.09.1999
File No.: 7E_SRSS.4
Older CPs do not support transfer of more than 240 bytes of data.
Please read the product information for your CP.

Training Center
User Data Areas in the CPU
• Data block (DB)
• Process image
• Bit memory address area

Date: 01.09.1999
File No.: 7E_SRSS.5
Alternative Different data areas in the CPU can be used for communication via
data areas configured connections. Your choice of data area depends on the type of CPU
and the task involved. The alternatives are:
• Data block (DB):

Data blocks can be used for storing Send/Receive data.
• Process image:
This choice is only possible if continuous Send and Receive areas can
be reserved in the process image of the S7 CPU. The capacity may be
restricted by the capabilities of the CPU and by the number of central
signal modules.
• Bit memory address area:

The bit memory address area can be used, for example, if there is not
sufficient space in the process image because of the central signal
modules.

Training Center
Programming the SEND/RECEIVE Interface
Principle of job The user program triggers the transfer of the user data areas
and data transfer by means of FC calls and monitors the execution by evaluating
the condition code bits returned by the FCs. The parameters
assigned to the FCs when they are called include:
• Connection number (ID);
• Location of the user data area in the CPU.
Purpose of the FCs Calling FC blocks results in the following action:
• The user data area is passed to the Ethernet CP

or accepted from the Ethernet CP.
• Positive or negative confirmation of execution of the job

is indicated in the status word.

Date: 01.09.1999
File No.: 7E_SRSS.6
Connections Program the SEND-RECEIVE interface in the user program as follows:
• Use the following FCs for transferring data via configured

connections:
- AG_SEND for passing the user data area to the Ethernet CP;
- AG_RECV for entering the data received from the Ethernet CP into
the user data area;
• Evaluate the condition codes issued by the FCs:
- For AG_SEND these are the parameters DONE, ERROR and

STATUS, and
- For AG_RECV the parameters NDR, ERROR and STATUS
Note You must use the configured connection numbers (IDs) when programming.

Training Center
Typical Execution Sequence for the FCs in the
CPU Cycle
Read PII Read in data received
via the connection
OB User program
AG_RECV
Connection
AG_RECV
Connection
AG_SEND
AG_RECV
Connection
AG_SEND
Pass Send data to the

AG_SEND connection
Write PIQ Key: CPU cycle

Hatching/shading shows which connections
and FCs go together

Date: 01.09.1999
File No.: 7E_SRSS.7
We can observe the following:
• The user program, which can consist of any number of blocks (OBs,
FBs or FCs), accesses several connections.
• The user program can send data via connections by means of

AG_SEND calls at any point (event-driven and program-controlled
execution).
• The user program can accept data received via connections by means
of AG_RECV calls at any point in the CPU cycle.
Note: The FCs can be called more than once in one cycle for the same connection.

Training Center
The FCs
The FCs are supplied with the NCM S7-Ethernet configuring software.
The following list shows the block numbers used for these FCs on delivery.
You can change these block numbers if you wish.
Block number FC type Purpose

5 AG_SEND Send data <= 240 bytes
6 AG_RECV Receive data <= 240 bytes
50 AG_LSEND Send data, max 8192 bytes
60 AG_LRECV Receive data, max 8192 bytes

Date: 01.09.1999
File No.: 7E_SRSS.8
Note For TCP connections you can only use the FCs AG_LSEND and AG_LRECV,
regardless of the amount of data to be transferred.

Training Center
Entering FCs in the STEP 7 Library
1. Open the library in the SIMATIC Manager with File >Open >
Library.
Result:
The currently existing libraries are displayed.
If the entry “SIMATIC NET CP” is not present, proceed as follows:
2. Search for the directory “Simnetcp” in

SIEMENS\STEP 7\S7libs\simaticn
and select or open the file CP.S7L in it.
Result:
The library “SIMATIC NET CP” is now created in the STEP 7 library.

Date: 01.09.1999
File No.: 7E_SRSS.9
In order to be able to use the FCs for writing your user program, follow the
procedure outlined above.

Training Center
General Notes on the FCs
• Specification of the CP address

- LADDR parameter
- Starting address of module from hardware configuration table
- Slot-oriented address assignment for Ethernet CP as for analog
modules
• Specification of the data area in the CPU
- Address and length
- Max. length 8192 bytes, depending on the type of block used

Date: 01.09.1999
File No.: 7E_SRSS.10
Specifying the When you call an FC, you assign the starting address of the CP module
CP Address to the LADDR parameter. You can obtain the starting address of the Ethernet CP
module from the hardware configuration.
Ascertaining the The module starting address can be determined from the slot-oriented
CP Address address assignment for signal modules. The rules for analog modules apply to
the Ethernet CP.
When the CP is configured with the STEP 7 hardware configuration tool, the
starting address of the module appears in the configuration table.
Specifying the When you call an FC you supply it with the address and length of the data
Data Area in the area in the CPU. Please note that the maximum length of the data area
CPU depends on the type of FC used.
FC Output On complete restart/restart of the Ethernet CP (e.g. when the switch is

Parameters on operated), the output parameters of the FC are reset as follows:
CP Startup
• DONE = 0
• NDR = 0
• ERROR = 0
• STATUS = 8180H for AG_RECV and 8181H for AG_SEND

Training Center
Reactions to Incorrect Address Entries
Error Response
CP address indicates a non-existent CPU remains in Stop mode due to a system error.
CP module or digital module.
CP address indicates a module with Possible error codes in STATUS:

analog I/Os. 8184H System error
80B0H Data record unknown to module.
80C0H Data record cannot be read.
80C3H Resource (memory) occupied.
80D2H Incorrect logical base address.

Date: 01.09.1999
If the S7 CPU cannot communicate with the Ethernet CP at the specified module
starting address, the result is as shown above.
Note:
The SIMATIC S7 addresses the Ethernet CP like an analog module. If an

incorrect address is specified, this can result in error codes which are not derived
from error messages from the FCs themselves.

Training Center
FC AG_SEND / AG_LSEND
Call interface in
LAD
BOOL ACT DONE BOOL
INT ID ERROR BOOL

WORD LADDR STATUS WORD
ANY SEND
INT LEN
Example in STL
STL Explanation
call fc 5 //AG-SEND FC call

ACT := M 10.0
ID := MB 11
LADDR := W#16#0100 =LADDR 256 dec. in hardware configuration
SEND := P#db99.dbx10.0 byte 240
LEN := MW 12
DONE := M 10.0
ERROR := M 10.7
STATUS := MW 14

Date: 01.09.1999
Purpose of The FC AG_SEND passes on data to the Ethernet CP for transmission

the FC via a configured connection.
The data area specified can be an area in the process image, a bit memory
address area or a data block area.
Successful execution is signalled when the complete user data area has been
transmitted via Ethernet.

Training Center
Explanation of the Formal Parameters (1)
Parameter Declaration Type Poss. values Remarks
ACT INPUT BOOL 0,1 If ACT = 1, LEN bytes from the transport
data area specified with the SEND
parameter are sent.
If ACT = 0, the DONE, ERROR and

STATUS codes are updated.
ID INPUT INT 1,2...64(S7-400) The ID parameter specifies the connection
1,2...16(S7-300) number of the transport connection.
LADDR INPUT WORD Module starting address
When the CP is configured with the STEP 7

hardware configuration tool, the module
starting address appears in the configuration
table. Enter this address here.
SEND INPUT ANY Address and length of transport data area
This may be:
- Process image area
- Bit memory address area
- Data block area

Date: 01.09.1999

Training Center
LEN INPUT INT 1..8192 bytes for Number of bytes from the transport data
ISO and area to be sent with the job. The number can
ISO-on-TCP be from 1 to the length specified for the
1..2048 bytes for SEND parameter.
UDP
DONE OUTPUT BOOL 0: Job in This parameter indicates whether or not the
progress job has been completed without errors. As
1: Job long as DONE=0, no new job can be started.
completed The CP sets DONE to 0 when it accepts a
job.
For meanings in conjunction with the
ERROR and STATUS parameters, see the
Condition Codes table.
ERROR OUTPUT BOOL 0: - Error code

1: Error For the meaning in conjunction with the
DONE and STATUS parameters see the
STATUS OUTPUT WORD See Status code
Condition Codes For the meaning in conjunction with the
table DONE and ERROR parameters see the

Date: 01.09.1999

Training Center
Operation of the AG_SEND FC
User program (CPU cycle) Ethernet CP Communication partner
Supply AG_SEND
ACT = 0
AG_SEND Startup phase
0, 1, 8181 1)
AG_SEND
1, 0, 0000 1)
Supply AG_SEND
with data ‘X’
ACT = 1
AG_SEND
0, 0, 8181 1)
Supply AG_SEND
ACT = 0 Transmission of ‘X’
via Ethernet
AG_SEND active Key:
0, 0, 8181 1) 1) Parameter transfer
DONE, ERROR, STATUS
AG_SEND
1, 0, 0000 1)
Time Time Time

Date: 01.09.1999
The diagram above shows the normal execution sequence of a data transfer
initiated by AG_SEND in the user program.
The Ethernet CP acknowledges every AG_SEND job in the user program by

setting the DONE, ERROR and STATUS output parameters.
The condition codes can be updated without issuing a new Send job by setting
the ACT parameter = 0.

Training Center
Condition Codes of AG_SEND (1)
DONE ERROR STATUS Meaning
1 0 0000H Job completed without errors.
This code is possible only with the S7-400.The FC was called
0 1 7000H
with ACT=0; the job has not yet been processed
0 0 8181H Job active.
0 1 8183H No configuration data or Transport service in Ethernet CP not yet
started.
0 1 8184H System error
0 1 8185H LEN parameter longer than SEND source area.
0 1 8186H ID parameter invalid, ID != 1,2...64.
0 1 8301H SAP not activated at destination station.
0 1 8302H No Receive resources at destination station, receiving station
cannot process received data fast enough or has not provided any
resources for receiving data.
0 1 8303H The SDA service (Send Data with Acknowledge) is not supported
by the destination station at this SAP (no SDA on Ethernet).
0 1 8304H Connection not established.

Date: 01.09.1999

Training Center
0 1 8311H Destination station not obtainable at the specified Ethernet
address.
0 1 8312H Ethernet error in CP.
0 1 8F22H Source area invalid, e.g. :
Area not present in DB
LEN parameter < 0
0 1 8F24H Range error when reading a parameter.
0 1 8F28H Alignment error when reading a parameter.
0 1 8F32H DB number in parameter too high.
0 1 8F33H DB number error.
0 1 8F3AH Area not loaded (DB).
0 1 8F42H Timeout when reading a parameter from the I/O area.
0 1 8F44H Address of parameter to be read disabled in access track.

0 1 8F7FH Internal error, e.g. illegal ANY reference
e.g. LEN parameter = 0.

Date: 01.09.1999

Training Center

0 1 8090H No module with this starting address or CPU in STOP.
0 1 8091H Module starting address not at double word boundary.

0 1 80B0H Data record unknown to module.
0 1 80B1H Destination area invalid
e.g. destination area > 240 bytes.
0 1 80B2H communication bus link between CPU and CP not established.
0 1 80C0H Data record cannot be read.
0 1 80C1H Specified data record currently being processed.
0 1 80C2H There are too many jobs pending.
0 1 80C3H Resources (memory) of CPU temporarily occupied.
0 1 80C4H Communication error.
0 1 80D2H Incorrect module starting address.

Date: 01.09.1999

Training Center
FC AG_RECV / AG_LRECV
Call interface in
LAD
BOOL
INT ID NDR
WORD BOOL
LADDR ERROR
ANY WORD
RECV STATUS
LEN INT
Example in STL
STL Explanation
call fc 6 //AG-RECV FC call

ID := DB 100.DBW 1
LADDR := W#16#0100
RECV := P#M 0.0 BYTE 100
NDR := DB 100.DBX 0.6
ERROR := DB 100.DBX 0.7
STATUS := DB 100.DBW 2
LEN := DB 100.DBW 4

Date: 01.09.1999
Purpose of The FC AG_RECV receives the data transferred via a configured

the FC connection from the Ethernet CP.
The data area specified as the data destination can be an area in the process
image, a bit memory address area or a data block area.
Successful execution is signalled when the data has been received from the
Ethernet CP.

Training Center

ID INPUT INT 1,2...16 The ID parameter specifies the connection
number of the transport connection.
LADDR INPUT WORD Starting address of module
When the CP is configured with the STEP 7

hardware configuration tool, the module
starting address appears in the configuration
table. Enter this address here.
RECV INPUT ANY Address and length of transport data area
This may be:

- Process image area
- Bit memory address area
- Data block area
LEN INPUT INT 1..8192 for ISO Number of bytes transferred from the
and ISO-on-TCP Ethernet CP to the transport data area.
1..2048 for UDP

Date: 01.09.1999

Training Center

NDR OUTPUT BOOL 0: - This parameter indicates whether new data
1: New data has been accepted.
For the meaning in conjunction with the
ERROR and STATUS parameters, see the
ERROR OUTPUT BOOL 0: - Error code
1: Error For the meaning in conjunction with the NDR
and STATUS parameters see the Condition
Codes table.
STATUS OUTPUT WORD See Condition Status code
Codes table For the meaning in conjunction with the NDR
and ERROR parameters see the Condition
Codes table.

Date: 01.09.1999

Training Center
Operation of the AG_RECV FC
User program (CPU cycle) Ethernet CP Communication partner
AG_RECV Transmission of ‘A’

0, 1, 8180 1) via Ethernet
in progress
AG_RECV
1, 0, 0000 1)
Accept/evaluate
received data ‘A’ Transmission of ‘B’
via Ethernet
AG_RECV in progress
0, 0, 8180 1)
AG_RECV
1, 0, 0000 1)
Accept/evaluate
received data ‘B’ Key:
Transmission of ‘C’ 1) Parameter transfer
via Ethernet NDR, ERROR, STATUS
AG_RECV
in progress
.
.
.
Time Time Time

Date: 01.09.1999
The diagram above shows the normal execution sequence for data acceptance
initiated by AG-RECV in the user program.
The Ethernet CP acknowledges every AG-RECV job in the user program by

setting the NDR, ERROR and STATUS output parameters.

Training Center
Condition Codes of AG_RECV (1)
NDR ERROR STATUS Meaning

1 0 0000H New data accepted.
0 0 8180H Data not yet present.
0 0 8181H Job active.
0 1 8183H No configuration data or ISO Transport service not yet started in
Ethernet CP.
0 1 8184H System error.
0 1 8185H Destination buffer (RECV) too small.
0 1 8186H ID parameter invalid, ID != 1,2...(16) 64.
0 1 8304H Connection not established.
0 1 8F23H Source area invalid, e.g.:
Area not present in DB.
0 1 8F25H Range error when writing a parameter.
0 1 8F29H Alignment error when writing a parameter.
0 1 8F30H Parameter in write-protected 1st active data block.

Date: 01.09.1999

Training Center

0 1 8F31H Parameter in write-protected 2nd active data block.
0 1 8F32H DB number in parameter too high.
0 1 8F33H DB number error.
0 1 8F3AH Destination area not loaded (DB).
0 1 8F43H Timeout when writing a parameter into the I/O area.
0 1 8F45H Address of parameter to be written disabled in the access track.
0 1 8F7FH Internal error, e.g. illegal ANY reference.

0 1 8090H No module with this starting address or CPU in STOP.
0 1 8091H Module starting address not at doubleword boundary.

0 1 80A0H Negative acknowledgement when reading from module.
0 1 80A4H Communication bus link between CPU and CP not established
0 1 80B0H Data record unknown to module.
0 1 80B1H Destination area invalid.

Date: 01.09.1999

Training Center

0 1 80B2H Communication bus link between CPU and CP not established.
0 1 80C0H Data record cannot be read.
0 1 80C1H Specified data record currently being processed.
0 1 80C2H Too many jobs pending.
0 1 80C3H Resources (memory) of CPU temporarily occupied.
0 1 80C4H Communication error.
0 1 80D2H Incorrect module starting address.

Date: 01.09.1999

Training Center
Job Header
User data area

Byte
Job buffer Port Low Byte High Byte 0,1
2,3
142 11
Job header IP address 4,5
40 35
User data Data byte 0 Data byte 1 6,7
Data byte 2040 Data byte 2041 2046,2047

Date: 01.09.1999
The address and job parameters for a specified connection are defined in the
connection configuration. The user program only needs to provide the user data
area by means of AG_SEND/AG_LSEND and AG_RECV/AG_LRECV.
Job Header Free UDP connections need a job header in the user data area.
The diagram shows the structure of the job buffer and the position and meaning
of the parameters in the job header.
The user data area can be up to 2048 bytes long.
6 bytes are reserved for the job header and up to 2042 bytes of user data can be
transferred.

Training Center

Programming With The SEND/RECEIVE Interface: Simatic Net

Uploaded by

Copyright:

Available Formats

Programming With The SEND/RECEIVE Interface: Simatic Net

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Programming With The SEND/RECEIVE Interface: Simatic Net

Uploaded by

Copyright:

Available Formats

Programming with the SEND/RECEIVE Interface

SIMATIC NET Industrial Ethernet

SEND-RECEIVE Interface in the CPU...................................................................................... 2

Siemens AG Page 1 SEND/RECEIVE Interface

Ethernet station SIMATIC S7

CPU cycle Transmission time

SIMATIC NET Industrial Ethernet

Note The information given here applies to both AG_SEND and

• The CPU cycle is faster than the transmission time.

Siemens AG Page 2 SEND/RECEIVE Interface

FC calls faster than the transmission time

FC calls slower than the transmission time

SIMATIC NET Industrial Ethernet

Siemens AG Page 3 SEND/RECEIVE Interface

ISO ISO-on- TCP UDP

Receive 8192 bytes 8192 bytes 8192 bytes 2048 bytes

SIMATIC NET Industrial Ethernet

Please read the product information for your CP.

Siemens AG Page 4 SEND/RECEIVE Interface

• Data block (DB)

• Bit memory address area

SIMATIC NET Industrial Ethernet

• Data block (DB):

• Bit memory address area:

Siemens AG Page 5 SEND/RECEIVE Interface

• Connection number (ID);

• Location of the user data area in the CPU.

Purpose of the FCs Calling FC blocks results in the following action:

• The user data area is passed to the Ethernet CP

• Positive or negative confirmation of execution of the job

SIMATIC NET Industrial Ethernet

Connections Program the SEND-RECEIVE interface in the user program as follows:

• Use the following FCs for transferring data via configured

• Evaluate the condition codes issued by the FCs:

- For AG_SEND these are the parameters DONE, ERROR and

- For AG_RECV the parameters NDR, ERROR and STATUS

Siemens AG Page 6 SEND/RECEIVE Interface

Pass Send data to the

Write PIQ Key: CPU cycle

SIMATIC NET Industrial Ethernet

We can observe the following:

• The user program can send data via connections by means of

Siemens AG Page 7 SEND/RECEIVE Interface

Block number FC type Purpose

SIMATIC NET Industrial Ethernet

Siemens AG Page 8 SEND/RECEIVE Interface

If the entry “SIMATIC NET CP” is not present, proceed as follows:

2. Search for the directory “Simnetcp” in

SIMATIC NET Industrial Ethernet

Siemens AG Page 9 SEND/RECEIVE Interface

• Specification of the CP address

SIMATIC NET Industrial Ethernet

FC Output On complete restart/restart of the Ethernet CP (e.g. when the switch is

• STATUS = 8180H for AG_RECV and 8181H for AG_SEND

Siemens AG Page 10 SEND/RECEIVE Interface

CP address indicates a module with Possible error codes in STATUS:

SIMATIC NET Industrial Ethernet

The SIMATIC S7 addresses the Ethernet CP like an analog module. If an

Siemens AG Page 11 SEND/RECEIVE Interface