The basic principle.

A lift controller receives calls and inputs, decides what action is appropriate, and coordinates outputs to the drive, doors and other equipment. Older systems may use extensive relay logic; modern systems often use programmable electronics.

The controller is not identical to the motor drive. The drive handles motor power conversion and control, while the controller coordinates the larger sequence. Some products combine functions within one assembly.

A registered call waits.

A worked-through example

The request can be stored while the doors are closing or another journey completes. A request becoming visible is not proof that every permission for movement has already been met.

Follow the relationship.

  1. InputsCalls, position and equipment states.
  2. LogicChooses the next permitted action.
  3. OutputsCommands doors, drive and associated systems.
Conceptual relationships; arrangements vary by installation.

Connect it to the lift.

Communication networks can carry information between devices, but the meaning and integrity of the information still matter. A fault report should distinguish the command, the reported state and the physical result.

A closer look

Dispatching a group of lifts adds another layer: a group controller can allocate calls while each lift still manages its own movement and protective conditions.

Check your understanding

Does pressing a floor button directly connect electrical power to the lift motor?

Reveal the explanation

Normally no. It requests an action that the control system evaluates and sequences.

Further reading.

Otis: the basic workings of a lift