alarmdecoder.com

I received my AD2USB and immediately tried it out on my Ademco Vista 20SE unit connecting to it via a Raspberry Pi and it worked! Yay!!

I then took the Rapsberry Pi with the AD2USB to my nephew's house and connected it to his Vista 10SE. Sadly it didn't work.

I verified the wiring several times and even reconnected everything thinking that maybe I had a loose connection. It’s wired as follows:
GND wired to 4
12V wired to 5
DI wired to 6
DO wired to 7

I use minicom (ver. 2.6.1) on the Raspberry Pi and can connect to the AD2USB device. I verified that the address was still set to 31 and as I needed to do with the 20SE, I set the Hardware Flow Control to No in minicom:

Serial Device : /dev/ttyUSB0
Lockfile Location : /var/lock
Callin Program :
Callout Program :
Bps/Par/Bits : 115200 8N1
Hardware Flow Control : No
Software Flow Control : No


I do not receive any messages from the 10SE alarm panel when I set the alarm to Stay from one of it's existing keypads or when I set the alarm panel to Off. When I press a key I get:

!Sending..done
or
!Sending...done

I reversed the DI and DO (I was running out of ideas) and that didn’t seem to help. It was odd though as the “!Sending..done” message seemed to respond faster. I then changed the wires back.

Attached below, I started minicom, pressed the = key to reboot the AD2USB and then hit several keys (1, 3, 4,3, 3) and then entered the ! key to get the configuration information:
=======================================================================
pi@raspberrypi:~$ minicom -b 115200 -o -D /dev/ttyUSB0

Welcome to minicom 2.6.1

OPTIONS: I18n
Compiled on Apr 28 2012, 19:24:31.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys

(Here’s where I hit =)
!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.

(Here’s where I entered 1, 3, 4,3, 3)
!Sending..done
!Sending..done
!Sending...done
!Sending...done
!Sending...done

(Here’s where I pressed the ! key)
!>Keypad Address (31) :>
!>Config Bits (ff00) :>
!WARNING. Do not enable a module if the physical module exists on the system.
!Zone Expanders Y/N Max allowed: 02
!>expander module #01 ZN 09-16 (N) :>
!>expander module #02 ZN 17-24 (N) :>
!>expander module #03 ZN 25-32 (N) :>
!>expander module #04 ZN 33-40 (N) :>
!>expander module #05 ZN 41-48 (N) :>
!Relay Modules Y/N Max allowed: 04
!>relay module #01 (N) :>
!>relay module #02 (N) :>
!>relay module #03 (N) :>
!>relay module #04 (N) :>
!>Emulate Long Range Radio Y/N: (N) :>
!>Address Filter Mask (ffffffff) :>
!>Deduplicate (N) :>
!Reading configuration.
!UART init.
=============================================

I've read the Quick start guide several times and watched the videos. I reviewed the FAQs and the trouble shooting guide but was not able to find anything that resolved the issue.

Unfortunately I am locked out of the Installer code. Powering on the panel and holding down the #* keys doesn't work. I need to run the Master Code finder but I can't do that until I get the AD2USB working on the 10SE.

Thinking that the problem might be with the Raspberry Pi, I connected my Mac to the AD2USB and it behaved the exact same way.

Can you suggest what I should do next? I installed AlarmDecoder Keypad on my Mac but haven't been back to his house to try it yet. They live 45 minutes away. I do have remote connectivity to the unit via the rPi.

Sometimes there are some timing quirks with the older SE panels with older firmware - can you confirm that this particular SE panel has Alpha keypad support?

If you could load up the latest beta firmware from http://www.alarmdecoder.com/wiki/index.php/Firmware (2.2a.8) and enter @48 from your terminal, this will put the AD2USB into "debug" mode where it shows the bits of all communication. If you could leave @48 enabled for long enough to capture traffic (please include sending keys such as 1234 in the stream)

Copy and paste some of that output to ad2usb@support.nutech.com

You can enter @00 to exit debug mode

This will help us determine any communication issues with the 10SE panel.

I upgraded the firmware, ran debug and sent the email.

Thanks for your help!

Ken

I also have an older 10SE panel and my AD2USB device works perfectly. If there is anything needed to help with troubleshooting, let me know..

-- Kevin

Thanks Kevin.

I worked with Sean this week and he determined that the AD2USB appeared to be defective. I took it back to the other location and tried it on my 20SE again and now it failed on the 20SE also.

I sent it to him via USPS for repair yesterday as he requested. I'll update the ticket when I get it back.

Thanks again.

Ken

PS. I really appreciate your great support!!!

Hi Sean,

I installed the repaired AD2USB you sent and it works great!

On a side note, I have never experienced such great customer support from a company. You were very knowledgeable and patient and resolved the issue in as little time as possible. I really appreciate your dedication to providing excellent support!!

Thanks again!

Ken