alarmdecoder.com

I am trying to hook up an AD2PI to a DSC1832. Alarm Decoder is completely new to me and I am finding the documentation to be a little hard to follow for the AD2PI.

Here is what I've done:
1.Hooked up the wiring as it is shown on the main page with green and yellow reversed than on a usual Ademco alarm.
2.Installed the rasbian image provided on the AlarmDecoder website.
3.Logged into the alarm decoder control panel page at the Raspberry Pi's ip address.
4.Run the setup, left all settings as default, when I click DSC all options disappear, click next.
5.Runs test, succeeds at opening the device, and sending device configurations.
6.Fails at Keypad communication (send and receive).

I have read some posts about needing to run beta software, but I do not know how to check what version I am running on the Raspberry Pi or how to do the upgrade. Any help would be appreciated!

You can verify the version of the firmware on the ad2pi by connecting to port 10000 of the ad2pi with telnet and issuing a 'V' command

You can upload new firmware from your PC with the GUI Keypad Software (available in downloads under documentation) or you can do it from the command line of the raspberry pi with the ad2-firmwareupload utility located in /opt - just download the beta firmware from here (http://www.alarmdecoder.com/wiki/index.php/Firmware) instructions are also provided there!

You will then be able to truly select DSC in the setup process.

Thanks so much for the help. That got me much further.

When I use the Keypad GUI, the program starts and the immediately closes in Windows 8.1 so I went the upgrade utility route via ssh.

I execute:

pi@alarmdecoder /opt/alarmdecoder/bin $ ad2-firmwareupload ademcoemu_V2_2a_8.zip /dev/ttyAMA0


I get the follow error:

Flashing device: /dev/ttyAMA0 - 115200 baud
Firmware: ademcoemu_V2_2a_8.zip
Rebooting device..
Waiting for boot loader..
Traceback (most recent call last):
File "/usr/local/bin/ad2-firmwareupload", line 61, in <module>
main()
File "/usr/local/bin/ad2-firmwareupload", line 56, in main
alarmdecoder.util.Firmware.upload(dev, firmware, handle_firmware)
File "/opt/alarmdecoder/alarmdecoder/util.py", line 156, in upload
do_upload()
File "/opt/alarmdecoder/alarmdecoder/util.py", line 76, in do_upload
if line[0] == ':':
IndexError: string index out of range


Any ideas? Thanks again!

You have stopped ser2sock as well as anything that may be using the serial port?

I made sure it is disabled. Apparently it was already stopped? Either way I get the same error.

pi@alarmdecoder /opt/alarmdecoder/bin $ service ser2sock stop

Stopping instantiation ser2sock of ser2sock...

Script name : ser2sock
Executable file : /usr/local/bin/ser2sock
PID file : /var/run/ser2sock.pid

Already stopped - Return Value = 1

I will keep poking around in the morning.

To be sure nothing is using the port try this command 'lsof -n | grep ttyAMA'

It does sound like it is in use by something.

Re
Sean M

Oh I see it - you are trying to flash the .zip file - you will want to unzip that and flash the .hex file

Duh! It upgraded as soon as I unzipped the file.

I keep thinking if I get passed this hump then it will work, but now I'm stuck again.

I did the upgrade and confirmed through the ssh that the version is correct:

VER:ffffffff,V2.2a.8a23,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;LR;KE;MK;CB;DS

Now when I run through the webapp to configure for a DSC, I still do not get options like we do for an Ademco device.

If I continue anyhow, I get the following error messages:

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.

There are not the options for DSC as there are Ademco for one - do make sure your DI and DO wires are hooked to the panel correctly. You can also setup the ad2pi manually through ser2sock by issuing a '!' key - there you can manually select DSC mode and test communications by trying to arm and disarm.

Thanks again to you both for all the help!

After all the tinkering, I did have a lose wire. Now things are working great!