Rumlogng windows how to#
Rumlogng windows for android#

The second tab we want to make modifications on is “LoTW/eQSL” ( LoTW stands for “Logbook of the World”): Here, the associated ADIF field is SIG_INFO. For the second party in a Park to Park contact, I use the second user defined field, and name it “P2P”. The associated ADIF information field is MY_SIG_INFO, and I check the “Remember” setting so that I only have to enter it once. For keeping track of the park reference I operated from, I use the first user defined field and call it “My Park”. I use the six character version of the grid square here. In the “Operator” section, I add my call sign, my name and the grid square that I operated from (from my paper log). Here is what my settings look like after applying everything I need: We start out with basic settings on the “General” tab. On the preferences dialog, we need to make modifications in two different tabs. To bring up the logbook preferences, use the RUMlogNG>Preferences menu item, or ⌘, However, in order to keep track of Park to Park contacts, and to upload to LoTW using the correct station location, you may want to do a bit more setup work before copying the first QSO from the paper log. At this point, we could add QSOs into the log, and if all you want is a simple ADIF file to upload, you can stop here.

K-2001 for the Adirondacks State Park, but for filenames, I leave out the dash), yyyymmdd is the date (e.g. The Kxxxx the park reference number (e.g. I use the following naming convention for my activations: When you instruct RUMlogNG to create a new log book, the first thing it does is to prompt for the location and the filename.

Rumlogng windows how to#

In the following, I show how to implement Vance’s recommendations in RUMlogNG. You can learn more about the nitty gritty of what happens in the database and how to fix that by watching Vance’s (N3VEM) YouTube video: If one of you moves to a different park, and you have another QSO on the same band, the system will flag that as a duplicate and not give you credit for another Park to Park contact. This works as long as you’ve only had one contact with the other party during your activation. The POTA database tries to identify Park to Park contacts automatically by matching two QSOs between two operators in different parks within a certain timeframe. In general, submitting a plain ADIF file is sufficient, but may not give you all the Park to Park credits you’ve earned. In RUMlogNG, this is done using the Logbook>New menu item, or ⌘N. A line in my log may look like this:Īfter the activation, when I am at my computer I start my logging application RUMlogNG (this is only available for macOS systems), and I create a new log book. For a Park to Park contact, I also log the park reference number. While I am making contacts, all I write down is the abbreviated time – I only write down the minutes – the call sign, the outgoing and received signal report and the state. In addition to that, I log my operating frequency, and when I change frequencies, I create a new line with the new frequency. All that information gets written at the top of my activation log.

Rumlogng windows for android#

The apps just mentioned work on my iPhone, there are similar apps available for Android phones. The first thing I do when arriving at my operating location is to get a few pieces of information from my phone: The grid square I am in (using the HamSquare app), the county I am in (using the Where Am I app) and the correct UTC date and time (using the Pilot Time app). So, don’t clean out your car too often or you will not have a backup for your logbook 🙂 Things like gas receipts, parking passes or old shopping lists, even paper napkins from fast food restaurants all work for this purpose. Even when my log book fails (because I left it at home), there are usually enough scraps of paper in the car that I can log an activation.

This is to eliminate one more device that can fail during an activation.

It’s not the only way to do this, and it may not be the best way, but it’s what I’ve developed over about 18 months, with more than 60 activations. The following process is what works for me. I am a POTA activator, which means that in addition to just logging for my own benefit, I also have to submit an ADIF file to my POTA regional coordinator.