Wireless Trouble 7

Wireless Trouble 7 "Burn in" on DSC 1555 panel

Secure Home | Search | About

CCTV, Alarms and other Physical Security - CCTV, fire alarms, secure access technologies 

Bookmark this page:  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Wireless Trouble 7 "Burn in" on DSC 1555 panel tourman 06-25-2009
Posted by tourman on June 25, 2009, 12:45 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Something I found out recently might help out if you experience a
problem eliminating a trouble 7 (wireless problem). It seems, if you
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 battery
in the wireless device, defaulting and reprogramming the wireless
receiver, or even changing out the wireless component itself. Bottom
line, there seems to be some sort of glitch in the firmware somewhere,
whereby the panel keeps cycling, looking for a wireless keyfob (even
if none is present on the system). If none is actually programmed in
the system, after a long length of time, this trouble may permanently
"burn in" to the panel itself, and cannot be cleared without changing
out the panel for a new one.

It seems the solution is to program in some number other than 000000
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

Posted by mleuck on June 25, 2009, 1:41 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
> Something I found out recently might help out if you experience a
> problem eliminating a trouble 7 (wireless problem). It seems, if you
> 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 battery
> in the wireless device, defaulting and reprogramming the wireless
> receiver, or even changing out the wireless component itself. Bottom
> line, there seems to be some sort of glitch in the firmware somewhere,
> whereby the panel keeps cycling, looking for a wireless keyfob (even
> if none is present on the system). If none is actually programmed in
> the system, after a long length of time, this trouble may permanently
> "burn in" to the panel itself, and cannot be cleared without changing
> out the panel for a new one.
>
> It seems the solution is to program in some number other than 000000
> 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 sometimes
caused phantom keyfob low batteries. The prevention was to program all
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.

They had a warning and new v4.22 firmware out about 5 years ago.

Posted by tourman on June 25, 2009, 2:37 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
>
>
>
> > Something I found out recently might help out if you experience a
> > problem eliminating a trouble 7 (wireless problem). It seems, if you
> > 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 battery
> > in the wireless device, defaulting and reprogramming the wireless
> > receiver, or even changing out the wireless component itself. Bottom
> > line, there seems to be some sort of glitch in the firmware somewhere,
> > whereby the panel keeps cycling, looking for a wireless keyfob (even
> > if none is present on the system). If none is actually programmed in
> > the system, after a long length of time, this trouble may permanently
> > "burn in" to the panel itself, and cannot be cleared without changing
> > out the panel for a new one.
>
> > It seems the solution is to program in some number other than 000000
> > 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 sometimes
> caused phantom keyfob low batteries. The prevention was to program all
> 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.
>
> They had a warning and new v4.22 firmware out about 5 years ago.

RHC: Thanks Mark, good to know. However, in my case, I didn't have to
replace the receiver just the panel. I will dial in though and put
numbers in the balance of the wireless keyfob locations.

The trouble 7 indicates a wireless trouble. I brought the old board
back, defaulted it again, and powered it up with just the keypad
attached.....definately trouble 7 still there. Next step ...garbage !!

Posted by mleuck on June 25, 2009, 3:12 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
>
>
>
>
> > > Something I found out recently might help out if you experience a
> > > problem eliminating a trouble 7 (wireless problem). It seems, if you
> > > 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 battery
> > > in the wireless device, defaulting and reprogramming the wireless
> > > receiver, or even changing out the wireless component itself. Bottom
> > > line, there seems to be some sort of glitch in the firmware somewhere=
,
> > > whereby the panel keeps cycling, looking for a wireless keyfob (even
> > > if none is present on the system). If none is actually programmed in
> > > the system, after a long length of time, this trouble may permanently
> > > "burn in" to the panel itself, and cannot be cleared without changing
> > > out the panel for a new one.
>
> > > It seems the solution is to program in some number other than 000000
> > > 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 sometimes
> > caused phantom keyfob low batteries. The prevention was to program all
> > 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.
>
> > They had a warning and new v4.22 firmware out about 5 years ago.
>
> RHC: Thanks Mark, good to know. However, in my case, I didn't have to
> replace the receiver just the panel. I will dial in though and put
> numbers in the balance of the wireless keyfob locations.
>
> The trouble 7 indicates a wireless trouble. I brought the old board
> back, defaulted it again, and powered it up with just the keypad
> attached.....definately trouble 7 still there. Next step ...garbage !!

Trust me, replace the receiver too

Posted by tourman on June 25, 2009, 4:30 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
>
>
>
>
>
> > > > 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 ?

Similar ThreadsPosted
Snow on house causing wireless trouble February 1, 2009, 7:39 pm
DSC 1555 vs DSL March 31, 2006, 8:02 pm
Infinite wireless control panel March 17, 2008, 3:38 pm
Power Wireless CCTV camera via solar panel? July 2, 2007, 5:37 am
Electronics Line USA releases Infinite: A Wireless Security Alarm Panel for the Future September 4, 2007, 3:20 pm
SDI Trouble Definition September 20, 2005, 1:27 pm
DSC Communications trouble - October 6, 2005, 7:22 pm
Check 70 Trouble April 4, 2007, 9:28 pm
DSC 2550 trouble October 26, 2008, 10:10 am
Trouble cyphering the Guzzintas July 24, 2006, 2:42 am

The site map in XML format XML site map

Contact Us | Privacy Policy