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: [OT] Anyone got a spare Gmail invitation ???


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

X10 control of CH and HW - Y plan confusion reigns...


  • Subject: X10 control of CH and HW - Y plan confusion reigns...
  • From: "LeeUKHA" <mailinglists@xxxxxxxxxxx>
  • Date: Sun, 10 Oct 2004 18:53:37 +0100


A while back when I bought my current home, I replaced the (rather
knackered) CH/HW timer with a new digital one. At the time I never really
understood the wiring, but it's been working fine for a couple of years so
I
guess it was OK.

However, now I'm attempting to control the CH and HW from the HA server...

After some googling I appear to have a standard Honeywell Y-plan set up
(?).
I can get the CH to fire by shorting out two links (live into CH request?)
on the timers backplate, which I'm guessing I can simulate by having an X10
appliance module feed 240V into that connection. But the HW I have a
problem
with, there appear to be two HW connections, one for "HW request"
and
another for "no HW request". I not sure I understand why this is,
but
shorting 240V in the MW request does not fire the boiler, when I thought it
ought to...

What am I missing here? Can this system be automated with two appliance
modules? Will the current leak that keeps power indicators lit (like on my
elecy blanket) cause problems? Why didn't I just put cat5 to the boiler?

Any suggestion gratefully accepted...
Lee

---
Outgoing mail is AVG certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.774 / Virus Database: 521 - Release Date: 07/10/2004




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.