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 384.8 km/s
Aurora 1
Updated 13:30 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 mode station setup: audio levels, CAT, time sync and picking the right weak-signal mode

ci_cover.jpg

This thread is for the practical side of running digital modes, from a first FT8 contact to a Winlink gateway session or a meteor scatter attempt. Most problems with FT8, FT4, JS8Call, PSK31, RTTY and WSPR come from the same few places: the audio path, the computer clock, rig control, and picking a mode whose timing and bandwidth fit the propagation. Propagation is rarely the cause.

A quick map of the modes helps. FT8 uses 15 second transmit/receive periods and 8-GFSK in roughly 50 Hz of bandwidth. The WSJT-X documentation puts its decode threshold near -20 dB, in the standard 2500 Hz reference bandwidth. FT4 uses 7.5 second periods and about 80 Hz of bandwidth. It trades some sensitivity for speed, which suits contesting. WSPR is a beacon mode with 2 minute periods and a very narrow signal, and it decodes far below the noise floor. It is not for conversation, but it is a good propagation probe. Q65 and MSK144 target the harder paths. Q65 is used for EME, tropo and ionospheric scatter with several period lengths. MSK144 is built for meteor scatter, where a usable signal may last only tens of milliseconds to a second or so.

The older and keyboard-style modes work differently. PSK31, RTTY, Olivia, MFSK and Hellschreiber are normally run in FLDIGI. They have no fixed T/R clock, so timing matters less, but you need clean audio and proper tuning. JS8Call borrows the FT8 modulation family for keyboard messaging and relaying, with several speed settings that trade speed against sensitivity. Winlink is a different job. It moves email-style messages over RF using VARA, ARDOP, Pactor, packet and other transports, with a client such as Winlink Express and a gateway on the other end.

For discussion: when a new digital setup 'hears nothing' or 'gets no replies', what do you check first, and in what order? The questions I would start with are these. Is the computer clock actually disciplined? Is the rig in a data mode with the filters wide enough? Is the receive audio in a sane range? Is the transmit drive low enough that the ALC is not working? Is CAT or PTT being handled by one program only? Please also say which interface you use (built-in USB codec, external sound card box, or a rig with a USB audio device), since that changes the answers.

  • Replies 2
  • Views 10
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I would start with the clock, because it is the easiest thing to rule out. FT8, FT4, WSPR, Q65 and MSK144 all depend on both stations agreeing on the start of each period. WSJT-X shows the offset as DT for each decode. If DT values are consistently large across many stations, the error is probably on your side. The program can tolerate a second or so, but marginal decodes are the first thing you lose. Windows does not discipline its clock aggressively by default, so a dedicated NTP client or a GPS source is a sensible fix. Run it before the session and check that it is actually syncing.

Next is the audio path. In WSJT-X the receive level should sit in the lower-middle of the meter, and the documentation suggests aiming around 30 dB. Clipping the input does far more damage than a slightly low level. On transmit, set the rig to its data mode (USB-D, DATA-USB or equivalent) and turn off speech processing, compression and any EQ. Then lower the soundcard output or the rig's data input gain until the ALC shows little or no movement. Digital modes have a high duty cycle, so a rig run flat out can overheat, and any distortion splatters beyond the 50 Hz you meant to occupy. Lower power is usually the right answer, and it often reads cleaner on PSKReporter.

For CAT, the usual traps are mismatched baud rate or stop bits in the rig menu, two programs fighting over the same serial port, and wrong PTT selection. If you key through CAT, make sure the rig actually routes the audio from the data input. Some radios need the mic gain or the data-port selection changed. In WSJT-X, the Split Operation setting (Rig or Fake It) keeps the audio tones within a clean range, so the rig does not have to be driven from high audio frequencies. Remember that opening a second program on the same serial port can silently break control.

  • Moderators

On picking modes: it helps to match the mode to the path. FT8 is the default for HF because 15 second periods and a narrow signal make it forgiving. Its main weakness is crowding on the common frequencies. FT4 gives you more contacts per hour, but it needs a stronger signal and more bandwidth, so it is not the best choice on a marginal path. WSPR will show you where your signal is being heard without any operator on the other end, which is useful for comparing antennas or checking a band opening. Q65 is the one to look at for EME, tropo and scatter. The submode (A to E) and period length should match the expected Doppler spread, so follow the WSJT-X user guide and current activity conventions rather than guessing. MSK144 is for meteor scatter, usually on 6 m and sometimes 4 m or 2 m. Both stations need accurate clocks and a coordinated period plan.

Decode thresholds quoted in documentation are signal-to-noise ratios in a 2500 Hz reference bandwidth, so the same number means different things for a 50 Hz mode and a 3 kHz SSB signal. The SNR the software prints is an estimate, not a calibrated measurement. Treat it as a relative guide when comparing modes or antennas, and do not take the absolute figure too seriously.

Grid squares matter because most of these modes exchange a Maidenhead locator. FT8 messages carry four characters, such as the field-and-square pair, and a six-character locator adds the subsquare for finer position. Use your real grid, because it feeds the distance calculations, award tracking and propagation maps. For Winlink, the gateway list and the VARA settings matter more than the grid. VARA is a proprietary modem, so check the author's current licensing and the speed limits on an unregistered copy. ARDOP is an alternative if that is a concern. With sound card modes in FLDIGI, such as PSK31, RTTY, Olivia, MFSK and Hellschreiber, clean audio and correct tuning on the waterfall matter far more than software tweaks. Olivia and MFSK are built for poor conditions at the cost of speed, while Hellschreiber is more of a niche mode you can read by eye on the display.

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.