Programming problem on Vista 20P

One keypad should be 16, the other 17

You also have to enable the use of the second keypad at address *191 (I think its 191) by entering 11 there. This should fix at least the Check 100.

You know how to change the keypad addresses right? ... hold down the 1 & 3 keys immediately after powering up the keypads.

You may have more probs...but thats all i remember without getting a programming sheet out...(later on this)

Post by Mike
I have a 20P with 2 keypads. A 6160 and a 6150RF.
Had everythng programmed and seemingly working fine on the bench. (good
advice guys thanks)
I initially programmed the 5804 Keyfob via the 6150RF keypad. It worked well
although i couldnt figure out how to change one of the buttons to be used as
a panic button.
I decided in my infinite greeny wisdom to try reprogramming the keyfob from
the 6160 keypad using the #3 template via *58.
After doing this i now get the error "Check 100 RF Receiver" according to
the info in the install and setup guide this indicates that "communication
between control and a zone expander or wireless receiver is interupted.
Where xx is the device address." So i know that 01 is the device address for
the 6150RF, so im not sure where to look in the programming to delete the
mistake i just made by going through the *58 Wireless Key Programming
Templates procedure.
I tried going back and disabling all the zones that were made active by
this, and im still getting the same error.
Funy thing is the 6150RF Keypad is still working, and the keyfob still works
as it was when i first programmed it from the 6150RF.
Somewhere i must have entered in device 00 as the device number for the
6150RF when i was trying to reprogramm the keyfob from the 6160.
Any Vista 20P gurus care to shed some light on this mess?
Thanks

Mike

2005-04-24 13:36:41 UTC

Thanks for the reply Crash,
Yes the 6160 is set to address 16 and the 6150RF is set to 17.
I did enable the use of the 6150RF at address *190 and entered in 10.
So im still stuck with this Check 100 RF Receiver error, and im considering
doing a factory reset but hate to go through the hair pulling iw ent through
to get this thing programmed from scratch.

"Crash Gordon�" <***@NONE.COM> wrote in message news:erJae.1$***@news.uswest.net...
One keypad should be 16, the other 17

You also have to enable the use of the second keypad at address *191 (I
think its 191) by entering 11 there. This should fix at least the Check 100.

You know how to change the keypad addresses right? ... hold down the 1 & 3
keys immediately after powering up the keypads.

You may have more probs...but thats all i remember without getting a
programming sheet out...(later on this)

Mike

2005-04-24 13:45:19 UTC

I just had a thought (i know thats a dangerous thing) is it possible that
the by trying to program the keyfob from the 6160 that it somehow thought i
had the wireless module installed and now its looking for it and thats why
im getting the 100 error? The 00 in the 100 is for device 00 which is the
6160 keypad.
Im trying to find where that would have been enabled to see if this is the
case.

Crash Gordon®

2005-04-24 19:35:38 UTC

Its something in the keypad setup..i cant remember...house code, house id..when you use certain wireless keypads/fobs. I'm drawing a blank and I don't have the program sheets at home. The 100 error is rf error...also maybe *24 in panel program. Sorry, either too much chaffeine or not enough this morning.

Mark L. will remember if he's around today.

Post by Mike
I just had a thought (i know thats a dangerous thing) is it possible that
the by trying to program the keyfob from the 6160 that it somehow thought i
had the wireless module installed and now its looking for it and thats why
im getting the 100 error? The 00 in the 100 is for device 00 which is the
6160 keypad.
Im trying to find where that would have been enabled to see if this is the
case.

Mark Leuck

2005-04-24 23:14:26 UTC

Sounds like he doesn't have the wireless receiver in the keypad addressed as
00, won't find it in *24 anymore thats for the older stuff only

"Crash Gordon�" <***@NONE.COM> wrote in message news:aASae.8$***@news.uswest.net...
Its something in the keypad setup..i cant remember...house code, house
id..when you use certain wireless keypads/fobs. I'm drawing a blank and I
don't have the program sheets at home. The 100 error is rf error...also
maybe *24 in panel program. Sorry, either too much chaffeine or not enough
this morning.

Mark L. will remember if he's around today.

RJD314

2005-04-24 22:37:35 UTC

The 6150RF keypad default wireless receceiver address is 00. Make sure
the keypad is seated correctly on the backplate. If the tamper switch
is tripped, the 20p will display a "Check 100 RF Receiver". Try
holding the tamper manually for a couple of minutes to see if the
"Check 100 RF Receiver" restores.

Crash Gordon®

2005-04-24 23:01:15 UTC

Thats weird...the one I did yesterday was set to default 31, I had to change it to 16 to be seen by the panel.

Post by RJD314
The 6150RF keypad default wireless receceiver address is 00. Make sure
the keypad is seated correctly on the backplate. If the tamper switch
is tripped, the 20p will display a "Check 100 RF Receiver". Try
holding the tamper manually for a couple of minutes to see if the
"Check 100 RF Receiver" restores.

Crash Gordon®

2005-04-24 23:11:21 UTC

sorry, thought you meant the keypad address.
keypad addr default it 31
receiver default is 00

"Crash Gordon®" <***@NONE.COM> wrote in message news:cBVae.40$***@news.uswest.net...
Thats weird...the one I did yesterday was set to default 31, I had to change it to 16 to be seen by the panel.

Mark Leuck

2005-04-24 23:15:20 UTC

The keypad part comes from the factory as 31 but the internal keypad
receiver is 00

"Crash Gordon�" <***@NONE.COM> wrote in message news:cBVae.40$***@news.uswest.net...
Thats weird...the one I did yesterday was set to default 31, I had to change
it to 16 to be seen by the panel.

Mark Leuck

2005-04-24 23:15:46 UTC

That keypad may not have a tamper switch, Honeywell took them out a while
back

Mike

2005-04-25 00:54:44 UTC

I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and trying
to set up the keyfob buttons.

The covers are on both keypads and i dont remember seeing or reading
anything about tamper switches.
I also didnt move or do anything with either keypad before this occured.
Please dont make me reset to factory defaults.
I guess if i have to, its only 3 zones and the keyfob programming. If you
guys have any other ideas, i wont be hopping on this again for a couple
days.
Thanks

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a while
back

Ranger

2005-04-26 00:58:50 UTC

Mike,
Sounds like you have the receiver in the keypad disabled. The 5804
will work with the keypad (local) whether the receiver is enabled or
disabled. Since you originally programmed the remote into the keypad, it
works. But when you went into *58, and added a wireless zone for the panic,
the panel, seeing its first wireless zone, is now looking for a receiver.
You said you disabled your new zones, but a disabled wireless zone is still
a wireless zone. It has to be deleted to keep the panel from looking for a
receiver.
(If this was not the first wireless zone in the panel, ignore the
above.)

I never tried programming the same remote into the panel and an RF
keypad; that could be an issue as well....

Try deleting the 5804 from the keypad, and delete the new zones from
the panel (using *56 menu.) Come out of programming and see if you still
get a check 100. If not, great. Then if you want to program the 5804 to
the panel, make sure the receiver is enabled in the keypad. Otherwise just
program the remote to the keypad as you did before, but make one button your
panic.

Hopefully helpful,
Rick C.

Post by Mike
I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and trying
to set up the keyfob buttons.
The covers are on both keypads and i dont remember seeing or reading
anything about tamper switches.
I also didnt move or do anything with either keypad before this occured.
Please dont make me reset to factory defaults.
I guess if i have to, its only 3 zones and the keyfob programming. If you
guys have any other ideas, i wont be hopping on this again for a couple
days.
Thanks

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a while
back

Crash Gordon®

2005-04-26 02:37:18 UTC

Doesn't button 4 (loop 4) on the 5804 have to be programmed?
Can't remember...I hate programming those things anyway.

Post by Ranger
Mike,
Sounds like you have the receiver in the keypad disabled. The 5804
will work with the keypad (local) whether the receiver is enabled or
disabled. Since you originally programmed the remote into the keypad, it
works. But when you went into *58, and added a wireless zone for the panic,
the panel, seeing its first wireless zone, is now looking for a receiver.
You said you disabled your new zones, but a disabled wireless zone is still
a wireless zone. It has to be deleted to keep the panel from looking for a
receiver.
(If this was not the first wireless zone in the panel, ignore the
above.)
I never tried programming the same remote into the panel and an RF
keypad; that could be an issue as well....
Try deleting the 5804 from the keypad, and delete the new zones from
the panel (using *56 menu.) Come out of programming and see if you still
get a check 100. If not, great. Then if you want to program the 5804 to
the panel, make sure the receiver is enabled in the keypad. Otherwise just
program the remote to the keypad as you did before, but make one button your
panic.
Hopefully helpful,
Rick C.

Post by Mike
I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and

trying

Post by Mike
to set up the keyfob buttons.
The covers are on both keypads and i dont remember seeing or reading
anything about tamper switches.
I also didnt move or do anything with either keypad before this occured.
Please dont make me reset to factory defaults.
I guess if i have to, its only 3 zones and the keyfob programming. If you
guys have any other ideas, i wont be hopping on this again for a couple
days.
Thanks

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a

while

Post by Mark Leuck
back

Ranger

2005-04-26 04:24:30 UTC

Yes, they say loop 4 must be programmed in the panel, but you can make the
zone type 00 if you don't want to use the button.
I think I had check 100 on a 20-P one time, when I put in house ID's for
partitions 2 and 3 (field 24), with one RF keypad, but I don't remember the
details...there was a bad keypad involved too.

"Crash Gordon�" <***@NONE.COM> wrote in message news:YPhbe.335$%***@news.uswest.net...
Doesn't button 4 (loop 4) on the 5804 have to be programmed?
Can't remember...I hate programming those things anyway.

Post by Mike
I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and

trying

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a

while

Post by Mark Leuck
back

Crash Gordon®

2005-04-26 04:38:22 UTC

i had a check 100 saturday (6150rf)...defaulted the keypad and reset it to addr 16 and went away...but i wasn't using buttons.

their manuals are getting better though.

Post by Ranger
Yes, they say loop 4 must be programmed in the panel, but you can make the
zone type 00 if you don't want to use the button.
I think I had check 100 on a 20-P one time, when I put in house ID's for
partitions 2 and 3 (field 24), with one RF keypad, but I don't remember the
details...there was a bad keypad involved too.
Doesn't button 4 (loop 4) on the 5804 have to be programmed?
Can't remember...I hate programming those things anyway.

Post by Ranger
Mike,
Sounds like you have the receiver in the keypad disabled. The

5804

Post by Ranger
will work with the keypad (local) whether the receiver is enabled or
disabled. Since you originally programmed the remote into the keypad, it
works. But when you went into *58, and added a wireless zone for the

panic,

Post by Ranger
the panel, seeing its first wireless zone, is now looking for a receiver.
You said you disabled your new zones, but a disabled wireless zone is

still

Post by Ranger
a wireless zone. It has to be deleted to keep the panel from looking for

Post by Ranger
receiver.
(If this was not the first wireless zone in the panel, ignore the
above.)
I never tried programming the same remote into the panel and an RF
keypad; that could be an issue as well....
Try deleting the 5804 from the keypad, and delete the new zones

from

Post by Ranger
the panel (using *56 menu.) Come out of programming and see if you still
get a check 100. If not, great. Then if you want to program the 5804 to
the panel, make sure the receiver is enabled in the keypad. Otherwise

just

Post by Ranger
program the remote to the keypad as you did before, but make one button

your

Post by Ranger
panic.
Hopefully helpful,
Rick C.

Post by Mike
I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and

trying

you

Post by Ranger

Post by Mike
guys have any other ideas, i wont be hopping on this again for a couple
days.
Thanks

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a

while

Post by Mark Leuck
back

Post by RJD314
The 6150RF keypad default wireless receceiver address is 00. Make

sure

Post by Ranger

Post by RJD314
the keypad is seated correctly on the backplate. If the tamper

switch

Post by Ranger

Post by RJD314
is tripped, the 20p will display a "Check 100 RF Receiver". Try
holding the tamper manually for a couple of minutes to see if the
"Check 100 RF Receiver" restores.

Mark Leuck

2005-04-26 05:25:32 UTC

"Crash Gordon�" <***@NONE.COM> wrote in message news:PBjbe.83$***@news.uswest.net...
i had a check 100 saturday (6150rf)...defaulted the keypad and reset it to
addr 16 and went away...but i wasn't using buttons.

their manuals are getting better though.

The manual doesn't show this tho, many times when exiting RF keypad
programming you will get a check 100, in those cases entering then exiting
panel programming clears that up. Older 6150RF keypads had problems with the
tamper switch which is why they deleted that on later versions. If he's
getting a check 100 then it's going to be one of the following

1. He doesn't have his receiver set at address 100
2. He doesn't have a receiver period
3. He's got an older 6150RF keypad with a bad tamper
4.
5. He's got a defective RF keypad

I've worked with these panels hundreds of times and thats pretty much all it
could be, I'd default the RF keypad and start over if I were him :)

Mark Leuck

2005-04-26 05:21:28 UTC

No you can't make loop 4 a 00 or it will show a check/trouble if activated,
instead if you don't want to use that button make it a 23

Ranger

2005-04-26 12:20:25 UTC

5804BD Install manual claims 00, (but it also claims you don't have to
assign a user # on a 20-P.) What if you were using another button to
activate a trigger with zt23, no alarm output?

the

Post by Ranger
details...there was a bad keypad involved too.

No you can't make loop 4 a 00 or it will show a check/trouble if activated,
instead if you don't want to use that button make it a 23

Mark Leuck

2005-04-27 02:16:33 UTC

Keep in mind the documentation for the 5804BD came out long before the
15P/20P panels did and so it is oriented more to the Vista-40/50 panels
which couldn't have the receiver at address 00 (thats for keypads). On the
20P yu do need to set the receiver address to 00 and you do have to link it
to a user code (make it below user 33 which by default is the master for
partition 2)

Triggers are easy, map the relay in *79 then set up a schedule in *80 and
use "Activated by Zone type" and make that zone type 23

Nice thing about that panel is it can do a ton of things in the schedules,
mine here arms/disarms every hour in the morning then sends 10 test signals,
I can set one relay to trigger 24 different ways if I want

Post by Ranger
5804BD Install manual claims 00, (but it also claims you don't have to
assign a user # on a 20-P.) What if you were using another button to
activate a trigger with zt23, no alarm output?

Post by Ranger
Yes, they say loop 4 must be programmed in the panel, but you can make

the

Post by Ranger
zone type 00 if you don't want to use the button.
I think I had check 100 on a 20-P one time, when I put in house ID's for
partitions 2 and 3 (field 24), with one RF keypad, but I don't remember

the

Post by Ranger
details...there was a bad keypad involved too.

No you can't make loop 4 a 00 or it will show a check/trouble if

activated,

Post by Mark Leuck
instead if you don't want to use that button make it a 23

Mark Leuck

2005-04-26 05:20:21 UTC

Yes but that will just give a check + zone not check 100, and you won't hate
doing keyfobs when you do the *58 menu and templates, it's a breeze

"Crash Gordon�" <***@NONE.COM> wrote in message news:YPhbe.335$%***@news.uswest.net...
Doesn't button 4 (loop 4) on the 5804 have to be programmed?
Can't remember...I hate programming those things anyway.

Crash Gordon®

2005-04-26 14:26:11 UTC

Yah I usually use the template.

I'm having a problem with one now that I have to deal with: 5804bd & 5800tm...slow response - pain in the butt.

Post by Mark Leuck
Yes but that will just give a check + zone not check 100, and you won't hate
doing keyfobs when you do the *58 menu and templates, it's a breeze
Doesn't button 4 (loop 4) on the 5804 have to be programmed?
Can't remember...I hate programming those things anyway.

Mark Leuck

2005-04-27 02:19:58 UTC

Thats a slow keyfob anyway, they are coming out with the 5805 abd 5805BDV
sometime this summer, I saw a prototype 2 years ago, will now give 8
functions instead of 4, smaller and slightly different design.

You could also try next time a 5883 Transeiver (sp?), has a built-in 5800TM

"Crash Gordon�" <***@NONE.COM> wrote in message news:Cdsbe.220$***@news.uswest.net...
Yah I usually use the template.

I'm having a problem with one now that I have to deal with: 5804bd &
5800tm...slow response - pain in the butt.

Crash Gordon®

2005-04-27 14:07:27 UTC

This was a takeover from a 3letter company. I've personally only installed a handful of 5804bd/tm's. I'm not a big fan of devices that disarm a system without a code entry.

But, anyway...the orig. installing co. put the box/5800tm/5881/ all down on the floor in a closet with mirrored doors. I think I spoke about this before...but it's happening on and off. Sometimes it works fine,,,sometimes it's slow...the other day it wouldn't disarm when they accidently set it off, they had to enter their code at the keypad.

It's an old Vista 10se ver. 12. Owners say its 10 years old. Everything works fine except this intermittant behavior of the 5804bd (actually they have two of them).

R.

Post by Mark Leuck
Thats a slow keyfob anyway, they are coming out with the 5805 abd 5805BDV
sometime this summer, I saw a prototype 2 years ago, will now give 8
functions instead of 4, smaller and slightly different design.
You could also try next time a 5883 Transeiver (sp?), has a built-in 5800TM
Yah I usually use the template.
I'm having a problem with one now that I have to deal with: 5804bd &
5800tm...slow response - pain in the butt.

Post by Mark Leuck
Yes but that will just give a check + zone not check 100, and you won't

hate

Post by Mark Leuck
doing keyfobs when you do the *58 menu and templates, it's a breeze
Doesn't button 4 (loop 4) on the 5804 have to be programmed?
Can't remember...I hate programming those things anyway.

Robert L. Bass

2005-04-27 14:34:24 UTC

Post by Crash GordonÂ®
This was a takeover from a 3letter company. I've personally only installed
a handful of 5804bd/tm's. I'm not a big fan of devices that disarm a
system without a code entry.
But, anyway...the orig. installing co. put the box/5800tm/5881/ all down
on the floor in a closet with mirrored doors. I think I spoke about this
before...but it's happening on and off. Sometimes it works
fine,,,sometimes it's slow...the other day it wouldn't disarm when they
accidently set it off, they had to enter their code at the keypad.
It's an old Vista 10se ver. 12. Owners say its 10 years old. Everything
works fine except this intermittant behavior of the 5804bd (actually they
have two of them).

Hi Crash,

Not sure if this is it but on some older panels I've seen a problem
responding to RF remotes when the siren was active. It turned out to be a
power problem. The siren would draw so much current that the voltage
available at the receiver was dropping. You can check to see if this is
happening by testing the voltage at the receiver with and without siren.
It's a long shot but it's easy enough to check. If that does turn out to be
the problem you can offload the siren(s) from the panel power supply with a
relay wired directly to the battery.

Frank would remind you if I didn't to run the power through an inline fuse.
:^)
--
Regards,
Robert L Bass

=============================>
Bass Home Electronics
2291 Pine View Circle
Sarasota · Florida · 34231
877-722-8900 Sales & Tech Support
http://www.bassburglaralarms.com
=============================>

Crash Gordon®

2005-04-27 15:34:14 UTC

That's a thought.

I'm still thinking the mirror and the recievers being mounted so low is a contributor to problem...except he claims this is a recent problem. I don't think its a programming problem or they wouldn't work at all...and I've replaced all batts...system, points, keyfobs. I hate to even mention the "m" word.

Hi Crash,
Not sure if this is it but on some older panels I've seen a problem
responding to RF remotes when the siren was active. It turned out to be a
power problem. The siren would draw so much current that the voltage
available at the receiver was dropping. You can check to see if this is
happening by testing the voltage at the receiver with and without siren.
It's a long shot but it's easy enough to check. If that does turn out to be
the problem you can offload the siren(s) from the panel power supply with a
relay wired directly to the battery.
Frank would remind you if I didn't to run the power through an inline fuse.
:^)
--
Regards,
Robert L Bass
=============================>
Bass Home Electronics
2291 Pine View Circle
Sarasota · Florida · 34231
877-722-8900 Sales & Tech Support
http://www.bassburglaralarms.com
=============================>

Robert L. Bass

2005-04-27 20:27:36 UTC

Post by Crash GordonÂ®
I'm still thinking the mirror and the recievers being mounted so low is a
contributor to problem...except he claims this is a recent problem. I
don't think its a programming problem or they wouldn't work at all...and
I've replaced all batts...system, points, keyfobs. I hate to even mention
the "m" word.

The trouble with RF is when you have a problem it's rarely simple. There
are so many possible factors. Have you checked with Paul? :^)

R.H.Campbell

2005-04-27 21:28:10 UTC

Hehehehehe.....

RHC

"Robert L. Bass" <***@comcast.net> wrote in message news:rKednYleb9NQaPLfRVn-***@comcast.com...

The trouble with RF is when you have a problem it's rarely simple. There
are so many possible factors. Have you checked with Paul? :^)

Robert L. Bass

2005-04-27 23:32:02 UTC

Post by R.H.Campbell
Hehehehehe.....

I figured that would get a rise out of someone. :^)

R.H.Campbell

2005-04-28 00:35:44 UTC

Chucking out the bait were you ? Wanted to see who would bite eh !!?? Ok, I
plead guilty....couldn't resist........ (like poking at a sore.......anxious
to see what Paulie has to say.....)

OOOOH NO !! ...here comes verbal diarrea post 1 of 10 on the horrendous
dangers of RFI....

(the ng's been a bit slow lately; maybe that'll stir him up a bit )

RHC

Post by R.H.Campbell
Hehehehehe.....

I figured that would get a rise out of someone. :^)

Crash Gordon®

2005-04-28 00:46:49 UTC

Would that be considered Troll trolling?

Post by R.H.Campbell
Chucking out the bait were you ? Wanted to see who would bite eh !!?? Ok, I
plead guilty....couldn't resist........ (like poking at a sore.......anxious
to see what Paulie has to say.....)
OOOOH NO !! ...here comes verbal diarrea post 1 of 10 on the horrendous
dangers of RFI....
(the ng's been a bit slow lately; maybe that'll stir him up a bit )
RHC

Post by R.H.Campbell
Hehehehehe.....

I figured that would get a rise out of someone. :^)

R.H.Campbell

2005-04-28 02:59:37 UTC

More like fishing for "crappies" (or sunfish as they are known in Canada).
Once we catch them, we throw them back as garbage fish. But it's fun to bait
and hook them nevertheless.

I figure if Paulie is going to "crap" all over the ng with his RFI garbage,
and not go away, we might as well have some fun with him and give him some
of his own medicine.....

Here Paulie..Paulie...Paulie.....take the bait !!

(Yawn...I must be bored tonight....)

RHC

"Crash Gordon�" <***@NONE.COM> wrote in message news:_oWbe.63$***@news.uswest.net...
Would that be considered Troll trolling?

Post by R.H.Campbell
Chucking out the bait were you ? Wanted to see who would bite eh !!?? Ok, I
plead guilty....couldn't resist........ (like poking at a
sore.......anxious
to see what Paulie has to say.....)
OOOOH NO !! ...here comes verbal diarrea post 1 of 10 on the horrendous
dangers of RFI....
(the ng's been a bit slow lately; maybe that'll stir him up a bit )
RHC

Post by R.H.Campbell
Hehehehehe.....

I figured that would get a rise out of someone. :^)

Crash Gordon®

2005-04-28 03:05:34 UTC

You must be bored!...me too I guess...lots of stuff to do, but I'm trying to procrastinate as best I can - but the Boss had me painting bedrooms today, cant wait to see what she will want me to do tomorrow.

We have lots of man-made little fishing ponds here...full of crappies. I bet theres plenty in Belgium too.

Post by R.H.Campbell
More like fishing for "crappies" (or sunfish as they are known in Canada).
Once we catch them, we throw them back as garbage fish. But it's fun to bait
and hook them nevertheless.
I figure if Paulie is going to "crap" all over the ng with his RFI garbage,
and not go away, we might as well have some fun with him and give him some
of his own medicine.....
Here Paulie..Paulie...Paulie.....take the bait !!
(Yawn...I must be bored tonight....)
RHC
Would that be considered Troll trolling?

Post by R.H.Campbell
Chucking out the bait were you ? Wanted to see who would bite eh !!?? Ok, I
plead guilty....couldn't resist........ (like poking at a
sore.......anxious
to see what Paulie has to say.....)
OOOOH NO !! ...here comes verbal diarrea post 1 of 10 on the horrendous
dangers of RFI....
(the ng's been a bit slow lately; maybe that'll stir him up a bit )
RHC

Post by R.H.Campbell
Hehehehehe.....

I figured that would get a rise out of someone. :^)

Robert L. Bass

2005-04-28 03:17:14 UTC

Post by Crash GordonÂ®
You must be bored!...me too I guess...lots of
stuff to do, but I'm trying to procrastinate as
best I can - but the Boss had me painting
bedrooms today, cant wait to see what she
will want me to do tomorrow.

Seen on a bumper sticker:
Procrastinate Now!
Don't put it off!

Post by Crash GordonÂ®
We have lots of man-made little fishing ponds
here...full of crappies...

What a coincidence. We have an ECLB member like that.

Crash Gordon®

2005-04-28 00:05:04 UTC

Yah...I have a call into him now!...except his cell phone is muzzled... Sheesh, that freekin lunatic :-)

The trouble with RF is when you have a problem it's rarely simple. There
are so many possible factors. Have you checked with Paul? :^)

Mark Leuck

2005-04-28 02:18:21 UTC

"Crash Gordon�" <***@NONE.COM> wrote in message news:piObe.21$***@news.uswest.net...
That's a thought.

I'm still thinking the mirror and the recievers being mounted so low is a
contributor to problem...except he claims this is a recent problem. I don't
think its a programming problem or they wouldn't work at all...and I've
replaced all batts...system, points, keyfobs. I hate to even mention the "m"
word.

They always claim it's a recent problem :)

Mount the receiver as high as you can, it'll fix it

Crash Gordon®

2005-04-28 02:55:44 UTC

Yep...just found an empty 5881 case, gonna remote it up near the closet's ceiling..same for the TM.

I assume I can just tap the TM lines into the 5881 instead of running 2 lines down..electrically should be the same right? Yah.

Thanks!

Post by Crash GordonÂ®
That's a thought.
I'm still thinking the mirror and the recievers being mounted so low is a
contributor to problem...except he claims this is a recent problem. I don't
think its a programming problem or they wouldn't work at all...and I've
replaced all batts...system, points, keyfobs. I hate to even mention the "m"
word.
They always claim it's a recent problem :)
Mount the receiver as high as you can, it'll fix it

Crash Gordon®

2005-04-27 19:07:15 UTC

Tech support says that the TM should be mounted between 1-2' from the reciever antenna on the same plane (ADT had installed it 2" from the reciever). They also recommend moving the reciever & TM up above the mirrored doors (DUH)...currently they're both mounted about 12" from the floor...and too close to each other.

Kinda what I suspected.

He could not find any mention of voltage drop while siren was running in tech data regarding this particular revision...he said maybe on an earlier rev. This one turns out to be rev 12 (1997+)

Now, I just gotta find an empty reciever case so I can remote the reciever.

Hi Crash,
Not sure if this is it but on some older panels I've seen a problem
responding to RF remotes when the siren was active. It turned out to be a
power problem. The siren would draw so much current that the voltage
available at the receiver was dropping. You can check to see if this is
happening by testing the voltage at the receiver with and without siren.
It's a long shot but it's easy enough to check. If that does turn out to be
the problem you can offload the siren(s) from the panel power supply with a
relay wired directly to the battery.
Frank would remind you if I didn't to run the power through an inline fuse.
:^)
--
Regards,
Robert L Bass
=============================>
Bass Home Electronics
2291 Pine View Circle
Sarasota · Florida · 34231
877-722-8900 Sales & Tech Support
http://www.bassburglaralarms.com
=============================>

Mark Leuck

2005-04-28 02:20:04 UTC

"Crash Gordon�" <***@NONE.COM> wrote in message news:jqRbe.18$***@news.uswest.net...
Tech support says that the TM should be mounted between 1-2' from the
reciever antenna on the same plane (ADT had installed it 2" from the
reciever). They also recommend moving the reciever & TM up above the
mirrored doors (DUH)...currently they're both mounted about 12" from the
floor...and too close to each other.

Kinda what I suspected.

He could not find any mention of voltage drop while siren was running in
tech data regarding this particular revision...he said maybe on an earlier
rev. This one turns out to be rev 12 (1997+)

Ademco doesn't have that voltage drop problem, if you're over the limit
you'll get one blip out of the siren and the system dies for a few seconds

Mark Leuck

2005-04-28 02:17:31 UTC

"Crash Gordon�" <***@NONE.COM> wrote in message news:01Nbe.8$***@news.uswest.net...
This was a takeover from a 3letter company. I've personally only installed a
handful of 5804bd/tm's. I'm not a big fan of devices that disarm a system
without a code entry.

Well that's easy to take care of, just don't program a disarm button :)

But, anyway...the orig. installing co. put the box/5800tm/5881/ all down on
the floor in a closet with mirrored doors. I think I spoke about this
before...but it's happening on and off. Sometimes it works fine,,,sometimes
it's slow...the other day it wouldn't disarm when they accidently set it
off, they had to enter their code at the keypad.

Mirrored doors? Umm I think that might be a problem

It's an old Vista 10se ver. 12. Owners say its 10 years old. Everything
works fine except this intermittant behavior of the 5804bd (actually they
have two of them).

Strange, I have a 5804BD and a BDV and haven't had that happen

Mark Leuck

2005-04-26 05:19:29 UTC

Post by Ranger
I never tried programming the same remote into the panel and an RF
keypad; that could be an issue as well....

I have, it does work and sometimes has it's advantages, for instance as a
trigger for the keypad relay AND panel relay

Ranger

2005-04-26 11:39:55 UTC

Good to know - might save adding a relay module sometime...

Post by Ranger
I never tried programming the same remote into the panel and an RF
keypad; that could be an issue as well....

I have, it does work and sometimes has it's advantages, for instance as a
trigger for the keypad relay AND panel relay

Mike

2005-04-27 10:28:22 UTC

Rick
I thought about deleting the wireless zones but thought they were there by
default.
This makes sense though if the zones should not even be showing (and they
are) In and L are showing for several zones and for all that are i set the
zone type to 00 to disable.
Do you know for a fact that these zones are "created" automatically when you
try to set up a wireless zone for the first time?

You said:
"Then if you want to program the 5804 to the panel, make sure the receiver
is enabled in the keypad.
Otherwise just program the remote to the keypad as you did before, but make
one button your panic."

Which of the above would be the preferred method for using the 5804 or it
doesnt matter as long as only one or the other is used?

Post by Mike
I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and

trying

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a

while

Post by Mark Leuck
back

Ranger

2005-04-29 04:31:28 UTC

Post by Mike
Rick
I thought about deleting the wireless zones but thought they were there by
default.
This makes sense though if the zones should not even be showing (and they
are) In and L are showing for several zones and for all that are i set the
zone type to 00 to disable.

If you don't select 'Delete Zone,' at the prompt, the panel retains the rf
type and serial #.

Post by Mike
Do you know for a fact that these zones are "created" automatically when you
try to set up a wireless zone for the first time?

well, not really created, but existing zone #'s , changed from 00 to a zone
type.

Post by Mike
"Then if you want to program the 5804 to the panel, make sure the receiver
is enabled in the keypad.
Otherwise just program the remote to the keypad as you did before, but make
one button your panic."
Which of the above would be the preferred method for using the 5804 or it
doesnt matter as long as only one or the other is used?

I find it easier to add them to the panel, but adding them to the keypad
will save zones in the panel for other things.
At work, all my RF keypads are mounted 8' off the floor anyway...
So, did you lose the Check 100?

for

Post by Ranger
a
receiver.
(If this was not the first wireless zone in the panel, ignore the
above.)
I never tried programming the same remote into the panel and an RF
keypad; that could be an issue as well....
Try deleting the 5804 from the keypad, and delete the new zones from
the panel (using *56 menu.) Come out of programming and see if you still
get a check 100. If not, great. Then if you want to program the 5804 to
the panel, make sure the receiver is enabled in the keypad. Otherwise just
program the remote to the keypad as you did before, but make one button your
panic.
Hopefully helpful,
Rick C.

Post by Mike
I tried setting the Receiver address on the 5160RF to 00 (was 01) and i
still get the same error.
This all happened as i first mentioned after going into the 6160 and

trying

Post by Mark Leuck
That keypad may not have a tamper switch, Honeywell took them out a

while