Automatic ELCB Reset System with/without GSM
Automatic ELCB Reset System with/without GSM is an iot monitoring and automation prototype that can be demonstrated with Isolated breaker-status simulator. A realistic FYP outcome is a working prototype with this processing path: Reads modules and runs the local control logic; Converts readings into a documented state, threshold or event. The result is delivered through SIM800L/SIM7600 cellular module, Status LEDs and buzzer. The important proof is repeatable input readings, decisions, output states, timestamps, and test results, not just a device that powers on.
Project Snapshot
Quick Summary
Automatic ELCB Reset System with/without GSM is a iot monitoring and automation prototype idea for students who need a working demo with Isolated breaker-status simulator. A good version focuses on SIM800L/SIM7600 cellular module, Status LEDs and buzzer using Arduino Uno, Isolated breaker-status simulator, SIM800L/SIM7600 cellular module, with testing evidence for input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour.
Difficulty
Intermediate
Time Required
4-8 weeks for wiring, coding, dashboard/app integration and repeated testing
Cost
No fixed price. Cost depends on selected controller, sensors, communication modules, casing, dashboard/app features and documentation scope.
Engineering profile
IoT monitoring and automation prototype
Function Flow
Power and initialise
The regulated 5 v supply with common ground starts the Arduino Uno and connected modules within their voltage and current requirements.
Acquire the input
Isolated breaker-status simulator supplies the project measurement, identity or trigger.
Validate the signal
Firmware rejects missing or implausible samples and applies calibration, debounce or averaging appropriate to the module.
Make the decision
The controller compares the validated value with the documented threshold, authorisation rule or operating state.
Act and communicate
Status LEDs and buzzer presents the local result, while the communication link sends the corresponding event or reading.
Record and recover
The test sheet records the input, decision and output. On a fault, the system enters a defined safe state instead of silently continuing.
System Block Diagram
Functional signal and data path for the recommended prototype scope. Final pin assignments and electrical wiring must follow the exact module datasheets.
Isolated breaker-status simulator
Represents trip status without automatically re-energising a mains circuit
Arduino Uno
Reads modules and runs the local control logic
Filtering and decision logic
Converts readings into a documented state, threshold or event
Status LEDs and buzzer
Reports detected trip status without resetting or energising the circuit
SIM800L/SIM7600 cellular module
Sends SMS or data using a powered SIM connection
Recommended Components & Platform
Arduino Uno
controllerReads modules and runs the local control logic
View component guide
Isolated breaker-status simulator
inputRepresents trip status without automatically re-energising a mains circuit
SIM800L/SIM7600 cellular module
communicationSends SMS or data using a powered SIM connection
View component guide
Status LEDs and buzzer
outputReports detected trip status without resetting or energising the circuit
Regulated 5 V supply with common ground
powerProvides stable power while keeping higher-current loads on suitable drivers
Engineering Validation Notes
Verify every module voltage, logic level, current draw and driver requirement against the exact purchased board datasheet before wiring.
Calibrate or baseline the input with known test conditions and report repeatability, response time and observed limitations.
The prototype must not automatically re-energise a tripped mains circuit. Demonstrate status detection on an isolated low-voltage simulator; inspection and manual reset belong to a qualified person.
Learning Resources
How to choose a strong FYP topic
Use this before locking the title, objectives and prototype scope.
FYP proposal: title, objectives and scope
A practical guide for turning a project idea into a supervisor-ready proposal.
Arduino Uno vs ESP32 for electronics FYP
Compare when Arduino is enough and when ESP32 is the better project controller.
GPS vehicle tracking system FYP guide
Understand GPS lock, GSM alerts, map links and testing limitations.
Electronics troubleshooting checklist before demo
Check wiring, power, sensors, alerts and backup demo flow before viva day.
Build Scope Options
Basic prototype
Core demo using Arduino Uno, Isolated breaker-status simulator, SIM800L/SIM7600 cellular module, Status LEDs and buzzer with visible input and output response.
Intermediate prototype
Adds dashboard/database logging, alerts, calibration notes, and cleaner wiring for reliable demonstration.
Advanced prototype
Adds casing, mobile/cloud features, multi-node setup, image processing, maps, or reporting depending on scope.
Expected Demo Outcome
- Shows SIM800L/SIM7600 cellular module, Status LEDs and buzzer from real or realistic Isolated breaker-status simulator.
- Stores or displays input readings, decisions, output states, timestamps, and test results as report evidence.
- Demonstrates the main iot monitoring and automation prototype workflow end to end.
- Includes a clear test scenario for input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour.
Accuracy & Limitations
This is realistic for FYP when the scope stays controlled: Validate the input-to-controller-to-output path with safe bench tests before adding cloud features, casing, or extra modules.
Prototype reliability depends on correct wiring, stable power supply, and proper module selection.
Sensor readings can vary with placement, calibration, environment, and demo conditions.
GSM and SMS features depend on SIM balance, signal coverage, and telco network availability.
Validation & Testing Plan
Run repeated tests under controlled demo conditions and record readings or status changes.
Verify input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour before adding extra features.
Capture photos, dashboard screenshots, serial logs, or database entries as testing evidence.
Document sensor/module limits honestly so the report does not overclaim industrial accuracy.
Troubleshooting
If readings are unstable, test the sensor separately before connecting the dashboard or app.
If the module resets, check power supply, common ground, loose jumper wires, and current requirements.
If alerts or cloud updates fail, test WiFi, hotspot, SIM balance, API token, and internet connection early.
If the demo is hard to explain, focus on one repeatable workflow for SIM800L/SIM7600 cellular module, Status LEDs and buzzer.
Common Mistakes
- Choosing a scope that is too large for the available FYP timeline.
- Validate the input-to-controller-to-output path with safe bench tests before adding cloud features, casing, or extra modules.
- Writing objectives that do not match the actual prototype or software demo.
- Preparing no backup demo flow for viva day.
- Using weak power supply, loose jumper wires, or unprotected sensors during demonstration.
- Skipping calibration or test readings before presenting results.
- Testing GSM/GPS only indoors and discovering signal issues during final demo.
Suggested Report Sections
Problem statement and project background
Objectives focused on iot monitoring and automation prototype and achievable prototype scope
System block diagram showing Isolated breaker-status simulator -> processing -> SIM800L/SIM7600 cellular module, Status LEDs and buzzer
Methodology using Arduino Uno, Isolated breaker-status simulator, SIM800L/SIM7600 cellular module, Status LEDs and buzzer with data flow and user/prototype workflow
Testing results for input calibration or baseline, response time, repeatability, power stability, communications failure, and safe-state behaviour
Limitations, discussion, and future improvements
Alternatives
Related Projects
Smart Helmet Alcohol Detection System with Vehicle Start Prevention
Gas Sensor, Relay, GSM
Auto Theft and Immobilized System with SMS and Camera Feature
Arduino, GSM, Camera
Vehicle Crash Alerting System with GPS and GSM
Arduino, GPS, GSM
Fingerprint based Vehicle Startup System with GPS and GSM Immobilisation
Arduino, Fingerprint, GPS
Child Left in Car Alert System with SMS alerting
Arduino, GSM, Temperature
Panic Button with GPS Alerting System
Arduino, GPS, GSM
FAQ
Is "Automatic ELCB Reset System with/without GSM" suitable for FYP?
Yes. This title can be suitable for FYP or Projek Akhir Tahun when the scope is controlled. The recommended scope is validate the input-to-controller-to-output path with safe bench tests before adding cloud features, casing, or extra modules.
What difficulty level is this project?
The suggested difficulty is Intermediate. The actual difficulty depends on whether you choose a basic, intermediate, or advanced prototype scope.
What platform can this project use?
This project can be planned using Arduino Uno, Isolated breaker-status simulator, SIM800L/SIM7600 cellular module, Status LEDs and buzzer. The final platform can be adjusted based on supervisor requirements and the chosen scope; common alternatives include Arduino, ESP32, Raspberry Pi, or another controller depending on the required features.
Is there a fixed project price?
No fixed price is published because the final quotation depends on project scope, features, timeline, hardware, software, and documentation requirements.
Can Rectronx help with documentation and demo preparation?
Yes. Rectronx can help with project planning, prototype development, coding explanation, report structure, testing evidence, and demo preparation.