Winlink over radio: a working checklist from first Telnet test to RMS gateway sessions, P2P and ICS-213 forms
- Replies 2
- Views 31
- 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 is easy to describe and fiddly to set up. A Winlink Express install can look finished while the radio side still isn't working. This thread is a checklist in the order that tends to isolate problems, with the main session types (Telnet, Packet, VARA HF/FM, ARDOP, Pactor, Radio-only, P2P) covered along the way. Corrections are welcome. Program versions, licensing terms and gateway lists change, so check anything version-specific against the current Winlink documentation.
Step 1: Prove the account and the software over Telnet. Install Winlink Express, enter your callsign and create or enter your password, and add a recovery email address. Then use a Telnet Winlink session. Telnet connects over the internet to the Winlink system (the CMS), with no radio involved. If you can send and receive a short test message that way, then your account, password and basic message handling work. Any later failure is then in the radio, audio or modem chain, not the account. Passwords are case-sensitive in practice, so a mismatch in capitalisation is a common cause of login failures. Remember the password also protects your account's mailbox, so don't share it around a club or leave it on a printed sheet in the go-kit.
Step 2: Understand what a gateway is. An RMS (Radio Message Server) gateway is an amateur station that connects radio sessions to the CMS. When you connect to one by packet, VARA, ARDOP or Pactor, your outbound messages go up to the system and your waiting inbound messages come down. This is store-and-forward email, not a live chat link. Most clients can't judge whether a gateway will be workable from your location, so use the channel selection window, update the channel list while you still have internet, and use propagation prediction for HF. On HF, check whether a listed frequency is a dial or a center frequency before tuning by hand. Winlink Express handles the offset when rig control is configured, but manual setups are where people end up 1.5 kHz off.
Step 3: Pick the mode for the band and the job.
VHF/UHF packet needs a TNC, either a hardware unit or a software one such as Direwolf or a soundmodem exposed over KISS or AGWPE. It is simple, works well for local gateways, and is limited by 1200 baud (or 9600 baud with a radio that has a proper data port). VARA FM is a sound card modem and is generally much faster than 1200 baud packet on a good FM path. It runs as a separate program, and Winlink Express talks to it over local TCP ports, so the host and port settings in the Winlink Express VARA setup must match the modem program.
VARA HF does the same job on HF. It is generally the high-throughput choice for sound card modes, but the free version is speed-limited and a licence unlocks full speed. ARDOP is a free sound card alternative, often chosen for weak-signal robustness or when VARA isn't an option. It also runs as a separate modem program and connects to Winlink Express over TCP. Pactor needs a supported hardware modem (SCS units, for example). Pactor 1 is widely available, while higher Pactor levels need specific hardware, and Winlink Express talks to the modem over a serial or USB port.
Step 4: Audio and PTT, where most problems hide. For any sound card mode, turn off Windows audio enhancements and system sounds on the interface used for the radio. Set the transmit drive so the rig shows little or no ALC action. Overdriving distorts the modem signal and costs throughput, especially with VARA. Make sure PTT works reliably via CAT, serial RTS/DTR, a CM108-style GPIO or a VOX interface, and confirm the radio actually returns to receive. Set the receive level so the modem's tuning or level display shows a healthy signal rather than clipping. Only then try a real connection.
Step 5: Message handling basics. A message goes into the outbox when posted, and is sent only when a session runs. Keep HF messages small. Plain text is fine, big attachments and embedded images are not. Messages to internet addresses use the SMTP: prefix in the To line when needed, and replies from outside addresses may be subject to Winlink's spam filtering, so test two-way flow before relying on it. Tactical addresses can be used by groups so that a served agency isn't tied to one operator's callsign. Remember Part 97-style rules for your country: no encryption, no commercial use, and watch third-party traffic rules.
What have I missed, and which parts do you think are worth rehearsing before an emergency?
Link to comment
https://www.hamradiobase.com/forums/topic/11241-winlink-over-radio-a-working-checklist-from-first-telnet-test-to-rms-gateway-sessions-p2p-and-ics-213-forms/Share on other sites