![]() ![]() 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. 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. 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. ![]() Just check the option “Auto Discovery.” This is not to be confused with the TX “Auto” enabled below.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. RUMLogNG has, IMO, the best rig control software out there for the Icom radios and using a simple option in RumLogNG you’ll never have to reset the transceiver port again. Support is excellent for RUMLogNG and you can find the forum here. There have been many updates since that time. I have a previous post on this and you can find it here, Ham Radio iMac (iCOM Macintosh) In The Shack. RUMLogNG is a free logging program for the MacOS. The computer starts off out of the box extremely fast, but later on with loading programs, everything slows down. ![]() This is the fastest computer I have ever owned, so far. I have not resolved the Parallels drivers’ issues, however I have Windows running in Parallels on my Mac Mini. The problem I see, if you want to run Windows with Parallels on your new Mac with the M1 processor, you may have trouble with drivers. I set my DX Alarms (countries, grids, continents I need) and when they pop up, the software starts the transmission automatically. It’s possible with the latest RumLogNG update and WSJT-X. DX Chasing with FT8! With this software combo you won’t miss needed DX. ![]()
0 Comments
Leave a Reply. |