Configuring BOP20 RPM Display on Sinamics G130 CU320-2PN: p0005 / p0006 Parameter Reference and Access-Lock Recovery

This technical reference covers commissioning of the BOP20 (Basic Operator Panel 20) on a Sinamics G130 chassis drive with CU320-2PN Control Unit so the panel displays motor speed (RPM), output current, and output voltage. The article directly addresses a common field symptom: the drive runs correctly, the engineering tool (Starter or TIA Portal with Startdrive) shows the correct actual speed on r0021, but the BOP20 2-line LCD remains pinned to a non-speed value (typically r0000 or r0020) and the parameters p0005[0], p0005[1], and p0006 appear read-only. The root cause is almost always a parameter-access condition on the Control Unit drive object, not the value selection itself.

1. Problem Statement and Symptom Map

Typical field observation on a Sinamics G130 chassis unit (315 kW class) with CU320-2PN Control Unit and a BOP20 plug-in operator panel:

• Drive accepts run command from PLC or terminal, motor accelerates to setpoint, Starter / Startdrive online trace shows r0021 (speed actual value, smoothed) and r0022 (unsmoothed) updating correctly.
• BOP20 2-line LCD does not display RPM. The display shows r0000 (operating display / status word) or toggles between r0000 and r0020 (setpoint) and never shows r0021 (smoothed actual speed).
• Writes to p0005[0], p0005[1], p0006 are rejected. Parameters appear "fixed" at p0005[0] = 0 and p0006[0] = 4 even when p0003 is cycled between standard (1), extended (2), and expert (3).

The correct value pair for a customer RPM display is known: p0005[0] = 21, p0005[1] = 27, p0006 = 0. The problem is that the write to these parameters fails or is masked before the value is applied. The drive rejects the access, not the value.

2. BOP20 Display Architecture on the G130

The BOP20 connects to the front of the CU320-2PN via the operator-panel serial interface. Two parameters control what is shown:

p0005 has two indices so the BOP20 can show two different r-parameters when toggled with the FN key:

• p0005[0] - value shown at the first FN press
• p0005[1] - value shown at the second FN press

p0006 controls what the BOP20 displays during operation versus the ready state:

With the factory default p0005[0] = 0 and p0006 = 4, the BOP20 always shows r0000 (operating display) - on the G130 in normal state this is the active command / fault word, not motor speed. The user must change at least p0005[0] to expose any meaningful process value.

3. Standard p0005 Values for the Sinamics G130

From the G130 / G150 List Manual (LH2 firmware family), the supported p0005 selections for the BOP20 are:

Recommended customer-facing configuration:

p0005[0] = 21   ; speed (RPM) shown in operation
p0005[1] = 27   ; motor current shown after FN toggle
p0006    = 0    ; in operation show r0021, otherwise toggle r0020<->r0021
p0003    = 2    ; extended access (use 3 only if 2 still blocks a write)

Reference: SINAMICS G130/G150 List Manual (LH2), parameter section p0000-p0100.

4. Why p0005 and p0006 Are Not Writable: Five Field-Proven Root Causes

4.1 Drive is still in a commissioning state (p0010 ≠ 0)

The G130 / CU320-2 has a top-level commissioning parameter p0010. When p0010 ≠ 0, several display and control parameters change write behavior. In particular, after a quick-commissioning wizard (p0010 = 1) finishes and writes p3900 > 0, the drive does an internal reset of the operator panel interface. If a write to p0005 arrives within 1-2 seconds of p3900, the write can be silently dropped. Always set p0010 = 0, confirm p3900 = 0, wait 2-3 seconds, then write p0005 / p0006.

4.2 Parameter access level p0003 not at the required level

On most firmware builds, p0005 and p0006 are writable at standard access (p0003 = 1). On G130 LH3.x and later, certain display values are gated to extended (p0003 = 2) or expert (p0003 = 3). When p0003 is changed, the change itself is accepted but the parameter filter does not re-evaluate the writable list until the next parameter read. Power-cycle the CU, or perform a parameter reload, before retrying.

4.3 BOP20 local-control key lock is active

The BOP20 has a local key lock: pressing and holding P + FN for more than 3 seconds toggles the lock. When locked, the BOP20 display continues to update from the drive but every key press (P, +, -, >>) is ignored. The lock state is not stored in any r-parameter and is not visible in Starter. Symptoms are exactly what the user describes: the panel does not respond to edits. To clear, power-cycle the BOP20 by removing it from the CU front connector for 5 seconds, then re-seat it.

4.4 Drive is in Operation while the edit is attempted

On LH1 and early LH2 firmware, p0006 and p0005 are only writable in the "Ready to switch on" or "Operation disabled" state. If the drive is running under load with the ON/OFF1 command asserted, the BOP20 will silently reject the write without showing an error. Stop the drive, remove the ON command at the terminal / PLC, wait for r0002 to read 0 ("Operation disabled") or 1 ("Ready to switch on"), then perform the edit.

4.5 Know-How Protection (KHP) is active on the Control Unit drive object

Sinamics supports a password-based parameter protection (p7766, p7767, p7768). When KHP is enabled on the Control Unit drive object, protected parameters read back as the factory default and reject writes regardless of p0003. This matches the user's observation: p0005[0] always returns 0 and p0006 always returns 4, even after a confirmed write attempt. KHP must be disabled (p7766 = 0 with the correct password) before the BOP20 display parameters can be reconfigured.

5. Step-by-Step Resolution Procedure

Apply these steps in order. Each step must be confirmed before moving to the next.

5.1 Confirm the drive is in a writable state

1. Read r0002 on the BOP20 or in Starter. r0002 must report 0 ("Operation disabled") or 1 ("Ready to switch on").
2. Remove the ON / OFF1 command source: de-assert the digital input wired to p0840 (ON/OFF1) at the PLC or terminal, or set p0840 = 0 from Starter.
3. Read r0046.0 - it must be 0 (no missing enable).

5.2 Clear all active faults and alarms

1. Read r0947[0..7] (current fault codes) and r2122[0..63] (current alarm codes).
2. Resolve any active F-class fault. Active faults typically do not block p0005 writes, but firmware inconsistencies have been observed where a stuck fault on a non-active drive object holds the Control Unit DO in a "partial commissioning" state and rejects display writes.
3. Acknowledge with p3981 = 0 -> 1 or via the BOP20 FN key (long press).

5.3 Power-cycle the BOP20 to clear the local key lock

1. De-energize the drive (or use the CU320-2PN's removable terminal strip to de-couple control power if the cabinet supports it).
2. Remove the BOP20 from the front of the CU320-2PN.
3. Wait at least 5 seconds.
4. Re-install the BOP20. The CU320-2PN performs a re-initialization of the operator-panel interface (the BOP20's backlight flashes during re-init).

5.4 Verify and raise the parameter access level

1. From the BOP20, press P to enter parameter mode.
2. Use the up / down arrow keys to scroll to p0003.
3. Press P; the value field blinks.
4. Use up / down to set p0003 = 3 (expert).
5. Press P to confirm.

If the BOP20 will not accept the p0003 change, perform the same write from Starter / Startdrive where the access-level change is explicit and the result is observable. The relevant Starter action is: online → write p0003 = 3 → Copy RAM to ROM.

5.5 Write the display parameters from the BOP20

1. Scroll to p0005, press P.
2. Press >> (right arrow) to expose the index field; the display toggles between [0] and [1].
3. With [0] selected, press P; use up / down to set 21; press P to confirm.
4. Press >> to select [1], press P, set 27, press P.
5. Scroll to p0006, press P, set 0, press P to confirm.

If the BOP20 rejects a write, the display will return to the parameter number without a value change. There is no explicit error code on the BOP20; the silent reject is the error. Diagnose via section 4.

5.6 Alternate write path: Starter / Startdrive

When the BOP20 cannot be made to accept the write, use the engineering tool. The procedure is identical in Starter and TIA Portal with Startdrive:

1. Open the project, go online with the CU320-2PN.
2. Navigate to the Control Unit drive object (not the Vector DO).
3. Open the parameter list and filter on p0005, p0006, p0003.
4. Set p0003 = 3 first and click "Write" (RAM only).
5. Click "Copy RAM to ROM" to commit the access-level change non-volatilely.
6. Set p0005[0] = 21, p0005[1] = 27, p0006 = 0.
7. Click "Write" and then "Copy RAM to ROM" again.
8. Cycle the BOP20 (remove and re-seat) to refresh the operator-panel display.

6. Commissioning-State Lock Map (p0010)

Reference: SINAMICS G130 / G150 List Manual (LH2), p0010 description.

After any p0010 != 0 sequence, set p0010 = 0 explicitly and observe r3996 (commissioning status word) return to 0 before editing display parameters.

7. Know-How Protection Recovery (p7766, p7767, p7768)

When KHP is active on the Control Unit drive object, the affected parameters read back as the factory default and reject writes. To disable KHP:

1. In Starter / Startdrive, go online with the CU320-2PN.
2. Select the Control Unit drive object.
3. Right-click -> Know-how protection -> Deactivate...
4. Enter the OEM password (matches p7766 of the original commissioning).
5. Click OK. Parameters become visible and writable immediately.
6. Set p0003 = 3, write p0005 / p0006 per section 5.

If the OEM password is lost, contact Siemens technical support with the drive serial number (r7841) and the Control Unit serial number (on the CU's nameplate) to obtain a factory-level release. A factory reset (p0010 = 30, p0970 = 1) clears KHP but erases all commissioning data and is destructive.

8. Verification Procedure

8.1 BOP20 display check

1. Issue the ON / OFF1 command. The drive runs.
2. BOP20 first line should display a number followed by "1/min" - this is r0021 in RPM.
3. Press FN - display toggles to a value followed by "A" - this is r0027 in amperes.
4. Press FN again - display returns to r0021.
5. Remove the run command; display should hold the last speed value (p0006 = 0) or toggle to r0020 (setpoint) per the p0006 setting.

8.2 Cross-check with Starter

1. In Starter / Startdrive, read r0021 (smoothed) and r0022 (unsmoothed) via the trace or the parameter list.
2. Compare r0021 with the BOP20 reading. The values should match within the smoothing time constant p0045 (default 5 ms) and the filter selection in p0046.
3. If Starter shows the correct value but the BOP20 does not, the issue is the BOP20 / p0005 binding, not the drive's speed calculation.

8.3 Persistent save verification

1. Confirm "Copy RAM to ROM" was performed in Starter.
2. Power-cycle the CU320-2PN.
3. After restart, the BOP20 should still display the speed in operation - the saved p0005 / p0006 values were retained.
4. If the display reverts to r0000, the RAM-to-ROM save did not occur; repeat it from the engineering tool.

9. Field Commissioning Checklist

10. Related Parameters for Extended BOP20 Display

Beyond the standard p0005 values listed in section 3, the G130 exposes the following connector outputs that are commonly mapped to the BOP20 via BICO for custom displays:

The standard p0005 list only exposes a subset of these via direct numeric selection. For OEM-specific displays (e.g., kW, torque, motor temperature), use a free connector via BICO and a user-defined display list, or replace the BOP20 with an AOP30 (Advanced Operator Panel 30) which supports user-defined screens. Reference: SINAMICS BOP20 / AOP30 Operating Instructions.

11. Safety, Lockout, and Working-State Considerations

• Display parameter changes (p0005, p0006, p0003) are non-safety-relevant. They can be performed in any operating state without disabling safety functions.
• If Safety Integrated (SI) is active on the drive, KHP on the Safety DO (separate from KHP on the Control Unit DO) does not affect p0005. p0005 lives on the Control Unit DO, not the Safety DO.
• Setting p0003 = 3 (expert) is a UI/UX feature, not a safety feature. It does not change the safety state, the Safety Integrated bit, or the stop behavior.
• Editing p0005 / p0006 while the drive is running under load does not affect the load, the motor, or the process. The BOP20 does not have a "control source" that competes with the PLC / terminal command source (p0700) for display edits. The risk is the key-lock being toggled by an unintended long-press on P + FN during the edit.

12. Frequently Asked Questions