Select MacLoggerDX Help from the Help menu and it will display the top level help screen. macOS looks for the help files contained in the app in the Applications folder.
There is an online reference manual here which is also available under the MacLoggerDX File menu and is updated several times a week - much more frequently than a PDF could be published. This is a reference guide - not a user manual with step-by-step instructions.
Most of the controls will display tool tips that describe what they do when you mouse over them.
If you don't find an answer to your questions here in the FAQ or in the user videos on YouTube then please refer your question to one of the support email reflectors. There are lots of knowledgeable people there who can help you:
Enter a call sign in the DX panel Call field, press return to do a Look Up and then press the Log QSO button. All the information in your DX or Contest panel for that QSO will be entered into the log.
You can open a new log file anywhere you want on your Mac but the default log file is your_home_directory/Documents/MLDX_Logs/MacLoggerDX.sql.
The current log is displayed in the File Menu/Open Recent sub-menu and in Log panel.
You can, for example, store your log file in your DropBox, Google Drive or iCloud Drive (Yosemite) folder and have your changes instantly available in the Cloud from any Mac. Copy your current Log file in the Finder to your DropBox/Google Drive folder and Open Log File... from the MacLoggerDX File Menu (Make sure you don't try and change your log from more than one location at once).
It's not supported, or for the faint of heart, but your MacLoggerDX preferences reside in this file: your_home_directory/Library/Preferences/com.dogparksoftware.MacLoggerDX.plist.
Where is the Log file backup procedure ?
There isn't one. Backup is an operating system function not an application feature but it is easy to do in a number of ways...
How do I Merge Logs?
You can merge any log into any other log.
Only use ADIF when transferring between MacLoggerDX and other software programs.
What does the Version 6 Upgrade cost ?
Please contact us by email if you are eligible for either upgrade discount.
Version 5 included almost 7 years of free updates and support. No one is required to upgrade to Version 6. It's easy to stay with or go back to Version 5 which will continue to work on the same Macs and under the same versions of Mac OS X as it does now. Support is still available and internal database updates will continue for years to come. All new development however will be on Version 6.
If you need to re-install Version 5.63 You can download it here: http://www.dogparksoftware.com/MacLoggerDX_older_versions.html.
Select Speed Log from the File Menu and enter them in the dialog.
The USB/UART Bridge chip inside the Icom, Yaesu and Kenwood radios is a Silicon Labs USB to UART Bridge Controller and the Mac drivers are available here.
The USB/UART Bridge chip inside the Eagle, K3S and KX3 is an FTDI USB to UART Bridge Controller and the Mac drivers are available here. Note: recent version of Mac OS X include an FTDI driver.
When you have more than one Silicon Labs UART device on your Mac USB Bus the port name (SLAB_USBtoUART) is defined in the driver. Since the two devices load the same driver, they get the same string to which OS X then adds a number suffix to to prevent name conflicts. The number will change depending on what order the devices are enumerated.
To make that string different for two devices you need each device to load a different driver. Then driver A will have one string while Driver B has another. To get different drivers loaded you must use two different PID's.
If the PIDs in two UART devices are the same it is not possible to create drivers with unique strings.
Manufacturers can request specific PIDs to be burned into the devices at the time of manufacture and they either did not realize the necessity for separate PIDs or ignored the issue. Silicon Labs is working on a signed Mac driver that would generate a unique name based on the serial number of the device.
If you are using a radio with an internal USB/Serial adapter and you turn off the radio before quitting MacLoggerDX the port will disappear.
Un-check the Radio panel VFO check box or quit MacLoggerDX before you turn off the radio and turn on the radio before you start MacLoggerDX.
You can tell which chip set is being used in your adapter by selecting "About This Mac / More Info / System Report / Hardware / USB.
Note: This tells you a USB/Serial adapter is plugged in - it doesn’t tell you if a working Mac driver (kext) has been loaded for it.
Here is an example of a Silicon Labs chip set based adapter (click to enlarge):
First choose your PTT Method in the MacLoggerDX Radio Prefs...
Then, the instructions for getting cocoaModem to tell MacLoggerDX to PTT are here.
Also have a look at this message on the MacLoggerDX Yahoo Group.
Note from VK5KX and ON4AEY about mldx V6 and cocoaModem PTT scripts:
There were issues with the scripts inside cocoaModem (Select app and Show Package Contents - Resources), some were named mldx5key, mldxkey etc. I ran the mldx5key script and it put the radio into TX mode but the mldxkey script failed to TX. I made copies of the mldx5key & mldx5unkey and renamed them to mldxkey & mldxunkey after I renamed the original files to mldxkey–old. When I rebooted and did a clean start, everything worked.
cocoaModem uses the mldx5key and mldx5unkey scripts if the version.scpt detects version 5. So with version 6 it falls back to the mldxkey and mldxunkey scripts which are designed to work with older mldx versions.
This is the entire Apple Script that cocoaModem uses:
Note from NR5K:The functionality to do this is built in to Fldigi via the <EXEC> macro. Any Fldigi value can be sent to an AppleScript which invokes MacLoggerDX to log the value. Everything you need to know to do this is in the Fldigi and MacLoggerDX doc.
MacLoggerDX supports all the popular logbooks with standard ADIF files. QSO's can be exported to ADIF, signed (using the ARRL supplied applications) and uploaded to LoTW. MacLoggerDX uses LoTW and eQSL ADIF confirmation files to update the QSL Received status of your logged QSOs (See the Confirm QSOs with ADIF File... Menu command under the Log Menu).
MacLoggerDX supports on-demand LoTW and eQSL confirmations where QSL Received is time stamped when QSOs are matched, and real-time upload of your QSO's to LoTW, eQSL, Club Log, QRZ Logbook,and HRDLOG when they are logged, optionally, QSL Sent can be time stamped for each QSO uploaded. Individual QSOs can be uploaded and confirmations requested in the Log panel contextual (right-click) menu.
LoTW, QRZ Logbook, Club Log, eQSL and HRDLOG are all configured in the MacLoggerDX Look Up prefs.
If QSO upload or confirmation errors occur, MacLoggerDX will display short error descriptions in the Look Up prefs error status field for each service and in an Error Alert. Longer error descriptions can be found in the Debug Log (File menu Show Debug Log). A confirmations log is also kept in your ~/Documents/MLDX_Logs/adif_confirmations folder.
QRZ Logbook can be configured to pass your QSOs on to LoTW.
There is also a user script written by Kevin Williams (WM4J) in the MacLoggerDX Yahoo Group File section (and in the MacLoggerDX download Extras folder) which automates the eQSL and LoTW batch upload and confirmation processes. The setup instructions are in the readme file included in the zip archive.
The Export ADIF... File Menu command will export the QSOs selected in the Log Panel or if none are selected, the entire log.
Enable the 2D Map Prefs DX Spots/Show Spots and Show Spot Labels check boxes and enter 1000 in the Max Number of Spots field.
The log spots displayed are also affected by the search criteria you have set in the log panel.
The SOTA reference number is visible in the SOTA column of the Spots Panel and in the DX Panel after a lookup in the SOTA field. It is also logged and exported in ADIF. The SOTA reference is not available from the Call Book Servers like QRZ XML but is broadcast by some dxclusters in the comments field of the spot. MacLoggerDX parses the SOTA Reference numbers from the elgur.dtdns.net:7300 SOTA dxcluster comments field automatically.
No, Select Update Selected Log Entries from the Log Menu and the missing fields will be filled in. This will perform an Internet Call Book look up for all selected log entries and add the found data to any blank fields in the entry, one at a time. This will ONLY update empty fields (or "0" in the case of DXCC), it will never overwrite existing data. MacLoggerDX will post an alert if you try to process more than 250 QSOs at once but the actual number that are practical to update at one time will depend on your Mac, OS version, your Call Book service and your Internet Connection speed. Keep in mind that some Call Book servers will throttle their response if you overload them.
The Locator field in the DX and Contest Panels will tell you what Geolocation method MacLoggerDX has used for each lookup:
In the downloaded Sample Files folder edit the dxcommands.dat and/or dxclusters.dat files and place them/it in ~/Documents/MLDX_Logs and restart MacLoggerDX.
This will also work for the CW Keyer Macros in cwmacros.dat.
Make sure you have added them all to the System Preferences / Internet Accounts.
No, MacLoggerDX creates a standard .png file named "MacLoggerDX_qsl_to_CALLSIGN.png", places it in your "~/Documents/MLDX_Logs/" folder and then asks Preview to display it but you could print the file from any application.
MacLoggerDX can export your Log to a Google KML file which will display your logged QSLs in Google Earth. Simply drag the exported KML file onto Google Earth and you will see all your logged QSOs displayed on the Google 3D Map.
Log Table, Awards Tables:
DX Panel: Call, Mode (dxcc), Band (dxcc), Grid (first 4 character), ITU, DXCC, CQ Zone, IOTA, State Text Color
Spots, Cluster (dxcc) and History (dxcc) Panels:
Spots on 2D Map and Bands Panel:
2D Map Marker Shapes:
Select Focus VFO from the Shortcuts menu, or click on the large frequency display and then press tab. Don't forget to enable All Controls in the System Preferences/Keyboard & Mouse/Keyboard Shortcuts Panel.
The VFO stepper up/down arrows will change the radio VFO 10 Hz up or down with each click of the keyboard up/down arrows, or you can set up the Griffin PowerMate to send up/down arrow clicks.
With the Shift Key Pressed the frequency will change 100 Hz up or down.
With the Control Key Pressed the frequency will change 1 KHz up or down.
With the Option Key Pressed the frequency will change 10 KHz up or down.
With the Command Key Pressed the frequency will change 100 KHz up or down.
You can also position the mouse pointer over the VFO Stepper or Band Panel Sliders and use the mouse scroll wheel or Magic mouse scroll surface to scrub the frequency up and down.
The mode popup reflects what mode the radio is actually set to.You can change the mode mapping of USB to PSK (or anything else) with the mode mapping pref and when you select USB from the mode popup it will display and log as PSK.If you decide to work USB, then you just change the mode mapping from PSK back to USB with the mode mapping pref and when you select USB from the mode popup it will display and log as USB.If you want to assign specific modes to specific bands or sub-bands then edit the sample band plan delivered with MacLoggerDX and add the actual radio modes desired for each sub-band and select it in the Station Prefs.
Make sure you have the Call Book popup set to QRZ XML (or the Call Book of your choice), your account is up to date and your Username and Password are correctly set.
Lookup will suggest an IOTA Zone based on the call sign. False positives can occur because the call sign cannot uniqely identify an IOTA entity in all cases. Even the IOTA id's supplied by a call book service may not be correct. The IOTA identifier supplied by MacLoggerDX must be verified in QSO. This also applies to the ITU Zone and CQ Zone values suggested by MacLoggerDX.
If I use the split function in MacLoggerDX, the log records the tx and rx frequencies but when I set split from the radio front panel, the log only records the receive frequency ?
Some radios do not report split status or split frequency so that MacLoggerDX only knows about split for those radios if it is set from within the program.
What are caches and how do I get rid of them ?
MacLoggerDX caches or stores the QRZ Online QSL pictures and the Lookup data for varying periods of time to reduce the load on your internet connection and speed things up. If you want to see a change you have made to the Online lookup data or your QSL picture immediately just do a manual lookup (enter the call and press return) which will bypass the cache or quit MacLoggerDX and rename or delete this folder:
You can also selectively remove one or more stale cached thumbnails from ~/Library/Caches/com.dogparksoftware.MacLoggerDX/Cached Thumb Pics by dragging them to the trash.
I'm using MacLoggerDX without a connected radio. How do I get the frequency and mode data into the log without manually correcting each entry ?
With no radio connected, whatever you enter in the DX/Contest Panel Frequency, Mode and Band text edit fields will be logged, these fields will stick until they are changed.
Why doesn't MacLoggerDX save the QRZ URL for Bios in the Log?
MacLoggerDX doesn’t save the URL when it is a QRZ bio with a session key, since the session key will eventually expire and not be valid in the future.
How do I Uninstall MacLoggerDX ?
MacLoggerDX doesn’t install any system extenstions so removing it from your Mac is fairly simple: