Callsign Lookup 

Geoff Anderson G3NPA, Jim Hargrave W5IFP and Rick Ellison N2AMG

1.0 General 

Logger32 offers the user several ways in which to look up information about the QSO partner. This can be: 

1)       Using a call book CDROM in a local drive to establish QTH information

2)       Using an internet-based call book to establish QTH information

3)       Using a local database to establish QSL Manager information.

4)       Using a user- specified URL to return ADI formatted data. 

Logger32 supports the QRZ Hamcall and RAC CDROMS and contains a sample QSL manager database from GoList. It also supports internet access to, and Information from these sources can be obtained either manually or automatically and the data obtained from the call book databases can be used in a variety of ways to automatically update the Logbook Entry window.  

Please note that Feed, and are subscription services – requiring passwords. Details of these services can be obtained from or 


You should be able to send eMail by clicking on an eMail address (if shown) in the callsign lookup window. If the Lookup returns a URL it will be shown as a functional website link (blue text with underscore).

From release Ver 3.16.0 forward, Logger32 will NOT provide Internet lookup capability to

From release 3.17.0 forward, Logger32 will NOT provide Internet lookup capability to

 Those wishing to access these services must use third party (non Logger32) modules that are available.

Since its inception, Logger32 has accessed through an external module (not part of Logger32 but written by the same author) called QRZLookup.exe. and the collected information has been forwarded to a routine within Logger32 to display the results. Data was provided by in a high throughput proprietary format that was free from advertising. The policies of have changed and the direct data feed for Logger32 is no longer available. The QRZLookup.exe module no longer works, and has been removed from the distribution package. This file together with QRZ.txt, is no longer used and can be deleted from the default Logger32 directory. However the display window remains as part of Logger32 and can be filled with data via the external interface.

From release 3.35.0 forward, Logger32 will provide Internet lookup service from HamQTH. Setup for this capability is covered in paragraph 8 below.

2.0 Using a Local CDROM – Manual method 

Using the menu item Setup|CDROM, select the CDROM type.  



In its default state, Logger32 expects the CDROM to be in the first CDROM drive on the computer.  If necessary, you can set the default drive for the CDROM to any drive letter from the above menu.  

For details on how to set up CDROM data on a HDD for faster access, please refer to the “Setup CDROM” help file section. 

To access the data, simply click on the CDROM icon   to obtain the window shown below:



Enter the callsign <Enter> and, if found, the data for the callsign will appear. 

All similar windows have a Toolbox and Transfer menu options. The toolbox allows for the user selection of data and label font/color and background color. The “Transfer” options will be described later. 

3.0 Using a Local CDROM – Automatic method 

If you wish an automated lookup from the CDROM then, in addition to the setting detailed above, also check the item  Setup|Auto Lookup|Auto CD-ROM Lookup. 


Entering a callsign in the Logbook Entry window and tabbing out of the field will automatically call up the CDROM window and fill it with data for that callsign. 

4.0 Using an Internet Database 

Logger32 provides capability to do callsign lookups via internet-based databases by use of external modules written for specific sites. A link to these external modules is available on the Logger32 web site at

Current lookup modules are available for: QRZ XML Lookup Database, QRZ Web Interface, and The QRZ XML Lookup Database Module is included and configured when Logger32 is installed. The use of this lookup module requires a subscription from

Sample source code of a non-functional (it doesn't go anywhere or retrieve any data) external InternetCallsignLookup module is (or will be) provided at the Logger32 website. Programmers can use this as a skeleton to access whatever database they choose.

4.1 Installing Internet Based Lookup Modules

  1. Download the Lookup Module of choice from the internet.
  2. Unzip the files in the downloaded zip file into the Logger32 directory.
  3. Open the Internet Callsign Lookup window -
  4. From the top menu of the Internet Callsign Lookup window, select "Toolbox".


  5. Select "Setup external module to use" from the menu to open the external module setup window.


  6. Click the browse button and search for the file you just downloaded and unzipped in the Logger32 directory. This will save the path information to the Lookup app you are installing in the External Program Name box on the setup window.
  7. In the Lookup form caption box you will enter the name you want to call the lookup. This will appear on the top of the Internet Callsign Lookup window.
  8. The setup window can hold configurations for up to five different lookup modules. The "Use" button needs to be selected for the lookup you want to use to be enabled.
  9. Once the above steps are followed, the lookup module of choice will be properly installed.

4.2 Using an Internet Database – Manual method 

To access the Internet Callsign Lookup window     manually, simply click on the icon shown to produce the lookup window. Enter the callsign <Enter> . The lookup module will open and retrieve the data. Once the data has been retrieved it will appear in the Internet Callsign Lookup window. If the data is not retrieved, there will be indication on the top of the window saying the information can’t be found. Note: You MUST be connected to the internet for this to work.

4.3 Using an Internet Database – Automatic method 

If you wish an automated lookup from the web, then in addition to the setting detailed above, also check the item Setup|Auto Lookup|Auto or Setup|Auto Lookup|Auto Internet Callsign Lookup (external). 


Entering a callsign in the Logbook Entry window and tabbing out of the field will automatically call up the web window and fill it with data for that callsign.  

5.0 Minimized display

If you wish to run the QSL information windows open in a “minimized” state rather than have them clutter up the screen, then select the option Setup|Auto lookup|Open minimized on auto lookup. 

6.0 Automatic transfer of QTH data to Log Input Window


Logger32 can be set up to automatically transfer information directly into the Logbook Entry window.  In the data display window, click on the “Transfer” menu option and set the desired option(s). The options available are self-explanatory.  

Note that QRZ, Hamcall and the CDROM lookups have their own display windows and therefore different options may be set up for each. 

If no automatic transfer options are selected, then the user can click on individual fields of the display to transfer just one particular piece of information.

Transferring of more precise position data (like US county or Gridsquare information) from a CD lookup window to the Logbook Entry window will update the heading/distance information.  

7.0 GoList

Like the CDROM and lookup system for obtaining individual QTH data, Logger32 also has the ability to search for QSL manager information using GoList.  There is a built-in database that was current when Logger32 was first released, and you are reminded that this will quickly go out of date. 

Subscribers have unlimited lookups for a year.  More information may be found on the GoList web site, or (assuming that you are already connected to the Internet) click on “Web lookup” to collect from the GoList database. 

7.1 GoList - Manual

To obtain the QSL manager information, enter the callsign into the Logbook Entry window, then click on the GoList icon.          


Alternatively, click on the icon first, enter the callsign and either press <Enter> to get the information from the local source. 


7.2 GoList – Automatic

PLEASE NOTE:  While the button that used to perform the on-line 'GoList' lookup still looks the same, the functionality has changed. The on-line 'GoList' lookup functionality has been removed. The 'Golist' local database lookup is as before, and those users who wish to do on-line 'GoList' lookups can invoke a local lookup and click the menu to do an on-line lookup.

8.0 Generic On-Line Lookup.


The original GoList auto lookup facility has been changed to a more general generic lookup facility.  The use of the facility is very much the same as the other lookup options described above except that the user can set up their desired URL


The button that was previously used for on-line 'GoList' lookup now invokes a generic on-line query. The user programs their URL, and waits to receive an ADIF formatted reply.


Logger32 defaults to HamQTH. has now added an ADIF lookup that Logger32 can access directly (the button between the Internet lookup [] and [CD ROM Lookup] is used to access this capability.

To access HamQTH directly from Logger32, you must first register with HamQTH:

Go to: and click on the register link to register with HamQTH . You must provide a USERNAME and PASSWORD.

Next, open the internal lookup window. Click TOOLBOX | Setup external module to use.





 Set the URL to:

NOTE: Substitute your HamQTH username for USERNAME and substitute your password for PASSWORD. The URL will should look something like this (example username is BWANA, and example password is MAKUBA):


It is envisaged that initial implementations will be for simple QSL Manager data retrieval, so the window presented is adequate.  If/when more complex sets of data are returned, the capabilities of the window will be enhanced to include user-defined field mapping.   Replies must be in ADI format. 


To change the window caption, use the menu item Toolbox | Change Window Caption








As well as defining the window title, the same words are used for the icon tooltip (see CSL_10 above)