Routing TSAPs

S7 Routing General

Routing is the ability of the OPC server to address PLC controllers across subnet boundaries as well. OPC communication is possible with all stations that can be reached via gateways. It does not matter how many gateways it has and how many are between the Ethernet network (where the OPC server station is located) and the destination network. For the FETCH / WRITE communication, a connection must only be configured on the OPC side. In S7 it is not necessary to create a connection. For the connection path, information of the destination network and the destination station must be known.

However, the TSAPs would have to be assembled manually. The following settings are necessary for the routing:

Own TSAP:

01 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00

Dest TSAP:

01 06 01 02 [aa bb] 00 00 [cc dd] [ee] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ff] [gg]

[aa bb] first part of the subnet ID from Step7

[cc dd] second part of subnet ID from Step7

[ee] MPI Profibus address

[ff] Service

[gg] Slot of the CPU

Destination PLC results in the Dest TSAP

Here, settings are made for the destination PLC, the controller from which values ​​are to be read out or written to the values.

S7 subnet ID

Each subnet in the S7 receives a subnet ID, which is automatically generated by Step 7. The subnet ID of the destination network must be specified here. The S7 subnet ID can be e.g. be determined as follows:

MPI / Profibus address

If it is an MPI network, the MPI address of the PLC is entered here. If it is a Profibus network, the Profibus address is entered.

Service

The service "3" is intended for OPC connections

Slot of the CPU

The slot number of the CPU is entered here.

Special case INAT echolink

Own TSAP:

Is the first device between network and MPI an echolink, then

FF FF FF FF FF FF 56 43 4F 4D 00 02 04 [aa] 00 00 00 00 00 00 00 00 00 00 00 [bb] 00

[aa] 0x80 plus backplane bus MPI CP Port, or MPI address of the CPU

[bb] = Com Connection of the echo

The first device between network and MPI is an echolink

If an echolink is in use that establishes the connection between Industrial Ethernet and the subnet, information about the routing PLC is required.

Routing PLC

The routing PLC is the S7 controller, which is connected to the echolink via MPI and represents the first transition from Industrial Ethernet to MPI. The MPI address of the routing module is entered here (MPI address of the CPU or CP).

COM port

Here, the COM port of the echolink device is selected, via which echolink is connected to the MPI interface of the S7 PLC.

Note:

Some CPs have their own MPI address. This MPI address is automatically determined and assigned by the CPU. If such a CP is in use, it is essential to ensure that the MPI address of the CP and NOT the MPI address of the CPU is used.

Determine the MPI address of the routing PLC

The MPI address of the routing PLC is determined in "NetPro" by marking the station and selecting "Object Properties" with the right mouse button. If a CP-MPI address is displayed next to a CPU MPI address, the MPI address of the CPs should be used.

Alternatively, the CP can also be marked in the hardware configuration and the "Object properties" selected using the right mouse button. The MPI address to be used is then displayed under "Backbone Connection".

Destination TSAP

The Dest TSAP is the same as described above.