Siemens 6SE7024-7TD61: Changing P434 Scale Add Setp1 Safely

Overview

The Siemens 6SE7024-7TD61-Z is a member of the SIMOVERT MASTERDRIVES family of three-phase AC drives. Field engineers and commissioning personnel routinely need to adjust the additional setpoint scaling (P434) for process tuning, setpoint summation tuning, or to remove a bias contribution. A common concern when editing P434 is whether switching parameter P060 into the drive-setting value (P060 = 5) — often recommended as a workaround to gain access — inadvertently alters other commissioning values stored in the drive's parameter sets. This article identifies the safe sequence to change P434 on the 6SE7024-7TD61-Z, clarifies what P060 actually controls, and documents what is and is not affected when the drive-setting mode is entered.

The official Siemens industry support portal is the authoritative source for the MASTERDRIVES parameter manual, firmware notes, and parameter set switching logic: Siemens support search for MASTERDRIVES P434.

Drive Identification and Order Number Decoding

Before any parameter edit, confirm that the order number on the drive rating plate matches the documentation you are following. The Siemens 6SE7024-7TD61-Z order number decodes as follows:

Cross-check the firmware label on the front of the CUVC (CUmV or CUVC electronics card). On the OP1S / OP2S operator panel, read r005 (drive type) and r006 (firmware version). The P434 behavior described here applies to the 7TD6x firmware family; on legacy firmware, online-edit availability is reduced, and the drive may refuse to accept writes while in operation.

Parameter P434 — Function and Behavior

P434 is the scaling factor for "Additional Setpoint 1" within the MASTERDRIVES setpoint channel. The parameter multiplies the additional setpoint value before that value is summed into the main setpoint passed to the ramp generator. The default factory value is 100.00 % (unity gain). Reducing P434 from 100 % to 0 % removes the contribution of additional setpoint 1 from the setpoint sum without touching the analog-input conditioning (e.g. P632/P634) or the wiring.

Key attributes of P434:

• Index: Single-element parameter (not indexed); one storage location per parameter set.
• Set membership: P434 exists in all four parameter sets (DS1, DS2, DS3, DS4). Each set carries its own copy.
• Editable states: Acceptable write states are typically r001 = 011 (Ready for operation) and, on firmware that permits online editing, r001 = 014 (Operation). Always verify the firmware revision before assuming online write.
• Resolution: 0.01 % typical; consult the parameter list for the exact resolution on your firmware.

Parameter P060 — Parameter Set Selection

P060 is a system-level parameter that selects the active parameter set or enters commissioning / drive-setting mode. Its accepted values are 0 through 5 with the following mapping on the 6SE7024-7TD61-Z:

When P060 is 1, 2, 3, or 4, parameter writes affect only the selected set; the drive does not change state. When P060 = 5, the drive enters drive-setting mode and parameter writes broadcast to all four parameter sets. Exiting requires returning P060 to 1–4 (or to 0) and, in some firmware revisions, executing a save command (P971) to commit to EEPROM.

Why the Original Two-Case Procedure Raises Concerns

The two-case workflow originally proposed was:

• Case A: If r001 = 011 (Ready for operation), edit P434 directly.
• Case B: Otherwise, set P060 = 5, verify r001 = 05, edit P434, then restore P060 to 1.

Case A is the preferred method and is correct as written. Case B is workable but introduces three concrete risks on the 6SE7024-7TD61-Z:

1. Cross-set overwrite: In drive-setting mode (P060 = 5), the value written to P434 overwrites the same location in all four parameter sets. If DS2, DS3, or DS4 previously carried a different P434 (e.g. for a recipe change), those legacy values are silently lost.
2. Implicit save requirement: Some MASTERDRIVES firmware revisions require an explicit P971 (save parameters to EEPROM) after returning from P060 = 5 to P060 = 1, or the new P434 value reverts on the next cold start.
3. State machine coupling: Switching P060 = 5 forces r001 = 05 and disables the run enable. If the drive is mid-process, this triggers a coast stop via the OFF1/OFF3 logic depending on the wiring of the enable inputs.

Recommended Procedure to Modify P434

The clean sequence for changing P434 on the 6SE7024-7TD61-Z without disturbing unrelated parameter sets:

1. Confirm the drive state by reading r001 from the operator panel. Acceptable source states are typically r001 = 011 (Ready for operation) — preferred — or, where firmware permits online editing, r001 = 014 (Operation).
2. Read r061 (active parameter set, 1–4). Document this value: you are about to edit this DS's P434 only.
3. Navigate to P434 on the OP1S / OP2S or via DriveMonitor / SIMOVIS.
4. Enter the new value (for example, 0.00 % to zero the contribution). Press the panel's "P" (parameterize) key or the equivalent DriveMonitor commit to write.
5. If the drive is running (r001 = 014), the new value takes effect on the next setpoint scan. Observe the process response before leaving the drive.
6. Issue P971 = 1 to save to non-volatile memory if the change is permanent.
7. Document the new value, the active DS, and the firmware revision in the drive's parameter log card.

If the goal is to change P434 in a parameter set that is not currently active (for example, DS2 is the recipe you want to prepare for the next shift, but DS1 is currently driving the motor), use this alternate sequence instead:

1. Stop the drive via OFF1 so that r001 = 011 (Ready for operation).
2. Set P060 = 2 to make DS2 active. Verify r061 = 2.
3. Edit P434 to the new value.
4. Return P060 to its previous value (or to 0 for external selection).
5. Issue P971 = 1 to save to EEPROM.

What Happens When P060 = 5 (Drive-Setting Mode)

Entering P060 = 5 on the 6SE7024-7TD61-Z produces several side effects that commissioning engineers must understand:

Verification After Changing P434

After committing the new P434 value, perform the following checks before handing the drive back to operations:

1. Read-back verification: Read r434 from the operator panel or DriveMonitor. Confirm the displayed value matches what you wrote.
2. Active-set confirmation: Read r061 and confirm it matches the parameter set you intended to modify.
3. Setpoint summation check: With the drive enabled but the motor at standstill (OFF2 or zero speed reference), observe the summed setpoint displayed in the setpoint-total readout. The expected contribution from additional setpoint 1 is 0.00 % when P434 = 0 % and the additional input is at zero.
4. Run verification at no-load: Issue a small setpoint and confirm the motor follows. If the additional setpoint is fed from an analog input, verify that the contribution from that input is now scaled to zero.
5. Cold-start verification: With the main power removed and the DC bus discharged per site safety procedure (typically below 50 V on the DC link test points), cycle the 24 V control supply on the CUVC electronics card. On reboot, read r434; it must retain the new value if P971 was executed.

Troubleshooting Matrix

Field Commissioning Caveats and Edge Cases

Cold-start vs. warm-restart persistence

A cold start (full power removal, including the 24 V control supply on the CUVC electronics card) triggers an EEPROM reload. If P971 was not executed, the RAM-resident P434 value is lost and the EEPROM-stored value returns on the next cold start. A warm restart (main power removed, DC bus discharge, 24 V control supply retained) does not reload EEPROM, so the RAM value persists. Always perform a cold-start test when you claim a permanent change has been saved.

Parameter set hot-swap during operation

The MASTERDRIVES supports parameter-set hot-swap via binary inputs when P060 = 0. If you set P060 = 5 mid-run and then return to 0, the next binary-input-driven set change applies the modified DS. Coordinate with the control system integrator to avoid mid-cycle set swaps that could trigger unexpected process behavior.

Firmware revision dependence

Online editing of P434 in r001 = 014 is firmware-dependent. Earlier MASTERDRICES firmware revisions may not permit parameter writes while running. Check r006 and reference the firmware-specific edit matrix from Siemens support search for MASTERDRIVES P434 before relying on an online-edit sequence.

BICO source for the additional setpoint

P434 scales the value entering the additional setpoint node in the setpoint channel, but the source of the additional setpoint is selected by connector parameter P632 (analog input assignment). Setting P434 = 0 % does not detach the input; it only scales the contribution to zero. If the analog input later becomes active, a 0 % scaling prevents runaway, but the input is still wired to the setpoint chain. To fully detach, repoint P632 to a constant zero or an unused connector.

Interaction with PID / process controller

If the drive is configured for closed-loop process control, P434 may affect the additional process setpoint path. After changing P434, verify the process setpoint total does not cause a process bump on the next enable. Consider stepping the setpoint from zero to its operating value to observe the response before committing to production.

Backing up parameter sets before edits

Best practice: read all four DS copies of P434 (cycle P060 1 → 2 → 3 → 4 → 1, reading r434 each time) and document them in the drive's parameter log. If a P060 = 5 edit inadvertently clobbers an unexpected value, the log allows restoration.

Alternative controllers and platforms

The MASTERDRIVES P434 / P060 architecture is specific to the 6SE70 family. Newer Siemens drive platforms — SINAMICS G120, G130, S120, S150 — use a different parameter numbering scheme (e.g. p2900 range and p21500 / p21510 ranges for setpoint scaling, and parameter set selection via p0820 / p0821 with drive setting via a separate bit, not a P060-style numeric mode). Do not apply this procedure verbatim to a SINAMICS drive without consulting the platform-specific parameter manual.

FAQ