Overview
The Siemens SINAMICS G120 modular drive system, when populated with a CU230E-2 control unit, is typically configured for safety-first operation: after a power cycle the drive boots, reads its parameter image, and waits for a fresh rising edge on the ON/OFF1 command source before it will run the motor. In many OEM and process applications (pumps, fans, conveyors, refrigeration compressors) this default behavior is undesirable. The application requires the drive to start the motor automatically as soon as the line and control voltage are healthy, using the last analog setpoint or a 4-20 mA process reference.
This reference documents three field-proven methods to achieve automatic restart on the G120 / CU230E-2 after a mains power interruption or a complete power-up:
-
Method 1: Built-in automatic restart using
p1210in combination withp840and the standard digital input wiring. -
Method 2: Free Function Blocks (FFB) — specifically a delay-on-make timer driven by the parameter
r20160— to synthesize a valid ON command a few seconds after the CU has finished booting. - Method 3: External power contactor interlock that uses the contactor's own auxiliary NO contact to re-issue the run command only after the contactor has been latched and the line is stable.
Each method has different implications for EMC, safety integrity, restart behavior after a fault, and the response of external safety circuits. Select the method based on the SIL/PL requirement of the machine, whether STO is wired, and whether the application is attended or unattended.
Prerequisites
| Item | Detail |
|---|---|
| Drive | SINAMICS G120 with PM240-2 or PM230 power module |
| Control unit | CU230E-2 (any variant: E, F, PN, DP) — MLFB 6SL3246-0BA22-1FA0 / -1PA0 / -1CA0 |
| Firmware | V4.7 SP3 or higher recommended; FFB support requires V4.4 or higher |
| Tooling | STARTER V5.1 SP1+, SINAMICS Startdrive V15+, or a BOP-2 / IOP-2 keypad |
| Setpoint | Analog input 0 (terminals 3/4) — 0-10 V or 4-20 mA configured via p756
|
| Command source | Digital input 0 (terminal 5) — 24 V sink or source per p0728
|
| Safety | STO inputs (X12.1, X12.2 on CU230E-2) wired to enable drive; F-DI not required for this configuration |
| Documentation | CU230E-2 List Manual (Parameter Description); CU230E-2 Operating Instructions; SINAMICS G120 Function Manual Free Function Blocks |
Before You Begin
Confirm three things before changing any parameter:
- The motor data identification (
p1910) and any rotating measurement (p1960) have been completed and saved to the active parameter set. - The drive was commissioned with the analog setpoint, and the ramp-up/down ramps in
p1120andp1121are appropriate for an unattended restart. - The application is rated for automatic starting; check the relevant product standard (e.g. EN 60204-1 §5.3 for unexpected start, NFPA 79 §6.4 for industrial machinery).
Understanding the G120 / CU230E-2 Power-Up Sequence
The CU230E-2 control unit executes a defined sequence on every power-up. The relevant steps for the auto-restart behavior are:
The critical detail is in the line labelled p840 (the ON/OFF1 command). Even if digital input DI 0 is held at logic 1 the entire time the control unit is booting, the SINAMICS firmware only accepts a 0→1 edge on this signal as a valid run command once the drive has reached the "ready" state. With the DI held continuously high, no edge exists, so the drive remains in the OFF1 state (r52.0 = 0) and the motor does not start.
Method 1: Built-In Automatic Restart (p1210)
Parameter p1210 defines the automatic restart behavior. Setting it to a non-zero value allows the drive to self-clear certain faults, re-acknowledge them, and issue a fresh run command after a mains power interruption or a black-out, using the last valid setpoint and the wired command source.
Required Parameter Set
| Parameter | Value | Description |
|---|---|---|
p840 |
r722.0 | BI: ON/OFF1 = status of DI 0 (rising edge still required) |
p1000 |
2 | Setpoint source = analog input (setpoint already wired) |
p1210 |
4 or 5 | Restart only after mains failure / restart with remaining faults and delay |
p1211 |
3.0 s (typical) | Wait time before automatic restart attempt |
p1212 |
10.0 s (typical) | Wait time between restart attempts |
p1213 |
3 (typical) | Maximum number of restart attempts |
p1210 Settings — Reference
| p1210 | Behavior | Typical Application |
|---|---|---|
| 0 | Disabled. No automatic restart. | Default — safety-first machines |
| 1 | Acknowledge all faults and restart at p1211
|
Test / commissioning |
| 2 | Acknowledge all faults + restart only if ON command active (rising-edge or level) | Process pumps with held-on DI |
| 3 | Acknowledge only critical faults, then restart | Re-energize after a glitch |
| 4 | Restart only after a line-side power interruption, all faults acknowledged | Recommended for unattended restart on power-up |
| 5 | Like 4 plus a delay based on p1214 and re-arming on rising edge of ON |
Sequenced process line |
| 6 | Like 4 but allows remaining faults to remain in the buffer | Diagnostic mode |
Wiring Requirement for Method 1
The 24 V supply to DI 0 must be sourced from a stable point that is energized whenever the drive should be running. The source may be the 24 V output on the CU230E-2 (terminal 9) or an external 24 VDC rail that is energized with the line. The DI 0 common must be configured to match the source — set p0728 to 0 for sink (PNP) with the internal 24 V, or to 1 for source (NPN) with an external rail. Holding DI 0 high continuously is acceptable; the firmware's p1210 = 2 (or 4/5) logic reissues a synthetic run command internally at the end of the restart window.
Method 2: Free Function Block (FFB) Timer
The CU230E-2 firmware includes a bank of Free Function Blocks (FFBs) — digital timers, AND/OR gates, comparators, and latches — that can be used to synthesize a delayed run command. The standard approach is a delay-on-make timer that holds the output low during the CU boot phase and then drives it high after a configurable delay, providing the required 0→1 edge on p840.
FFB Parameters Used
| Parameter | Function | Recommended Value |
|---|---|---|
p20158 |
BI: Timer block input (P20158.0) | r722.0 (DI 0 state) — or a constant 1 to ignore the DI |
p20159 |
Timer delay (ms) | 5000 (5 seconds; longer for slow-booting PMs) |
p20161 |
Timer mode | 5 (delay-on-make, non-retriggerable) |
p0840 |
BI: ON/OFF1 | r20160 (FFB timer output) |
Step-by-Step via BOP-2
- Press ESC to enter the parameter menu, navigate to
P20158, press OK. - Set index
.0to722(this is the BICO source for the status of DI 0 — confirm with the List Manual for your firmware). - Navigate to
P20159, set to5000(5 seconds in ms). - Navigate to
P20161, set to5(delay-on-make mode; refer to the FFB documentation if the mode number differs for your firmware build). - Navigate to
P0840, set index.0to20160(route the FFB output to the ON/OFF1 command). - Set
p840= 20160 to clear the original direct DI 0 wiring, leaving only the FFB in command. - Save to the active parameter set:
p0971 = 1or use the SAVE soft key on the BOP-2.
FFB Signal Flow (SVG)
Why the FFB Method Works
The CU230E-2 finishes its boot in roughly 20-60 seconds (depending on the parameter set size and any plugged-in option boards). The FFB timer stays at 0 for the configured delay and then produces the missing 0→1 edge on the ON/OFF1 command source. The drive sees a valid rising edge, exits the OFF1 state, ramps to the analog setpoint, and runs.
p20160 and confirm its index .0 transitions from 0 to 1 once with a STARTER trace or via the BOP-2 diagnostics menu. If the trace shows the timer output already at 1 during boot, the FFB is not the source of the start — likely p20158 is wired to a constant 1 by mistake, which still works but defeats the protective function.Method 3: Power Contactor Interlock
When the drive should not energize the motor on a brief control-power blip, but should resume automatically only after a full re-close, an upstream power contactor is the most deterministic approach. The contactor's own auxiliary NO contact (one of its normally-open blocks wired back to a free DI on the CU) provides the rising edge required for the next run command.
Wiring Diagram (Conceptual)
Sequence of Operation
- Control logic energizes coil of contactor K1. Line is applied to the SINAMICS G120 power module.
- K1's auxiliary NO closes simultaneously with the main contacts. DI 0 on the CU sees a 0→1 transition.
- CU230E-2 boots. The rising edge on DI 0 is latched in the parameter
r722.0; once the drive reaches the ready state, it issues the ON command. - On a mains power interruption, K1 drops out, line is removed, DI 0 falls back to 0. When the line is re-applied and the control logic re-energizes K1, the cycle repeats — fresh 0→1 edge, fresh run command.
Parameter Reference (Quick Copy)
; === Method 1: p1210 auto-restart ===
p0840 = 722.0 ; ON/OFF1 from DI 0 (rising edge)
p1000 = 2 ; Setpoint from analog input
p1210 = 4 ; Auto-restart on mains failure
p1211 = 3.0 ; Wait time before first restart (s)
p1212 = 10.0 ; Wait time between restart attempts (s)
p1213 = 3 ; Max restart attempts
; === Method 2: FFB timer ===
p20158 = 722.0 ; Timer input from DI 0 (or use 1 to ignore DI)
p20159 = 5000 ; Delay in milliseconds
p20161 = 5 ; Delay-on-make mode
p0840 = 20160.0 ; Route FFB output to ON/OFF1
; === Method 3: contactor interlock ===
; No parameter change vs. Method 1. The rising edge comes from K1's NO aux contact.
Enter these via STARTER, Startdrive, or the BOP-2. Save to non-volatile with p0971 = 1 and then cycle the control power to verify the values were stored.
Safety Considerations
| Topic | Requirement |
|---|---|
| STO (Safe Torque Off) | If the machine uses STO on terminals X12.1 / X12.2, the STO inputs must be energized before any of these methods will start the motor. Auto-restart with active STO is impossible — the firmware will not run while STO is low. |
| Overload behavior | Set p640 (current limit) and p2177 (motor blocked) trips to match the unattended-start profile. A motor stalled against load on restart can be a hazard. |
| Fault memory |
p1210 = 4 acknowledges only the faults defined in p1206. Verify which faults will be auto-acknowledged before relying on unattended operation. |
| Emergency stop | Use a separate DI (typically DI 1 or DI 2) wired to p2102 (acknowledge) and/or p0848 (OFF2) so the E-stop circuit is independent of the run command DI. |
| Mains monitoring | If the application requires the drive to distinguish a brief voltage dip from a true power failure, configure p0281 (line supply overvoltage) and p0283 (line supply undervoltage) thresholds. |
| Documentation | Per EN 60204-1, the unexpected start shall be marked on the equipment with a warning label (ISO 7010-W026). Document the auto-restart logic in the machine's safety file. |
Verification Procedure
- With the drive running, capture
r52.0(status word 1 bit 0 = "Drive ready") andr53.0(bit 0 = "Run") in the STARTER trace. - Open the upstream disconnect or de-energize the line (do this in coordination with a safe state of the driven equipment).
- Wait at least 30 seconds. The CU230E-2 will power down, the bus caps on the power module will discharge, and the line monitoring will drop out.
- Re-apply the line. With the chosen method, the drive should ramp to the analog setpoint within the time window defined by
p1211(Method 1), the FFB delay (Method 2), or the contactor close time (Method 3). - Verify motor rotation direction, current, and frequency match the expected operation. Confirm
r0021(smoothed actual speed) tracks the setpoint. - If the drive does not start, capture the active fault buffer
r0945[]and warning bufferr2122[]before cycling power again.
Troubleshooting Matrix
| Symptom | Likely Cause | Diagnostic | Remedy |
|---|---|---|---|
| Drive does not start on power-up; OFF1 light on | No rising edge on p840 because DI is held high the entire time |
Check r722.0 in trace; confirm transition 0→1 occurs after r899.0 (operating state 4 = ready) |
Use Method 1 (p1210 = 4) or Method 2 (FFB) |
| Drive starts then faults F30027 (power module overload) on restart | Motor starts against a high-inertia or loaded condition | Read r0034 (motor utilization) on the trace |
Lengthen ramp-up (p1120), reduce the setpoint at restart, or use flying restart (p1200 = 1) |
| FFB timer does not trigger |
p20158 wired to a value other than r722.0 or wrong index |
BOP-2 status view: r20160.0 should toggle |
Re-check BICO assignment; some firmware builds require index .0 explicitly |
| Drive starts but the analog setpoint is 0 | Setpoint source reverts because of p1000 macro |
Check r2250 (active setpoint after ramp-function generator) |
Confirm p1000 is still 2; check that the analog input scaling (p756, p757, p758, p759) is intact |
| Fault F30021 (STO active) prevents run | STO inputs not energized | Check r1860 and the wiring to X12 |
Apply 24 V to X12.1 and X12.2, or bypass the safety circuit per machine safety design |
| Drive starts only after pressing RUN key | Automatic restart is not actually enabled | Read p1210; read the active command source via r854.0
|
Set p1210 = 4 and re-save |
| Drive faults on every restart with F07801 (motor overcurrent) | Motor data has not been identified | Check p1910 / p1960 history |
Run the motor data identification in no-load condition |
| Drive starts then immediately OFF2 (coast down) | OFF2 path active — check p0848 and p0852
|
Trace r52.1 (OFF2) and r899 state |
Ensure the DI assigned to OFF2 is not held low by the wiring |
Related Parameters Worth Knowing
| Parameter | Function |
|---|---|
p1200 |
Flying restart mode — recommended if the motor may be still coasting on a quick mains return |
p1206 |
Faults that should be auto-acknowledged by p1210
|
p1211 |
Initial wait time after mains OK before first restart |
p1212 |
Wait time between restart attempts |
p1214 |
Restart time used in p1210 = 5 mode |
p1207 |
BiCo source for the rising edge of OFF1→ON that p1210=2 looks for |
p840 |
BI: ON/OFF1 (command source) — may be r722.0, r20160.0, or a fieldbus bit |
p848 |
BI: OFF2 source |
p852 |
BI: OFF3 source |
p898 |
BiCo source for the OFF1 (inversion of p840) |
p756 |
Type of analog input 0 (0 = 0-10 V, 2 = 0-20 mA, 3 = 4-20 mA) |
p0971 |
Save parameters to non-volatile memory |
Field Commissioning Checklist
- [ ] Confirm the application permits unattended restart (safety file updated, ISO 7010-W026 label applied).
- [ ] Run motor data identification and save.
- [ ] Verify analog input wiring and scaling on
p756–p759. - [ ] Wire the E-stop to a separate DI (DI 1 or DI 2) routed to
p2102and/orp848. - [ ] Apply the chosen method's parameters and save with
p0971 = 1. - [ ] Power cycle the drive, observe the trace, and verify the drive runs within the expected time window.
- [ ] Test an E-stop trip and confirm the drive stops in OFF1/OFF2 as required.
- [ ] Document the wiring and parameter set in the cabinet drawing set and the controller's tag database.
Why does the G120 with CU230E-2 not start on power-up even when DI 0 is held at 24 V?
The SINAMICS firmware requires a 0→1 rising edge on the ON/OFF1 command source (p840) only after the drive reaches the ready state (r52.0 = 1). A continuously held DI produces no edge, so the drive stays in OFF1. Enable automatic restart with p1210 = 4 or synthesize an edge with a Free Function Block timer (p20158–p20161, route the output to p0840).
What is the difference between p1210 = 2 and p1210 = 4 on a G120?
p1210 = 2 acknowledges all faults and restarts whenever the ON command is active, including after a non-mains-related trip. p1210 = 4 restarts only after a mains-side power interruption and is generally preferred for unattended applications because it does not auto-clear non-mains faults such as overcurrent or motor overload.
How long should the FFB timer delay (p20159) be set to?
Set p20159 to at least the worst-case CU230E-2 boot time plus a 2-3 second safety margin. A value of 5000 ms (5 s) is a reasonable starting point for a small parameter set; large parameter sets, plugged-in I/O modules, or projects using SINAMICS Startdrive should increase this to 10000-15000 ms. Verify the actual boot time by watching r899 transition from 0 to 4 in STARTER.
Can the auto-restart work with a fieldbus command source (PROFINET or PROFIBUS) instead of DI 0?
Yes. The procedure is identical except p840 is wired to a fieldbus control word bit such as r2090.0 (bit 0 of the PZD receive word, e.g. STW1.0). The PLC keeps STW1.0 = 1 after the drive reaches ready, and the same edge requirement applies — use p1210 = 4 or a PLC application-side one-shot to produce the rising edge on the fieldbus interface.
Is auto-restart permitted on a STO-equipped safety circuit?
STO is a higher-priority function than ON/OFF1. If STO is active (X12 inputs low), the drive cannot produce torque regardless of auto-restart settings. The safety circuit must be designed to de-energize STO only when the safe state is verified, in line with ISO 13849-1 and IEC 61800-5-2. Auto-restart is permitted as long as the overall safety function (typically SLS, SS1, or STO) meets its required Performance Level.