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 modes, setting up Winlink Express, and handling ICS-213 traffic

ci_cover.jpg

We're putting together a Winlink capability for a small emergency communications group and want to make sure we're not building on bad assumptions. Right now we have a few HF rigs, a couple of VHF/UHF mobiles, laptops running Windows, and a mix of sound card interfaces. One member has an older hardware TNC. Nobody has done more than a Telnet test message.

These are the points we want to sort out:

1. Which session types make sense for which job: Telnet, Packet, VARA FM, VARA HF, ARDOP, Pactor, and P2P. Where does "radio-only" fit?
2. How to find usable gateways (RMS stations) and what the channel list is actually telling us.
3. Sound card versus hardware TNC setup, including audio levels and PTT.
4. How to handle forms like ICS-213, and how to keep messages organized.
5. Password and account setup so we don't get locked out when it matters.
6. Whether Winlink Wednesday is worth using as a regular exercise.

Corrections to the above are welcome if I've got any of the terminology wrong. I'd like the group to have a short written setup guide when we're done.

  • Replies 2
  • Views 23
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Start with how the pieces fit. Winlink Express is the Windows client. When you connect to an RMS gateway over RF, the gateway passes your traffic to the Winlink Common Message Servers (CMS) over the internet. A Telnet session in Winlink Express goes directly to the CMS over the internet with no radio involved. That's why Telnet is useful for first-time account checks, testing forms, and sending messages while you're still at home, but it doesn't prove your radio chain works.

For the radio modes, think about what each one needs:

Packet (1200 baud AFSK on VHF/UHF) can use a hardware TNC or a sound card with software such as Direwolf or Soundmodem. In Winlink Express you'll typically define the TNC type and port, or the KISS connection if you use software. VHF packet is simple and works well for local gateways, but it's slow and shares the channel with other users.

VARA FM also uses the sound card, with the VARA modem running alongside Winlink Express. It's meant for VHF/UHF FM and is much faster than 1200 baud packet when the signal is solid. VARA is shareware: the unregistered version works but has a speed limit, and a license removes it. For a group, decide ahead of time who will register what.

VARA HF is the same family for HF SSB. It's usually what you'll find on busy HF gateways because it's fast for the bandwidth it uses. Same licensing situation as VARA FM.

ARDOP is a free alternative for HF with a sound card. It's often a good fallback if VARA licensing is an obstacle, and it's also available for P2P, but the available gateway list is generally smaller than VARA's, so check the channel list for your area.

Pactor is the odd one out because it needs a dedicated hardware modem. Pactor 1 can be handled by some multimode controllers, but the higher Pactor levels need specific modems. Unless a member already owns one, most new groups skip it.

On the sound card side, the usual HF setup is rig in USB (or the data mode your radio provides, often USB-D or DATA-USB), all audio processing off (compression, equalizer, noise reduction), and the transmit audio set so the ALC barely moves. If you're seeing steady ALC action, you're overdriving and spreading splatter. Gateway operators will notice. For PTT, use CAT control if your rig supports it reliably, or serial RTS/DTR or a dedicated interface's PTT line. VOX works in a pinch but can cause clipped starts.

On gateway locations: the Winlink Express channel selection window pulls from a list that has to be refreshed over the internet. Update it before you go anywhere, because the cached copy is only as good as your last update. For HF, the window can also give you a propagation estimate, but treat that as a hint and not a promise. For VHF/UHF, the list gives you stations near your grid or location, but check the station's actual coverage with a test connection. Don't assume a listed gateway is up on any given day.

  • Administrators

A few things I'd add around forms, P2P, passwords, and practice.

Forms: in Winlink Express, templates are under the Forms menu in the message composer. ICS-213 General Message is in the ICS USA set. You fill it out in a browser-based form and Winlink Express attaches the data to the message. When it's sent over radio, the recipient needs Winlink Express (or a compatible client) to render it correctly. If they're reading it in a plain email client, they'll often just see the text body and a small attachment. For a served agency using plain email, the message body usually contains a readable text version of the form, but test that with your actual recipient before you rely on it. Keep templates updated while you have internet, since forms get revised.

Message handling: keep your Outbox and Sent Items tidy during an exercise, use clear subject lines (form name, from, priority), and keep attachments small. Large files over HF are slow and tie up the gateway for everyone. If you're sending over a weak path, a long message with a photo attached is the wrong choice.

P2P sessions: peer-to-peer means two stations connect directly, with no gateway or internet in the middle. In Winlink Express you pick the P2P version of the mode you want (Packet P2P, VARA P2P, ARDOP P2P, and so on). One station initiates and the other must be set to listen. Agree on frequency, mode, and bandwidth before you start. P2P is what you rely on when no gateway is reachable, when you're staying inside a local net, or when you want to move traffic between your own sites. It's also a good way to practice, since you can test the full radio chain without depending on someone else's gateway.

Radio-only: this is a Winlink setting meant for situations where you don't want traffic to go through the internet. Messages flagged this way are only handled over radio paths. Details on how it behaves depend on the current Winlink documentation, so read the official guidance for the version you're running before you use it in an exercise. I wouldn't assume it behaves like normal Winlink routing.

Passwords: your Winlink account password is separate from your radio or PC login. You set it up on first use, and it's used for sessions with the CMS. If you forget it, recovery depends on the recovery email you set up in your account. Make sure each operator has that information set before an incident, and make sure the callsign in Winlink Express matches the one you registered. Passwords are case-sensitive in practice, and typos at the keyboard are a common cause of failed logins, so a quick Telnet login test before the exercise saves time. If your group also uses tactical addresses, those are set up separately and still tie back to the account.

Winlink Wednesday: it's an informal weekly practice many operators use to send test messages and make sure their setup still works. Look at the current details on the Winlink site or community pages instead of relying on a secondhand description, since the exact address, format, and schedule can change. The useful part for your group is the habit: pick a day, have everyone open a session, send a test, and record what worked. Log which gateway, mode, frequency, and outcome. After a few weeks you'll have a real picture of what works from each member's location, and that's better than any one-time test.

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.