Siemens S7-300 Field PG: Resolving MPI/PPI Connection Failures

Problem Overview

When commissioning a SIMATIC Field PG running Step 7 V5.5 + SP4 against a SIMATIC S7-300 CPU 313 (6ES7 313-1AD01-0AB0), maintenance technicians frequently hit one of three blocking messages on the first connection attempt:

• "The connection to the module could not be configured." (PG/PC interface set to PC Adapter Auto)
• "With the set interface configuration, communication in Step 7 is not possible." (PG/PC interface set to PC Adapter PPI)
• "Online: communication link to the adapter damaged." (raised in the SELECT NODE ADDRESS window, no activity LEDs on the adapter)

All three errors are the same fault viewed through three different interface settings: the wrong cable is plugged in, or the wrong protocol is selected in the PG/PC interface applet. The USB/PPI Multimaster cable (order number 6ES7 901-3DB30-0XA0) that ships with many S7 spare-parts kits speaks PPI only. The S7-300 CPU 313 has no PPI port — its front X1 socket is a combined MPI/PROFIBUS-DP interface that runs MPI at the default 187.5 kbps. The cable is electrically compatible (RS-485, same DB9 pinout), but the protocol stack is not.

This article walks through the correct cable and interface selection, the upload procedure for an unknown station, the meaning of the SF (System Fault) LED when the loaded hardware configuration does not match the physical rack, and the diagnostic steps for bench-debugging an S7-300 station that has been in storage. The official Siemens support portal is SiePortal, where the S7-300 system manual, CPU 31x operating instructions, and PC Adapter USB driver packages are published.

Hardware Identification

Before touching any software setting, document the exact MLFB (machine-readable order number) of every component. Step 7 V5.5 binds the project to article numbers, and the diagnostic buffer reports deviations in those exact terms. Mixing up the last two characters of a 6ES7 3xx-xxxxx-xxxx article number is enough to light the SF LED.

Root Cause: PPI Is Not MPI

Both PPI and MPI use the same RS-485 physical layer and the same DB9 pin-out on the S7-300 X1 socket. The bus arbitration tokens, the telegram structure, and the default baud rates are different. The PG-side driver in Step 7 V5.5 produces the three error strings above whenever it tries to open a protocol that the destination CPU does not speak. The CPU firmware in the S7-300 family has never included a PPI service, so a PPI handshake is answered with silence, the driver times out, and the channel is closed with the misleading "damaged" wording.

The error "Online: communication link to the adapter damaged" is misleading English. It is a literal translation of the German diagnostic "Verbindung zum Adapter unterbrochen", which means "the connection to the adapter has been interrupted". The driver has issued an MPI/PPI telegram, the CPU has not acknowledged it within the timeout (typically 5 s), and the driver has closed the channel. The cable is not necessarily damaged; the protocol selection is wrong.

The same diagnostic is returned whether the wrong cable is plugged in, the wrong interface is selected, or the CPU is in power-down. Disambiguate the three cases with the SITOP Power 5 DC OK LED and the CPU DC5V LED before changing any software setting. If the DC5V LED is off, the fault is electrical, not protocol-related.

Cable, Bus Topology, and Interface Selection

Two physically valid options exist for connecting a Field PG to the CPU 313 X1 socket on the bench:

1. DB9 male-to-male cable into the Field PG COM port. Set the PG/PC interface to "PC Adapter (MPI)". This is the path that the user's DB9 cable was already wired for, but the PG/PC interface was still set to PPI in the original error. Switching the interface alone resolves the fault.
2. Siemens PC Adapter USB (6ES7 972-0CB35-0XA0, 6ES7 972-0CA23-0XA0, or 6GK1 571-1AA00) into a USB port of the Field PG. Set the PG/PC interface to "PC Adapter (MPI)" or "PC Adapter (Auto)". The "Auto" option scans first at 187.5 kbps, then 19.2 kbps, then 1.5 Mbps.

The X1 socket pinout is the standard PROFIBUS DP connector footprint:

For first commissioning on a Field PG that is known good, the DB9 cable at the default 187.5 kbps MPI baud rate is the simplest path. The MPI segment limit at 187.5 kbps is 50 m end-to-end. The cable between the PG and the CPU X1 is the only segment in this bench setup, so the 50 m budget is more than sufficient. For runs above 50 m, add a PROFIBUS repeater (6ES7 972-0AA01-0XA0) or move to a PC Adapter USB with fibre-optic media converters.

Step-by-Step: Establishing the Online Connection

Prerequisites

• Step 7 V5.5 + SP4 installed, with the latest cumulative hotfix for the target Windows version. On Windows 10 20H2 and later, install hotfix K7.5.5.4 or later to avoid the "S7DOS online interface not responding" regression.
• "SIMATIC PC Adapter" driver installed and visible in "Set PG/PC Interface". The driver entry should show "PC Adapter (MPI)", "PC Adapter (Auto)", and "PC Adapter (PROFIBUS)".
• CPU 313 powered from SITOP Power 5; 24 V DC present at terminals 1L+ and 2L+ of the digital modules; SITOP DC OK LED green.
• Memory card (MC 951 / 16 KB / 5 V, 6ES7 951-0KD00-0AA0) seated in the CPU slot. An empty or absent card is acceptable for an upload from RAM.

Procedure

1. Set the CPU mode selector to STOP. In STOP, the CPU accepts all programming functions without cycle timeouts. The SF LED may already be on — leave it; it is a symptom of a mismatched configuration, not the cause of the connection failure.
2. Plug the DB9 male-to-male cable into the Field PG COM1 (or COM2) and into the X1 socket of the CPU 313. Hand-tighten both locking screws. The CPU X1 socket uses the standard Siemens PROFIBUS connector footprint — a 9-pin sub-D with thumbscrews.
3. Open the Windows "Set PG/PC Interface" applet. Assign "PC Adapter (MPI)" to the access point of the application "S7ONLINE (STEP 7)".
4. In the Properties dialog of PC Adapter (MPI), set the MPI address of the PG/PC to 0 (the default) or 1, leave "Default" checked, and set the transmission rate to "187.5 kbps". The "Highest station address" parameter of the MPI network must be at least 31 to include the CPU's default address 2.
5. Launch SIMATIC Manager.
6. From the menu PLC → "Upload Station to PG" (or "Upload to PG").
7. SIMATIC Manager opens the MPI bus, scans for active nodes, and displays the discovered CPU 313 in the "Accessible Nodes" window. The "Accessible Nodes" view is the lowest-level diagnostic for verifying that the PG can see the CPU at all. If the CPU does not appear, the problem is electrical, not configuration-related.
8. Select the CPU and confirm. The project structure is mirrored to the PG, including the SDBs (system data blocks) that describe the hardware configuration.

After a successful upload, the online/offline comparison highlights every block where the on-card version differs from the uploaded version. The HW Config in the uploaded project is the basis for diagnosing the stored configuration that does not match the physical rack.

PG/PC Interface Configuration Matrix

The four common PG/PC interface settings and their effect on a CPU 313 are summarized below.

SF LED and the Hardware Configuration Mismatch

The CPU 313 reports "SF" (System Fault) when the loaded system data (SDB) describes a module population that does not match the actual rack, or when an I/O module raises a diagnostic interrupt that has not been acknowledged. In a bench setup that has been in storage, the most common SF cause is an SDB referencing a module article number that is not physically present, or a missing module that is in the SDB.

The diagnostic buffer is accessible via PLC → Diagnostics/Settings → Module Information, or from STEP 7 V5.5 via "PLC → Diagnose Hardware". Typical entries for this rack would be:

• "Module comparison: Module in slot 4 expected as 6ES7 322-1BL00-0AA0, found as 6ES7 322-1BH01-0AA0"
• "Parameter assignment error on module in slot 5: diagnostic interrupt not acknowledged"
• "I/O access error: write to output byte 0 in slot 4 — module not present"

After upload, the engineer must:

1. Open HW Config in the uploaded project.
2. Compare each catalog entry against the actual article numbers on the front of the modules.
3. Replace the entries and save / compile the hardware configuration (Station → Save and Compile).
4. Download the corrected hardware configuration to the CPU (PLC → Download to Module).

After a successful download and a STOP→RUN transition, the SF LED clears provided that no analog wire break, no missing 24 V on the load supply of the DO module, and no I/O fault remain. A memory reset (MRES) does not clear SF when the cause is a structural configuration mismatch. MRES resets work memory and re-runs the startup routine, but the SDB on the flash card is read again on the next power cycle and the fault returns.

Analog Module 6ES7 331-7KF01-0AB0: Configuration Cautions

The AI 8 × 12 bit module is the most misconfigured module in the S7-300 family. Eight channels are split into two groups of four, and each group has a wire-break detection jumper (channel 0 and channel 4) that must be set to "voltage" or "current" via a hardware jumper on the side of the module. The HW Config entry must match the jumper position; otherwise the analog value reads back as 7FFF (overflow) on the first channel and the module raises a diagnostic interrupt that lights SF.

For this bench setup with the 6ES7 331-7KF01-0AB0:

1. Verify the side jumpers: each group of four channels is either all voltage (default) or all current (4-wire transducer). Mixed voltage/current within a group is not supported.
2. In HW Config, double-click the AI 8 slot, set "Measurement type" to "Voltage" or "4-wire current" per the jumper.
3. Set "Measuring range" per channel. For ±10 V, select "±10 V". For 4–20 mA, select "4 wire, 4 to 20 mA".
4. Save and compile, then download the SDB.

After download, the AI 8 module enters cyclic conversion and the input bytes in the process image (PIW 288 through PIW 303 in a typical slot 5 placement) reflect the field-side voltage or current within 1 ms per channel. The status byte at PIW 288 / PIW 304 reports the channel quality in bit 0; a value of 1 indicates a fault (overflow, wire break, or out-of-range).

Memory Card and Project Persistence

The 16 KB flash card 6ES7 951-0KD00-0AA0 is the smallest flash card in the S7-300 family. The CPU 313 has 32 KB of integrated load memory. A 16 KB card replaces a portion of internal load memory; it does not extend it. If the project is larger than 16 KB, the CPU reports "Card size insufficient" at startup and the project is not loaded.

For bench debugging of this rack (one DI 32, one DO 32, one AI 8, no project code), the 16 KB card is sufficient. For any production code with multiple FBs, DBs, and SFCs, upgrade to a 64 KB card (6ES7 951-0KE00-0AA0) or larger.

When the card is present and contains a valid project, the CPU boots from the card on every power-up. When the card is empty or absent, the CPU boots from internal RAM. Internal RAM loses content on power failure unless the optional battery is installed and healthy. For a stored station that will be re-commissioned, always verify the battery voltage (> 2.7 V) and the battery date code before relying on RAM-resident project data.

Troubleshooting Matrix

Verification Checklist and Field-Commissioning Safety Notes

After the online connection is established and the corrected hardware configuration is downloaded, verify the system is fully online with the following sequence:

1. SIMATIC Manager shows the project in the offline/online view with green status icons on CPU 313, DI 32, DO 32, AI 8.
2. CPU mode selector reads RUN (or RUN-P); the RUN LED is steady green, the STOP LED is off.
3. The SF LED is off. The BF (Bus Fault) LED is off. The DC5V LED is steady green.
4. PLC → "Monitor/Modify" on a known DI point reflects the field-side 24 V within the configured input debounce time (typ. 3 ms for 6ES7 321-1BL00-0AA0).
5. PLC → Module Information → Diagnostic Buffer shows "No error" as the most recent entry.
6. Disconnect the MPI cable and reconnect; the connection is re-established without restart of the SIMATIC Manager.
7. Cycle power to the SITOP. The CPU 313 returns to RUN within 5 s with the SF LED off (assuming flash card present and battery healthy).

Before powering the rack from the SITOP Power 5 for the first time on a service bench, perform the following safety checks:

• Verify mains voltage selection on the SITOP (115 V / 230 V) matches the local mains. The 6EP1333-1SL11 supports 85–132 V and 170–264 V autoranging; verify the range, do not assume.
• Verify the protective earth (PE) connection to the SITOP. The PE terminal is on the input side; without PE, the SITOP reports "DC OK" but the leakage current path is undefined.
• Verify that no outputs are wired to actuators that could move on power-up. The DO 32 (6ES7 322-1BL00-0AA0) defaults to "0" on power-up, but if a previously loaded SDB has a startup value of "1" on a particular output, that output will energize within 50 ms of the CPU entering RUN.
• Verify that the analog inputs are not wired to current sources when the AI 8 jumpers are set to voltage. A 4–20 mA signal applied to a voltage-configured channel produces an out-of-range value and a diagnostic interrupt.

Once the bench checks pass, the procedures in this article apply unchanged to the field installation. Move the Field PG to the cabinet, plug into the CPU X1, and run "Upload Station to PG" to confirm the as-built configuration matches the engineered hardware configuration. Download the corrected SDB only after confirming that the actuator wiring is safe to energize.

Frequently Asked Questions