The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: EIB versus CBUS



by redundancy, I meant (eg) having sufficient PIR sensors to be sure
movements are picked-up ...


On 6 Oct 2007, at 11:44, Chris Hunter wrote:

> good question ... and I remember my conclusion better than the
> detail (!) ... but the main points were that Idratek has a free
> topology, has a good EPS & falls back to Reflex when Cortex goes
> down (eg: if 'XP has a fit, there's a power-cut, etc) ... and EIB
> is built like a tank (well, not quite) and has an open standard
> with multiple sources (ABB, Siemens, Philips, Merten, Jung, and
> umpteen more) ... ISTR there was something about the C-Bus & EIB
> topologies, too, but can't now remember why they should be
> different !   I'll dig into the diary to get more ... maybe this
> evening !
>
> Idratek also has things like multiple parallel PIR & digital input
> options, and a number of other features to help things run smoothly
> - eg: a good range on input & output devices, general
> affordability, so you can actually have redundancy, with sufficient
> sensors, a multi-purpose controller module, for special needs, a
> good intercom, etc - all of which are important, ISTM, because an
> underspecified set-up ain't going to work too well !
>
> just my view, in our situation, of course !!
>
> Chris
>
>
> On 6 Oct 2007, at 10:45, Kevin Hawkins wrote:
>
>> Hi Chris - what aspect were you referring to here ... and how does
>> EIB
>> and indeed your choice of  Idratek address the issue ?
>>
>> Just interested.....
>>
>>     K
>



[Non-text portions of this message have been removed]




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

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.