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

Winlink over radio: choosing a mode, finding RMS gateways, and keeping message handling sane

ci_cover.jpg

This thread is a working checklist for getting Winlink Express talking over RF, and a place to compare notes on the setup decisions that usually cause trouble. It covers sound card versus hardware modems, gateway selection, passwords, forms, and when to use P2P instead of a gateway. Corrections are welcome, since details change between software versions.

How the pieces fit. Winlink Express is the Windows client. When you connect over radio, you reach an RMS gateway, a station with a radio, a modem and RMS software that is normally also connected to the internet. The gateway passes your traffic to the Common Message Servers (CMS), which hold your mailbox. Telnet sessions skip the radio and connect straight to the CMS over the internet. That makes Telnet the quickest way to confirm that your account, password and templates work before you blame an antenna.

Mode choice by band.

Packet (1200 or 9600 baud AX.25) is a VHF/UHF mode. You need a hardware TNC, or a software TNC such as Dire Wolf feeding Winlink Express through KISS or AGWPE-style connections. It is simple and widely used for local gateways, but slow and sensitive to collisions on busy channels.

VARA FM is a sound card modem for VHF/UHF FM. It is much faster than 1200-baud packet when the path is solid. VARA HF is the HF counterpart. Both run as separate modem programs that Winlink Express controls over local TCP ports, and the unregistered versions are speed-limited. Check the current VARA documentation for the exact limits and licensing.

ARDOP is a sound card mode with open specifications. It is usually somewhat slower than VARA HF but is a reasonable choice if you want a free, fully open option.

Pactor needs a dedicated hardware modem, and Pactor 3 or 4 requires a compatible controller. It is common on established HF gateways, so it is worth considering if you already own the hardware.

Sound card setup basics. Most failed sound card sessions come down to levels and rig settings:

  • Use USB or data mode, with no speech processing, no compression and no EQ.
  • Turn off OS sounds and any enhancements on the audio device so nothing else gets transmitted.
  • Set transmit audio so ALC barely moves. Overdriving produces splatter and a slow, retry-heavy session.
  • Make sure PTT works, whether by CAT, serial RTS/DTR or VOX. It should key and unkey cleanly.
  • Keep the computer clock accurate. Some digital modes are timing-sensitive.

Finding gateways. Winlink Express has a channel selection window for each session type. It uses a gateway list downloaded from the internet, so refresh the list while you still have connectivity. The list shows distance, and for HF it can show propagation estimates. Treat those as a guide, not a guarantee. Before connecting, listen to the frequency, because gateways do not all use the same offset convention, and check whether the frequency shown is a dial frequency or a center frequency for your rig setup. Do not use a gateway for casual testing if a Telnet or P2P test would do.

Passwords. Your Winlink account password is needed for CMS and gateway sessions. Keep it stored securely, and set up password recovery while you can still reach the internet. P2P sessions between two stations do not depend on the CMS, but you still need the other station's callsign, mode settings and a clear frequency.

Message handling. Compose to the outbox, connect, and the session sends and receives together. Keep messages short, especially on HF. Large attachments eat session time and increase the chance of dropped links. Radio-only handling matters when you want messages to stay on RF paths rather than being forwarded via the internet. Check the current Winlink documentation for how it is flagged and which recipients it supports. Messages sent to ordinary internet email addresses may be subject to filtering on the receiving side, so test important recipients ahead of time.

Forms and ICS-213. Winlink Express includes templates, including the ICS-213 General Message form. Forms are filled out in a local viewer and sent as small data attachments. Update templates while you have internet, and use the same template version as your served agency or net when possible. Agree beforehand on whether the receiver will see a rendered form or only the plain text.

Practice. Winlink Wednesday is a recurring exercise for sending test traffic. Check the current instructions from the organizers, since address and format details can change. Use it to test your whole chain: account, rig control, gateway selection, forms and a short message.

Questions for the thread: what is your preferred test order when bringing up a new station, and when do you choose P2P over a gateway?

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

A test order that isolates faults: Telnet first, then local radio, then distance. Telnet proves the account, password, templates and message flow without any RF variables. Next, do a P2P or short gateway session on VHF with a strong local signal, which proves PTT, audio levels and the modem. Only then move to HF, where propagation, frequency choice, noise and timing all become possible failure causes.

For the sound card, set levels in the modem software and watch the rig ALC meter rather than guessing. A common mistake is driving the audio hard to get extra power, which gives a distorted signal and more retries. With VARA, remember it has its own settings window for sound devices and PTT, and Winlink Express only talks to it over the configured ports. If Winlink Express says it cannot connect to the modem, check that the VARA program is running and that the command port and data port match on both sides, typically 8300 and 8301 by default, though your setup may differ.

For gateway choice, nearest is not always best. On HF a station a few hundred miles away can beat a closer one, depending on the band and time of day. Try two or three candidates before concluding your station has a problem.

  • Moderators

On P2P versus a gateway: P2P is the better fit when you need to move traffic directly between two known stations, such as a field site and an EOC, and neither needs internet email. A gateway session is better when the destination is a Winlink address, a regular email address, or an account that someone checks from a mailbox. P2P also works when the internet is down, as long as both ends agree on mode, frequency and callsigns, and one side listens.

On forms, treat ICS-213 as a structured message, not a document. Keep the text concise and put the key facts in the body, because a recipient who has not updated their templates, or is reading on a different platform, may not see the rendered form. Agree on a naming convention for subject lines, so that traffic can be sorted quickly in the inbox during an exercise or activation.

For Winlink Wednesday, a useful approach is to run a full dry run beforehand, then use the exercise to confirm the actual procedure with the current instructions. Check which gateway or P2P path you intend to use, and note the result in a log. If a session fails, record which layer failed: CMS login, modem connection, PTT, audio level or RF path. That record makes the next attempt faster.

One more point: passwords and callsigns are case- and format-sensitive in some places, and a typo can look like a radio failure. Confirm a clean Telnet login first, then troubleshoot RF.

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.