My Thoughts on CQRLOG

March 13, 2014 — 1 Comment

Read Setting Up My Ham Shack for a bit of background, in case you missed it.

Twice I’ve complained (in some capacity) about CQRLOG on this blog which, to be honest, isn’t fair to this application (or it’s authors).  My complaints (if you want to call them that) around CQRLOG had to do with its limitations.  But getting back to that aforementioned honesty — it isn’t CQRLOG’s fault.  I was simply trying to use the application on platforms or in situations for which it was not designed.

As far as Linux is concerned, it’s actually quite a nice and capable application.  So in defense of CQRLOG (as if it needed it), here are the features which I most enjoy:

In not particular order (of importance):

  1. I love how, given the callsign of the other station you’re communicating with, CQRLOG will auto-populate your QSO details with information scraped from  Obviously you’ll want to validate this information with the other party.  Especially if you typed their callsign wrong.  I’m sure most mainstream loggers do the same thing — but I don’t have experience with many (any?) of them, so everything is new and exciting to me. 🙂
  2. CQRLOG will also display the distance between you and the other station.  While not exactly a deal-breaker, it’s often fun to know.  Especially if you usually operate low power like I do.  (I hope they’ll actually provide an option to change it from km to mi in a future release!)
  3. I love the transceiver control integration with hamlib.  Especially the ability for CQRLOG to start hamlib at startup thereby not forcing me to do it manually beforehand.
  4. Multiple QTH profiles.  As a SOTA activator, I want to be able to accurately log where my QSOs occur.
  5. Entering a log by pressing ENTER.  What a novel idea?  (Xlog required you to use CTRL-W.)
  6. Automatically reading logs from fldigi.  Nice.
  7. A great DXCC (and WAS) Statistics display!
  8. Ability to import/export QSLs directly with Logbook Of The World.  I could write an entire blog on how useful this feature is.
  9. Built-in DXCluster: The ability to double-click on someone’s spot and have my radio directly tune to that frequency AND auto-populate my QSO with all the relevant information is MONEY.  That alone is worth a donation!  (In fact, I just went to PayPal and sent them $25.)

Items I’d like to see fixed:

  1. CQRLOG can’t read the current signal report from the other station.  I really got used to how Xlog handled this and wish there were a more “automated” way to do it.  Yeah, it’s easy to type two digits into your log, but when the application can already do just about everything else…
  2. I’m not sure if it’s a limitation of CQRLOG or hamlib, so let’s blame both: It would be nice if it could read the current power output from my radio.  I change it on occasion (especially with distant stations) and I sometimes don’t recall to reflect that in my log.

And that’s about a brief a summary as I can make about this Linux logging application.  If you’re a ham radio operator and Linux user, I’d highly recommend you give CQRLOG a look to see if it fits your logging needs.


Aaron Melton


One response to My Thoughts on CQRLOG

  1. tried cqrlog but seems it is unable to get tranceiver control…
    been trying for days now to get it work.

    not really a hard core linux user but not totaly new to linux too.

    using it on a raspberry pi 3 running raspbian ( a debian based system)
    all runs except the rig control (and not shure about rotor control as i don’t have/use any of those)



Leave a Reply

Text formatting is available via select HTML.

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>