Background

The first version of HRD did not have any logbook support at all - the original idea was a simple program which just provided computer control of commonly available radios.

At the request of many HRD users an integrated logbook was added in 2004, now in mid-2008 it is time to revisit the logbook and design a solution which will meet future needs.


Schedule

Development during Q4 of 2008, tentative public beta by January 1st, 2009.

Stay tuned!


 

Proposal

The future of HRD is a suite of programs which interconnect using TCP/IP:

  • HRD users have more computer power available - often with two or more systems,
  • Networking is becoming very common and easy to configure,
  • Remote station operation is increasing as the harware required becomes cheaper.

A logbook was originally a paper solution satisfying the requirements of licencing authorities.

Today a full-featured logbook must support:

  • Multiple databases opened simultaneously, for example:
    • RTTY Contest 2007
    • DX expedition to Isle of Man 2005
    • Portable operations in the Himalayas 2008
  • Automatic backups - add new entries to multiple databases, for example:
    • Hard drive,
    • USB memory stick.
  • UNICODE support for all languages and character sets - if you can type it then the database can store it.
  • Networking:
    • Logbook can run on a different computer,
    • HRD / DM780 / 3rd party programs can send new entries using a simple TCP/IP syntax,
    • Store-and-forward - save the entry in a local logbook and also forward to a logbook running at another location for added security in case of a hard disk failure.
  • Database access through ODBC (Access, MySQL, SQL Server Express) and ADO connection strings.
  • Printing entries in a standard logbook format
  • Printing address and QSL labels
  • Upload and synchronising with eQSL.cc, LOTW
  • Interface to common logbook programs such as DXkeeper and N1MM.
  • Web interface
  • User-definable ALE tab ordering
  • Award tracking
    • IOTA tracking
    • Etc.
  • Import / export using:
    • ADIF
    • Cabrillo
    • XML (export to Word, Excel, Web, ...)
  • Store:
    • QSO's,
    • SWL reports,
    • Pictures (QSL cards, SSTV images),
    • Audio tracks.
  • Interface for callsign lookups:
    • QRZ.com,
    • Hamcall CD,
    • etc. 
  • Analysis displays similar to the sh5 log analysis program from http://rescab.nm.ru/ .
Simple Configuration

   

In this example HRD and DM780 are using the same logbook, the logbook is either on the same computer as HRD and DM780 or on another computer somewhere on your network.

This is the most basic configuration, operation is totally transparent.

The logbook is using three databases:

  • Current - read/write, new entries are added in this database.
  • RTTY 2007 - read only, from your record-breaking entry in this contest.
  • CQ WW 2006 - read only, all QSO's from this contest.

The contest databases are loaded to provide callsign looking information - date last worked, name and address etc. You could even load a database from someone else!

 

 

Advanced Configuration

This is a typical multi-user scenario. Bill (GD4ELI) and Ben (HB9DRV) go on holiday to an exotic location taking their laptops for radio control and logging.

Each laptop stores QSO's locally and uses the store-and-forward option to forward QSO's to a central server located in a secure facility somewhere. The server optionally returns information from QRZ.com and various callsign CD's as well as updating Bill and Ben's website.

The central server updates two databases,

  1. C:\Data\Database.mdb which is located on a disk drive and has read-write access, and
  2. Z:\Data\Backup-2008.mdb which is located on a USB memory stick. Only new and modified entries are added to this database.

In addition the Old QSO's 2000 to 2008 database is used for name and address lookup.

When the network connection from the holiday island to the secure server is not available the secure server cannot be access; when the network is restored the secure server's databases are updated with the contacts made while the network was unavailable.

 Even if the airline loses our two friends' laptops during the return flight all QSO's are safely stored on the central server on both hard disk and on a USB memory stick.

 

Copyright 2009 by Simon Brown, HB9DRV Terms Of Use Privacy Statement