Built to order

IoT-Based Underground Cable Fault Detection

An ESP32-based unit that locates underground cable faults by measuring line resistance, displays the phase and fault distance on an LCD, and pushes alerts to a cloud dashboard — a classic high-volume EEE search, rebuilt modern while rivals still sell stale Arduino+GSM kits.

Illustrative render of the IoT-Based Underground Cable Fault Detection prototype.
More project photos (2)

The problem

When an underground power cable faults, utilities today dig up entire road stretches hunting for the break — expensive, slow, and disruptive. This project pinpoints the fault from the surface: an ESP32-based unit injects a test signal into the cable, measures the resulting line resistance, and computes the fault distance in kilometers using the cable's resistance-per-km constant. The phase and distance show on an LCD and push to a cloud dashboard with alerts. Underground cable fault detection is a classic high-volume EEE student search — three sellers already monetize it with thin WooCommerce pages and stale Arduino+GSM designs. This is the modern ESP32 + cloud rebuild that outranks them.

How it works

  1. The cable is modeled as a resistor ladder; each kilometer of cable contributes a known resistance.
  2. The ESP32 injects a low-voltage test signal through a relay-switched circuit into the suspect cable.
  3. An ADC measures the loop resistance; the firmware divides by the calibrated ohm-per-km constant to compute fault distance.
  4. The faulted phase is identified by testing each phase in sequence; results display on the LCD instantly.
  5. Readings are pushed to the cloud dashboard and an SMS/push alert fires with phase + distance, so the repair crew digs at one spot, not the whole road.

Project features

Features:

  • Fault distance calculation from line-resistance measurement (Murray/Varley loop principle, simplified for demo)
  • Three-phase cable support — identifies which phase faulted (R/Y/B)
  • 16x2 LCD showing faulted phase + distance in kilometers
  • Cloud dashboard (ThingSpeak/Blynk) with fault history and location log
  • SMS/push alert on fault detection with phase and distance
  • Simulated fault switches — create faults at known distances to demo and calibrate
  • Relay-based cable switching for safe test-signal injection
  • Calibration mode: set the cable's ohm-per-km constant for accurate readings

What is included

What's included:

  • Complete ESP32 firmware with full source code
  • Circuit diagram and PCB-ready wiring layout
  • Calibration procedure for the ohm-per-km constant
  • Project report PDF (synopsis, fault-location theory, design, testing, results)
  • Presentation PPT for review/demo day
  • Viva Q&A sheet covering cable faults, Murray loop, and IoT architecture
  • Demo script: injecting faults at known distances and verifying readings

Limitations & prerequisites

  • Demo uses a resistor-ladder cable model; real-field deployment needs high-voltage isolation and utility-grade equipment (out of scope)
  • Distance accuracy depends on correct ohm-per-km calibration and stable temperature
  • Detects short-circuit/low-resistance faults; high-impedance arcing faults need advanced TDR methods (discussed in the report)
  • Cloud alerts need WiFi at the unit's location
  • This is a built-to-order project — delivery time depends on component availability
Components & software requirements
  • ESP32 microcontroller
  • Resistor ladder cable-simulation board (or real cable sample)
  • 16x2 LCD display (I2C)
  • Relay module for test-signal switching
  • Voltage/current sensing circuitry
  • Push buttons for simulated fault injection at set distances
  • Power supply unit, enclosure, connecting terminals
  • ThingSpeak/Blynk cloud dashboard

Download abstract (PDF)

Related guides

All guides
Technical illustration of a cloud server pushing event envelopes outward to web application endpoints for payments, dashboards and chat.Web development and IoT students who have built a REST API or an ESP32 project and now need external services (payments, GitHub, messaging) to notify their app when things happen

Webhooks Explained: Receive Data from Payments, GitHub and IoT

A webhook lets a service call your server the moment an event happens — payments, code pushes, form submissions. This guide explains the event anatomy, HMAC signature verification, the fast-acknowledge reliability pattern, local testing, and how webhooks compare with polling, WebSockets and SSE.

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