Troubleshooting MPI Communication: S7-315-2PN/DP to Magelis HMI

Problem Overview

An MPI (Multi-Point Interface) link between a Siemens SIMATIC S7-315-2PN/DP CPU and a Schneider Electric Magelis HMI fails to establish after the PLC was replaced. The original CPU was an S7-315-2DP, which communicated with the same HMI on the same RJ45 cabling. The user has confirmed the MPI addresses, local network settings, and RJ45 pinout match the previous working configuration, yet the bus remains silent on the new CPU. This is a recurring field issue when migrating from a CPU that exposes MPI on its DB9 front port to one that exposes MPI/DP on the same physical connector type but with different electrical and address defaults.

The diagnostic path must rule out four distinct causes before swapping hardware:

1. MPI protocol is not configured or disabled on the S7-315-2PN/DP interface.
2. MPI bus address conflict between HMI and CPU.
3. RS485 Data+/Data- polarity inversion between the HMI COM2 RJ45 socket and the CPU MPI/DP connector.
4. Wrong interface selected on the S7-315-2PN/DP (PROFINET port is not MPI-capable, the X1 MPI/DP port is the only MPI path).

MPI Protocol Fundamentals

MPI is Siemens' proprietary serial bus based on RS485 physical layer with a Siemens-specific token-passing data link protocol. It is the default programming and HMI protocol for S7-300/400 CPUs. Maximum bus length without repeaters is 50 m at 187.5 kbit/s, the most common HMI baud rate. Up to 32 nodes can be addressed (0 to 31, with reserved defaults for PG=0, OP=1, CPU=2).

Default MPI parameters for S7-300 CPUs are:

When migrating from a CPU where MPI worked, the new CPU must be assigned the same address it replaces, and the bus profile (baud rate, highest station address) must match the HMI configuration exactly. Mismatches do not produce an obvious error on the HMI; the HMI simply times out and shows "Connection failed" or "PLC not responding".

S7-315-2PN/DP vs S7-315-2DP Interface Comparison

Both CPUs are 6ES7315-series devices, but the interface layout differs in ways that drive this exact failure mode.

On the S7-315-2PN/DP, the DB9 connector labeled MPI/DP can operate in three modes selectable in STEP 7 / TIA Portal hardware configuration:

• MPI – master/slave token passing, default for HMI integration.
• DP-Master – PROFIBUS DP-V0/V1 master.
• DP-Slave – DP slave to a higher-level master.

If the port is left at its factory default or switched to DP, the HMI's MPI requests are ignored. The TIA Portal must explicitly set the X1 interface to "MPI" with the correct address and transmission rate.

Physical Layer: RJ45 on the Magelis COM2 Port

The Magelis HMI (for example XBTGT, HMIGTO, HMISCU series) provides MPI/PROFIBUS on its COM2 port through an RJ45 connector wired for RS485. The RJ45 on the HMI is not Ethernet; it is a Siemens-style RS485 pinout that matches the PROFIBUS cable standard (6XV1830-0EH10). This is the most common source of confusion when migrating HMI cabling: an installer sees RJ45 and assumes Ethernet.

Magelis COM2 RS485 RJ45 pinout (Schneider Electric standard, compatible with Siemens PROFIBUS cable):

The CPU DB9 MPI/DP pinout is the legacy Siemens PROFIBUS assignment:

The legacy CPU MPI/DP DB9 has Data+ on pin 3 and Data- on pin 8. The Magelis COM2 RJ45 has Data+ on pin 3 and Data- on pin 6. When the field cable was wired for the old S7-315-2DP, the Data+ / Data- mapping is fixed. Because the HMI RJ45 and CPU DB9 use different physical pins for the same logical signals, a passive 1:1 cable is not possible. A crossover wiring is required.

Root Cause: Data+/Data- Polarity Inversion

The single most common cause of "MPI worked on the old CPU, fails on the new CPU" with identical RJ45 cables is pin remapping, not polarity inversion. The cable was wired for the old DB9 pinout (pin 3 = Data+, pin 8 = Data-). On the new S7-315-2PN/DP, the DB9 pinout is unchanged, but the wiring into the HMI RJ45 may have been done by referencing the wrong pinout table (Schneider Magelis uses pin 3 = Data+, pin 6 = Data-, while some older XBT models use pin 4 / pin 5).

Two failure modes appear in the field:

1. Crossed polarity: HMI pin 3 (Data+) wired to CPU pin 8 (Data-) and HMI pin 6 (Data-) wired to CPU pin 3 (Data+). Bus stays in error state; no node responds.
2. Straight-through with wrong DB9 pin: HMI Data+ goes to DB9 pin 8 instead of pin 3, leaving the RS485 driver un-driven from the CPU side.

The corrective action is to swap the Data+ and Data- wires on one end of the segment (industry-standard practice: swap on the cable, not on the device). After the swap, the CPU and HMI see the same logical polarity on the bus and the token-passing sequence can begin.

MPI Bus Address Configuration

Address assignment is the second most frequent cause of this failure. On a working MPI bus the addresses must be unique and must be set in two places:

1. CPU side (TIA Portal or STEP 7): Properties → MPI/DP interface → Address. The S7-315-2PN/DP default is 2. If the previous CPU used address 2, the new CPU must also use 2.
2. HMI side (Vijeo Designer / EcoStruxure Operator Terminal Expert): The HMI's own MPI node address must be unique on the bus, default 1 for Magelis OP panels.

Procedure to set the CPU MPI address when the original project is available:

1. Open the STEP 7 / TIA Portal project matching the station.
2. Navigate to Devices & Networks → select the S7-315-2PN/DP → open Properties → MPI/DP interface.
3. Set Interface type = MPI.
4. Set Address to the value the HMI expects (typically 2).
5. Set Transmission rate = 187.5 kbit/s unless the HMI is configured for a different rate (1.5 Mbit/s or 12 Mbit/s are also possible on S7-300 MPI/DP combined ports).
6. Set Highest MPI address to 31 (default) or to the highest node physically on the bus to limit token rotation time.
7. Compile and download the hardware configuration to the CPU.

When the original project is not available, the only option is to connect a PG with STEP 7 and use Accessible nodes or Online & Diagnostics to inspect the current interface assignment. The MPI address can be changed online via Online & Diagnostics → Assign MPI address without a full project download, but the baud rate and bus profile can only be changed with a configuration download or by writing the system data blocks manually with an active connection.

TIA Portal HMI Connection Configuration (Reference)

For a complete HMI-to-S7-300 MPI link, the TIA Portal connection setup follows a specific path documented in the Siemens TIA Portal Help (V20) under Configuring an HMI connection via MPI. The full procedure is documented at the official Siemens TIA Portal documentation portal.

High-level steps for a working HMI connection via MPI in TIA Portal:

1. Add the S7-300 CPU to the project; ensure the X1 MPI/DP interface is set to MPI with the correct address and baud rate.
2. Add the HMI device (Basic Panel, Comfort Panel, or PC RT) under the same project.
3. Open Devices & Networks, select the HMI, and create a new HMI connection.
4. Set the connection endpoint to the S7-300 MPI/DP interface.
5. Configure the HMI's own MPI node address (default 1) and the same transmission rate as the CPU.
6. Compile and download the HMI configuration separately from the CPU configuration.

Reference documentation:

• Configuring an HMI connection via MPI – TIA Portal V20 documentation

Diagnostic Procedure When the HMI Project Is Unavailable

The user explicitly stated the original Magelis project file is not on hand, which is a common constraint in brownfield retrofits. The following procedure verifies communication and identifies the HMI's actual settings without needing the project.

1. Confirm physical wiring polarity. Use a multimeter to verify HMI RJ45 pin 3 (Data+) → CPU DB9 pin 3 (Data+) and HMI RJ45 pin 6 (Data-) → CPU DB9 pin 8 (Data-). If inverted, swap on the cable.
2. Connect a Siemens PG via MPI. Set the PG to MPI, address 0, baud 187.5 kbit/s, and attach to the CPU MPI/DP port. If the PG finds the CPU, MPI is operational and the issue is HMI-side (address, baud, or wiring to HMI).
3. Read the CPU interface assignment. In STEP 7 / TIA Portal Online & Diagnostics, read the CPU's MPI address, baud rate, and bus profile. Note these values.
4. Read the HMI's own MPI address. On most Magelis panels, navigate to Settings → Network → COM2 on the HMI itself. The HMI will display its configured MPI address and baud rate without needing the project file.
5. Compare HMI address to CPU address. They must differ. If both are 2, the HMI cannot take the token. Reassign the HMI to a free address (commonly 1) or the CPU to a free address (commonly 2, then HMI = 1).
6. Compare baud rates. Both must match. The default 187.5 kbit/s is the most reliable for HMI panels. Mismatches produce silent timeouts with no diagnostic on the HMI screen.
7. Set the HMI as bus master. The HMI must be a master on the MPI bus to read/write the CPU. If the HMI is configured as a passive listener, it will not poll and will appear "offline" from the CPU's perspective. In Magelis configuration this is the Master/Slave parameter under the COM2 MPI driver settings, default Master.
8. Check bus termination. MPI segments require termination at both ends. The S7-315-2PN/DP DB9 port has no built-in terminator. The HMI COM2 has no built-in terminator. A PROFIBUS connector with switchable terminator (Siemens 6ES7972-0BA12-0XA0) is required at each end of the segment. Missing terminators cause intermittent failures that look like address or baud mismatches.

Verification: Confirming the Link Is Live

After applying the corrective wiring and configuration, verify operation with the following checks:

1. HMI diagnostic screen: Magelis panels show a connection status indicator on the system screen. "Connected" / green confirms MPI is up.
2. CPU diagnostic buffer: In TIA Portal online view of the S7-315-2PN/DP, check Diagnostics → Diagnostic buffer. No MPI bus errors (SF / BF) should appear after the HMI polls.
3. PG accessible nodes scan: With a PG attached to the bus, run Accessible nodes. The HMI should appear in the discovered node list with its configured MPI address.
4. Live tag read: On the Magelis, configure a numeric display bound to a known tag (e.g., MW0 or a DB bit) in the CPU. The display should update at the configured polling rate. A static value or "####" indicates the HMI is connected to the CPU variable table but receiving a default/faulted value.
5. LED status on CPU: The S7-315-2PN/DP SF LED should be off, BF LED should be off (or briefly flashing during HMI poll), and the LINK LEDs on the PN port are unrelated to MPI operation.

Troubleshooting Matrix

Field-Proven Recommendations

1. Always use a Siemens PROFIBUS cable (6XV1830-0EH10) or equivalent with characteristic impedance 135 to 165 ohm. Standard Ethernet Cat5 cable is not rated for RS485 at the speeds used on MPI; it works at 187.5 kbit/s over short distances but is not recommended for new installations.
2. Label both ends of every MPI cable with the signal mapping (e.g., "HMI pin 3 → CPU pin 3, HMI pin 6 → CPU pin 8"). This eliminates the polarity question on every future retrofit.
3. When migrating an HMI/PLC pair, capture the active project files from both devices before the swap. For Magelis, the active project can be uploaded from the HMI itself through Vijeo Designer's Transfer → Get from HMI function if the HMI firmware allows it.
4. Keep a PG with STEP 7 / TIA Portal on site for any MPI troubleshooting; the Accessible nodes function is the fastest way to confirm bus health without an HMI.
5. Document the MPI bus profile (baud, highest address, master/slave roles) in the panel drawing so the next commissioning engineer does not have to reverse-engineer it from the hardware.

Safety and Wiring Precautions

MPI/DP bus cables carry low-voltage signals but the S7-300 systems typically include 24 VDC power wiring in the same cabinet. Observe the following before touching any conductor:

• De-energize the 24 VDC supply to the CPU and HMI before inserting or removing DB9 or RJ45 connectors. Hot-plugging MPI connectors can corrupt the CPU interface object and require a full hardware reconfiguration.
• Verify the shield is bonded to PE at one end only (typically the cabinet entry point) to avoid ground loops that can shift the RS485 common-mode voltage outside the transceiver's input range.
• Never apply 24 V to the HMI RJ45 pin 7 unless the cable is specifically a Siemens PG/PC RS485 repeater cable (6ES7901-4BD00-0XA0). Standard PROFIBUS cables do not carry 24 V on pin 7; if a custom cable ties 24 V to a CPU pin, the result is immediate driver damage.

FAQ