ⓘ 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 — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
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
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.
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.
Link to comment
https://www.hamradiobase.com/forums/topic/11747-digital-mode-station-setup-audio-levels-cat-time-sync-and-picking-the-right-weak-signal-mode/Share on other sites