Troubleshooting MicroMaster 430 PROFIBUS CP5512 PC Connection

Problem Definition: MM430 Slave Not Visible on a Direct PC-CP5512 Link

The fault symptom is a MicroMaster 430 (MM430) PROFIBUS slave that cannot be reached from a laptop or desktop PC fitted with a Siemens CP5512 PCMCIA adapter, when no PLC is in the bus. The PC serves as the only DP-V0 master; STEP 7 / STARTER's "Accessible Nodes" or "Browse" returns no MM430, even though the same cable works with a CPU 313C-2DP acting as master. This is a classic single-master PC-to-drive commissioning scenario and has a finite, ordered diagnostic flow that does not require a controller.

The failure modes that produce this exact symptom are, in descending order of probability: (a) GSD file not registered in the commissioning tool, (b) PROFIBUS module DIP switch / parameter P0918 mismatch, (c) CP5512 PCMCIA driver not loaded or assigned to the wrong PC interface slot, (d) missing bus terminator on the CP5512 segment when no PLC is present, and (e) 24 V supply missing or weak on the MM430 PROFIBUS module. The article treats each branch in detail and ends with a verification matrix.

Hardware Architecture: Direct DP-V0 Master on a Single Slave

The MM430 is a low-voltage inverter (200 V / 400 V / 690 V class, frame sizes A to F) with an optional PROFIBUS-DP communication module plugged into the front option slot. When you use a CP5512 as the only DP master, the bus is a point-to-point segment that must be terminated on both physical ends — at the CP5512 (which has a built-in, switchable terminator) and at the MM430 PROFIBUS module (terminator is not built in; you must add a 9-pin sub-D PROFIBUS terminator plug at the drive).

The topology above is electrically simple but operationally fragile: a single missing terminator, a single reversed A/B pair, or a single floating shield produces the exact "not found" symptom you see. Treat the wiring as a controlled specification, not as "a standard cable."

MM430 PROFIBUS Module Identification and Specifications

The PROFIBUS option for the MM430 family (MM420, MM430, MM440) is:

If the diagnostic LED on the PROFIBUS module is steady red after power-up, the drive has accepted the address but cannot see a master. If the LED is off, either the module is not fully seated or the 24 V feed is missing. If the LED is flashing red, the GSD/parameterisation that the master is sending does not match the configured PPO type.

CP5512 Adapter: Hardware, Driver and Slot Constraints

The CP5512 is a PCMCIA (PC-Card Type II) PROFIBUS adapter. It was superseded by the CP5711 (USB) and CP5611/CP5612 (PCI) and is now in the Siemens "legacy" list, but it is still functional and supported by SIMATIC STEP 7 V5.5 and STARTER up to roughly V5.4. The PCMCIA driver layer is the most common silent failure mode in this scenario because Windows 7/10/11 no longer ships the CardBus stack the CP5512 expects, and the CP5512 will appear in Device Manager with a yellow exclamation mark even when the SIMATIC NET software is installed.

If the CP5512 is unstable on a modern laptop, do not substitute a generic USB-RS485 converter. The CP5512 implements the DP-V0 token master state machine; a USB-RS485 adapter is a passive physical layer only and cannot be a DP master. The functional replacement for the CP5512 is the CP5711 (USB, order number 6GK1571-1AA00), which is fully supported by STEP 7 V5.5 SP4+ and STARTER V4.4+.

GSD File: Installation and Verification

The MM430 family (MM420, MM430, MM440) is described by the GSD file:

Two distinct commissioning tools historically support the MM430: DriveMonitor / SIMOVIS (legacy) and STARTER (current). Both require the GSD to be installed into STEP 7 if you intend to use the PC as a DP-V0 master that browses for slaves.

Install the GSD file in STEP 7 (V5.x):

1. Close all STEP 7 and STARTER instances.
2. Open SIMATIC Manager → Options → Install GSD File.
3. Browse to the folder containing SIEM808F.GSD (and the matching SIEM808F.BMP icon file).
4. Confirm SI808F appears under PROFIBUS DP → Drives → SIMOVERT in the hardware catalogue.
5. Restart SIMATIC Manager so the catalogue is rebuilt.

Verify the install with STARTER (≥ V4.2):

1. Open STARTER and choose Online → Accessible Nodes (or Target Device Search).
2. Confirm the PROFIBUS interface is set to CP5512.
3. STARTER should detect the MM430 within 5 to 15 s, independent of whether a STEP 7 project exists.

PG/PC Interface Configuration in STEP 7 / STARTER

The PG/PC interface configuration is where most direct PC-to-drive links go wrong, because STEP 7 and STARTER maintain two parallel access points that must both point at the CP5512 with the same profile.

Set the access point of the PC:

1. Open Start → Control Panel → PG/PC Interface (or the 32-bit variant on 64-bit Windows).
2. Select the access point S7ONLINE (STEP 7) → CP5512 (PROFIBUS).
3. Click Properties and configure:

The "PG/PC is the only master on the bus" checkbox is the single most important item. When the checkbox is off, the CP5512 expects another DP master to handle token passing; the MM430 alone never produces a token, and the PC sits in "passive listener" mode. The symptom is identical to a missing GSD or wrong address. Re-verify this checkbox every time the COM port or USB-serial adapter is changed.

For STARTER, the equivalent access point is S7ONLINE_STARTER; point it at the same CP5512.

PROFIBUS Address: DIP Switch and Parameter P0918

The MM430 PROFIBUS module exposes a 7-segment DIP switch on its top face. The switches form a binary address from 1 to 126 (switches 1..7, switch 8 is reserved for the address mode). When the DIP is set to all OFF (address 0), the bus address is taken from parameter P0918 in the MM430 parameter set.

Field rule: pick one source of truth. If you set the DIP to anything other than 0, P0918 is ignored. If you set the DIP to 0, edit P0918 in the drive parameter set and save with the RAM-to-EEPROM commit (P0010 = 30, P0971 = 1, or via BOP/AOP). Most "not found" symptoms during a single-master bench session trace to a leftover default P0918 = 3 with a DIP set to 0, which makes the drive scan for slave address 3 instead of the 4 the engineer typed into STARTER.

Bus Termination, Cable and Shielding

A direct PC-to-drive PROFIBUS segment must be terminated at both ends. The CP5512 has a switchable terminator on the 9-pin sub-D (slide switch on the PCMCIA card's pigtail); the MM430 PROFIBUS module does not have a built-in terminator, so plug a PROFIBUS terminator (Siemens 6ES7972-0DA00-0AA0 active terminator or a passive 9-pin sub-D terminator plug) onto the unused 9-pin sub-D on the MM430.

If you have only the MM430 and the CP5512 in the segment and the CP5512 is connected via its pigtail, the terminator must be ON at the CP5512 end. If a 9-pin sub-D gender adapter is used in between, the terminator at the CP5512 still applies.

Check the A/B lines (the green and red cores of a violet PROFIBUS cable):

• Pin 3 of the CP5512 sub-D = B (red core).
• Pin 8 of the CP5512 sub-D = A (green core).
• Pin 5 = shield/drain, bonded at both ends with low-impedance contact.

Reversing A and B is recoverable — the bus simply does not come up, and the MM430 LED remains off or steady red — but it is a common bench error when reusing cables from older PC-Adapter (RS232-to-RS485) converters.

24 V Logic Feed to the PROFIBUS Module

The MM430 PROFIBUS option module has an independent +24 V logic feed on its two screw terminals. The MM430 base unit does not feed the module from its internal 24 V supply; the field installer must wire an external 24 V DC source (typically the same 24 V that powers the MM430's control terminals 9/10). When the external 24 V is missing, reversed, or below ~18 V, the module's PROFIBUS LED stays dark and the bus is electrically invisible.

Diagnostic Workflow Matrix

Run the steps in order. Stop at the first pass.

Verification: Confirm the Link is Healthy

1. Open STARTER → Online → Accessible Nodes → PROFIBUS (CP5512). The MM430 should appear with the address you configured.
2. Right-click the drive → Online. The status bar shows the bus baud rate detected (auto-baud).
3. Open the Diagnostics buffer of the MM430 and verify no PROFIBUS-related fault entries (F0070, F0071, F0072).
4. From STARTER, jog the drive via PZD word 1, bit 0 (OFF1) and PZD word 1, control bits. Confirm the drive accelerates. If you intend to use SIMATIC control, configure P0700 = 6 (PROFIBUS command source) and P1000 = 6 (PROFIBUS setpoint source), then save with the EEPROM commit.
5. Cycle power and confirm the link comes back without manual intervention.

Fault Codes Related to the Link

After a hard reset (P0970 = 1) the PROFIBUS address returns to the DIP switch value, even if P0918 was set previously. Always re-verify the address after a factory reset.

Field-Proven Caveats and Common Pitfalls

• PCMCIA slot type. CardBus slots only. ExpressCard slots do not accept the CP5512 without an active adapter, and the CP5512 will draw too much current from passive adapters.
• USB-to-CP5512 adapters. None exist. The CP5512 is not a USB device; do not assume a USB-CP5711 driver will recognise it.
• Multiple DP masters on a bench. If you accidentally connect a CPU (e.g., a CPU 313C-2DP) and a CP5512 at the same time, token-passing may elect the CPU, not the PC, and "Accessible Nodes" returns nothing because the CP5512 is in passive listener state. The checkbox "PG/PC is the only master" disables passive listening and forces master role.
• Long cable without terminator. A 3 m test lead can show a healthy LED but fail parameterisation because of ringing on the A/B pair at 12 Mbaud. Force 1.5 Mbaud during bench tests.
• Shield not bonded. The shield must be bonded to the sub-D backshell at both ends. A floating shield at the PC side is the most common cause of intermittent "found then lost" behaviour during moves of the cable.
• Save parameters before going online. P0700 and P1000 must be committed to EEPROM (P0971 = 1) before a power cycle, or the drive returns to terminal control and the DP link appears "dead" at the application layer even though the bus is healthy.

Quick Sanity Test Without STEP 7

Use SIMATIC NET Commissioning (Start → SIMATIC → SIMATIC NET → Commissioning → "Set PC Station") to confirm the CP5512 is alive and the bus is wired correctly. The tool shows Bus Statistics — character counts, frame errors, and token retries — without requiring STEP 7 to be open. If the bus statistics show zero frames and non-zero errors, the physical layer is broken (cable, terminator, A/B swap). If the bus shows frame activity but no slave responses, the slave side (MM430 module, address, GSD) is the cause.

Reference Documentation

The MM430 base unit operating instructions and the PROFIBUS option module manual are the primary references. The manuals include the wiring diagram for the 24 V logic feed, the DIP-switch address table, the PPO type definitions, and the parameter list including P0010, P0700, P0918, P0970, P0971, P1000 and P2041. Cross-check any parameter default listed here against the manual revision matching your drive firmware, since defaults have shifted across MM430 firmware revisions (FW V1.x → V2.x → V3.x).