<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.dbzoo.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://www.dbzoo.com/feed.php">
        <title>DBZoo</title>
        <description></description>
        <link>http://www.dbzoo.com/</link>
        <image rdf:resource="http://www.dbzoo.com/lib/images/favicon.ico" />
       <dc:date>2012-02-05T21:09:28+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/twitter?rev=1327698578&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/development?rev=1327617244&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/hah_plugboard_v2?rev=1327615170&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/pachube?rev=1327521717&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/xapflash?rev=1325778483&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/livebox?rev=1325445554&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/hah_hahnode?rev=1325442144&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.dbzoo.com/livebox/hah_i2c?rev=1325359890&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://www.dbzoo.com/lib/images/favicon.ico">
        <title>DBZoo</title>
        <link>http://www.dbzoo.com/</link>
        <url>http://www.dbzoo.com/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://www.dbzoo.com/livebox/twitter?rev=1327698578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-27T21:09:38+00:00</dc:date>
        <dc:creator>kevint</dc:creator>
        <title>livebox:twitter - [xAP Twitter] </title>
        <link>http://www.dbzoo.com/livebox/twitter?rev=1327698578&amp;do=diff</link>
        <description>This component allows you to tweet messages and control any xAP compliant device.  The Livebox being such a device.



Due to the way in which Twitter works, you are not able to enter the same tweet twice. To work around this, the xap-twitter daemon will DELETE the tweet once it has processed it.</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/development?rev=1327617244&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-26T22:34:04+00:00</dc:date>
        <dc:creator>karl</dc:creator>
        <title>livebox:development - [USB Filesystem support] Updated redundant external link and added reference to example on HAH</title>
        <link>http://www.dbzoo.com/livebox/development?rev=1327617244&amp;do=diff</link>
        <description>To extend the functionality of the inventel box you need more software.  This will require a MIPS cross compiler that can be executed on an external Development Linux server.

All linux development was done using Ubuntu 8.10 running inside VMWARE.



This is the toolchain that I have been using to perform all my development, including on the Home Automation Hub. It's based upon the Inventel toolchain with a few additional libraries thrown in for good measure.</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/hah_plugboard_v2?rev=1327615170&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-26T21:59:30+00:00</dc:date>
        <dc:creator>kevint</dc:creator>
        <title>livebox:hah_plugboard_v2 - [More samples] </title>
        <link>http://www.dbzoo.com/livebox/hah_plugboard_v2?rev=1327615170&amp;do=diff</link>
        <description>Whilst developing the HAH project I noticed there was an architectural component that would simplify the interactions between xAP compliant devices and daemons.  I call this the plug-board.



Consider the following use cases:

	*  Send a twitter message when the power being monitored with currentcost goes above 2kW
	*  If the temperature drops below 10C turn on a heater turning it off again when it reaches 12C
	*  When a currentcost/temperature event is seen, log it to pachube
	*  If Input 1 go…</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/pachube?rev=1327521717&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-25T20:01:57+00:00</dc:date>
        <dc:creator>kevint</dc:creator>
        <title>livebox:pachube - [Graphing] </title>
        <link>http://www.dbzoo.com/livebox/pachube?rev=1327521717&amp;do=diff</link>
        <description>So that the data being collected by the Livebox can be graphed, shared or used to trigger other real world events we use pachube - which people in the know pronounce 'pach-bay', but sound much cooler as 'pa-chu-be'.

The xap-pachube daemon has been designed to feed any xAP event that appears on the bus to pachube.  This means the Livebox hardware plus any other xAP compliant software/device that you may have running elsewhere on your network.</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/xapflash?rev=1325778483&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-05T15:48:03+00:00</dc:date>
        <dc:creator>brett</dc:creator>
        <title>livebox:xapflash - [Browser] </title>
        <link>http://www.dbzoo.com/livebox/xapflash?rev=1325778483&amp;do=diff</link>
        <description>Introduction


 The xAPFlash application, written by Kevin Hawkins et al, is a GUI front-end that allows you to control xAP compliant devices.

As the name suggests this is a FLASH based application targeted primarily at the O2 Joggler by OpenPeak. However, as this is in Flash it will run on many other supported platforms.</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/livebox?rev=1325445554&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-01T19:19:14+00:00</dc:date>
        <dc:creator>brett</dc:creator>
        <title>livebox:livebox - [Components] </title>
        <link>http://www.dbzoo.com/livebox/livebox?rev=1325445554&amp;do=diff</link>
        <description>I bought an Orange_Livebox off of eBay for the purpose of learning how to put together an embedded operating system.

For the money that I paid I've had countless hours of enjoyable Livebox hacking.

In the spiriting of giving, I've compiled my notes.  Some work is original; some is derived from other resources on the internet.</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/hah_hahnode?rev=1325442144&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-01T18:22:24+00:00</dc:date>
        <dc:creator>brett</dc:creator>
        <title>livebox:hah_hahnode - [Configuring the jeenodeApplet.lua] </title>
        <link>http://www.dbzoo.com/livebox/hah_hahnode?rev=1325442144&amp;do=diff</link>
        <description>JeeNodes are RF enabled AVR328P boards using the same development tools as the Arduino.  We love the JeeLabs weblog, jcw inspires us.

As JeeNodes are RF based, they make a great way to RF enable a variety of functions. Importantly, the JeeNodes support reliable bi-directional RF comms, so we can both send commands to the JeeNode and receive information from it.</description>
    </item>
    <item rdf:about="http://www.dbzoo.com/livebox/hah_i2c?rev=1325359890&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-31T19:31:30+00:00</dc:date>
        <dc:creator>brett</dc:creator>
        <title>livebox:hah_i2c - [Firmware debugging] </title>
        <link>http://www.dbzoo.com/livebox/hah_i2c?rev=1325359890&amp;do=diff</link>
        <description>The I2C bus can be used to extend the number of controllable devices that the HAH can access.  Using the PCF8574 chip (PPE) an additional 8 I/O pins are available.  Times this by up to 16 chips on the I2C bus and you have at your disposal 128 I/O channels; all accessible using the xAP protocol.




The HAH PCB exposes the I2C bus on a set of four pins. See the image below for the pinout detail.</description>
    </item>
</rdf:RDF>

