Motion control / holding brake

Siemens 6SE70 Brake Control Path

Maps drive brake-control logic to relay output, brake coil supply, release/close delays and mechanical brake condition for hoist and vertical-axis applications.

Machine-control circuit path6 min read

Scope of this technical record

Brake command, coil supply, timing and mechanical brake path for MASTERDRIVES applications with motor-mounted or external holding brakes.

Safety boundary

Treat this page as a machine-safety route. Never test brake release on an unsecured vertical load.

6SE70 brake command path

1Torque build-up
2Timing
3Relay / output
4Coil
5Brake mechanism

The path separates drive command, coil supply and mechanical holding evidence.

6SE70 brake command path image

6SE70 brake command path torque buildup timing relay output coil brake mechanism
The image separates torque command, coil supply and mechanical brake evidence.

Path description

The brake-control path runs from drive torque/build-up logic and configured timing through a digital or relay output to the brake coil supply and the mechanical brake. A fault at any node can look like a drive-control fault from the panel.

The evidence route keeps electrical command and mechanical brake state separate. This prevents parameter edits from hiding a brake-wear or coil-supply problem.

Field record checklist

  • Torque/command sequence
  • Release and close delays
  • Output relay status
  • Coil voltage
  • Brake air gap/wear
  • Load-holding proof

Technical basis and reference documents

This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.

SIMOVERT MASTERDRIVES Vector Control Operating InstructionsSiemens Industry Support

OEM basis for 6SE70 / 6SE71 safety, control connections, motor temperature evaluation and option context.

SIMOVERT MASTERDRIVES brake and thermal protection evidence notesIndustrialDriveData editorial extraction

Internal technician note set used only to structure public diagnostic routes around KTY/PTC thermal protection and brake-control evidence.

Evidence intake

Turn this record into a qualified service request

A repair decision is much more reliable when the request includes the exact identity of the drive, the first fault evidence and the machine condition when the symptom appeared.

  • Complete drive type code / MLFB or nameplate model
  • Fault code, fault value and first event before reset
  • When the event appears: power-up, enable, ramp, run, decel or stop
  • Motor/cable connected or isolated during the symptom
  • Visible board, option-card, module and connector identifiers
  • Previous repair history, replacement parts and repeat-failure pattern
Prepare request →