THIS IS NOT YOUR MAIN LOGGING PROGRAM!

This is a replacement for the excellent potaplus Chrome browser extension. If you have used that then this application should be very familiar.

This application allows you to browse the current POTA spots, QSY your rig via FLRIG, and log them to your logger through a remote ADIF message.

Hunterlog is in active development and any feedback is welcome. Here are the download links:

Release page v0.0.2

Windows Download

Ubuntu Download

On Windows, run the executable in any folder.

On Linux, you may have to chmod +777 the executable file and run it via the terminal.

The very first thing you should notice is that the default configuration is for N0CALL. You must change your callsign and gridsquare. Click the CONFIGURATION button next to the callsign and input your callsign and your gridsquare.

Let's look at the configuration options.

Default TX Power is used in logging. Put over legal limit if you want.

FLRIG Host IP and Port:

The app uses FLRIG to handle CAT control. These two values are the remote endpoint of the FLRIG instance that's running. The default FLRIG port is 12345

The radio buttons are for the logger. Select Default or Log4om to send the basic ADIF data to a remote logger. Select AClog if you use AcLog as it has to have the data wrapped in a different command. (Default and Log4om do the same thing currently)

Remote ADIF Host and port:

The remote endpoint data to send logged QSOs. This computer should be running Logger32, Log4om, AClog, or any other logger that accepts raw ADIF over network connections.

Select TCP for loggers that use a TCP socket (ex: Logger32), UDP for loggers that use a UDP (ex: Log4om), or AcLog for N3FJP's Amatuer contact logger.

Click save to store the changes. Then click the refresh button on the main screen to see your callsign and your configured Gravatar. You have a POTA account right?

STATISTICAL DATA SHOWN IN THIS APP IS NOT AUTHORITATIVE The authoritative data of record is your data in https://pota.app

👉 For instructions on importing stats See the STAT guide 👈

If you want to see your some nice stats like the POTAPlus addon, you need to update your stats using the STATS menu. There are three options here:

The most important one is the PARK STATS. You will want that to import that so you can see what parks you need to hunt.

Click a spot to load the QSO info into the top portion of the screen. Click green frequency button to QSY with CAT control. Click Log QSO after you've had the contact. The app will update stats and send the QSO data (with any modifications you do to the input) to your main logger.

It also will store a copy locally in hunter.adi as well as in the database. This is for your convenience.

You can now spot/re-spot activators through Hunterlog. When this is done the RST Sent and COMMENT QSO field are used to build the spot comment. Other posted spot info also comes from the QSO entry fields: Frequency, Callsign, and Mode. These will be sent to the POTA website and everyone will be able to see them.

Running the app will create the spots.db which is very important as it will contain all your qsos, configuration settings and stats such as parks and locations. You should back up this file occasionally and back it up before upgrading to newer versions of Hunterlog.

The file index.log is the application's log file. It is not the same as the Javascript console that maybe seen when inspecting the webpage.

This app is currently under pre-release. Please report bugs here on Github issues. In your report, please include both the app version number and the db version number. Both are displayed at the very bottom of Hunterlog.

- Cainan N9FZ