Winlink over radio: how the pieces fit together (RMS gateways, session types, sound card/TNC setup, forms and P2P)
- Replies 2
- Views 22
- Created
- Last Reply
A better way to browse. Learn more.
A full-screen app on your home screen with push notifications, badges and more.
Winlink setups tend to go wrong because people mix up the layers. This post lays out the layers, so replies can fill in gaps or correct me where practice differs from the documentation.
The path a message takes. Your client, usually Winlink Express on Windows, builds a message. It then reaches the system either through a radio gateway (an RMS, Radio Message Server) or over the Internet via Telnet. Gateways pass traffic to the Common Message Servers, which handle the mailbox side and Internet email delivery. A Telnet session is the easiest way to confirm that your callsign, password and mailbox work before you involve a radio. If Telnet fails, no antenna change will fix it.
Session types in Winlink Express. Each one is a different transport to the same mailbox.
Packet is 1200 baud AFSK on VHF/UHF, usually through a hardware TNC or a software TNC over KISS or AGWPE. VARA FM is the faster VHF/UHF option and runs on a sound card. VARA HF is the HF equivalent. ARDOP is an open protocol that also uses a sound card and is a common choice on HF. Pactor needs a supported hardware modem, and the higher Pactor levels are proprietary. Telnet is Internet only. Winlink Express also supports other modes, but these are the ones most people meet first.
P2P and Radio-only. A P2P (peer-to-peer) session connects two stations directly with no gateway and no Internet. Both sides need compatible software and the same mode, such as Packet P2P, VARA P2P or ARDOP P2P. It is useful when the infrastructure is gone, and it is a good way to test your radio chain without relying on a gateway being on the air. Radio-only is a different idea. It keeps traffic on the radio network and off the Internet side of the system. Check the current Winlink documentation for how it behaves in your client version before depending on it in an exercise.
Choosing a gateway. The channel selection window in Winlink Express pulls a list of RMS stations by mode and band, and it can show distance and propagation estimates. The list is downloaded over the Internet, so update it while you still have a connection and keep a cached copy. Pick gateways that match your path. For VHF/UHF that means line of sight or a decent repeater-less path. For HF, pick by time of day and band conditions rather than by what is nearest. Listen before you connect. If the channel is busy, wait, because gateway channels are shared and a failed connect on top of someone else's session helps nobody.
Sound card and TNC basics. With VARA or ARDOP, the radio is a USB or data-mode audio path, so the sound card settings matter more than they seem to.
Turn off speech processing, compression and any radio DSP effects on the data path. Set transmit audio so the rig is not showing ALC action. Overdrive creates splatter and lowers decode success. Make sure Windows system sounds aren't going out through the same interface. Pick the correct PTT method: CAT, serial RTS/DTR, or VOX if nothing else works. For packet with a software TNC like Dire Wolf or a hardware TNC, confirm the KISS port and baud rate match what Winlink Express expects.
Passwords. You need your Winlink account password for Telnet and generally for gateway sessions. It is case sensitive, so a mismatch in capitalisation is a classic cause of rejected logins. If a P2P session works but gateway sessions fail, start with the password and callsign entry rather than the audio.
Forms, ICS-213 and Winlink Wednesday. Winlink Express includes a library of templates, including ICS-213, the general message form. A form fills out in a browser-style window and sends as a compact message with the data attached. Update the templates periodically so the form versions match what the receiving station has. Many groups hold a weekly practice often called Winlink Wednesday, where operators send a check-in or a test form and confirm delivery. Local organisers set their own details, so look up your area's net or ARES/emcomm group rather than assuming a schedule.
What are the first things people check when a session connects but never completes? And does anyone have a preferred order for testing: Telnet, then P2P, then a gateway?
Link to comment
https://www.hamradiobase.com/forums/topic/11529-winlink-over-radio-how-the-pieces-fit-together-rms-gateways-session-types-sound-cardtnc-setup-forms-and-p2p/Share on other sites