At the end of the summer of 2008 we changed a small part of our garden. Somehow the plants just didn’t want to grow in this part of our garden; only weeds flourished well. So we covered the place with root canvas and put a layer of small stones on top of it. In the middle we put a fountain-like thing with a pump that pumps water over the sphere. And we put 3 spots around it to illuminate it in the dark.
However autumn followed quickly, so i never got the chance to automate this. Today i did.
First job was to get electricity available. Although there was a power cable near, i had to replace the upper part of the cable to be able to split the cable in the junction box. And of course, I wanted to control the pump and the lights with a couple of micro-modules.
In the left box on the photo there are a PLCBUS PLC 2267, a Xanura SAIX and the adapter for the halogen spots. Although the adapter should be suitable to be placed outside, i felt more comfortable with some extra protection against rain and other things that can trigger malfunction.
With the PLC2267 and Xanura SAIX i can control the halogen lights and the pump individually.
After putting all things together, ready to seal the boxes that contain the hardware, i remembered i had to program both the PLC2267 and Xanura SAIX… what now ?
Well..i preconfigured both devices in my Home Automation System, went outside with my Asus R2H, sat down by the box with the modules inside, pushed the programming button and used my website to program the modules 🙂
This week the ASUS R2H arrived that i bought from a domoticaforum member.
I’m going to test the R2H and see if it’s suitable as a second GUI to my Home Automation System, next to the Asus TOP that is on the wall in the livingroom.
Maybe the Asus can be placed somewhere on the 2nd floor, or in the bedroom.
The Asus consumes 16W idle on AC Power and is quite audible, compared to the Asus TOP. You can clearly hear the fan blowing out hot air out of the upper heat vent. Time will tell if it’s to annoying. If so, i can always use the R2H as travelling companion on holidays.
I stripped the R2H from a lot of additional (memory consuming) software that’s installed out of the box to make it a bit more lean.
Next thing on my todo-list is develop a small application that should make the Asus R2H function as Domotica Interface.
Only a subset of the functionality that is available on the ASUS TOP will be added to the GUI, cause i don’t want to spend to much time on it; let’s first see if the ASUS R2H is suitable for the task and if so, i can extend the GUI with what i want.
Today i finished the interface for my Siemens M20T. This interface handles all the low-level communication with the M20T:
- Initialization at startup for things like PIN code, Echo setting, SMS mode;
- Sending SMS;
- Receiving SMS notifications and reading the SMS;
- Deleting read SMS message from the message store.
The class i created for handling the communication with the M20T was derived from a special ‘Physical Interface’ class i created a long time ago when i was developing the basics for my Home Automation system. All classes that interface with hardware, whether it is PLCBUS, RFXCOM, X-10 or whatever, are derived from that class. That way i only have to develop the device-specific routines and when that part is finished, the new hardware is instantly and completely integrated with the rest of my system:
No need to do additional development to enable an SMS to trigger an event, store historical data in the database, or to have the information available in my Home Automation GUI that’s running on my ASUS TOP in the living room. It’s just like writing a HS Plugin 🙂 Last month i developed 2 new interfaces for new hardware this way.
The Siemens M20T will be moved to the place where lots of other Domotica hardware can be found, the fuse cabinet. There it will be attached to a Sollae EZL-400S, and occupy it’s 3rd port. The first 2 ports are going to be used by my X10 interface and my PLCBUS interface. Those last 2 interfaces are currently connected to 2 single port serial to Ethernet converters, but by connecting these 3 devices to a single multi-port serial to Ethernet converter i can save additional power usage.
Last week i bought a Siemens M20T. The Siemens M20 Terminal is a GSM900 Phase II voice, data, group 3 fax and SMS terminal device. This device has been on my wish list for a long time. Although i had the ability to send SMS by using Voipbuster, using a dedicated device like the Siemens M20 has always been my favorite. Last week the Siemens M20T arrived and yesterday i took some time to do some tests. After making a straight 1:1 RS232 cable and inserting the new arrived SIM, i connected the M20T to my PC and switched on the power adapter. The LED kept on blinking, where it should burn continuously. Of course, i had to enter the PIN code, so i started Hyperterminal and sent the appropriate command. So far so good.
Now it was time to test sending a SMS to my mobile phone. That wasn’t to hard, the command for sending a SMS is quite easy and human readable:
> TESTING 123<Ctrl+z>
It worked. One problem though; the mobile phone displayed an error message saying the message could not be displayed? 🙁 After some searching i found out that the text mode SMS i sent with the command above, is not supported by all mobile phones. However there’s another mode to send a SMS, called PDU mode. It involves a bit more work in encoding the SMS before it can be sent to the M20T, but i found enough documentation to send my first PDU-mode SMS after 2 hours. This worked well! 🙂
The command for sending a PDU mode SMS looks like this:
The text sent is no longer human readable, the phone number is hard to recognize, but who cares if it’s working, as long as the M20T and my mobile phone understand it, it’s fine by me..
This evening i’ve started to write an interface to my Home Automation software so that i can send SMS messages whenever interesting things happen in and around my house.