Older AD2USB not sending correctly?

[hamw]

I have used these devices for almost 10 years. currently have one working well at my home, and have another that I've hooked up to the alarm system at another house. that one is not working correctly. This is on a new 20p system. The chip reads WA20p Rev 10.23. The keypads set the alarm with out a problem.

The AD2USB reads the config and the panel messages without a problem, but I cannot set the alarm despite all I've tried. The terminal shows "sending....." for about 6 seconds and nothing happens. Here's some output to show it is working, at least to receive.


boot from monogui:

Code: Select all

10/4/2020 9:55:10 AM !sn:ffffffff
10/4/2020 9:55:14 AM !boot....................
10/4/2020 9:55:14 AM !
10/4/2020 9:55:15 AM !Ademco Keypad Emulator V2.2a.6
10/4/2020 9:55:15 AM !Copyright (C) 2008-2010 Nu Tech Software Solutions, Inc.
10/4/2020 9:55:15 AM !Reproduction without permission is prohibited
10/4/2020 9:55:15 AM !By Sean Mathews <drwho at f34r.com>
10/4/2020 9:55:15 AM !For support email general@support.nutech.com
10/4/2020 9:55:15 AM !www.NuTech.com
10/4/2020 9:55:15 AM !Reading configuration.
10/4/2020 9:55:15 AM !UART init.
10/4/2020 9:55:23 AM !Ready. Press ! for configuration.


!
!>Keypad Address       (01) :>
!>Config Bits        (c081) :>

!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  (c0181e8c) :>

!>Deduplicate          (Y) :>

!Reading configuration.
!UART init.


Trying to set the alarm:

Code: Select all

!AUI:1606000000006663024543f531fb456cf5ec01020106
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
!AUI:120600000000676c02456cf5ec0101010000
!AUI:1606000000006063024543f531fb456cf5ec01010101
[0000000100000000----],007,[f70000ff1007000008020000000000],"FAULT 07        DOWNSTAIRS MOTIO"
!AUI:120600000000616c02456cf5ec0101010000
!AUI:1606000000006263024543f531fb456cf5ec01020106
!AUI:120600000000636c02456cf5ec0101010000
!AUI:1606000000006463024543f531fb456cf5ec01010101
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending......done
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending......done
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending......done
!Sending......done
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "
!Sending......done
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED****  Ready to Arm  "



The config is Indigo, ser2Sock and AD2USB with ver 2.2a.6, which seems to be the Indigo compatible firmware. I re-uploaded the firmware with no improvement

Code: Select all

10/4/2020 1:08:43 PM Sending :00000001FF
10/4/2020 1:08:46 PM !okÿ!sn:ffffffff
10/4/2020 1:08:50 PM !boot....................
10/4/2020 1:08:50 PM !
10/4/2020 1:08:50 PM !Ademco Keypad Emulator V2.2a.6
10/4/2020 1:08:50 PM Uploading done resetting the AlarmDecoder and waiting for Ready.
10/4/2020 1:08:51 PM !Copyright (C) 2008-2010 Nu Tech Software Solutions, Inc.
10/4/2020 1:08:51 PM Restoring configuration to the AlarmDecoder
10/4/2020 1:08:51 PM !Reproduction without permission is prohibited
10/4/2020 1:08:51 PM !By Sean Mathews <drwho at f34r.com>
10/4/2020 1:08:51 PM !For support email general@support.nutech.com
10/4/2020 1:08:51 PM !www.NuTech.com
10/4/2020 1:08:52 PM !Reading configuration.
10/4/2020 1:08:52 PM !Init EEPROM
10/4/2020 1:08:52 PM !UART init.
10/4/2020 1:08:53 PM !Ready. Press ! for configuration.
10/4/2020 1:08:53 PM Send>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
10/4/2020 1:08:53 PM Sending 'V' command to the AlarmDecoder
10/4/2020 1:08:53 PM [0000000100000000----],009,[f70000ff1009000008020000000000],"FAULT 09 REAR   SLIDING DOOR    "
10/4/2020 1:08:53 PM !>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
10/4/2020 1:08:53 PM !setting ADDRESS 31
10/4/2020 1:08:53 PM !setting CONFIGBITS c081
10/4/2020 1:08:53 PM !setting LRR emulation OFF
10/4/2020 1:08:53 PM !setting EXPANDER emulation NNNNN
10/4/2020 1:08:53 PM !setting RELAY emulation NNNN
10/4/2020 1:08:54 PM !>setting MASK c0181e8c
10/4/2020 1:08:54 PM !>setting DEDUPLICATE ON
10/4/2020 1:08:54 PM !CONFIG>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
10/4/2020 1:08:54 PM !VER:ffffffff,V2.2a.6,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;LR;KE;MK;CB
10/4/2020 1:08:54 PM Found Version String
10/4/2020 1:08:55 PM [0000000100000000----],009,[f70000ff1009000008020000000000],"FAULT 09 REAR   SLIDING DOOR    "
10/4/2020 1:08:55 PM Sending 'C' command to the AlarmDecoder
10/4/2020 1:08:55 PM !>
10/4/2020 1:08:55 PM !CONFIG>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
10/4/2020 1:08:55 PM Found and saving Config String
10/4/2020 1:08:56 PM Sending '\r\n' command to the AlarmDecoder
10/4/2020 1:08:59 PM [0000000100000000----],009,[f70000ff1009000008020000000000],"FAULT 09 REAR   SLIDING DOOR    "


I checked the setup with MonoGUI and disconnected the AD2USB completely and reconnected. All appears to be working, but trying to send to set the alarm does not work. I've posted some details on the Indigo forum, and rather than repost here, pls click this link:

https://forums.indigodomo.com/viewtopic ... 78#p195236

Of course, I can repost the conversation if needed.

It's a new 20p panel. The wiring is correct -- I tried reversing the data wires anyway, and it did not read... any help would be appreciated. I also recognize it is possible the unit has somehow failed and I need a new one, but before taking the plunge would like to be sure that is the issue.

Thanks very much!!!!

[mathewss]

I thought indigo was fixed to work with newer firmware but thats fine. That one has fewer features but is very stable.

I did not see your configuration settings.
Please send them.

Probably the address is wrong.

If you see messages on an Ademco 15/20p panel but can't send its one of the following.

- Keypadd address is wrong or not programmed in panel
- Conflict with another keypad address
- Green wire DI is faulty

Best
SM.

[hamw]

Just for thoroughness I uploaded the latest stable firmware here....

Code: Select all

!ae
!00FF:0000
!ok
!sn:ffffffff
!boot....................
!
!Ademco Keypad Emulator V2.2a.8.8
!Copyright (C) 2008-2015 Nu Tech Software Solutions, Inc.
!Reproduction without permission is prohibited
!By Sean Mathews <coder@f34r.com>
!For support email AlarmDecoder@support.nutech.com
!www.AlarmDecoder.com
!Reading configuration.
!Init EEPROM
!UART init.
!Ready. Press ! for configuration.
!>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
!CONFIG>MODE=A&CONFIGBITS=c081&ADDRESS=31&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=Y
!Reading configuration.
!UART init.
!VER:ffffffff,V2.2a.8.8,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;L2;KE;M2;CB;DS;ER;CR


still no joy. Would appreciate any help.

[mathewss]

Config bits are wrong and so is the mask.
Unless maybe the mask was done on purpose as it is a multi partition setup?
Maybe a result of upgrade from a very old firmware.

Stock settings MODE=A&CONFIGBITS=ff04&ADDRESS=18&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=N

Config bits should be ff04
mask should usually be ffffffff
Your address is 18 not sure if that matches your panel programming.

[hamw]

Thanks for the quick reply! This unit previously existed in my multi partition home. Have a single partition in this house.

You’re right, the panel should be 31, but it didn’t work when it was 31 before...

The AD2USB Indigo plug-in reads the new firmware panel as “A”, which is unaddressable. So I’ve reverted back to the 2a.6 for now.

How do I reset the unit to factory so the mask and flags are correct?

[mathewss]

What you have now is not a SE panel It is a 20P panel so Address 31 should not be used. 31 is only for SE panels and you would not see messages from an SE panel if the Address was set to 18 on the AD2.

RESET is an undocumented config option on newer firmware. Dont think it was in ".6" using putty or custom command from GUI app send CRESET=Y and Enter.

So for your old panel if it was an SE you never had to set an address in programming mode on the panel. On this panel you will. On a side note a recent 20P panel I got with the latest firmware has all keypads enabled by default figure that needed to happen a few decades ago but it was a good improvement IMHO on the panel in recent releases.

[hamw]

Do you think there is a proper address already in this panel? It is, AFAIK, brand new having been just installed. Rev 10.23.

I did upload the latest firmware and did !CRESET=Y with the following results:

!Reading configuration.
!UART init.
[10000001000000003A--],008,[f70000ff1008001c08020000000000],"****DISARMED**** Ready to Arm "
!>
!CONFIG>MODE=A&CONFIGBITS=ff04&ADDRESS=18&LRR=N&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=Y
!Reading configuration.
!UART init.
[10000001000000003A--],008,[f70000ff1008001c08020000000000],"****DISARMED**** Ready to Arm "
!>ADDRESS=18&EXP=nnnnn&REL=nnnn&LRR=Y&DEDUPLICATE=Y
!CONFIG>MODE=A&CONFIGBITS=ff04&ADDRESS=18&LRR=Y&COM=N&EXP=NNNNN&REL=NNNN&MASK=ffffffff&DEDUPLICATE=Y
!Reading configuration.
!UART init.
[10000001000000003A--],008,[f70000ff1008001c08020000000000],"****DISARMED**** Ready to Arm "
!Sending......done
!Sending......done
[10000001000000003A--],008,[f70000ff1008001c08020000000000],"****DISARMED**** Ready to Arm "

/quote]

Which I think is the config bits and mask you are looking for. However, when I downgraded it back to 2a.6 it read:

!ok
!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.
!Init EEPROM
!UART init.
!Ready. Press ! for configuration.
!>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
!setting ADDRESS 31
!setting CONFIGBITS c081
!setting LRR emulation OFF
!setting EXPANDER emulation NNNNN
!setting RELAY emulation NNNN
!>setting MASK c0181e8c
!>setting DEDUPLICATE ON
!CONFIG>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y
!VER:ffffffff,V2.2a.6,TX;RX;SM;VZ;RF;ZX;RE;AU;3X;CG;DD;MF;LR;KE;MK;CB
[1000000100000000----],008,[f70000ff1008001c08020000000000],"****DISARMED**** Ready to Arm "
!>
!CONFIG>ADDRESS=31&CONFIGBITS=c081&LRR=N&EXP=NNNNN&REL=NNNN&MASK=c0181e8c&DEDUPLICATE=Y

Not sure which I should use, or why the 2a.6 firmware would read the apparently wrong config bits even after the unit was reset with the CRESET=Y command. The AD2USB plugin reads the new firmware keypad address as "A" as noted.

[mathewss]

If you have no other keypads you can use 16. It will be enabled by default. Best to just get into programming mode if you can with another keypad or the AD2 on address 16 with all other keypads disconnected. Not every time but often they install one keypad at 16 so we have to disable it to use 16. Other installers never use 16 so they can connect easy and do maintenance and not worry about a conflict.

Try address 16.
As for the config settings just use ! and enter ff04 and ffffffff for bits and mask and the rest should be good. Also turn off deduplicate this is off by default and I see it turned on as well switching to older firmware. All other settings look good.

If you don't have your installer code it is not hard to find.

Best
SM

[hamw]

I successfully made the changes to the config bits and mask, checked the three existing keypads which were 16, 17 and 18, and also checked continuity for each of the wires from the AD2USB to the panel. Everything checks out. Nonetheless it will not transmit. Guess I will order a new one and see how that works.

Thanks for the support and what has been a great product.

[mathewss]

If it failed I will send you a replacement.

Load the debug firmware using the free gui app on my download page. This will have debug firmware.

Use custom command on log tab of gui app. Send @48

Then oress the * on the keypad gui app and copy paste log tab and send to me here or email support ad2usb@support.nutech.com

Best
Sean M