How to Clear DSC 832 Wireless Smoke FAULT??

[[email protected]]

Please no "wireless is no good" rants.


System DSC 832 PC 5010 Version 2.0, PC 5132-433 NA Version 4.2

Is there a way to clear a FAULT reported by the keypad??? I understand
that when the wireless receiver supervision does not receive the "i am
ok" from a wireless device within the window that is programmed the
receiver declares a device FAULT. The device in this instance is a
wireless smoke.

I don't know why wireless smoke causes FAULT occasionally. It is
supposed to send the "I am OK" signal to the receiver every 64
minutes. In this case, a window of 8 hours or more should be more
than sufficient.

The Wireless smoke tests OK (push button causes sound, using an actual
smoking source created an alarm signal and pressing a magnet against
designated spot on the smoke housing creates an alarm signal.

The smoke is located nearer the receiver than several MIRs and
window/door switches. These father located devices do not fault unless
a very short window is programmed (a 1 hour window generates many
faults of course)

Disconnecting both AC & battery power "clears" the fault. It may or
may not reappear hours later. Having to disconnect battery & AC power
to CLEAR the FAULT seems drastic.

Yes, I understand that setting the supervision window to the maximum
of 96 x 15 min increments(the 24 hour window default value) minimizes
chance for FAULT unless wireless device REALLY is not sending "I am
OK" supervision signal every 64 mins. Should a setting of 8 hours be
so short that any working device is faulted?

Thanks for your help,
Puzzled

Please post answers in this newsgroup. Private email may get killed by
my spam filter.

 

[alarman]

Please no "wireless is no good" rants.


System DSC 832 PC 5010 Version 2.0, PC 5132-433 NA Version 4.2

Is there a way to clear a FAULT reported by the keypad??? I understand
that when the wireless receiver supervision does not receive the "i am
ok" from a wireless device within the window that is programmed the
receiver declares a device FAULT. The device in this instance is a
wireless smoke.

I don't know why wireless smoke causes FAULT occasionally. It is
supposed to send the "I am OK" signal to the receiver every 64
minutes. In this case, a window of 8 hours or more should be more
than sufficient.

The Wireless smoke tests OK (push button causes sound, using an actual
smoking source created an alarm signal and pressing a magnet against
designated spot on the smoke housing creates an alarm signal.

The smoke is located nearer the receiver than several MIRs and
window/door switches. These father located devices do not fault unless
a very short window is programmed (a 1 hour window generates many
faults of course)

Disconnecting both AC & battery power "clears" the fault. It may or
may not reappear hours later. Having to disconnect battery & AC power
to CLEAR the FAULT seems drastic.

Yes, I understand that setting the supervision window to the maximum
of 96 x 15 min increments(the 24 hour window default value) minimizes
chance for FAULT unless wireless device REALLY is not sending "I am
OK" supervision signal every 64 mins. Should a setting of 8 hours be
so short that any working device is faulted?

How does the detector perform in a placement test? (Section 904) I'd try
relocating the detector. IME, DSC wireless transmitters located very close
to the receiver do not perform consistently. If relocating doesn't work, try
another detector. They have had some QC issues lately.
js

 

[i]

Is it possible to set supervision time on the wireless smoke detector?

 

[Mark Leuck]

You might be able to although I couldn't find it in programming but that
doesn't fix the problem

 

[[email protected]]

Thanks for all the suggestions on how to AVOID the FAULT. The
device(s) does well on the wireless placement test. If the FAULT
happens again (now that I set the window to 24 hours), I will try the
re-locating them.

No I do not know of any way to change the timing of the "I am here"
signal sent by the smoke.Only the window for reception of the signal
can be set according to manual.

Not mentioned thus far: Does anyone know how to clear the FAULT
without disconnecting power to the panel?

Thanks for the responses,

Less Puzzled

 

[[email protected]]

Thanks for all the suggestions on how to AVOID the FAULT. The
device(s) does well on the wireless placement test. If the FAULT
happens again (now that I set the window to 24 hours), I will try the
re-locating them.

No I do not know of any way to change the timing of the "I am here"
signal sent by the smoke.Only the window for reception of the signal
can be set according to manual.

Not mentioned thus far: Does anyone know how to clear the FAULT
without disconnecting power to the panel?

Thanks for the responses,

Less Puzzled

 

[[email protected]]

Thanks for all the suggestions on how to AVOID the FAULT. The
device(s) does well on the wireless placement test. If the FAULT
happens again (now that I set the window to 24 hours), I will try the
re-locating them.

No I do not know of any way to change the timing of the "I am here"
signal sent by the smoke.Only the window for reception of the signal
can be set according to manual.

Not mentioned thus far: Does anyone know how to clear the FAULT
without disconnecting power to the panel?

Thanks for the responses,

Less Puzzled

 

[alarman]

Not mentioned thus far: Does anyone know how to clear the FAULT
without disconnecting power to the panel?

Remove/replace the detector on it's bracket, or put it into alarm. But these
will also send signals.
js

 

[i]

LED blinks with different speed in different situation(troubles), maybe this
may help you come close to solution.
Regards
I

 

[i]

WOW, you are realy smart! I am so a shamed!

You might be able to although I couldn't find it in programming but that
doesn't fix the problem

 

[i]

I was thinking WLS device's LED...

Yes, I always relied on those blinking LEDs when I had 1 Partition and
8 Zones. However all that's over now that I have 8 Partitions and 48
zones. I will keep my existing LED KPs for small systems as well as
the 4 other small systems I have.
Thanks, Richard


Thank you, Richard