SINAMICS V20 Parameter Backup and Modbus-Compatible Drive Enable Setup

The SINAMICS V20 is a general-purpose 1AC/3AC drive in the Siemens SINAMICS family, and it appears widely in small pumps, fans, conveyors, and air-compressor skids. Two practical questions come up repeatedly on fielded V20 installations that are controlled over Modbus RTU: (1) how do I save and replicate the parameter set without losing the application tuning, and (2) how do I hard-wire a maintained safety interlock — typically an air-pressure, door, or e-stop contact — into a drive that is otherwise told to run by a Modbus master. This document covers both, with the exact parameter paths, the firmware gating that blocks the modern backup tools, the BICO interconnect that ties a digital input to the V20's pulse enable, and the verification steps that prove the interlock actually removes torque from the motor.

1. Prerequisites

Before configuring the backup workflow or the Modbus enable interlock, confirm the following baseline:

• Drive model and frame: 6SL3210-5BE... (1AC 230 V), 6SL3210-5CE... (3AC 400 V), or 6SL3210-5DE... (3AC 230 V). Frame size determines which options physically fit (FSAA and smaller frames do not accept all option modules).
• Firmware version: read with r0019. The parameter is read-only. Confirm the string matches one of the V20 release branches (3.92, 3.93, 4.x) listed in the operating instructions entry SINAMICS V20 Operating Instructions (ID 109773836).
• Command source today: read P0700. For Modbus RTU control the typical setting is P0700 = 5 (USS/Modbus via RS485) with P1000 = 5 for setpoint source. Any change to digital-input functions must not collide with these assignments.
• Hardware options: at least one of (a) Smart Access Module 6SL3255-0VA00-5AA0, (b) Parameter Loader 6SL3255-0VE00-0UA0, or (c) a BOP 6SL3255-0VA00-4BA0 plus a means of reading/writing .xml or .clx files.
• Free digital input: the interlock described below assumes DI4 is unused. If DI4 is already assigned, the same BICO scheme works on DI1–DI3 by using the matching bit of r0722.

2. SINAMICS V20 Firmware Landscape

The V20's firmware gating is the single most common reason backup tools fail in the field. The compatibility matrix for the option modules that touch the parameter store is:

If the drive's r0019 reads lower than 3.93, the upgrade is mandatory before SAM commissioning. The legacy upgrade path is to upload the new firmware through the Parameter Loader from a PC with the SINAMICS V20 Assistant tool, then download the firmware from the Loader to the drive. The same workflow simultaneously writes the parameters into P0010 = 30 commissioning-filter mode and saves the user parameter set. Verify post-upgrade with r0019 and by reading P0010 = 0 on the next power-up.

3. Method 1 — Backup via Smart Access Module (SAM)

The SAM is the cleanest end-user backup path. It plugs into the V20's option port on the front face and exposes a Wi-Fi access point. After the wireless connection is up, browse to the SAM web page to upload the live parameter set to the drive, then download it as an .xml file on a PC or tablet. The official step sequence per the SAM manual ID 109780683 is:

1. Power down the drive. Insert the SAM into the V20's option slot until it latches. Power back up.
2. From a PC or mobile device, connect to the SAM's Wi-Fi SSID (default SINAMICS_V20, password on the SAM label). Open 192.168.1.1 in a browser.
3. On the SAM home page, choose Backup. The SAM copies the live parameters from the drive RAM into its internal store and offers an .xml download link.
4. Save the .xml to a versioned folder on the PC. Treat this as a controlled artifact under the plant's change-management procedure; the file is a complete V20 parameter image that can be re-flashed to a replacement drive.
5. To restore: choose Restore on the SAM page, browse to the saved .xml, and confirm. The drive cycles through the parameter list and writes each parameter non-volatile.

4. Method 2 — Backup via the Parameter Loader

For drive-to-drive cloning — common when commissioning a fleet of identical fans or pumps — the Parameter Loader is the right tool. It is a small sealed module that sits between two V20 option ports and copies parameters without a PC in the loop. Procedure:

1. With the source drive powered and at stop, set P0010 = 30 on the source. The BOP or SAM will display the parameter-set loader view.
2. Power down. Unplug the Loader from the source drive. The Loader retains the parameter image in its own non-volatile store.
3. Power down the target drive, plug the Loader in, and power up. The Loader writes the saved image to the new drive automatically when P0010 = 30 is active on the target.
4. Verify on the target by reading a checksum of critical parameters (motor data P0300–P0311, command source P0700, setpoint source P1000, and any application-specific tuning such as ramp times P1120/P1121).

The Parameter Loader doubles as the firmware upgrade vehicle for V20 units shipped below 3.93. The procedure and tool versions are documented at ID 109743991. A typical upgrade cycle is 4–6 minutes end-to-end.

5. Method 3 — Backup via BOP or MMC Card

If no SAM or Loader is on site, the BOP plus a micro-MMC card (FAT16/FAT32, ≤2 GB) can save a single drive's parameter set:

1. Insert the MMC card. Set P0010 = 30.
2. On the BOP, navigate to Clone → Upload to MMC. The drive writes a parameter file named CLONE00.BIN.
3. To restore, fit the same MMC into the target drive, set P0010 = 30, and select Clone → Download from MMC.

The MMC path is fully functional on firmware 3.92, but it stores a binary image rather than the human-readable .xml produced by SAM. For engineering documentation and audit trails, prefer the SAM workflow where possible.

6. Drive Enable Under Modbus Control — The Real Question

When a Modbus master (PLC, HMI, SCADA) owns the run command, the V20's command source is P0700 = 5 (USS/Modbus via RS485). The control word for start/stop and the main setpoint both arrive on the serial line. The question that the original engineering inquiry raises — and that is repeated across V20 application notes — is whether a hard-wired maintained switch can be added so that the drive physically cannot run regardless of what the Modbus master commands.

The intuitive answer — "set P0701 = 1 and treat DI1 as ON/OFF1" — works only when the command source is terminal-based (P0700 = 2). With P0700 = 5, the run command is owned by the control word, and overriding it from a digital input requires a BICO interconnect rather than a simple function assignment.

7. Why P0701=1 Doesn't Fit Under Modbus

Setting P0701 = 1 assigns the value ON/OFF1 to DI1. Internally this links DI1 to P0840[0], the OFF1/ON command. Under P0700 = 5 (Modbus), P0840[0] is driven by Modbus control word bit 0, not by DI1. The DI1 assignment to P0840[0] therefore does not gate the drive in the way an engineer might expect: Modbus bit 0 still commands the drive, and DI1 becomes a second, parallel source feeding the same internal control word. The two are OR-combined, not AND-combined, so a low DI1 does not block a Modbus start.

To get an AND-gating effect — Modbus says start AND a hard-wired interlock says safe — the digital input must drive an OFF2 command, not ON/OFF1. OFF2 is the pulse-cancellation command in SINAMICS topology; activating OFF2 removes gate pulses from the IGBTs immediately, which decouples the drive from the motor in a way that no Modbus bit can override.

8. BICO Interconnect: P0704=99 with P0852[0]=722:3

The clean field-tested interconnect uses BICO parameterization to wire DI4 directly into the V20's pulse enable (OFF2) input. The exact two-parameter write is:

After these writes, the drive's behavior is:

• DI4 HIGH (24 V applied): bit 3 of r0722 is 1, OFF2 is inactive, the IGBT gate pulses are enabled, and the Modbus control word is free to start the drive.
• DI4 LOW (0 V or open): bit 3 of r0722 is 0, OFF2 is asserted, the drive immediately removes gate pulses and the motor coasts to rest. Modbus commands and setpoint changes are accepted into the control word but produce no torque at the motor.

9. OFF2 (Pulse Enable) vs OFF1 (Coast-to-Ramp) vs OFF3

SINAMICS command structure distinguishes three stop modes that are easy to conflate in field wiring:

The pressure-interlock use case is correctly served by OFF2 because the goal is not a controlled deceleration but an unambiguous removal of torque when the air supply fails. If the application instead requires the motor to ramp down on loss of interlock — for example, to protect downstream check valves from water hammer — OFF3 is the correct choice and the interconnect becomes P0854[0] = 722:3 instead.

10. Wiring a Maintained Pressure Switch to DI4

The terminal layout on the SINAMICS V20 control board places DI4 on the same removable plug as DI1–DI3 and the 24 V output. Pin references are confirmed in the wiring diagram inside the operating instructions (ID 109773836); the relevant excerpt for a typical FSAA–FSC frame is:

Wire the pressure switch so that its closed contact sits between terminal 8 (DI4) and terminal 9 (+24 V). When pressure is above the cut-in threshold, the contact closes, 24 V appears at DI4, and the drive is allowed to run. When pressure falls, the contact opens, DI4 returns to 0 V through its internal pull-down, OFF2 asserts, and the drive removes gate pulses regardless of the Modbus control word.

11. Step-by-Step Commissioning Procedure

1. Verify firmware. On the BOP or SAM, read r0019. If below 3.93, upgrade via the Parameter Loader before attempting the SAM backup.
2. Capture a baseline. Use SAM or BOP to download the current parameter set. Store the file under the plant's revision-control system. This is the rollback artifact.
3. Set the BICO interconnect. With the drive at stop and P0010 = 0, set P0704 = 99 and P0852[0] = 722:3. Press the BOP 'OK' key or use the SAM commit button to write the parameter to non-volatile memory.
4. Wire the interlock contact to DI4. Confirm 24 V is present at DI4 with the interlock in the "safe" state, and that DI4 drops to 0 V with the interlock in the "trip" state.
5. Test Modbus-driven run with interlock released. From the Modbus master, issue control word 0x047E (ready, energized, no coast stop, no quick stop, enable, no fault, no setpoint enable → next write 0x047F for run, setpoint enable). The drive should ramp to setpoint.
6. Test Modbus-driven run with interlock active. With the drive already running, open the interlock contact. The drive should immediately remove gate pulses; the BOP will show OFF2 active. Modbus status word bit 1 (drive ready) will clear and bit 13 (alarm active) will set as appropriate.
7. Re-arm and verify. Close the interlock, then issue a fresh run command from Modbus. The drive should restart cleanly.
8. Save the final parameter image. Repeat step 2 to capture the post-commissioning backup.

12. Verification Checklist

After commissioning, walk the following list. Any failure indicates that either the parameter write did not take, the CDS index is wrong, or the wiring polarity is reversed.

• r0722.3 reads 1 when 24 V is applied to DI4 and 0 when it is removed.
• r0046.0 (OFF2 inactive) reads 1 when DI4 is high and 0 when DI4 is low.
• Modbus run command with DI4 low: motor does not turn, drive status word reports not ready.
• Modbus run command with DI4 high: motor runs; opening DI4 stops the motor within one control cycle (typically ≤20 ms at 9600 baud, faster at higher baud rates).
• Alarm history r0947[0..7] does not accumulate F0001 (overcurrent) or F0021 (ground fault) entries from the commissioning test. Repeated assertion of OFF2 under load should not generate these faults because the IGBTs are not switching during coast-down.

13. Troubleshooting Matrix

14. Modbus Status-Word Bits Worth Knowing

Once the BICO interlock is in place, the Modbus status word reflects the interlock state in two places. From the V20 Modbus register map (PZD1 / word 1 returned to the master):

Reading bit 1 in the SCADA is the cleanest way to confirm at a glance that the interlock has released the drive's output stage and not merely that Modbus registers are still being exchanged.

15. Integration with a Higher-Level Controller (S7 / TIA Portal)

If the Modbus master is a SIMATIC S7-1200 or S7-1500 CPU, the same BICO interlock is invisible to the application code — the S7 only sees the V20 as a Modbus slave with control and status words. The PLC program should:

1. Poll status word bit 1 (pulses enabled) at the configured Modbus scan rate.
2. If bit 1 reads 0 while the application has issued a run command (control word bit 0 = 1), flag the interlock as "asserted" and treat the drive as not running.
3. Avoid issuing repeated OFF2 resets if the interlock contact is still open — let the field hardware release first, then issue the run command.

For plants where the V20 is part of a larger PROFINET / PROFIBUS topology and parameters must be pushed down during plant operation, see the function manual section on changing and saving device parameters during plant operation for the function-block pattern that pairs a CPU-side write trigger with a backup call.