The basic principle.

The controller manages the journey and permissions. The drive controls electrical power to the motor. The motor produces electromagnetic torque. The machine brake supplies its intended mechanical braking or holding function.

During a designed traction start, torque establishment and brake release are coordinated to avoid uncontrolled movement. During arrival, motor control and brake application are similarly coordinated.

A command is not the result.

A worked-through example

A controller can issue a release command while the brake mechanism fails to release fully. Feedback and physical behaviour help distinguish the request from the actual state.

Follow the relationship.

  1. Controller requestsDefines the desired action.
  2. Drive and motor respondProduce the required torque and motion.
  3. Brake coordinatesReleases or holds at the appropriate stage.
Conceptual relationships; arrangements vary by installation.

Connect it to the lift.

If one element behaves incorrectly, another may report the consequence. A drive fault therefore does not automatically prove the drive electronics are defective. Wiring, feedback, mechanics and commands form part of the evidence.

A closer look

Not every lift uses a modern VFD traction arrangement. Older controls and hydraulic installations distribute these functions differently.

Check your understanding

If the controller requests movement, is that proof the brake has released?

Reveal the explanation

No. Command, feedback and physical response are distinct.

Further reading.

Otis: the basic workings of a lift