[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: Wireless Trouble 7 "Burn in" on DSC 1555 panel
On Jun 25, 3:12=A0pm, mleuck <m.le...@xxxxxxxxx> wrote:
> On Jun 25, 1:37=A0pm, tourman <robercampb...@xxxxxxxxx> wrote:
>
>
>
> > On Jun 25, 1:41=A0pm, mleuck <m.le...@xxxxxxxxx> wrote:
>
> > > On Jun 25, 11:45=A0am, tourman <robercampb...@xxxxxxxxx> wrote:
>
> > > > Something I found out recently might help out if you experience a
> > > > problem eliminating a trouble 7 (wireless problem). It seems, if yo=
u
> > > > have a wireless receiver and at least one wireless point of entry
> > > > (door or motion) on a DSS 1555 panel, after some time, you may
> > > > experience a trouble 7, which doesn't respond to changing the batte=
ry
> > > > in the wireless device, defaulting and reprogramming the wireless
> > > > receiver, or even changing out the wireless component itself. Botto=
m
> > > > line, there seems to be some sort of glitch in the firmware somewhe=
re,
> > > > whereby the panel keeps cycling, looking for a wireless keyfob (eve=
n
> > > > if none is present on the system). If none is actually programmed i=
n
> > > > the system, after a long length of time, this trouble may permanent=
ly
> > > > "burn in" to the panel itself, and cannot be cleared without changi=
ng
> > > > out the panel for a new one.
>
> > > > It seems the solution is to program in some number other than 00000=
0
> > > > in section 41 of the programming in section 804 of the wireless
> > > > receiver.
>
> > > > I have no idea why this happens, but this is the second occurrence =
of
> > > > this problem that I have experienced.
>
> > > > Hope this helps someone else
>
> > > That is because you are using a v4.2 wireless receiver which sometime=
s
> > > caused phantom keyfob low batteries. The prevention was to program al=
l
> > > keyfobs with something other than 000000 however if it already
> > > happened you had to replace both panel and receiver. Never heard of
> > > the zone 7 part tho.
>
> Trust me, replace the receiver too
RHC: I just got back from Tried looking for the replacement chip for
that receiver. They were giving them out for awhile, but not a chance
to get one now. Seems a patch solution is to dial in and program all
32 keyfob locations with 100000. Apparently, this will prevent a re-
occurrence of the problem.
However Mark, do you know anything different that would cause you to
say to change out the receiver too ?
alt.security.alarms Main Index |
alt.security.alarms Thread Index |
alt.security.alarms Home |
Archives Home