How to use iC9200 controller as a PROFINET I-Device

Version Number	Description
1.0	Initial Version

This document shows how to use iCube controller as an PROFINET I-Device on different PROFINET Controller PLCs:

Siemens 1500
Phoenix AXC F 2152
YASKAWA SLIO 15
YASKAWA iCube

1. Supported Components

Component Name for PROFINET I-Device	Version
iC9200 series PLC with “PROFINET I-Device + Controller” License (JXPMC-OPX010703)	≥ 2023.9.1
iCube Engineer	≥ 2024.03
Example PROFINET Controller CPUs and programming tools
YASKAWA MICRO / SLIO / 300+ PLC <1> <2>
Siemens 300 / 1200 / 1500 PLC <2>
Phoenix PLCnext AXC F 2152 PLC <3>
<1> SPEED7 Studio
<2> Siemens TIA Portal	≥ TIA 15
<3> Phoenix PLCnext Engineer	≥ 2023.9

2. Supported libraries

No library needed.

3. Overview hardware configuration

Figure 1: Example for hardware configuration with iCube as PROFINET I-Device

PROFINET I-Device enables very simple and fast communication between two PROFINET IO controllers. This document shows how to use iCube CPU iC9226M-EC as an PROFINET I-Device with different controller CPUs. An Example is included to use user defined data structure communication between Controller and I-Device. A “PROFINET I-Device + Controller” License is required on iCube.

4. Configuration of the PROFINET Controller

Import the GSDML File for iCube I-Device in the programming system.
Configure hardware with iCube I-Device from Catalog
Put Module with needed number of Bytes to device
Set Device name and Ethernet IP address of I-Device

GSDML files to use iCube as I-Device:

Figure 2 : GSDML files

V2.31 and V2.43 are different versions specified in PNO: GSDML / GSDX Specification for PROFINET - www.profibus.com

4.1 Example PROFINET controller CPU with TIA Portal

For Yaskawa / Siemens 300 and Siemens 1200 / 1500 CPU’s there is the same handling of hardware configuration. Steps to integrate GSDML files of iC9200 for PROFINET I-Device into TIA catalog:

Figure 3: Integrate GSDML file into TIA catalog

Add iCube iC9226M-EC as PROFINET I-Device into TIA hardware configuration

Figure 4: Hardware configuration with iCube PROFINET I-Device

Select the number of Bytes for data exchange for the I-Device. There is only one Submodule possible. The number of input and output bytes is always the same.

Figure 5: Select 64 Bytes for I-Device communication

Configuration of Ethernet IP address and PROFINET device name in hardware configuration. The IP address must be in the same subnet of controller’s IP address. IP address and device name has to match the settings in iCube hardware configuration (see figure 3).

Figure 6: IP address and PROFINET Device name setting

4.2 Example YASKAWA SLIO 15 controller CPU with SPEED7 Studio

GSDML File Import in SPEED7 Studio

Figure 7: Import GSDML File in SPEED7 Studio

Connecting iCube as PROFINET I-Device to the SLIO 15 Controller CPU

Figure 8: SPEED7 Studio Hardware configuration with iCUbe as PROFINET I-Device

Setting of Ethernet IP address and PROFINET device name in SPEED7 Studio

Figure 9: Setting PROFINET bus system properties in SPEED7 Studio

4.3 Example Phoenix AXC F 2152 PROFINET controller CPU with PLCnext Engineer

GSDML File Import with PLCnext Engineer (As with iCube Engineer)

Figure 10: Import GSDML files with PLCnext Engineer

Insert iCube as PROFINET I-Device into PLCnext Engineer hardware tree and add Submodule with number of needed DIO Submodule.

Figure 11: Hardware configuration PLCnext Engineer

Setting device name and IP address in PROFINET tree

Figure 12: Setting IP address and Device Name in PLCnext Engineer

5. Configuration of the iCube Controller to run as a PROFINET I-Device:

Enabling I-Device System service on iCube Webpage

Figure 13 : Enable PROFINET I-Device on iCube

Setting unique Device name and Ethernet address in HW configuration in the same range of PROFINET controller PLC (e.g. 192.168.1.x)

Figure 14 : Setting IP-address and PROFINET Device name

Transfer Device Name and IP address to the connected iCube PLC

Figure 15 : Device Name and IP address setting to iCube controller

6. Diagnostic of PROFINET I-Device communication

After connecting PROFINET controller PLC with iCube PROFINET I-Device PCL and booting up the PROFINET bus system will be initialized and go into run state with automatically data exchange. The status of PROFINET I-Device communication is monitored in the PND_S1_* variables of iCube PLC. Data exchange will be done automatically with the array [0..511] of byte variables PND_S1_OUTPUTS and PND_S1_INPUTS. The length of transferred bytes is defined in hardware configuration of the controller PLC and shown in PND_S1_DATA_LENGTH. Input and output data has the same length.

Figure 16 Diagnostic of I-Device functionality of iCube