Not seeing all messages using via connected AD2USB

[davide123]

I just successfully connected my AD2UDP serially via a Raspberry Pi 4 running Raspbian (Buster). I'm using screen to connect, configure and see messages.

The issue I am having is that I am only seeing RFX messages.

My configuration bitmask is CONFIGBITS=ff04.

I am not seeing any other message than the RFX messages (example RFX:0049296,84), no zone faults, arm/disarm, etc.

I am also using the Home Assistant integration to interrogate the AD2USB device which it can see but also isn't populating anything there either. I must have some misconfiguration on the AD2USB or perhaps the keypad programming itself?

Here is the entire configuration dump for my device:

CONFIG>MODE=A&CONFIGBITS=ff04&ADDRESS=23&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N

Does anyone have any ideas why I'm only seeing RFX messages?

Thanks!

[mathewss]

Nope. Thats a new one.

Firmware version?

How about the version and full config strings.

Best
SM.

[davide123]

Hi thank you so much for your quick response.

The full configuration string is:
CONFIG>MODE=A&CONFIGBITS=ff04&
ADDRESS=23&LRR=N&COM=N&
EXP=NNNNN&REL=NNNN&MASK=ffffffff
&DEDUPLICATE=N

!VER:ffffffff,V2.2a.8.8,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;L2;KE;M2;CB;DS;ER;CR


Note I'm using address 23 on my Vista 20p.

Screenshot of version attached.

Weird that I'm getting a drip of RF messages but that is all.

David

[davide123]

One more note on my config:
1. I'm powering the AD2USB externally via a 12V adapter (seems to work fine)
2. The Do Di wires are about 4 feet in length from the panel, perhaps there is an attenuation issue?

Thx

[davide123]

Ok, I reconfigured the device with new CONFIGBITS mask of FF0F (default was FF04) and I am now seeing lots of messages including RFX, AUI, KPE... which is great. What I am still unable to do apparently is see zone information and also send keypad commands directly to the panel through the interface.

Examples of what I am able to see now:

!RFX:0099288,04
!AUI:00006cf5ec00
!AUI:1600
!AUI:00006200
!AUI:00006001
!RFX:0524515,dc
!RFX:0000000,fe
!AUI:
!AUI:000065
!AUI:000000
!AUI:00006400
!AUI:000066
!AUI:160067
!RFX:0784387,dc
!RFX:0343280,84
!RFX:0000254,f4
!RFX:0633856,ed
!RFX:0835831,ba
!AUI:000000e8
!AUI:0000

Progress, but something is still a little off....

[kd7mlg]

imo, those AUI messages look suspiciously short. You should be seeing something like this:

Code: Select all

!AUI:120600000000656c02456cf5ec0101010000
!AUI:1606000000006663024543f532fb456cf5ec01010101


Have you enabled keypad address 23? (*196)

I would think you should see some keypad messages regardless of the keypad address being enabled, but not being able to interact with the panel makes me think the address isn't enabled.

[davide123]

Ty for your response and help. Yes, *196 (23) is enabled, I even moved the address to the only other open address *195 (22). Both set as:
code 800 *196 1 0 *99

'E' from the AD2USB shows !ERR: 0 so I think that is ok, just doesn't seem to pull the full messages nor accept input to the keypad, almost like there is some other setting on the panel that isn't yet enabled. I'm reading about GSM/LRR settings (I have a cellular backup installed) and am wondering if something is missing there....

[davide123]

Ok I fixed my issues per this post. Turns out that the AlarmDecoder, or any keypad wired to the Vista 20(p), has trouble being powered externally. I removed external powering of the AD2USB and plugged in to the panel's AUX power. Apparently, the Vista panels need to cross-bus to ground each keypad even when powered externally. So, if you do power the AlarmDecoder externally, you need to connect the external negative wire to the Aux ground. The easiest thing to do I found was just power the AlarmDecoder from the panel's AUX.

Hope this helps someone else.