[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Napco GEM3200 Reporting problem



On Feb 21, 11:21=A0am, mleuck <m.le...@xxxxxxxxx> wrote:
> On Feb 20, 11:01=A0pm, djteche <dillo...@xxxxxxxxx> wrote:
>
>
>
> > On Feb 20, 10:57=A0pm, mleuck <m.le...@xxxxxxxxx> wrote:
>
> > > On Feb 20, 10:52=A0pm, djteche <dillo...@xxxxxxxxx> wrote:
>
> > > > New to the group, DIY'er, I have a GEM3200 that's reporting to my
> > > > Asterisk PBX just fine, but when it finishes it still throws a Comm
> > > > Fail E03-00 Trouble. I get full events reported, no problems, but i=
t
> > > > still throws the trouble...
>
> > > > Any ideas of what to look for in programming? The same thing happen=
s
> > > > if I switch to pager format.
>
> > > What format are you currently using? My guess is it's expecting an ac=
k
> > > from a central station receiver that doesn't exist
>
> > Ah, stupid of me, Napco calls it Point ID but I know it's Ademco
> > Contact ID, and the script I'm using gives a handshake and ACK signal,
> > like I just armed and disarmed and both signals came in at once, so
> > the panel is catching the ACK signal.
>
> > When in pager format, would it expect an ACK signal as well?
>
> No not with the pager format, does it resend the signal over and over
> again before going into trouble?

No sir, sends the correct signals, each once, hangs up, throws a
trouble, then momentarily picks up the line and re-hangs up. Doesn't
attempt to re-send.


alt.security.alarms Main Index | alt.security.alarms Thread Index | alt.security.alarms Home | Archives Home