Resolving SIMOCODE DP PDM Upload Error 3340:4 in PCS 7 V6.1

1. Problem Overview

After a full Engineering Station (ES) reinstall on a SIMATIC PCS 7 V6.1 system running SIMATIC PDM V6.0, the operator observes a partial loss of PDM integration for SIMOCODE DP (3UF5) motor management devices. The symptoms are:

• The SIMOCODE DP stations are visible inside the Process Device Network View of SIMATIC PDM.
• The same stations do not appear in the PDM LifeList.
• A Download to PG/PC (parameter upload) or a Compare parameters action returns an empty parameter set accompanied by status Error 3340 : 4.
• A Download to device appears to complete successfully (no popup error), but the device does not actually enter the remote-controlled state required for parameter write operations.
• The SIMOCODE DP faceplate on the plant bus shows the device stuck in "Local" operating mode.

This is a known failure pattern that emerges when the device data (EDD/GSM files) for SIMOCODE DP is not re-imported after a fresh ES installation, or when a pre-existing ES image is restored without the matching SIMOCODE device data.

2. Affected Components and Software Stack

The error occurs because PCS 7 V6.1 ships only a baseline set of EDD libraries. The SIMOCODE DP EDD is delivered as a separate package on the "Additional Products" DVD or on a standalone device-data CD supplied with PCS 7 V6.1. A fresh ES install without that package loads, however, will display the SIMOCODE DP station objects in the project (because the GSD/GSM info is embedded in the PCS 7 master data library) but cannot interpret the parameter slots, which manifests as Error 3340:4 during upload or compare.

3. Decoding Status 3340:4

SIMATIC PDM organizes status messages as 4-digit error class . sub-code. Status 3340 belongs to the communication / parameter-set class:

Sub-code 4 is the specific indicator that the SIMOCODE DP EDD on the ES is either missing, outdated, or referring to a different device catalog number than the one physically installed. The visible effect – empty parameter list after an upload – is a direct consequence: PDM has no slot map to populate.

4. Root Cause 1 — Missing or Outdated SIMOCODE DP EDD

The most common cause after an ES reinstall is that the SIMOCODE DP EDD V6.0 package has not been imported. PCS 7 V6.1 + PDM V6.0 require the matching EDD revision for each PROFIBUS DP field device family. Without it:

1. PDM discovers the slave through its GSD file (so the object appears in the network view).
2. PDM cannot match the slot list to a known EDD, so Device → Upload to PG/PC produces no usable parameter list.
3. LifeList, which relies on EDD slot identification, shows nothing because the slave's identification does not match any catalog device on the ES.

The authoritative fix is documented in the Siemens Industry Online Support entry SIMOCODE DP EDD V6.0 – ID 109750852, which states that the EDD is a separately downloadable software component for SIMATIC PDM V6.x.

5. Root Cause 2 — SIMOCODE DP Stuck in Local Operating Mode

SIMOCODE DP has a front-panel selector (and a corresponding parameter) that switches the device between Remote (control via PROFIBUS / PCS 7), Local (control via the device keypad), and Manual. While the selector is in Local:

• All write-class PDM operations are rejected at the device level (the device returns "function not allowed in current mode").
• The SIMOCODE faceplate on the OS shows Local in the operating-mode field.
• PDM may still complete a Download to device for purely informational parameters but cannot write operational setpoints, which is reported as a compare mismatch and, on older EDD revisions, surfaces as 3340:4.

Always confirm the operating-mode selector on the SIMOCODE DP face is rotated to Remote / Auto (the symbol ≠ on the dial) before any PDM upload/download.

6. Root Cause 3 — Communication Path Inconsistencies (CP 1613 + IE/PB)

PCS 7 V6.1 separates the Plant Bus (AS-to-ES / OS) from the Terminal Bus (engineering / OS terminal). In the reported configuration:

• CP 1613 on the ES connects to the Plant Bus (Industrial Ethernet, ISO transport).
• An IE General (typically an IE/PB Link PN IO or IE/PB Link with default routing) bridges to the Terminal Bus.
• The PROFIBUS DP master (CP 443-5 Ext) sits on the AS and is reachable only from the Plant Bus side.

After a fresh ES install, the PG/PC interface assignment in SIMATIC Manager → Options → Set PG/PC Interface is often reset to a default (e.g. TCP/IP on the IE General) instead of the CP 1613's S7ONLINE access point routed to ISO Industrial Ethernet. When that happens, PDM attempts to reach the SIMOCODE DP through the wrong stack and fails slot discovery, producing the 3340:4 status during upload.

7. Step-by-Step Resolution

Step 1 — Re-import the SIMOCODE DP EDD V6.0

1. Open SIMATIC Manager → Options → SIMATIC PDM → Manage device data.
2. Click "Find..."" and browse to the location that contains the SIMOCODE DP device data. On PCS 7 V6.1, this is either:
   • the Additional Products DVD (DeviceData\SIMOCODE_DP\EDD), or
   • the standalone SIMOCODE DP EDD V6.0 installer from the Siemens support entry 109750852.
3. Select the file SIMOCODE_DP_V60.EDD (or the equivalent .gsm + .edd pair) and click Open → Install.
4. Confirm the catalog entry SIMOCODE DP V6.0 appears in the device-catalog list under PROFIBUS DP → Motors → SIMOCODE.
5. Restart the SIMATIC Manager to force PDM to re-read the EDD cache.

Step 2 — Correct the PG/PC Interface Assignment

1. Close SIMATIC Manager.
2. Open Start → SIMATIC → SIMATIC Manager → Options → Set PG/PC Interface.
3. Set the access point S7ONLINE to CP 1613 → ISO Industrial Ethernet (the CP 1613 entry shows the MAC of the Plant Bus card).
4. If you also need PDM to talk to slaves reached through the Terminal Bus / IE/PB Link, set a second access point PDM_PG to IE General → TCP/IP and select it in SIMATIC Manager → Options → SIMATIC PDM → Settings.
5. Click OK and re-open the project.

Step 3 — Verify SIMOCODE DP Operating Mode

1. On the SIMOCODE DP front panel, rotate the selector to 1 = Remote / Auto.
2. Confirm the green REMOTE LED on the device is lit.
3. In the PCS 7 OS faceplate, the operating-mode text field must show Remote, not Local.
4. If the device still shows Local, check the parameter P081 (Operating mode) in SIMOCODE DP itself: the value must be Remote (typically 0x01).

Step 4 — Force a Fresh Upload with the New EDD

1. In the Process Device Network View, right-click the SIMOCODE DP object.
2. Choose Upload to PG/PC (not Download).
3. The PDM Device window must now show the full parameter tree (Motor protection setpoints, I&M data, diagnostics buffer, etc.).
4. Run Compare parameters. The result must show Equal for every parameter; any Different lines point to parameters whose write was rejected in Local mode.

Step 5 — Re-Verify LifeList Visibility

1. Start SIMATIC PDM → Device → LifeList.
2. Set the PROFIBUS DP address range to the actual segment (e.g. 3..32).
3. Click Start Scan. All SIMOCODE DP stations on the bus must appear within 10–15 seconds with their catalog ID and EDD revision shown in the right pane.

8. Verification Matrix

9. Optional Hardening — Prevent Recurrence After Next ES Rebuild

1. Catalog every device-data package in the project documentation; mark each EDD installer with its SIOS article ID (e.g. 109750852 for SIMOCODE DP V6.0).
2. Export the full device catalog with Manage device data → Export after each successful commissioning and store the export alongside the PCS 7 project backup.
3. After any ES image restore, run Manage device data → Verify before opening the project. This rebuilds devcat.mdb against the imported EDDs.
4. Where possible, deploy PCS 7 with SIMOCODE ES (TIA Portal) or SIMOCODE DP V6.x on a parallel maintenance PC so the device-data installers are kept current.
5. Lock the SIMOCODE DP selector behind a key switch or cover once commissioning is complete to avoid accidental Local-mode transitions during plant operation.

10. Field-Proven Caveats

• Mixed EDD revisions: If the plant contains both 3UF50 (legacy) and 3UF51/3UF52 (current) SIMOCODE DP variants, import both EDD revisions. PDM V6.0 will match the correct one by catalog number; mixing them in one catalog is allowed.
• SP update resets: Installing PCS 7 Service Packs that touch PDM (e.g. PCS 7 V6.1 SP4) does not always preserve EDDs installed afterwards. Re-verify after every SP.
• Multiple ES on one plant: Each ES has its own device catalog. Importing the EDD on one ES does not propagate it to the other; repeat on every ES.
• Time-out on first upload: The very first upload after EDD import can take up to 60 s per device because PDM rebuilds the slot cache. Do not interrupt the operation or it will leave a partial parameter file.

11. Related Status Codes You May Also See

12. FAQ