Resolving Siemens MM440 PROFIBUS Parameter Upload via Scout

Problem Description

When commissioning a Siemens MICROMASTER 440 (MM440) inverter of 1.5 kW class with the optional PROFIBUS communication module, engineers frequently encounter a "found but cannot accept" condition inside SCOUT V4.2 (or its successor STARTER): the Accessible Nodes browser correctly lists the drive at its configured PROFIBUS address (for example, PPO type 3 / address 5), but double-clicking the device or pressing Accept fails to insert the MM440 into the project tree. The same condition is observed whether the engineer attempts:

• A direct PROFIBUS link from the programming device (PG) to the MM440 with the CP5611 card and the on-board PROFIBUS module 6SE6400-1PB00-0AA0, or
• A routed path through an S7-315-2 DP PLC (CPU 315-2 AF03 / 315-2 AG13 / 315-2 EH14 depending on firmware release).

The fault is not a defective bus cable, a wrong slave address, or a faulty drive. The root cause lies in the way SCOUT resolves the PG/PC interface for the PROFIBUS channel — the default selection is normally S7ONLINE (STEP 7) -> CP5611 (PROFIBUS), which is the correct setting for the STEP 7 hardware catalog but not for the drive's DPV0/DPV1 protocol stack used by SCOUT.

Affected Components and Versions

Root Cause Analysis

The MM440 communicates over PROFIBUS using the PROFIdrive profile (PNO order no. 3.072). It exposes only the DP slave side, not an S7-compatible passive S7 communication. SCOUT must therefore open the bus through a DP-master capable interface, not through the S7ONLINE access point that STEP 7 uses for PG functions such as download, monitor and Accessible Nodes from the SIMATIC Manager.

Symptoms tied to wrong PG/PC access point:

• Bus scan returns the MM440 at its slave address (e.g. 5) with a yellow ? marker, indicating SCOUT received an FDL response (GetCfg) but cannot resolve the device description.
• The Accept or Insert button is greyed out, or pressing it triggers the error 0xE0A0: "The selected device cannot be inserted, the configuration does not match."
• Routing via the S7-315-2 DP shows the CPU in Accessible Nodes, but the MM440 hanging off the DP master system of the CPU is invisible, even when the CPU is online.

There are three independently sufficient causes that produce the same surface symptom, so they should be checked in this order:

1. Wrong PG/PC access point in SCOUT (S7ONLINE selected instead of DEVICE / STARTER / SCOUT). This is the most common cause in field practice.
2. Missing or outdated GSD in the STEP 7 / SCOUT device catalog. The MM4 PROFIBUS module must be installed from SIEM80F0.GSD (DPV0) or SI8180F0.GSD (DPV1).
3. Bus profile mismatch between the master (CP5611, PLC DP master) and the slave (MM4 module), especially when the highest station address, bus timing (Tslot, Tset, Tqui), and repetition rate differ.

Solution: Configure the PG/PC Interface for SCOUT

The fix is to switch SCOUT's Set PG/PC Interface selection from the S7-Online entry to a dedicated access point that opens the CP5611 as a DP master:

1. Close SCOUT and STEP 7 if open.
2. Open Start > SIMATIC > STEP 7 > Set PG/PC Interface (the dialog launched by S7PGPCDX.EXE).
3. In the Access Point of the Application dropdown, select DEVICE (STARTER/SCOUT). If only S7ONLINE is shown, install the SIMATIC NET SOFTNET-DP software (DVD 6GK1704-0AA00-0AA0 or newer) to register the additional access points.
4. In the Interface Parameter Assignment Used list, choose CP5611 (PROFIBUS) – AUTO or, if AUTO fails on a specific PCI slot, CP5611 (PROFIBUS) – PROFIBUS (1) for the first CP5611 instance.
5. Click Properties and verify the CP5611 settings:
      – Transmission rate: DP, 1.5 Mbps (or whatever the project bus profile specifies).
      – Highest PROFIBUS address: 126 (default) – must be equal to or higher than the MM440 slave address.
      – Profile: DP (Universal), Bus parameters tab — set Tslot = 300, Tset = 4, Tqui = 0, GAP factor = 5, repetition rate = 3, or copy the values from STEP 7 HW Config to keep all masters consistent.
6. Click OK and then OK on the parent dialog. Restart SCOUT.

Install the Correct MM4 GSD File

SCOUT relies on the STEP 7 device catalog to resolve the slave GSD before it can construct the cyclic PPO image. Without a matching GSD the Accessible Nodes scan sees the slave as an unidentified DPV0 device.

1. Download the GSD from the Siemens Product Support portal: search for entry ID 49229556 ("MICROMASTER 4 PROFIBUS GSD") or the successor FAQ MICROMASTER 4: GSD files for PROFIBUS. Approved filenames:
      – SIEM80F0.GSD – DPV0 standard PPO1 / PPO3 / PPO4.
      – SI8180F0.GSD – DPV1 with acyclic parameter channel.
2. Extract the archive; copy the *.GSD and the bitmap files (BMP, ICO) into %ProgramFiles%\Siemens\Automation\S7GSIM\ for STEP 7 V5.5, or into the SCOUT / STARTER \Devices subfolder.
3. In STEP 7 choose HW Config > Options > Install GSD File…, browse to the file, and confirm. The new MM4 slave appears in the catalog under PROFIBUS-DP > Drives > SIMOVERT MASTERDRIVES / MICROMASTER.
4. Re-open SCOUT and rebuild the device tree.

Match PROFIBUS Bus Parameters to STEP 7

Once the access point and the GSD are correct, the bus parameters must match across all DP masters on the segment. The reference configuration in STEP 7 / TIA Portal is documented in the Siemens topic page What you need to know about PROFIBUS bus parameters. The relevant field-level constraints are:

If the CP5611 and the CPU 315-2 DP live on the same physical segment, copy the bus profile from HW Config into the CP5611 Properties (right-click CP5611 > Properties > PROFIBUS) so that the PG and the PLC master see the same bit-time budget. Mismatches here cause the MM4 to drop out of Accessible Nodes randomly or to be reported as address 127 (passive).

Direct PG-to-Drive Connection (No PLC)

For a direct link from PG > CP5611 > MM4 PROFIBUS module (no S7-300 in the loop), follow this sequence after fixing the access point:

1. Power up the MM440; the PROFIBUS module's LED should blink green or steady green (LED "DP" or "BF" off).
2. Connect the 9-pin D-sub PROFIBUS connector of the CP5611 cable to the MM4 module's female D-sub. Ensure termination is ON at the MM4 end (the module ships with the bus terminator switch in the OFF position; enable it only when the MM4 is the last device on the segment).
3. In SCOUT open your project, right-click the drive > Online > Accessible Nodes (or Target system > Accessible Nodes depending on SCOUT build). The MM4 must appear with the correct GSD name, not Unknown Device.
4. Double-click the device. SCOUT should now offer to insert it into the project. Accept the PPO type that matches the parameter view you need: PPO1 (4 PKW + 2 PZD words), PPO3 (0 PKW + 2 PZD), PPO4 (0 PKW + 6 PZD). For a parameter upload of a 1.5 kW MM4, PPO1 is typically the right choice because it exposes the full PKW (parameter identifier value) channel.

Routing Through S7-315-2 DP

If the PG is connected to the Ethernet port of the CPU and the MM4 hangs off the integrated DP master of the S7-315-2 DP, the route is PG → Ethernet → CPU → DP master → MM4. SCOUT uses a gateway which must be set explicitly:

1. Set the PG/PC interface as described above (the Ethernet access point is now S7ONLINE > TCP/IP > Intel…; the DP side uses the S7 routing tables).
2. In SCOUT, choose Options > Set PG/PC Interface > TCP/IP(BROADCAST) for the Ethernet side.
3. Open Accessible Nodes — the CPU 315-2 DP will appear as the master; expand the DP subnet. The MM4 will be displayed as a child of the CPU if the GSD is installed and the slave is configured in HW Config.
4. Insert the MM4 in the project. If the CPU is not online (yellow / red status in the tree), SCOUT will fail with 0xE001 — No route to target. Resolve PLC online state first.

Step-by-Step Verification Procedure

1. Close and re-launch SCOUT so the new access point is loaded.
2. Open the project; right-click the drive → Online → Accessible Nodes. The MM440 must now resolve to MICROMASTER 4 with the correct order number suffix (e.g. 6SE6440-2UC15-5AA1).
3. Right-click the device → Load to PG to upload the parameter set. SCOUT will report progress and finish with the message Load operation completed without error if the PKW channel is healthy.
4. Open the parameter list. The drive's P0010 (commissioning parameter filter), P0700 (command source = 6 for PROFIBUS), P1000 (setpoint source = 6 for PROFIBUS), and the PROFINET/PROFIBUS diagnostic parameters P2051 and r2050 should all be readable.
5. Toggle the control word in the SCOUT control panel (PZD1 word) to value 16#047E (precharge close) and observe r0052 bit 0 (control word valid) toggling high. This confirms the cyclic PZD channel is bidirectional.
6. Save the project and export the drive parameter set via Drive → Load to file (XML/CSV) for documentation.

Troubleshooting Matrix

Field-Proven Tips

• Always copy the bus profile out of HW Config into the CP5611 properties; never leave the CP5611 on DP, AUTO if a CPU master is also on the segment — the AUTO mode uses the slowest detected baud rate, which starves the drive of throughput.
• Use PROFIBUS Diagnostics in SCOUT to read the diagnostic buffer of the MM4 module (r0947 indices). Codes 0xA001 … 0xA015 correspond to PROFIdrive-specific faults such as subscriber not found or invalid PPO and pinpoint the channel in fault.
• For DPV1 acyclic parameter read, set P0927 = 1 on the MM4 and configure a DPV1 slot in HW Config. PPO3/PPO4 with DPV1 expansion is required for STARTER V5.4+.
• After upload, commit the parameter set to the MM4's EEPROM by toggling P0010 = 30 and P0971 = 1 ("Save to EEPROM"). Without this, parameter changes are lost on power-off.

Safety Notes

FAQ