I’m Switching from Aether to MacLoggerDX for logging

I’m a Mac user and have been using Aether for logging my contacts for several years.  I love aether.  It’s nice and clean and for the most part is very intuitive.

The trouble however started when I got my vanity call.  Aether does not know how to handle the fact that contacts prior to date XXX were made using my old call (WB7OBG) and subsequent contacts were made using my new call, K7RPM.  The only workaround I came up with was have two log files. Also, Aether seems to be unable to connect to QRZ.com for callbook access.  I give it my callsign and password and it says “Login Failed”.  I’ve manually logged in to QRZ.com with no problems.  Multiple callsigns (and certificates) is also problematic when interfacing with LotW.

A couple of days ago my frustration level was to the point I was ready to drive a marlin spike through my monitor.  I decided to look at alternatives.

So far, MacLoggerDX seems to work pretty well. The ‘two callsigns’ problem is solved with the ‘Operator’ field. MacLoggerDx’s integration with LotW is a little looser:

“MacLoggerDX supports LoTW and eQSL with Ham standard ADIF files. QSO’s can be exported by ADIF, signed (using the ARRL supplied applications) and uploaded to LoTW. MacLoggerDX also uses LoTW and eQSL ADIF confirmation files to update the QSL received status of your logged QSOs”

MacLoggerDX also seems to have no problem connecting to my Kenwood TS-590s

73’s

Dave