Subject: From: Date:

Re: [ECS] PLC Interface overflow? Bruce Prager Tue, 4 Jul 2000 12:09:05 -0400

---

Look at visionic.com.  They offer a wireless motion sensor that is
pet-immune.  The receiver provides a contact closure output that ECS can
read (or can be read by your existing hardwire inputs of your alarm system).
I've been using them with 2 cats and the're great.  I'm running them into a
Gemini 9600 system that ECS monitors for sensor changes.
Note that the sensor will trip, then not trip again for 2-3 minutes.
Unfortunately,  that kind of timeout is fairly standard for most wireless
motion sensors.
Hardwired don't have the problem, but running the wires in my hours would
have been a nightmare.
Good Luck!
----- Original Message -----
From: "Lanter, Steven SB SNORC" <SL144457@MSXSOPC.SHELL.COM>
To: <ecs-list@netbloc.com>
Sent: Monday, July 03, 2000 1:00 PM
Subject: RE: [ECS] PLC Interface overflow?


> One thing I've found is that the MS-12A will only send an "on" command
upon
> first detecting motion and will not send another until after it has sent
an
> "off" command.  It appears the MS-13A will send "on" commands almost every
> time it detects motion -- I see "on" commands being sent within 15 seconds
> of each other.  Adjusting the delay time for sending the "off" command
does
> not appear to change the frequency of the thing sending "on" commands
(I've
> only tried two different delay settings).
>
> So I guess the 12A is better for managing overall X-10 traffic on the
> powerline, but if your system misses the single "on" command it sends . .
.
> well, then you'd go with the 13A's, but if you've got a bunch of them,
just
> imagine all the traffic and PLC collisions you'd have when you had more
than
> a couple of rooms occupied!!
>
> I don't know if the 12A is even available anymore.  All I see on the X-10
> website are 13A's and 14A's -- the only difference between the two that I
> see is the 14A is black (rather than white) and is waterproof (rather than
> not, of course).
>
> I got these as freebies also, last year from X-10.  I got 3 12A's and 6
> 13A's but have never utilized them in the system.  I've just played with
> them some to see how I could or would use them.  And White Out does work
to
> disable the dawn/dusk sensor!  I've done this to both the 12A's and the
> 13A's -- no more +1 codes get sent (even if you disable the feature on the
> 13A, rather than White Out the sensor, it still sends the +1 code -- it
just
> allows the sending of the primary code full time, day or night).
>
> If there was a way to adjust the 13A (and I guess there may be) so that it
> wouldn't send another "on" command unless, say, a full minute had passed
> since the last "on" command, then I guess it would be okay to have a bunch
> of these in the house.  Does anyone know how to do this?  Other than
> hardwired sensors, what other motion sensors are available?
>
> Steve
>
> > -----Original Message-----
> > From: Paul Fitch [SMTP:pfitchjr@bellsouth.net]
> > Sent: Saturday, July 01, 2000 8:56 PM
> > To: ecs-list@netbloc.com
> > Subject: Re: [ECS] PLC Interface overflow?
> >
> > While mining the Home Automation tips archive I came across a fast,
easy,
> > and
> > REVERSIBLE method of disabling the dawn/dusk sensor....White Out!!!
Just
> > paint
> > it on and your done.
> >
> > "A.J. Griglak" wrote:
> >
> > > I have four X-10 motion detectors in my house, and have no such
> > problems.  I
> > > have, however, disabled the dusk/dawn setting, which is useless in my
> > > opinion.  For one thing, they eat up another precious house code  ;-)
I
> > > don't have problems with "lots of x-10 commands," so maybe the extra
> > > commands are from the dusk/dawn thing.
> > >
> > > Anyway, do the mod yourself.  At first glance it looks scary, but once
I
> > did
> > > one, I did them all withour referring back to the directions.
> > >
> > > http://www3.edgenet.net/lingling/x10-mod1.html#defeat
> > >
> > > or
> > >
> > >
> >
http://www.geocities.com/ido_bartana/modifying_hawkey_sensor.htm#Disabling
> > %2
> > > 0dusk/dawn%20sensor
> > >
> > > Hope that helps,
> > >
> > > -=A.J.
> > >
> > > -----Original Message-----
> > > From: J Gary Mull [mailto:jgary@mindspring.com]
> > > Sent: Friday, June 30, 2000 9:37 PM
> > > To: ecs-list@netbloc.com
> > > Subject: Re: [ECS] PLC Interface overflow?
> > >
> > > Are you using an X10 motion sensor.  X10 motion detectors send out
lots
> > of
> > > X10 commands so I use hard wired motion sensors.
> > >
> > > At 05:06 PM 6/30/00 -0700, you wrote:
> > > >It just occurred to me that I have a motion detector in one of the
> > hallways
> > > >where a light is turned on by the bed time event.  It's probably the
> > motion
> > > >detector sending out the "daylight" command.  If that's it, there's
not
> > > >much I can do about it.  I use the "daylight" signal to determine if
> > the
> > > >hallway light should be turned on when motion is detected, so I can't
> > > >disable the light sensor.  As long as ECS retries whatever didn't go
> > > >through the first time I guess it should be okay.
> > > >
> > > >  -- Jay
> > > >
> > > >At 18:40 06/30/00 -0400, you wrote:
> > > >
> > > >>This error means that a command has been issued to
> > > >>the CM11A (by ECS) which has not been acknowledged
> > > >>after 5 seconds (i.e. it is "busy" doing "something").
> > > >>What that is I don't know (perhaps ANOTHER transmitter
> > > >>sending a burst of continuous commands ?).
> > > >
> > > >
> > > jgary@atl.mindspring.com   Gary at Home
> > > jgmull@us.ibm.com          Gary at Work

---