Removing K80 Safe Stop from Siemens Masterdrive VC: Procedure

Overview of the K80 Safe Stop Option on Masterdrive VC

The K80 option on the Siemens MASTERDRIVE VC (6SE70 series) implements a hardware-based Safe Stop function, broadly equivalent to category 1 / SS1-style stop behavior in modern IEC 61800-5-2 terminology. It is a factory-fitted option only on the Compact-Plus (6SE702x) variants and cannot be retrofitted in the field. Compact and chassis-format units (6SE703x, 6SE709x) have different retrofit rules and should be treated as a separate engineering exercise.

The option is sometimes colloquially referred to as "Z80" in informal documentation; the correct Siemens ordering code is L80 / K80 in the MLFB (Maschinenlesbare Fabrikate-Bezeichnung, machine-readable product designation) — verify the option code on the drive rating plate before commencing any work. The original equipment in the case described is a 6SE7021-0TP60, which is a Compact-Plus 2.2 kW class unit in the 6SE70 family.

Identifying Whether the K80 Option Is Fitted

Before any parameter manipulation, confirm the option status. Three independent indicators must agree:

1. MLFB / Order Code — the 6SE7021-0TP60-Z suffix (the "-Z" plus option code) appears on the rating plate. K80 will be appended if fitted at the factory.
2. Physical connector X533 — a 4-pin Phoenix-style connector is present on the top-left of the unit, immediately adjacent to the control terminal block. Drives supplied without K80 do not have this connector populated on the PCB; the footprint may exist but is unpopulated.
3. Drive parameter r977 / r978 (control word status) — read back the safety-related status indicators from the drive parameter set. The exact parameter index varies with firmware version; consult the parameter list for the firmware load installed (see firmware identification below).

Only proceed with parameter changes once you have confirmed, by physical inspection, whether X533 is populated. If the replacement drive is a spare that has never had K80, there is no safety interlock to release — only the parameter expectations of the upstream controller need to be normalized.

Hardware Architecture: X9, X533, and the Safety Path

The K80 option implements a hardware interlock that breaks the gate-pulse path to the IGBTs (Insulated Gate Bipolar Transistors — the drive's power-switching devices) when the safety input is opened. The relevant terminals are:

Key engineering rule: With K80 fitted, the safety function is enforced by a hardware break in the gate-pulse path. Parameters alone cannot recreate a Safe Stop function. Setting P555/P556/P557 only changes which binectors (binary control flags used internally by the drive firmware) gate the OFF1/OFF2/OFF3 ramps; it does not re-establish a safety-rated hardware interlock. This is the single most important misconception in the field and is the reason multiple sources in the original case study pushed back hard on the proposal.

Parameter Map: P555, P556, P557, P558, P561

The MASTERDRIVE VC parameter model is binector-driven. The following parameters are the ones typically involved in any Safe Stop deactivation. Read the current values and record them (DriveMonitor trace or r parameter readback) before making changes.

Firmware Identification and Parameter-Lock Behavior

MASTERDRIVE VC firmware versions in service today range from V1.x through V3.x (the latter shipped with later 6SE70 hardware). Some firmware loads have a parameter-write protection that must be released before P555–P561 can be changed. The procedure is:

1. Read r001 — drive state (must be in Ready or Run, not Fault or Commissioning lock).
2. Set P053 = 7 (parameter-access enable for the safety-related subset). Some firmware loads require P052 = 40 first as a master access key.
3. Read r060 / r061 to confirm the firmware version and the parameter set in use. Cross-reference against the Siemens Industry Online Support (SIOS) portal parameter manual for that version — older loads (V1.x) have different numbering for the safety parameters than V2.x+ loads.

If the drive is password-locked (P052 contains a non-zero user password), obtain the password from the responsible engineer before proceeding. There is no factory backdoor password for production firmware loads.

Procedure: Replacing a K80-Fitted Drive with a Non-K80 Spare

The cleanest case is a planned replacement of a failed unit, where the original was K80-fitted and the spare is not. The objective is to get the non-K80 drive into a state where the upstream controller sees a normal, ready drive without the safety interlock asserting a permanent fault.

Pre-work

1. Lock out and tag out the drive (LOTO — Lockout/Tagout, the procedure for ensuring equipment is de-energized and cannot be re-energized until maintenance is complete) per site procedure. Wait the discharge time printed on the front of the unit (typically 5 minutes for 400 V class units) before opening covers.
2. Verify zero energy at the DC bus with a Cat III (CAT III 600 V minimum) meter on the DC-link test points (measured DC bus voltage should be < 5 V DC before proceeding).
3. Document the existing parameter set via DriveMonitor, STARTER (Siemens' commissioning software, suitable for older 6SE70 units with the correct firmware), or by hand-typed list. Include the safety-related P555–P561 values and their binector sources.

Spare-Drive Preparation

1. Confirm the spare's MLFB and that it has no K80 option. The spare will not have an X533 connector on the PCB. Do not attempt to wire to a non-existent connector footprint.
2. Apply power to the spare and read P053, P052, and the safety-related subset. Note the firmware version (r060 / r061).
3. Upload the parameter set from the original (K80) drive if available. Caveat: if you upload naively, the safety-related parameters will be transferred as set, and the drive will appear to "expect" a K80 input that does not exist. The recommended workflow is to:

• Upload all non-safety parameters from the original drive (P000–P500, P600–P999).
• Manually set the safety subset (P555, P556, P557) to a known safe default — typically 0 (always released) for a decommissioned safety function, or to a digital input that mimics the original Profibus bit if the upstream PLC still asserts it.
• Set P558 and P561 to match the original — typically P558 = 0 (control word bit 0 via Profibus) and P561 = 0 (control word bit 2 via Profibus).

Re-commissioning

1. Restore the original control wiring (Profibus, terminals, encoder, motor cables). Do not attempt to wire to X533 pins 1/2 or X9 pins 3/4 on the non-K80 drive — the safe-stop hardware path does not exist.
2. Run a no-load commissioning (motor uncoupled) at low speed (5 Hz) to verify direction, encoder feedback, and the OFF1/OFF2/OFF3 ramps.
3. Test each stop command source: Profibus control word bits 0 and 2, terminal stops if wired. Confirm the drive ramps down rather than coasting for OFF1, and that OFF3 (fast stop) is still functional via the parameter (not the safety hardware).

Parameter Reference: Common Binector Sources for P555–P561

The exact binector numbering depends on the firmware version. Always cross-reference against the Siemens MASTERDRIVE VC parameter list for the specific firmware load in use. Do not guess binector numbers from one firmware to another — they can shift between V1.x and V2.x.

Verification: How to Confirm the Drive Is Operating as Expected

1. No faults on first power-up: the drive should reach state o007.0 (Ready for Run) within 5 seconds of pre-charge completing. Any F-fault related to "safe stop," "SS1," or "X533 open" indicates either the wrong parameter set is loaded or the wrong spare has been selected.
2. Control word handshake: with the PLC asserting the standard 047Eh control word (the typical "enable operation" pattern: bit 0 = ON, bit 1 = no OFF2, bit 2 = no OFF3, bit 3 = enable, bit 4 = enable ramp, bit 5 = reserved, bit 6 = enable setpoint), the drive should accept the run command. If the PLC is configured to assert a safety bit, that bit must be re-mapped in the PLC program, not in the drive.
3. Stop-ramp validation: from 50 Hz, command OFF1 via Profibus — the drive should ramp to zero in the time set by P464 (ramp-down time 1), typically 5–10 s. Then command OFF3 — the drive should ramp to zero in the time set by P466 (ramp-down time 3, the fast-stop time), typically 0.5–3 s.
4. Loss-of-comms test: physically disconnect the Profibus connector; the drive should execute the comms-failure response defined by P685 (default: OFF2 / coast). If the drive continues to run, the fieldbus watchdog is not configured correctly — this is a separate problem from the K80 removal but is often uncovered during the same commissioning visit.

Safety and Compliance Implications

Removing a Safe Stop function is a functional-safety change, not a parameter edit. The following must be addressed before the drive is returned to service:

• Risk assessment update: the original safety function (hardware break of the gate-pulse path) contributed to the machine's PL (Performance Level, defined in ISO 13849-1) or SIL (Safety Integrity Level, defined in IEC 61508) rating. Removing it requires a new risk assessment under ISO 12100 and a documented justification.
• Alternative stop category: if the machine previously relied on K80 for category 1 stop, an equivalent stop must be implemented externally (e.g., a contactor in the motor supply, a certified safety relay monitoring a hard-wired E-stop loop, or a replacement drive with a current-generation safety option such as STO (Safe Torque Off) or SS1).
• Documentation trail: the parameter changes (P555, P556, P557) must be recorded in the machine's technical file, with the date, the engineer, the firmware version, and a justification. Most regulatory bodies expect this to be a controlled engineering change, not a field tweak.
• Marking the drive: apply a label on the front of the unit indicating that the original Safe Stop function is no longer present. This prevents a future engineer from assuming the drive is K80-functional based on its appearance alone.

Troubleshooting Matrix

Alternatives to Removing the K80 Function

Before deciding to remove the K80 function, consider these alternatives, in order of preference:

1. Source a K80-fitted replacement. Siemens used to offer the K80 as a factory option on the 6SE7021 series. The lead time is the typical constraint, not feasibility. Contact your Siemens drive spares channel with the original MLFB including the -Z option code.
2. Replace the entire drive with a current-generation SINAMICS platform. The SINAMICS S120, G120, or V90 families offer certified STO and SS1 functions as standard options, with full support for PROFIsafe (the safety communication profile over Profinet/Profibus). The mechanical and electrical retrofit path is well-documented and the safety case is far easier to defend.
3. Add an external safety contactor upstream of the drive. If the machine's risk assessment allows a category 0 stop (immediate removal of power) as an alternative to category 1, a certified safety contactor in the motor supply lines can provide an equivalent PL/SIL rating. This is the lowest-cost path and is appropriate for non-Servo, non-vertical-axis applications.
4. Accept the loss and re-rate the safety function. Only valid if the machine's risk assessment permits it. Requires sign-off from a competent safety engineer and a documented change to the technical file.

Field-Proven Caveats

• The K80 option label can also appear as "L80" on some markets' MLFB encoding; cross-check the order code, not the option suffix, before any work.
• Some 6SE70 firmware loads (notably V1.4x) treat P555–P557 as a triple — changing one without the others causes an internal consistency check to fail and the drive to refuse to leave the commissioning state. Change all three in the same parameterization session.
• DriveMonitor v5.x and earlier cannot read the safety subset on firmware V2.20+ without the safety-license dongle. STARTER is unaffected.
• If the upstream PLC expects a "Safety OK" feedback bit, that bit will never come on a non-K80 drive. Either re-map the PLC logic to ignore the bit, or hard-wire a permanent "OK" signal from a separate source. This is the most common cause of a PLC refusing to enable the run command after the K80 drive is replaced.
• Masterdrives approaching end-of-life (manufacture date > 20 years) may have dried-out electrolytic capacitors in the safety path. Even if you are keeping the K80 hardware, plan for a full capacitor refresh on the safety PCB before re-commissioning.

Summary Workflow

1. Confirm the spare drive is not K80 by physical inspection of X533 and the MLFB.
2. Capture the original K80 drive's full parameter set, with special attention to P555, P556, P557, P558, and P561 — and the binector sources of each.
3. Power the spare, identify firmware (r060 / r061), unlock P053 = 7.
4. Set P555 = P556 = P557 = 0 (or to a digital input that mimics the original Profibus bit if the PLC still asserts one).
5. Set P558 = 0, P561 = 0 to match standard control-word-driven OFF1 / OFF3.
6. Do not wire anything to X533 pins 1/2 or X9 pins 3/4 on the non-K80 drive.
7. Re-commission with motor uncoupled: test run, OFF1, OFF3, loss-of-comms.
8. Update the machine's technical file, apply a "Safe Stop removed" label, and inform the safety engineer.