The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: RE: Re: UKHA 2003 Update


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sensors / Switches / etc


  • To: ukha_d@xxxxxxx
  • Subject: Re: Sensors / Switches / etc
  • From: "patricklidstone" <patrick@xxxxxxx>
  • Date: Sun, 13 Apr 2003 19:34:43 -0000
  • Mailing-list: list ukha_d@xxxxxxx; contact ukha_d-owner@xxxxxxx
  • Reply-to: ukha_d@xxxxxxx

> - Are there any particular protocols people use ?
> Are people using XAP ?  I don't know anything
> about comfort etc, is there a standard ?

Yes, I'm using xAP. There is no "universal" standard for this
kind of
thing -- that's why we invented xAP :-)

Comfort is now xAP enabled.

> - What physical presentation would be required ?
> (RS232/RS485/Ethernet/X10/Other ?)

I use: RS232, 485 and Ethernet. Ethernet is favourite, but bumps up
the cost significantly. For simple activities I use PIC's with a
serial interface, and daisy chain them off an Ethernet enabled
controller. All the comms - serial and ethernet - is xAP compliant.

> - Are people intending to rewire between I/O
> points around the building ?  i.e. is something
> a single Cat5 run with I/O drops along it prohibitive
> because of the wiring ?

Hub based architecture which is also 802.11b/Bluetooth friendly is my
personal preference.

> - is there actually any widespread interest in something
> like this or are people actually happy with what they
> already have ?

I think there is interest... most of us have only just begun to
explore the possibilities offered by "pervasive connectivity"
between
devices (and I think my HA setup is reasonably cutting edge...)

Patrick



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.