Troubleshooting Siemens S7-300 CPU 318-2 MPI Port Failure

1. Problem Overview

Maintenance engineers frequently encounter a situation in which a Siemens S7-300 CPU 318-2 continues to run its user program, exchanges process I/O over the backplane, and answers PROFIBUS DP requests on its second port (X2) — yet refuses every Multi-Point Interface (MPI) handshake from a programming device (PG), operator panel (OP), or text display (TP). Because MPI is the lowest-cost commissioning path and the default protocol for every STEP 7 PG/PC adapter, a silent MPI failure brings a line down at start-up or during service even though the CPU itself is running with a green DC 5 V LED and no system fault indication on the PLC side.

The classic symptom set is:

• STEP 7 reports "No connection to partner" or "Online: Cannot reach the target CPU".
• HMI tag polling stalls; the panel shows "PLC No Response" or a similar diagnostic string.
• PROFIBUS DP traffic on the second interface is unaffected.
• The diagnostic buffer contains an entry such as "Interface X1 fault" or "MPI connection aborted".
• An MRES (memory reset) does not restore MPI connectivity.

The remainder of this reference walks the engineer through isolating the failure to one of three root-cause classes — configuration drift, ESD/EMC damage from the bus cable, or hard failure of the RS-485 transceiver on the CPU’s X1 port — and presents the documented Siemens recovery paths.

2. CPU 318-2 Hardware and Interface Architecture

The CPU 318-2 is a high-end member of the S7-300 family. It mounts on a standard DIN rail together with a power supply (PS 307/PS 305), signal modules (SM), function modules (FM), and communications processors (CP). Two PROFIBUS-capable interfaces are integrated on the front panel:

Per the official Siemens product release "S7-300 — New CPU 318-2" (Industry Online Support entry ID 4348545), the integrated MPI interface can be converted to PROFIBUS DP and used as a master. Once the conversion is performed, the integrated communication services on that port (global data packets, S7 basic communication, S7 communication PUT/GET) are no longer available. This is a critical configuration dependency that often presents itself as a "failed MPI port" when in fact the port is simply not configured for MPI anymore.

The electrical layer of both interfaces is RS-485, isolated to a typical common-mode rating of ±35 V, with on-board bus termination that can be switched in by the connector. The transceiver die sits under the Sub-D shell; any voltage transients, ground-loop currents, or hot-plug arcs applied to pins 3 (RXD/TXD-P) and 8 (RXD/TXD-N) propagate directly into the ASIC. A block diagram of the front panel is shown below.

3. The MPI/DP Configuration Switch on X1

MPI is a proprietary Siemens subset of PROFIBUS operating at 187.5 kbit/s (or 19.2 kbit/s on legacy devices). It is a token-passing ring with a maximum address space of 0–126; address 0 is reserved for a PG, address 1 is reserved for the PG port on an MPI cable, and address 2 is the default CPU MPI address.

PROFIBUS DP on the same hardware runs from 9.6 kbit/s to 12 Mbit/s, supports DP-V0 cyclic I/O, DP-V1 acyclic services, and DP-V2 isochronous mode. The bus profile, gap maintenance, and GSD file semantics are completely different. The CPU 318-2 cannot speak both protocols on the same port simultaneously — the choice is made at hardware-configuration time in STEP 7 (HW Config → Properties of CPU 318-2 → Interface X1 → Interface Type).

The silent-DP-switch scenario plays out in the field as follows:

1. An integrator configures X1 as PROFIBUS DP to attach a distributed ET 200 station on the first port.
2. Years later, a maintenance engineer uploads the project and re-downloads it from a different PC. STEP 7 writes the active project back to the CPU, including the DP-mode setting.
3. Old HMIs on the MPI bus start reporting "No PLC response".
4. The engineer concludes the port is damaged.

The fix is a one-line change in HW Config. The lesson is to always export the active online configuration (PLC → Save to PC) before changing the offline project, and to check the Interface Type field rather than trusting the project name.

4. X1 Physical Layer and Bus Topology

4.1 Connector pinout

The X1 port uses a 9-pin female Sub-D connector with the following PROFIBUS pin assignment:

Pins 3 and 8 carry the differential signal. Pins 6 and 5 deliver the 5 V used by the bus-termination network inside the connector. A short between pins 3 and 5, 3 and 6, 8 and 5, or 8 and 6 will pull the bus down and the CPU will raise BF.

4.2 Cable and terminator

Use only purple-jacketed PROFIBUS cable (Siemens 6XV1 830-0EH10 or equivalent) with characteristic impedance 150 Ω. Both ends of every bus segment must have exactly one terminator engaged, and the terminator must sit at the physical ends of the bus, not in the middle. With the on-board terminator engaged (switch in the connector set to "ON"), the resistance between pins 3 and 8 measures 220 Ω. With terminator off, the reading is open-circuit. An open 220 Ω resistor inside the connector indicates a damaged terminator; replace the connector (for example, 6ES7972-0BA12-0XA0).

4.3 Bus topology and timing

A token-rotation time-out on an MPI segment with more than 32 devices or with a segment length above 50 m at 187.5 kbit/s presents as "MPI partner not reachable" rather than "port damaged" — the BF LED does not latch solid. Use this distinction to avoid ordering a spare CPU unnecessarily.

5. Symptom Matrix: LED Patterns and Diagnostic Buffer

The CPU 318-2 front panel carries four status LEDs relevant to interface diagnosis. Their behavior distinguishes the three failure classes.

Common diagnostic-buffer event IDs reported by STEP 7 (PLC → Diagnostic Buffer) for MPI port failures:

6. Root Cause Classes: Configuration, ESD/EMC, Hardware Damage

Three root-cause classes dominate field reports. They can be told apart by correlating the failure with recent activity in the cabinet.

6.1 HMI-side driver/receiver damage

An HMI panel that does not galvanically isolate its RS-485 transceiver can inject common-mode voltage onto the bus when its own power supply is faulted. If the panel shares a 24 V supply with the CPU and that supply is referenced to a different ground than the rest of the cabinet, the differential voltage between grounds can exceed the common-mode isolation of the S7-300 port. The first device to fail is the one nearest the ground-potential difference — frequently the CPU, which sits at the top of the bus segment.

6.2 ESD/EMC during hot-swap

Connecting a live MPI cable to a running CPU discharges the cable’s stray capacitance through the shield. If the operator touches the connector body to a grounded DIN rail before the data pins mate, the static charge path goes through the cable shield to the CPU’s Sub-D shell, which is bonded to chassis ground. The transient couples into the transceiver and can latch up the RS-485 driver. The CPU continues to scan, but the port no longer transmits.

6.3 Configuration switch (silent DP conversion)

The third and most easily missed cause is the configuration switch described in Section 3. A STEP 7 project that was downloaded with X1 set to "PROFIBUS DP" makes the port a DP master. The CPU does not raise BF for "no MPI traffic" because, from its point of view, it is a DP master waiting for slaves. An MPI master (the PG) attempting to take the token will time out and report the CPU as absent.

To distinguish the three classes, answer two questions before opening the cabinet:

1. Did the failure coincide with HMI maintenance, panel replacement, or a new MPI cable being attached? → suspect class 6.1 or 6.2.
2. Did the failure coincide with a project download, a hardware reconfiguration, or a firmware update? → suspect class 6.3.

7. Step-by-Step Diagnostic Procedure

Follow this sequence before authorising a CPU replacement. The procedure is non-destructive and takes 10–20 minutes.

Step 7.1 — Connect a known-good PG over the X2 PROFIBUS port

Open STEP 7 SIMATIC Manager. Set the PG/PC interface to "PC Adapter (PROFIBUS)" or the relevant CP 5611 / CP 5613 / CP 5711 driver. Connect to the CPU on its MPI address (default 2) over the X2 port. If the project is configured for X2 = DP master with no PG enabled, set the PG/PC interface to "PROFIBUS (DP)" and use the accessible-nodes browse.

Step 7.2 — Read the diagnostic buffer

PLC → Diagnostic Buffer. Look for the 0xE080, 0xE083, 0x4502 family of events. Note the time stamp of the first occurrence. If the first occurrence coincides with a known HMI intervention, the cause is hardware damage. If the buffer shows a clean run-up and the failure appears immediately after a project download, suspect configuration.

Step 7.3 — Inspect the HW Config setting for X1

Open the project’s HW Config. Select the CPU 318-2. Double-click the X1 interface. Verify "Interface Type" reads "MPI" (default) or the "MPI/PROFIBUS universal" option depending on the hardware catalog. If it reads "PROFIBUS DP", change it back to "MPI", save, recompile, and download. Power-cycle is not required for protocol-type changes on the 318-2, but the CPU may need to be STOP/RUN once.

Step 7.4 — Check the MPI cabling

Disconnect the bus connector from X1. Measure the bus terminator resistance between pins 3 and 8 with a multimeter. With the on-board terminator engaged (switch in the "ON" position), the reading should be 220 Ω. With terminator off, the reading should be open-circuit (OL). An open 220 Ω resistor inside the connector indicates a damaged terminator; replace the connector.

Step 7.5 — Test X1 with a PG-only loopback

Connect a PC/PG directly to X1 using a 6ES7901-0BF00-0AA0 MPI cable (or current equivalent PC Adapter). Set the PG/PC interface to "PC Adapter (MPI)". Power-cycle the CPU. From STEP 7, "Accessible Nodes" should return the CPU with MPI address 2. If the CPU appears only on X2 and never on X1, the X1 physical layer is dead.

Step 7.6 — Check the BF and SF LED pattern during the test

While the PG attempts to connect on X1, observe the BF LED for X1. A solid red BF LED that does not clear within 5 seconds indicates a permanent physical-layer fault — the RS-485 transceiver is shorted or open. A flashing BF LED indicates configuration or partner-side trouble, not CPU damage.

Step 7.7 — Memory reset and reload

If the buffer does not show a hardware fault event (0xE080), perform an MRES: turn the mode switch to MRES, hold for 3 seconds until the STOP LED flashes slowly, then within 3 seconds turn to MRES again. The CPU reloads its system data. Re-download the project and retest X1.

8. Workarounds and Repair Strategy

When the diagnostic buffer confirms a hard fault (0xE080 + permanent BF on X1 + no response to direct PG test), the X1 port’s RS-485 transceiver is not field-replaceable on the CPU 318-2 — it is soldered onto the main PCB. The Siemens-supported recovery path is CPU replacement, but three workaround paths buy time.

Always order the exact MLFB printed on the front of the failed CPU. Mixing firmware versions can change the behavior of S7 communication blocks; STEP 7 will warn if a project is downloaded to a CPU whose firmware is older than the one originally used to compile the project. When in doubt, use the "PLC → Save to PC" function on the suspect CPU before de-energising — the saved project is the authoritative offline source.

9. Verification Procedure

After repair, validate the recovery on the bench or in the panel before re-energising the line.

1. Power up the CPU. Verify DC 5 V green, STOP or RUN green, SF off, both BF off.
2. Connect the PG over MPI on X1. STEP 7 → Accessible Nodes must list the CPU on address 2 within 5 seconds.
3. Download the project. Verify the CPU performs a restart (RUN LED steady).
4. Connect the HMI. Verify polling resumes and tags update.
5. Connect a second PG and verify S7 routing from X1 MPI to X2 DP works (test with a CP 343-1 Lean on Ethernet if present).
6. Run the user program for 30 minutes under load and re-check the diagnostic buffer — no new 0xE0xx entries should appear.
7. If GD packets or S7 communication PUT/GET are used, verify them with a deliberate test from a partner CPU or a WinCC client.

10. Preventive Measures and Field-Commissioning Checklist

Most field failures of MPI ports on S7-300 stations are preventable with three practices.

10.1 Cabling discipline

Use only Siemens 6ES7901-0BF00-0AA0 (or current equivalent) MPI cables for PG connections. Never use unshielded cable. Both ends of every bus segment must have exactly one terminator engaged. The terminator must sit at the physical ends of the bus, not in the middle. Avoid daisy-chaining the PG port on connectors that are in the middle of a segment — the PG port passes the signal through but introduces a stub that reflects at high baud rates.

10.2 Ground bonding

Bond the cable shield to chassis ground at the cabinet gland with a 360° clamp — pigtails pick up HF noise. Avoid running the MPI cable parallel to VFD output cables; if a crossing is necessary, run it at 90°. Verify with a clamp-on ground-resistance tester that cabinet-PE to plant-PE measures below 1 Ω at the MPI cable gland.

10.3 Hot-swap protocol

Train operators to power down the HMI or PG before connecting the MPI cable. A live hot-plug of a cable that has been wound up on the floor is the single most common source of ESD damage to RS-485 ports in service vehicles and commissioning carts. If a hot-plug is unavoidable, touch the connector shell to the cabinet chassis first to equalise potential before mating the data pins.

10.4 Commissioning checklist

• Verify HW Config shows "MPI" on X1 before first power-up.
• Verify PG can browse the CPU on MPI address 2 within 5 seconds of power-up.
• Verify HMI tag polling at normal update rate before enabling process outputs.
• Export the final project to a versioned archive (TIA Portal / STEP 7 project on the engineering server).
• Note the firmware version of the installed CPU on the cabinet drawing.

11. Migration Note: S7-1500 as a Modern Alternative

The S7-300 is in the classic-support phase of its life cycle; spares are increasingly expensive and lead times for the CPU 318-2 are stretching. For greenfield installations or for stations where the MPI protocol itself is not contractual, a migration to S7-1500 is the long-term answer. The relevant differences for an MPI-replacement project are:

Siemens provides a migration path with the S7-1500 migration kit and the SIMATIC Automation Tool. For users who must retain MPI on a brownfield site, the CP 343-1 Lean can be added to an existing S7-300 station to provide Ethernet PG access without replacing the CPU.

FAQ