AD2PI with DSC1832

[ciscotwo]

I too am using a DSC panel and when I try to flash the firmware I get the following response..


i@alarmdecoder /opt/alarmdecoder/bin $ ad2-firmwareupload ademocoemu_V2_2a_8.hex /dev/ttyAMA0 ^@Flashing device: /dev/ttyAMA0 - 115200 baud
Firmware: ademocoemu_V2_2a_8.hex
Rebooting device..
Traceback (most recent call last):
File "/usr/local/bin/ad2-firmwareupload", line 7, in <module>
execfile(__file__)
File "/opt/alarmdecoder/bin/ad2-firmwareupload", line 61, in <module>
main()
File "/opt/alarmdecoder/bin/ad2-firmwareupload", line 56, in main
alarmdecoder.util.Firmware.upload(dev, firmware, handle_firmware)
File "/opt/alarmdecoder/alarmdecoder/util.py", line 147, in upload
read_until('......', timeout=15.0)
File "/opt/alarmdecoder/alarmdecoder/util.py", line 122, in read_until
raise TimeoutError('Timeout while waiting for line terminator.')
alarmdecoder.util.TimeoutError: Timeout while waiting for line terminator.
pi@al

Any suggestions? I also made sure the ser2sock was stopped and I unzipped the firmware file.

Thanks!

[mathewss]

Hmm.. Ok can you see if your AD2* is still alive or is the firmware on it erased or damaged? Is the LED flashing.

I am presuming this is a Ad2Pi and as such should already have been running DSC capable firmware.

Anyway its not possible to brick the Ad2Pi board but it does require a little help in recovery if the firmware is damaged and the unit is not having a heartbeat.

Re
SM

[ciscotwo]

I re-imaged the SD card with a copy from your website. And from the image I was able to update the firmware to the DSC version as shown below

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


When i logon to the webpage, I get a little further. as seen below.

Device Testing
Opening device ✔
Saving device configuration ✔
Keypad communication (Send) ⚠ Test timed out.
Keypad communication (Receive) ⚠ Test timed out.

the Di is connected to the Yellow
DO is connected to Green
+ Red
- Black

Is there something in the logs I can look at? See below.

2016-03-20 19:37:01,362 INFO: Attempting to reconnect to the AlarmDecoder [in /opt/alarmdecoder-webapp/ad2web/decoder.py:452]
2016-03-20 19:37:01,841 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:315]
2016-03-20 19:37:36,180 INFO: AlarmDecoder device was closed. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:327]
2016-03-20 19:37:36,443 INFO: AlarmDecoder device was closed. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:327]
2016-03-20 19:37:36,473 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:315]
2016-03-20 19:43:48,341 INFO: AlarmDecoder device was closed. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:327]
2016-03-20 19:43:48,597 INFO: AlarmDecoder device was closed. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:327]
2016-03-20 19:43:48,624 INFO: AlarmDecoder device was opened. [in /opt/alarmdecoder-webapp/ad2web/decoder.py:315]

I also did a diagnostic and this is what showed up:
distutils PIL speaklater
cookielib
google
compileall html5lib dateutil ujson
chardet optparse Crypto
requests

Cookie dns simplejson imghdr
pycurl
FixTk sndhdr distlib
getopt csv urllib3 lxml
colorama chump bz2 xmlrpclib

Any suggestions?

[kevin]

Please see if you can communicate with the alarm directly from the device properly - if you are running ser2sock, telnet to port 10000 of the raspberry pi - here just enter keystrokes and see if you are able to receive/send messages to the alarm. If you are not running ser2sock, then you will connect directly to /dev/ttyAMA0 at 115200 baud - try ser2sock first if using our image.

[ciscotwo]

Hello,

I utilized telnet to get into the RPI with the 10000 port. Here is what was generated.


!>
!CONFIG>MODE=D&CONFIGBITS=ff00&ADDRESS=01&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N
!Reading configuration.
!UART init.
!>ADDRESS=1&CONFIGBITS=ff00&MASK=ffffffff&EXP=NNNNN&REL=NNNN&LRR=N&DEDUPLICATE=N&MODE=D
!setting ADDRESS 01
!setting CONFIGBITS ff00
!>setting MASK ffffffff
!setting EXPANDER emulation NNNNN
!setting RELAY emulation NNNN
!setting LRR emulation OFF
!>setting DEDUPLICATE OFF
!CONFIG>MODE=D&CONFIGBITS=ff00&ADDRESS=01&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N
!Reading configuration.
!UART init.
!Sending.....done
!Sending.....done

thoughts?

[kevin]

If you are not seeing messages from the panel, and are timing out on sending, I have to suggest looking at the DI and DO wiring

If that doesn't work, please retry flashing the latest stable firmware (maybe it didn't take correctly after the failed flash)