Resolving S7-300 CPU 312C 'PC Adaptor Damaged' MPI Connection

Problem Overview

The CPU 312C (order number 6ES7312-5BF04-0AB0 and earlier -C variants in the S7-300 family) occasionally returns a "PC adaptor damaged" dialog when an engineer attempts to download a STEP 7 project from SIMATIC Manager. The same fault typically blocks the "Display Accessible Nodes" (PG/PC → "Display Accessible Nodes") function, so the engineer cannot read station addresses, online diagnostics, or perform a download at all. Both the legacy PC-Adapter (serial, RS-232 to MPI) and the modern USB PC-Adapter (order number 6ES7972-0CB20-0XA0) can trigger the same symptom if the bus parameters, the physical DIP switch, or the MMC content are inconsistent.

The fault usually points to one of three real problems:

1. Bus parameter mismatch between the PC-Adapter firmware and STEP 7 PG/PC interface (baud rate, segment timeout, master role, max node count).
2. Stuck or mis-set DIP switch on the serial PC-Adapter (19.2 kbps vs. 38.4 kbps).
3. Corrupted hardware configuration in the load memory (MMC), which prevents the CPU from bringing up its MPI interface in a state the programming device can negotiate with.

Affected Hardware and Firmware Context

The CPU 312C and the rest of the S7-300 V3 generation require the MMC for firmware and project storage. If the MMC contains a hardware configuration that the current STEP 7 version cannot parse - for example, an SDB referencing a module that is no longer in the rack - the CPU may come up in STOP with a request for overall reset, but the MPI port still answers in a degraded mode that STEP 7 reports as "adaptor damaged".

Root Cause Analysis

STEP 7 raises the PC adaptor damaged popup (error class 0x0311 to 0x0315 depending on sub-cause) when the PC-Adapter driver detects a hardware handshake failure, a timeout, or a parameter mismatch before any S7 connection is opened. For the CPU 312C specifically the most common underlying causes are:

1. Speed mismatch. The serial PC-Adapter is hard-capped at 19.2 kbps or 38.4 kbps by a 2-position DIP switch. STEP 7 by default attempts 187.5 kbps. If the switch reads 19.2 and STEP 7 expects 38.4, or vice-versa, the driver aborts.
2. Master role not asserted. The PG must be the only active master on the MPI bus. With several CPUs online, the driver cannot guarantee token passing and aborts.
3. Timeout too aggressive. The default 3 s timeout is borderline for legacy serial adapters. Increase to 10 s.
4. Node count too high. The default MPI profile can request 126 addresses; serial adapters only support 31. Lower to 31.
5. Corrupt SDB on MMC. A previously downloaded HW Config that does not match the current rack produces an MPI bring-up failure. MRES does not erase SDBs on the MMC - it only clears work memory and the diagnostic buffer. The hardware configuration must be removed by erasing the MMC.

Step 1 - Validate the PG/PC Interface

1. Open Start → SIMATIC → STEP 7 → Set PG/PC Interface.
2. Select the access point S7ONLINE (STEP 7) → PC Adapter (MPI) → PC Adapter (PROFIBUS) for the legacy serial, or PC Adapter USB (MPI/PROFIBUS) for USB.
3. Click Properties and apply the following values, which match the Siemens PC Adapter FAQ 23898073:

4. Set the local PG/PC MPI address to a high unused value, e.g. 20, so it does not clash with any default CPU address 2.
5. Click OK, close STEP 7, and reboot the PC. Reopen SIMATIC Manager before connecting.

Step 2 - Verify the Physical PC-Adapter

For the RS-232 PC-Adapter (6ES7972-0CA20-0XA0):

• Open the small hatch on the adapter and inspect the 2-position DIP switch. Position 1 = 19.2 kbps, position 2 = 38.4 kbps. Older units have a 4-position switch where SW1 selects baud, SW2-SW4 are unused.
• The switch is known to become "sticky" - the slider looks centred but the internal contact is half-open. Cycle it: slide fully to one end, back, and then to the desired position.
• Confirm the 24 V power LED is solid green; flashing or off indicates the MPI bus is shorted or the supply is below 19 V.

For the USB PC-Adapter (6ES7972-0CB20-0XA0):

• In Set PG/PC Interface, the device dropdown must show USB, not COM port. If a virtual COM port driver was installed in error, the bus will not come up.
• Baud rate selection is firmware-controlled - the speed dropdown in STEP 7 directly programs the adapter. Use 187.5 kbps for first contact.
• Verify the USB driver is at least V2.0.4; older drivers cannot read the USB descriptor and report "adaptor damaged".

Step 3 - Memory Reset (MRES) Procedure

MRES clears the work memory, the diagnostic buffer, and the run-time DBs. It does not erase the SDBs on the MMC. Use MRES as the first recovery step; if the fault persists, proceed to Step 4 - MMC Erase.

1. Set the mode selector to STOP (the key must be in the white position).
2. Hold the MRES switch toward the spring-loaded MRES position. The amber/yellow STOP LED will:

• First flash slowly twice (~2 s on / 2 s off).
• Then change to a steady amber glow after approximately 5-7 s.
• Release the switch briefly, then press and hold MRES again.
• The amber LED will now flash rapidly (> 2 Hz). Release immediately when the rapid flash starts.

3. The CPU is now reset. All RAM-resident data blocks, flags, and the diagnostic buffer are cleared. The SDBs and the HW Config remain on the MMC.
4. Cycle power to the rack to make sure the bring-up is clean.

Reference: SIMATIC S7-300 CPU 31xC Operating Instructions (entry ID 19537634), section 7.2 "Memory reset".

Step 4 - Erase the MMC (Deletes the Hardware Configuration)

This is the procedure that removes the offending SDB set from the load memory. There are two approved methods.

Method A - In-CPU Erase via Mode Selector

1. Power down the rack, remove the CPU 312C.
2. Remove the MMC from the slot on top of the CPU.
3. Insert the MMC into a different S7-300 CPU type, e.g. a CPU 314 or CPU 315-2 PN that you know is healthy and has its own power supply. The other CPU will detect an unknown MMC and offer to format it.
4. Confirm Yes to format. The MMC is wiped, including all SDBs and the HW Config.
5. Reinsert the MMC into the CPU 312C and power up.
6. The CPU will boot with no configuration, the STOP LED will blink at 1 Hz, and the MPI port will respond to PG/PC scans with the default address 2.

Method B - External Prommer (Field PG or SIMATIC Field PG)

1. Remove the MMC from the CPU and insert it into the external MMC prommer (e.g. SIMATIC Field PG with integrated prommer).
2. Open SIMATIC Manager and choose File → S7-Memory Card → Delete.
3. Confirm deletion. The MMC is wiped to factory state.
4. Reinsert into the CPU 312C and power up.

Step 5 - Rebuild and Download a Clean Configuration

1. Open your STEP 7 project. In HW Config, right-click the CPU 312C and select Object Properties → MPI Interface Properties. Confirm:

2. Compile and save the HW Config (Station → Save and Compile).
3. Use PLC → Download to Target System from HW Config, not from the project tree. This forces the full SD

2. Compile and save the HW Config (Station → Save and Compile).
3. Use PLC → Download to Target System from HW Config, not from the project tree. This forces the full SDB refresh.
4. When STEP 7 prompts "Do you want to overwrite the existing configuration?", click Yes.
5. After the download, the CPU should switch to RUN within 5 s if the program is consistent.

Step 6 - Verification Procedure

1. Open PLC → Display Accessible Nodes. The CPU 312C must appear with address 2.
2. Open PLC → Online → Diagnostic Buffer. The most recent entries should show "Power-on", "STOP caused by", or "RUN" with no SDB-format errors (SF LED off).
3. Open PLC → Module Information. All configured modules should be present in slot 1-N with status OK.
4. Test a small edit: toggle a single bit in OB1, download, verify the change is reflected in the VAT table.

Communication Parameter Reference Table

Troubleshooting Matrix

Edge Cases and Field Notes

• USB adapter on a virtualised engineering station: VMware or Hyper-V can re-route the USB descriptor and cause the PC-Adapter to enumerate on the wrong pipe. Use a native Windows host or pass-through the USB device directly.
• STEP 7 V5.4 SP5 and CPU 312C V3.3: the HW Config library must be at least HSP0186 to include the latest 312C GSD. Without it, the download will succeed but the SDB will reference modules with firmware the CPU cannot find, producing an SF on first RUN.
• MMC write protection: MMC cards for S7-300 do not have a write-protect tab; protect them at the project level by exporting a final SDBL snapshot before live editing.
• 24 V supply to the PC-Adapter: the RS-232 adapter draws up to 100 mA from the MPI connector. If the CPU's 24 V sensor supply is loaded above 80 %, the adapter may brown out and report damage. Power the adapter from a separate 24 V source if in doubt.
• Multiple PG on the bus: if another PG is online on the same MPI, the PC-Adapter driver can lose the token and time out. Disconnect the second PG before troubleshooting.

FAQ