[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Distant powering using device local control (difficult to
describe!)
- Subject: Re: Distant powering using device local control
(difficult to describe!)
- From: "noughtomate" <balraj_jassal@xxxxxxxxxxx>
- Date: Tue, 21 Mar 2006 15:47:34 -0000
Thanks for the ideas.
Ok, I'll own up :
- Device A : Synology DS-101g+ NAS server
- Device B : Netgear WiFi access point
- Device C : Belkin WiFi bridge to Ethernet
So, on pressing the NAS local power up, I want everything else to
power up.
I've pretty much limited my world to X10 at the moment so I have no
idea about Wall Warts, relays and current sensors. Are there any
dumbo-newcomer websites ?
Cheers
--- In ukha_d@xxxxxxx, "Tim Hawes" <timsyahoo@...> wrote:
>
> Replied at the bottom:-)
> On 3/21/06, noughtomate <balraj_jassal@...> wrote:
> > Hi,
> >
> > (A lengthy read, but your patience is appreciated!)
> >
> > I've got a dilemma here, which I don't think can necessarily be
> > solved using X10.
> >
> > I have three devices (say A, B, and C) which I want to ALL power
on
> > using the device A's actual local device power switch. I could
> > choose to leave all the devices permanetly on, but I'm trying to
be
> > eco-friendly and keep my power consumption down!
> >
> > Here's the situation :
> > - Device A and B are located next to each other.
> > - Device C is situated away from Devices A and B. I want this
to be
> > powered on when devices A and B are on
> > - Device A should only really be powered on using local
control, as
> > opposed to mains power control (i.e. X10 is not an option)
> > - I have a Comfort alarm/HA system, which could be harnessed to
> > implement this solution
> >
> > The only way I can think of doing this is :
> > - A is plugged into the Master socket of a Master/Slave multi-
socket
> > - B is plugged into the Slave socket of the Master/Slave
multisocket
>
> Now instead of an X10 module plugged in for device C, plug in a low
> voltage, low current wall-wart and wire the output to the coil of a
> relay. When A comes on and B is turned on, the wall wart will be
> turned on too. That closes the contact on the relay whcih you can
then
> wire to Comfort. When Comfort sees the contact closed it can then
> issue the "on" signal as before.
>
> If you don't think X10 is reliable enough for the "send from
Comfort"
> to be received you could direct wire the contact side of the relay
to
> a mains socket to switch the power directly for device C. If you do
> this then check component rating carefully for compatibility, and
> running the 12V a long distance is probabably safer than wiring
mains
> back to the lcoation of devices A+B (I hope that bit made sense).
>
> There's all sorts of other permutations possible depending on what
> other hardware and software you have (e.g. NetIOM, WebBrick, xAP,
xPL
> etc.) but how does that sound for starters?
>
> HTH,
>
> Tim.
> (p.s. is device C a wireless access point? if so, and if you
already
> have Cat5 from device A/B to C then think about using a
> power-over-ethernet kit, either a "proper" one or DIY
version to
send
> the device's power down the same length of Cat5 as the Ethernet
> packets. That way, you can use your master-slave power strip and
> switch the device C PSU directly, and local to A/B)
>
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|