Troubleshooting CPU315-2DP MPI Connection in SIMATIC Manager

Troubleshooting CPU315-2DP MPI Connection Failures in SIMATIC Manager

A field engineer attempts to upload the program from a SIMATIC S7-300 CPU315-2DP to a laptop running STEP 7 / SIMATIC Manager. The serial port on the laptop is proven good because the same machine communicates with non-Siemens PLCs. The PC Adapter is detected, the correct COM port is chosen, and Upload Station to PG is clicked — but the connection fails. This is one of the most common upload scenarios in legacy S7-300 service work, and in the majority of cases the root cause is not the laptop, the cable, or the CPU, but the class of adapter sitting on the MPI bus. This reference walks through identification, configuration, and verification procedures to recover the connection.

1. Problem Definition

The reported symptom chain is consistent across hundreds of CPU315-2DP service cases:

1. STEP 7 / SIMATIC Manager starts without errors.
2. A new project is created without the wizard.
3. PG/PC interface is set to PC Adapter (Auto).
4. The expected COM port is selected.
5. PLC → Upload Station to PG produces a connection error, an MPI timeout, or the error message Online: Cannot reach the partner.

When the same laptop successfully connects to other vendor PLCs through the same physical COM port, the COM hardware, the USB-to-serial driver, and the PCMCIA / ExpressCard stack are exonerated. The fault lies somewhere in the Siemens-specific chain: adapter identity, driver selection, MPI bus parameters, or CPU interface configuration.

2. Root Cause: Wrong Adapter Class

The diagnostic shortcut used in service work is to read the Siemens order number from the adapter housing and compare it to the catalog of supported device classes. Three classes of device are commonly confused:

• PC Adapter (MPI/DP ↔ RS232 or USB) — designed for direct PG-to-PLC programming traffic.
• TS Adapter (Teleservice Adapter) — designed for dial-up / WAN remote service over an external modem.
• HMI Adapter — historically used for OP/TP panels and limited protocol bridging.

A TS Adapter is a perfectly functional Siemens product, but it is not a drop-in replacement for a PC Adapter. It does not advertise itself to the PG/PC interface as PC Adapter (Auto) in the same way, and STEP 7 will not establish a programming session through it using the standard PC Adapter driver. Using a TS Adapter where a PC Adapter is required manifests exactly as the symptom above: the driver loads, the COM port opens, no bus node is reachable, and the upload fails.

3. PC Adapter vs TS Adapter: Identification Matrix

If the unit in your toolbox does not match a PC Adapter line, the upload problem will not be solved by adjusting STEP 7 options. The corrective action is to obtain the correct adapter class. No firmware tweak, baud-rate adjustment, or PG/PC interface parameter will turn a TS Adapter into a programming interface.

4. CPU315-2DP Communication Interfaces

The CPU315-2DP exposes two physical ports on the front panel:

• X1 (MPI) — used for programming, OP/panel connection, and MPI bus nodes. This is the port to which the PC Adapter connects for an upload.
• X2 (DP) — the PROFIBUS-DP master interface, used for distributed I/O. It is not the default target for an upload station operation, although STEP 7 can be routed through it if the project topology allows.

The MPI port is a 9-pin D-sub female connector wired to the PROFIBUS RS-485 physical layer. Default MPI parameters for the CPU315-2DP at the time of delivery are:

These values can be read and changed under STEP 7 → HW Config → CPU properties → MPI interface. If the field site has modified the highest MPI address or the baud rate, the PC Adapter must be set to match. PC Adapter (Auto) attempts bus parameter discovery automatically; PC Adapter (MPI) requires the operator to specify the address and baud rate. If discovery is failing, fall back to the explicit driver entry.

5. PG/PC Interface Configuration Procedure

1. Open the Windows Control Panel → Set PG/PC Interface (the entry installed by STEP 7). The exact location varies by Windows version; on Windows 10/11 it is normally reached from the SIMATIC Manager menu Options → Set PG/PC Interface.
2. In the Interface Parameter Assignment list, locate the entry that matches the physical hardware.
   • For the USB PC Adapter A2: choose PC Adapter (Auto) or PC Adapter (MPI) with the matching USB COM port.
   • For the legacy RS232 PC Adapter: choose PC Adapter (MPI) with the assigned COM port.
   • Do not select any of the TS Adapter entries for an upload job.
3. Click Properties and verify:
   • COM port number matches the operating system (Device Manager → Ports).
   • MPI address of the PG is in the range 0–31 and does not collide with the CPU (CPU is typically 2).
   • Highest MPI address is high enough to include the CPU (default 31 is safe).
   • Baud rate is 187.5 kbit/s unless the site has been re-engineered.
4. Click OK and close the dialog. STEP 7 will commit the selection.

6. Step-by-Step Upload Procedure

Once the PG/PC interface is correctly assigned and the physical adapter is confirmed to be a PC Adapter, the upload is a six-step operation:

1. Launch SIMATIC Manager.
2. Select File → New → New Project (without wizard). Give the project a name that identifies the plant and the CPU order number.
3. From the menu select PLC → Upload Station to PG.
4. STEP 7 broadcasts an MPI discovery frame. If the CPU responds, the Online node list populates with the CPU's MPI address and order number (for example, CPU 315-2 DP / 6ES7315-2AH14-0AB0).
5. Select the target CPU in the list and click Upload.
6. SIMATIC Manager transfers the S7 program (blocks, system data, hardware configuration) into the local project. Confirm by expanding the Blocks container and verifying OB1, FB/FC instances, and the system data blocks are present.

7. Accessible Nodes Diagnostic Path

When Upload Station to PG does not list the CPU, the next diagnostic step is PLC → Accessible Nodes. This menu issues a single broadcast and displays every node the PC Adapter can see on the bus, regardless of project context. The output is a small object tree that reveals:

• Whether the PC Adapter is even on the bus (the entry for the PG/PC address 0 or 1 will appear if the adapter is functional).
• The MPI address of the CPU (the tree entry for the CPU315-2DP will appear at the address configured in HW Config).
• Any other MPI participants, including OP panels and DP slaves (DP slaves will only be visible if the PC Adapter is on the DP segment or if the route is configured).

If Accessible Nodes returns an empty list while Upload Station to PG also fails, the fault is on the physical layer. The PC Adapter, the MPI cable, the bus terminator, and the CPU MPI port must each be checked. If Accessible Nodes lists the CPU and Upload Station to PG still fails, the fault is at the project / protocol level — most often a PG/PC interface mis-assignment or a wrong driver class.

8. Common Error Causes and Resolutions

9. Verification Checklist

After applying a corrective action, verify the upload with the following sequence. Each step has a deterministic pass/fail outcome; do not skip ahead.

1. PG/PC Interface assignment: In SIMATIC Manager, Options → Set PG/PC Interface shows the correct driver and the correct COM port.
2. Adapter LED state: The PC Adapter LED labeled ACTIVE or ONLINE illuminates when the CPU replies. If it never illuminates, the bus is not reaching the CPU.
3. Accessible Nodes: PLC → Accessible Nodes returns at least the PC Adapter's own address and the CPU315-2DP entry.
4. Upload Station to PG: completes without error and populates the project's Blocks folder.
5. Block integrity: open OB1 and verify the network count and program structure match the field documentation. Open the system data blocks (SDB) and verify the hardware configuration matches the rack layout.
6. Online diff: PLC → Compare Online / Offline shows zero differences for the uploaded blocks. This is the strongest single confirmation that the upload captured the live program state.

10. CPU315-2DP Order Numbers and Replacement Notes

The CPU315-2DP family has been manufactured in several firmware revisions. The order number (MLFB) printed on the front of the module must be matched when ordering spares or replacement CPUs. Typical entries encountered in the field:

When the CPU is replaced in the field, an uploaded backup alone is not always sufficient. The system data blocks in the backup must be re-loaded to the new CPU, and the MPI address, the DP master parameters, and the keep-alive / retentive memory selections must be verified to match the project documentation. STEP 7 will warn on a firmware mismatch between the project and the replacement CPU — resolve the warning by re-translating the hardware configuration, never by ignoring it.

11. Field-Commissioning Notes

Engineers moving between sites often carry a single PC Adapter in a service kit. Two practices reduce the rate of CPU315-2DP upload failures in the field:

• Label the adapter: physical adhesive label with the Siemens part number. Two otherwise identical-looking PC Adapter housings can carry different firmware versions or even different product classes. The label removes ambiguity at the cabinet door.
• Carry an MPI bus terminator: a 220 Ω PROFIBUS D-sub terminator and a 390 Ω termination pair (commonly sold as a single 9-pin D-sub plug). Many field cabinets have one terminator missing, and the resulting reflections will cause an upload to fail even when the bus is otherwise wired correctly.
• Document the CPU's MPI address before powering down: if the CPU retains its MPI address across power cycles, the address can be read from the operator panel or the diagnostic buffer. If it has been reset to default (address 2), this is the address STEP 7 will use for an upload attempt.
• Use the explicit driver, not Auto, on the first attempt: PC Adapter (MPI) with manual parameters removes the auto-detection race that causes intermittent failures on long MPI cables or on bus segments with high capacitance.
• Verify the STEP 7 version against the CPU firmware: a project created in STEP 7 V5.x can be uploaded to any CPU315-2DP variant that supports S7-300 instruction set. A TIA Portal project is not interchangeable with a SIMATIC Manager project; cross-load is not supported.

12. Frequently Asked Questions