RFXCOM RFXtrx433 Spécifications

Department of Electrical Engineering and Information TechnologyInstitute for Media TechnologyDistributed Multimodal Information Processing GroupProf.

Chapter 2.Related Work/Fundamentals2.1. Intelligent EnvironmentsIntelligent Environments (IE) are highly embedded, interactive spaces that aim to brin

Chapter 2. Related Work/Fundamentals 42.2. Home AutomationHome Automation (HA) describes the functionality provided by control systems to operate, sup

Chapter 2. Related Work/Fundamentals 5such as multimedia and entertainment features. However, these services play an important role indomestic life, c

Chapter 2. Related Work/Fundamentals 6and take a picture of him. However, such disturbances can be prevented by simulatingactivities in the house by s

Chapter 2. Related Work/Fundamentals 7two actuators. Connections are unidirectional, which means that actuators cannot send signalsbut just receive th

Chapter 2. Related Work/Fundamentals 8Security: Wireless systems are generally more insecure than comparable wired solutions. Thewireless media can be

Chapter 2. Related Work/Fundamentals 9control of home appliances over the existing power grid. X10-based devices are inexpensive andeasy to install an

Chapter 2. Related Work/Fundamentals 10ing machines, involving more complex controls. Other HA systems usually can only switch thesedevices on or off.

Chapter 2. Related Work/Fundamentals 11ZigBeeZigBee is a specification for a suite of high level communication protocols based on IEEE802.15.4 [14]: A

Chapter 2. Related Work/Fundamentals 12HomeEasyHomeEasy (HE) is a simple wireless home automation system produced by the British companyCH Byron5. It

Author: Philip ParschAddress:Matriculation Number:Professor: Prof. Dr.-Ing. Eckehard SteinbachAdvisor: Dipl.-Ing. Luis RoalterProf. Dr. Matthias Kranz

Chapter 2. Related Work/Fundamentals 13connected until the memory is cleared by a manual reset. If the memory was full, connection willfail.Data is tr

Chapter 2. Related Work/Fundamentals 14UKEU980 320 980320275275 1320275"1""0"Figure 2.6.: The bit timings of the UK and EU protoco

Chapter 2. Related Work/Fundamentals 15There are two different types of devices: The classic system, which uses manual address selectionand a newer sys

Chapter 2. Related Work/Fundamentals 16systems, above all to Asian products, where this IC is widely used due its low cost. This makesit possible to u

Chapter 2. Related Work/Fundamentals 17Input Vss: „00” Input Vcc: „11” Input Float: „01” Sync: „0” Figure 2.11.: All possible bit combinations.

Chapter 2. Related Work/Fundamentals 18HomeEasy Intertechno X10 EnOcean ZigBee KNXMedium RF 433 MHz RF 433 MHz PLC, RF 433 MHz RF 868 MHz RF2.4 GHz TP

Chapter 2. Related Work/Fundamentals 192.3. Home Automation GatewaysA gateway is a linking device between two or more different network technologies. I

Chapter 2. Related Work/Fundamentals 20Figure 2.12.: Three different gateways: RFXtrx433, TellStick and CUL.RFXCOM RFXtrx4338: USB transceiver for 433

Chapter 2. Related Work/Fundamentals 21data between its interfaces, for example USB to SPI. Due to the integrated WLAN module,it can be accessed and c

Chapter 2. Related Work/Fundamentals 222.4. MiddlewareMiddleware describes software that facilitates data exchange between applications within the sam

Department of Electrical Engineering and Information TechnologyInstitute for Media TechnologyDistributed Multimodal Information Processing GroupProf.

Chapter 2. Related Work/Fundamentals 23mBS Smart Home11is a platform-independent, Java-based framework, based on the OSGimiddleware. It is optimized f

Chapter 2. Related Work/Fundamentals 24The philosophical goals of ROS can be outlined as13:• Peer-to-peer topology avoids a central communication serv

Chapter 2. Related Work/Fundamentals 25Services are for communication between two nodes, whereas topics are for many-to-many com-munication. Nodes can

Chapter 2. Related Work/Fundamentals 26There exist further useful tools and functions:Logging and Playback: ROS supports two different mechanisms for l

Chapter 3.ConceptThis chapter covers basic concepts and ideas about the integration of Home Automation (HA)components in Intelligent Environments (IE)

Chapter 3. Concept 28These modules can only be used as a whole; no direct intervention is possible allowing communi-cation only before or after the mo

Chapter 3. Concept 293.2. HardwareMany different HA systems are available on the market, but in this work only two of them areconsidered: HomeEasy (HE)

Chapter 3. Concept 30The device manager node connects HA protocols with a set of data, which contains the mostimportant information about the device.

Chapter 3. Concept 31gateway_driverwlanusbdatabasedevicemanagerprotocol datadevicelistvisualization &namespacen/devicelistHardware Protocol Device

Chapter 3. Concept 32gateway_driverdevice_managerprotocoltype: ITIT 000AA8data: 000AA8name: "table_light"id: 12description: "light on m

KurzfassungIn der Kurzfassung der Arbeit werden auf maximal einer Seite die Hintergründe, Motivation,Aufgabenstellung und Lösungsansätze und die die E

Chapter 3. Concept 33The assignment in different structures makes certain assumptions: On the one hand, transmittersdo not have a state, which correspo

Chapter 3. Concept 34low range and the range of the gateway is limited as well. The use of various gateways enables thecontrol of larger systems and t

Chapter 3. Concept 35feature was not implemented. Nevertheless, it can easily be set up as another node on top of thesoftware stack.

Chapter 4.ImplementationThis chapter deals with the implementation of the concepts as presented in the chapter 3.4.1. GatewayThere are many different s

Chapter 4. Implementation 37XMEGAexpansion portFT232RN171RFM22BUSART433MHzWLANUSBSPI 3 USART 22 I/O-PinsPower+5VDCRTCusb-serial bridgeSPIUSARTFigure 4

Chapter 4. Implementation 38ISRhimedlow433Mhz reception, time controlUSART, SPI receptionhelping functions, RTCdata transmission, corenormalpriorityfa

Chapter 4. Implementation 39Figure 4.4.: The WifiCtrl on the left and the MiniCtrl without its antenna on the right. Bothmodels were generated by eagle

Chapter 4. Implementation 404.1.3. USB-serial-bridge ReplacementThe USB-serial-bridge FT232RL was initially selected because it can easily be integrat

Chapter 4. Implementation 41Another drawback of using the internal USB hardware, is the high memory use of almost 2 kBRAM and 10 kB ROM. The big ATXMe

Chapter 4. Implementation 42RFM22B is a low-cost transceiver with a large functional range. Basically, it consists of the ICSI4432 from SiLabs with a

AbstractIn the abstract, on a maximum of one page, the background, motivation, problem defition andpursued solution strategy are summarized.The abstrac

Chapter 4. Implementation 43result, not all data can be obtained and a compromise must be made, whether weak or strongsignals are preferred. In this w

Chapter 4. Implementation 44Figure 4.9.: Different data streams recorded with the scanalogic 2 logic analyser. The blue traceis the reference data rece

Chapter 4. Implementation 45time between now and the last call are measured to get the duration of each level. These timesare then compared with a tab

Chapter 4. Implementation 46Optimizations: The overall performance increased because of small changes in the structure andreprogramming of time consum

Chapter 4. Implementation 474.2. Software BasicsThe next sections cover the implementation of the three ROS Nodes: gateway driver, devicemanager and v

Chapter 4. Implementation 48Currently, only the gateways MiniCtrl and WifiCtrl are supported, but more gateways can beadded because the software provid

Chapter 4. Implementation 49come from the interface converter service or the "send usb" and "send wlan"-command.Raw output: Emits

Chapter 4. Implementation 50the RFM22B, the output streams are sometimes fragmented during CPU intensive tasks, such asthe reception of HA protocols.

Chapter 4. Implementation 51device manageraddremovechangeprotocol outputserviceprotocol inputreceiver/senderget set device_listswitchreceiver/sendersa

Chapter 4. Implementation 52by the "switch sender/receiver"-services and topics. However, if the state was changed bydirect manipulation via

ContentsContents vi1. Introduction 11.1. Motivation, Goals and possible Challenges . . . . . . . . . . . . . . . . . . . . . 11.2. Outline . . . . . .

Chapter 4. Implementation 53other thread is ready to exchange data. As a result, they are only suitable for large data transfers,such as the device li

Chapter 4. Implementation 54device ID to optimize the seek time. When accessing the database with those keys, the device IDis first fetched from the co

Chapter 4. Implementation 55HE 1 IT 1HE 1HE 2IT 1HE 1HE 2IT 1IT 2IT 3receiver sender receiver sender senderreceivernetwork 1 network 2 network 3Figure

Chapter 4. Implementation 56MainWindow: The MainWindow is the graphical framework in which the two previously men-tioned classes are embedded. It cont

Chapter 4. Implementation 57Switch receiver/sender: These services provide similar functionality as the "switch re-ceiver/sender"-services f

Chapter 4. Implementation 58device managerrosnodemainrosvisualizationthread 1 thread 2scene menuvisualizationmenuMainWindow XMLdatabaseFigure 4.18.:

Chapter 4. Implementation 59Figure 4.19.: The MainWindow displaying the start menu.manager node, the import function can either replace or merge the i

Chapter 4. Implementation 60Figure 4.20.: The receiver dialog on the left and the transmitter dialog on the right.4.5.2. Visualization MenuThe visuali

Chapter 4. Implementation 61Figure 4.21.: The visualization menu showing the database in receiver view.reason, the visualization node contains a local

Chapter 4. Implementation 62key1: value1key2: value2keyN: valueNuserQGraphicsViewQGraphicsScenereceiver itemsender itemQMultiHash <name, receiver i

CONTENTS vii4.1.4. Ceramic antenna for WLAN . . . . . . . . . . . . . . . . . . . . . . . . 414.1.5. Reprogramming of the RFM22B radio module . . . .

Chapter 4. Implementation 63Figure 4.23.: The scene menu with the example scene "dormitory", which contains three receivers:a light, a power

Chapter 4. Implementation 64The internal structure of the scene menu is similar to the structure of the visualization menu,except that no QHash contai

Chapter 5.EvaluationThis chapter deals with the evaluation of different parts of the system. Two test scenarios aredescribed, one office and one home env

Chapter 5. Evaluation 66The following sections describe the benchmark results for each node in more detail. Each publisher,subscriber and service was

Chapter 5. Evaluation 67gateway driverdevicemanagerdevice_changedvisualization &namespacesimulationnodeprotocol_out device_changed_nsswitch_device

Chapter 5. Evaluation 68Office HomeDeskPCDoorDoorWindow1 Window2PIRLightswitchRemoteContactswitchContactswitchLamp1Lamp2DeskPCRemoteBedContactswitchLi

Chapter 5. Evaluation 69IMAGE MISSINGTEXT MISSINGoffice homeday 1 day 2 day 1 day 2transmitter on off on off on off on offwindow contact 2 3 2 2 5 4 3 3door

Chapter 6.ConclusionThe goals of this work have been achieved: The presented soft- and hardware chain providesa unified framework between Intelligent E

Appendix A.Message, Topic and Service FilesA.1. Gateway DriverTopic NameCodeprotocol_output topicprotocol_input topicuint8 OTHER=0uint8 HE_EU=1uint8 H

Appendix A. Message, Topic and Service Files 72A.2. Device ManagerName Codereceiver_struct messageint32 i dstring namestring d e s c r i p t i o nint3

Chapter 1.IntroductionNew technologies provide increased comfort and quality in all areas of our lives. With homeand building automation, simple thing

Appendix A. Message, Topic and Service Files 73Name Codechange_receiver serviceint32 i d #if i d ==0, u se name i n s t e a dstring namereceiver_struc

Appendix A. Message, Topic and Service Files 74Name Codeset_devicelist servicebool mergebool d i s c a r d _ c o n f l i c t i n g _ d a t asender_str

Appendix A. Message, Topic and Service Files 75A.3. VisualizationName Codedevice_changed topicbool n e w_ st a te #true : on−code was s e n tstring s

Appendix B.Databases1 <? xml version ="1.0" encoding =" UTF -8"?>2 <!DOCTYPE d e v i c e s>3 <e le m en t s>4 &l

Appendix B. Databases 771 <? xml version ="1.0" encoding =" UTF -8"?>2 <!DOCTYPE s c e n e>3 < s c e n e l i s t>

WifiCtrl Reference CardCommunicationWifiCtrl can be controlled by simple ascii based commands via USB,WLAN, SPI and USART. Default communication port is

Command listset commandsset flush size X X = size (5..80)set flush time X X = time in µs (1k..10k)set separator X X = separator (ascii char)set format

List of Figures2.1. Possible applications at home. (Adopted from: http://www.lingg-janke.de/uploads/pics/eib-system-viele-funktionen.jpg . . . . . . .

LIST OF FIGURES 813.3. The software part of the communication chain, which contains three ROS Nodes.ROS serves as a link between the nodes connecting

LIST OF FIGURES 824.9. Different data streams recorded with the scanalogic 2 logic analyser. The bluetrace is the reference data received with a RF Lin

Chapter 1. Introduction 2Reuse: Already existing HA devices can be combined and reused. This reduces the installationtime as well as overall costs.Thi

LIST OF FIGURES 835.2. The latency of the complete system. Each time was measured 100 times and hasbeen averaged. . . . . . . . . . . . . . . . . . .

List of Tables2.1. The presented automation systems at a glance. . . . . . . . . . . . . . . . . . . 182.2. The differences between the presented gatew

List of AcronymsIE Intelligent EnvironmentHA Home AutomationIT InterTechnoHE HomeEasyHVAC Heating, Ventilation and Air ConditioningPLC Power Line Comm

Bibliography[1] M. Kranz, T. Linner, B. Ellmann, A. Bittner, and L. Roalter, “Robotic Service Cores for Am-bient Assisted Living,” in 4th Internationa

BIBLIOGRAPHY 87[12] KNX Association, KNX System Specifications, v3.0 ed., Jul. 2009.[13] A. Anders, “Energy for free - wireless technology without batt

BIBLIOGRAPHY 88Proceedings of the 5th ACM/IFIP/USENIX international conference on Middleware, pp. 397–416, Springer-Verlag New York, Inc., 2004.[25] M