In the next weeks I will start experimenting with XBee and Arduino, to do some basic Domotica things.
- Base Station – The Base Station is a below 200 euro Netbook in low power mode, with the screen switched off. Connected to one of the USB ports is a XBee mudule
- XBee / Arduino module – Using serial communication between the two and running some of the shelf library to establish communication between the two
Devision of Roles
- XBee module – The XBee module will:
- Read analog sensors
- Check states on switches
- Send instructions to the Arduino module
- Manipulate analog and digital devices
- Arduino – Will:
- Receive instructions from XBee
- Report its state to XBee
- Do process intensive stuff that can be done locally. Like:
- Send a constant pulse-modulated signal to color-leds, to allow these leds to show any possible color
- Change state between one to another – For instance – make a transition on a dimmable light from one level of brightness to another
- xbee-arduino – Is [quote:] an Arduino library for communicating with XBees in API mode, with support for both Series 1 (802.15.4) and Series 2 (ZB Pro/ZNet).
- xbee-api – Is [quote:] a Java API for communication with XBee/XBee-Pro series 1 (802.15.4) and series 2 (ZNet 2.5 and ZB/ZigBee Pro) OEM RF Modules, in API mode.
Setup: Java, HotForestGreen, Mediators, Virtual Objects and Remote Objects
The libraries will be used as the communication layer between a Mediator that represents a specific solution and the actual hardware that makes that solution real.
As the XBee API offered is in Java, the XBee/Arduino/Real Objects Mediators created with this library will be in Java as well.
Using the HotForestGreen Java Framework, they will connect to a HotForestGreen Server and offer Virtual Objects (representing the real objects in a space) to be used anywhere else in the Application Cluster.
The main goal is to create simple to use objects that can be manipulated from any machine connected to the Application Cluster these Virtual Objects are part of.
Brief explanation of terms
- Mediators – Are software solutions which make it possible for two normally incompatible solutions to communicate to each other. A Mediator can mediate between software and hardware, offering the software a Virtual Object representing the Actual Object and deals with all protocols to make communication from Software to the Real Object and back seem immediate.
- Virtual Objects – Virtual Objects are Mediators, with a specific purpose and a very specific interface for a very specific set of solutions. They represent a Real Object and deals with the translation of actions and data between the Software using the Virtual Object and the Real Object you want to use in your solution.
- Real Objects – Real Objects can be Software or Hardware based Objects. They are the actual components doing the actual work.
- Remote Objects – Used in HotForestGreen Application Clusters. Represent the Virtual Objects on other computers or in other applications connected to our provider. The Remote Object in this case, represents the Virtual Object. Instead of dealing with complex instructions, the Remote Objects simply offers an interface over the Application Cluster to the Virtual Object and via the Virtual Object to the Real Object
- HotForestGreen Application Clusters – Are clusters of Distributed Software communicating over a (local) network to perform specific tasks. Application Clusters can include:
- Remote controls – Running on a SmartPhone, with which you can temperature or change light settings in a room and read the state of that room
- Local Smartness – Being very specific applications running in a room or a specific location and dealing with specific tasks like translating the state of a Virtual Object to the state of a Real Object and vice versa.