Download A Cell Phone-Based Remote Home Control System

A Cell Phone-Based Remote Home
Control System
Adam Mohling – CprE
[email protected]
1
Issa Drame – EE
[email protected]
Chau Nguyen – EE
[email protected]
Faculty Advisor:
Client: ECpE Department
Ahmed E. Kamal, Professor
[email protected]
www.ece.iastate.edu
May 23, 2017
SDMay6-13
Presentation Outline










2
Problem statement
Operating environment
Intended users/uses
Assumptions & limitations
End product & other deliverables
Resources & schedules
Commercialization
Risks & risk management
Lessons learned
Closing summary & evaluation
May 23, 2017
SDMay6-13
List of Definitions




3
GSM – Global System for Mobile
communication
SMS – Short Message Service
MSDNAA – Microsoft Developers Network
Academic Alliance
M2M – Mobile to Mobile / Machine to Machine…
May 23, 2017
SDMay6-13
Problem Statement
Design a system that allows users,
upon authentication, to remotely
control and monitor multiple home
appliances using a cell phonebased interface.
4
May 23, 2017
SDMay6-13
General Approach (Proof of Concept)
The system will be microcontroller based and will
do the following:
 Have connectivity to a cellular network
 Accept commands from a cell phone
 Be able to decode (and issue) user commands
 Have the ability to interface with electrical
devices
5
May 23, 2017
SDMay6-13
Research Activities
The team researched the various components
of the system, including the following:
 Cellular modules
 Microcontroller
 Programming languages
 Interfacing with potential controlled devices
 Miscellaneous circuit components
6
May 23, 2017
SDMay6-13
Operating Environment
Two separate units:
 Cellular module and control unit will be
located indoors
 Cell phone from which the user will interact
with the system
7
May 23, 2017
SDMay6-13
Intended User(s) and Use(s)
Any group or individual who wish to have the
ability to control or check the status of an
electrical device from a remote location.
Feasible appliances:
Lights, thermostat, security system, garage
door, etc…
8
May 23, 2017
SDMay6-13
Assumptions





9
Dry environment (indoors)
Only electrical devices shall be controlled
by the system
A cellular signal shall be accessible in the
cellular module’s location
Users are familiar with text messaging
The individual installing the unit shall have
an electronics background
May 23, 2017
SDMay6-13
Limitations





10
A 120V power source will be available
Communication can only be established
through SMS messaging (text message)
Only electrically operable devices can be
controlled by the system
System will not operate in an extreme climate
This system will not perform in real time
May 23, 2017
SDMay6-13
End Product and Other Deliverables

System Components:
–
–
–
–
–

Other:
–
11
Cellular Phone
Cellular Module
Microcontroller
Software
Controlled Devices
–
Documentation
Project poster
May 23, 2017
SDMay6-13
Research Activities
The team researched the various components of the
system, including the following:
 Cellular modules
 GSM network communication
 Microcontroller
 Programming languages
 SMS messaging format
 Modem AT commands
 Interfacing with potential controlled devices
 Miscellaneous circuit components & designs
12
May 23, 2017
SDMay6-13
System Components





13
Cellular Phone
Cellular Module
Microcontroller
Software
Controlled Devices
May 23, 2017
SDMay6-13
Project in Action – Entire System
Controlled Devices…
Lamp
14
May 23, 2017
SDMay6-13
Fan
Thermostat
Approaches Considered – User
Communication


Tone Decoding (DTMF)
Text Messaging (SMS)
Technologies Selected: Text Message
Reasons for Selection:
 Allows user to verify and edit the message before sending to
ensure the command issued is the command requested
 Data is transmitted in binary, requires less hardware to
manipulate (as opposed to DTMF)
 Most commonly used in M2M technology
15
May 23, 2017
SDMay6-13
Approaches Considered – Cellular
Modules
Considered
 EE54 edge
 GM47/48
 GM28/29
Module Selected: GM28
Reasons for Selection:
 RS232 DB9 connector
 No kit necessary (~$600)
 Located coding examples
16
May 23, 2017
SDMay6-13
Approaches Considered –
Microcontrollers
Considered:
STK200 Features ($66)
STK300 Features ($85)
Freescale (Motorola) MC68HC11E9 Starter Kit Features ($99)
Philips 51 Plus Starter Kit Features ($95)
Microcontroller Selected: STK300 Starter Kit
Reasons for Selection:
 Most economical ($85)
 Largest amount of memory (128KB)
 RS232 connectivity
 Application Builder, AVR Studio, programmable in C Language
17
May 23, 2017
SDMay6-13
Approaches Considered –
Programming Languages


All the software developed for this project will be loaded into the
memory of the STK300 microcontroller.
The language must be supported by the STK300’s compiler
–
–
The STK300 compiler supports C and Assembly
Java and C++ considered because code can be converted to C
Assembly
C++
C
Java
Selected Programming Language : C Programming Language
Reasons for Selection:
 Vast amount of online resources
 Ease of development
 Team members have experience coding C
18
May 23, 2017
SDMay6-13
Controlled Devices
The following devices have been selected to be
controlled by the team for proof of concept:



19
Fan
Light
Digital thermostat
May 23, 2017
SDMay6-13
Design Activity – Fan Circuit
20
May 23, 2017
SDMay6-13
Design Constraints – Thermostat
21

Setting based on simulating
up/down push-button inputs

Current temperature determined
by decoding LCD data input
May 23, 2017
SDMay6-13
Design Constraints – Decoded LCD
Display
Green/Gray
Yellow/Blue
Blue/Grey
White/Blue
Brown/Grey
Blk/Gold
Blk/Green
White/Green
Black/Blue
1….....2…….3…4……5…….6
22
Scan direction
May 23, 2017
SDMay6-13
Implementation Activity


The serial I/O between the STK
and GM28 were conflicting.
Status detection circuit:
RD – output
for GM28
GM28 Female
1
–
–

Initially voltage detector
Redesigned into current detector
All other implementation activities
went according to plan
TD – input
for GM28
2
6
1
3
7
2
6
4
8
9
3
7
5
4
8
5
9
STK300
- Female
STK300
output
23
May 23, 2017
STK300
input
SDMay6-13
Testing and Modification
GM28
 Testing was performed using the Windows HyperTerminal application
STK300
 Simple programs were developed to manipulate the I/O pins and
voltages were measured for correctness
 Serial communication was tested using the Windows HyperTerminal
application
Circuits
 Circuits were developed using PSpice and then implemented in the lab
–
Unit Testing

Each circuit component will be tested for proper voltage levels prior to
connectivity to other components
Other
 Subjects from the general public were selected to test the end product
24
May 23, 2017
SDMay6-13
Reporting Schedule
25
May 23, 2017
SDMay6-13
Development Schedule
26
May 23, 2017
SDMay6-13
Personnel Resources
27
May 23, 2017
SDMay6-13
Financial Resources
28
May 23, 2017
SDMay6-13
Project Evaluation
Milestone

GM28 & STK300 communication
–
–

Text message retrieval and parsing
Text message sending
Fully met
Not met
STK300 & control devices
–
–
–
–
–
–
Status detection circuit design
Status detection circuit implementation
Control circuits
LCD decode matrix
Thermostat control
Software





29
Outcome
User authentication & password change
Fan
Light
Thermostat
Initialization of serial and I/O ports
May 23, 2017
Fully met
Partially met
Fully met
Partially met
Partially met
Fully met
Fully met
Fully met
Fully met
Fully met
SDMay6-13
Commercialization

Modifications to control unit
–
–

Create new software adapted for given product
Implement a commercially available standard bus
Modifications to existing commercial product
–
Hardware interface installation


30
Send installation team onsite to install product
Not feasible for small-scale development in a
single user household
May 23, 2017
SDMay6-13
Recommendations for Additional Work


Obtain permanent service from a cellular provider
Additional system implementation
–
Hardware


–
Software




31
Status detection
LCD matrix decoding
Sending of messages via GM28
Status detection software
Thermostat & LCD software
Continued system testing
May 23, 2017
SDMay6-13
Risk Management
The team planned for the following risks:
 Loss of a team member
–

Data loss
–

Alternative distributors
Destruction or loss of parts
–
32
Multiple storage locations
Part orders
–

Two team members per task
Reorder parts as quickly as possible
May 23, 2017
SDMay6-13
Lessons Learned
What went well

Team organization

Time management

Spread of effort

Equal contribution among team members
What did not go well

Delay of delivery of system components

Serial communication

Status detection circuit
What technical knowledge was gained

AT commands

Digital logic

Microcontroller knowledge

Use of online resource such as forums provided
a great deal of knowledge to the team
33
May 23, 2017
What non-technical knowledge was gained

Time management

Realization of efforts required for
documentation

Working on a professional project
What would be done differently if the
project was to be done again

Follow the schedule more closely

Order parts sooner

Work ahead
SDMay6-13
Acknowledgements
Special thanks to the following:
 Sony Ericsson for providing the team’s GM28
cellular module
 Kanda for providing the team’s STK300
microcontroller kit
 Professor Kamal for his continued support to
the team
34
May 23, 2017
SDMay6-13
Closing Summary
Although the team encountered many
obstacles during the development of this
project, the realization that devices can be
controlled from a remote location via a cell
phone interface makes this proof-of-concept
project a success. All team members
contributed equally to progress this project
as far as it did and all team members were
satisfied with the end result.
35
May 23, 2017
SDMay6-13
Questions?
Lamp
GM28
STK300
Text
Messages
36
May 23, 2017
Controlled Devices…
Any device with an
electrical interface
SDMay6-13
Fan
Thermostat