Configuring BOP20 User List to Display P0210 on SINAMICS S120
Field engineers commissioning SINAMICS S120 drives frequently need to read parameters that are not part of the default BOP20 menu. This reference covers the full procedure to build a user-defined parameter list using STARTER commissioning software, then expose P0210 (and any other parameter such as r70) directly on the BOP20 operator panel attached to a CU320-2 Control Unit. The same procedure is used when troubleshooting faults such as F06310 where on-panel visibility of internal parameters is required without a live STARTER session on the floor.
The BOP20 (Basic Operator Panel 20) is a two-line alphanumeric alternative to the IOP (Intelligent Operator Panel). It supports direct parameter access via three control modes and a configurable user-defined parameter list (p0013[0..19] / p0016). By default the BOP20 exposes only a small subset of operational parameters; everything else requires either STARTER, Startdrive, or a custom user list. Exposing P0210 in the user list is a six-step STARTER parameter operation followed by two BOP20 key sequences.
p0210 in the STARTER/Startdrive expert list. The leading zero in the BOP20 display reflects the parameter group (0xxx group = CU/system level), not a separate parameter number. The same mapping applies to r70, which is a display parameter accessed as r0070 in STARTER. Throughout this article the BOP20 notation P0210 / r70 is used; in STARTER the parameter is written without the leading zero.
Prerequisites
- SINAMICS S120 drive system with CU320-2 Control Unit (firmware ≥ 4.4 for full expert list support; ≥ 4.7 recommended for current STARTER compatibility)
- BOP20 connected to the CU320-2 front port
- STARTER V5.4 SP1 or later, or Startdrive V15 / TIA Portal V15.1 or later
- Ethernet cable to access service interface X127 (RJ45 socket directly above the BOP20 connector on the CU320-2 front face)
- Engineering PC IP address on subnet
169.254.0.0/16(X127 default IP 169.254.11.22, subnet mask 255.255.0.0) - Optional: VSM (Voltage Sensing Module) installed if working in the context of line-side monitoring where F06310 is active
- Active drive configuration with at least one drive object (DO1 or higher)
CU320-2 and BOP20 Hardware Architecture
The CU320-2 is the central Control Unit for SINAMICS S120. The BOP20 plugs into the front of the CU320-2 and draws power directly from the unit; no separate supply is required. The service interface X127 is an RJ45 socket positioned immediately above the BOP20 connection on the front face of the CU320-2. This port is pre-configured with a fixed IP address (169.254.11.22) and subnet mask (255.255.0.0). A direct Ethernet patch cable can be used to connect a notebook without any IP conflicts because the entire 169.254.0.0/16 range is reserved for link-local addressing.
Figure 1 — CU320-2 front-face topology with BOP20 and X127 service interface.
STARTER Online Connection Setup
- Connect the engineering PC Ethernet port to X127 on the CU320-2 using a Cat5/6 patch cable (or crossover — X127 supports both with auto-MDI/MDIX behavior).
- Set the PC Ethernet adapter to a static IP in the link-local range: IP
169.254.11.21, mask255.255.0.0, gateway left blank. - Disable any active VPN/Wi-Fi on the engineering PC to avoid default route conflicts with 169.254.0.0/16.
- Launch STARTER and open the project matching the drive configuration (or create a new project and run "Accessible nodes" scan).
- From the project tree, right-click the CU320-2 node and select Target system → Connect, or use the toolbar Online → Connect to target system.
- STARTER scans the subnet for accessible nodes; the CU320-2 will appear at 169.254.11.22. Click the node and confirm.
- The status bar at the bottom of STARTER should display Online in green. The orange/yellow online indicator on the project tree icon confirms the connection.
Configuring the User Parameter List in STARTER
Three parameters control the BOP20 user list: p0003 sets the access level, p0013[0..19] defines the parameter indices, and p0016 activates the user list. Each drive object (the CU itself and every axis DO) has its own p0013. The p0016 parameter is set on the CU and enables the user list globally for the BOP20 bound to that CU.
| Parameter | Scope | Value | Function |
|---|---|---|---|
| p0003 | CU / Axis | 3 (Expert) | Unlocks p0013 and p0016 for editing |
| p0013[0] | Axis DO | 210 | User list index 0 → exposes p0210 on BOP20 |
| p0013[1] | Axis DO | 70 | User list index 1 → exposes r0070 (display parameter) |
| p0016 | CU | 1 | Activate BOP20 user-defined list (0 = inactive) |
| r975[7] | CU | read-only int | Drive Object number the BOP20 is currently bound to |
Step-by-Step STARTER Procedure
- From the online project tree, expand the CU320-2 node and right-click the CU icon.
- Select Expert list from the context menu. The expert list opens in a tabular view.
- Filter or scroll to
p0003and set its value to 3 (Expert). Confirm with ENTER. Without Expert access, p0013 and p0016 appear dimmed/read-only. - Locate the drive object representing the axis of interest (typically DO1, DO2, ...) in the project tree. Right-click the axis node and open its Expert list (not the CU Expert list).
- In the axis Expert list, navigate to
p0013[0]and enter 210. Press ENTER to commit to RAM. - Navigate to
p0013[1]and enter 70. Press ENTER. - Optionally, fill additional indices (p0013[2..19]) with other parameters of interest, up to firmware-supported count.
- Return to the CU320-2 Expert list and navigate to
p0016. - Set
p0016 = 1to activate the user list. Press ENTER. - From the toolbar, click Copy RAM to ROM (or right-click the CU → Copy RAM to ROM) to commit all changes to non-volatile memory. Without this step the user list reverts to factory defaults on the next power cycle.
BOP20 Navigation Procedure
Once STARTER has activated the user list and committed to ROM, the BOP20 must be put into user-list mode and bound to the correct drive object before the parameters are visible. The BOP20 has three top-level operational modes:
- I mode (Index) — displays the parameter number (e.g., P0210)
- R mode (Read/Run) — displays the parameter value (e.g., 1450)
- A mode (Acknowledge) — fault acknowledgement entry
The P key cycles between I mode and R mode. The FN key is the function modifier, used in combination with other keys for user-list entry, acknowledge, and parameter set switching.
Figure 2 — BOP20 keypad layout with FN + Arrow Up combination used to enter user-list mode.
BOP20 Step-by-Step Procedure
- Ensure the BOP20 displays the standard operational screen (speed/status/fault banner).
- Press and hold FN and the Arrow Up key simultaneously for approximately 2 seconds.
- The BOP20 enters user-list mode and displays the first drive object number (e.g., DO 1) on the LCD.
- Use the Up/Down arrow keys to scroll to the drive object whose user list you configured. To confirm the correct DO, read
r975[7]in STARTER beforehand — the value is the DO number to which the BOP20 is currently bound. - Press P to enter the user list for the selected drive object.
- The BOP20 displays the first parameter from the user list, which will be
P0210(index 0). - Press P again to enter R mode and read the value of p0210.
- Press the Up/Down arrow keys to scroll through the remaining user-list entries;
r70will appear at index 1. - To exit back to the operational screen, press FN repeatedly or hold FN + Arrow Down.
Reading P0210 and r70
After navigating to the parameter with P, the second press displays its current value. The value updates live on the BOP20 — for a real-time parameter such as r0070 (actual speed smoothed) the displayed value changes in step with the drive state. For configuration parameters such as p0210, the value reflects the currently active parameter set and may require a warm restart to take effect after modification.
| BOP20 Display | STARTER Equivalent | Read/Write | Use Case |
|---|---|---|---|
| P0210 | p0210 | R/W (depends on attributes) | Configuration parameter exposed via p0013[0] |
| r70 | r0070 | Read-only | Display parameter exposed via p0013[1] (typical: actual speed value) |
If the BOP20 LCD shows three dashes (---) instead of a numeric value for either parameter, the value is indeterminate — usually because the drive is in a stop state, the relevant encoder is not homed, or a referenced parameter set is not yet loaded.
F06310 Alarm Context and Clearing
F06310 is a SINAMICS S120 fault indicating an incomplete or missing enable condition within the drive enable signal chain. Common root causes observed in field commissioning include:
- OFF1 enable missing — terminal EP not energised, or control word bit 0 (STW1.0) false
- OFF3 (coast stop) enable missing — control word bit 1 (STW1.1) false or safety chain open
- Inverter enable chain interrupted — line contactor open, missing 24 V at terminals, missing pulse enable
- Commissioning parameter set inconsistent with hardware topology — VSM not configured, Sensor Module mismatch, motor/encoder ID not run
- Safe Stop (SS1/STO) active — safety relay open or PROFIsafe telegram missing
When F06310 is active, certain runtime parameters become inaccessible until the fault is acknowledged. Acknowledgement is performed by pressing FN + ACK on the BOP20 or via STARTER's "Acknowledge faults" toolbar button (F5 hotkey). F06310 does not prevent reading p0210 once the user list has been created in STARTER, but if the drive is in a safe stop state some parameter values may show --- indicating indeterminate value.
For VSM-related commissioning where F06310 appears during initial power-up, validate the VSM wiring at the terminals and confirm the active Line Module is correctly configured in the topology (DO ordering, DRIVE-CLiQ port assignment, VSM slot index). The VSM parameters live on the Active Line Module DO; mismatches between physical DRIVE-CLiQ topology and STARTER topology trigger cascading enable faults that surface as F06310.
Verification Procedure
After completing the STARTER configuration and BOP20 navigation, run the following verification checklist to confirm the user list is functional and persistent:
- Cycle 24 V control power to the CU320-2. Confirm the user list survives (means p0016 = 1 was committed to ROM).
- On the BOP20, enter user-list mode (FN + Up). Confirm the correct drive object is selectable and matches the axis configured in STARTER.
- Navigate to index 0. Confirm parameter
P0210appears on the LCD. - Press
Pto read the value. Compare the value with the same parameter read live in STARTER Expert list. Values must match exactly. - Navigate to index 1. Confirm
r70appears and displays a numeric value (or---if drive is stopped and parameter is encoder-derived). - Toggle the drive enable from STARTER or a wired terminal. Verify that r70 (actual speed) updates in real time on the BOP20.
- If any step fails, re-check p0013 entries and p0016 activation in the CU Expert list, then verify the BOP20 is bound to the correct DO via r975[7].
- Save the project to a network share and create a backup
.parfile from STARTER for archival.
Parameter Reference Summary
| Parameter | Scope | Type / Range | Default | Engineering Purpose |
|---|---|---|---|---|
| p0003 | CU / Axis | 1..4 (Standard, Extended, Expert, Service) | 1 | Unlocks expert parameters for editing |
| p0013[0..19] | Axis DO | Parameter number (int) | 0 | BOP20 user list parameter indices (up to 20 entries on FW ≥ 4.4) |
| p0016 | CU | 0 = inactive, 1 = active | 0 | Activate BOP20 user-defined list globally |
| r0070 | Axis DO | float (rpm or %) | n/a | Actual speed smoothed (SERVO) / DC link voltage (VECTOR) depending on DO type |
| r975[7] | CU | int (DO index) | n/a | Drive Object number / BOP20 binding target |
| p0210 | Axis DO | Depends on drive type | Drive-specific | Configuration parameter exposed at user-list index 0 |
Common Pitfalls and Field Notes
- Wrong drive object selected on BOP20: The single most common failure. Verify r975[7] in STARTER matches the DO the BOP20 is bound to after FN + Up. The DO must be selected manually with the arrow keys before pressing P.
- Editing p0013 on the wrong DO: Each axis has its own p0013 instance. Configuring p0013 on the CU Expert list does not expose parameters on the axis BOP20 list — p0013 is a per-DO parameter array.
- p0003 not set to 3: Without Expert access, p0013 and p0016 appear dimmed/read-only in STARTER. The change fails silently with no error message.
- Not committing to ROM: p0016 = 1 is volatile unless copied to ROM via the toolbar. After the next power cycle the BOP20 returns to the factory default parameter list.
- BOP20 I/R/A mode confusion: Operators confuse the three modes. P cycles I ↔ R; FN + ACK enters A. The mode letter is not always shown on the LCD — only the parameter number and value.
- Firmware < 4.4 limits user list: On firmware < 4.4, p0013 supports only 8 entries (index 0..7). Indexes 8..19 are silently ignored on older firmware.
- Startdrive vs STARTER path difference: In Startdrive (TIA Portal), the same parameters p0003 / p0013 / p0016 exist but the Expert list is opened from the device view → Parameters → Show all parameters. The procedure is identical but the menu structure differs.
- VSM topology mismatch: When commissioning with an Active Line Module + VSM, an incorrect DRIVE-CLiQ topology in STARTER can cause the VSM to be reported on the wrong DO, leading to F06310 and blocked parameter access downstream.
Related Siemens Documentation
Official Siemens documentation is the authoritative source for parameter definitions and firmware-specific behaviour. Reference the SINAMICS S120 Commissioning Manual and the BOP20 Operating Instructions from the Siemens Industry Online Support portal for the exact parameter text and FW version notes:
- Siemens Industry Online Support — search "SINAMICS S120 parameter list" or "BOP20" for the latest commissioning manuals and parameter reference PDFs.
- SINAMICS S120 List Manual — full parameter descriptions including p0013, p0016, p0003, r975.
- STARTER Commissioning Tool documentation — online connection, expert list navigation, RAM to ROM procedure.
Frequently Asked Questions
Why does P0210 not appear in the default BOP20 menu?
The default BOP20 menu exposes only a curated set of operational parameters (speed, current, status, faults). To display non-default parameters such as p0210 you must build a user-defined list by writing p0013[0..19] on the relevant drive object, then activating it with p0016 = 1 on the CU.
What does r975[7] tell me?
r975[7] returns the drive object (DO) number to which the BOP20 is currently bound. When you enter the BOP20 user-list mode via FN + Up, you can scroll through the available DOs. r975[7] confirms you are editing and viewing parameters for the intended axis, avoiding the common mistake of selecting the wrong DO on a multi-axis system.
Can I edit P0210 directly on the BOP20 after exposing it?
Whether p0210 is editable depends on the parameter attributes defined in the SINAMICS firmware. If p0210 is a writable parameter and the current access level (p0003) permits editing, the value can be modified on the BOP20 by pressing P twice (read), then using Up/Down to change, then P again to confirm. Read-only parameters display the value but reject write attempts.
How is F06310 related to P0210?
F06310 (enable missing/incomplete) is unrelated to p0210 directly, but during the active F06310 state some runtime parameters may show indeterminate values (---) on the BOP20. Acknowledging F06310 via FN + ACK or the STARTER toolbar restores full parameter visibility. Never force-acknowledge the fault without identifying the missing enable source — the OFF3 enable in particular must come from a safety-rated circuit.
Do I need STARTER if I only want to view parameters on the BOP20?
Yes. To view any parameter not in the default BOP20 menu, the user list must first be built, which requires STARTER (or Startdrive). After the user list is configured and saved to ROM, the BOP20 alone can navigate and read the listed parameters without a live STARTER connection — useful for floor operations where no engineering PC is available.
How many parameters can the BOP20 user list hold?
On firmware ≥ 4.4, p0013 supports indices 0..19 (20 entries). On firmware < 4.4 the array is limited to indices 0..7 (8 entries). Exceeding the supported count results in silent truncation of the higher indices.