alarmdecoder.com

I've been using my AD2USB connected to Vera for around 18 months with no issues. All zones are hardwired, and there are no wireless zones. I am using the virtual relay outputs to show zone status in Vera while disarmed. This week, both keypads started beeping with a "Check 100" error on the screen. The beeping won't stop until power is disconnected.

Any thoughts as to what caused this, or how to fix it? TIA!

Here's what I'm seeing in PuTTY while connected to the AD2USB:

Code: Select all

[1000040100000000----],008,[f700000f1008041c08020000000000],"****DISARMED****  Ready to Arm  "
[1000040100000010----],100,[f700000f10000412080200000100ff],"CHECK 100 RF    RECEIVER        "
[1000040100000010----],112,[f700000f10120412080200000100ff],"CHECK 112 RELAY MODULE          "
[1000040100000010----],113,[f700000f10130412080200000100ff],"CHECK 113 RELAY MODULE          "

Please post your AD2USB configuration by issuing a 'C' command to it. As well as version by sending a 'V'

Wondering if LRR Emulation and Relay Emulation got enabled on accident? Or disabled on accident?

kevin wrote:Please post your AD2USB configuration by issuing a 'C' command to it. As well as version by sending a 'V'
Wondering if LRR Emulation and Relay Emulation got enabled on accident? Or disabled on accident?

Thanks for the quick reply. I have no idea how either of those would happen. I was away at the time it started.

Code: Select all

!sn:ffffffff
!boot....................
!
!Ademco Keypad Emulator V2.2a.6
!Copyright (C) 2008-2010 Nu Tech Software Solutions, Inc.
!Reproduction without permission is prohibited
!By Sean Mathews <drwho at f34r.com>
!For support email general@support.nutech.com
!www.NuTech.com
!Reading configuration.
!UART init.
!Ready. Press ! for configuration.
[0000000100000000----],0d1,[f700000f10d1000008020000000000],"Busy - Standby           v9.12D1"
!>
!CONFIG>ADDRESS=00&CONFIGBITS=c0ff&LRR=N&EXP=NNNNN&REL=YYYY&MASK=ffffffff&DEDUPLICATE=N
!VER:ffffffff,V2.2a.6,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;LR;KE;MK;CB
[0000000100000000----],0d1,[f700000f10d1000008020000000000],"Busy - Standby           v9.12D1"

According to your configuration, you have all 4 relay emulation settings enabled - does your panel expect this to be so?

Also, LRR is turned to no - does your panel expect there to be an LRR module enabled?

Did you have an RF keypad that became disconnected or stopped working?

Are you able to arm and disarm using the AD2USB? Does this continue with the AD2USB disconnected from the panel?

If everything is connected up properly, you can clear the errors by disarming twice.

kevin wrote:According to your configuration, you have all 4 relay emulation settings enabled - does your panel expect this to be so?
Also, LRR is turned to no - does your panel expect there to be an LRR module enabled?
Did you have an RF keypad that became disconnected or stopped working?
Are you able to arm and disarm using the AD2USB? Does this continue with the AD2USB disconnected from the panel?
If everything is connected up properly, you can clear the errors by disarming twice.

The keypad ready light is illuminated.
I have no RF keypads or sensors. I don't know what an LRR module is (long-range radio?), but I've not changed any wiring since connecting the AD2USB device in late 2013.
I'm unable to do anything using the keypad emulator or any of the keypads. The alarm behaves the same whether AD2USB is connected to the panel or not. The alarm will not clear.
I have no outside connections to the alarm... so there's no way anyone could have dialed in and changed configuration.
In 2014 sometime, I configured the virtual relays to output to Vera for each zone as in the image below... it's all been working fine for a year or so. This is really aggravating, as I have to remove all power to the panel just to keep the keypads from beeping incessantly. Nothing works. No response from the keypads.

Well if it behaves the same whether the AD2USB is connected or not - I would suggest that maybe something happened to the panel while you were away?

We are happy to test and exchange the AD2USB if necessary if you want to go that route before investigating your panel itself. Email ad2usb@support.nutech.com if you want to do this.

The only time I have really heard of the "Check RF" messages is when the panel is configured for wireless zones and can no longer communicate with them. This (may) be a symptom of a bad AD2USB but we can't know for sure without testing it ourselves. Since you can't really do anything with your panel without the AD2 or with the AD2 there is nothing else I can really suggest to try at this time.

kevin wrote:The only time I have really heard of the "Check RF" messages is when the panel is configured for wireless zones and can no longer communicate with them. This (may) be a symptom of a bad AD2USB but we can't know for sure without testing it ourselves. Since you can't really do anything with your panel without the AD2 or with the AD2 there is nothing else I can really suggest to try at this time.

Well, I have no wireless zones. Are you able to tell by the config I sent earlier whether the panel is configured for them? I haven't made any changes, so I don't know why that would occur now.

I'll send an email as suggested. I don't know what else to do.

Nope, no indication of that we can tell of. First step I think would be to get the AD2 to us for testing and replacement.

Ok sorry for the delay on contributing on this subject. Check 100 error means the RF expander is not operating and the panel has a zone configured as RF so the panel is trying to talk to an RF expander.

You say you do not have a RF expander but your panel disagrees.
It may be inside of one of your keypads some keypads serve dual purpose as a keypad and a RF expander.

You can confirm this by looking on the back of each of them to find the model #'s also if you look inside they tend to have a LONGish metal wire from one side to the other that is the antenna.

So AFAIK having the AD2* on the bus or not will change your results if the panel has a 100 error.

Re
Sean M