IOT Based Smart Energy Meter

A PROJECT REPORT ON
“IoT BASED SMART ENERGY METER. ”
SUBMITTED TO THE MSBTE, MUMBAI

IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD
DIPLOMA IN COMPUTER TECHNOLOGY

SUBMITTED BY
Miss. Badge Kajal D.
Miss. Dhanwate Vaishali B.
Miss. Tupke Kaveri S.
Miss. Bhingare Komal H.
Under the Guidance of

PROF. V. A. PARJANE
DEPARTMENT OF COMPUTER TECHNOLOGY,
SANJIVANI RURAL EDUCATION SOCIETY
S.K.B.P. POLYTECHNIC, KOPARGAON
DIST. AHMEDNAGAR - 423603
( 2019-20 )
Department of Computer Technology
S.K.B.P. POLYTECHNIC, KOPARGAON
CERTIFICATE
This is to certify that the project work entitled

IoT BASED SMART ENERGY METER.
Submitted by
Is a bonafide work carried out by above students under the supervision of Prof.
V. A. Parjane and it is submitted towards the partial fulfillment of the require-
ment of MSBTE, Mumbai for the award of Diploma in Computer Technology.
Prof. V. A. Parjane Prof. V. A. Parjane

(Project Guide) (Project Coordinator.)
Prof. G. N. Jorvekar Prof. A. R. Mirikar

(HOD) (Principal)
Date : / /
Place : Kopargaon
MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI
EXAMINERS CERTIFICATE
This is to certify that the project work entitled
IoT BASED SMART ENERGY METER.
Submitted by
for the partial fulfillment of the requirement of Diploma in Computer Technol-
ogy is examined certified.
Internal Examiner External Examiner

(Name of Internal) (Name of External)
ACKNOWLEDGEMENT
First and the foremost I, express my deep sense of gratitude, sincere thanks and
deep sense of application to Project Guide Prof. V.A.Parjane , Department of Computer
Technology, Sanjivani K.B.P. Polytechnic, Kopargaon. Your availability at any time through-
out the year, valuable guidance, opinion, view, comment, critics, encouragement, and sup-
port tremendously boosted this project work. .
Lots of thanks to Head, Computer Technology Department, Prof. G. N. Jorvekar for
providing me the best support I ever had. I like to express my sincere gratitude to Prof. A.R.
Mirikar, Principal, Sanjivani K.B.P. Polytechnic, Kopargaon for providing great platform
to complete the project within the scheduled time.
I am also Thankful to all the faculty members, Computer Technology Department,
Sanjivani K.B.P. Polytechnic, Kopargaon for giving comments for improvement of work,
encouragement and help during completion of the project.
Last but not the least; I should say thanks from my bottom of heart to my family and
friends for their never ending love, help, and support in so many ways through all this time.
Thank you so much.

Abstract
In this paper the idea of smart energy meter using IoT and Node MCU have been
introduced. In this method we are using Node MCU because it is energy efficient i.e.
it consumes less power, it is fastest and has two UARTS. In this paper, energy meters
which is already installed at our houses are not replaced, but a small modification on the
already installed meters can change the existing meters into smart meters. The use of Wi-Fi
module provides a feature of notification through Server. One can easily access the meter
working through web page that we designed. Current reading with cost can be seen on web
page. Automatic ON OFF of meter is possible. Threshold value setting and sending of
notification is the additional task that we are performing.
Contents
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . II
1 INTRODUCTION 1
1.1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 PROBLEM STATEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 REQUIREMENT ANALYSIS 3
2.1 REQUIREMENT SPECIFICATION . . . . . . . . . . . . . . . . . . . . . 3
2.2 SYSTEM REQUIREMENT . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2.1 HARDWARE REQUIREMENT . . . . . . . . . . . . . . . . . . . 3
2.2.2 SOFTWARE REQUIREMENT . . . . . . . . . . . . . . . . . . . 4
2.3 Literature Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 SYSTEM ANALYSIS 5
3.1 PROCESS MODEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1 Waterfall Model . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.2 Advantages of Waterfall Model . . . . . . . . . . . . . . . . . . . 5
3.1.3 When to Use Waterfall Model . . . . . . . . . . . . . . . . . . . . 6
3.2 BLOCK DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 ER DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5 UML Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.5.1 Use case Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.6 Sequence Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.6.1 Activity Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4 IMPLEMENTATION DETAILS 14
4.1 NODE MCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 RELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 POTENTIAL TRANSFORMER . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 CURRENT SENSOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.5 VOLTAGE SENSOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6 LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.7 FLOWCHART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.8 CODING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5 TESTING, RESULTS AND ANALYSIS 26

5.1 TESTING AND RESULT . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.1 Hardware Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.2 SOFTWARE TESTING . . . . . . . . . . . . . . . . . . . . . . . 26
5.1.3 Unit Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.1.4 INTEGRATION TESTING . . . . . . . . . . . . . . . . . . . . . 27
5.1.5 VALIDATION TESTING . . . . . . . . . . . . . . . . . . . . . . 27
5.2 TEST CASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2.1 RESULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6 APPLICATION, FUTURE SCOPE AND ADVANTAGES 31

6.0.1 APPLICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.0.2 FUTURE SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.0.3 ADVANTAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7 CONCLUSION AND REFERENCES 33

7.0.1 CONCLUSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.0.2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
List of Figures
3.1 The Waterfall Model: A Traditional Approach Of SDLC . . . . . . . . . . 6

3.2 Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 DFD Level 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 DFD Level 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.5 DFD Level 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.6 ER Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.7 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.8 Sequence Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.9 Architectural Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1 Node MCU DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2 RELAY DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3 POTENTIAL TRANSFORMER DIAGRAM . . . . . . . . . . . . . . . . 17
4.4 CURRENT SENSOR DIAGRAM . . . . . . . . . . . . . . . . . . . . . . 18
4.5 VOLTAGE SENSOR DIAGRAM . . . . . . . . . . . . . . . . . . . . . . 19
4.6 LCD Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7 FlowChart Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
I
List of Tables
5.1 Taste Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2 Literature Survey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
II
IoT BASED SMART ENERGY METER
C HAPTER 1
INTRODUCTION
1.1 INTRODUCTION
In the present billing system the distribution companies are unable to keep track
of the changing maximum demand of consumers. The consumer is facing problems like
receiving due bills for bills that have already been paid as well as poor reliability of elec-
tricity supply and quality even if bills are paid regularly. The remedy for all these problems
is to keep track of the consumers load on timely basis, which will held to assure accurate
billing, track maximum demand and to detect threshold value. These are all the features to
be taken into account for designing an efficient energy billing system. The present project
“IoT Based Smart Energy Meter” addresses the problems faced by both the consumers and
the distribution companies. The paper mainly deals with smart energy meter, which utilizes
the features of embedded systems i.e. combination of hardware and software in order to
implement desired functionality.
Department of Computer Technology, S.K.B.P.Polytechnic, Polytechnic 1

1.2 PROBLEM STATEMENT
Smart energy meter as the name suggest; it is a next generation meter which is highly
efficient and user friendly ,which provides a great way to save control the usage of energy.
These are all the features to be taken into account for designing an efficient en-
ergy billing system. The present project “IoT Based Smart Energy Meter” addresses the
problems faced by both the consumers and the distribution companies. The paper mainly
deals with smart energy meter, which utilizes the features of embedded systems i.e. combi-
nation of hardware and software in order to implement desired functionality.
1.3 OBJECTIVES
The main objective of smarter meter reading syatem is provides effective, reliable
and efficient wireless automatic meter reading, biling and security through the use of this
system. Thus reduce human operator meter reading operation costs. . The remedy for all
these problems is to keep track of the consumers load on timely basis, which will held to
assure accurate billing, track maximum demand and to detect threshold value.

C HAPTER 2
REQUIREMENT ANALYSIS
2.1 REQUIREMENT SPECIFICATION
As per the problem definition of the project the requirement analysis from the
software and hardware has been performed. The requirements have been elaborated
in the following section.
2.2 SYSTEM REQUIREMENT
In this chapter of our project all the requirement needed to run the project
successfully on the system are specified. The project requirements are useful for
its deployment in users computing environment. Generally they are categorized
as.
2.2.1 HARDWARE REQUIREMENT
• Node MCU
• Wifi Modem
• Relay
• 16*2 LCD Display
• Current sensors
• Voltage sensors
• Energy Meter

2.2.2 SOFTWARE REQUIREMENT
• Orcad
• Altium
2.3 Literature Survey

C HAPTER 3
SYSTEM ANALYSIS
3.1 PROCESS MODEL
This is the most common easy to implement and classic of all the life cycle models.
It is also referred as the Classic Life Cycle Model or Linear-Sequential Life Cycle Model.
This model places a lot of emphasis on document.
3.1.1 Waterfall Model
This is the most common easy to implement and classic of all the life cycle models.
It is also referred as the Classic Life Cycle Model or Linear-Sequential Life Cycle Model.
This model places a lot of emphasis on documentation i.e. Requirement Specification and
Design Document. In waterfall model each phase must be completed successfully before
the immediate next phase can design.
3.1.2 Advantages of Waterfall Model
• It allows for departmentalization and control.
• It is very simple and easy to implement.
• A schedule can be set with deadlines for each stage of development and a product
can be proceed through the development process model phases one by one.

Figure 3.1: The Waterfall Model: A Traditional Approach Of SDLC
• Development moves from concept, through design, implementation, testing, in- stal-
lation, troubleshooting, and ends up at operation and maintenance. Each phase of
development proceeds in strict order.
3.1.3 When to Use Waterfall Model
• Requirements are very well known.
• Product definition is stable.
• Technology is understood.
• New version of an existing product.
• Porting an existing product to a new platform.
3.2 BLOCK DIAGRAM
A control system may consist of a number of components. In order to show the
functions performed by each component in engineering, we commonly use a diagram called

the Block Diagram. A block diagram of a system is a pictorial representation of the function
performed by each component and of the flow of signals. Such a diagram depicts the
inter-relationships which exist between the various components. A block diagram has the
advantage of indicating more realistically the signal flows of actual system. In a block
diagram all system variables are linked to each other through functional blocks. The
functional block or simply Block is a symbol for the mathematical operation on the input
signal to the block which produce the output. The transfer functions of the components are
usually entered in the corresponding blocks, which are connected by arrows to indicate the
direction of flow of signals.
Figure 3.2: Block Diagram

3.3 Data Flow Diagram
A data flow diagram is the graphical representation of flow data through an informa-
tion system. Modeling its process aspects often they are preliminary step used to create an
overview of system which can be later elaborated DFDs can be also used for the visualiza-
tion of data processing. A DFD shows what kind of information will be input to and output
from the system where the data will come from and go the data will be stored. It does not
show information about whether process will operate in sequence or parallel.
DFD 0
Figure 3.3: DFD Level 0
DFD 1

DFD 2

3.4 ER DIAGRAM
Figure 3.6: ER Diagram

3.5 UML Diagrams

3.5.1 Use case Diagram:
Figure 3.7: Use Case Diagram

3.6 Sequence Diagram:
Figure 3.8: Sequence Diagram

3.6.1 Activity Diagram:
Figure 3.9: Architectural Diagram

C HAPTER 4
IMPLEMENTATION DETAILS
4.1 NODE MCU
Specifications and Features of Node MCU:
11 b/g/n Wi-Fi Direct (P2P), soft-AP
Integrated TCP/IP protocol stack
CP2102 Serial / USB Chip
4MB Flash Memory
Integrated low power 32-bit CPU
SDIO 1.1 / 2.0, SPI, UART
Integrated TR switch, balun, LNA, power amplifier and matching network
Integrated PLLs, regulators, DCXO and power management units
On board USB to serial chip to easily program and upload codes from the Arduino
IDE
Has on board 3.3V regulator to ensure enough power to function as your go-to WiFi
chip!
Easy access to the GPIO pins for easy prototyping
ESP-12E Processor
Voltage Regulator / Converter, excellent DC to DC conversion, super efficient

Figure 4.1: Node MCU DIAGRAM
4.2 RELAY
Relay are output devices which are used to control or operate some external devices.
This is a 5 volt Isolated relay module which means that there is a Optocoupler used in
between your control circuit and the relay thus protecting your circuit in case of any short
circuit issues on the relay side.The relay is driven safely by BC547 transistor which is
triggered via an Optocoupler IC which serves as isolator between your microcontroller and
the relay.

Figure 4.2: RELAY DIAGRAM
4.3 POTENTIAL TRANSFORMER
Potential transformer or voltage transformer gets used in electrical power system for
stepping down the system voltage to a safe value which can be fed to low ratings meters
and relays. Commercially available relays and meters used for protection and metering, are
designed for low voltage.

Figure 4.3: POTENTIAL TRANSFORMER DIAGRAM
4.4 CURRENT SENSOR
This sensor produces an output voltage which is directly proportional to sensed cur-
rent. It works on the principle of Hall Effect.
5V should be supplied to Vcc of ACS712 breakout board and the GND should be the neg-
ative of 0v of supply. Once it is powered, the Vout should produce output voltage which
represent current going through the sensing pads. When the load is in OFF state then the
sensor produces Vcc/2 voltage (no loadvoltage).
ACS712 is able to measure current in two directions. Output voltage more than 2.5V
(VCC/2) indicates current in one direction and voltage less than 2.5V indicates current
in another direction.

Figure 4.4: CURRENT SENSOR DIAGRAM
4.5 VOLTAGE SENSOR
FEATURES of ZMPT101B AC voltage sensor Module
9. • Voltage upto 250 volts can be measured.

13.
12.
11.
10.
8.
7.
6.
5.
4.
3.
2.
1.
• Light weight with on-board micro-precision voltage transformer.
• High precision on-board op-amp circuit.
• Operating temperature: 40o C + 70o C Supply voltage 5 volts to 30 volts.

Figure 4.5: VOLTAGE SENSOR DIAGRAM
4.6 LCD
Features of LCD
• 5*8 dots with cursor.
• Built-it controller(KS 0066 or equivalent).
• +5V power supply (also available for +3V).
• 1/16 duty cycle.
• B/L to driven by pin1, pin2 or pin 15,pin 16 or A.K (LED)
• N.V. optional for +3V power supply

Figure 4.6: LCD Diagram
4.7 FLOWCHART
Step 1: Start
Step 2: Initialize LCD, Relay, Energy Meter
Step 3: Wait for Second
Step 4: Display Collage name
Step 5: Wait for Command
Step 6: Load ON, then Display Reading and Bill.
Step 7: If OFF = 1 then Load OFF
Step 8: Go to Step 5

Figure 4.7: FlowChart Diagram
4.8 CODING
char ssid[] = ”yash123”;
char pass[] = ”123456789”;
int units,calc,offr am;
intcounter = 0;
intRelay = D6;
boolgob ys witch = true;
intlasti nputv alue = LOW ;
intB;

intButton = D4;
//intswitchi nputv alue = LOW ;
void setup()
Serial.begin(9600);
Bly.begin(ssid, pass);
lcd.begin(16,2);// initialize the lcd
lcd.init();
lcd.backlight();
lcd.setCursor(0 ,0);
lcd.print(”Sanjivani K.B.P”);
lcd.setCursor( 0,1);
lcd.print(”Polytechnic”);
delay(3000);
lcd.setCursor(0 ,0);
lcd.print(”IOT based smart ”);
lcd.setCursor( 0,1);
lcd.print(”energy meter”);
delay(3000);
lcd.clear();
pinMode(Relay, OUTPUT);
pinMode(Button, INPUT);
digitalWrite( Relay,HIGH);// put your setup code here, to run once:

void loop()
Blynk.run();
int val;
val=digitalRead(Button);
if (val==0)
// digitalWrite( Relay,LOW);
int switchi nputv alue = digitalRead(B);
if (switchi nputv alue == HIGH)
lcd.setCursor(0, 0);
lcd.print(”T otalunits = ”);
lcd.print(”U nitCost = ”);
counter = (counter + 1)delay(10000);
Serial.print(counter);
units = counter;
Serial.print(”T otalU nits = ”);
//lcd.setCursor(0, 0);
//lcd.print(”T otalunits = ”);
Serial.println(units);

Blynk.virtualW rite(V 1, units);
lcd.print(units);
calc = units ∗ 4;
Serial.print(”U nitCost = ”);
//lcd.setCursor(0, 1);
//lcd.print(”U nitCost = ”);
Serial.println(calc);
Blynk.virtualW rite(V 2, calc);
lcd.print(calc);
delay(2000);
lasti nputv alue = switchi nputv alue;
else
delay(500);
counter = (counter + 1)Serial.print(counter);
else{
digitalW rite(Relay, HIGH);

lcd.print(”SystemisOf f ”);
lcd.print(”T urnOnSwitch”);
//putyourmaincodehere, torunrepeatedly :

C HAPTER 5
TESTING, RESULTS AND ANALYSIS
5.1 TESTING AND RESULT
•Testing is an internal part of any system. The various objectives of testing are:
• To uncover the errors in function logic or implementation for the software.
• To verify that software needs the specific requirement.
• To verify that software has been implemented according to the predefined standard.
• The primary purpose of testing is to uncover systems limitations and measure its full
capabilities. A list of various planned tests and a brief explanation follows belows.
5.1.1 Hardware Testing
Automated hardware testing validates or verifies a products performance before it leaves
the factory, using special automated test hardware the product being tested is generally
called UUT (Unit Under Test), or sometimes DUT (Device Under Test).
5.1.2 SOFTWARE TESTING
Software testing is the process of validating and verifying that a software program or
application or product, meets the business and technical requirements that guided its design
and development.

5.1.3 Unit Testing
In this each module is tested individually. Criteria selected for identifying unit test module
is that identity modules that has core functionality implementation. Module could be and
individual function or procedure.
5.1.4 INTEGRATION TESTING
tegration testing individuals modules and tested as a group. Integration Testing takes as
its input modules that have been unit tested, groups then in larger aggregates, applies tests
define in an integration test plan to those aggregations, and delivers as its output the in-
tegrated system ready for testing. The purpose of integration testing to verify functional,
performance and reliability requirements.
5.1.5 VALIDATION TESTING
The process of evaluating software during or at the end of the development process is to
determine whether its satisfied requirement or not.

5.2 TEST CASE
Table 5.1: Taste Case
5.2.1 RESULT



C HAPTER 6
APPLICATION, FUTURE SCOPE

AND ADVANTAGES
6.0.1 APPLICATION
• Many industries.
• In household.
• It can be used by utilities to communicate information to bill customers and operating
their electric system.
6.0.2 FUTURE SCOPE
• It can be used by utilities to communicate information to bill customers and operating
their electric system.
• Converting this system to home automation will prove an emerging benefit to IoT tech-
nology.
• Using this technology in smart grid can provide more efficient power supply and power
saving.
• IoT technology coupled with smart meters and smart devices can help in the upbringing
the cities into smarter and developed cities.

6.0.3 ADVANTAGES
• There will be no more estimated bills. The user has to pay bills for what is actually used
in a billing period.
• The smart meter will report if it encounters any electrical issues to deliver better quality
of supply.
• It will facilitate prepayment facility.
• Electricity providers can offer new schemes on usage of electricity.
• It will be providing precise details of consumption. This will allow users to manage the
usage of electricity.
• The user can monitor the usage remotely.
The user can set his limits of consumption and crossing of this limit will gener-
ate warning message to the user.

C HAPTER 7
CONCLUSION AND REFERENCES
7.0.1 CONCLUSION
Meter reading by using IOT modem and also we can control the load using relays
via the web page. The IOT based energy meter was developed and extended with the relay
controls to disconnect the load from the power supply. Live status about power consumption
can be viewed by both consumer as well as electric board. The relay in the energy meter
can be controlled by the EB officer using the website created, for turning off the power
supply. Another relay is provided to the Thus by this project we have created the prototype
model using which we will be able to monitor the energy consumer for turning off the load
from the power supply during emergency cases.
7.0.2 References
[1] Petri Oksa, Mikael Soini, “Considerations of Using Power Line Communication. In the
AMR System”, 2006 IEEE International Symposium on 26-29, pp.208- 211, Mar. 2006
[2] Ashna.k,Sudhish N. George”GSM Based Automatic Energy Meter Reading System
with Instant Billing”,2013IEEE.
[3] Ali Abdollahi, Marjan Dehghani, and Nega Zaman zadeh,”SMS-based Reconfigurable
Automatic Meter Reading System”,16th IEEE International Conference on Control Appli-

cations Part of IEEE Multi-conference on Systems and Control Singapore,pp.1103-1107,2007.
[4] Champ Prapasawad, Kittitach Pornprasitpol and Wanchalerm Pora,”Development of
An Automatic Meter Reading System Based on ZigBee PRO Smart Power Profile IEEE
802.15.4 Standard”, 2012.
[5] Subhashis Maitra, “Embedded Power Meter- A new concept to measure the power con-
sumed by a consumer and to pay the bill”, Power System Technology and IEEE Power
India Conference, 2008.

IOT Based Smart Energy Meter

Uploaded by

Copyright:

Available Formats

IOT Based Smart Energy Meter

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IOT Based Smart Energy Meter

Uploaded by

Copyright:

Available Formats

A PROJECT REPORT ON

“IoT BASED SMART ENERGY METER. ”

SUBMITTED TO THE MSBTE, MUMBAI

DIPLOMA IN COMPUTER TECHNOLOGY

Under the Guidance of

DEPARTMENT OF COMPUTER TECHNOLOGY,

SANJIVANI RURAL EDUCATION SOCIETY

S.K.B.P. POLYTECHNIC, KOPARGAON

DIST. AHMEDNAGAR - 423603

This is to certify that the project work entitled

Prof. V. A. Parjane Prof. V. A. Parjane

Prof. G. N. Jorvekar Prof. A. R. Mirikar

This is to certify that the project work entitled

IoT BASED SMART ENERGY METER.

Miss. Badge Kajal D.

Miss. Dhanwate Vaishali B.

Miss. Tupke Kaveri S.

Miss. Bhingare Komal H.

for the partial fulfillment of the requirement of Diploma in Computer Technol-

ogy is examined certified.

Internal Examiner External Examiner

deep sense of application to Project Guide Prof. V.A.Parjane , Department of Computer

port tremendously boosted this project work. .

Lots of thanks to Head, Computer Technology Department, Prof. G. N. Jorvekar for

to complete the project within the scheduled time.

I am also Thankful to all the faculty members, Computer Technology Department,

encouragement and help during completion of the project.

Thank you so much.

5 TESTING, RESULTS AND ANALYSIS 26

6 APPLICATION, FUTURE SCOPE AND ADVANTAGES 31

7 CONCLUSION AND REFERENCES 33

3.1 The Waterfall Model: A Traditional Approach Of SDLC . . . . . . . . . . 6

4.1 Node MCU DIAGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1 Taste Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

5.2 Literature Survey. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

implement desired functionality.

Department of Computer Technology, S.K.B.P.Polytechnic, Polytechnic 1

1.2 PROBLEM STATEMENT

nation of hardware and software in order to implement desired functionality.

Department of Computer Technology, S.K.B.P.Polytechnic, Polytechnic 2

2.1 REQUIREMENT SPECIFICATION

2.2 SYSTEM REQUIREMENT

2.2.1 HARDWARE REQUIREMENT

• 16*2 LCD Display

Department of Computer Technology, S.K.B.P.Polytechnic, Polytechnic 3

2.2.2 SOFTWARE REQUIREMENT

2.3 Literature Survey

Department of Computer Technology, S.K.B.P.Polytechnic, Polytechnic 4

3.1 PROCESS MODEL

This model places a lot of emphasis on document.

3.1.1 Waterfall Model

the immediate next phase can design.

3.1.2 Advantages of Waterfall Model

• It allows for departmentalization and control.

• It is very simple and easy to implement.

Department of Computer Technology, S.K.B.P.Polytechnic, Polytechnic 5

Figure 3.1: The Waterfall Model: A Traditional Approach Of SDLC

lation, troubleshooting, and ends up at operation and maintenance. Each phase of

development proceeds in strict order.