Re: Wiring light switches...

["bensbarn2001" <ben_wilkinson@xxxxxxx>]

Paul,

I'd be amazed if the comfort/hv link contributes to any significant
delay.  The total time for a transaction is probably of the order of <= BR> 50ms, which nobody is going to detect.  The last time I looked at the =
X10 spec, it looked like the minimum execution time was 2/3 of a
second (can't remember exactly but it was close to this).  So
everything else is small compared with this.  You can walk a
surprisingly long way in this time.  Judicious sensor positioning (to =
trigger before you get into a room) or using info from other sensors
to work out what is happening can make things better, but more
complicated.

A variable you can control is the time that Comfort takes to trigger
a sensor.  This is a definable number for each sensor type.  It <= BR> allows removal of effects due to false triggers, or noise, but you
can set it very small if you don't care about these things.  As
others have said, sensor type and positioning makes a big difference
too.  The dual type (uwave and PIR) can usually be set to trigger on <= BR> uwave only which can be very sensitive.


Ben


ukha_d@y..., "psghome2002" <psghome@h...> wrote:
> Thanks Ken,
>
> I've set the schedule up in a similar way (using timers and only
> sending X10 on initial ON and OFF). I guess my problem is still the > delay in Comfort - RS232 - HV. I'll let you know how it goes when I > connect directly to HV (although re-wiring needed if I eventually
> change to this method - and it's only taken me 2 months so far!)
>
> Paul.
>
> --- In ukha_d@y..., "Kenneth Watt" <kennwatt@b...> wro= te:
> > Paul,
> >
> > I have all the PIRs connected directly to the HV expansion board,=
> IIRC
> > there are 10 PIRs connected and one pressure mat in terms of
> occupancy
> > detection and the schedule reads something like this from memory:=
> >
> > If
> >       Input Port D1 goes high
> >       And time is after sunset and befor= e sunrise
> >       And Flag XXXX is clear
> >       And timer PIR timer (for this PIR)= is not running
> > Then
> >       X10 A1: Lounge lamps On
> >       Set X10 device A1 directly to leve= l 32
> >       Load Timer PIR timer (for this PIR= ) with 2.30 and start
> > End if
> > If
> >       timer PIR timer (for this PIR) is = running
> > Then
> >       Stop timer PIR timer (for this PIR= )
> >       Load Timer PIR timer (for this PIR= ) with 2.30 and start
> > End if
> > If
> >       Input Port D1 goes high
> >       And time is after sunset and befor= e sunrise
> >       And Flag XXXX is set
> >       And timer PIR timer (for this PIR)= is not running
> > Then
> >       X10 A1: Lounge lamps On
> >       Set X10 device A1 directly to leve= l 20
> >       Load Timer PIR timer (for this PIR= ) with 2.30 and start
> > End if
> >
> > In this way you can control the level of lighting dependant on the
> flag
> > or, indeed, another X10 device, simply insert the "and X10 d= evice
> XXX is
> > on" or off instead of a flag.
> >
> > This also saves HV sending out X10 commands repeatedly by using a=
> timer,
> > so the commands are more accurate and tend to get through, in my =
> place,
> > I would reckon it works 99.9999999% of the time ;). By using the<= BR> > > dependant on the timer thing the way I do, HV sends no signal > unless
> > there is no movement detected for more than, in this case, two > minutes
> > thirty seconds and only then sends an OFF command. If the PIR is =
> tripped
> > while the timer is running then HV simply cancels the timer and <= BR> > restarts
> > it, loops and repeats until it detects no movement. Repeating the=
> ON
> > command seems a common mistake and if HV is trying to fire out > signals
> > repeatedly then this will cause huge delays due the traffic on th= e
> > powerline of X10 commands, this was designed to get around that <= BR> > problem.
> >
> > HTH
> >
> > K.
> >
> > > -----Original Message-----
> > > From: psghome2002 [mailto:psghome@h...]
> > > Sent: 18 July 2002 12:20
> > > To: ukha_d@xxxxxxx > > > Subject: [ukha_d] Re: Wiring light switches...
> > >
> > > Ken,
> > >
> > > What X10 command do you use - I've used the standard ON comm= and
> and
> > > the 'Set X10 device directly to' command. Both seem to take = the
> same
> > > amount of time.
> > >
> > > I've got a pretty big setup here and am limited by the numbe= r of
> > > zones or inputs to Comfort / HomeVision. I've currently got = 32
> > > Comfort zones active and am planning to connect my A/V matri= x
> > > switcher and mic mixer logic terminals to HV. That equals a = lot
> of
> > > inputs, more than I've got even with the expansion board > connected :(
> > >
> > > I was trying to keep the cost as low as I can (even then I'v= e
> spent
> > > way over =A315K so far!) and using Comfort for the dual purp= ose of
> > > alarm and lighting triggering is ideal (and it works well ap= art
> from
> > > the speed). However, I need to check exactly how long it tak= es
> > > Comfort to send the serial report to HV (no ACE in the loop = for
> > > this - a direct connection from Comfort to a second serial p= ort
> on
> > > HV).
> > >
> > > I'll try the direct PIR - HV input and see if this improves = the
> time.
> > >
> > > Cheers,
> > >
> > > Paul.
> > >
> > > --- In ukha_d@y..., "Kenneth Watt" <kennwatt@b.= ..> wrote:
> > > > Paul,
> > > >
> > > > I think your problem with response times could be down = to the
> way
> > > you
> > > > are getting HV to send the on command. I have PIRs conn= ected
> > > directly to
> > > > HV, no Comfort in the way or a PC, you walk into the ro= om and
> the
> > > lights
> > > > come on in well under a second, in fact it's almost > instantaneous,
> > > Phil
> > > > has seen this in action too, he can confirm this if he = reads
> it.
> > > >
> > > > In many rooms, such as my AV room or the bathroom, all = I need
> to
> > > do is
> > > > wave at the PIR and the lights come on. I have said bef= ore, I
> > > rarely
> > > > touch a light switch in the house, or an X10/momentary = switch,
> > > virtually
> > > > everything is either off a PIR or done by IR in some ca= ses.
> > > >
> > > > Having said that, I have noticed a huge difference betw= een
> > > different
> > > > PIRs and, additionally if HV is stuffed full of conditi= ons to
> > > check then
> > > > the response time drops. Also if you read the command t= o
> Comfort,
> > > then
> > > > to ACE and then to HV then, inevitably, there will be a= huge
> delay
> > > in
> > > > that and one I would not find acceptable never mind SWM= BO! ;)
> > > >
> > > > Not having Comfort (yet) I've never tried routing PIRs = through
> > > another
> > > > machine and, even if/when I install Comfort I would not=
choose
> to
> > > go
> > > > down that route simply due to the problems you describe= .
> > > >
> > > > K.
> > >
> > >
> > > ------------------------ Yahoo! Groups Sponsor
> > >
> > > For more information: http://www.automatedhome.co.uk
> > > Post message: ukha_d@xxxxxxx > > > Subscribe:  ukha_d-subscribe@xxxxxxx > > > Unsubscribe:  ukha_d-unsubscribe@xxxxxxx > > > List owner:  ukha_d-owner@xxxxxxx > > >
> > > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.c= om/info/terms/

For more information: http://www=
.automatedhome.co.uk 
Post message: ukha_d@xxxxxxx 
Subscribe:  ukha_d-subscribe@xxxxxxx 
Unsubscribe:  ukha_d-unsubscribe@xxxxxxx 
List owner:  ukha_d-owner@xxxxxxx

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.