Jordan the author of JS8Call suggested using the API to do this.
I decided to see what was around and found this well documented js8net API library, with that I was able to interact with the API from the command line, and could read and set the frequency.
Python is not something I'm familiar with, so I used ChatGPT to help me write a python script that would cycle through a list of frequencies changing to the next one every few minutes.
The result was JS8BandHop, a fairly simple Python script.
How to configure MacLoggerDX and Flrig, with WSJT-X, Fldigi, JS8Call for rig control and one click log uploading to LoTW, QRZ, and Club Log.
Jump to:
My shack PC is an iMac 5K 27" (Late 2015), the rig is an Icom IC-7300. This is how I have it setup in the event anyone else finds it useful! This is a living post that I occasionally update.
MacLoggerDX is a well designed full featured logging application, it expects to own the rig CAT control with features that make use of rig control, and can share control with other applications via built-in DXLab TCP server.
Flrig is a nice rig control program providing control and feedback of most features. This is very useful when remoting into the shack mac, or directly. Flrig must own the CAT control and shares rig control with other applications via a TCP port (XMLRPC).
Fldigi is a well featured digital modes application, and supports many keyboard to keyboard modes such as DominoEX, Feld Hell, MFSK, Olivia, PSK31, RTTY, Thor, and more.
WSJT-X / WSJT-X Improved well known for FT8/FT4, I also use it for WSPR on HF, MSK144 and Q65-30A on 6m.
JS8Call / JS8 is a keyboard to keyboard chat mode which uses the FT8 protocol (with its error correcting/decoder tech) as the transport. JS8Call also supports mailbox, relays, position reports and email/sms via APRS (one way).
 |
| Flrig with MLDX connected, WSJT-X on 17m FT8, and Fldigi decoding end of ARRL digital broadcast on PSK31 (click for larger image - sorry the retina display makes for a large image) |
macOS contains the Silicon Labs drivers for Icom rigs, plug in the USB cable and it works.
Menu > Set > Connectors:
MacLoggerDX's DXLab TCP server, Flrig's xmlrpc server, and rigctld's TCP server when started bind to and listen on all network interfaces.
Since for simplicity they offer no authentication or encryption system, anything else that can reach the machine over the network can interact with and issue commands to these rig control applications.
Unless you highly trust your local network (anyone and anything else connected to it), and these applications are all on the same machine, it would be recommended to turn on the macOS firewall under System Preferences > Security and Privacy > Firewall and only allow incoming connections specifically as needed. Once turned on a prompt about allowing incoming connections to these applications will be shown, clicking Deny will still allow local machine access via the loopback address (127.0.0.1).
Note: MacLoggerDX is a signed application, the macOS firewall will silently add an exception for it. If the DXLabs TCP server is enabled it will be reachable from the network unless it's set to deny under macOS firewall settings which would limit it to local machine access only.
One way to authenticate and secure the communication for these applications between different machines over untrusted networks would be to tunnel the ports over SSH.
Testing connectivity to TCP ports using netcat (nc) e.g:
nc -zv 192.168.1.100 12345
http://www.w1hkj.com/flrig-help - Users Manual
https://groups.io/g/linuxham - Email list/forum
Flrig offers control of various radio functions and displays feedback.
With Flrig and my IC-7300 this lets me control most of the useful front panel controls - volume, NB/NR, ATT, Pre amps, Tuner on/off, output power, and more. Also displays useful information including signal level, Po, SWR, ALC, voltage etc.
The ALC reading is especially useful with digi mode apps to make sure audio drive levels are correct, e.g. no ALC action. SWR is also perhaps equally useful to know that things are working as expected - ALC action can also indicate high a SWR condition as well.
Very useful if you remote control the station, even if it's from another room in the house which I sometimes do.
Configure:
After configuring, close and re-open Flrig for the xmlrpc port change to take effect.
Needed for MacLoggerDX rig control via Flrig
https://hamlib.sourceforge.net/html/rigctld.1.html
Note: MacLoggerDX can be left disconnected to simply catch the logs which contain all the required info from digi mode apps. When on voice modes (SSB/AM/FM) digi mode apps and Flrig can be closed, rig control given to MacLoggerDX (check box top left on main screen) allowing it can capture and log mode/frequency automatically when manually logging a QSO. If that is sufficient then the rigctld setup is not needed. However MacLoggerDX has features that make use of rig control, and I like to minimize the number of steps/settings etc to do or change when changing modes..
How it works:
Setup:
Here is a script to start Flrig and rigctld, then close rigctld when Flrig is no longer running:
Save as Flrig-Rigctld.sh, from Terminal run "chmod +x Flrig-Rigctld.sh" to make it executable, and "./Flrig-Rigctld.sh &" to run it in the background (&), allows you to keep using that terminal session.
When I figure out a nicer way, I'll update this. I had tried to wrap the script in an macOS application bundle, but the while loop causes the icon to bounce in the dock forever.
What would be nice is if Flrig supported running shell commands on startup and exit.
https://dogparksoftware.com/MacLoggerDX.html
https://dogparksoftware.com/MacLoggerDX Help/MacLoggerDX Help.html - Online Manual
https://groups.google.com/g/macloggerdx - Email list/forum
Preferences > Station:
Preferences > Radio:
Preferences > Lookup > QRZ XML:
QRZ Logbook Upload API Key - QRZ forums.
The QRZ logbook can sync with LoTW to pull in confirmations.
Preferences > Look Up > Club Log:
Club Log among other things is good for tracking your progress, and requesting QSL cards if the op enables OQRS etc. Setup is simple, input your username and password, uncheck Show in comments (unless you want the date/time of the Club Log upload to be added to the comments).
Club Log can sync with LoTW to pull in confirmations.
Preferences > Look Up > LoTW:
Location name same as setup in TQSL.
Note: The location is useful for example if operating portable to activate a grid on 6m, setup the location in TQSL. Locations button under the Station tab can be used to manage different locations, or manually update grid on the Station tab, and the location name under Lookup > LoTW. Stations Prefs in the MacLoggerDX manual covers this.
Password is not needed unless one was set for the location in TQSL.
https://www.arrl.org/tqsl-download
It can take up-to a few minutes before the log entries appear in your QRZ logbook and LoTW.
For these Look Up and logging services, you can also enable the option to upload in real time for each or some. This removes of burden of constantly having to select and upload new log entries. If unsure about a log entry, uncheck Upload QSOs in Real Time (the main option above the different lookup tabs switches it on/off for all), log it, then decide what to do.
In WSJT-X, JTDX under Preferences > Reporting > Prompt me to log QSO, when checked a prompt to log the QSO will appear when RR73/73 are sent/received as the QSO is completed. If real time log uploads are enabled in MacLoggerDX, one click and the QSO is logged and uploaded to the configured services.
When more than one application will be consuming UDP packets, e.g. when WSJT-X and JT-Bridge are running together, switch from using a UDP unicast address (127.0.0.1) to a multicast address (224.0.0.1), open Terminal and run:
defaults write com.dogparksoftware.MacLoggerDX wsjtx_multicast_group "224.0.0.1"
For more info see
https://dogparksoftware.com/MacLoggerDX Help/mldxfc_wsjtx.html search the page for "multicast".
In WSJT-X, JS8Call, and JTDX > Reporting tab > UDP server, change 127.0.0.1 to 224.0.0.1
One annoyance I found with MacLoggerDX are its band plans (Preferences > Band Plan), if you go "out of band" to a "non-standard" FT8 frequency for example, then touch anything in MacLoggerDX it'll change modes on you to RTTY or CW - pretty annoying!
Fix is to edit/remove the CW and RTTY sub-bands, and add sub bands for USB-D mode to cover where you're likely to use digi modes.
The MacLoggerDX manual FAQ section recommends disabling iCloud Drive Documents and Desktop syncing.
I make use of iCloud Drive for my Documents, disabling it is not an option. I found that MLDX might be placing locks on some of the files it uses in the Documents/MLDX_Logs folder, this would cause syncing problems with iCloud Drive Documents where it would not always upload/download reliably and keep everything the same across multiple machines.
The work around I found was to rename MLDX_Logs to MLDX_Logs.nosync then create a symbolic link to it with the original folder name.
With MLDX closed, open terminal and run:
iCloud Drive will ignore any file or folder names ending in .nosync, while it will sync the symbolic link, it doesn't do anything with files/folders the link points to.
To make a backup copy of the MLDX_Logs and store them in iCloud Drive, create a new folder in Documents called MLDX_Backup, close MLDX and periodically copy the contents of MLDX_Logs over to it, or rely on Time Machine backups, or both.
MLDX Backup is a script I wrote and use to create backups into a backup folder under Documents which iCloud Drive syncs.
I still find on occasion the iCloud Drive syncing gets out of step the service can be restarted by running: killall bird
The process will then automatically restart, and everything gets caught up.
When MLDX is left running, overnight it should perform an Update Internet Files. For me this doesn't appear to work.
Once a week or so I run it manually from the File menu.
https://wsjt.sourceforge.io/wsjtx.html
https://wsjt-x-improved.sourceforge.io - WSJT-X Improved
Preferences > General:
Preferences > Radio:
Preferences > Audio:
Preferences > Reporting:
Receive: On quiet band with no signals (e.g. 10m or 6m tuned away to a quiet spot), adjust AF output in rig and/or macOS sound device sliders (if supported) to show 30 dB. This is what the WSJT-X user guide suggests under section 5 Transceiver Setup > Receiver Noise Level.
When I've seen weak signal ops (160m and below, 6m and above) discussing receive levels, For FT8/FT4 they recommend setting the level to show 60 to 80 dB, and AGC set to fast for best performance. With the FT modes and ~60 dB, the quick and short reason is weaker signals will be with-in the dynamic range of the A/D converter, at 30 dB they wont be.
For MSK144 and Q65 I've seen 30 dB and AGC off recommended.
The setting to adjust in the IC-7300 is ACC/USB AF Output Level.
Clipping and over driving in the receive audio chain can also occur, be aware of that.. I had a local telling me on 6m FT8 I had harmonics all over the band with a screen shot to prove it (it looked awful), after some tests with another local said it was clean, if the issue was my transmit levels then everyone should see the problem.
What do I use? Currently 60 dB and AGC fast (0.1s) is the default I leave things set to, adjusting them for MSK144 and Q65 as needed (memory permitting).
Transmit: Detailed document FT8 - Avoiding Harmonics and Audio Settings by W9MDB. Recommend reading and working through the document as it goes into good detail, including understanding ALC behavior which varies with different radios. This post by Bill G4WJS (SK) also talks about ALC.
Basic steps for reference:
Optional, but nice to do.
https://lonneys-notebook.blogspot.com/2022/06/wsjt-x-freqcal-waterfall-flattening.html
WSJT-X includes cty.dat (Country data), this helps map callsigns to their actual locations/entity.
WSJT-X Improved 2.7.x (rc) has an option to download cty.dat in Preferences > Colors tab.
Otherwise updated cty.dat files can be placed in the log directory:
https://www.country-files.com/contest/wsjt-x
Big CTY: https://www.country-files.com/category/big-cty
The Big CTY file will also work, tested this with a KL7 station located in Oregon. They were calling CQ with CN84 grid, WSJT-X showed their entity as Alaska, checking QRZ showed they were located in Oregon/CN84. After dropping in the big cty.dat file into the log directory and restarting WSJT-X their entity was correctly shown as USA.
Some notes on configuring and using Q65 on 6m for EME, terrestrial, and auroral scatter.
https://lonneys-notebook.blogspot.com/2022/04/try-out-6m-q65-eme-or-terrestrial.html
WSJT-X can also be built from source on macOS.
https://lonneys-notebook.blogspot.com/2023/06/how-to-build-wsjt-x-from-source-on-macos.html
https://sourceforge.net/projects/jtdx/files
https://jtdx.freeforums.net (Support forum)
JTDX is an alternative to WSJT-X for some modes. Basic configuration is essentially the same as WSJT-X in JTDX v2.2.159.
I like consistency..
I was able to make the color coding match by having both WSJT-X and JTDX pref windows open, and use the eye-dropper tool to match the colors.
JTDX uses the same two log file names wsjtx.log and wsjtx_log.adi, one of the things these are used for is color coding what entities/stations/bands you've worked or not.
If like me you want to have the luxury of being-able to switch between these two apps have it all match up and be the same, this can be done by creating two symlinks:
JTDX's S meter and Output power options (enable on the Radio settings tab) also work (displayed top right corner) when using Flrig for CAT control.
JT-Bridge is the Mac equivalent of JT-Alert. This tool becomes increasingly useful as you need to start looking for countries, states, or grid squares that are hard to get or have not yet been logged and confirmed, this helps filter all band activity down to what you're looking for or need by syncing with the MacLoggerDX log. As QSOs show confirmed in MacLoggerDX by running Log > LoTW Confirmations, JT-Bridge is kept in sync by running File > Sync with Logger.
Preferences > Network:
There is also GridTracker, but I have not gotten into using it yet.
https://jp1lrt.asablo.jp/blog/2021/06/25/9391328
With WSJT-X v2.5.4 I get 58 decodes, with JTDX defaults 62, and after tweaking the settings 68. My Late 2015 iMac has a 4 GHz Quad Core i7-6700K CPU - this was the highest CPU option available in these at the time!
On busy bands CPU performance makes a big difference. Further discussions I've seen also indicate more memory helps. If we want the bleeding edge of performance out of the FT modes then max the CPU and memory options, close all unnecessary applications etc.
Since WSJT-X v2.6.0-rc became available for testing, it's very close to JTDX defaults with the number of stations decoded each cycle, sometimes a few more, a few less, but always fairly close from what I've seen.
With the sample file and WSJT-X 2.6.1 I get 67 decodes, but I've seen as many as 103 on a busy 10m band (many JAs calling a V26 station) - that above file may not be the ideal test of the decoder performance? Perhaps what we need are set of test files better suited to use as benchmarks for WSJT-X.
Maybe we can squeeze a little more decoder success by renicing WSJT-X or JTDX to give it a higher priority?
I have used htop (brew install htop) to renice the WSJT-X jt9 process to -20 (maximum, yes less is more) - jt9 process appears to be doing the decoding as it spikes in CPU use during the decodes at the end of each FT8 sequence, wsjt-x process is the rest of the application from what I can tell, its CPU use increases when menus and options are clicked/changed etc
https://www.g4ifb.com/FT8_Hinson_tips_for_HF_DXers.pdf - highly recommended reading!
http://files.js8call.com/latest.html (2.2.0)
https://github.com/js8call/js8call/releases (2.3.0 and later)
https://groups.io/g/js8call - Email list/forum
Basically the same as WSJT-X, except the radio tab has two sub tabs - CAT Control and Rig Options. TCP server and port address is set under CAT Control but confusingly appears as a greyed out unchangeable option under Rig Options!
Preferences > Radio:
Preferences > Audio:
Prior to MLDX v6.46, in JS8Call if the UDP port was changed to 2237 under the Reporting tab, logging a QSO in JS8Call would also send the log to MLDX the same with WSJT-X, but WSJT-X changed the API and MLDX was updated to suit, which broke this functionality with JS8Call.
Since this change, log a QSO as per normal in JS8Call, then open the logs directory Log > Open Log Directory, right/control click the js8call.adi file > Open With > MacLogger DX to import any new QSOs from the ADI file.
I got into JS8Call a while back because I was interested in APRS over HF. I also enjoy the keyboard chat modes too.
https://wikipedia.org/wiki/Fldigi
http://www.w1hkj.com - Downloads
http://www.w1hkj.com/FldigiHelp - Users Manual
http://www.w1hkj.com/beginners.html - Beginners guide to Fldigi
http://www.w1hkj.com/modes - Sights and sounds of digi modes
https://sourceforge.net/p/fldigi/wiki/osx_howto/ - How to compile Fldigi on macOS
https://groups.io/g/linuxham - Email list/forum
Configure:
The _Log2MLDX.scpt included with the MacLoggerDX disk image didn't work properly for me.
Logging on MacLoggerDX with Fldigi is a Python script I found searching the MacLoggerDX Google group, it works perfectly.
The Nov 27, 2022 version uses an ADIF import, after clicking the macro button in Fldigi, MacLoggerDX will prompt to import the file and add it to the log, however MLDX will not auto upload imported logs (if this is enabled/used).
After an email with Fred it sounds like a future update may include UDP as an option again to eliminate the import prompt from MacLoggerDX.
If Fldigi was previously setup to work with MacLoggerDX using the work arounds, these can be undone:
QSO Today with Dave W1HKJ (author of Fldigi, Flrig, and more).
70 Years of Amateur Digital Modes - pretty interesting !
DominoEX and DominoEX FAQ.
Data & Text mode Digital Radio Communication - VU2NSB.
Feld Hell Club - Info about the mode, frequencies, and nets.
FSQ (Fast Simple QSO) - Info about the mode and frequencies.
I came across a lot of PSK31 activity by chance (7.070, 14.070), but it took a while to figure out how to take part..
Frustratingly the information needed to simply get setup and get going is not found in one place. I like to give points to field day/contest stations but not seriously compete. Are they trying to get more people into contesting by keeping it mysterious?
Info collected from:
I set these up on an empty macro row in Fldigi:
ANS CQ (Answer CQ):
W/FD Exch (Send exchange for your station, e.g. 1H is single home op, WWA is western WA):
73 (Send when your exchange was copied):
QSO @>> (Start free text message):
RX (Go back to receive):
Simple method using WSJT-X to do frequency calibration of an Icom IC-7300 (or any rig with a reference adjustment), and waterfall flattening.
I got the idea from this post https://groups.io/g/icom705/message/532
Let the radio warm up for a couple hours or so in a room at average operating temperature. Mine is on 24/7 since I leave it running overnight on 160m FT8, or 6m MSK144 to spot meteor scatter stations, so there is no warming up and cooling down :-)
WSJT-X has a FreqCal mode - the manual covers how run a calibration cycle which will work with any radio by configuring WSJT-X to do an internal adjustment compensating for the radio, or it can also be used to align the radio it self - easy if it offers a reference adjustment via a menu option.
If in range of WWV or WWVH, or another (highly) accurate time standard broadcast, edit the FreqCal frequencies (Settings > Frequencies) to use only those you can receive.
Switch to FreqCal (Mode menu) and select one of the time standard frequencies from the frequency/band drop down.
WSJT-X sets the radio to USB mode and 1500 Hz below the carrier frequency, it then measures tone or heterodyne and displays the frequency.
If your radio has a frequency reference adjustment such an the Icom IC-7300 (Menu > Set > Function > REF Adjust) adjust it until you are close as possible to 1500 Hz in fMeas column or 0.0 in DF column.
Here I was able to get very close using WWV on 10 MHz, I see about the same DF on WWV at at 5 and 15 MHz. It will drift slightly with changes in room temp which you can see by repeating the measurement.
If the radio doesn't have a user setting for frequency reference, execute a WSJT-X frequency calibration cycle per the manual with the Measure box checked (this writes the fmt.all file in logs directory). I found I had to let it run for at least two or three cycles. Edit fmt.all and remove any lines with a * at the end, then run solve for calibration.
The latter may be more accurate, WSJT-X will apply the offset needed internally, but I didn't like it showing this offset subtracted/added to the WSJT-X frequency display (blame OCD) and it only applies to WSJT-X when it is running.
More words about FreqCal by AG6EE at WSJT-X Calibration.
A good guide by KA1GT - https://bobatkins.com/radio/wsjtx_wide_graph.html - while orientated for EME use the steps can be followed to optimize your waterfall.
After running through all that this is what my waterfall looks like
The one signal at 1090 Hz is -17 dB on a quiet 6m band.
With a 6m Yagi and weak signal digital mode Q65-A it's possible to receive EME (Earth Moon Earth) signals during moonrise or moonset.
Q65 can also be used for terrestrial contacts where other weak signal modes such as FT8 may not succeed.
It's also possible to do "QRP EME" on 2m and 70cm, see QRP EME - An incomplete Guide (KG5CCI).
Note: Unlike on FT8, WSJT-X wont make use of Split fake it/rig to keep the TX audio in the middle of the filters, if you get too far away from 1500 Hz power output will start to drop off.
Mode > Q65
6m > 50.275 MHz
File > Settings > Enable VHF and sub-mode features (not sure that is required)
File > Settings > Decode after EME delay - only used for EME, leave unchecked for terrestrial - though I’ve had this checked and its worked ok.
Decode > Fast for terrestrial (remember to set this back to normal or deep for FT8 and other modes). Enable averaging, and Auto clear AVG after decode on.
Terrestrial: On the main WSJT-X screen set the offset to 1500 Hz, F Tol to 100 or 200, Submode A, T/R 15 or 30 - these last two settings indicate the mode, e.g. Q65-15A, Q65-30A.
Once a QSO starts change F Tol to 100, 50, or 20.
WSJT-X Wide Graph has a Q65_Sync setting.
https://wsjtx.groups.io/g/main/topic/83263895 that post has a lot of info about terrestrial Q65. Suggests that using 15s T/R for Q65-15A is very close in performance to 30A, and twice as fast. Also covers other sub-mode combinations and QRP use.
In practice 30-A on 6m seems to be the most commonly used Q65 submode.
Here is a more recent QSO on 6m Q65-30A with W7OUU who is 500 mi / 800 km south east of me in Idaho, the band was otherwise closed with no FT8 activity.
They were running 1.1 kW with 7 elements, I was running 85 watts with 3 elements. This QSO took around 45 minutes to complete, and 15 minutes before I got the first decode (Q65 averaging at work):
I was able to reliably decode them on nearly every cycle after the first decode, with my much lower power output and lower gain antenna it took some time for them to decode my messages, but we got there in the end, and DN22 is a new grid on 6m for me too!
I've since worked W7OUU again, and WB7UNU in Spokane 200 miles east for another new grid with the band was otherwise closed.
Final thought: Since Q65 uses averaging to build confidence in subsequent decodes, and can take advantage of any propagation mode (tropo, aircraft scatter, meteor scatter, etc), this QSO may have used a combination of these to complete with enough "fragments" eventually making it though for a successful decode.
With a recent Auroral opening (23-Mar-2023) on 6m was the first time I'd experienced this. On SSB and CW the signals were quite distorted which is normal, but they are readable.
It was then suggested to try Q65-30C or Q65-15B (same tone spacing, half the time). Listening to the tones with the volume up they sounded distorted, and yet it worked reliably. I was able to complete a couple of QSOs quite easily with good decodes on each sequence, and one on SSB:
This was quite a nice surprise, as the distorted FT8 signals I heard did not decode. Q65 certainly seems to be the magic mode for the magic band!
My interest in EME starts in the mid 90s when I was a freshly minted new ham, friend and I got invited (likely we invited our selves) to see Paul ZL1PE's 2m EME setup. Back then it was CW only (no digital modes existed then for EME, or much else).
Paul had built an H stack of four long boom 2m Yagi's with elevation and azimuth rotator, home brewed an amplifier using something along the lines of a 3CX1000 (I forget exactly), high gain masthead pre-amp and high powered coaxial relays, the feedline was hardline. Amazing stuff to see, and a lot of effort for a propagation mode where you could only use CW when the moon was up.
With the advent of digital modes and home computers faster than we could imagine 30 years ago and now take for granted, the barrier to entry for EME is much much lower.
Much thanks to Bob ZL1RS for most of the EME information.
Find when and where the moon is with something like https://www.timeanddate.com/moon/
With a Yagi pointed at the horizon (a regular horizontal Yagi installation) the added advantage of ground gain can be made use of during moonrise and moonset.
Antenna height, higher not always better! Consider these two 4NEC2 plots of 7 element Yagis at different heights, one at 7 meters / 23 feet vs 18 meters / 60 feet:
 |
| Plot by Bob ZL1RS |
Red is the Yagi at 7 meters, it has one broad lobe that will cover between the horizon and about 15 to 20 degrees elevation. The same antenna at 18 meters, has 3 lobes, the moon will pass through each of those much quicker and be "lost" in the nulls.
Test 1 - Disconnect the antenna and with WSJT-X note the noise floor with the dB meter bottom left. If there is a difference of more than 10 dB when connected, the local noise floor might be too high.
Test 2 - Preamps - With antenna aimed at moonrise/set direction, turn preamp(s) on and AGC to fastest setting. If any signal level is registered on the S meter (indicating AGC action in the receiver) the local noise floor might be too high.
For me living in city my local noise floor is too high based on the second test as I get AGC action in the receiver. I'd need use to higher gain Yagi(s) with elevation rotators to get away from the noise sources when the moon is (much) higher in the sky.
Mode > Q65
File > Settings > Enable VHF and sub-mode features (not sure that is required)
File > Settings > Decode after EME delay (that one is important)
Decode > Deep (some say fast is more sensitive). Enable averaging, and Auto clear AVG after decode on
On the main WSJT-X screen set the offset to 1500 Hz, F Tol to 100 or 200, Submode A, T/R 60 (these last two settings indicate the mode, e.g. Q65-60A).
WSJT-X Wide Graph has a Q65_Sync setting.
Most EME activity is in the 50.180 to 50.210 area with 50.188 to 50.208 being most popular for sked arrangements. You wont find it tuning around.
A DT of 2.5 seconds indicates EME, DT of 0.0 or 0.1 indicates terrestrial propagation modes.
ON4KST runs an online chat service (runs in browser), goto http://www.on4kst.info/chat/start.php and choose EME all bands/mode, this is where coordination between stations happens.
HB9Q EME Logger is another.
Receiving Q65 via EME is the first step, transmitting typically power levels around 1 kW are used.
For a time FT8 seemed pointless to simply log the minimum for a contact in an automated way and move on, the social side and having a chat getting to know someone, and share ideas is removed from the equation.
I always did see FT8's good points and purpose, its a weak signal mode, efficient, and gets the job done neat and tidy.
Ideal for contesting, special events, or working a DX-Pedition for example to get that rare one in the log where all that is happening is exchanging of callsigns and signal reports anyway. FT8 simply took that function, and made it efficient. No problem with that.
But I was being a Curmudgeon, so back in April this year I tried out FT8 to at least figure out how to drive it. With a busy summer out of the way and fall around the corner I decided time to get a little more serious and start using logging software and maybe work towards getting awards, and QSL cards to stick on the wall.
The result was MacLoggerDX, WSJT-X, JS8Call, Fldigi and Flrig Integration. MacLoggerDX does the right things, and once configured makes rig control, and logging contacts with WSJT-X, JS8Call, and Fldigi seamless, couple mouse clicks and its all done. Now there is no excuse, the tools are in-front me to get to work.
Now it makes sense, a lot of sense. Most FT8 ops upload logs to LoTW, which is appreciated if like me you want them to also count towards awards for example. After a few weeks I had logged and confirmed contacts all over the world, and sent and received a number of QSL cards.
This reminded me how much I enjoyed sending and receiving paper QSL cards too. Today when everything is electronic and instant, it's nice to receive a physical object from somewhere that took a journey.
This mode also spurred me to upgrade my antenna systems. The OCFD was replaced with 130 ft doublet fed with 600 ohm line into a remote auto tuner which is interfaced to the rigs ATU port. This makes band changes seamless, and enables me to operate on all bands 160-10m. I finally assembled the 6m 3 element LFA Yagi I had bought, which then blew down in strong winds a few weeks later, and since tediously unbent with a vice, straight edge and a mallet. See Thats the end of Six meters for a while..
Maybe the spark gap ops didn't like the new kids running vacuum tubes at the time either. It's just an evolution of technology that enables us to set the bar higher. DXCC is easier, so we get that then set the next goal and keep going, and/or set goals with friends and compete.
For example, KL2R and I set the goal of a clean sweep, logging and confirming a contact on every band. This turned out to be quite fun.
I've also logged contacts with friends I've since not heard from in a long time, and follow ups via email sometimes result which is a nice surprise.
All the same I enjoy text chats on JS8, PSK31, and talking to people on voice modes just like always. Remember to stop and smell the roses.
I've simply added an additional mode I can use for awards and other goals, and to get some of those nice QSL cards that would otherwise be much harder or if not impossible to get.
100 countries confirmed in LoTW under three months - I started on September 10th, and 100th country was confirmed on December 1 by E75C. Simply from putting in a consistent effort with a modest station - a single wire antenna, 80W, sometimes 350W when needed.
Time for a break from chasing DX, work on some other projects and think about the next goal..
I got around to trying out FT8, the HF digital mode that everyone seems to be doing these days. I guess don't knock it until you try it..
It makes completing a contact very easy after setting some options.
Answering a CQ just double click station calling CQ, from there the process of your station answering, the exchange of callsigns, grid square and signal report are fully automated.
Calling CQ is simply clicking enable TX and waiting for others to answer, the same automated process takes over and completes the contact.
I can see this has it's uses with contesting, working a DX-Pedition under trying conditions to get that rare one for example since its simple, automated and completes a contact in five 15 second T/R sequences.
Here on the 17m band yesterday evening completed my very first ever FT8 contact with ZL2DD.
