Entry type: FAQ, Entry ID: 29737976, Entry date: 11/20/2014
(2)
Rate

How do you program the communication blocks FB63 "TSEND", FB64 "TRCV", FB65 "TCON" and FB66 "TDISCON" in order to use the ISO-on-TCP protocol for data exchange via the integrated PROFINET interface of an S7-300/S7-400 CPU or via the CP443-1 Advanced?

  • Entry
  • Associated product(s)

Description
You can use, for example, the "Open User Communication" over Industrial Ethernet for data exchange via the integrated PROFINET interface of a CPU or via CP4431 Advanced. The protocols below are supported for this:

  • TCP
  • ISO-on-TCP
  • UDP

The following communication blocks are available for "Open User Communication" via Industrial Ethernet using the ISO-on-TCP Protocol:

  • FB65 "TCON" for establishing the connection
  • FB66 "TDISCON" for ending the connection
  • FB63 "TSEND" for sending data
  • FB64 "TRECV" for receiving data

These communication blocks are available in the Standard Library -> Communication Blocks.
Copy the latest versions of the above-mentioned communication blocks from the standard library into your user program and then call them in your user program.
The connection data for establishing the ISO-on-TCP connection are saved in a data structure. The data structure "OUCW_1" will be used in this example. This is stored in the DB1 data block and is parameterized by the user.

Note

  • Use the "Open Communication Wizard" for simple creation of connection data. This is available for downloading in Entry ID 98957840.
  • The ISO-on-TCP connection is not configured in NetPro.

Table 01 shows the "OUCW_1" data structure in which the connection data is stored.
 

Byte Parameter Data type Description
0 to 1 block_length WORD Length of the "OUCW_1" data structure
2 to 3 id BYTE Reference to this connection
Value range: W#16#0001 to W#16#0FFF
You must specify the value of this parameter for the ID in the block concerned.
4 connection_type BYTE ISO-on-TCP protocol version: B#16#12
5 active_est BOOLEAN ID for how the connection is established.
  • FALSE: connection established passively
  • TRUE: connection established actively
6 local_device_id BYTE Communication through the integrated PROFINET interface of the CPU 315-2 PN/DP: B#16#02
7 local_tsap_id_len BYTE Length used for the local_tsap_id parameter
Possible values if connection_type = B#16#12: 2 to 16
8 rem_subnet_id_len BYTE This parameter is not used currently. It has the value B#16#00.
9 rem_staddr_len BYTE Length of the address of the remote connection end point:
  • 0: unspecified, which means that the rem_staddr parameter is irrelevant
  • 4: valid IP address in the rem_staddr parameter.
10 rem_tsap_id_len BYTE Length used for the rem_tsap_id parameter
Possible values if connection_type = B#16#12: 0 or 2 to 16
  • active side: 2 to 16
  • passive side: 0 or 2 to 16 (0 means unspecified)
11 next_staddr_len BYTE Length used for the next_staddr parameter
12 to 27 local_tsap_id ARRAY [1..16] of BYTE Local TSAP, such as ISO1:
local_tsap_id[1] = B#16#49
local_tsap_id[2] = B#16#53
local_tsap_id[3] = B#16#4F
local_tsap_id[4] = B#16#31
local_tsap_id[5-16] = B#16#00

Note
In the case of CPUs that do not support the ASCII format for the TSAPs, then the first two bytes of the TSAP must be defined with the values B#16#E0 and B#16#02.

28 to 33 rem_subnet_id ARRAY [1..6] of BYTE This parameter is not used currently. It has the value B#16#00.
34 to 39 rem_staddr ARRAY [1..6] of BYTE IP address of the remote connection end point, such as 192.168.0.30:
rem_staddr[1] = B#16#C0
rem_staddr[2] = B#16#A8
rem_staddr[3] = B#16#00
rem_staddr[4] = B#16#1E
rem_staddr[5-6] = B#00 (reserved)
40 to 55 rem_tsap_id ARRAY [1..16] of BYTE TSAP of the remote connection end point, such as ISO1:
rem_tsap_id[1] = B#16#49
rem_tsap_id[2] = B#16#53
rem_tsap_id[3] = B#16#4F
rem_tsap_id[4] = B#16#31
rem_tsap_id[5-16] = B#16#00

Note
In the case of CPUs that do not support the ASCII format for the TSAPs, then the first two bytes of the TSAP must be defined with the values B#16#E0 and B#16#02.

56 to 61 next_staddr ARRAY [1..6] of BYTE next_staddr[1-6] = B#16#00

Note
If local_device_id=B#16#00, then here you specify the rack and slot of the (local) CP.

62-63 spare WORD Reserve, the parameter has the value W#16#0000.
Table 01

The CPUs below support the ASCII format for the TSAPs.

  • CPU 314C-2 PN/DP
  • CPU 315(F)-2 PN/DP, CPU 317(F)-2 PN/DP V3.1 and later
  • CPU 315T-3 PN/DP, CPU 317T-3 PN/DP, CPU 317TF-3 PN/DP
  • CPU 319(F)-3 PN/DP
  • CPU 414-3 PN/DP, CPU 416(F)-3 PN/DP V5.2 and later
  • CPU 414F-3 PN/DP, CPU 412-2 PN
  • CPU 412-5H PN/DP, CPU 414-5H PN/DP, CPU 416-5H PN/DP, CPU 417-5H PN/DP
  • IM 151(F)-8 PN/DP CPU V2.7 and later
  • IM 154(F)-8 CPU V3.2 and later

Description of the sample program
The S7 program contains the call of the FB65 "TCON" and the DB1 data block of the "OUCW_1" data structure in which the connection data for setting up the ISO-on-TCP connection are stored. The S7 program also includes the call of the function blocks FB63 "TSEND" and FB64 "TRECV" from the Standard Library -> Communication Blocks. The FB63 "TSEND" is for sending data to an S7 station or to an S5 station, to a PC station or to a third-party system. The FB64 "TRCV" is for receiving data from another S7 station or an S5 station, from a PC station or from a third-party system.

First create the hardware configuration for your S7-300 station. Configure Marker byte 100 as clock marker. The send job is triggered by this clock marker. Save and compile the hardware configuration of your S7-300 station and load it into the CPU.

The STEP 7 program consists of the blocks OB100, OB1, FB1, DB11, DB1, DB100, DB200 and FB63, FB64, FB65 and FB66.

OB100
The OB100 is a restart OB and is run when the CPU is restarted (warm start). In this OB the first communication trigger is enabled with marker M0.3.

OB1
OB1 is called cyclically. The FB1 is called in OB1 with the instance data block DB11, with the marker M0.3 as INIT_COM parameter and with the marker 10.0 as ABORT parameter. The marker M0.3 is reset in OB1 after the FB1 has been called.


Fig. 01

FB1
The FB1 is called cyclically in OB1. The following function blocks are called in FB1.

  • FB65 "TCON"
  • FB63 "TSEND"
  • FB64 "TRCV"
  • FB66 "TDISCON"

Define connection number
You can change the connection number separately. Change the connection number in network 2 of FB1 in accordance with your configuration. The connection number is stored in a static tag and so in the instance data block DB11.
The connection number "1" is defined in this example.


Fig. 02

Connection setup
Establishing a connection is started by a positive edge in the "REQ" input parameter of the FB65 "TCON". The "OUCW_1" data structure with the connection parameters is incorporated in the data block DB1.
On the input parameter "CONNECT" of the FB65 "TCON", the memory area is specified that contains the connection parameterization.
The connection is set up at system start and remains until it is disabled with FB66 "TDISCON", or the CPU goes into STOP mode, or the power supply is switched off.


Fig. 03

The send request is triggered by a positive edge at the input parameter "REQ" of the FB63 "TSEND". The send request trigger is controlled by clock marker M100.6 and the variable "SEND_BUSY". If the send request is running, "SEND_BUSY" is set. It is then not possible to trigger a new send request.
You specify the memory area that contains the data to be sent at the input parameter "DATA".
You enter the number of bytes to be sent at the input parameter "LEN".
In this example the Send data is stored in DB100. 100 bytes of data is sent to the communication partner.
The output parameters "DONE", "ERROR" and "STATUS" are required for job evaluation.


Fig. 04

If the send request is successfully completed, "SEND_BUSY" is reset. A new send job can now be triggered.
If the send request is completed with an error, then "SEND_BUSY" is likewise reset and the value of the output parameter "STATUS" of the FB63 is saved for an error analysis.


Fig. 05


Fig. 06

The data can be received as soon as the ISO-on-TCP connection is established.
At the input parameters "DATA" and "LEN" you specify the address and length of the data area where the received data is saved.
In this example 100 bytes of data are received and stored in DB200.


Fig. 07

The output parameter "NDR" is for showing that new data has been received. The "RECV_LEN" output parameter indicates the length of the data received.
If the data is received successfully, then the value of the "RCVD_LEN" output parameter is saved.


Fig. 08

If the data is not received successfully, then the value of the "STATUS" output parameter is saved and evaluated.


Fig. 09

You can disable the ISO-on-TCP connection with the FB66 "TDISCON". You start the request to disable the ISO-on-TCP connection via a positive edge on the input parameter "REQ" of the FB66 "TDISCON".


Fig. 10

The STEP 7 project as a download
The STEP 7 project contains a sample program for calling FB1 and the function blocks FB65 "TCON", FB66 "TDISCON", FB63 "TSEND" and FB64 "TRECV" with status evaluation. It was created with STEP 7 V5.5 SP3.

Sample_open_IoT.zip ( 285 KB )

Configuring additional ISO-on-TCP connections
To configure additional ISO-on-TCP connections you copy the FB1 so that you receive another function block (such as FB101). Change the parameters and generate a new instance data block.

Further Information

  • Detailed information on open communication over Industrial Ethernet is available in the manual "System and Standard Functions for S7-300/400 Volume 1 and Volume 2" in Entry ID: 44240604.
  • Instructions for configuring an ISO-on-TCP connection for communication via S7-300 and S7-400 CPs are available in Entry ID: 47885440.

Error details
Detailed error description
Help us to improve Online Support.
The page requested cannot be displayed. Please contact the webmaster.
Contact to webmaster