Professional Documents
Culture Documents
Table of Contents
Chapter 1 – Introduction ............................................................................................................ 3
Chapter 1.1 objective of this chapter:..................................................................................... 3
Chapter 1.2 Project Background ............................................................................................ 3
Chapter 1.2.1 summary and overview of the project .......................................................... 3
Chapter 1.2.2 Current Scenario .......................................................................................... 3
Chapter 1.2.3 problem statement and motivation ............................................................... 4
Chapter 1.3 Approaches taken ............................................................................................... 5
Chapter 1.4 Project as a solution ............................................................................................ 5
Chapter 1.5 projects Aims and Objectives ............................................................................. 6
Chapter 1.5.1 AIM .............................................................................................................. 6
Chapter 1.5.2 Objectives .................................................................................................... 6
Chapter 1.6 Structure of the report ......................................................................................... 6
Chapter 1.7 summary of the chapter ...................................................................................... 6
Chapter 2 Background and Literature Review ................................................................... 7
Chapter 2.1 About the client and Survey ......................................................................... 7
Chapter 2.1.1 About client .................................................................................................. 7
Chapter 2.1.2 Interview with client .................................................................................... 7
Chapter 2.1.3 list of Questionnaire ..................................................................................... 8
Chapter 2.2 Similar projects .............................................................................................. 9
Chapter 2.2.1 GSM based Smart Energy Meter ......................................................... 9
Chapter 2.2.2 Smart Energy Meter with Reading Indication using GSM .............. 10
Chapter 2.2.3 Arduino-Based Prepaid Energy Meter Using GSM ......................... 11
Chapter 2.2.4 Comparison between similar projects ............................................... 12
Chapter 2.2.5 Critical analysis ..................................................................................... 12
Chapter 2.3 Understanding the Solution .............................................................................. 12
Chapter 2.3.1 Technical Requirements: ........................................................................... 12
Chapter 2.3.2 Analog meter .............................................................................................. 13
Chapter 2.3.3 Considered IOT devices ............................................................................. 13
Chapter 2.3.4 Considered Analog meter information exchange ...................................... 14
Chapter 2.4 Review of technical aspects ...................................................................... 15
Chapter 2.4.1 Arduino ...................................................................................................... 15
Chapter 2.4.2 Arduino IDE............................................................................................... 15
Chapter 2.4.3 considered of Arduino Libraries to GSM SIM900a .................................. 16
Chapter 2.4.5 Architecture of Smart Energy Meter.......................................................... 17
Chapter 3 Development ........................................................................................................... 18
Chapter 3.1 Projects Methodology: ...................................................................................... 18
Chapter 3.1.1 Dynamic System Development Method (DSDM) ..................................... 18
Chapter 3.1.2 Enhanced Waterfall .................................................................................... 20
Chapter 3.1.3 Spiral model ............................................................................................... 21
Chapter 3.1.4 Selection of methodology: ......................................................................... 22
Chapter 3.2 Dynamic System Development Method (DSDM) ........................................... 22
Chapter 3.2.1 MOSCOW prioritization............................................................................ 22
Chapter 3.2.2 The Project Plan: ........................................................................................ 22
Chapter 3.2.3 Work Break Down Structure ..................................................................... 23
Chapter 3.2.4 Gant Chart .................................................................................................. 25
Chapter 4 Code ........................................................................................................................ 26
Chapter 4.1.1 Declaration..................................................................................................... 26
Chapter 4.1.2 Setup function ................................................................................................ 26
Chapter 4.1.3 Interrupt function ........................................................................................... 27
Chapter 4.1.4 Loop function ................................................................................................ 28
Chapter 4.1.5 SendMessage function ................................................................................... 29
Chapter 5.1 Test Cases ......................................................................................................... 30
Chapter 5.1.1 Test Case 1 ................................................................................................. 30
Chapter 5.1.2 Test Case 2 ................................................................................................. 31
Chapter 5.1.3 Test Case 3 ................................................................................................. 32
Chapter 5.1.4 Test Case 4 ................................................................................................. 33
Chapter 5.1.5 Test Case 5 ................................................................................................. 35
Chapter 1 – Introduction
Chapter 1.1 objective of this chapter:
The objective of this chapter is to provide the overview and total idea of the project
“Smart Electric Energy Meter using Arduino”. It also provides the core concept of the
project and to introduce the problem background as planned. This chapter helps to
initiate the project by introducing different project aspects:
1. Project background
2. Current scenario
3. Problem statement and motivation
4. Approaches taken
5. Project as a solution
6. Aims and objectives
7. Project plan
• Meter reading and other related task like bill payment and line cut system are
performed by many staffs. i.e. large number of employees are required.
• Billing errors due to careless of staff (human errors).
• In context of Nepal (meter reading is carried out in once in 3 months due to
road condition and situation of place. So, it creates a lot of problems to
consumers) source: NEA https://www.nea.org.np
Case Study: Digital tech addressing Brazil’s power theft crisis. Rising incident of
electricity theft in Brazil was costing its government billons in lost revenue. On
average, 8% of energy in Brazil was stolen from grid each year, reaching a staggering
40% in some areas.
Solution: Siemens used innovation Smart Meter software to access, collect and
process data from meters. Integration the platform with the billing and management
system to ensure efficient energy billing to users.
Overview of project
k. Bowya had a purpose a GSM based smart energy meter. On this project’s information of
analog meter is send through SMS using GSM modem. On initial phase of this projects the
development phase is carried out in virtual simulation on proteus software. After completing
virtual simulator, hardware component is design and implemented it. Hardware component
used in this project are energy meter, optocoupler which is used to connect Arduino and energy
meter, Arduino, GSM shield, circuit board and bulb(load).
Finding from the project
• Easy applicable in daily life for end user because GSM Modem easily push notification
to user at any time.
• The features like relay control bulb, SMS alert notification are impressive and
workable.
• Projects development phase is carried out in both hardware and software.
Analysis of the project
GSM based smart meter reading is best way to implemented on client side. Both hardware and
simulation phase are carried out in this project. Optocoupler is used to communicate Arduino
and analog meter. Relay is used to control bulb or load. If user didn’t pay bill or don’t recharge
meter reading instantly energy meter will cut off.
Chapter 2.2.2 Smart Energy Meter with Reading Indication using GSM
Overview of project
M. leelavathin had a purpose the smart energy meter with reading indication using GSM. It is
developed to decrease the electric consumption bill by providing the energy meter reading to
the user by an alert SMS at certain days. the reading from electric analog meter data is send
through end user by GSM module using SMS services. This project is based on both customer
and server side. Using WIFI module sending meter information to sever side and control the
consumption of electricity and can easily cut the utility by using relay. Some of the pros and
cons of this projects are as follows:
Finding from the project
• The features of smart energy meter are based on both client and server side.
• Features like smart notification, wireless and server connection with load cut off are
workable.
• Features like SMS service using GSM modem is practicable and more reliable.
Analysis from Project
the features like server connection, database details and GSM are well managed. So, this project
gives an idea of both client and server connection. This program will only run if the meter is
recharge. Current consumption price is also set in this project.
Chapter 2.2.3 Arduino-Based Prepaid Energy Meter Using GSM
Overview of Project
U.A Rajput had a purpose Modeling of Arduino-Based Prepaid Energy Meter Using GSM
technology this projects or research paper is based on study of different country analog meter
reading system and necessary change to make it smart, workable and applicable on working
environment. Different problem statement faced by analog meter which can be improve by
implementation of smart energy meter. Some of the problem faced by analog meter reading are
meter reading error ratio is high, large number of employees are required, billing errors due to
careless of meter reading and human error. So, to solve these types of problems smart meter is
designed and implement by display information of meter reading in LCD display and
information of meter is send through SMS by GSM module. Some of pros and cons of this
projects are as follows:
Finding from the project
• Research of different county meter reading condition.
• Information of meter is display in LCD and display information at certain interval of
time on user by SMS services.
• Used optocoupler for meter reading pulse in Arduino. Which make meter reading error
ratio in low.
Analysis from Project
LCD display is used in this project to interact with user. It displays units and balance. User
need to recharge the system using GSM SMS. If user doesn’t pay bill amount it will alert user
and further line will cut. To cut electricity relay is used.
1. Feasibility study: During this stage of the project, the feasibility of the project
is examined. Gathering research for the current projects in this method is suited
or not. The most important techniques used in this phase are the research
gathering and using this methodology related project can be easier or not.
2. Business study: In this phase the overall business study of the desired system
is done. The requirement of the business is specified on a leveling method.
After it, the basic framework layout or prototype of the desire system is
prepared. The development portion or system architecture is done by using
Rapid Application Development (RAD), as on this process the prioritization of
work (MOSCOW principle) also separated with highly important to low
important. Moscow prioritization priorities are set as M- must have requirements
S - Should have if possible, C - Could have but not critical W - Won’t have this
time, but potentially later.
3. Functional model iteration: this model consists of models and functioning
prototype. Mention two things are key techniques within this project or in this
stage. The developed prototype is review again and again. Every review testing
is done. The prototype is improved through demonstrating the clients or the
user of the projects.
4. Design and build iteration: It this phase, focus identifies functional and non-
functional requirements that need to be implement on system and designed it.
Identified the functional requirement which is need to the end user and build
iteration the tested system is handed over to the next phase.
5. Implementation: In this stage, the pre-design system is installing and tested.
According to Goldman and Rawle’s this phase is cited as pilot test where
problems can be determined, corrected and corrections can be made to the
project plan for future works. If end user wants some non-functional
requirement to be added. We can move on development phase to design and
implement the system if possible. End user can easily approve the tested
system for implementation. Further guidelines of end user system can be
modified.
Advantages of DSDM:
1. Provide a technique-independent process.
2. Flexible in terms of requirement evolution.
3. Incorporates stakeholders into the development process.
4. Strict time and budget adherence.
Disadvantage of the DSDM:
1. Focus on RAD can lead to decrease in code robustness
2. Involves progressive development of requirements.
3. Required significant user involvement.
Chapter 3.1.2 Enhanced Waterfall
Waterfall model describes a development method that is linear and sequential. Waterfall
development has distinct goals for each phase of development. On this methodology, once a
phase of development is completed, the development proceeds to the next phase and there is
no turning back. (Rouse, 2007)
Advantages of Waterfall:
1. Process and result are well documented.
2. Works well for small projects and predefined requirement projects.
3. Easy to understand and implement.
4. Process and result are well documented.
Disadvantages of waterfall:
1. It is very difficult to estimate time for each phase of development process.
2. Not a good model for complex and undefined projects which requirement are
at moderate to change.
3. Idealized, doesn’t match reality well
Chapter 3.1.3 Spiral model
The spiral model is like iterative model with more emphases placed on risk analysis. The
development phase of this model is planning, design, build and test phase over and over with
risk analysis. The spiral model is typically used for large projects. A software projects
repeatedly passes through these phases in iterations. The baseline spiral, starting in the planning
phase, requirement is gathered during the planning phase. Risk analysis phase identify risk and
gives alternative solution, along with testing at the end of the phase. The evaluate phase allow
to evaluate the output of the project to date before the projects to the next spiral. (Guru99,
2017)
Advantages:
1. High amount of risk analysis.
2. Good for large and mission-critical projects.
3. Software is produced early in the software life cycle.
Disadvantages:
1. Can be a costly model to use.
2. Risk analysis requires highly specific expertise.
3. Doesn’t work well for smaller projects.
Chapter 3.1.4 Selection of methodology:
To generate a successful working framework on this project different methodology
were discussed. Among them Dynamic System Development Method (DSDM) is feasible,
implementable and easier with extra features of rapid application development (RAD). On my
projects, there is not any fixed approach. It means end products can be change when problem
arrived. On DSDM methodology time is fixed, resource is fixed but requirement is allowed to
change when any problem arise. On waterfall methodology product need to pre-define before
projects start. This project is about IOT projects on “Smart energy meter”. End products can
be change as end user want or problem can arise on hardware components. DSDM method will
be easier than waterfall method on this project.
DSDM method life cycle is divided into 5 phases. They are clearly described above its scope
and areas. It’s enough to clear those boundaries and criteria and also provide the clear-cut
concept of implemented framework or prototype. In my projects all planning and requirements
are cleared but it can be change as required. So, I will follow the step of DSDM methodology
for my project.
Chapter 3.2 Dynamic System Development Method (DSDM)
Planning the project using Dynamic System Development Method (DSDM)
Chapter 3.2.1 MOSCOW prioritization
M - Must have requirements S - Should have if possible, C - Could have but not critical W -
Won’t have this time, but potentially later
Must have should have could have won’t have this time
MO1: user need to SO1: Display the CO1: plot the WO1: display
get information of details information graph of current multiple meter
analog meter of Analog Meter used of certain reading on a same
through the Reading in Arduino days used. display.
message. Serial monitor.
SO2: user also can CO2: Give alert to Wo2: send data of
send message to user to pay current meter reading
get detail of energy or cut the network. through WIFI
meter reading.
Char incomingbyte helps to store incomming SMS in char and used for further communcation
between Arduino and GSM. After storing incomming SMS in char again storing it in string
inputstring. Decelaration of pulse in 2( int pusle = 2) which means connection of analog meter
anode wire in digital pin 2 of arduino. Reason to connect in digital pin 2 is interrupt of arduino
UNO board can be configured only in 2 and 3 pin. When led of analog meter will blink counter
integer will count it and display it in serial monitor of arduino. Integer price will count each
pulse price and display iy in serial monitor of arduno.
Connection of GSM SIM900a with arduino. Myserial is declared as SIM900a and Arduino
connection of decleration portion. While myserial is available then connection will be tested
by using AT command. AT command is used for testing and communcation between arduino
and GSM modem. While testing is true then on Arduino Serial monitor it will display
Connected. “AT+CMGF=1” command is used to set GSM into SMS mode.
“AT+CMGL=\”REC UNREAD\”” command is used to read all unread message.
When incoming SMS is stored in string inputstring display it in Serial monitor of Arduino.
Stored inputstring or user SMS is change into uppercase. Checking if inputstring is equal to
“METER” or not if statement is true then sendmessage function is called. “AT+CMGDA”
command is used to delete all SMS of SIM card. SIM card will store only 30 SMS only. If
SMS exceed then it will show error. Storing inputstring into null. Newly SMS will only store
in inputstring.
Chapter 4.1.5 SendMessage function
sendmessage function will be called when inputstring is equal to “METER”
“AT+CMGF=1” command of GSM is used to set GSM in SMS setup mode. AT is used to
check the interaction between arduino and GSM module. “AT+CMGS” is used to set phone
number to send SMS. User will get SMS of (“Dear Customer, Your Meter pulse (current
pulse) and its price (current pulse price”). Information of analog meter reading is shared or
exchange by using SMS service to user. To end function and using ASCII code of char(26)
which is shown in below diagram.
Chapter 5.1 Test Cases
Chapter 5.1.1 Test Case 1
Test Case 01
Expected Results When Load is given on Analog meter and pulse will
counted and display it in Serial monitor
Actual Results When load is on the pulse of analog meter is started to
count and display it in Serial Monitor of Arduino
Analysis Pulse will count on Serial Monitor of Arduino if LED of
analog meter will blink.
Further Notes (If
any)
Objective Send SMS from phone and display it in serial monitor using
GSM SIM900a
Expected Results Sending SMS from phone and display it in Serial monitor of
Arduino
Actual Results Arduino display the user input which is SMS.
Analysis Using GSM SIM900a user can send SMS to Arduino board
and display it in Serial monitor
Further Notes (If
any)
Expected Results User need to send SMS to Smart meter and it will again
send SMS to user about the current information of user. In
initial stage meter reading and price will be zero.
Actual Results Information of Smart meter is sent to user when user send
SMS to smart meter.
Analysis