Concord Expr. new Snapcard - Bus Failure
#1
Member
Thread Starter
Join Date: Aug 2006
Location: Allentown
Posts: 4
Upvotes: 0
Received 0 Upvotes
on
0 Posts
Concord Expr. new Snapcard - Bus Failure
After a lightning strike, my concord express system was dead (no power to keypads). I traced the problem to a blown transient voltage suppressor (TVS) on the 8 input SnapCard. After removing the TVS, the system came to life but failed the sensor test for all of the sensors connected to the SnapCard. I replaced the SnapCard and all sensors are working, however I get a Bus Falure Unit 0 message, which seems to prevent the system from being fully operational. Do I need to reprogram the thing, because I replaced a SnapCard, or are there still other problems?
#3
Member
Thread Starter
Join Date: Aug 2006
Location: Allentown
Posts: 4
Upvotes: 0
Received 0 Upvotes
on
0 Posts
Thanks for the reply. Well, I got a hold of the manuals and managed to get in to the system programming menus. I found where to delete ID numbers for bus devices, so I removed the number for the Bus 0 device (bus 0 was reporting the failure). However, my new SnapCard doesn't have an 8 digit number on any of its labels (there was a 7 digit number, but that didn't seem to work).
Do I have to enter a number for the new SnapCard, or is it learned when I power up the system?
I'm tempted to clear the entire memory and start fresh, but I didn't install the system, and I don't want to end up making things worse.
Do I have to enter a number for the new SnapCard, or is it learned when I power up the system?
I'm tempted to clear the entire memory and start fresh, but I didn't install the system, and I don't want to end up making things worse.
#5
Member
Join Date: Aug 2006
Location: USA
Posts: 1,268
Upvotes: 0
Received 0 Upvotes
on
0 Posts
Hey there, I work for the manufacturer of that panel...Your problem is not the snapcard anymore. A snapcard is not a bus device, it has no ID numbers. My guess is that the bus failure was caused by the programming keypad you hooked up to the panel to service it?! If you did not use a programming keypad (the one that you plugged into the mother board) let me know..We'll troubleshoot further.
#6
Member
Thread Starter
Join Date: Aug 2006
Location: Allentown
Posts: 4
Upvotes: 0
Received 0 Upvotes
on
0 Posts
Hi. Well, I thought things were looking better for a while. Using one of the wired-in keypads to do the programming from (there are two in my house), I deleted the ID numbers for both of the listed bus devices. I was hoping that after powering down, the system would learn the bus IDs and be happy. At first, it looked like this worked. From the bedroom keypad (the one that I do the programming from) everything was working. However, the downstairs keypad was displaying a * next to the time, and doesn't seem to respond to most commands.
Are the keypads the bus devices? Perhaps the downstairs keypad was also damaged by the lightning?
Thanks!
Are the keypads the bus devices? Perhaps the downstairs keypad was also damaged by the lightning?
Thanks!
#7
Member
Join Date: Aug 2006
Location: USA
Posts: 1,268
Upvotes: 0
Received 0 Upvotes
on
0 Posts
From the bedroom keypad, enter 8+code+01. This will force the panel to manually scan the data bus and pick up all bus devices (keypads are bus devices). When you hit the star button on the good keypad what does it tell you?? If you are still getting a bus failure on unit # whatever, you can hit the "D" and "6" at the same time from any keypad (like the one downstairs giving you trouble) and it will give you it's address. It will look something like this..."DA 000. That would be device address 0. That way you can figure out which one the panel doesn't see.
#8
Member
Thread Starter
Join Date: Aug 2006
Location: Allentown
Posts: 4
Upvotes: 0
Received 0 Upvotes
on
0 Posts
Thanks for your help debugging the faulty key pad. The downstairs one was bad, so I removed it, and the system works fine. When I get around to it, I'll order a new one and the system will be as good as new. Thanks again.