Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 412.9 km/s
Aurora 1
Updated 14:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Digital modes toolchain: choosing between FT8, FT4, JS8Call, PSK31, RTTY, WSPR, Q65 and MSK144, and where setups usually break

ci_cover.jpg

Digital operating is really two problems stacked together. The first is picking a mode that fits the path and the goal. The second is making the station behave: audio levels, CAT, and a clock that is actually right. Most "the software is broken" threads turn out to be the second problem.

Rough mode map. FT8 uses 15-second T/R periods, 8-GFSK, and about 50 Hz of occupied bandwidth. Its decode threshold is around -20 dB SNR, referenced to a 2500 Hz noise bandwidth. FT4 is faster (7.5 s periods, roughly 80 Hz wide) and gives up a few dB of sensitivity, which makes it better suited to contest-style exchanges. WSPR is a beacon mode with 2-minute transmissions and a very narrow signal. Its threshold is around -30 dB, so it is a propagation tool rather than a QSO mode. Q65 has several T/R period and tone-spacing submodes and is aimed at hard paths such as EME, tropo and ionospheric scatter. MSK144 is built for meteor-scatter pings, where the usable signal may last only a fraction of a second.

JS8Call borrows FT8-style modulation but adds free-form keyboard messaging, relaying and store-and-forward. Its speed settings trade throughput for sensitivity. Older keyboard modes are still useful: PSK31 (31.25 baud, very narrow, but weak against fading and QRM), RTTY (45.45 baud, 170 Hz shift, the standard in contests), Olivia and other MFSK variants (strong forward error correction, slow, good in poor conditions), and Hellschreiber (readable by eye, which is its oddity and its charm). Winlink is a different animal. It is message transport rather than a chat mode, using gateways and modems such as VARA, ARDOP or Pactor. VARA is proprietary, and its free version is speed-limited.

Questions to get the thread going:

  • What is your checklist for a station that shows signals on the waterfall but decodes nothing?
  • How do you decide between a sound card interface with CAT and a simple VOX or RTS/DTR PTT setup?
  • For weak-signal work, how much do you trust the dB figures that decoders report?
  • Replies 2
  • Views 32
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Start with the clock. FT8, FT4, WSPR and Q65 all depend on both stations being within a fraction of a second of true time. In WSJT-X the DT column tells you how far off you are. If your decodes cluster at +0.8 or -0.6 instead of near zero, fix the clock before touching anything else. The default Windows time service syncs infrequently, so a dedicated NTP client or a GPS-disciplined source is the usual fix. Make sure the correction is actually being applied and not only displayed.

Second, audio level. The rig's ALC should show little or none on a data mode. If the ALC is moving, the audio drive is too high. The result is splatter and a signal that looks fine on your own waterfall but is wider than it should be. Turn the PC output down and set power with the rig's own power control. Also disable system sounds and any audio "enhancements" on the interface's sound device, because a notification chime going out over the air is a very real failure.

Third, CAT. The usual culprits are mismatched baud rate, stop bits or rig address (on CI-V radios), a USB virtual COM port that renumbered after a reconnect, and two programs fighting for the same port. If WSJT-X reports a rig control error, confirm that nothing else (a logger, a rig control program) holds the port. In the Radio settings, "Split Operation" with Rig or Fake It keeps the audio tones in a clean part of the passband. It does this by shifting the dial frequency, not by pushing the audio offset around.

On PTT: CAT PTT works well when the rig supports it cleanly. RTS/DTR through a serial line is fine, but some USB chips toggle those lines at port open, which can key the transmitter momentarily. VOX on a data mode is the most fragile of the three.

  • Moderators

On the dB question: treat reported SNR as a rough, mode-relative estimate, not a calibrated measurement. The figures are normalized to a 2500 Hz reference bandwidth so that different modes can be compared, but the estimate gets unreliable at the extremes, and QSB or a nearby strong signal can shift it. It is perfectly good for "did this change help?" comparisons on one band. It is a poor basis for ranking antennas by fractions of a dB unless you average many spots.

For choosing a mode, think about what limits you. If the path is simply weak but steady, a slower, narrower mode wins on sensitivity. If the path is short-lived, as on meteor scatter, a slow mode may never finish a message, which is why MSK144 uses fast, repeating bursts. If the band is crowded and you only need a quick exchange, FT4 or RTTY may fit better than FT8. For keyboard conversation with weak signals, JS8Call's slower speeds buy sensitivity at the cost of a long wait for every line. Olivia and other MFSK modes make a similar trade, with lots of redundancy and very little speed.

Grid squares matter because most of these modes exchange them directly. Maidenhead locators go field (two letters), square (two digits) and subsquare (two letters), for example FN31pr. FT8 messages normally carry only the four-character form. Entering a wrong or stale locator in the settings will not break decoding, but it will distort distance calculations, award tracking, and the map that others see for your spots. For VHF weak-signal work, six characters are worth the effort.

For Winlink, check the gateway's band, mode and distance first, then confirm the PC clock and audio chain just as you would for FT8. A poor VARA link is often an audio-level or noise problem on the receiver side rather than a software fault. Be sure you know the licence and content rules in your jurisdiction before sending messages through a gateway.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.