Simply select MacLoggerDX Help from the Help menu and it will display the top level help screen. 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 then please refer your question to one of the support email reflectors. There are lots of helpful people there who can answer your question:
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).
Where is the Log file backup procedure ?
There isn't one. Backup is an operating system function not an application feature. Use Time Machine which is built into every Mac to back up the log automatically - or - Keep your log in your DropBox or Google Drive folder which is backed up automatically - or from the Finder drag the MacLoggerDX.sql file in ~/Documents/MLDX_Logs/ onto your backup device.
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 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.
Mac OS X 10.10 Gatekeeper, no longer loads unsigned or improperly signed kexts (Kernel Extensions) unless they are listed in OSKextSigExceptionList.
To see if your driver is in that list enter this into a Terminal app window (do not enter the "$" terminal prompt):
$ cat /System/Library/Extensions/AppleKextExcludelist.kext/Contents/Info.plist | grep FTDI
Note: (FTDI or SiLabs, or Keyspan or Prolific etc.)
To use unsigned kexts this strict check can be disabled by adding a “kext-dev-mode=1” boot arg.
Enter this in a Terminal app window (do not enter the "$" terminal prompt):
$ sudo nvram boot-args="kext-dev-mode=1"
$ sudo reboot
Disabling Gatekeeper's driver security is not an ideal solution and hopefully driver manufacturers will sign their drivers in future releases.
Until then, you will need to use the nvram command to set kext-dev-mode=1.
Note: To turn this off use $ sudo nvram boot-args=""
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.
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.
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.
Version 4 will run on any Mac OS from OS 9 to OS 10.6.
Version 5 requires OS X 10.6 or later (Snow Leopard)
Version 4 is written in Carbon and runs native on PPC hardware and under emulation mode (Rosetta) on Intel hardware.
Version 4 uses a tab-delimited database which slows down with logs larger than 10,000 QSO's.
Version 5 is written in Cocoa, uses a SQLite database with unlimited size, instantaneous edits and is generally much faster.
All new development will be on Version 5.
Version 4 http://dogparksoftware.com/MacLoggerDX_Carbon.html
Version 5 http://dogparksoftware.com/MacLoggerDX.html
There was an upgrade discount promotion which expired June 1st of 2010 after running for a year and a half.
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 (See the Confirm QSOs with ADIF File... Menu command under the Log Menu).
This loose coupling and reliance on the international ADIF standard protects MacLoggerDX's stability from changes in 3rd party APIs.
MacLoggerDX supports real-time upload of your QSO's to Club Log.
There is also a user script written by Kevin Williams (WM4J) in the MacLoggerDX Yahoo Group File section which automates the upload and confirmation processes:
The latest version of DQSLManager is in the Files section (and in the MacLoggerDX download Extras folder). The setup instructions are in the readme file included in the zip archive.
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.
I changed the call sign of a QSO in the log, how do I change the DXCC ?
Each Log field including DXCC and DXCC Country can be edited by double-clicking in it, editing the data in the Edit field and then pressing <return> or tabbing out of that field. The change is instantly saved to your log.
Selecting the Update Selected Log Entries command from the Log Menu will look up the 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 ID), it will never overwrite existing data.
To update the DXCC values after a call sign change, set the DXCC numeric ID to 0, clear the DXCC Country field to blank and then Update Selected Log Entries with the new call and the new DXCC and DXCC Country will be entered automatically.
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.
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.
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:
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.