Problem Overview
On a SINUMERIK 828D controller running SINAMICS S120 firmware 4.8, an operator-assisted grinding process requires manually rotating the rotor of a 1FT7 synchronous servo motor. The machine builder must therefore provide a way to force the holding brake open by software without driving the axis through its normal motion program.
Several conventional approaches — setting p1215 = 2, activating the extended brake control (p1278 = 1), and commanding the NC/PLC interface signal DB380x.DBX4000.5 — all report the correct status bits in the drive (r0899.12 = 1, r0899.13 = 0), but the 24 V brake output on the Single Motor Module (SMM 6SL3120-1TE21-8AD0) never energises. The brake still opens normally when the control enable and pulse enable are active, or when 24 V is applied externally to the BR+ / BR- terminals.
The root cause is not a wiring fault or a defective brake coil — it is the SINAMICS brake-control state machine: software brake release is only authorised when the drive is in the correct operating state. This article documents the correct parameter combination and the conditions under which the drive will physically open the brake contacts.
Affected Hardware and Firmware
| Component | Designation / Order Number | Notes |
|---|---|---|
| NCU | SINUMERIK 828D | Operates as the NCK/PLC master |
| Drive firmware | SINAMICS S120 FW 4.8 | Brake parameter set matches List Manual 04/2014 and later |
| Motor | 1FT7 (synchronous servo, integrated holding brake) | Brake lead brought out at connector BR+ / BR- |
| Motor Module | SMM 6SL3120-1TE21-8AD0 | Single Motor Module, 18 A, internal brake driver |
| Brake wiring | X2 BR+ / BR- on the Motor Module | Integrated electronic brake control (EBC) |
| Commissioning tool | STARTER (or Startdrive) for SINAMICS | Used to view r0899 and edit p1215
|
Brake Control Architecture in SINAMICS S120
The holding brake on a 1FT7 motor is driven from the Motor Module, not from the NC. The drive runs an internal state machine that uses the operating state, the safety state, the OFF responses, and the configuration parameters to decide whether to energise BR+ / BR-.
Two brake-control modes are available in firmware 4.8:
-
Basic brake control — selected when the drive option Extended brake control is inactive (
r0108.14 = 0). The brake follows the sequence control (SCC) and is driven by the signal open holding brake derived fromr0899.12/r0899.13. -
Extended brake control — activated by
p1278 = 1(with option module). It provides separate signals for opening and closing, plus diagnostic words such asr0899.0…r0899.13.
In both modes the physical output on the Motor Module is not switched solely because r0899.12 = 1. The state machine must additionally see that the drive is in Operation enabled (r0899.0 = 1) or that an explicit "open brake by sequence control" path has been configured.
Parameters and Signals Reference
| Parameter / Signal | Meaning | Expected value for software release |
|---|---|---|
p1215 |
Motor holding brake configuration (sequence control) |
1 (sequence control) or 3 (sequence control + BICO), not 2
|
p1216 |
Opening time of holding brake [ms] | From 1FT7 data sheet, typically 60 – 180 ms |
p1217 |
Closing time of holding brake [ms] | From 1FT7 data sheet |
p0855 |
BICO source for "open holding brake" (only with p1215 = 3) |
Connect to a free digital input, MCP button, or PLC output |
p1278 |
Activate extended brake control |
0 for basic, 1 for extended |
r0108.14 |
Drive option "Extended brake control" present |
0 (basic) or 1 (extended) |
r0898.7 |
Status word sequence control: "close holding brake" | Derived from p0855; should follow the request |
r0899.12 |
Status word: "open holding brake" command active | 1 |
r0899.13 |
Status word: "close holding brake" command active | 0 |
r0899.0 |
Drive state "Operation enabled" | Must be 1 for the brake contacts to physically close (release the rotor) |
DB380x.DBX4000.5 |
NC→PLC interface: "Open motor holding brake" (per axis) |
1 from the PLC user program |
DB390x.DBX4000.5 |
NC→PLC interface: feedback that the signal is accepted | Mirrors the command, confirms wiring of the request |
The parameter list above is taken from the Siemens Industry Online Support parameter documentation for the SINAMICS S120/S150 List Manual. The signals DB380x/DB390x are documented in the SINUMERIK 828D List of Interface Signals (NC variables interface).
Root Cause Analysis
Three different attempts were made on the bench:
-
Setting
p1215 = 2— this is the value "motor holding brake always released" in some firmware versions, but in S120 FW 4.8 the value2means "motor holding brake, connection via BICO" only when used together withp0855; the 24 V output is still gated by the state machine. Result: drive-status bits toggle, but the BR+ / BR- terminals stay de-energised. -
Extended brake control (
p1278 = 1) with the option module not licensed — the drive reports the correct sequence-control status words (r0899.12 = 1,r0899.13 = 0), but the option module is not active, so the output stage is not enabled. -
NC/PLC command
DB380x.DBX4000.5 = 1via the SINUMERIK PLC — the NC correctly echoes the command (DB390x.DBX4000.5 = 1) and the drive-side status bits change, but the Motor Module still does not drive the brake output because the drive is in Pulse inhibit / Ready to switch on rather than Operation enabled.
The common denominator is the missing operating state: the SINAMICS S120 will not energise the internal brake output unless the drive is at least in Ready to operate with the controller enable and pulse enable both set. In other words, the sequence control must have produced a request to open the brake (r0899.12 = 1) AND the drive must be in a state where it is allowed to follow that request.
Solution Procedure
The combination that actually opens the brake contacts from software on this configuration is:
- Set
p1215 = 1(motor holding brake like sequence control, connection via MOTOR connector — internal output on the Motor Module). - Set the controller enable
STW1.0 = 1for the drive object (or wirep0840 = 1via the PLC). - Bring the drive to Ready to operate by clearing all faults (
r2135 = 0) and confirming that the pulse enable is granted (r0899.0 = 1). - From the PLC user program, set
DB380x.DBX4000.5 = 1for the axis. The drive setsr0899.12 = 1and afterp1216milliseconds the BR+ / BR- output energises the brake coil. - To release the brake without rotation, keep the drive in a torque-disabled state (e.g., jog speed set to zero) so the rotor can be turned manually by the operator.
p1215 = 2 does not work on this firmware: the value 2 in the S120/S150 list manual corresponds to "motor holding brake, connection via BICO" only when the option "Extended brake control" (r0108.14 = 1) is present. Without that option, p1215 = 2 is silently rejected and the brake output is not driven. Use p1215 = 1 for the integrated BR+ / BR- output on a Single Motor Module.
Alternative: BICO Release Through a Digital Input
If you need to release the brake from a hardware key (for example, a button on the MCP) without involving the PLC, use the BICO path:
p1215 = 3 ; sequence control + BICO
p0855 = r0722.x ; source = status of digital input x on the Control Unit
p0840 = r0722.y ; optional: drive enable tied to the same input
As long as the digital input is high, r0899.12 = 1 and the Motor Module energises BR+ / BR- after the configured opening time p1216. The brake closes immediately when the input goes low, following the closing time p1217.
This is the same wiring path that the Siemens application example for "service / setup mode" uses when the operator must be allowed to move the motor by hand before the axis has been homed.
NC/PLC Interface Method (SINUMERIK 828D)
The signal DB380x.DBX4000.5 is the "Open motor holding brake" request from the PLC to the NC. The NC forwards it to the drive as a request; the drive then executes the brake sequence through r0899.12.
Minimal PLC example (structured text, axis index 1):
// Manual brake release request, axis 1
// DB3801 is the axis-specific request DB; bit 4000.5 is "open holding brake"
U E 100.0; // MCP key "release brake"
= DB3801.DBX4000.5;
// Optional interlock to prevent the operator from moving the rotor
// while the spindle drive is at high speed
U DB3901.DBX4000.5; // acknowledge from NC
S M 200.1; // "brake released" flag for HMI
On the HMI the operator button can be wired through softkey PLC flags; the SINUMERIK Operate screen does not normally expose a "release brake" command, so this is almost always a custom screen or a user-defined key on the MCP.
Extended Brake Control with p1278 = 1
When the drive option "Extended brake control" is licensed (r0108.14 = 1), p1278 = 1 unlocks the full set of status words in r0899 and adds the diagnostic signals listed in the List Manual. With extended brake control, the brake opening request can come from:
- The sequence control (default —
p1215 = 1) - A BICO source on
p0855(withp1215 = 3) - The drive-internal signal
r0899.12via the NC/PLC interface
The physical output on the Motor Module is identical in all three cases. The extended mode only changes which status bits are visible in r0899 and how the brake is integrated with Safety Integrated (SBC / SS1).
Safety Considerations
The discussion thread that produced this case highlights a critical point: any active Safety Integrated function will overrule the manual brake release. If SBC (Safe Brake Control) or SS1 (Safe Stop 1) is configured for the axis, neither p1215 nor p1278 nor the NC/PLC command will energise the brake output while the safety function requests "brake closed".
- Verify that no Safety Integrated function is active on the affected axis. In STARTER, the screen form Functions > Safety Integrated must show the safety option as deactivated for the axis.
- If the axis is part of a Safety Integrated group, all axes in that group must be in a safe state before the manual brake release is honoured.
- For a horizontal grinding spindle (as in this case), the rotor position is not gravity-loaded. The mechanical risk of an unintentional free rotation is low, but the application is still subject to the general safety policy of the machine.
For a deeper treatment of brake timing in vertical and horizontal applications, the Rockwell Automation motion application note "Vertical Load and Holding Brake Management" is a useful cross-vendor reference. The holding-brake opening time given in the 1FT7 data sheet (typically 60 – 180 ms) should be entered in p1216 so the drive does not command torque before the brake has physically released.
Verification
- Connect a voltmeter between BR+ and BR- on the Motor Module X2 terminal block.
- With the drive in Ready to operate and the controller enable asserted, set
DB380x.DBX4000.5 = 1from the PLC. - Read
r0899.12 = 1,r0899.13 = 0in STARTER / Startdrive. - After the time
p1216, the voltmeter should read 24 V DC, polarity BR+ = positive. - Confirm the rotor can be turned by hand with the controller in this state.
- Reset
DB380x.DBX4000.5 = 0and verify the brake re-engages afterp1217.
If step 4 shows 0 V even though all status bits are correct, check the safety state of the drive with r9772 (SI diagnostics) and the drive state with r0899.0. The drive must be in Operation enabled for the BR+ / BR- output to be active.
Parameter Quick Reference
| Parameter | Setting | Purpose |
|---|---|---|
p1215 |
1 | Holding brake via sequence control (integrated output on the Motor Module) |
p1216 |
60 – 180 ms (per 1FT7 data sheet) | Brake opening time |
p1217 |
Per 1FT7 data sheet | Brake closing time |
p0855 |
Optional BICO source for "open brake" when p1215 = 3
|
Allows a digital input / MCP key to open the brake without PLC |
p1278 |
1 (only with option) | Activates extended brake control and full r0899 diagnostics |
DB380x.DBX4000.5 |
1 from PLC | "Open motor holding brake" request from SINUMERIK PLC |
DB390x.DBX4000.5 |
Read-only feedback | Confirms the request reached the NC and the drive |
Troubleshooting Matrix
| Symptom | Likely cause | Action |
|---|---|---|
r0899.12 = 1 but no 24 V on BR+ / BR- |
Drive not in Operation enabled (missing pulse enable) | Set controller enable, clear faults, verify r0899.0 = 1
|
r0899.12 = 0 despite PLC command |
p1215 set to 0 or 2, or p0855 not wired |
Change p1215 to 1 (integrated) or 3 (BICO) and verify p0855
|
| Brake holds, no release after PLC command | Active Safety Integrated function | Check r9772, deactivate SBC / SS1 for the axis |
| Brake chatters when released |
p1216 or p1217 too short |
Set brake times from the 1FT7 data sheet |
DB390x.DBX4000.5 = 0 |
NC did not accept the request, axis in follow-up mode / not referenced | Check axis state with DB390x.DBX1.0 / 1.1 / 1.2
|
Why does the brake not open even though r0899.12 = 1 on SINAMICS S120 FW 4.8?
Because the SINAMICS state machine only energises the BR+ / BR- output when the drive is in Operation enabled. Set the controller enable, clear all faults so that the pulse enable is granted, and confirm r0899.0 = 1 before the brake contacts will close (release the rotor).
Which p1215 value is correct for software brake release on a 1FT7 motor?
Use p1215 = 1 when the brake is wired to the integrated BR+ / BR- output on the Motor Module, or p1215 = 3 when the release command comes from a BICO source such as a digital input on the Control Unit. Avoid p1215 = 2 unless the drive option Extended brake control is licensed.
How do I release the 1FT7 brake from a SINUMERIK 828D PLC?
Set the per-axis request DB380x.DBX4000.5 = 1 from the PLC, with p1215 = 1 and the drive in Operation enabled. The NC echoes the command in DB390x.DBX4000.5 and the drive energises BR+ / BR- after the configured opening time p1216.
Can Safety Integrated block the manual brake release?
Yes. If SBC (Safe Brake Control) or SS1 (Safe Stop 1) is active on the axis, the SINAMICS safety state machine keeps the brake closed regardless of p1215, p1278, or the PLC request. Deactivate the safety function for the affected axis (and its safety group) before the manual release will be honoured.
What brake opening and closing times should I enter in p1216 and p1217?
Take the values from the 1FT7 data sheet for the specific motor frame (typically 60 – 180 ms opening, similar or longer closing). The values are used to delay the torque enable and the pulse inhibit so the drive does not command torque before the brake has physically released.