Subject: From: Date:

Re: [ECS] Security-Interface-A Mark Gilmore Wed, 01 Jul 1998 20:48:09 -0700

---

The problem with sct-b is that there is only ONE line for
both TX & RX, requiring some fairly nasty logic.
BUT although ECS.DOC says it's "not supported", the
W95 code is there and so it MIGHT be operational under W95.
IS ANYONE USING SCT-B WITH ECSW ??

Daniel A. Dubay wrote:
> 
> It has been a while since I looked at it.  Security-IFC-A is just the
> wireless receiver, Security-IFC-B is the stand alone security system.  I'm
> glad you asked me this question because I just found out that
> Security-IFC-B is not supported by ECSW.  I was planning to upgrade to
> this soon.  Mark, might this be supported in the near future?  ECSW
> programs the sensors through the wireless receiver.
> 
> Dan Dubay
> 
> On Wed, 1 Jul 1998, Dan Carrington wrote:
> 
> > I guess I am a bit confused as to your setup.  How do you have the
> > receiver only connected to the ECS computer and how do you program your
> > sensors and such without the alarm panel?
> >
> > Dan Carrington
> >
> >
> > Daniel A. Dubay wrote:
> >
> > > Thanks for your reply Dan.  I set my different sensors to different
> > > report
> > > timeouts for a test (as recommended by Mark).  I believe this is the
> > > SPV
> > > you refer to.  I do not have a panel but only the wireless receiver
> > > connected to my computer.  I have all my car sensors set to a 10 sec
> > > report time too.  (The batteries last about two years.)  This worked
> > > well
> > > for me until I upgraded to the recent version of ECS.  My previous
> > > version
> > > was about two years old.  I'm not sure why it isn't working correctly
> > > now.
> > > I haven't tried testing this with a blank ecs.cfg yet.  I can't
> > > understand
> > > how my .cfg file could be causing this anomoly.
> > >
> > > Dan Dubay
> >
> >
> >

-- 
Mark Gilmore
Omnipotence
http://ourworld.compuserve.com/homepages/mark_gilmore_2

---