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]

Fw: IR help - Xantech with Sky + with Russound


  • Subject: Fw: IR help - Xantech with Sky + with Russound
  • From: Gareth Cook <g@xxxxxxxxxx>
  • Date: Mon, 10 Oct 2005 16:05:35 +0100

I use Xantech Dist block with Buffalo receivers - works apart from my
interference I get which slows things downt. But 95% of the time, no
issues.

G.

Gareth Cook
Tools and Process Architect
IBM SWG Sales - Lotus Park, Staines, TW18 3AG
Office: +44 (0)1784 445166 - Mobile: +44 (0)7980 445166
AIM Chat : TheBoyG - MSN Chat : chat@xxxxxxx
email: g@xxxxxxx


----- Forwarded by Gareth Cook/UK/IBM on 10/10/2005 15:59 -----

Discussion
Main Topic

ukha_d@xxxxxxx
Today 14:43

.
Subject:
.
[ukha_d] IR help - Xantech with Sky + with Russound
.
Category:



Hi All,

Is anyone successfully using a xantech ir distribution block with Sky +
????

I also want to feed my xantech from the ir out of a Russound Cav6.6 -
anyone
ever done that?

All the Russound keypads have IR receivers. These signals are added
together
and spat out the back of the russound CaV amplifier into an mini-emitter.
I
have attached this to a xantech mini-reciever wired into a xantech 4-zone
in
10 emitter out distribution block and then out a xantech emitter on the
front of the sky+. Very flakey indeed - 1 in 10 remote presses works
although sky+ remote light registers them all.

Russound emitter to sky+ worked flawlessly on its own - putting the
xantech
in the middle buggers things up - (I have to do a 1 to many on the
russound
single out unfortunately hence the Xantech block).

Any advice etc ....

C







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.