Sec. 1) Virtual Keypad (GUI) Software

For windows you need Gtk# for .NET and you need to have Microsoft .NET 2.0 or later installed

First install GTK# from this URL
www.go-mono.com/mono-downloads/download.html
Select your operating system from the given choices - example: Select windows. A new set of links will be presented - from here, download the Gtk# for .NET.


Optional and probably not needed by most
Microsoft .Net 2.0 Redistributable:
www.nutech.com/images/fbfiles/files/dotnetfx.exe
Microsoft .Net 4.0 Redistributable:
www.nutech.com/images/fbfiles/files/dotnetfx40.exe


The ad2usbgui package
Places the contents of this zip someplace modify the config file and then you can just run the exe file by double clicking on it in explorer.

v2.0.6 Windows,Linux, Other .Net 4.0


v2.0.6 Mac OSX Bundle


OLD v2.0.5 Windows,Linux, Other .Net 3.5


Special Build v2.0.6 Windows,Linux, Other .Net 3.5


OLD 2.0.1 Windows, Linux, Other .Net 2.0



Sec. 2) Firmware for the ad2usb boards

You need firmware V2.1f.09 or later to make the most of this version. The latest firmware can be downloaded further down in this post. Once you have downloaded the firmware file, place it on your system someplace and use the MonoGUI or the Console Upload Utility to upload to your firmware. If the ad2usb board does not respond after uploading wait a minute and the reset the board using the new "Reset" button on the logs tab.




After completing a firmware update you MUST reset your configuration on the device by entering ! in a terminal connected to the AD2USB com port

Make sure you select the firmware version that is correct for your ad2usb board. The following two sections will help you determine which board you have and provide links for the appropriate software.

Sec. 2.1) Firmware for V2.0 ad2usb boards


You can identify the V2.0 boards by squarish USB-B connector.

This firmware version V2.1f_10 fixes a problem in V2.1f.0e where the board could potentially jump into SERIAL mode and drop communications to the USB port. If you are using V2.1f.0e you need to update to version V2.1f_10 .

NOTE: Version V2.1f_10 requires that a JUMPER and place on the J3 connector on the board. You must connect pins C3-C4 for USB or C4-C5 for SERIAL output. If you need to run firmware V2.1f.0e you can jumper C3 to GND to resolve the mode change problem.



Older firmware versions are also available:







Sec. 2.2) Firmware for V2.2 - V2.3a ad2usb boards


You can identify the V2.2 - V2.3a boards by the Mini-USB Connector.

Firmware version 2_2a_4 contains three new features not available in previous releases, and not available on the v2.0 boards.

• Keypad Address Mask:This features allows you to select specific keypad addresses to listen to. The keypad address mask is the same masking that the AD2USBGUI uses under "Configuraiton->General->Keypad Address Mask. This is then converted into a 32bit hex number ie ffffffff
  
  From the MSB(left) to the LSB(right) of this 32 bit word the address of each device is as follows
  7,6,5,4,3,2,1,0,15,14,13,12,11,10,9,8,23,22,21,20,19,18,17,16,31,30,29,28,27,26,25,24


• Long Range Radio (LRR) Emulation:The availability of a LRR device in the alarm system causes the panel to send messages containing the user code used to arm/disarm the panel. If a real LRR is not present, this feature allows the ad2usb to become a virtual LRR.


• Deduplication:The availability to remove repetitive messages. This in conjunction with the Address Mask will remove duplicate alarm messages the panel produces. You can get a fresh message by sending a blank link or any data to the AD2USB

Current production firmware


Current BETA firmware



Older firmware versions are also available:




Sec. 3) AD2USBGUI revision history

• 1.0
  • First version just simple interface no keypad just display of text


• 1.1
  • Added LCD Display


• 1.0
  • First version just simple interface no keypad just display of text


• 1.1
  • Added LCD Display


• 1.2
  • Added Keypad


• 1.2a
  • Some tweeking on keypad and interface


• 1.2b
  • Upload firmware function
  • Small GUI changes.


• 1.2c
  • Small bug fixes button 1 was disconnected? um how did that happen?


• 1.3a
  • Lots of changes a few are as follows
    1. New RF sensor tab
    2. New Floorplan alert window
    3. Bux fixes including parsing of commas in text buffer bug
    4. Socket client and server ( no ssl yet sorry )
    5. Reset the device button
    6. Diagnostics settings button


• 1.3b
  • Refactor socket code and serial code to allow for byte by byte reading. Now we can upload firmware over ethernet
  • Exposed button and LED images in resource folder so user can customize them
  • New features in config file
    1. Window size
    2. LCD display colors
    3. Window size
    4. Log font size
    5. Disable for com port
  • Some GUI changes LCD looks cleaner centered with background color missing now fixed
  • Fixed some race conditions in socket and serial code that was causing crashes
  • Other small stuff was a busy weekend so I dont recall it all


• 1.3c
  • Working on F1-F4 keys needs more testing but I think it is all working now
• 1.3d
  • Now shows name of rf device if it defined in the config and not the serial number
  • Fixed another race condition
  • Added address mask filter to only see messages for keypad addresses you choose
  • Added a global exception handler


• 2.0
  • Renamted RF Tab to "Items"
  • Added custom icons to the Items tab
  • Added custom command to Log tab
  • Configure Ad2USB firmware (requires fimrware V2_1f_09 or later
  • Added example module code for custom modules
  • Added zonetracker module for purchase that tracks zones open/close in items tab
  • Created unlocker module for purchase that will help discover installer codes
  • Config setting to ignore unknown RF devices
  • Signon messages for connecting sockets
  • Sorting on ID and Type in Items tab
  • Configuraiton Dialog
  • About Box
  • myresources folder for custom images
  • Improved excpetion management continue running after exception dialog
  • mysettings.conf for private settings


• 2.0.4
  • Fixed a bug with jpegs on windows
  • Added support for config of relay modules
  • Some minor performance improvements
  • missing client certificate fixed


• 2.0.4033
  • Added full build version data to program window title. This is the number of days since 1/1/2000
  • Added more exception handling around loading of key files
  • Fixed a bug in the Diagnostic Mode entry.
  • Added function F4 to mark the log to help me decode output from the panel better.


• 2.0.5
  • Fixed some exceptions
  • Added log file support
  • Added mystuff.cs
  • Changed examples licensing to MIT
  • Added webkit.cs

Keypad View:


Alarm Sensors and Zones View:


Floorplan alert view:

I have the V2.0 board with the square connector. Could you post a pic showing the jumper in the proper position for USB? Also, if the jumper is placed there, is the board still able to operate via USB with either serial addressing or telnet as well? I'm currently still using the Indigo Serial Bridge script i posted about here a while back but am considering Berkinet's telnet plugin. I'm a little confused about what is lost when committing the board to "serial" or "USB" based on the jumper location.

I will let Sean post the jumper picture, if he has one. However, I can answer the other question. The jumper sets the ad2usb board to user either USB or RS-232 serial communications. It does not affect how your application software communicates with the ad2usb. If you already have your ad2usb board connected to your computer with a USB cable, then you want to jumper the board for USB. Most users will want to set their jumper for USB.

This was buried deep. This link describes the jumper setting that is needed on that board.

Hay Hamw

On that board it was one or the other serial or usb. The 2.2 version of the board the serial adapter was on all the time but caution should be used to only talk to USB or Serial not both allowing attaching the AD2USB directly to a micro controller or max232 chip. I also have RS232 version with no USB chip that can connect directly to a DB9 connector.

Hope this helps.

Re
Sean M

Does that mean that as long as I don't hook it up to a serial device I am OK and don't need to put on the jumper? Would make life easier if it is just the SW update.

hamw wrote:
Does that mean that as long as I don't hook it up to a serial device I am OK and don't need to put on the jumper? Would make life easier if it is just the SW update.Unfortunately, no. To assure that the connection does not accidentally shift between serial and USB you need the jumper. The ad2usb might work without the jumper, but, it might also just change settings at some random time.

The jumper is very easy to add. While the pictures show an empty circuit board, in actuality, there are small pins on the board where you can insert a short piece of wire. It is not difficult and does not require any soldering.