ⓘ 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
Winlink over radio: a practical setup checklist (gateways, modes, forms, passwords, P2P)
This is a working outline for getting a station from zero to sending Winlink messages over RF, plus the points where setups usually go wrong. Corrections and additions are welcome, especially on mode choice and form handling.
Start with Telnet. In Winlink Express, enter your callsign, create or confirm your account password, and run a Telnet Winlink session first. It uses the internet rather than a radio, so it confirms your account, password and message database before RF adds variables. Passwords are case-sensitive, so a login failure is often a capitalization or typo problem. Set up password recovery while you still have internet access.
Choose the mode by path. Packet (AX.25, typically 1200 baud on VHF/UHF) suits local RMS packet gateways and needs a hardware TNC or a software TNC such as Direwolf. Winlink Express can talk to a hardware TNC, to KISS over serial or TCP, or to an AGWPE-style interface. VARA FM is the sound-card option for FM paths, with narrow and wide variants. It needs clean audio and a radio that can pass the data bandwidth. VARA HF and ARDOP cover HF, and both are sound-card modems. VARA HF is commonly run in 500 Hz or 2300 Hz bandwidth, and its free version is speed-limited unless you register it. ARDOP is free and open. Pactor needs a dedicated hardware modem. Higher Pactor levels need a modem that supports them, so check what your hardware actually supports.
Sound card and radio setup. Most data-mode problems come from audio levels and PTT. Pick the right sound devices in the modem software, set up PTT through CAT, serial RTS/DTR or a USB interface, and turn the transmit drive up only until you get clean output. On HF, watch ALC and keep it from moving much. An over-driven SSB signal splatters and costs you throughput. On FM, over-deviation is the equivalent mistake. Disable computer sound effects and make sure Windows does not resample or change the levels.
Gateway selection. Each RMS channel list in Winlink Express shows gateways with frequency, mode, distance and bearing, and HF lists can include propagation predictions. Update the list while you have internet and keep an offline copy, because you may need it when the internet is down. A listed gateway is not a guarantee. Check recent status and try more than one. Frequency conventions matter on HF, so confirm whether the listing is a dial frequency or a center frequency, and how your rig control handles USB offset.
Radio-only and P2P. A Telnet session reaches the Winlink system over the internet, while a radio-only workflow is meant for situations where traffic should travel without internet dependence. Read the current Winlink documentation on how radio-only messages are handled before relying on it. P2P (peer-to-peer) skips the gateway entirely. One station opens a P2P session to a specific callsign, and the other listens in the same mode on an agreed frequency. That is useful when gateways are down or too far away, but it needs coordination and careful frequency choice so you do not interfere with existing activity.
Forms and ICS-213. Winlink Express can fill templates, including the ICS-213 General Message, and send the form data as a small attachment, so the message stays compact over a slow link. The recipient generally needs Winlink Express, and templates up to date, to see the form rendered. Otherwise they may see only the plain text. Keep attachments small, avoid images on HF, and remember amateur-radio rules on content and identification still apply.
Practice. Winlink Wednesday is a community weekly practice exercise. Check the current schedule and instructions from the Winlink community rather than relying on a forum post. Practice sessions are a low-pressure way to test your whole chain, including gateway choice, levels, message composition and form use.
Questions for the thread: which mode do you use as your first choice for local EmComm, and how do you decide when to fall back to P2P?
This is a working outline for getting a station from zero to sending Winlink messages over RF, plus the points where setups usually go wrong. Corrections and additions are welcome, especially on mode choice and form handling.
Start with Telnet. In Winlink Express, enter your callsign, create or confirm your account password, and run a Telnet Winlink session first. It uses the internet rather than a radio, so it confirms your account, password and message database before RF adds variables. Passwords are case-sensitive, so a login failure is often a capitalization or typo problem. Set up password recovery while you still have internet access.
Choose the mode by path. Packet (AX.25, typically 1200 baud on VHF/UHF) suits local RMS packet gateways and needs a hardware TNC or a software TNC such as Direwolf. Winlink Express can talk to a hardware TNC, to KISS over serial or TCP, or to an AGWPE-style interface. VARA FM is the sound-card option for FM paths, with narrow and wide variants. It needs clean audio and a radio that can pass the data bandwidth. VARA HF and ARDOP cover HF, and both are sound-card modems. VARA HF is commonly run in 500 Hz or 2300 Hz bandwidth, and its free version is speed-limited unless you register it. ARDOP is free and open. Pactor needs a dedicated hardware modem. Higher Pactor levels need a modem that supports them, so check what your hardware actually supports.
Sound card and radio setup. Most data-mode problems come from audio levels and PTT. Pick the right sound devices in the modem software, set up PTT through CAT, serial RTS/DTR or a USB interface, and turn the transmit drive up only until you get clean output. On HF, watch ALC and keep it from moving much. An over-driven SSB signal splatters and costs you throughput. On FM, over-deviation is the equivalent mistake. Disable computer sound effects and make sure Windows does not resample or change the levels.
Gateway selection. Each RMS channel list in Winlink Express shows gateways with frequency, mode, distance and bearing, and HF lists can include propagation predictions. Update the list while you have internet and keep an offline copy, because you may need it when the internet is down. A listed gateway is not a guarantee. Check recent status and try more than one. Frequency conventions matter on HF, so confirm whether the listing is a dial frequency or a center frequency, and how your rig control handles USB offset.
Radio-only and P2P. A Telnet session reaches the Winlink system over the internet, while a radio-only workflow is meant for situations where traffic should travel without internet dependence. Read the current Winlink documentation on how radio-only messages are handled before relying on it. P2P (peer-to-peer) skips the gateway entirely. One station opens a P2P session to a specific callsign, and the other listens in the same mode on an agreed frequency. That is useful when gateways are down or too far away, but it needs coordination and careful frequency choice so you do not interfere with existing activity.
Forms and ICS-213. Winlink Express can fill templates, including the ICS-213 General Message, and send the form data as a small attachment, so the message stays compact over a slow link. The recipient generally needs Winlink Express, and templates up to date, to see the form rendered. Otherwise they may see only the plain text. Keep attachments small, avoid images on HF, and remember amateur-radio rules on content and identification still apply.
Practice. Winlink Wednesday is a community weekly practice exercise. Check the current schedule and instructions from the Winlink community rather than relying on a forum post. Practice sessions are a low-pressure way to test your whole chain, including gateway choice, levels, message composition and form use.
Questions for the thread: which mode do you use as your first choice for local EmComm, and how do you decide when to fall back to P2P?
Link to comment
https://www.hamradiobase.com/forums/topic/10914-winlink-over-radio-a-practical-setup-checklist-gateways-modes-forms-passwords-p2p/Share on other sites