Why a Receive-First LQ8 Lab Makes Sense
The LQ8 weak signal mode is timely because a September 2026 paper has placed it in front of technically curious operators, and current qFT8 documentation indicates practical software support for experimenting with it. For most HF operators, the right first question is not “Should I call CQ?” It is “Can I hear it, decode it, time it, and compare it fairly against FT8 and FT4 at my own station?”
That receive-first approach protects other operators from unnecessary QRM, helps you avoid chasing a mode that is inactive on your bands, and gives you a repeatable way to decide whether LQ8 deserves transmit testing. WSJT-X 3.0.2 is a logical baseline for FT8 and FT4 because WSJT-X is widely used for those modes, while qFT8 is the practical place to study LQ8 support and operating details. The goal is not to crown a universal winner. The goal is to produce station-specific evidence: decode threshold, time discipline, operator workload, and real on-air activity.
What You Can Compare Without Transmitting
A useful receive-only comparison does not require a perfect laboratory. It does require consistent conditions. You are comparing three things: the software’s ability to decode weak signals, your station’s timing and audio chain, and actual activity on the bands you operate.
- FT8: the familiar 15-second weak-signal workhorse for structured QSOs on HF and VHF.
- FT4: a faster mode used especially where quick exchanges matter, with a different tradeoff between speed and sensitivity.
- LQ8: a newer mode to evaluate from documentation, current software support, and your own receive observations before transmitting.
Do not assume that a paper result or a software claim will translate directly to your antenna, receiver, noise floor, computer clock, and band conditions. HF noise, AGC behavior, sound-device levels, and local RFI can dominate the result.
Sources to Read Before You Start
Before running a lab, read the primary material rather than relying on band gossip. Start with the September 2026 paper at arXiv:2609.06427. Then review the current qFT8 project information at qFT8.com and the qFT8 manual. Use WSJT-X as your FT8/FT4 reference implementation and confirm that you are using the intended version, such as WSJT-X 3.0.2, for your comparison.
Software behavior changes over time, so avoid writing down old menu paths as if they are permanent. Record the exact versions used, operating system, radio model, interface method, and settings that affect decoding.
Station Setup for a Fair Receive-Only Comparison
Hardware and signal path
Use the same antenna, feed line, receiver, sound interface, sample rate, and RF gain strategy for each mode. If you compare LQ8 on one antenna and FT8 on another, your result is no longer a mode comparison. It becomes an antenna, band, and noise comparison.
- Disable speech processing and transmit audio features; you are receiving only.
- Set receiver bandwidth wide enough to include the digital passband you are observing.
- Avoid heavy noise reduction, notch filtering, or aggressive DSP unless you use the same settings for all runs.
- Keep waterfall gain and audio levels in the normal decoding range. Overdriven audio can look impressive and decode poorly.
- Synchronize the computer clock with a reliable time source before each session.
For HF digital modes, time accuracy matters. A clock that is off by a second or two can make a good signal look bad. A receive-first lab should include a timing check before you blame a mode.
Recordings make the comparison repeatable
The cleanest amateur approach is to record audio or IQ from the same receiving session and replay it consistently. If the software allows decoding from saved files, use that. If not, you can still document live receive windows carefully. Saved recordings let you compare software settings without depending on changing propagation.
Label recordings with UTC date, band, frequency or dial setting, antenna, receiver bandwidth, software version, and whether the passband contained obvious interference. Do not publish other operators’ personal information beyond ordinary amateur call sign context, and be mindful of local rules and privacy expectations.
Measuring Decode Thresholds Without Inventing Numbers
A decode threshold is the approximate signal-to-noise condition where a mode stops decoding reliably. You do not need a calibrated RF laboratory to learn something useful, but you do need to avoid fake precision. If you cannot calibrate the whole chain, call the result “station-relative” rather than absolute.
Method 1: Relative audio attenuation
Start with a recording that decodes clearly in the target mode. Replay the same file while reducing audio level in known steps using audio software or a controlled playback chain. At each step, note whether the decoder produces the same messages, partial decodes, or no decodes.
- Use the same recording segment for each run.
- Change only one variable at a time.
- Repeat a step if results vary from run to run.
- Record the lowest attenuation step that still decodes consistently.
This does not give a formal published sensitivity number, but it can show whether LQ8, FT8, or FT4 is more tolerant in your station’s receive path under the same conditions.
Method 2: Live SNR distribution
During a busy band opening, collect decode reports from FT8 or FT4 over a fixed period, then collect LQ8 observations during a comparable period on the appropriate activity area if one is documented and legal for your privileges. Compare distributions, not one lucky decode. Write down the weakest repeated decodes, the number of unique stations heard, and how often decodes fail during QRM or fading.
The limitation is obvious: live HF conditions change. A 20-meter FT8 session at local afternoon and an LQ8 session after sunset are not equivalent. Treat live data as operating evidence, not laboratory proof.
Timing: The Hidden Variable in Weak-Signal Modes
Weak-signal modes rely on synchronized transmit and receive intervals. FT8 and FT4 operators already know that poor time sync causes missed decodes and awkward QSOs. When evaluating LQ8, timing deserves the same attention.
Build a timing checklist
- Synchronize the computer clock before the session.
- Confirm the radio is not adding unexpected receive latency through virtual audio routing.
- Check whether the software shows receive offset, DT, or similar timing indicators.
- Compare decode timing between software packages using the same saved recording when possible.
- Do not transmit until you understand the cycle timing and message structure for the mode.
If your FT8 decodes show large time offsets from many stations, investigate your own clock first. If only one station shows a large offset, that may be the other station. If every mode struggles, look for computer sleep settings, overloaded CPU, unstable virtual audio cable settings, or an unsynchronized clock service.
Measuring Real On-Air Activity
A mode can be technically excellent and still be quiet. Before calling CQ in LQ8, find out whether anyone is listening where you operate. Your receive-first log should answer four questions:
- Which bands show actual LQ8 activity from your location?
- At what UTC times do decodes appear?
- Are the decoded stations local, regional, or DX?
- Is the activity recurring or just a one-time experiment?
For FT8 and FT4, you will usually have enough activity to benchmark your station quickly. For LQ8, you may need multiple sessions across several days and bands. Do not assume silence means the mode fails. It may mean your timing, frequency choice, software setup, or monitoring window is wrong—or simply that no one was transmitting at that time.
A Practical Logging Template
Use a simple spreadsheet or station notebook. The key is consistency.
- UTC date/time: Use UTC, not local time.
- Band and dial frequency: Include enough detail to reproduce the session.
- Mode: FT8, FT4, or LQ8.
- Software/version: For example, WSJT-X 3.0.2 for FT8/FT4 and the qFT8 version used for LQ8.
- Antenna and receiver settings: Include bandwidth, preamp, attenuator, AGC, and DSP choices.
- Clock status: Note whether time sync was freshly checked.
- Decodes: Count unique call signs, weakest repeated decodes, and periods of no decode.
- Interference notes: Local RFI, contest congestion, splatter, or storm noise.
This template helps prevent the classic mistake of comparing a clean FT8 opening with a noisy LQ8 session and calling it a technical conclusion.
Decision Matrix: When to Move From Receive to Transmit
Consider transmitting only after the receive evidence is strong enough to make an orderly QSO likely. A practical go/no-go matrix might look like this:
- Go: You have confirmed software setup, time sync, receive decodes, message sequence, band legality, and an appropriate operating area.
- Wait: You can run the software but have not decoded any real LQ8 signals yet.
- Fix first: FT8/FT4 also decode poorly, suggesting a station, audio, timing, or RFI problem.
- Do not transmit: You are unsure of your license privileges, band allocation, emission compatibility, or local rules.
When you do transmit, start conservatively. Use the minimum power needed for the communication objective, keep ALC and audio drive under control, and monitor the waterfall for conflicts. Digital modes are not exempt from courtesy or spectral responsibility.
Safety and Regulatory Caveats
Always operate within your license privileges and the allocations that apply in your jurisdiction. In the United States, amateur operators must also consider RF exposure requirements, station identification, good engineering practice, and avoidance of harmful interference. Band plans are voluntary in many contexts but still important for orderly operation. Technical capability does not automatically mean legal or courteous operation.
Digital-mode experimentation can encourage long automated receive sessions. Make sure your station is electrically safe, ventilated, and protected against weather and lightning risks. If you are using outdoor antennas, disconnect during storms and follow safe installation practices. Receive-only operation is lower risk than transmitting, but the station environment still matters.
Common Problems and Fixes
No decodes in any mode
Check the clock, audio input device, receiver mode, bandwidth, RF gain, and whether the waterfall actually shows signals. If FT8 on a busy band produces no decodes, solve that before judging LQ8.
Waterfall looks strong but decodes are poor
Reduce audio level, disable excessive DSP, and check for clipping. Strong visual traces are not the same as clean demodulation.
LQ8 shows no activity
Confirm you are using current qFT8 documentation, the correct mode selection, and an appropriate monitoring window. Try multiple bands and times. A new mode may have sparse activity compared with FT8.
FT8 decodes but LQ8 does not
That may indicate low activity, wrong setup, unsupported assumptions, or an actual performance difference at your station. Use recordings and notes before drawing conclusions.
FAQ
Is LQ8 a replacement for FT8?
Not necessarily. Treat it as a mode to evaluate. FT8 and FT4 have large user bases and established operating habits. LQ8 may offer interesting weak-signal behavior, but practical usefulness depends on software maturity, activity, timing, and operator adoption.
Can I compare modes from signal reports alone?
Signal reports are useful but incomplete. Different stations, antennas, paths, and software settings can distort the comparison. A better approach combines recordings, controlled replay when possible, live observation, and careful station notes.
Should I call CQ if I have never decoded LQ8?
It is better to wait. Decode real signals first, confirm your timing and setup, understand the message sequence, and verify that transmitting is legal and appropriate on the band.
Why use WSJT-X 3.0.2 as the baseline?
Using a known FT8/FT4 implementation gives you a practical reference point. If your station cannot decode normal FT8/FT4 activity reliably in WSJT-X, your LQ8 experiment may be compromised by station setup rather than mode performance.
Key Takeaways
- The best first step with the LQ8 weak signal mode is receive-only observation, not immediate CQ.
- Use WSJT-X 3.0.2 as a practical FT8/FT4 baseline and qFT8 documentation for LQ8 setup.
- Measure station-relative decode thresholds with controlled recordings or carefully logged live sessions.
- Time synchronization, audio levels, receiver bandwidth, and local RFI can dominate weak-signal results.
- Move to transmitting only after confirming activity, legality, timing, message flow, and courteous spectrum use.
