Editing SIMOCODE .sdp Files: Migration, Memory Modules, and PROFIBUS Addressing

Siemens SIMOCODE pro (3UF7 series) is the motor management system used to protect, control, and diagnose motor feeders in low-voltage switchgear. Every time a SIMOCODE pro device is parameterized, the engineering tool creates two artifacts on the engineering station's hard disk: an .htm report file describing the configuration and a .sdp parameter file containing the compressed device image. Engineers who only need to change a handful of values (FLC, descriptor text, I/O assignment) frequently look for a text editor or scriptable method to modify the .sdp file directly. This reference documents why that approach does not work, the supported alternative workflows (memory module, addressing plug, SIMOCODE ES parameter editor), and the migration path from SIMOCODE ES 2007 to the current TIA Portal-based SIMOCODE ES V14+ releases.

1. SIMOCODE pro Parameter File Architecture

SIMOCODE pro stores its operating parameters in two physical locations: in the basic unit (3UF7010-xA, 3UF7011-xA, 3UF7012-xA) and in the optional memory module (3UF7910-0AA00-0). When the project is saved on the engineering PC, SIMOCODE ES produces:

2. Why a Normal Text Editor Fails on .sdp Files

The .sdp format is essentially a compressed and checksummed snapshot of the device's internal parameter object dictionary. The structure is:

1. Header block with magic number, SIMOCODE ES version, and basic-unit type code.
2. Compressed parameter blocks (function blocks 0–99, control functions, I/O mapping, protective functions).
3. Compressed communication blocks (PROFIBUS DP / PROFINET device name, GSD slot mapping, diagnostic addresses).
4. CRC-16 trailer covering the preceding sections.

Attempting to change a value with a text editor fails because the structure, length, and CRC are interdependent. A single string change shifts byte offsets, breaks block boundaries, and invalidates the checksum. SIMOCODE pro basic units verify the CRC at download and abort with fault F70 if the integrity check fails.

3. SIMOCODE ES Versions and Capabilities

SIMOCODE ES has shipped as both a standalone tool and a TIA Portal option. The following matrix shows the major release branches and the matching TIA Portal integration.

4. Editing Parameters with SIMOCODE ES

The supported editing path always runs through SIMOCODE ES. Use the following procedure for routine parameter changes such as full-load current (FLC), rated voltage, I/O assignment, or description text.

4.1 Prerequisites

• SIMOCODE ES installed at a release level matching the device firmware.
• Original .sdp parameter file (project archive) on the engineering PC.
• PROFIBUS DP / PROFINET / Ethernet IP connection between the PC and SIMOCODE pro basic unit, or a memory module and a docking station.
• Engineering password (if project is write-protected).

4.2 Step-by-Step Editing Procedure

1. Launch SIMOCODE ES and open the existing .sdp file via File → Open or from the TIA Portal project tree.
2. Select the basic unit in the device view; the editor splits into a Parameters, Function Blocks, and Signals tab.
3. Change the required values (e.g., Motor → Rated motor current (FLC), Control Functions → Control station block).
4. Click Save. SIMOCODE ES writes a new .sdp and regenerates the .htm report.
5. Select Device → Download to device (or PC ↔ SIMOCODE pro → Download in the legacy ES 2007 menu).
6. Confirm the parameter assignment dialog and wait for the green status bar.
7. Verify the change is active: Online → Open device view → check the parameter page or test the wiring on a non-energized test bench.

5. Migrating from SIMOCODE ES 2007 to TIA Portal V14+

SIMOCODE ES 2007 is a 32-bit standalone tool that runs on Windows XP / Windows 7 and writes legacy v1.x .sdp files. Siemens officially replaces the standalone ES line with the TIA Portal option. The migration is described in detail in the Siemens support article Replacement of the SIMOCODE ES 2007 parameterizing and service software and migration to SIMOCODE ES TIA.

5.1 When to Migrate

• The PC running Windows XP / 7 is being decommissioned.
• New SIMOCODE pro V devices (EtherNet/IP, OPC UA, web server) are added to the line.
• PROFINET / S7-1500 / S7-1200 controllers are introduced and TIA Portal is the standard engineering environment.

5.2 Migration Procedure

1. Install TIA Portal with the SIMOCODE ES option (V14 SP1 or later recommended).
2. In the TIA Portal Portal view select Migrate project.
3. Browse to the SIMOCODE ES 2007 parameter file of type *.sdp and confirm.
4. Choose a destination TIA Portal project file. The wizard translates the parameter blocks, I/O mapping, and PROFIBUS DP slot assignments into the TIA project tree.
5. Review the migration log for warning entries (typically I/O names that did not match, or unused blocks that were dropped).
6. Compile and download the project. The TIA Portal release writes a v4.x .sdp that is incompatible with the legacy ES 2007 tool — keep a backup of the original v1.x file in case the legacy tool is still required for a service job.

5.3 Common Migration Errors

6. Memory Module: Cloning Parameters Between Devices

For production lines with many identical motor feeders, the recommended approach is to download once and then copy the parameter image via a SIMOCODE pro memory module (order number 3UF7910-0AA00-0).

6.1 Memory Module Workflow

1. Configure the first SIMOCODE pro unit with SIMOCODE ES and download to device.
2. Insert the memory module into the docking station and select SIMOCODE pro ↔ Memory module → Download. The module stores the complete parameter image, including the PROFIBUS address placeholder.
3. Walk the line, powering each SIMOCODE pro basic unit. The basic unit detects the memory module on power-up and copies the parameter image into its internal flash. LED DEVICE shows steady green on success.
4. Remove the memory module. The unit runs on its internal copy from now on.

The memory module allows the FLC, descriptor, I/O mapping, and protective function parameters to be cloned, but the PROFIBUS DP node address stored in the memory module is overwritten by the basic unit's addressing plug or the existing address in flash. Use the addressing plug (Section 7) to give each device a unique DP address before or after cloning.

7. PROFIBUS DP Addressing Plug

The PROFIBUS addressing plug (order number 3UF7910-0AA01-0) is a small dial that plugs into the front of the SIMOCODE pro basic unit. It is used to set the PROFIBUS DP node address in the field without a PC.

7.1 Procedure

1. Set the rotary switch on the addressing plug to the desired DP address (1–125). Switch positions 0 and > 125 are invalid.
2. Insert the plug into the front of the basic unit.
3. Power-cycle the basic unit. On boot, the device reads the address from the plug and stores it in non-volatile memory.
4. The plug can remain in place or be removed; the address is retained in flash.

8. Bulk Commissioning Workflow for Production Lines

For a typical MCC line with 20–60 motor starters, the field-proven sequence is:

1. Configure the first unit in SIMOCODE ES (TIA Portal). Set FLC, control functions, I/O mapping, and protective function thresholds.
2. Save the project as MASTER_LINE_xx.sdp.
3. Download to the first unit, validate, then export to memory module.
4. Walk the line with the memory module + addressing plug: insert the memory module, power-up, observe green DEVICE LED, remove module, dial next DP address on the addressing plug, power-cycle, repeat.
5. Record the DP address / motor name on the enclosure label.
6. Run a PROFIBUS DP bus scan from the PLC (PG → Accessible nodes) to confirm every node responds.

This workflow produces a reproducible, auditable commissioning record and avoids the time cost of opening 60 individual projects in SIMOCODE ES.

9. TIA Portal Integration Notes (V14 → V18)

Newer TIA Portal releases read older .sdp files transparently. Older releases will reject newer files with the message "File format not supported". Maintain a single TIA Portal baseline across the engineering team to avoid the round-trip issue described in Section 5.2.

10. Troubleshooting .sdp File Operations

11. Safety and Commissioning Notes

12. Summary of Recommended Workflows

FAQ