[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
Re: Alarm panel won't drive bell current
On Monday, March 10, 2014 1:14:19 PM UTC-5, Jim wrote:
> Change the batteries.=20
>=20
> The batteries share the load of powering the bell/siren when the panel is=
in the alarm condition. A dead battery has low resistance therefore the pa=
nel transformer is trying to provide current for the panel, the keypads the=
motion detectors the smoke detectors the almost shorted bad batteries and =
the bell/siren. Batteries are to be changed every three to four years NOT n=
ine years. Likely your bell/siren hasn't been able to ring for a number of =
years because you ignored the low battery signal.=20
>=20
>=20
>=20
> Apparently, one of the other short comings of DMP panels is that it lets =
you ignore a failure of a vital supporting function. Other panels give you =
a constant warning until the batteries have been changed.=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> On Sunday, March 9, 2014 3:20:22 PM UTC-4, blueman wrote:
>=20
> > I have a DMP XR200 alarm panel with the bell output driving an MPI-11
>=20
> >=20
>=20
> > siren driver. The panel bell output supplies 12VDC @1.5A max via an
>=20
> >=20
>=20
> > output relay.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > When the siren driver is connected, I can hear the bell output relay
>=20
> >=20
>=20
> > switch on but then within about 1/2 second the relay immediately switch=
es
>=20
> >=20
>=20
> > off -- this occurs in both pulsed and steady alarm modes.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > The siren driver itself seeems to be working and the panel itself seems
>=20
> >=20
>=20
> > to have sufficient amperage, because when I connect its inputs directly
>=20
> >=20
>=20
> > to +12VDC on the panel, it properly drives the alarm speakers at full
>=20
> >=20
>=20
> > volume, drawing only about 0.4Amps. My oscilloscope confirms that the
>=20
> >=20
>=20
> > output is the expected pseudo-sine wave.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > This led me to think that the problem must be with the panel bell outpu=
t
>=20
> >=20
>=20
> > circuitry. However, when I disconnect the siren driver, the relay stay=
s
>=20
> >=20
>=20
> > on and the voltage to the bell outupt is ~12VDC as it should be. I then
>=20
> >=20
>=20
> > tested it under load using a 10ohm 10W resistor and even under load, th=
e
>=20
> >=20
>=20
> > relay still stayed closed -- using my DVM I verified that the panel was
>=20
> >=20
>=20
> > sourcing ~1.2A without tripping the overcurrent protection. So, at leas=
t
>=20
> >=20
>=20
> > with a static load, all seems to work fine on the panel.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > I then noticed that the siren driver has a 2200 uF cap across its
>=20
> >=20
>=20
> > input. When I put a similar 2200uF cap across the panel bell output, it
>=20
> >=20
>=20
> > caused the relay to switch off. Similarly, when I temporarily removed
>=20
> >=20
>=20
> > the 2200uF cap from the siren driver, the siren driver board no longer
>=20
> >=20
>=20
> > caused the relay to shut off. (I also tried swapping a new 2200uF on th=
e
>=20
> >=20
>=20
> > siren driver and it still caused the relay to shut off)
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > So I can only conclude that the transient current draw used to charge
>=20
> >=20
>=20
> > the 2200uF input capacitor is somehow tripping some internal overcurren=
t
>=20
> >=20
>=20
> > protection circuitry on the XR200 panel. Note that tripping only causes
>=20
> >=20
>=20
> > the alarm output to stop -- the rest of the panel functioning is
>=20
> >=20
>=20
> > unchanged.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > Until now, my alarm has been working reliably for the past ~10
>=20
> >=20
>=20
> > years. So, it seems like something has gone wrong in the current
>=20
> >=20
>=20
> > oversensing circuitry for the bell output.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > Has anybody experienced similar issues before? Any thoughts on how to
>=20
> >=20
>=20
> > further troubleshoot & fix?
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > One other aside which may or may not be related. The alarm a few days
>=20
> >=20
>=20
> > ago started showing a battery trouble which by itself didn't seem
>=20
> >=20
>=20
> > worrisome since the batteries are about 9 years old. Meanwhile, I have
>=20
> >=20
>=20
> > new batteries on order.
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > But this still leaves me to wonder whether the two problems may somehow
>=20
> >=20
>=20
> > be related. Did the battery issue trigger the bell output issue or
>=20
> >=20
>=20
> > vice-versa? Are the batteries even bad or is the 'trouble' really just
>=20
> >=20
>=20
> > triggered by something wrong with the board. (Note: I only discovered
>=20
> >=20
>=20
> > the issue with the bell output after I noticed the battery trouble but
>=20
> >=20
>=20
> > it may have preceded that too)
>=20
> >=20
>=20
> >=20
>=20
> >=20
>=20
> > (note: disconnecting the batteries did not stop the problem with the
>=20
> >=20
>=20
> > siren driver -- I thought initially perhaps that bad batteries could be
>=20
> >=20
>=20
> > drawing too much current but removing them had no effect).
alt.security.alarms Main Index |
alt.security.alarms Thread Index |
alt.security.alarms Home |
Archives Home