Re: Lufkin Security Experiances

["Mark Leuck" <m..leuck@xxxxxxxxxxx>]

"Crash Gordon®" <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®" <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