Procedure to change AD2USB device address

[Simon]

Please be gentle with a NOOB helping someone get set up with their Vista 15P and AD2USB

I note from the "Configuring Your AD2USB" section in the manual that by default the AD2USB is configured for address 18. This is of significant to my particular installation because it has 3 keypads, with security panel addresses 17, 18 and 19. I have read the user manual, browsed the FAQ, watched the excellent videos and got some hints. However I'm finding this part of the procedure still a bit confusing.

To avoid any conflict, i.e. my keypad and the AD2USB "fighting over address 18" a.k.a. address contention, I understand there is a need to change the AD2USB device address. In my case, address 20 would seem to be the logical choice.

Q1: WHEN SHOULD THE AD2USB ADDRESS CHANGE BE MADE?

I followed through on the Mac help video, and at around 7:30 there is the explanation about simply clicking within the GUI to change the device address. Judging from the video, the AD2USB is connected to the alarm system at this time.

Also the manual then reads: "To do this just press ! in your terminal program to configure the AD2USB and set the address". So if I were to follow what is suggested by the manual, it would have me (1) connect the AD2USB to the panel, then (2) connect the AD2USB to the computer, then (3) resolve the address 18 contention by pressing !.

However I'm wondering whether it would make more sense (read: avoid conflict and potential damage) to do this as (1) connect the AD2USB to the computer, (2) pre-empty any content by setting the new address, then (3) connecting the AD2USB to the computer.

Q2: HOW TO CHANGE THE ADDRESS?

The Windows video (at about 6:00) seems to walk the user through this procedure with PuTTY, which ties in to the user manual mentioning pressing !. However there was no demo of a GUI-based version of this... compared to the MAC video, which showed a GUI where the user simply selected the new AlarmDecoder address.

I'm thinking it would be best to use the GUI, and in my case select 20. Can this be done on Windows through a GUI, just like the Mac version?


Q3: ARE ANY PANEL CHANGES REQUIRED?

Is it really as simple as:
- Remove from packaging
- Wire it up, first panel then plug in to USB (or other way around?)
- Install Mac (Mavericks) software
- Make the change of address from 18 to 20 as indicated in the video
- Start using!

... or is there something else required e.g. additional programming at the control panel?

Many thanks in advance for the patience and help.

[kevin]

You can change the address on the device any time through the GUI. Just like the Mac video shows.

Unfortunately, it does need to be wired to the alarm panel for power at the minimum to do this.

You will have to enable the address on your alarm panel which is in the FAQ under our Documentation

Thanks!

[Simon]

With your advice, I have wired in my AD2USB in to the panel to get the power. When I switch on the system, I get the green flashing LED on the device. I've plugged in the USB to my Mac running 10.9.4 (Mavericks). Under more info, system report, USB, the system reports that an FT230X Basic UART is present and has a Version 10.00 and serial number DJ005XTJ. So far so good.

On the Mac installation video at about 6:30, the demonstrator runs the AlarmDecoder app and then selects the Configure option. I select "Serial & Socket" tab and have "Serial Port Enabled" checked. I then look at Port Name: this currently has the default "COM4". On the drop down however there are many options but not one looking like /dev/tty.usbserial-DJ005XTJ. (The baud rate option is 115200, as by default.) In the log, it reports "PM Opening com port: 'COM4'".

So I suspect at this point things are a bit broken. However to make sure, on the Setup AlarmDecode tab, I try to change the AlarmDecoder address to 20. (See earlier in the post.) When I click on Upload Settings to AlarmDecoder, the application quits unexpectedly.

How should I proceed?

====
Starting AlarmDecoderApp build #2.0.10.23844
05/09/2014 2:18:15 PM Loding modules. To remove modules use the modules tab under the about menu
05/09/2014 2:18:15 PM Example V1.0 initialized
05/09/2014 2:18:15 PM keypad V1.0 initialized ()
05/09/2014 2:18:15 PM MyStuff V1.0b initialized
05/09/2014 2:18:24 PM Waiting for communication to AlarmDecoder to open
05/09/2014 2:18:24 PM Opening com port: 'COM4'
====

And the screen is sitting there with "Waiting For AlarmDecoder Communications To Open".

[Simon]

Supplemental information... So I ran this on a virtualized PC on my Mac, and did a Windows install. Once I changed the com port from the default COM4 to the one in use on my virtual PC (COM3) then now I get the message "Waiting for message"... and a few moments later, I'm up and running. So at least that proves that e.g. the unit is working, the USB cable is working, the connection to the control panel is working.

Still, I should be able to get this running on the Mac...

[kevin]

Did you install the FTDI drivers? I know one of our videos says not to if you are using a specific version of OSX, however it has been my experience that you should still install the drivers.

[Simon]

Back on the Mac... no, I did not install the FTDI drivers because I'm running Mavericks.

(1) The "Mac" installation video at 2:10 says that Apple includes them so don't bother.
(2) As indicated in my first paragraph above, under more info, system report, USB, the system reports that an FT230X Basic UART is present and has a Version 10.00 and serial number DJ005XTJ.

Anyway:

(1) http://www.ftdichip.com/Drivers/VCP.htm
(2) Download the Mac OS x64 2.2.18 driver
(3) Double click FTDIUSBSerialDriver_10_4_10_5_10_6_10_7

Now when I restart the Mac application, it does appear. So when using Mavericks, the drivers do exist... however not with the enumerators required but the Mac AlarmDecoder application. This solves the issue, as I am now up and running.

[kevin]

I know one of our videos says not to if you are using a specific version of OSX, however it has been my experience that you should still install the drivers.

Glad this worked for you.