home automation

13
k.Vishnu prasanna [email protected] HOME-NETWORK REMOTE CONTROL

Upload: vishnu-kudumula

Post on 04-Jul-2015

84 views

Category:

Engineering


1 download

TRANSCRIPT

Page 1: Home automation

k.Vishnu [email protected]

HOME-NETWORK REMOTE CONTROL

Page 2: Home automation

INTRODUCTION

Objectives Home-Network Why Remote Control? Proposed Home Automation System

– X-10– GSM– Internet Protocol

Interfaces & Middleware Conclusion

Page 3: Home automation

OBJECTIVES

Develop a Home Automation Remote System

Use different inner and outer network technologies

Use devices that are easy to install

Use low-price materials and devices

Make it suitable for inexperienced users or even disabled people

Make it scalable for further add-ons

Manage multiple control points

Encourage standardization

Page 4: Home automation

HOME-NETWORK

Figure 1: The Home-Network

Page 5: Home automation

WHY REMOTE CONTROL?

Enables control from almost anywhere (more comfortable)

Instant alerts greatly increase security

Backup emergency control

Optimal for people with reduced mobility

It can be combined with local control to give higher flexibility.

The network hierarchy has been rapidly moving lower in the chain towards smaller and more personal devices (Canosa, 2001)

Page 6: Home automation

PROPOSED HOME AUTOMATION SYSTEM

Figure 2: Proposed Home Automation System

Page 7: Home automation

X-10

– Technique “Power Line Carrier” – Frame sent two times– Noise filter / Phase coupler– Up to 256 controlled devices

Figure 3: X-10 frame

Page 8: Home automation

GSM

Figure 4: GSM connection

– AT / AT+ commands – Serial connection– SMS– MMS– Dials

Page 9: Home automation

INTERNET PROTOCOL

Figure 5: Siemens UPnP

– Control Points – IP devices

IP cameras

– Web browsers– XML – Siemens UPnP Stack

Addressing Discovery (SSDP) Description (XML)

– Control (SOAP)– Eventing (GENA)– Presentation (HTML,WML)

Addressing

Discovery

Description

PresentationEventingControl

Page 10: Home automation

INTERFACES & MIDDLEWARE

Middleware– Standard compatible– Link technologies (translation)– Robust

User interfaces (Local & Remote)– Must follow Heuristic Evaluation (Molich and Nielsen 1990) – High usability

Good visibility of system status Match between system and real world

– Error prevention (minimize error messages)– Aesthetic and minimalist– Help

Page 11: Home automation

STATE DIAGRAMS

INTERNET ACCESS

ACTIVE REMOTE ACTION

PING SUCCESSFUL

LOGIN FAILURE

CONNECTIVITY TESTRESPONSES

PING IP

USE OF WEB INTERFACELOGIN()

LOGIN()LOGIN ERROR

ACTIVATE_SERVICE()

INITIAL ESTATE

ESTABLISH CONNECTION

SEND_PLC_COMMAND() / IP SERVICE

SERVER ACCESSED

BROWSER ACCESS

CONNECTIVITY FAILURE

CONTROLPOINT

DEVICE HOST

SERVICE DONE

NEW ESTATE

INTERFACE ERROR

Figure 6: Estate Diagrams

GSM ACCESS

REMOTE ACTION STARTED

GSM MODEM ACTIVE

GSM TEST

CALL GSM MODEM

X10_COMMAND()

INITIALESTATE

RECEIVESMS

MIDDLEWARE

SMS_TRANSLATION ()

CONNECTIVITY FAILURE

ACTION NOT REALIZED

LOCAL ACTION

CHANGE_STATUS()

SEND_STATUS() // UPDATE

MOBILE

X10 DEVICE

ERROR

SEND_STATUS() / ERROR

NEWESTATE

RESPONSE

RESPONSE

SERIAL PORT ACCESS

X10_COMMAND()

Page 12: Home automation

Conclusion

The E-home is coming quickly

Standards are not completely established

Remote Control is necessary for certain purposes

Developing low-price systems will accelerate the

process of turning our homes intelligent

The price of the “intelligence” in a house in

comparison with its “body”, is insignificant

Page 13: Home automation

Thanks!

Any question? – (Ask Slowly please)