Troubleshooting CP5512 PROFIBUS Missing Master Node on S7-300 CPU

Troubleshooting CP5512 PROFIBUS Missing Master Node on S7-300 CPU 318-2

When a Siemens CP5512 programming adapter scans the PROFIBUS segment attached to an S7-300 CPU 318-2, every DP slave appears in the Accessible Nodes list, but the master CPU itself (address 2) is missing. The PG/PC cannot open the project online, the upload-to-PG function fails, and the entire machine stays down. This article documents the root causes of this specific symptom, the verification path, and the recovery sequence for engineers who must bring the line back into production without replacing the PLC.

1. Symptom Definition

The exact symptom must be captured before any diagnostic step is executed. In the reported case:

• Menu path used: PLC > Upload Station to PG > View opens the Accessible Nodes window inside STEP 7.
• All 54 slaves behind the DP/DP coupler are listed and respond.
• The DP/DP coupler itself (address 3) is listed.
• The CPU master (address 2) is not listed.
• The CPU 318-2 has two physical interfaces: the MPI/DP combined port (X1) and a second DP port (X2) on most 318-2 variants. The accessible-nodes scan only returns the master when the CP5512 sits on the same physical segment as the master's own DP interface.

The above combination — slaves visible, master missing — is the signature of one of the conditions listed in Section 2.

2. Root Cause Analysis

For a DP master to appear in the Accessible Nodes table, the CP5512 must receive an FDL response from the master at PROFIBUS data-link layer. If the master is silent on the bus segment the CP5512 is connected to, it is invisible to the scan regardless of STEP 7 settings. The dominant root causes for the exact symptom are:

2.1 CP5512 attached to the wrong physical segment

The CPU 318-2 has two DB-9 ports. The first port is normally configured as MPI or PROFIBUS master. If the engineering station is plugged into the slave-side PROFIBUS segment of the DP/DP coupler, the coupler blocks FDL frames between segments, and the master simply does not exist on that segment. The 54 slaves are visible because the CP5512 is sitting on their segment, but the master is hidden behind the coupler.

2.2 Master's DP interface in slave mode or disabled

If the master's PROFIBUS interface has been reconfigured as a DP slave (a configuration that can occur after a corrupted download, partial TIA migration, or firmware mismatch) the CPU will not respond to master-class FDL polls. The hardware configuration in STEP 7 may show the interface as "DP master", but the actual interface database on the CPU may have been overwritten with a slave image.

2.3 PROFIBUS address conflict on segment 2

If two devices on the scanned segment share address 2, the token-passing protocol excludes one of them. Slaves are typically polled individually, so they may still respond to diagnostic reads, but the master-class FSL/FMA services return errors.

2.4 Bus termination or cable fault isolating the master

An open termination resistor at the master end, a broken PROFIBUS connector pigtail, or a shielded cable with the shield lifted by a recent maintenance event will leave the master electrically present but functionally silent. CP5512 will still see everything downstream of the fault if the fault is on the segment between the master and the first repeater/coupler.

2.5 CP5512 driver, firmware, or interface parameter mismatch

The CP5512 (catalog 6GK1551-2AA00) requires a specific PC interface parameter assignment in Set PG/PC Interface. If the assignment points to a non-existent COM port, an MPI-only profile, or a baud rate the master does not support, the master's response is interpreted as no response.

2.6 Windows XP and parallel-port/USB stack degradation

CP5512 is USB-based but uses the Siemens S7DOS patch and the SIMATIC NET CP5512 driver stack. After extended uptime or after a Windows XP security update, the S7DOS helper service can fail silently, causing all PROFIBUS master-class queries to time out. Slaves may still appear because the scan falls back to a lower-priority service.

3. Pre-Diagnostic Inventory

Before opening STEP 7, record the following on a paper sheet — the value of these data points is highest when the machine is down:

4. Diagnostic Procedure

Execute the steps in order; do not skip the physical-layer checks. The fastest recoveries on this class of fault historically come from the physical layer, not from STEP 7 settings.

4.1 Confirm CPU LED state and fault class

1. Power the S7-300 rack; do not assume the CPU is in RUN.
2. Read the LED pattern of the CPU 318-2. Compare against the Siemens S7-300 CPU 31x LED patterns reference.
3. If the SF (system fault) LED is solid red and BF (bus fault) is flashing, the CPU is detecting a PROFIBUS error on its DP interface. This rules out a CP5512-side problem and points to the master's own interface or its segment.
4. Note whether the DC5V LED on the CPU is solid green. A missing DC5V or an under-voltage condition can be caused by an overloaded backplane or a shorted PROFIBUS connector shielding wire.

4.2 Inspect the CP5512 physical attachment

1. Disconnect the CP5512 from the DP segment.
2. Inspect the DB-9 connector for bent pins, broken retainer screws, and missing termination switch position. The CP5512 ships with a 9-pin sub-D and a switch block that selects on/off termination. Confirm the switch is OFF when the CP5512 is mid-segment.
3. Reconnect the CP5512 to a known-good DB-9 pigtail and tighten the screws to 0.4 Nm.
4. Open Windows Device Manager > Universal Serial Bus controllers and confirm the CP5512 enumerates as SIEMENS CP5512. If a yellow bang is present, the driver stack is broken (see Section 4.6).

4.3 Try the MPI port on the CPU directly

The CPU 318-2's first port is combined MPI/DP. If the port is in MPI mode, the master's FDL profile is published on the MPI profile and the CPU is reachable from the MPI side even when the PROFIBUS DP side is degraded.

1. Disconnect the CP5512 from the PROFIBUS segment.
2. Plug the CP5512 directly into the X1 MPI/DP port of the CPU.
3. Open Set PG/PC Interface and create an assignment of type PC Adapter (MPI) → CP5512 with the PC Adapter profile set to MPI, 187.5 kbps, station address 0, master address 0.
4. Open STEP 7 and run PLC > Display Accessible Nodes.
5. If the CPU appears at address 2, the CPU is alive; the original fault is on the DP side of the CPU. Skip to Section 4.5.
6. If the CPU still does not appear, the CPU's own communications interface may be dead. Proceed to Section 4.7.

4.4 Try the CP5512 on a known-good segment

Validate the CP5512 hardware itself by attaching it to a spare PROFIBUS segment with a known good S7-300 master. If the spare master appears in Accessible Nodes, the CP5512 is healthy. The original fault is on the production machine, not on the engineering station.

4.5 Verify the DP/DP coupler segment isolation

The DP/DP coupler (typical MLFB 6ES7158-0AD01-0XA0) routes only the data configured in its GSD-based mapping. It does not forward FDL broadcast or FDL diagnostic services. As a result, the master will never appear in Accessible Nodes on the slave-side segment of the coupler.

1. Confirm the CPU 318-2's X2 (second DP) port terminates the segment on the master side. The DP/DP coupler is the device that starts the slave segment.
2. Plug the CP5512 into a tap on the master-side segment of the DP/DP coupler, not on the slave side.
3. Re-run PLC > Display Accessible Nodes. The CPU 318-2 should appear at address 2.

4.6 Reset the CP5512 driver stack on Windows XP

1. Open Control Panel > Add or Remove Programs and remove SIMATIC NET PC Software if present.
2. Unplug the CP5512.
3. Delete the registry key HKLM\SOFTWARE\Siemens\SINEC after exporting it as a backup.
4. Reboot Windows XP.
5. Reinstall the CP5512 driver from the original SIMATIC NET CD matching the STEP 7 version (typically V8.x or V13 SPx).
6. Plug the CP5512 back in and verify the S7DOS helper service starts: sc query s7dos in a command prompt should report STATE: 4 RUNNING.

4.7 Inspect the master interface in HW Config

1. Open the STEP 7 project and navigate to HW Config.
2. Double-click the DP interface of the CPU 318-2.
3. Confirm the Operating Mode is DP Master and not DP Slave or Deactivated.
4. Confirm the PROFIBUS address is 2.
5. Confirm the bus parameters (Tslot, Tset, Ttr, etc.) match a real, documented profile. A corrupted configuration with Tslot = 0 will silence the master.

4.8 Power-cycle the master interface

1. Switch the CPU to STOP using the mode selector.
2. Cycle power on the entire S7-300 rack; do not perform a memory reset (MRES) unless a complete re-download is acceptable.
3. Wait for the CPU to complete its self-test. The STOP LED should remain solid amber.
4. Re-run PLC > Display Accessible Nodes from the CP5512 on the master-side segment.

5. Recovery Path Once the Master is Visible

Once the CPU 318-2 appears in Accessible Nodes at address 2, perform the upload to a new STEP 7 project immediately. This protects the program source even if the CPU later fails:

1. In STEP 7, select PLC > Upload Station to PG.
2. Choose the visible CPU and confirm.
3. Save the uploaded project to a network share, not to a local Windows XP profile. Windows XP is end-of-life and the disk image is at risk.
4. Compare the uploaded S7 program block by block against the most recent backup, if any. Look for OB82, OB86, OB122 blocks that may have been added by the running machine's diagnostic logic.

6. Permanent Corrections

The temporary recovery described above should be backed by permanent engineering changes:

• Add a second programming tap on the master-side segment of the DP/DP coupler. Place a passive PROFIBUS connector with a PG socket on the master segment so future CP5512 connections do not require opening the slave-side cabinet.
• Add a PG routing entry in the S7 project so that the CP5512 can reach the master through the slave segment when needed. Configure PG routing in NetPro and download the routing table to the CPU.
• Replace Windows XP with a supported OS. Windows XP SP3 is required for STEP 7 V5.5 SP4 onward, but security patches since 2014 are not available and SIMATIC NET versions newer than V14 may not install correctly.
• Document the bus topology with PROFIBUS cable lengths, terminator locations, and a fixed baud rate in the project documentation. A 1.5 Mbps segment of more than 100 m on a copper cable is at the limit and will degrade over years.
• Schedule a CP5512 firmware update to a current version. The CP5512 was last updated by SIMATIC NET to firmware that supports the PC Adapter USB driver profile used by STEP 7 V5.5 and TIA Portal V13 onward.

7. Escalation Checklist

If the master still does not appear after completing Sections 4.1 through 4.8, escalate to Siemens regional support with the following data ready:

1. CPU diagnostic buffer dump (read via STEP 7 with the MPI connection in Section 4.3, even if the DP side is silent).
2. SF LED state and BF LED state, photographed.
3. List of slaves that do appear in Accessible Nodes, with their addresses and GSD versions.
4. Set PG/PC Interface screenshot showing the active assignment.
5. CPU MLFB and firmware version.
6. CP5512 driver version and Windows XP service pack level.

When opening a Siemens support request, reference the offline diagnostic buffer events. A 318-2 with a failed DP interface typically logs entries such as Event ID 0x394A (interface error) or 0x35CE (PROFIBUS DP bus error). These hex codes are recognized by the Siemens support tool and accelerate triage.

8. Use TIA Portal to Display Accessible Devices

If the engineering station can be migrated to TIA Portal (a longer-term project), the procedure for displaying accessible devices is documented in the official TIA Portal help. The procedure is: double-click "Update accessible devices" below the selected interface in the project tree. This forces a fresh scan on the selected PROFINET or PROFIBUS interface. The TIA Portal implementation handles some edge cases that STEP 7 V5.x covers less cleanly, including mixed baud rate detection.

For a step-by-step procedure in the TIA Portal environment, see the TIA Portal V20 help: Displaying accessible devices.

9. Safety and Operational Notes

10. Summary Decision Matrix

Frequently Asked Questions