Note from Dave Rogers NR5K:The functionality to do this is built in to Fldigi via the <EXEC> macro. Any Fldigi QSO value like <FREQ>, <CALL>, <NAME> etc. can be sent to an AppleScript which invokes MacLoggerDX to log the QSO. Everything you need to know to do this is in the Fldigi and MacLoggerDX documentation.
Sample script from Dale Puckett K0HYD: "This fully functioning, self-documenting Applescript may be used to log QSOs from FLDIGI directly into MacLoggerDX. To get this to work required solving five puzzles. Those puzzles, or questions, along with their answers are explain in detail in the embedded documentation. Additionally, each section of the Applescript itself is fully document. I believe it will help other hams that need to set up an Applescript to send QSO information to MacLoggerDX from any other software that supports Applescript."
YouTube Video by Mike Greb AC2RK- fldigi logging to MacLogger DX.
No two applications can control the same Mac serial port, but if MacLoggerDX owns the radio CAT port then Fldigi can ask MacLoggerDX to key the PTT line.
In this configuration, MacLoggerDX owns the CAT connection to the radio and broadcasts the VFO values to Fldigi through UDP on your LAN. This allows click and tune operation of Fldigi from DX Cluster Spots in the MacLoggerDX feed.(don't run udp_listener at the same time as fldigi, it can steal the packets).
K3DCW: Both of the scripts (mldx5Key.scpt and mldx5Unkey.scpt from the Extras/V5 Scripts/cocoaModem Scripts folder) work just fine with the PTT between Fldigi and MLDX.
... for each of two buttons, labeled PTT ON and PTT OFF.
It works perfectly, at least with my K3 - the PTT method in MacLoggerDX depends on your radio and interface.
To fully automate the process, the user needs to address both scripts in the macro; the PTT on at the beginning and the PTT off at the end.
They also need to use the <TX> macro command to start sending text AFTER the PTT is keyed on, and the <RX> macro command to stop sending text before the PTT is released.
As there is no way to use the EXEC command somehow inline I built a "dirty workaround". This AppleScript just runs the whole time fldigi is opened in the background and detects fldigi's RX/TX status through the XMLRPC interface. According to this status it sends the RX/TX commands to MacLoggerDX.
Fldigi_PTT_DJ7AQ.scpt in MacLoggerDX Extras / Sample Files / Scripts / fldigi scripts / folder.
Fldigi_PTT_KA3DHV.scpt in MacLoggerDX Extras / Sample Files / Scripts / fldigi scripts / folder was added to fix a problem with the IC-7300.
We try to make it easy for any program to interface with MacLoggerDX.
Besides being able to import ADIF log files from any program, MacLoggerDX has been a standard Apple scriptable application since Version 5.0 was released.
MacLoggerDX supports an open and documented AppleScript interface for logging which cocoaModem integrates with seamlessly and has done so for years.
AppleScript is the standard for Mac interprocess communication and even though Fldigi does not provide this capabilty it can pass information to an AppleScript with the EXEC macro.
MacLoggerDX also broadcasts UDP packets over your LAN when the connected radio VFO changes or a QSO is logged (Enable UDP Broadcast check box in Station Prefs). The udp_listener application (a sample application provided for illustration) in the Download Extras folder will display radio report packets that MacLoggerDX transmits on UDP Port 9932 whenever the connected radio VFO changes. Source code for udp_listener is available here.
WSJT-X can control your radio directly or through MacLoggerDX.
In either case MacLoggerDX will log QSOs from WSJT-X, fill in any missing data from your Call Book (i.e. QRZ XML) and then optionally upload them to LoTW, eQSL etc.
MacLoggerDX will look up the WSJT-X DX Call when it changes. Spots are posted to the DXClusters/Spots table for all WSJT-X CQ and heard messages. These spots can be combined with the DXCluster or extra_cluster spots and you can set Alarms for these spots as well as setting Auto Lookup just as you would for dxcluster spots.
Note: "Make sure you are using MacLoggerDX's importADIF function so that data will be taken from JT-Bridge and WSJT-X only - it's enabled with the option "Don't let the logging application fill in data when logging a QSO" in JT-Bridge. For new installations of JT-Bridge this is now the default." - Anders.