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

Re: DSC Maxsys PC 4020 Reporting probs.



That wasn't a problem, if sending Contact ID or 4/2 on a 1555/832 you had to
use A instead of 0 in the account however that wouldn't cause it to have
problems connecting to the receiver

"McKenzies" <mckenzieclanatcleardotnet.nz> wrote in message
news:42747441@xxxxxxxxxxxxxxx
> You have more experience than I do with the DSC's, so I guess I'm on the
> wrong track.
> I don't recall exactly what the DSC panel model was - probably an 832 ,
but
> there was a definite problem with using zeros in the account number.  It
was
> a while ago, and not one of my panels .  The solution was to replace any
> zeros in the account number with A's.  eg - 1003 would be programmed as
> 1AA3.
>
> Graeme McKenzie
>
>
>
> "Mark Leuck" <m..leuck@xxxxxxxxxxx> wrote in message
> news:rYudnVddZJF5bO_fRVn-pw@xxxxxxxxxxxxxx
> >
> > "Anonymoose" <none@xxxxxxxxxxxxx> wrote in message
> > news:lDBce.50$i1.11@xxxxxxxxxxxxxxxxxxxxxxxxx
> > > "McKenzies" <mckenzieclanatcleardotnet.nz> wrote in message
> > > news:4272c984@xxxxxxxxxxxxxxx
> > > > Have you got a zero programmed as one of the CS account numbers ?  I
> > seem
> > > > to
> > > > remember that there was a problem with that.  The answer was to
> program
> > an
> > > > 'A'   eg; 12A4
> > > >
> > > > Graeme McKenzie
> > >
> > > I do recall the primary system acct # was originally 3AAA. Since this
> > > problem happened, I've changed it to 3000 (which is what the receiver
is
> > > setup to receive). Are you saying that maybe I should change the acct.
#
> > to,
> > > maybe 30A0, 3A00 etc?
> > > thanks.
> >
> > That will just cause the panel to possibly send on the wrong account
> number,
> > it won't prevent problems communicating with the receiver
> >
> >
>
>
>




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