Reading SINAMICS G120 Hand/Auto Mode Status in a PLC

David Krause11 min read
SiemensTechnical ReferenceVFD / Drives
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

The SINAMICS G120 is a modular frequency converter used for speed-controlled operation of three-phase motors. The drive accepts a manual/auto operating-mode command in two places:

  • Locally from the BOP-2 (Basic Operator Panel 2) HAND/AUTO key, or
  • From a digital input on the Control Unit (CU), wired to BICO parameter P806.

Once selected, the active mode is reflected in the read-only parameter r807. A PLC that needs to know which mode the drive is currently in (for example, to suppress a remote start, change setpoint source, or log operator actions) reads r807 — typically as a single bit in a periodic PROFINET/PROFIBUS telegram, or as a digital output on the CU wired back to the PLC.

This reference documents the exact parameter numbers, BICO interconnections, telegram bits, and wiring patterns required to make the Hand/Auto state visible to an external PLC. It is built around the CU230P-2 and CU240E-2 control units but applies to the whole G120 family with minor I/O index differences.

G120 Hand/Auto Operating Concept

The G120 distinguishes two command sources, often called the "Hand" and "Auto" channels:

Mode Default Setpoint Source Default Command Source (ON/OFF/REV) Typical Use
Hand Motor potentiometer (MOP) or BOP-2 keys BOP-2 RUN/STOP keys or DI selected by P806 Local commissioning, jogging, manual service
Auto Analog input, fieldbus setpoint, or fixed setpoint Fieldbus control word 1 (STW1) or DI Normal process operation driven by PLC

The selection between these two channels is stored internally and is independent of the drive's enable state. Selecting Hand does not start the motor; it only re-routes setpoint and command source.

Parameter P806 – Hand/Auto Command Source

P806 is a Binector Input (BI) parameter that defines where the drive listens for the Hand/Auto toggle. It is part of the command source group (parameter range 800–809 on most CU firmware versions).

Parameter Name Type Default Function
P806 Hand/Auto selection (source) BI (Binector Input) 0 (BOP-2 key only) 0 = Auto, 1 = Hand

The default value 0 ties Hand/Auto control to the BOP-2 button only. If you want a PLC or a hard-wired switch to override the BOP-2 selection, you must wire P806 to a digital input or to a control-word bit that the PLC writes.

Common interconnections for P806:

Wanted Source Value to Enter in P806 Notes
BOP-2 HAND/AUTO key only (default) 0 PLC cannot influence mode
DI3 of the CU 722.3 DI3 active = Hand, inactive = Auto
DI4 of the CU 722.4 Alternative input
DI5 of the CU 722.5 Alternative input
DI6 of the CU 722.6 Alternative input (CU230P-2 only)
PROFINET control word bit Fieldbus-dependent; route via free BI/BO connectors Requires telegram customization
Warning: The CU230P-2 has a different DI numbering than the CU240E-2. The index .3 always refers to DI3 on every CU; however, the actual terminal number is hardware-specific. Verify the terminal assignment in the wiring diagram of your CU before commissioning.

Parameter r807 – Hand/Auto Status Feedback

r807 is a Binector Output (BO) read-only parameter that mirrors the currently active mode. It is the answer to the question "what does the drive think the operator mode is right now?".

Parameter Name Type Value Meaning
r807 Hand/Auto status (actual) BO 0 = Auto active
1 = Hand active

Two important behavioural rules for r807:

  1. BOP-2 does affect r807. When the operator presses the HAND/AUTO key on the BOP-2, r807 toggles immediately, regardless of P806's source. This is a frequent commissioning surprise: engineers expect the BOP-2 key to be "overridden" by P806, but in reality the BOP-2 acts as a parallel front-panel selector.
  2. P806 affects the command/setpoint routing, r807 reports the mode. If P806 is set to 0 (BOP-2 only), the PLC cannot change the mode but can still read r807 to know what the operator selected.

BICO Interconnection Patterns

There are three practical ways to expose the Hand/Auto state to a PLC. Each has different latency, wiring cost, and firmware-version constraints.

Pattern A – r807 Wired to a Digital Output (CU Local I/O)

Route r807 into the source of a digital output, then wire the DO terminal back to a DI on the PLC.

CU DO Terminal BICO Parameter to Set Value
CU230P-2 DO0 (X11.5 / X11.6) P730.0 r807
CU230P-2 DO1 (X12.3 / X12.4) P730.1 r807
CU240E-2 DO0 (terminal 18/19/20) P730.0 r807

Use STARTER, Startdrive (TIA Portal), or the SINAMICS Web Server to set the parameter. After the parameter write, perform a power cycle or "Copy RAM to ROM" if you want the setting to survive a CU restart.

Pattern B – r807 Read via PROFINET/PROFIBUS Cyclic Telegram

The standard PROFIdrive telegrams (1, 2, 3, 4, 20, 350, 352, 353) do not include r807 directly. To expose r807 cyclically, you must either:

  • Use a free telegram (telegram 999 or a manufacturer-specific telegram) and add r807 as ZSW bit, or
  • Use acyclic parameter access (PROFIdrive parameter channel, DS47 / record-data) and read r807 in the PLC's background OB.

For S7-1200/S7-1500 with the SINA_SPEED or SINAMICS library, the recommended block is "SINA_ReadDriveParameter" or "RDREC" against the PROFINET slot. The slot/sub-slot for the drive object DO1 is 1; for the CU's parameter object (DO0) use slot 0.

Pattern C – r807 Mapped into ZSW1 (Status Word 1)

If a free status-word bit in ZSW1 is available (e.g., bit 9–13 depending on the active telegram), r807 can be BI-connected to one of those bits:

  • P2080[0..15] = bit source for ZSW1 bits 0..15 (CU-side ZSW1 = r2089)
  • Example: P2080[9] = r807 puts Hand/Auto state into ZSW1 bit 9.
Critical: ZSW1 bits are reserved by PROFIdrive for standard signalling. Overwriting an allocated bit (e.g., bit 3 = "Fault present") will break the standard fault-handling chain. Use an unallocated bit only, and document the override clearly in the project.

PLC-Side Integration (S7-1200 / S7-1500)

Reading r807 over PROFINET (Acyclic)

// SCL example for S7-1500 using RDREC
// Slot 1 = drive object DO1; index = parameter number 807
// Attribute = 0 (value)
#req.Header.Slot := 1;
#req.Header.Index := 807;        // r807
#req.Header.Length := 4;         // 1 WORD = 4 bytes
#status := RDREC(
    REQ          := TRUE,
    ID            := #hwIdDrive,
    INDEX         := 16#002F,    // PROFIdrive parameter channel
    MLEN          := 10,
    VALID         => #valid,
    BUSY          => #busy,
    ERROR         => #error,
    STATUS        => #recStatus,
    LEN           => #recLen,
    RECORD        := #paramRecord);
// r807 low byte contains 0 (Auto) or 1 (Hand)

Reading r807 via SINAMICS Library Block

With TIA Portal V17+ and Startdrive V17+ you can also use the official "SINA_PARA" or "LAcycStartDrvLib" blocks from the SINAMICS G120 library. The block encapsulates the PROFIdrive parameter request and returns r807 as an integer.

Commissioning Procedure

  1. Decide who owns the mode — local (BOP-2 / DI on the CU) or remote (PLC via fieldbus). This drives P806 configuration.
  2. Wire or define the source — if using a DI, land the wire on the correct terminal of the CU and document the terminal-to-index mapping (e.g., DI3 = 722.3).
  3. Set P806 in STARTER / Startdrive. Accept the prompt to "Copy RAM to ROM" if persistence is required.
  4. Configure the feedback path — either route r807 to a digital output (P730.x = r807) and wire to a PLC DI, or expose r807 over PROFINET.
  5. Verify r807 toggles — use STARTER's online watch on r807 while pressing the BOP-2 HAND/AUTO key. The value must change between 0 and 1.
  6. Verify the PLC sees it — in the PLC tag watch, force the input (for DI) or read the parameter (for acyclic PROFINET) and confirm the value tracks r807.
  7. Test fault transitions — issue an OFF2 from the PLC while the drive is in Hand. The drive must trip and r807 must remain at its last value (Hand/Auto is not cleared on fault).
  8. Document — record P806, P730.x, telegram layout, and PLC tag names in the project functional specification.

Verification Checklist

Check Expected Result Method
BOP-2 button changes mode r807 toggles 0/1 Watch r807 online in STARTER
DI3 wiring takes effect P806 = 722.3 confirmed; r807 follows DI3 Toggle DI3, watch r807
DO0 reflects r807 DO0 terminal voltage tracks r807 Multimeter on DO terminals
PLC receives status PLC tag updates within 1 telegram cycle (~4 ms at 250 µs) Cross-reference in TIA Watch table
Mode survives power cycle r807 resumes its last value if P806 is unchanged Cycle control voltage, re-check
Fault does not clear mode r807 still valid after OFF1/OFF2/OFF3 Trip drive, read r807

Troubleshooting Matrix

Symptom Likely Root Cause Corrective Action
r807 always 0 P806 not configured; BOP-2 not connected or not pressed Set P806 to intended source; verify BOP-2 ribbon cable
r807 always 1 DI assigned to P806 is hard-wired high; polarity wrong Check DI terminal voltage; configure P841 if inversion needed
BOP-2 button does nothing Parameter access locked; BOP-2 access level set to read-only Set P0003 ≥ 3 and P0010 = 0; check P0013 BOP access
PLC reads r807 but it does not update Acyclic parameter read not being re-triggered; telegram not configured Re-call RDREC cyclically; confirm slot 1 access
r807 toggles when BOP-2 pressed but PLC sees the inverse Polarity difference in DI vs. expected logic Apply inverter at P730 or invert the PLC tag mapping
Drive trips F08501 (PROFIdrive comm fault) after P806 change P20650 telegram mismatch (PZD assignment invalid) Restore default telegram; re-assign ZSW bits one at a time
Settings lost after power cycle RAM-to-ROM not executed Trigger "Copy RAM to ROM" via P0971 = 1 in STARTER/Startdrive
DO0 does not follow r807 DO inverted (P7418) or not set to source r807 Inspect P730.0; reset inversion in P7418 if present

Edge Cases and Field-Proven Caveats

  • BOP-2 + DI conflict: If P806 is wired to a DI but the BOP-2 is also connected, the BOP-2 key still toggles r807, but the command/setpoint routing still follows the DI. This means the drive can be in "Hand" per r807 but not actually respond to the BOP-2 RUN key. The fix is either to remove the BOP-2 or to align logic so both sources are in the same state.
  • Firmware version: Parameter numbering for P806/r807 is consistent from V4.4 through V6.0 of the G120 firmware, but the BICO of digital outputs changed in V5.x. Always cross-check the parameter list (r2) of your installed firmware version. The official list of all parameters is in the SINAMICS G120 Parameter Manual.
  • PROFIdrive application class 3 (AC3): If the drive is in application class 3 with active closed-loop control, the Hand/Auto handling is essentially identical but the safety telegram (PROFIsafe) and STW1/ZSW1 bit allocations differ. Override r807 onto ZSW1 only on unallocated bits (typically 11, 12, 13).
  • Multiple parameter sets: G120 supports up to four drive parameter sets (DDS). r807 is a status and not stored in the DDS, but P806 is. If the active DDS is switched, P806 may change, which will change the active command source for Hand mode.
  • Safety integrated (SINAMICS Safety Integrated): On a CU250S-2 with safety enabled, an SS1/STO does not affect r807. The Hand/Auto state is preserved across safety events, which is correct behaviour but must be tested.

Reference Parameter Summary

Parameter Direction Type Function Typical Source/Destination
P806 PLC → Drive BI Select Hand (1) or Auto (0) 722.3 (DI3) or BOP-2 default 0
r807 Drive → PLC BO Report active mode r807 → P730.0 (DO0), or to PROFINET ZSW1 bit
P730.0 Internal BI Source for DO0 Set to r807 for Hand/Auto feedback
P7418 Internal BI Inversion of DO0 (firmware-dependent) Use if r807 logic is inverted at the terminal
P2080[0..15] Internal BI Bit source for ZSW1 Use free index for r807 mapping
P0971 PLC → Drive CI Save parameters to ROM Set to 1 to persist settings

For full parameter lists and the BICO list, refer to the SINAMICS G120/G120C/G120D Parameter Manual and the SINAMICS G120 Operating Instructions. The latest firmware is available on the SINAMICS G120 support and download page. For TIA Portal integration, see the SINAMICS G120 in TIA Portal (Startdrive) manual.

What parameter reports the G120 Hand/Auto mode to the PLC?

Parameter r807. It is a read-only binector output: 0 = Auto, 1 = Hand. It updates immediately when the BOP-2 HAND/AUTO key is pressed and follows the source configured in P806.

How do I select Hand/Auto from a PLC or hard-wired input?

Assign P806 to a digital input (e.g., P806 = 722.3 for DI3) or to a free bit of the PROFINET control word using a free telegram. The default P806 = 0 keeps selection on the BOP-2 only.

Does the BOP-2 button still work if I set P806 to a digital input?

Yes. r807 still toggles when the BOP-2 key is pressed, but the command/setpoint routing follows P806. This can cause the drive to be in "Hand" per r807 yet not respond to the BOP-2 RUN key. Document the chosen logic carefully.

How do I read r807 from an S7-1200 or S7-1500 over PROFINET?

Use acyclic parameter access with RDREC against the drive object's parameter channel. Set INDEX = 16#002F (PROFIdrive parameter channel) and read parameter 807 from the drive object (typically slot 1). The returned value is a WORD with the active mode in the low byte.

Why is r807 always 0 even when I press the BOP-2 key?

Most commonly the parameter access level is locked (P0003 < 3) or the BOP-2 is in read-only mode. Set P0003 to at least 3 and P0010 = 0 to allow commissioning changes, then press the BOP-2 HAND/AUTO key while online in STARTER and watch r807.

Can I save the P806 assignment so it survives a power cycle?

Yes. After writing P806 in STARTER or Startdrive, trigger a RAM-to-ROM copy via P0971 = 1 (or use the "Copy RAM to ROM" toolbar button). The setting is then retained in non-volatile memory.

Does r807 reset when the drive trips on a fault?

No. r807 is the operating-mode status, not the drive status. It preserves its last value across OFF1, OFF2, OFF3, and faults. Read the drive status separately via ZSW1 bit 3 (fault present) or r2132 bit 3.

Back to blog