Yep, that’s me. At an ARES-RACES meeting the other night, a few fellow members were discussing JS8Call. I decided to download the software and give it a whirl.
After installing the software and looking it over, I watched a few YouTube videos to learn how to use it. Once I thought I had the basics down, I fired up my KX3 to take JS8Call for a spin.
I didn’t see any activity on the waterfall, but after a while, I was able to decode a transmission on 20M. That was a good sign. I called CQ few times with no response. Checking PSKReporter, however, I saw spots from as far away as southern California. Not bad for 5 watts and a rainspout antenna.
I dropped down to 40M and saw immediately saw a few decodes pop up. I called CQ a few times and received a call from N4YTM in North Carolina. Gordon, as it turns out, was only slightly more experienced with JS8Call; I was his third contact. Despite our collective inexperience, we had a nice, albeit slow, chat with this new mode.
I found that carrying on a basic QSO with JS8Call was pretty intuitive. I still have a lot to learn about some of the more advanced messaging features, though. JS8 is an interesting mode and less robotic than FT8. It’s slow for a keyboard-to-keyboard chat mode but I was decoding signals I could hardly see on the waterfall.
Although CW will always be my primary mode, I’m sure there will be more JS8Call activity in my future.
Going all the way back to my Novice days in the mid-70s, I’ve always been a bit anal… er… diligent, when it comes to logging contacts. Years ago I started using logging software and that diligence persists. Over the years, I’ve evolved to a logging process that I’m sure some would find overly complex. It’s actually not that bad and it works well for me.
I use a variety of methods to capture QSO information. Eventually, everything ends up in one central log. From there, all QSOs are uploaded to Logbook of the World (LoTW). The diagram below shows how everything ties together.
Here are the main components of my logging system:
ACLog. I use this software by N3FJP for my main log. All QSOs, no matter how they are made or logged wind up in here. Because most of my HF operating is done while portable, I added a few custom fields to keep track of where I was (MY_QTH), what rig I was using (MY_RIG) and what power I was running (TX_PWR). Everything in my main log gets uploaded to LoTW. ACLog makes it very easy to do that. For casual operating at home, I enter the contacts directly into ACLog. Same goes for paper logs from portable operations with just a few contacts. For larger batches of contacts, I might resort to other methods.
ADIF Master. I use this great piece of freeware a lot. It allows me to take an ADIF file and easily add in the custom fields I keep track of and do a quick bulk edit to populate the fields for all QSO records in the file.
Fast Log Entry (FLE). I wrote about this software in an earlier post. This came in handy last year for National Parks on the Air activations. When I used paper logs for activations, FLE gave me a fast way to enter the QSO data and generate an ADIF file.
SKCC Logger. I use AC2C’s SKCC Logger software to log all of my Straight Key Century Club contacts. This software does automatic lookups from the SKCC member database when you enter a callsign. It also helps keep track of award levels and generates award applications. From SKCC Logger, I generate an ADIF file for further editing and importing into ACLog.
fldigi. Every now and then I get on a digital mode kick. Initially, I use fldigi’s internal log and export an ADIF file. I haven’t worked JT65 or JT9 in a while but, when I do, I export an ADIF file from the WSJT-X software.
HamLog. When I’m away camping for a few days, I use HamLog on Android cellphone to log my contacts. If I have a cell connection, I can do QRZ.com lookups while logging a contact. I export an ADIF file when I get home. After, editing the ADIF and successfully importing it into ACLog, I go back to HamLog and clear out the log file so I’m ready for the next trip.
Contest Loggers. When I use a specialized contest logging program for a contest… Well, you know the drill. I export an ADIF file, edit in my custom fields, and ingest it into ACLog.
So, that’s it in a nutshell. It probably sounds complicated but it has all become second nature to me. I’m not suggesting that you do the same but, perhaps, some of the utilities and techniques will be useful to you.
I recently discovered a very useful piece of software. Fast Log Entry (FLE) is a small text editor that lets you quickly get your QSO information from paper logs onto your computer. I originally installed FLE about a month ago but I didn’t immediately see its benefits. After taking a closer look at it, I have now added into my logging utility “toolbox.” FLE is a free download from DF3CB, although donations are welcomed. It is a Windows application but it runs great on Linux under Wine.
Here’s a typical use case for me. Quite often, I’m operating portable and logging my contacts in a small notebook. If there’s a small number of contacts, I could just enter them into N3FJP’s ACLog, which I use for my main log. However, entering into ACLog can be a little tedious if I have a significant number of contacts to deal with. This is where FLE comes into play.
FLE provides a simple, keyboard-only, way of entering the information. It uses a very simple format for the information. To get started, you enter the date in the format YYYY-MM-DD. Then, enter the band (e.g., 40m, 20m, etc.). Similarly, for the mode, you can just enter it (like “CW” or “SSB”). See the screenshot below for an example.
You can now start entering your contacts. Once you enter a contact at a particular time, you only need to enter the portion of the time that changed for the next contact. For example, let’s say you worked a station at 1510 and another at 1511. After you enter the contact at 1511, you only have to enter “11” (i.e., just the minutes) for the next contact. If you run a string of stations, you only need to note the time periodically in your paper log (say every 5 or 10 minutes). FLE will interpolate the time for your contacts after you enter them if you like. Also, there’s no need to worry about capitalization; FLE takes care of that. You can enter RST (send and receive) information, or let it default to 599 or 59. You can populate the “comments” field by enclosing the comment in angle brackets <>. You can also add grid square information by prefacing it with a pound sign, like “#FN20.”
After you have finished entering your contacts, you can easily export an ADIF (Amateur Data Interchange Format) file for ingesting into your logging program. FLE will also let you create a Cabrillo file for contest submissions.
My brief attempt at describing FLE probably doesn’t do it justice. I recommend going to the author’s website to download a copy and taking it for a spin. Be sure to check out the step-by-step instructions on the website. Another great resource is a video by VK5PAS. He gives a very thorough introduction to FLE and explains it much better that I can. Although his video is targeted at the WorldWide Flora and Fauna program, it is a great tutorial on using FLE.
So, if you do a lot of portable operating with paper logs (think SOTA, NPOTA, IOTA, WWFF, etc.), take a look at FLE.
I’m planning to take part in ARRL’s National Parks on the Air (NPOTA) event next year. In fact, I plan to activate Valley Forge National Historic Park on New Year’s Day. It will likely be cold so I plan to operate “stationary-mobile” from the cab of my pickup truck. I suspect there will be a lot of “chaser” stations so I’m planning to use a computer for logging and sending CW.
I considered a couple of options. One is to use N3FJP’s ACLog on my Windows laptop. I use ACLog for my main log and I’m very comfortable with it. The drawback is that my Windows laptop might be a bit large for the cramped cab of my little truck. That led me to using my little Acer netbook computer, which runs Ubuntu Linux.
In my search for a contest-type logger for Linux, I tried several programs before stumbling across one called YFKtest. YFKtest satisfied my three main requirements for a logging program:
It has to be simple to use with keyboard input only; I don’t want to have to use a mouse.
It needs to provide programmable CW messages and be able to key my transmitter.
It has to have the ability to export logs as ADIF files that I can import into my main log.
Fabian DJ1YFK is YFKtest’s original author while Bob Finch WY9A currently maintains the software. Since it has been around for a while, the code base is stable. YFKtest is a PERL program, so it runs under Linux. It supports a large number of contests, including some QRP contests. It generates CW over a serial or parallel interface, as well as via Winkey. It works with the same serial interface that I use with the N3FJP software, so that’s a plus. If you are so inclined, YFKtest will do rig control using the hamlib utilities. It also generates ADIF, Cabrillo and contest summary files.
Installation on Linux was straight-forward. The user interface is a bit “old school,” compared to other logging software. It was, however, easy to configure and use. For NPOTA use, I took the “DXPED.def” definition file for DXpeditions and made a few minor tweaks to it. To give myself some peace of mind, I created a cron job in Linux that automatically backs up my log files to an SD memory card every 15 minutes.
YFKtest is hard coded for “599” or “59” signal reports. There may be a way to accommodate honest signal reports, but I haven’t explored that yet. Since LoTW doesn’t use signal reports, this is a non-issue for NPOTA logging.
Bob Finch’s support is top-notch. During my initial testing with it, I reported a bug in the ADIF files. In a day or two, Bob uploaded a fix. You can’t complain about support like that.
So, I’m going to give YFKtest a shot for my New Year’s Day operation. I’m anticipating a lot of NPOTA activity on the first day and that YFKtest will help me keep up with it!