• Like
"Programming Manual for Smart Houses" by Genge Bela @ eLiberatica 2007
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

"Programming Manual for Smart Houses" by Genge Bela @ eLiberatica 2007

  • 173 views
Published

This is a presentation held at eLiberatica 2007. …

This is a presentation held at eLiberatica 2007.

http://www.eliberatica.ro/2007/

One of the biggest events of its kind in Eastern Europe, eLiberatica brings community leaders from around the world to discuss about the hottest topics in FLOSS movement, demonstrating the advantages of adopting, using and developing Open Source and Free Software solutions.

The eLiberatica organizational committee together with our speakers and guests, have graciously allowed media representatives and all attendees to photograph, videotape and otherwise record their sessions, on the condition that the photos, videos and recordings are licensed under the Creative Commons Share-Alike 3.0 License.

Published in Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
173
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
4
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Programming manualfor smart houses Genge Bela “Petru Maior” University, Tg. Mures consultant Intelligent Building Solutions
  • 2. What is a smart house?  Must have:  Sensors and control elements for monitoring and controlling physical equipments  Software modules that can take decisions based on data received from sensors  The human operator should not interfere in the decision process
  • 3. The main problem: multi-protocols for controlling diversed equipments Connection: - Ethernet - Firewire - USB - Lon - CAN - X10 - EIB - SCP/CEBus - ZigBee - iButton - RFID etc
  • 4. ESS (“Environmental Service System”) server architecture PEER = Mirror ofa physical equipment EXTERNAL APPLICATIONS Database XML SMS User connection functionality functionality functionality functionality Communication BUS Interface Interface Interface Interface Interface Interface PEER PEER PEER PEER PEER PEER Regulator Relay EMeter Regulator Relay Dimmer Interface Interface Monitor 1 Monitor n Interface Interface EQUIPMENTS EQUIPMENTS
  • 5. Levels of abstractisations Allows the manipulation of the exported PEER functionalities Functionalities Hides the details regarding Interface equipment functionality implementation PEER Hides the details regarding Interface the communication with the ”bridge” Monitor Transforms some of the standard protocols Interface (COM,USB,LPT,…) into signals“Bridge” to physical equipments Interface Physical equipment network
  • 6. ESS = Environmental Service System- Extensibility according to the controlled env. - Internet ESS Server User SOCKET func. Monitor X10 PEERs Monitor CANX10 – International communication standard based on electricalpower linesCAN – “Controller Area Network”, international communicationstandard based on a BUS similar to Ethernet
  • 7. ESS = Environmental Service System- Extensibility according to the user’s demands - ESS Server Send SMS Message SMS sending repport functionality Database configuration function Monitor and control User socket functionality PEERs Monitor and control Monitor Event script Allows the implementation of the following scenarios: -Activating the lights when a door opens -Unarming an area when introducing the correct PIN Physical Equipments -Starting a video camera on movement detection -Starting the heating system on by another event
  • 8. Easy to use protocol The architecture allows a simple and clear replacement of the basic user protocol module The implemented protocol was built on simplicity and clarity:  Request-response protocol  Parameter separator that is easy to parse Message examples:  User->ESS: (GET)(PEERS)(demon)(monitor)  ESS->User: (NEW)(PEERS)(demon)(monitor)(peer1)(peer2)...(peerN)
  • 9. System exampleMonitoring and controlling equipments connected via X10 X10 – International communication standard based on electrical power lines Lights Temperature sensors X10 interface X10 interface X10 interface X10 interface Movement sensors X10 interface X10 interface X10 interface X10 interface ESS Server Heaters Func. User SOCKET X10 interface X10 interface PEERs X10 interface X10 interface Door control Monitor X10 Standard X10 interface X10 interface COM/USB/LPT/… X10 interface X10 interface Smoke detectors Vent control “Bridge” St <-> X10 X10 interface X10 interface X10 interface X10 interface
  • 10. System exampleVideo cammeras controlled by movement Rotate camera Event script ESS Server User SOCKET Receive functionality Start images Recording PEERs Video Server Monitor Receive images Control camera: rotire,zoom,… Physical equipments Interface
  • 11. Moving towards the Open Source community  Opened sources:  ESS server  X10 equipment software and schematics  Benefits to developers:  Integrate own type of equipments  Develop new scenarios  Develop new functionality modules (e.g. GPS) or hardware modules (e.g. CEBus)  Develop a monitoring system using practically any communication protocol  Perspectives on the future:  Open the code for other integrated applications: Video, Replay, XML  Open the code for client applications: Standalone monitoring client, Mozilla XUL-based monitoring client
  • 12. Thanks for the attention! Genge Bela Contact: bgenge@upm.ro, bela.genge@ibs.ro Home Page: www.ibs.ro/~belaThe sources can be found at: http://www.ibs.ro/opensource