[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: Lufkin Security Experiances
Tell the truth, it looks almost new except for a little paint on the =
can's door. Guy's saying 10 years but certainly didn't look it.
thanks
"Mark Leuck" <m..leuck@xxxxxxxxxxx> wrote in message =
news:GeudnRTjCqJel87fRVn-sQ@xxxxxxxxxxxxxx
>=20
> "Crash Gordon=AE" <NONE@xxxxxxxx> wrote in message
> news:rWx4e.1$3n3.37@xxxxxxxxxxxxxxxxxx
> otay thanks!
>=20
> slightly diff topic:
>=20
> I did a ADT takeover a couple of days ago it was a Vista 10se, the =
chip said
> Version 12 (?)...panel looked new but client said it's been in for
> years..but Ver. 12 ? Did ADT have it's own chip versions 7-10 years =
ago?
> Panel programming matched the sheet I brought...except for one entry.
>=20
>=20
> The Vista-10SE stopped at v15 so it might indeed be old, as far as ADT =
their
> versions usually follow Honeywell/Ademco's as far as I know
>=20
> (I know ours does anyway)
>=20
>=20
>=20
> "Mark Leuck" <m..leuck@xxxxxxxxxxx> wrote in message
> news:9OedndFcCtjEjM_fRVn-3Q@xxxxxxxxxxxxxx
> >
> > "Crash Gordon=AE" <NONE@xxxxxxxx> wrote in message
> > news:BSk4e.46$Sd3.1045@xxxxxxxxxxxxxxxxxx
> > inline...
> >
> >
> > "Mark Leuck" <m..leuck@xxxxxxxxxxx> wrote in message
> > news:DKKdnYepA6-bJ8zfRVn-jg@xxxxxxxxxxxxxx
> > >
> > > "Crash Gordon=AE" <NONE@xxxxxxxx> wrote in message
> > > news:Veb4e.7$Sd3.44@xxxxxxxxxxxxxxxxxx
> > > Yah, addressing non-supervised keypads always confuses me. I still =
hit
> > > myself in the head after pulling the 6139 and discovering the 6148 =
has
> no
> > > display because I forgot to set the addressssss on it...DUH.
> > >
> > > The fun part is when you set the programming keypad to the same =
address
> as
> > > another keypad, it won't let you into programming
> >
> > hmmm i think ive done that too.
> >
> > >
> > > Still confuses me about setting the daily test schedule vs. =
installer
> code
> > > #00 thing for daily tests.
> > >
> > > They made it easier to setup daily, weekly, monthly test reporting =
with
> > that
> > > method than going into scheduling and doing it the hard way, works
> pretty
> > > well too and beats walking someone through schedules
> >
> > Soooo you're saying I don't havta set the scheds...sheesh. I've =
been
> doing
> > it BOTH ways to be safe.
> >
> > It automatically sets the test time in schedule 11, never hurts to =
check
> it
> > either way since you may run into a v1 and not realize it, only the =
v2 and
> > up support that feature
> >
> >
> >
>=20
>=20
>
alt.security.alarms Main Index |
alt.security.alarms Thread Index |
alt.security.alarms Home |
Archives Home