Smart Elevator, IoT layer
Elevator IoT hardware designed for your controllers.
A generic gateway reads voltage. It cannot tell you the car is at floor seven, that the door operator is drawing more current than it did in spring, or that the drive logged a fault two minutes before the callout. That takes an interface board built for the panel it lives in.
The problem
The panel is not a standard interface.
Two elevators in the same building can be five years apart in controller design. One publishes a clean serial frame with a documented register map. The next holds nothing but relay coils and a floor selector, and the only way to know the car is moving up is that a particular contactor is energised while another is not.
A universal IoT gateway handles neither case properly. It samples a few generic points, guesses at meaning, and produces a feed that looks like data and behaves like noise. Once that feed reaches a maintenance team, the credibility of the whole system goes with it.
The alternative is to survey the controller first and design the interface to what is really there. It is more engineering up front and far less argument later.
What the survey records
Controller make, model, and firmware revision per unit
Available signal points and whether they can be read safely
Panel voltages, free terminals, and physical space
Fault code table and how the controller reports it
Door operator type and its own control interface
Network options at the site, cellular coverage included
Whether the unit is in warranty and who holds it
Controller coverage
Four families, four different jobs.
How the hardware attaches to a lift depends entirely on what the controller is willing to say. These are the four cases that cover most elevators.
VVVF drives
Serial or fieldbus where the drive exposes one, plus discrete status lines
Modern variable frequency drives usually publish speed, current, and fault registers over a serial link. The interface reads the frame format the drive actually uses, which varies by manufacturer and by firmware revision within the same model line.
Relay logic panels
Isolated digital inputs across contactor and relay coils
Older panels hold no data bus at all. State has to be reconstructed from coil energisation, floor selector position, door operator contacts, and safety chain continuity. The board carries a wider input bank for this case.
Proprietary OEM boards
Vendor protocol decoded from a monitored bus or diagnostic port
Many OEM controllers expose a diagnostic connector intended for the manufacturer service tool. Where the electrical layer can be tapped safely and read only, the interface listens on it without participating in control traffic.
Mixed and older lifts
One hardware family, variant interface sections, per-controller firmware
Service companies rarely have one brand. The platform is designed so a single device family covers all your elevators, with the differences carried in the interface section and the firmware build rather than in five separate products.
| Controller family | What the interface reads |
|---|---|
| VVVF drives | Serial or fieldbus registers, plus discrete status lines |
| Relay logic panels | Isolated digital inputs across contactor and relay coils |
| Proprietary OEM boards | Vendor protocol read from a monitored diagnostic bus |
| Mixed and older lifts | One device family, variant sections, per-controller firmware |
Edge device architecture
What is actually on the board.
The device is deliberately unglamorous. Its job is to read correctly, survive the panel, and never require a site visit to recover. Six blocks carry that.
What the hardware captures
- Car floor position and direction of travel
- Door open, close, and full cycle time
- Motor feed and door operator current
- Controller fault codes with device timestamps
- Run starts, completions, and trip counts
- In-service and out-of-service state
Signal conditioning and isolation
Optocoupled digital inputs rated for the panel voltages actually present, with transient protection at the connector. Galvanic isolation keeps the elevator safety circuit and the measurement electronics electrically separate.
Analog and current sensing
Non-invasive current measurement on the motor feed and on the door operator, sampled fast enough to see the shape of a start rather than only an average. This is the input that later makes trend analysis possible.
Serial and bus interfaces
RS485, RS232, and CAN front ends configured per controller, with termination and biasing options set at build time so one board can be fitted to different panels without rework.
Edge compute
A microcontroller sized for continuous protocol decoding, event detection, and local storage, chosen for long-term availability rather than for the lowest unit price on the day of design.
Connectivity
Cellular for most retrofits, Ethernet where the building offers a stable drop, and Wi-Fi only where the site allows it. Antenna placement is planned for a metal panel inside a concrete shaft, which is a hostile radio environment.
Local storage and power handling
Non-volatile buffering so an outage does not create a gap in history, and a wide-range supply input with holdup so the device can report its own power loss before it goes down.
Send us the controller makes in your elevators. We will tell you what can be read from each one and how.
Book a technical assessment →Design constraints
Built for a machine room, not a desk.
A prototype that works on a bench proves very little. The device has to hold up in a steel panel next to contactors that slam a few hundred times a day, in a room that nobody air-conditions, for the length of a service contract.
Component derating, conformal coating where the site needs it, connector choice that survives an installer in a hurry, and thermal margin are decided at design time. Field failures are expensive in a business where a truck roll is the unit of cost.
What the enclosure faces
Panel temperatures that sit well above ambient for years without a break
Continuous vibration and mechanical shock from the machine room floor
Switching noise from contactors and drive output stages on every trip
Dust and oil mist in machine rooms and shaft-mounted enclosures
Enclosure space measured in a few free DIN slots, not a rack
Sites that will not be revisited for years, so field access has to be remote
Retrofit and new install
Two paths onto your elevators.
Retrofit into existing elevators
The panel is surveyed before anything is designed: available voltages, free space, terminal access, and which signals can be read without touching the safety chain. The device is then built to fit inside that reality, with a wiring loom and a labelled terminal map so an installation is a repeatable job rather than an investigation.
Factory fit on new units
For OEMs the interface can move inside the panel design itself, sharing the controller supply and using a defined wiring loom. Serial numbers are assigned and paired to the unit on the production line, so a lift arrives on site already known to the platform.
Hardware is only half of it. The decoding, the fault mapping, and the update path live in the firmware. That side is covered on elevator embedded firmware.
Certification and production
Approval planned at schematic stage.
Compliance failures found at the test lab are respins, and respins are months. The layout, the filtering, and the isolation strategy are decided with the target approvals already on the table.
EMC
Emissions and immunity planned into the layout from the start, with filtering at every cable entry. A drive panel is one of the noisier places a small board can live, so immunity work matters as much as emissions.
Electrical safety and isolation
Creepage and clearance set for the mains-referenced sections, isolation barriers documented, and the interface designed so a fault on the device cannot propagate into elevator control wiring.
Radio approvals
Pre-certified cellular and radio modules used where possible to keep the approval scope on the host product rather than on the radio itself.
Production test
A functional test fixture and protocol defined with the board, so each unit is powered, exercised across every input, and serialised before it leaves the line.
FAQ
Questions about the hardware.
Elevator IoT hardware is the interface device installed in the lift control panel. It connects to the controller signal points, converts and isolates those signals, runs firmware that decodes them into structured events, and sends the result to a monitoring platform over cellular or Ethernet.
Related
Where this fits.
Start with a controller survey.
Every hardware decision follows from what your panels expose. Bring the list and we will give you a straight read on feasibility before anything is designed.