FireNet Community
FIRE SERVICE AND GENERAL FIRE SAFETY TOPICS => Technical Advice => Topic started by: youngsy01 on June 15, 2009, 09:50:09 PM
-
BLC loop 02 interrupt
Called to a large site today to this fault, after previous maintenace company proved incompetant at the task!
Is there a panel that tells you which device is polling incorrupt / bad data?
This would give you a great heads up.... as a pose to an afternoon on site finding the devil device.
Ta muchly
-
Which panel is at the site, and what protocol is it running, do you know?
-
Vega running apollo XP95.
Fault turned out to be a call point!
-
Could you not check the devices analogue value..? Or were they all appearing correct..?
-
All appeared correct........
-
Sometimes spurious faults with devices are only indicated on a panel like this and it can take a while to determine which device is in fault unfortunately. This wasn't running radio devices on it by any chance was it...?
Do you know how old the panel is...? As initially there were software issues, which were corrected in later releases of software for the panel
-
No radio devices running.... panel must be approximately 6-10 years old.
Another quick one...... auto learn on the Kidde Vega does that highlight only additional devices found like advanced, or does it over write existing like Kentec.
Im going down to see Kidde on the 25th, so will be much more familiar then.
-
Aside from the software issue (which KIDDE were quick to respond to and rectify - weell,thats what I found!) I liked the VEGA.From memory though it autolearns without comparing the current device list so no error reported.
I have a manual on it on a folder somewheres so I'll have a look at it.
allen
-
We had a mare with loop sounders , when the panel came out first.
-
Vega can be a pain.
The logon count is the important part.
If you accept with out reviewing any changes you can lose devices.
Detectors that were removed and isolated for example, if they are then reinstated but no auto learn and logon count accepted they sit on the loop, cause loads of problems but are not visible on loop scans.
First thing to do with a vega with problems is an autolearn then compare logon changes