Entry type: FAQ, Entry ID: 51339682, Entry date: 04/21/2016
(4)
Rate

Which "local_device_id" do you parameterize in order to establish a connection with FB65 "TCON" for Open User Communication (OUC) via Industrial Ethernet?

  • Entry
  • Associated product(s)
Depending on the module and interface through which the connection with the FB65 "TCON" for open communication via Industrial Ethernet is established, you parameterize the "local_device_id" accordingly.

The "local_device_id" for the S7-300 and S7-400 CPUs as well as for the IM151-8 PN/DP CPU and IM154-8 CPU is in the Hardware Configuration (STEP 7 V5.x) or in the Device View of the hardware and network editor (STEP 7 (TIA Portal)). The slot identification for a module's PROFINET interface contains the "local_device_id".

Example for STEP 7 V5.x
The slot identification for the PROFINET interface of a CPU319-3 PN/DP is "X3", in other words you parameterize the "local_device_id" = B#16#03 for open communication via the integrated PROFINET interface of a CPU319-3 PN/DP.


Fig. 01

Example for STEP 7 (TIA Portal)
The slot identification for the PROFINET interface of a CPU319-3 PN/DP is "2 X3", in other words you parameterize the "local_device_id" = B#16#03 for open communication via the integrated PROFINET interface of a CPU319-3 PN/DP.


Fig. 02

Note
The slot identification for the PROFINET interface of an S7-300 CPU, S7-400 CPU, IM151-8 PN/DP CPU or IM154-8 CPU is also printed on the module.

Overview
Table 1 shows the "local_device_ids" which are to be parameterized for open communication via WinAC RTX and S7-400 Industrial Ethernet CP. The "local_device_id" of the WinAC RTX depends on the interface slot of the Industrial Ethernet interface.
 

local_device_id Description
B#16#00 Communication via Industrial Ethernet CP of the S7-400 (only with ISO-on-TCP, in other words connection_type = B#16#12)

Note
Entry ID 15368142 contains information about which S7-400 series Industrial Ethernet CPs support open communication services using T blocks.

B#16#01 Communication via the Industrial Ethernet interface at interface slot 1 (IF1) with WinAC RTX
B#16#06 Communication via the Industrial Ethernet interface at interface slot 2 (IF2) with WinAC RTX
B#16#0B Communication via the Industrial Ethernet interface at interface slot 3 (IF3) with WinAC RTX
B#16#0F Communication via the Industrial Ethernet interface at interface slot 4 (IF4) with WinAC RTX

Table 1

Table 2 shows the "local_device_id" that you parameterize for open communication via the integrated PROFINET interface of an S7-300 CPU, S7-400 CPU, IM151-8 PN/DP CPU or IM154-8 CPU.
 

local_device_idDescription
B#16#01Communication via the integrated PROFINET interface of the IM151-8 PN/DP CPU
B#16#02Communication via the integrated PROFINET interface of the IM151-2 PN/DP CPU
B#16#03Communication via the integrated PROFINET interface of the CPU319-3 PN/DP, CPU315T-3 PN/DP, CPU317T-3 PN/DP, CPU317TF-3PN/DP
B#16#04Communication via SINUMERIK NCU7x0.2 PN with CPU319-3 PN/DP and SINUMERIK NCU7x0.3PN with CPU317-2 PN/DP
B#16#05Communication via the integrated PROFINET interface of the CPU412-2 PN, CPU414-3 PN/DP, CPU416-3 PN/DP, CPU412-5H PN/DP (Rack 0), CPU414-5H PN/DP (Rack 0), CPU416-5H PN/DP (Rack 0) and CPU417-5H PN/DP (Rack 0)
B#16#08Communication via the integrated PROFINET interface of the CPU410-5H (Rack 0)
B#16#15Communication via the integrated PROFINET interface of the CPU412-5H PN/DP (Rack 1), CPU414-5H PN/DP (Rack 1), CPU416-5H PN/DP (Rack 1) and CPU417-5H PN/DP (Rack 1)
B#16#18Communication via the integrated PROFINET interface of the CPU 410-5H (Rack 1)

Table 2