Re: X10 RF Link Command Translater

[nobody@xxxxxxxxxxxx (Dave Houston)]

Jeff,

OK. That's a lot like how the Insteon translator is programmed.

The PIC16F88 is pin compatible with the PIC16C54A used in the RR501 and you
can use code space for storage if needed.

"Jeff Volp" <JeffVolp@xxxxxxx> wrote:

>Hi Dave,
>
>I've been using tricks to make controllers user programmable for years.
>
>My thought was to use the toggle button as a program enable - maybe 2 quick
>presses.  That would open a window during which it would look for a complete
>RF command, followed by a X10 line transmission (the reason for choosing the
>RR501).  It would then store the translation for that pair.  Acceptance
>could be acknowledge by relay clicks.  This is sort of like the programmable
>remotes work.
>
>Jeff
>
>"Dave Houston" <nobody@xxxxxxxxxxxx> wrote in message
>news:43ae0a32.56156134@xxxxxxxxxxxxxxxx
>> Jeff,
>>
>> But how do you make it user programmable? The RR501 has no serial
>interface
>> and adding one would require isolation. In essence you end up with a CM15A
>> w/o an RF transmitter.
>>
>> "Jeff Volp" <JeffVolp@xxxxxxx> wrote:
>>
>> >Hi Dave,
>> >
>> >I remember that capability in the BX24-AHT.  Most high-end controllers
>can
>> >do it with macros.  I'm wondering if there would be enough interest in a
>> >cheap revision to existing RR501s to make it worth the effort.  Of
>course,
>> >much of that work could be ported to the CM15A mod.
>> >
>> >Jeff
>> >
>> >"Dave Houston" <nobody@xxxxxxxxxxxx> wrote in message
>> >news:43acfbfe.52519929@xxxxxxxxxxxxxxxx
>> >> Jeff,
>> >>
>> >> What I did with the BX24-AHT and what I had planned to duplicate with
>the
>> >> CM15X was to allow users to determine the response to any RF command
>> >> (including those from X-10 security devices). The default action was to
>> >just
>> >> do a normal response but the user could select which housecodes to
>> >> transceive and do things like have an 'A1 ON' RF command trigger a
>totally
>> >> different PLC code (or macro). They could also do nothing for
>individual
>> >> codes like the extra codes sent by EagleEyes, etc.
>> >>
>> >> Also, with additional IR or RF receivers (of other frequencies) on an
>> >RS485
>> >> network you can get inputs from non-X10 devices. With other devices you
>> >> might transmit RF codes for ceiling fans, etc.
>> >>
>> >> There's really a lot of potential. I had envisioned it as a central
>> >> switchboard for HA.
>> >>
>> >> The BX24-AHT had a little less EEPROM left for this than the CM15A has
>> >> available and I was using it rather wastefully by allowing the 100
>custom
>> >> responses to contain 20 character strings. If the 8K EEPROM in the
>CM15A
>> >is
>> >> too small, you can replace it with up to 32K.
>> >>
>> >> "Jeff Volp" <JeffVolp@xxxxxxx> wrote:
>> >>
>> >> >Based on comments here and some personal experience, I've been
>thinking
>> >> >about creating a X10 RF Link Command Translator.
>> >> >
>> >> >Many of us have devices we would like to control with RF remotes, and
>> >other
>> >> >devices we would rather not have controlled accidentally.  Sometimes
>> >these
>> >> >devices span several housecodes.  While what I describe here is easily
>> >> >implemented in a high end controller, a PIC change to a RR501 could
>allow
>> >it
>> >> >to handle the translation.
>> >> >
>> >> >Basically, the user would select any one housecode for the RF link.
>The
>> >> >modified RR501 would then translate RF housecode-unit pairs to any
>other
>> >> >housecode-unit X10 line commands.  The RF link might also include a
>> >> >"security mode" where a 2 key input within a time window would be
>> >necessary
>> >> >to accept the command.
>> >> >
>> >> >Any thoughts on how useful something like this would be?
>> >> >
>> >> >Jeff
>> >
>>
>