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 412.9 km/s
Aurora 1
Updated 14:00 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, setting up Winlink Express, and handling messages sensibly

ci_cover.jpg

This thread is a working checklist for getting Winlink Express talking over radio, plus some questions on where setups usually go wrong. Corrections and additions are welcome.

How the system fits together. Your message goes from Winlink Express over a radio link to an RMS gateway. The gateway is a station connected to the internet that relays traffic to the CMS (Common Message Servers). Telnet is the same session type over the internet, with no radio involved. Because of that, Telnet is the best first test: it confirms your callsign, password, and address work before you add rig control, audio levels, and propagation as variables.

Choosing a session type in Winlink Express.

Packet (RMS Packet) is usually 1200 or 9600 baud on VHF/UHF. It suits local gateways, and it can use a hardware KISS TNC or a sound card modem, depending on how your station is built. VARA FM is a sound card modem for VHF/UHF FM. It is generally faster than 1200 baud packet when the path is clean, but it needs a good audio path and, for its wider mode, a radio and interface that pass data audio properly.

On HF, the main choices are VARA HF, ARDOP, and Pactor. VARA HF and ARDOP are sound card modes. Pactor needs a dedicated hardware modem, typically from SCS, and the higher Pactor levels are proprietary. VARA is shareware, and the unregistered versions are speed-limited. ARDOP is open source and has several bandwidth settings, which makes it a reasonable starting point if you do not want to buy a license.

Peer-to-peer (P2P) connects two stations directly with no gateway and no CMS, using the same modems. It is useful when the internet is down and both ends have prearranged frequencies and modes. Radio-only messages are a related idea: the message is flagged so it moves only over radio paths and not through internet-connected servers. Check the Winlink documentation for exactly how your version treats them, because the behavior is easy to misunderstand.

Gateway selection. Use the RMS channel selection window rather than guessing frequencies. It lists gateways by mode, distance, and (on HF) predicted propagation, and you refresh the list over the internet while you still have it. Keep a cached copy for when you do not. One detail catches people out: listed HF frequencies are the center frequency of the signal. If you are tuning a rig by hand in USB, the dial frequency is typically about 1.5 kHz lower. Letting rig control set the frequency avoids the arithmetic. Listen before you connect, and do not keep calling a gateway that is not answering.

Passwords. The Winlink account password is separate from any email password. It is case-sensitive, and recovery depends on having a valid recovery address on the account. Set that up while you still have internet.

Questions for the thread: for a first HF setup, would you start with ARDOP or VARA? And what is the most common cause of failed connections, audio levels, PTT, or gateway choice?

  • Replies 2
  • Views 43
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the sound card side, most failed sessions come down to audio and PTT rather than Winlink itself.

Set the rig to a data mode (USB-D or the equivalent) and turn off speech processing, compression, and any noise reduction that touches the receive audio. Pick a PTT method that works reliably: CAT, a serial RTS/DTR line, or a CM108-style GPIO in an interface that supports it. VOX tends to clip the start of a transmission and is a poor fit for protocols that expect clean timing.

In Windows, disable audio enhancements on the radio's sound device, and keep system sounds off that device so a notification never goes out on the air. Set the transmit drive for a clean signal rather than maximum power. With most sound card modes you want little or no ALC action. Power turned down and a clean signal beats a loud, distorted one, and over-driving also splatters onto neighboring channels. VARA and ARDOP both give you tuning or level displays, so use them instead of guessing.

For 1200 baud packet, a KISS TNC or a sound card TNC both work, but check how your software expects to reach it. Winlink Express talks to supported TNC types over a serial or Bluetooth serial port, and a software TNC may need a bridge to present itself that way. For VARA FM, the narrow mode works through ordinary mic and speaker audio. The wide mode needs a radio and cable with a flat data path, so a plain mic/speaker connection may not be enough.

As for the first-mode question: ARDOP is the easier place to start if you want to avoid license costs, and VARA is worth trying afterward to compare. Whichever you pick, test on Telnet first, then on a local VHF gateway if one exists, before attempting HF.

  • Moderators

Message handling deserves as much attention as the radio setup, because the link is the slow part.

Keep messages small. Text is cheap, and large attachments can tie up a gateway and your own session for a long time. Winlink compresses traffic, but JPEGs and zip files are already compressed, so they gain little. If an image is truly needed, shrink it first, and consider whether a form or a few lines of text would do the job.

For incoming mail from regular internet senders, Winlink has spam controls. Unknown external senders may be rejected, and the usual workaround is to have the sender start the subject line with //WL2K, or to add the sender to your whitelist. Sort that out before you need it.

The ICS-213 form, and the other templates in Winlink Express, are filled in locally and sent as structured data attached to the message. The recipient then sees the formatted result, which is more reliable for served-agency traffic than free text. The recipient needs a client that can render the form, so confirm that with the other end ahead of time. Also remember that the form is only a container. A message that is clear, short, and signed with the right names, times, and locations is still what makes it useful.

For practice, the weekly Winlink Wednesday routine is a low-pressure way to exercise the whole chain: account, modem, rig control, gateway choice, and form handling. Check the current Winlink Wednesday announcement for the specific instructions, because the details can change and I would rather not guess at them here.

Finally, content rules still apply. Amateur-band Winlink traffic must not be encrypted or obscured, and it should stay within the rules for your license and band. The control operator is responsible for each transmission, so look at the session log when something goes wrong before blaming the gateway.

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.