Log inBook a walkthrough
Book a walkthrough
English

Event codes, learn runs and levelling, answered from your controller manuals.

Your engineers’ questions are already answered in your technical manuals, event lists and quick-set-up guides. Lingo turns them into guides your technical team approves. Each guide asks which controller is fitted, then sends that controller’s checks to the lift engineer, at any hour.

Book a walkthroughSee how it works

Lingo

Online

Installer: Car is stopping short at floor 3. Do I redo the learn run?
Lingo: Is the lift already commissioned and in service? 1. Yes, it is in service 2. No, still commissioning
Installer: 1
Lingo: 1. Do not start a full learn run. On this controller it clears every floor level. 2. Adjust the level at the floor concerned, as the controller manual sets out. 3. If the levels keep drifting, ask for a person.

Floor levels out after a service

Published
Start

QUESTION

Is the lift already commissioned and in service?

ANSWERS

  1. 1.Yes, it is in service
  2. 2.No, still commissioning
Yes, it is in service

FIX

1. Do not start a full learn run. On this controller it clears every floor level. 2. Adjust the level at the floor concerned, as the controller manual sets out. 3. If the levels keep drifting, ask for a person.

Manufacturers already ask lift engineers to look before they call.

One controller manual ends its fault-finding with a list: “If further help is required whilst fault finding please make a note of the following before contacting” the maker. The answers are published. Finding the right one, in an event list of hundreds, is the slow part.

Before you call, one manual asks for

  1. 1Which LEDs are lit
  2. 2The state of the contactors and relays
  3. 3A full report of the lift fault
  4. 4A full report from the fault logger
A guide asks for the same details in the conversation, so they are in front of your team when the engineer asks for a person.

Events listed in three controllers’ documents

Each event has its own meaning, and often its own checks.

  • Controller AEvent history guide, 20 pages314
  • Controller BTechnical manual, recognised events135
  • Controller CEvent code descriptions, 80 pages99

Six documents in. One guide out, that asks first whether the lift is in service.

You send the manuals and quick guides for one controller. Lingo drafts guides from them, your technical team checks each draft against the source and publishes it, and the engineer gets the checks for the controller in front of them.

Your documents for one controller

  • Technical manualContents to p.53
  • Event history guide314 events
  • Learn-run set-up guide6 pages
  • Brake test guide4 pages
  • Unintended movement detectionSet-up and tests
  • Drive maker’s manualDrive faults

Floor levels out after a service

Published
Start

QUESTION

Is the lift already commissioned and in service?

ANSWERS

  1. 1.Yes, in service
  2. 2.Still commissioning
Yes, in service

FIX

1. Do not start a full learn run: on this controller it clears every floor level. 2. Adjust the level at the floor concerned, as the manual sets out. 3. Levels still drifting? Ask for a person.

  • A warning sits in front of its step

    One learn-run guide says in capitals that, once the lift is commissioned, the feature wipes every floor level. A guide asks first, and only sends the step where it belongs.

  • The event list points elsewhere

    Some entries in one event guide send the engineer to the drive maker’s manual; others say to contact the maker. A guide follows the pointer, or hands over to your team.

  • Controllers, drives and generations

    Makers publish documents for current and earlier controllers, and for the drives and door operators fitted with them. A guide asks which is fitted before it sends a check.

What lift engineers ask, and what a guide sends back.

These are the subjects controller makers’ documents cover. For each, a guide puts your documented checks in order and sends them one message at a time.

A lift engineer reads his phone in a machine room, beside an open lift controller cabinet and the traction machine.

  • Events and fault indications

    The controller is showing an event, or a fault LED is lit

    A guide asks which controller and drive are fitted, then sends the checks your event list gives for that event, in order. Where your guide says to contact you, the engineer can ask for a person in the same conversation.

  • Learn run and levelling

    Floor levels, the learn run and the limits

    The set-up steps from your quick guides, one at a time, with your warnings in front of the steps they belong to. A guide asks whether the lift is already in service before it sends anything that would clear the levels.

  • Doors and door operators

    Doors that will not open, close or reopen as set

    Door operator wiring and parameter documents become guides in the same way, for the operator fitted with your controller.

  • Tests and set-up

    Brake tests, unintended movement detection and software updates

    The documented steps for running a test, loading parameters or updating software, in your order. What to do with a failed test is your team’s call, and the guide hands it to them.

Your technical team checks every guide and sees every conversation.

  • Every guide is published by your team

    They can edit a guide, write one by hand or unpublish it. When a question comes up that no guide covers, they can add the answer.

  • You choose who can use it

    One maker asks technical callers for their contract number. Access to Lingo can be limited to the engineers’ phone numbers you approve, company by company.

  • Your team in your hours

    Guides answer at any hour. An engineer can ask for a person at any point: in the hours you set, your team replies in the same conversation with the earlier messages, and the details your manual asks for, in front of them.

  • Every conversation is kept

    With the engineer’s name and number, the controller and the guide used, so your team can see which events and set-up steps come up most.

A technical support engineer on a headset reads a table of event codes in a ring-bound controller manual at her desk.

Your team, with the details already in front of them

The controller, the event and the checks already made arrive with the request.

Your team decides what gets a guide. The safety chain stays with your people.

A guide sends the steps your team published, in your order. The questions where a wrong answer puts someone at risk can go straight to a person.

Modifications intended to keep a lift operating but which may result in unsafe operation must not be carried out under any circumstances.

HSE, Safety Bulletin OPSD1-2019 on platform lifts, March 2019

A guide can take

  • What an event or a fault LED means on this controller, and the checks your manual lists
  • Learn run, levelling and limit set-up, with your warnings in place
  • Door operator set-up for the operator fitted
  • The documented steps for running a brake or movement detection test
  • What your manual asks the engineer to note before contacting you

Your technical team keeps

  • The safety chain

    Anything that bypasses, bridges or resets part of the safety chain, beyond the functions your controller provides for it.

  • Movement detection and failed tests

    Resetting an unintended movement fault, and any brake, safety gear or governor test that fails. One maker’s guide says a movement fault “will need resetting by a competent person”.

  • Releasing trapped passengers

    When the equipment does not behave as the manual describes. LEIA says release “should only be undertaken by a trained lift engineer or the Rescue Services”.

  • Firefighting and fire recall

    How the lift behaves under firefighters control or a fire recall signal.

  • Changes that need a new examination

    Under LOLER, after “exceptional circumstances which are liable to jeopardise the safety of the lifting equipment”.

  • Passwords, corrupt parameters and boards

    Access codes, parameters that will not reload, and boards that need to come back to you.

  • 6 months

    LOLER. A lift that carries people needs a thorough examination at least every 6 months.

    Source

  • 13,760

    Fire and rescue. Lift releases attended in England in the year to March 2026, the largest category of non-fire incident.

    Source

  • EN 81-20

    New lifts. The safety rules for permanently installed new passenger and goods passenger lifts.

    Source

  • EN 81-50

    Components. Design rules, calculations, examinations and tests of lift components.

    Source

LEIA’s guidance on releasing trapped passengers says release “should only be undertaken by a trained lift engineer or the Rescue Services”. Read the guidance.

What it takes to start.

A lift engineer in a hard hat stands on the roof of a lift car in the shaft, reading his phone beside the inspection control box.
  1. 1

    Send the documents for one product

    One controller’s technical manual, event list, learn-run and test guides, and the drive and door operator manuals that go with it.

  2. 2

    See your own draft guides

    Lingo drafts a guide for each task. We go through the drafts with you in a 15-minute walkthrough.

  3. 3

    Your team checks and publishes

    Checking each draft against the manual is the main work. Your team corrects it and publishes it, and can edit or unpublish it at any time.

  4. 4

    Start with people you choose

    Approve the engineers at one or two maintenance companies first. Each conversation is kept with the controller and the guide used.

Questions lift controller manufacturers ask

We already have remote monitoring. What does Lingo add?

Remote monitoring tells your team what a connected lift is reporting. Lingo takes the engineer standing at the controller through the documented checks for that event, in order, on WhatsApp, Teams, web or email, at any hour. It works from what the engineer tells it, on any phone, so it also serves lifts that are not connected, and it keeps a record of every conversation.

Can it cover controllers we no longer make?

Yes, where the documents exist. Each controller has its own guides, and a guide asks which controller, drive or generation is fitted before it sends a check.

We only support engineers with a contract. Can we limit who uses it?

Yes. Access can be limited to the phone numbers you approve, added one at a time or imported as a list, so you can start with one maintenance company’s engineers.

Will a guide tell an engineer to bridge the safety chain?

Only what your published manual sets out, in the order it sets it out. Your team decides which procedures get a guide. Anything that bypasses or resets part of the safety chain can go straight to your people.

What happens when an engineer asks something no guide covers?

The engineer can ask for a person at any point. Your team is notified by email and replies in the same conversation, in the hours you set. They can then add the answer to a guide.

How is it priced?

By the number of products you support, from £500 a month for five products. There is no setup fee, and no limit on engineers or conversations.

Further reading

Sources, read 22 October 2026: technical manuals, event lists, quick set-up guides and support pages from three UK lift controller makers (issues dated 2014 to 2026); HSE, Safety Bulletin OPSD1-2019, platform lifts; The Lifting Operations and Lifting Equipment Regulations 1998, regulation 9; LEIA, Safety Information Sheet PA 70, release of trapped passengers; Home Office, Detailed analysis of non-fire incidents, England, year ending March 2026, September 2026; scope statements for EN 81-20:2020 and EN 81-50:2020.

Send us one controller’s documents.

We’ll convert them and show you your own guide in a 15-minute walkthrough.

Book a walkthroughWork out what routine queries cost your team