alarmdecoder.com

Hi Guys,

I am in need of a little help and advice here if I may? I recently purchased the AD2PI module, and have added it to a PI and connected it to my Vista20p panel. I can communicate with the module over serial, both locally and using the ser2sock software.

Problem 1 - the device seems to 'lose' its address setting, is this normal?
When I first connected the device to my Pi and connected to the device, I noticed that the address reported was 00. I changed this to 18 however I notice that whenever I disconnect power to the module, for example powering down and powering up the alarm panel, the configuration is lost and the address reverts back to 00. Is this normal? Can I do anything to have this setting save.

Problem 2 - I don't seem to get any messages from the alarm, am I missing something?
I have checked and double-checked my wiring, and I can connect AD2PI device however I don't seem to get anything back from the alarm. If I use the keypad application (over ser2sock), I get the 'waiting first message' response.

I have enabled the 3rd keypad using *191 01 in installer mode using one of the other keypads which according to the manual (if I am reading it correctly) says that keypad has address 18. I have powered everything down and back up again after doing this however I still don't get anything.

Now I admit I am very new and may be missing something entirely.

Please can anyone offer any advice?

Many Thanks!
Jon

B69CA wrote:Hi Guys,

I am in need of a little help and advice here if I may? I recently purchased the AD2PI module, and have added it to a PI and connected it to my Vista20p panel. I can communicate with the module over serial, both locally and using the ser2sock software.

Problem 1 - the device seems to 'lose' its address setting, is this normal?
When I first connected the device to my Pi and connected to the device, I noticed that the address reported was 00. I changed this to 18 however I notice that whenever I disconnect power to the module, for example powering down and powering up the alarm panel, the configuration is lost and the address reverts back to 00. Is this normal? Can I do anything to have this setting save.

Problem 2 - I don't seem to get any messages from the alarm, am I missing something?
I have checked and double-checked my wiring, and I can connect AD2PI device however I don't seem to get anything back from the alarm. If I use the keypad application (over ser2sock), I get the 'waiting first message' response.

I have enabled the 3rd keypad using *191 01 in installer mode using one of the other keypads which according to the manual (if I am reading it correctly) says that keypad has address 18. I have powered everything down and back up again after doing this however I still don't get anything.

Now I admit I am very new and may be missing something entirely.

Please can anyone offer any advice?

Many Thanks!
Jon

Ok, so you added this to your own pi - did you happen to disable the built-in serial console in our instructions? It sounds like maybe this is spitting garbage to the ad2pi at boot and nuking it's configuration

Code: Select all

 Remove the following entries from /boot/cmdline.txt:

    console=ttyAMA0,115200
    kgdboc=ttyAMA0,115200

Remove the following line from /etc/inittab:

    T0:23:respawn:/sbin/getty -L ttyAMA0 115200 vt100



After that, you will reboot then want to check your address filter mask and ensure it is FFFFFFFF as default

Here is a default configuration:

Code: Select all

!>Keypad Address       (18) :>
!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) :>
!>ZoneTracker track zone restore Y/N: (N) :>
!>Address Filter Mask  (ffffffff) :>
!>Deduplicate          (N) :>
!>Config Bits        (ff00) :>


It sounds like once you get the device configuration sorted (you can send the device a '!' over ser2sock or serial) you should be fine as long as the address you are using is enabled on the panel

Also do make sure your DI and DO are not backwards

I also believe that it is *191 10 for address 18 enable and disable sound, you can verify by checking your programming manual and sending a #191 to view the fields - we have a video of this here: http://www.alarmdecoder.com/wiki/index. ... figuration

Thank you Kevin.

I did indeed have my DI and DO wires reversed which is why I wasn't getting any messages. As soon as I reversed these my messages began to come through. I checked and double-checked these when I installed the device, it just goes to show that when you are concentrating hard, you can still be color blind

The wires took care of the communications issue, however my power-down loose config still remains. I did everything regarding the serial you put but will double check that all again today. Once its up and configured with the address, I can reboot the AD2PI module without an issue, its only when it looses power that I seem to loose the config.

I will double-check the serial settings and everything and just re-confirm that I'm still having the challenge.

Thanks for your help,
Jon

I am having the same problem. I get the following message in Indigo:

Interface Error startComm: Faled connection to socket://192.168.1.114:80. Will retry in 10 seconds

Question: what is the proper sequence for the wires. I assumed they are the same as the AD2USB. Looking from the front of the AD2Pi I connected the wires left to right: yellow, green, red, black. Is that correct?

wideglidejrp wrote:I am having the same problem. I get the following message in Indigo:

Interface Error startComm: Faled connection to socket://192.168.1.114:80. Will retry in 10 seconds

Question: what is the proper sequence for the wires. I assumed they are the same as the AD2USB. Looking from the front of the AD2Pi I connected the wires left to right: yellow, green, red, black. Is that correct?

With the terminal block facing you, from left to right it is:

DO, DI, +, -

I'm not sure what this is: "Interface Error startComm: Faled connection to socket://192.168.1.114:80. Will retry in 10 seconds" where is this message coming from? Port 80 for our appliance is HTTP by default, and Port 10000 is ser2sock by default - I am assuming you are trying to communicate via ser2sock??

I have and Ademco 20P with 8 zones and a AD2Pi. I use Indigo with the AD2USB plugin. All is working fine. I can see all my zones status on my iPhone and can arm and disarm from the iPhone. It is really slick. However, I am having trouble with a new goal as described below.

Goal: Add a zone 9 for a detached shed. I have an insteon door sensor and a variable set that tells me if the door is open or closed

Steps I took: I created Emulate zone expander #1 using the setup process in the alarmdecoder.alarm web app
In Indigo I created an Indigo Managed Virtual Zone as follows:
Zone number: 9
Partition Number: 1
Assign virtual Expansion board address: 7 (ad2usb #1)
Assign virtual Expansion Device number: 1
I setup triggers to change the state of zone 9 based on the shedDoorStatus becoming open or closed

Zone 9 in the device list does not show any state. The wiki at Indigo said I need to setup the Ademco panel to recognize the new zone. I went into programming mode and entered *56. The Ademco programming guide may make complete sense if you are a security installer, but for the home automation enthusiast, I is not clear. Has anyone had experience with this? I feel I am at the 5 yard line.

See this video https://www.youtube.com/watch?v=Jm2dfKDi_ig, it explains it really well step by step!

Thank you, but the video is for adding a wired device to one of the standard 8 zones of the panel. What I am doing is adding a 9th zone. It is a virtual zone. The programming I need is different than what the video shows.

The basic premise is the same, I can't really help you further here unfortunately. Not an alarm installer or programmer myself.

You would still add this as a "wired zone" even though it is virtual, the "zone expander" is added by the AD2USB. This will make zones 9-16 available to program.

As far as I know, the programming is the same, you just substitute your needed numbers over the ones thevideo is using.

Here is a video specifically programming zone expander zones: https://www.youtube.com/watch?v=dQTNiLTRzSo

The devil is in the detail. The settings have to be exactly right. I would think someone has figured this out and made it work and will share how they did it.