AD2Pi Appliance - Check wiring and keypad address

[BravoCharlie]

Spent pretty much all day trying to resolve this and am completely out of ideas. I have a Honeywell/Ademco Vista-20P with 4 keypads. For the initial setup of the AD2Pi Network Appliance I selected Address 20. I configured the alarm panel *193 [1] [0] for the AD2Pi.

I can talk to the AD2Pi but it can't talk to the alarm panel. I changed the keypad at Address 18 to 20 and moved the AD2Pi to 18; no change. I've disconnected and reconnected the wiring twice; no change. Applied all updates; no change. Any ideas?

Opening device ✔
Saving device configuration ✔
Keypad communication (Send) ✘ Check wiring and that the correct keypad address is being used.
Keypad communication (Receive) ⚠ Test timed out.

AlarmDecoder device settings:
Address 20
Configbits 0XFF05
Address Mask 0XFFFFFFFFL
Zone Exander Emulation False False False False False
Relay Emulation False False False False
LRR Emulation False
Deduplicate False
Panel Type ADEMCO
Firmware version V2.2a.8.8
Serial Number FFFFFFFF
Device Flags TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;L2;KE;M2;CB;DS;ER;CR

[kevin]

Do you see messages from the raw stream by telnetting to port 10000?

From the error message I would assume the tx and rx wires are backwards or there is a keypad address conflict, which the above will tell us

[BravoCharlie]

Hey Kevin,

Three things I loved about your reply:

1st - Super quick, thx.

2nd - The certainty that it had to be an address issue or the DI/DO wiring. Thats the assumption I was working on but couldn't figure out.

3rd - Asking me if I had telnetted into the device like that would be one of the 1st steps anyone would take in the 21st century where everything has a graphical UI.

So I went back and did the easiest first, checked the addresses AGAIN. OK. Then I was starting to redo the wiring AGAIN when I noticed 1 strand of wiring had broken off and was jammed in one of the terminals and was shorting across to the other. Problem solved.

If I could make one suggestion, maybe include a section on telnet troubleshooting on the website or maybe a sticky on the forum.

Thank you very much for your help. It was exactly what I was looking for.

Bob