Resolving PROFIBUS DP Communication Failures on SIMOTION D435-2

Problem: D435-2 PROFIBUS DP/MPI Red LED and Missing I/O

Field reports on the SIMOTION D435-2 (a member of the SIMOTION D4x5-2 motion-controller family) show a recurring symptom: the integrated X136 PROFIBUS DP/MPI interface reports a steady red DP/MPI LED and configured process data such as PIW 0 / PQW 0 remain in the "Does not exist" state in the SIMOTION Scout / TIA Portal address list. The fault is observed both when the D435-2 is configured as a DP slave to a third-party master and when it is configured as a DP master to a third-party slave (e.g., a National Instruments cRIO).

The interface will not enter cyclic data exchange (Data_Exch) until the bus fault is cleared at the physical, link, or application layer. This article walks through the root-cause analysis and corrective actions in the order they are most efficiently ruled out on the plant floor.

SIMOTION D4x5-2 Hardware and the X136 PROFIBUS Interface

The D4x5-2 (D425-2, D435-2, D445-2, D455-2) is a SIMOTION motion controller with an integrated PROFIBUS DP/MPI interface (X136) and an additional PROFINET interface (X150 P1/P2). The X136 port is implemented on a 9-pin Sub-D (DB9) male connector and is electrically isolated.

Maximum PROFIBUS segment length depends on baud rate:

Reference the official Siemens Industry Online Support manuals for the D4x5-2 (operating instructions, function manuals, and the SIMOTION Communication Configuration Manual) for the full pinout, cable specification, and shielding guidance.

DP/MPI LED State Meanings

The DP/MPI LED on the D435-2 front panel is a two-color (green/red) status indicator. The relevant states are:

A steady red DP/MPI LED is the classic signature of a physical-layer or "no token" condition: the controller either sees no bus activity or the bus is shorted / unterminated. It is the symptom most often reported by integrators working with mixed-vendor masters (Siemens / NI / Mitsubishi / Honeywell).

Layered Root-Cause Analysis

PROFIBUS DP faults are resolved most efficiently by walking the ISO/OSI layers from the bottom up. On the D435-2 platform the dominant failure modes for a red DP/MPI LED are:

1. Layer 1 — Physical (cable, connector, termination, shield): most common cause. Includes broken strands in the twisted pair, missing 220 Ω terminating resistors at both ends, A/B polarity swap, shield not bonded to connector housing, or the DB9 backshell not fully tightened so pin 3 or pin 8 loses contact.
2. Layer 2 — Bus parameters / baud rate: mismatch between master's HSA (Highest Station Address), gap factor, slot time, and the D435-2 settings. Default PROFIBUS DP is 1.5 Mbit/s unless overridden.
3. Layer 7 — Configuration / GSD: a missing or incorrect GSD file on the third-party master, or the master not assigning the I/O slots that the D435-2 expects.
4. Application — Address / symbolic mapping: process image configured (PIW/PQW 0) but the I/O area is not bound to a symbolic name in the SIMOTION project, or the wrong slot is referenced.

Step-by-Step Recovery Procedure

Prerequisites

• SIMOTION SCOUT (or TIA Portal with SIMOTION extension) version matching the D4x5-2 firmware on the controller.
• Authorized GSD file for the D435-2 (SIEM815F.GSD or the device-specific variant supplied with SCOUT). Place it in the master-side GSD directory and refresh the hardware catalog.
• PROFIBUS DP cable (Profibus-DP cable, type A: 150 Ω characteristic impedance, AWG 22 / 0.34 mm² solid conductor, twisted pair, foil + braid shield).
• Two PROFIBUS DP connectors with integrated 220 Ω termination + 390 Ω pull-up/pull-down (per IEC 61158).
• Multimeter, oscilloscope, or a PROFIBUS bus tester (e.g., Softing PB-T3, Indu-Sol PROFI-TM).

Procedure

1. Power down and physically re-terminate the bus. Confirm the two end nodes each have their terminator ON (switch in the connector set to ON). All intermediate connectors must be set to OFF. A common cause of a red DP/MPI LED is one device with termination enabled in the middle of the segment, which collapses the differential signal.
2. Verify the DB9 connector on X136. Open the connector housing and inspect the crimps on pins 3 (B) and 8 (A). A single broken strand — the one this case study was traced to — is enough to keep the LED red. Re-crimp and torque the backshell.
3. Confirm shield bonding. The PROFIBUS cable shield must make 360° contact with the metallized connector housing and be bonded to a low-impedance ground at one point in the cabinet. See the Pro-face PROFIBUS DP Slave Driver manual for a typical wiring example that also applies to Siemens-class devices.
4. Check bus parameters on the third-party master. For a National Instruments cRIO acting as DP master or slave, ensure the Baud rate and HSA are configured identically on both ends. NI-Profibus (NI PXI/PXIe-8531 or cRIO-954x modules) defaults to 1.5 Mbit/s with HSA = 126.
5. Install the GSD on the master side. On the NI side this is done in the NI-Profibus Configuration Tool (or whatever third-party configurator is in use). On the Siemens side, when the D435-2 is the master, ensure the cRIO's GSD is imported under HW Config > Options > Install GSD File.
6. Match the slot configuration. Define the same number of input and output words on both sides. In SCOUT, under X136 > DP Slave Properties > I/O Addresses, configure the PII/PIQ lengths and slot assignments. On the cRIO, configure the equivalent module slots in the NI tool so the master and slave agree on slot count and length.
7. Download the project to the D4x5-2. Online → Target system > Download → select Download to target device. Confirm the project is in RUN, not in STOP or commissioning.
8. Watch the DP/MPI LED transition. After the master (whether it is the D435-2 or the cRIO) starts token rotation, the LED should change from red to flashing green within a few token rotations, then to static green on a successful Data_Exch.

Verification

• In SIMOTION Scout, open Project Navigator > Address List — PIW 0 and PQW 0 must change from "Does not exist" to a valid I/O address with a quality flag of OK.
• Use the Diagnostics > PROFIBUS Diagnostics buffer on the D4x5-2 to confirm DP Master: Data_Exch with the expected slave address.
• Force a known pattern from the master and read it on the slave's I/O image. For example, write 0xAAAA to PQW 0 on the master; on the slave, PIW 0 should return 0xAAAA within one PROFIBUS cycle.
• On a PROFIBUS bus tester, monitor the bus signal: a healthy 1.5 Mbit/s differential signal is ±2.5 V across the line, with idle near +1 V (A low, B high) and toggling symmetrically.

Third-Party Master / Slave Configuration Notes

National Instruments cRIO as DP slave to D435-2 master

Use a NI cRIO module that supports PROFIBUS DP (e.g., NI 9543 / NI-9853 in some revisions, or the cRIO-908x with NI-Profibus). In the NI-Profibus Configuration Tool, import the GSD for the D435-2 (if the D435-2 is the slave being polled, the GSD is on the cRIO's PC side; if the cRIO is the slave, the cRIO's GSD goes into SCOUT HW Config). Configure the slot list to match exactly — for a single PIW/PQW word test, define one input slot of 1 word and one output slot of 1 word on both sides.

D435-2 as DP slave to a third-party master

When the D435-2 itself is the slave, the third-party master must be supplied with the D4x5-2 GSD. The slot count and slot type must be identical in the master's configuration and the D4x5-2's DP Slave Properties in SCOUT. The SIMOTION Direct data exchange via PROFIBUS DP documentation in the TIA Portal Help describes the equivalent configuration for two SIMOTION masters and can be adapted to mixed-vendor masters.

Mitsubishi and Honeywell PROFIBUS references

For reference, the Mitsubishi PROFIBUS DP-V0 Slave Interface (2D-TZ577) manual documents the same GSD-driven slot model for a Mitsubishi robot controller acting as a DP slave. The Honeywell / Saia-Burgess Profibus-DP and Profi-S-IO manual explicitly notes that "Simultaneous communication as DP slave and Profi-S-IO master is not possible via the onboard MPI interface" — a constraint that also applies to the D4x5-2 X136 when configured in mixed modes: the X136 port operates as either DP or MPI at any given time, and the configuration in HW Config must reflect that.

Troubleshooting Matrix

Configuration Parameters to Verify

Commissioning Checklist

1. Verify the PROFIBUS cable has the characteristic purple sheath and 150 Ω characteristic impedance; substitution with Ethernet cable is a frequent commissioning error.
2. Confirm exactly two terminators in the segment, at the physical ends.
3. Set the D435-2 station address in SCOUT before download; do not leave it at the default 0.
4. On the third-party side (cRIO, Mitsubishi, Honeywell), confirm the same baud rate, same slot count, and same I/O length per slot.
5. Use Online > PROFIBUS Diagnostics in SCOUT for a live view of slaves in Data_Exch.
6. Document the bus topology (T-drivers, repeaters, segment count) — the Acromag Introduction to PROFIBUS DP white paper is a good field reference for class-1 vs class-2 master behavior and bus segmentation rules.

FAQ