FireNet Community
FIRE SERVICE AND GENERAL FIRE SAFETY TOPICS => Technical Advice => Topic started by: Benzerari on October 23, 2008, 07:09:47 PM
-
Why in some systems, before touching the panel, every things looks perfect, 'system under normal operation' when setting the systems in test mode, carry on servicing till the end, then try to reinstate the system back to normal, only at this stage some detectors comes up as faulty, till we replaced them. But why they didn't come up faulty before touching the system. Some times I guess we have done some thing wrong, but what is it?
This happened several times with new Gent Vigilon, fitted with old existing heads... etc
Has any one have such experience?
-
Yes frequently with Aritech Panels and on occasion with Advanced using multisensors.
Used to get this loads back in the days of the Ademco FCC500 when a system could sit happy unitl a test of a single mcp then it would bring up loads of dormant device faults.
The only expalnation i can give is that the device in fault has lost comms some how during a test.
-
Yes frequently with Aritech Panels and on occasion with Advanced using multisensors.
Used to get this loads back in the days of the Ademco FCC500 when a system could sit happy unitl a test of a single mcp then it would bring up loads of dormant device faults.
The only expalnation i can give is that the device in fault has lost comms some how during a test.
Thanks Grame for the try, this make sense, but what makes devices to lose comms only under test?..., why not before test? is there some thing to do with loop over loaded? over current in the loop? just doggie device?
I personaly haven't got a clue!
Any more technical explanations?
-
Yes frequently with Aritech Panels and on occasion with Advanced using multisensors.
Used to get this loads back in the days of the Ademco FCC500 when a system could sit happy unitl a test of a single mcp then it would bring up loads of dormant device faults.
The only expalnation i can give is that the device in fault has lost comms some how during a test.
Thanks Grame for the try, this make sense, but what makes devices to lose comms only under test?..., why not before test? is there some thing to do with loop over loaded? over current in the loop? just doggie device?
I personaly haven't got a clue!
Any more technical explanations?
You need to clear the sub-faults Benz after testing on the GENT kit mate.It's in the menu structure (might be under engineer but can't quite remember),you select CLEAR and clear them one by one.Any faults still remaining won't clear and need rectifying.
Check your mail and read from 74 onwards on clearing faults and what the 1000000000 etc. means .
Read the rest of it also if you are bored!!
-
Yes frequently with Aritech Panels and on occasion with Advanced using multisensors.
Used to get this loads back in the days of the Ademco FCC500 when a system could sit happy unitl a test of a single mcp then it would bring up loads of dormant device faults.
The only expalnation i can give is that the device in fault has lost comms some how during a test.
Thanks Grame for the try, this make sense, but what makes devices to lose comms only under test?..., why not before test? is there some thing to do with loop over loaded? over current in the loop? just doggie device?
I personaly haven't got a clue!
Any more technical explanations?
You need to clear the sub-faults Benz after testing on the GENT kit mate.It's in the menu structure (might be under engineer but can't quite remember),you select CLEAR and clear them one by one.Any faults still remaining won't clear and need rectifying.
Check your mail and read from 74 onwards on clearing faults and what the 1000000000 etc. means .
Read the rest of it also if you are bored!!
It wasn't subfault which can be cleared out through clear option...I had cleared out all subfaults..., but it didn't clear out the genuine fault (wiring fault at device 80 ; in Kitchen flat 80) when replaced the Heat/sounder and realocate the loop every thing went perfect
-
if you have disturbed the detector enough to jolt the loop breakers in it this may cause a wiring split on pos line. Allocating this loop would cure this issue....
-
if you have disturbed the detector enough to jolt the loop breakers in it this may cause a wiring split on pos line. Allocating this loop would cure this issue....
All we had done is, put the system in test mode ... tested all rooms, after half hour or so, we tried to reset the system back to normal, the wiring fault came up, who do you think disturbed the detector enough to jolt the loop breaker and how?
-
Only a thought Benz but it may have been hit with the edge of a smoke cup. I've done it myself several times.
-
Only a thought Benz but it may have been hit with the edge of a smoke cup. I've done it myself several times.
110% in agreement there.
-
Only a thought Benz but it may have been hit with the edge of a smoke cup. I've done it myself several times.
But no one touch it with a cup... the kitchen was empty
-
Only a thought Benz but it may have been hit with the edge of a smoke cup. I've done it myself several times.
But no one touch it with a cup... the kitchen was empty
Am I detecting an attempt at humour there Benz???
-
I have definately had the same problem with an Aritech panel and it's on a detector i have been no where near.
-
Only a thought Benz but it may have been hit with the edge of a smoke cup. I've done it myself several times.
But no one touch it with a cup... the kitchen was empty
Am I detecting an attempt at humour there Benz???
To be honest the kitchen was empty, no one touch the head, it came up faulty on its own, and only after test... that's the strange thing, one of the causes could be what Ark Agel and youself suggested, but definitely is not the case in here, even Grame have had such weired things with different make... probably who has long experience too may have some... :)