Configuring SINAMICS Expert Lists in SIMOTION SCOUT V4.x

Overview

The Expert List in SIMOTION SCOUT (and the equivalent toolset in STARTER) is the central worksheet for editing every writable and readable parameter of a SINAMICS drive object (DO) or a MICROMASTER (MM4xx, ET200, G110, G120) drive. SCOUT V4.x expands the classic parameter table with four auxiliary tabs that allow engineers to:

• Curate a working subset of parameters (Tab 1: User-defined parameter list)
• Recall saved lists for documentation or replication (Tab 2: Open existing parameter list)
• Capture a point-in-time value snapshot and diff it against the live drive (Tab 3: User-defined value list)
• Persist the working set in one of three formats for downstream use (Tab 4: Save list as *.cdl, watch table, or executable script)

This reference covers each tab, the underlying *.cdl ASCII format, the script-generation logic (including the MicroMaster start/stop unlock sequence), and the version-compatibility rules that govern interchanging lists between SCOUT V3.2, V3.2 SP1, V4.0, and V4.2.

Expert List Architecture and Storage Model

The four expert-list tabs share a single storage philosophy: only the parameter name and the user's comment string are persisted inside the user-defined list. The actual parameter value lives in the associated drive object (DO) inside the S7 project. When a value changes anywhere in the engineering tool, SCOUT synchronizes the value back to the source expert list automatically. This decoupled model means that:

• Deleting a user-defined list does not delete parameter values on the drive.
• Renaming a DO may orphan a user-defined list; SCOUT flags this with informational text in the list view.
• Two user-defined lists can reference the same parameter index (e.g. p1120) without conflict.

Default storage location for any saved list, value list, or script is the S7 project under the U7 user-data folder, with the *.cdl extension for parameter and value lists. Users may export the same files to any external directory via the Save As dialog.

Tab 1: User-defined Parameter List

Tab 1 is the working surface. Use it to assemble a curated subset of the parameters that matter for a given commissioning task — for example, ramp-up time (p1120), ramp-down time (p1121), reference speed (p2000), and control word source (p922) on a CU320-2.

Supported operations:

1. Add parameters — copy from the main expert list, paste from the clipboard, or enter the parameter index in p####[index] notation (for indexed parameters).
2. Comment — every row accepts a free-text comment column, allowing group headings such as "Speed Limits" or "Encoder Configuration".
3. Duplicate — the same parameter may appear multiple times in different rows, in unsorted order, with different comments.
4. Export — save as *.cdl, as a watch table (V4.2+), as a value list, or as an executable script.

To create a new list, click the left-most tab and choose New; to edit an existing list, click the second tab and choose Open. SCOUT opens a new register where rows can be added, edited, or removed.

File Format: *.cdl

The *.cdl file is a plain ASCII text file. It stores parameter names and comment text only — never the parameter values. Example structure:

; User-defined parameter list
; Created: 2024-05-12 SCOUT V4.4
p1120    ; Ramp-up time
p1121    ; Ramp-down time
p2000    ; Reference speed
p922     ; Control word source

Tab 2: Open Existing User-Defined List

The second tab opens a previously saved parameter list. SCOUT resolves the list against the currently selected DO and overlays the values from that DO's online or offline view, depending on the active connection state. The visible cell values therefore always reflect the project's current state, not a frozen snapshot.

Tab 3: User-defined Value List

The third tab is the commissioning engineer's comparison tool. Unlike Tab 2, a value list stores both the parameter index and its unit-tagged value at the moment the list was saved. When reopened against any DO, SCOUT performs a cell-by-cell diff:

• Equal — white background, no action required.
• Different — colored background (red/orange), indicating a divergence between the saved value list and the current DO value.
• NOT AVAILABLE — orange background in the second column; the parameter index does not exist on the current DO (firmware mismatch, optional module absent, etc.).

The dialog provides three action buttons:

1. Accept values — pushes the value-list values into the current DO. Each write request is logged in the Scripting output window. SINAMICS components may apply dynamic locks (access level, expert-level lock, drive state) and skip individual parameters; SCOUT reports these as errors in the Scripting window.
2. Convert to script — generates an executable script (see next section) that performs the same transfer when run later.
3. Close — dismisses the comparison without writing anything.

Direct edit in the second column (the "current object" column) is supported; the cell color updates as soon as the edit field loses focus.

Tab 4: Save Format Selection

The fourth tab is the export hub. From the context menu, choose Save list and select one of three output targets:

Converting Lists to Watch Tables

Watch tables are SCOUT's standard online-monitoring widget, with force/modify buttons per cell. They are the only conversion target that allows live manipulation of drive values during commissioning.

1. Select the rows in the expert list to migrate.
2. Right-click and choose Add to watch table > New watch table.
3. In the Insert Watch Table dialog, edit the name, author, version, and comment fields. The name is auto-populated.
4. Confirm; SCOUT creates a new watch table under the DO.

To append to an existing watch table instead, choose Add to watch table > <existing name>. No secondary dialog appears; values are appended immediately.

Save Expert List as Script

From V4.0 onward, SCOUT can serialize any parameter selection as a chain of read/write requests stored in a script under the DO's Script folder. If the folder does not exist, SCOUT creates it. Typical applications:

• Capturing the result of a "factory setting comparison" as a script that restores the commissioning state on a replacement drive.
• Series commissioning: copy a reference drive's parameters to N identical machines by replaying the script.
• Change documentation: the script is a textual record of which parameters were touched and in which order.

Script Example

' 10/1/2006 from "Script_test.cdl" converted script
APP.LogActive = TRUE                       ' Activate output

' Readable parameter
Value = (Parameters(2, 0))                 ' Drive operating status

' Writable parameter
Parameters(5, 0) = 2                       ' BOP operating status selection

MicroMaster Unlock Sequence

For MICROMASTER drives (MM4xx, ET200, G110, G120), SCOUT auto-prepends a start/stop sequence around the visible parameter set so that the script can run online. The sequence is inserted during conversion, not authored by the user:

' Start sequence (auto-inserted)
Parameters(3, 0) = 4                       ' p3 = 4 (parameter access level)
Parameters(3950, 0) = ZS4_password         ' p3950 = expert password
Parameters(10, 0) = 29                     ' p10 = 29 (drive commissioning filter)

' User parameter set (visible)
...

' Stop sequence (auto-inserted)
Parameters(340, 0) = 1                     ' p340[0] = 1 (save to EEPROM)
Parameters(340, 1) = 1                     ' p340[1] = 1
Parameters(340, 2) = 1                     ' p340[2] = 1
Parameters(10, 0) = 0                      ' p10 = 0 (filter off)
Parameters(3, 0) = old_p3                  ' restore original access level
Parameters(3950, 0) = old_p3950            ' restore original password

The drive-side password ZS4 must match the expert password configured on the MM4xx for the start sequence to succeed.

SINAMICS Limitations in V4.0

• Auto-unlock is not supported for SINAMICS drives in V4.0. If a parameter is read-only because of CU access level (e.g. p9, p10, p301, p922), each blocked write is reported as an error in the Scripting output window.
• Structure-changing parameters (e.g. p140 on SINAMICS, which switches BICO topology) are not reordered. The user must ensure such parameters are at the top of the selected set so the script executes before dependent BICO references exist.
• Unit-system changes (e.g. switching SI <-> US units via p0100) are not applied by the script. The engineer must ensure the unit context is consistent before script execution.
• Expert-list locks (access level, motor code dependency, p340 EEPROM status) are ignored — every green/blue writable parameter gets a write request.

Procedure: Generate an Executable Script

1. Right-click the Tab 1/2 register and choose Save list.
2. Activate the Save as executable script checkbox in the dialog and click OK.
3. Enter a script name in the Insert Script dialog and click OK.
4. SCOUT creates a script folder under the DO containing the new script.
5. (Optional) Right-click the script and Export to ASCII to save a portable copy.

Parameter Index Reference Table

The following parameter indices are referenced by SCOUT's auto-inserted unlock/EEPROM sequences and are essential for manual debugging when a script fails.

Version Compatibility Matrix

Troubleshooting Matrix

Field-Proven Commissioning Workflow

1. Establish baseline. On the reference drive, open Tab 1 and add every parameter that defines the machine's behaviour. Save as reference_drive.cdl.
2. Capture value snapshot. Save the same selection via Tab 4 as a value list. Verify Tab 3 shows zero diffs against the online drive.
3. Generate script. Use Tab 4 > Save as executable script. Confirm the MM4xx start/stop sequences (or manually inject unlock code for SINAMICS).
4. Series replication. On each target drive, open the project, navigate to the DO, right-click the saved script, and Execute. Verify Tab 3 on each drive shows zero diffs after execution.
5. Permanent storage. Append the EEPROM save (p340 = 1 for MM4xx; p0977 = 1 for SINAMICS) so the parameters survive a power cycle.
6. Documentation. Export the script and the *.cdl file to a project archive folder under version control.

Verification Checklist

• [ ] Parameter list opens without "NOT AVAILABLE" warnings on the target DO.
• [ ] Value list diff (Tab 3) is all white after Accept values.
• [ ] Script runs end-to-end with no errors in the Scripting output window.
• [ ] Drive retains all parameters after a power cycle (EEPROM persistence confirmed).
• [ ] Watch table (if generated) shows the same values as the source parameter list.
• [ ] *.cdl file is checked into the project archive with a date stamp.

Frequently Asked Questions