<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
     >
  <channel>
    <title>Temporal Anomaly</title>
    <link>http://www.temporalanomaly.com/blog</link>
    <description>Automating our house and other random stuff</description>
    <pubDate>Sun, 20 May 2012 14:40:18 GMT</pubDate>
    <generator>Blogofile</generator>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>Solving More X10 Problems</title>
      <link>http://www.temporalanomaly.com/blog/2011/04/09/solving-more-x10-problems</link>
      <pubDate>Sat, 09 Apr 2011 20:56:22 BST</pubDate>
      <category><![CDATA[x10]]></category>
      <category><![CDATA[home automation]]></category>
      <category><![CDATA[rfxcom]]></category>
      <guid isPermaLink="true">http://www.temporalanomaly.com/blog/2011/04/09/solving-more-x10-problems</guid>
      <description>Solving More X10 Problems</description>
      <content:encoded><![CDATA[<p>In the previous post, I described two of the three significant X10
problems we had when setting up our home automation system.  This
post will cover the third problem, latency.</p>
<p>Although all our lights have conventional switches (well, momentary
switches in conventional locations), we use a lot of <a href="http://www.amazon.co.uk/gp/product/B00131NWNW?tag=temporalanoma-21&amp;m=A2UN5I0HGBX2YJ">X10 RF Remotes</a>
and <a href="http://www.amazon.co.uk/gp/product/B000MC8OP4?tag=temporalanoma-21&amp;m=A2UN5I0HGBX2YJ">X10 Motion Sensors</a> to trigger lights and other devices.
Initially, we used a <a href="http://www.amazon.co.uk/gp/product/B0018D1YX0?tag=temporalanoma-21">TM13U RF Transceiver Module</a> that receives the
X10 RF signals and converts them in to X10 powerline signals.  If we
stopped here and let the powerline signals trigger the X10 devices
directly this solution would probably be okay.  However, we wanted
computer control so we have another level of indirection.  The
powerline signals are then received by the <a href="http://www.amazon.co.uk/gp/product/B000KB02S4?tag=temporalanoma-21&amp;m=A2UN5I0HGBX2YJ">X10 CM12U Transceiver</a>
and sent to the house computer.  The computer then figures out how to
react to this signal and, if the action involves an X10 device, sends
another signal back to the CM12U where it is sent on the powerline.</p>
<p>The problem with this setup is that the X10 powerline is slow, so converting
the (fast) RF signal to a slow X10 signal to get it to the computer is
not very smart.</p>
<p>Additionally, RF devices repeat their signals which in turn get
repeated on the powerline.  While the repeats are going on, the
computer, responding to the first received signal, is instructing the
X10 Transceiver to transmit a command on the powerline.  This results
in frequent <a href="http://jvde.us/x10/x10_collisions.htm">collisions</a> leading to noticeable delays (and X10
powerline signalling isn't fast to begin with).</p>
<p>So, we purchased a <a href="http://www.wgldesigns.com/w800.html">W800 X10 RF Receiver</a> and gave up on the
<a href="http://www.amazon.co.uk/gp/product/B0018D1YX0?tag=temporalanoma-21">TM13U</a>.  Using the W800 serial port
receiver, the X10 RF could be read directly by the house computer.
This avoids the delay and the collisions of the X10 powerline signals
for the trigger and any triggered X10 commands.</p>
<p>The <a href="http://www.wgldesigns.com/w800.html">W800</a> was a solid piece of kit and worked
very reliably.  However, in the end, I replaced it with an
<a href="http://rfxcom.com/receivers.htm">RFXCOM RF Receiver</a> as that was able to receive additional protocols.
I expect I'll rave about RFXCOM products in future posts.</p>]]></content:encoded>
    </item>
  </channel>
</rss>

