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

Matching the digital mode to the path: decode thresholds, time sync, CAT and audio setup

ci_cover.jpg

Most problems with digital modes come from three things: a mode that doesn't suit the path, a PC clock that has drifted, or an audio chain that is overdriven. This thread is for comparing notes on all three.

Thresholds. Published decode thresholds are quoted as SNR in a 2500 Hz reference noise bandwidth, not in the bandwidth the signal actually occupies. That is why a signal 20 dB below the noise on the meter can still decode. Approximate figures: FT8 is about -21 dB, FT4 about -17 dB, and WSPR about -31 dB. WSPR is so sensitive because a 2-minute transmission is spread over roughly 6 Hz. Q65 has several submodes and period lengths, from 15 seconds to 5 minutes. The longer periods are meant for marginal paths such as EME, ionoscatter and weak tropo. MSK144 is designed for meteor scatter, where the useful signal is a burst of a fraction of a second to a couple of seconds, so a slow mode is no use there. Keyboard modes need much more signal. PSK31 and RTTY are readable on a modest path, but they don't approach FT8 at the noise floor. Olivia and other MFSK modes trade speed for robustness, which is why they are used for text on poor HF paths.

Time. FT8, FT4, WSPR, Q65 and MSK144 all run on fixed UTC T/R periods. If the PC clock is off by more than about a second, decodes drop sharply. Watch the DT column in WSJT-X. If most stations show a consistent offset, your clock is probably wrong, not theirs. Use NTP or a GPS source, and check that the sync service really is running and not just installed.

Audio and control. Set the rig to a data mode (USB-D, DATA-U or similar), turn off speech processing and any DSP noise reduction, and keep the receive filter wide enough for the whole passband. On transmit, set the power with the WSJT-X output slider and the rig's power control. The ALC should show little or no movement. A clean 50 W is better than an overdriven 100 W, because splatter spoils the decode for everyone nearby. CAT through Hamlib or the rig's native interface handles frequency and PTT. If it is flaky, check baud rate, stop bits and whether a second program is holding the COM port. Sound card interfaces range from the rig's built-in USB codec to a separate isolated interface. Ground loops and RF on the cables show up as hum, raised waterfall noise or random PTT drops, and ferrites plus a separate power feed are the usual cure.

Grid squares. Maidenhead locators like FN31 are two letters (field), then two digits (square), and in six-character form two more letters (subsquare). A four-character square is 2° of longitude by 1° of latitude, which is why FT8 exchanges are usually just four characters. Many award and VHF contest rules count in grids, so it helps to know your own six-character locator.

Which modes do you reach for on which bands, and what has given you the most trouble: time, audio levels or CAT?

  • Replies 2
  • Views 55
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

One point worth adding about thresholds: the quoted figure is the limit for decoding, not for a useful QSO. A QSO needs several decodes in a row, and fading can knock out one of them. In practice a path sitting right at -20 dB on FT8 will give you many incomplete exchanges.

FT4 is a good fit for contests and busy bands because the 7.5 s period halves the exchange time. You give up a few dB and use more bandwidth. For quiet, long-haul work, FT8 or Q65 on a longer period is usually the better choice.

JS8Call uses FT8-style modulation but adds free text, directed messages and relaying. It has several speeds. The slower ones decode weaker signals but take noticeably longer to send a message. If you only want to see who can hear you, WSPR gives you propagation data without a QSO, and the spots can show whether a band is open before you call CQ.

  • Administrators

For the Winlink side: Winlink is the messaging system, not a mode. Winlink Express can use VARA HF, VARA FM, ARDOP, Pactor and packet. VARA is proprietary, and the free version is speed-limited. ARDOP is the open option, although performance differs between the two. The usual ARDOP and VARA problems are audio level and PTT timing. Before transmitting into a gateway, make sure the modem's drive level is set so the rig isn't compressing or hitting ALC.

On fldigi: PSK31 and RTTY are easy to set up, but poor tuning is very visible. Click the signal on the waterfall and use AFC cautiously, since on a crowded band it can chase the wrong signal. Olivia and the MFSK modes are slower but tolerant of fading. Hellschreiber is different again, because you read the text visually off the screen. It is not a good match for the weak-signal digital modes. For the sound card, make sure Windows isn't resampling or applying enhancements. Also keep fldigi and WSJT-X from opening the same audio device at the same time, as one will usually block the other.

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.