alarmdecoder.com

Hi,
I had upgraded 2.2a.8.6 because I was not receiving all events. After upgrade, a command sent to the ad2usb 2.2+ rebooted it, so put the project on the side for a while.
I just upgraded to the latest 2.2a.8.8 and still having the same issue (after multiple reboots, usb reset, etc.).
This has worked for years before with no problem. I just moved and rewired the whole thing. Same config, same panel , etc.
The device does:
- rapid blinking
- reboot when sending a command (such as V or !)

Strangely, alarmdecoderkeypad could get a version number before doing the latest upgrade.


Log:
-bash-4.3$ nc localhost 8888
!SER2SOCK Connected
!SER2SOCK SERIAL_CONNECTED
!
!no�!no�!sn:!sn:ffffffff
!boot.ffffffff
!boot.......................................
!wait

!wait
!load
!load
V
!no�!no�!sn:ffffffff
!boot!sn:ffffffff
!boot........................................
!wait

Log of (end of) upgrade to 2.2a.8.8 :
11/19/2017 9:22:10 PM Sending :10EF300083B3F42667DBBFCB97CD85FB5BFC56E93B
11/19/2017 9:22:10 PM !wait
11/19/2017 9:22:10 PM Sending :10EF4000F9BD74D0FE2A97F582C4EE148E43CE8CA0
11/19/2017 9:22:11 PM !load
11/19/2017 9:22:11 PM Sending :0200000400F00A
11/19/2017 9:22:11 PM !load
11/19/2017 9:22:11 PM Sending :01000000FF00
11/19/2017 9:22:11 PM !ae
11/19/2017 9:22:11 PM Sending :00000001FF
11/19/2017 9:22:11 PM !ceÿ!ae
11/19/2017 9:22:14 PM !ceÿ!sn:ffffffff
11/19/2017 9:22:14 PM !boot!sn:ffffffff
11/19/2017 9:22:18 PM !boot........................................
11/19/2017 9:22:18 PM Uploading done resetting the AlarmDecoder and waiting for Ready.
11/19/2017 9:22:19 PM !wait
11/19/2017 9:22:19 PM Restoring configuration to the AlarmDecoder
11/19/2017 9:22:19 PM !wait
11/19/2017 9:22:19 PM !load
11/19/2017 9:22:19 PM !load
11/19/2017 9:22:28 PM Timeout waiting for !Ready message. Config not restored.
11/19/2017 9:22:29 PM Sending '\r\n' command to the AlarmDecoder
11/19/2017 9:22:32 PM !noÿ!noÿ!sn:ffffffff
11/19/2017 9:22:32 PM !boot.!sn:ffffffff
11/19/2017 9:22:36 PM !boot.......................................
11/19/2017 9:22:36 PM !wait
11/19/2017 9:22:36 PM !wait
11/19/2017 9:22:36 PM !load
11/19/2017 9:22:36 PM !load
11/19/2017 9:31:23 PM !sn:ffffffff
11/19/2017 9:31:23 PM !boot!sn:ffffffff
11/19/2017 9:31:27 PM !boot........................................
11/19/2017 9:31:27 PM !wait
11/19/2017 9:31:27 PM !wait
11/19/2017 9:31:28 PM !load
11/19/2017 9:31:28 PM !load


Any idea what's going on ?
thanks,
Bob

Hi Bob,

Looks like a possible failed firmware upload, please try again - you can't brick it, but sometimes this happens during uploading firmware

I'll try again, no problem.
All upgrades I've done take way more than 20 minutes, hope that's ok. (alarmdecoderkeypad -> ser2sock)
Thanks

That doesn't seem normal... any chance you can use the python uploader? If you continue to have issues, please email support.

thanks Kevin
Upgrade was successful. Interestingly, ad2-firmwareupload gave

Code: Select all

Flashing device: localhost:8888 - 115200 baud
Firmware: ademcoemu_V2-2a-8-8.hex
Rebooting device..
Waiting for boot loader..
Uploading firmware.
Error: Checksum error in ademcoemu_V2-2a-8-8.hex

when using the socket, but was successful via direct USB.

One problem solved.

thanks again
Bob

Certainly weird on the socket doing that, but I suppose it could happen... can you make sure your ser2sock configuration for raw device mode is enabled? Also, maybe you're running an older version without a couple bugfixes??, check github

I checked and I was running the latest version.
I was not running with raw device mode, that may be reason. Will try next upgrade.
Hope this helps others in the future.

Thanks for the hints Kevin