Configuring PROFINET I-Device Between SIMOTION D425 and S7-1200

Overview

This reference covers the configuration of PROFINET I-Device (Intelligent IO Device) communication between a SIMOTION D425-2 PN/DP motion controller and a SIMATIC S7-1215C CPU (S7-1200 family). The goal is to deterministically exchange Boolean (BOOL), 16-bit integer (INT), and 32-bit floating-point (REAL) tags between the two controllers through PROFINET transfer areas rather than user-level protocols such as S7 PUT/GET, BSEND/BRCV, or OPC UA.

Both controllers integrate a PROFINET interface with an internal 2-port switch. The I-Device function allows each controller to be a fully programmable PROFINET node on a higher-level PROFINET segment while still running its own application. The data exposed to the higher-level controller is structured as transfer areas: byte-aligned input and output slots. Bit, INT, and REAL data is packed into these bytes with no additional protocol overhead, so the I/O access is identical to a standard I/O module.

PROFINET I-Device Architecture

An I-Device behaves like a PROFINET IO Device on its lower-level segment, while simultaneously running an application program like a standard controller. The data exposed to the higher-level PN Controller is defined by transfer areas: byte-aligned I/O slots that the I-Device's program reads and writes through its own I/O image.

When to Use the I-Device Method

I-Device is the correct pattern when all of the following are true:

• Both controllers are part of the same machine and need deterministic, cyclic data exchange at PROFINET update times (1 ms / 2 ms / 4 ms).
• The exchanged payload is bounded (typically less than 256 bytes per direction) and fits in the I/O image.
• Bit, INT, and REAL data is laid out as packed structures without per-tag overhead.
• Either controller needs to be the deterministic master of motion while the other runs sequence logic.

If the payload is large, sparse, or event-driven, or if the controllers are on different subnets, use S7 PUT/GET, BSEND/BRCV, or OPC UA Server on the S7-1200 (firmware V4.4+) instead.

Prerequisites

Verify each item before starting configuration. The procedure will not complete reliably if any of these is wrong.

Topology and Role Selection

Pick which controller is the PN Controller and which is the I-Device based on the application:

• S7-1215C as PN Controller, SIMOTION D425-2 as I-Device: the typical machine-cell pattern. The S7-1200 orchestrates HMI, safety, and sequence logic; the SIMOTION runs motion axes. The SIMOTION exposes axis status, current values, and faults to the S7-1200; the S7-1200 feeds enable, setpoints, and job commands down to the SIMOTION.
• SIMOTION D425-2 as PN Controller, S7-1215C as I-Device: used when the SIMOTION is the master of a complex line, and a small S7-1200 acts as a satellite (e.g., distributed local I/O, local safety, or a small subsystem with its own HMI).

Step 1 - Plan the IP Addresses and Subnet

Document the addressing before you open TIA Portal. PROFINET I-Device communication requires both ports to be on the same IP subnet.

Reserve the next free IP for the HMI panel and leave at least 10 free addresses for service and future expansion. The PROFINET device name is case-sensitive; match the spelling in TIA Portal exactly.

Step 2 - Configure SIMOTION D425-2 as I-Device

Open the TIA Portal project (or SCOUT standalone project) that contains the SIMOTION D425-2.

1. In the project tree, add the SIMOTION D425-2 PN/DP from the catalog under Controllers > SIMOTION > D4xx-2.
2. Open Devices & Networks, select the SIMOTION, and open Properties > PROFINET interface [X150] > Ethernet addresses. Enter the IP address, subnet mask, and the PROFINET device name simotion-d425.
3. Open Properties > PROFINET interface [X150] > Operating mode. Select I-Device. The interface mode shows as I-Device and the I-Device editor is unlocked.
4. Open the Transfer areas tab and add the slots the PN Controller will read or write. For a typical S7-1215C ↔ SIMOTION D425 layout:
   Slot 0 - Input - 16 bytes - SIMOTION → S7-1200 (axis status, current values)
Slot 1 - Output - 16 bytes - S7-1200 → SIMOTION (enable, setpoints, job commands)
5. Click on each transfer area to set the I/O addresses in the SIMOTION I/O image. The PN Controller's view of the slot is independent; only the I-Device side addresses matter here.
6. Save and compile the SIMOTION project. Address-consistency errors appear as compile warnings if a transfer area overlaps an existing I/O symbol.

Step 3 - Configure the S7-1215C as PN Controller

1. Add the S7-1215C to the same TIA Portal project (in-project scenario) or to a separate project (cross-project scenario, see Step 5).
2. Open Properties > PROFINET interface [X1] > Ethernet addresses. Enter the IP 192.168.0.10, mask 255.255.255.0, and PROFINET device name plc-cpu1215c.
3. Open Properties > PROFINET interface [X1] > Operating mode. Set the role to PN Controller. Do not enable I-Device mode on this side.
4. From the device catalog, drag the SIMOTION D425-2 (in-project: under the same project tree; cross-project: under Other field devices > PROFINET IO > ... after GSDML install) onto the PROFINET subnet.
5. In the Devices & Networks editor, draw the PROFINET connection from the S7-1215C X1 to the SIMOTION X150. The S7-1200 becomes the controller, the SIMOTION becomes the I-Device.
6. Open the S7-1200's Device view, drag the I-Device's transfer areas from the catalog into the I/O slots. The S7-1200 will assign I and Q addresses automatically; these are the I/O addresses the S7 program uses for direct I/O access.
7. Set the IO cycle time on the PROFINET interface. For motion applications, use 1 ms or 2 ms. For pure status exchange, 4 ms is sufficient and reduces bus load.

Step 4 - Define the Data Layout Inside the Transfer Areas

Plan the byte-level structure before you start programming. The I-Device does not differentiate between BOOL, INT, and REAL - all are packed into the byte image. The PN Controller's I/O view of the same area must use the same byte order.

Use the same byte offset on both sides. Address-tag mismatch on byte 4 (REAL access on a 32-bit boundary) is the most common cause of garbled values.

Step 5 - Cross-Project GSDML Export and Import

If the SIMOTION D425-2 and the S7-1215C are in different TIA Portal projects (typical when SIMOTION is engineered by a motion specialist and S7-1200 by a PLC specialist), export the I-Device description and install it on the other side.

Export the GSDML from the I-Device project

1. In the I-Device project (SIMOTION D425-2), open Devices & Networks and select the SIMOTION D425-2.
2. Open Properties > PROFINET interface [X150] > Operating mode > I-Device.
3. Click Export I-Device GSDML. TIA Portal generates a .xml GSDML file in the project folder under Documents > GSDML.
4. Copy the GSDML file to the PN Controller project (or a network share both engineers can access).

Install the GSDML on the PN Controller project

1. In the S7-1200 project, choose Options > Manage general station description files (GSD).
2. Browse to the GSDML file and click Install. TIA Portal places the SIMOTION under Other field devices > PROFINET IO > SIMOTION > D4xx-2 in the catalog.
3. Drag the SIMOTION from the catalog onto the PROFINET subnet and assign it as an IO Device of the S7-1215C.
4. Drag the I-Device's transfer areas into the S7-1200 slot table. The catalog slot list matches the export 1:1.

Step 6 - Wire the I/O Variables in the Application

Both controllers access the data through their standard I/O instructions, not through special PROFINET blocks.

S7-1215C side (TIA Portal, SCL or LAD)

// Read axis status from SIMOTION (input area)
IF "Axis1Ready" AND NOT "Axis1Faulted" THEN
    "HMI_Axis1State" := "Axis1State";          // INT
    "HMI_Axis1ActPos" := "Axis1ActPos";        // REAL
END_IF;

// Send enable and setpoint to SIMOTION (output area)
"Axis1Enable" := "HMI_Start" AND "SafetyOK";
"Axis1Stop"   := NOT "SafetyOK";
"Axis1Cmd"    := 10;                            // INT, e.g. job code
"Axis1SetPos" := "HMI_TargetPos";              // REAL, mm

SIMOTION D425-2 side (ST or MCC chart)

// my_io_data is the I/O variable block mapped to the transfer area
// Convention: %I.. on the SIMOTION side = process inputs from S7-1200
//             %Q.. on the SIMOTION side = process outputs to S7-1200

IF cmdAxis1Enable AND NOT cmdAxis1Stop THEN
    stAxis1Ready := TRUE;
    stAxis1Faulted := FALSE;
    iAxis1State := axis1.state;       // INT
    rAxis1ActPos := axis1.actualPos;  // REAL [mm]
ELSE
    stAxis1Ready := FALSE;
END_IF;

Make sure the SIMOTION IO data block is mapped to the same process image that the I-Device transfer area uses. In SIMOTION SCOUT, open Project > I/O > Address table and confirm the address ranges match the transfer area offsets defined in Step 2.

Step 7 - Compile, Download, and Go Online

1. Compile the SIMOTION project first. Resolve any address-overlap warnings before continuing.
2. Compile the S7-1200 project. The compile log must show the SIMOTION I-Device as a known PROFINET IO Device.
3. Download the S7-1200 hardware configuration. After the download, TIA Portal prompts you to assign the PROFINET device name plc-cpu1215c to the S7-1200 - confirm.
4. Download the SIMOTION project. The PROFINET device name simotion-d425 is assigned during the SCOUT download or via the Topology editor.
5. On the S7-1200, go online. Open Online & diagnostics > PROFINET diagnostics. The I-Device should appear with state Connected and no error code.
6. On the SIMOTION, go online in SCOUT. Open Diagnostics > PROFINET diagnostics. The PN Controller should be listed, and the cyclic data should be exchanging without diagnostic alarms.

Verification and Online Diagnostics

S7-1200 verification

• Open a watch table and monitor %I0.0 and %IW2. Force %Q0.0 ON and confirm the corresponding SIMOTION IO variable changes within one PROFINET update time.
• Open Online & diagnostics > PROFINET diagnostics > Port statistics. Discards, CRC errors, and late collisions must be zero.
• Use the S7-1200 web server (default URL http://192.168.0.10) and navigate to Diagnostics > PROFINET > IO Devices. The SIMOTION should show OK.

SIMOTION verification

• Open Diagnostics > PROFINET diagnostics > I-Device status. State must be AR established and Data exchange active.
• Use the SIMOTION trace to record the IO variables and confirm the update time matches the configured cycle time (1 ms / 2 ms / 4 ms).
• Watch the BF (bus fault) LED on the SIMOTION X150. Steady off = OK; flashing at 2 Hz = no PROFINET link; on solid = configuration error.

Use PRONETA for free PROFINET diagnostics

Siemens PRONETA is a free engineering tool for PROFINET network analysis. Run it on the engineering PG to:

• Scan the subnet and confirm both devices appear with their configured names and IPs.
• Run the topology check; mismatches show up as a yellow topology diff.
• Capture cyclic traffic and confirm the AR between the S7-1200 and SIMOTION has no vendor-specific extension mismatches.

Simulation with SIMOSIM and PLCSIM

Simulating PROFINET I-Device communication is possible, but with limitations.

To run a closed-loop simulation, the practical approach is:

1. Start PLCSIM Advanced with the S7-1200 instance and enable the soft PROFINET interface.
2. Start SIMOSIM with the SIMOTION D425-2 instance. Confirm the I-Device transfer areas are exposed.
3. Use the TIA Portal topology editor to connect the two soft instances over the local loopback.
4. Download the programs into both simulators and run. Monitor the IO variables in the same way as on real hardware.

Troubleshooting Matrix

Field-Proven Tips

• Stick to byte alignment. REAL data must start at byte offsets that are multiples of four. INT data at multiples of two. Misalignment is the most frequent cause of "values look right until the third byte" symptoms.
• Watch the S7-1200 process image limit. The S7-1215C has 1024 bytes of input process image and 1024 bytes of output process image. The I-Device transfer area addresses are taken from this image. Plan the address space so that the I-Device transfer areas do not collide with the S7-1200's local I/O module addresses.
• Use distinct PROFINET device names. Re-using plc-cpu1215c on multiple S7-1200s in the same subnet causes the PN Controller to bind to the wrong physical node.
• Keep the GSDML under version control. The exported XML file is the authoritative source of the I-Device interface. Store it in the same Git or SVN repository as the TIA Portal project.
• Update the PRONETA topology before each FAT. A 30-second scan in PRONETA catches device-name and IP issues that would otherwise show up as intermittent AR aborts during commissioning.
• Enable the SIMOTION diagnostic buffer alarm filter. Filter on the PROFINET IO source so motion-specific IO faults are not buried under axis-level alarms.

Standards and Further Reading

Refer to the official Siemens documentation for parameter defaults, firmware-specific behavior, and certified PROFINET conformance classes:

• SIMATIC S7-1200 Communication Manual - covers I-Device configuration, PROFINET interface parameters, and supported communication services for the S7-1200 family.
• PROFINET Installation Guideline (PNO document NEMA 100.1) - the authoritative document on cabling, topology, and delay budgets for PROFINET networks.
• PROFINET Conformance Classes (CC-A, CC-B, CC-C) - documented in the PROFINET specification; S7-1200 and SIMOTION D4xx-2 both meet CC-B minimum.

FAQ