Built to order

IoT Escalator Health Monitor with Vibration and Performance Dashboard

This project builds a wireless IoT sensor node for escalator condition monitoring: a MEMS accelerometer tracks vibration (RMS, crest factor, dominant frequency) while motor current, step speed and gearbox temperature are monitored alongside. An ESP32 streams the data to a web dashboard with live gauges, switchable vibration waveform and frequency-spectrum views, a 7-day RMS trend against an alert threshold, an event/fault log, and plain-language maintenance suggestions from trend rules. The node only observes — it never commands the escalator controller. It ships with the working node,

IoT Escalator Health Monitor with Vibration and Performance Dashboard — project thumbnail preview
More project photos (2)

The problem

Escalators in malls and metro stations run 12–18 hours a day, and their failures are disruptive and occasionally dangerous — step-chain elongation, bearing wear and drive faults develop silently until a breakdown or an emergency stop. Maintenance today is mostly schedule-based: technicians inspect at fixed intervals whether the machine needs it or not. Vibration is the earliest tell — a degrading bearing or loosening chain changes the machine's vibration signature weeks before failure. This project builds the instrument that watches for it: a wireless ESP32 node with a magnet-mounted MEMS accelerometer at the drive-end bearing, plus motor current, step speed and gearbox temperature sensing, streaming to a dashboard that renders waveform and spectrum views, trends vibration RMS over 7 days, logs events, and suggests the right maintenance check in plain language. Strictly monitoring-only: nothing in this build can command the escalator.

How it works

  1. The accelerometer is magnet-mounted at the drive-end bearing; current, speed and temperature sensors are fitted at the drive.
  2. The ESP32 samples vibration at ~1.6 kHz, computing RMS, crest factor and dominant frequency per window, shown live on the OLED.
  3. Feature sets plus current, speed and temperature are published over Wi-Fi to the backend with timestamps.
  4. The dashboard renders live gauges, the waveform/spectrum view, the 7-day RMS trend and the event log.
  5. Threshold and trend rules watch the data: RMS crossing the alert line or a rising elongation trend raises a fault event.
  6. Each fault event carries a maintenance suggestion; the node itself only observes and never drives the escalator.

Tech stack:

  • ESP32 (node controller + Wi-Fi)
  • ADXL345-class MEMS accelerometer, magnetic mount
  • Current · speed · temperature sensors
  • 0.96" OLED on-node display
  • Wi-Fi telemetry with timestamps
  • Vibration feature extraction (RMS · crest factor · FFT)
  • HTML · CSS · JS dashboard
  • Threshold + trend alert rules engine
Parameter Value
Vibration sampling ~1.6 kHz (design target)
Features RMS, crest factor, dominant frequency
Extra channels Motor current, step speed, gearbox temp
Alert threshold Vibration RMS 6.3 mm/s (configurable, design target)
Trend window 7-day RMS history
Dashboard Gauges, waveform/spectrum, trend, event log
On-node display 0.96" OLED with live bar graph
Telemetry Wi-Fi, timestamped feature sets
Mounting Magnetic accelerometer base at drive-end bearing
Control interface None — monitoring only, by design

Project features

  • [Vibration feature extraction] Tri-axial MEMS sensing with RMS, crest factor and dominant-frequency computed on the ESP32 at ~1.6 kHz sampling (design target).
  • [Multi-channel monitoring] Motor current, step speed and gearbox temperature tracked alongside vibration for full context.
  • [Waveform + spectrum views] Switchable time-waveform and frequency-spectrum plots of the latest vibration window on the dashboard.
  • [7-day trend with alert line] Vibration RMS trended daily against a configurable alert threshold.
  • [Event & fault log] Timestamped INFO/WARN events: comms gaps, heartbeat restores, threshold crossings.
  • [Maintenance suggestions] Plain-language advisories from trend rules (e.g. chain-elongation trend → schedule tension check).
  • [On-node OLED readout] Live vibration bar graph, RMS and status on the node's own display for field checks.

What is included

  • Assembled sensor node (ESP32, accelerometer, OLED, sensor inputs, enclosure)
  • Node firmware with vibration feature extraction and telemetry
  • Web dashboard (gauges, waveform/spectrum, trend, event log, suggestions)
  • Backend with data store and alert rules engine
  • Installation and mounting notes
  • Project report PDF (vibration theory, system design, methodology)
  • PPT presentation and viva Q&A

Limitations & prerequisites

  • Vibration thresholds and sampling figures are design targets; fault rules are heuristic advisories, not certified diagnostics.
  • The system must never be wired into escalator safety circuits or the controller — monitoring only, stated throughout the documentation.
  • Installation needs facility permission and a safe mounting point; the guide covers placement, not site certification.
  • Wi-Fi coverage is required at the node; a LoRa/cellular variant is future scope.
  • Bearing-fault frequency matching is future scope — the base build reports features and trends, not named fault diagnoses.

Frequently Asked Questions

What does vibration tell you about an escalator?

Bearings, chains and drives each have a vibration signature; rising RMS, a climbing crest factor or a new dominant frequency indicates developing wear weeks before it becomes a failure.

How is the sensor attached?

The MEMS accelerometer sits on a round magnetic base, mounted at the drive-end bearing — no drilling, removable for maintenance windows.

Can it stop the escalator on a fault?

No, and it must not. This is a monitoring-only instrument; all control stays with the escalator's own certified controller and safety circuits.

What is crest factor and why show it?

Peak-over-RMS ratio — it rises when impacts (like a spalled bearing) appear in the vibration, often before RMS itself climbs. The dashboard reports both.

Does it work on moving walkways too?

The sensing approach transfers directly; thresholds and mounting points would be re-tuned per machine, documented as an adaptation path.

Is this project suitable for a final-year project?

Yes — for Electronics, Electrical and IoT programs. It combines vibration analysis, embedded DSP, wireless telemetry and a genuinely useful dashboard. Suitable for B.E./B.Tech final-year projects in Electronics, Electrical and IoT.

Components & software requirements
  • ESP32 (node controller + Wi-Fi)
  • ADXL345-class MEMS accelerometer, magnetic mount
  • Current · speed · temperature sensors
  • 0.96" OLED on-node display
  • Wi-Fi telemetry with timestamps
  • Vibration feature extraction (RMS · crest factor · FFT)
  • HTML · CSS · JS dashboard
  • Threshold + trend alert rules engine
Delivery information

Built-to-order project. Delivery timeline is shared after order confirmation based on current queue.

Support terms

Complete documentation, setup guide, and viva preparation included. Support for setup and explanation provided.

Download abstract (PDF)

Related guides

All guides
Blueprint-style technical illustration of an ESP32 development board at the centre, with sensor nodes, data-flow arrows and a circuit-brain motif representing an AI agent reasoning and sending decisions back.Engineering students building IoT or embedded final-year projects who want to add local AI agent behaviour with ESP32, MQTT and a small language model.

AI Agents on ESP32: Agentic IoT Final-Year Projects

An agentic IoT system observes, reasons, acts, remembers and explains. On ESP32 that means a split architecture: the chip senses and acts while a small local model (Ollama on your laptop) reasons over MQTT — a full LLM needs gigabytes of RAM the chip doesn't have. This guide covers three working patterns (host-reasoned agent, on-device tinyML on ESP32-S3, and a hybrid of both), plus Wi-Fi CSI presence sensing, parts and budget for India, code shapes, and honest limits to state in your report.

Read guide
Technical illustration of three electronic control units linked by a twisted-pair CAN bus cable carrying signal pulses between them.Electronics, E&TC, IoT and robotics students who keep hearing “CAN bus” in EV, automotive and industrial project ideas and want to understand it properly before wiring anything

CAN Bus Basics for Students: How ECUs Communicate

CAN bus is the shared network that lets dozens of controllers in a car, EV or robot communicate over two wires. This guide explains message IDs, arbitration, the physical layer, frame structure, error handling and CAN FD, then walks through building a working two-node bench network with an ESP32 and a transceiver.

Read guide
Illustration of a quadcopter drone build showing labeled parts including frame, motors, propellers, ESCs, flight controller, and battery.B.E./B.Tech Electronics, Mechanical, and Computer Science students planning to build a quadcopter drone who need to select compatible parts without wasting money on mismatched

Drone Build: Parts Selection Guide

Picking drone parts that actually work together is a sizing problem, not a shopping problem. This guide walks the compatibility chain — frame to props to motors to ESCs to battery — with the thrust math, firmware choices, LiPo safety, and the bench-test order that prevents disasters.

Read guide
Get a quotation