Battery Checks (Was: 13a/14a hack = closed circuit?)
Thomas D Arman
tdarman at us.ibm.com
Thu Apr 21 11:33:52 PDT 2005
In reference to the statement below: "XTension sometimes thinks they are
battery checks but the signal integrity is good."
How are people handling this? Are you having to add handler code to every
unit to check if this is a "missed" alert?
I am still asking (I know I am a pain in the butt sometimes) that WE be
given the option of treating the "battery checks" as "ON" or "OFF" and
ignoring them if WE want to rather than XTension ALWAYS ignoring them. And
also that being able to do this NOT require additional coding that checks
unit properties in order to do so. We are already used to checking "time
delta" and "current state" to make the decisions about what actions to
take upon state change reports from various sensors.
Tom
------------------------------------------------------------------
Thomas (Tom) Arman
On 4/21/05 6:39 AM, "Steve Hume" <stevelist at hume.ca> wrote:
> I second the opinion on the security stuff. I am getting reliable
> signals form the door mag switch. XTension sometimes thinks they are
> battery checks but the signal integrity is good.
>
> I did the mag switch hack to a MS12 adding it instead of the dusk
> detector. I put the unit in an envelope to blind the motion sensor. It
> worked but not all events produced a signal! If you use a normally
> closed mag switch then a series resistor helps with battery life.
>
> James, How are you dealing with the 16 unit limit on security sensors?
>
More information about the XTensionlist
mailing list