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: a sensible order for setting up Express, gateways, modes and P2P

ci_cover.jpg

Winlink setups often fail because too many things get changed at once. Someone installs Winlink Express, adds a sound card interface, installs VARA, picks an HF gateway and calls it all broken when the first connect fails. Here is a build order that separates the problems, followed by some questions on the parts people disagree about.

Step 1: Telnet first. Install Winlink Express (the Windows client), enter your callsign and create or enter your Winlink account password. Then run a Telnet Winlink session. This only checks the account, the password, the mailbox and the program itself. It involves no radio, so a failure here is an account or software problem. The password is case sensitive. If you lose it, recovery depends on the recovery email on file, so confirm that is current before you need it.

Step 2: write a message and look at the message flow. Compose a plain text message to yourself or a test address and post it to the Outbox. Nothing is sent until a session connects, whether Telnet, radio or P2P. Keep test messages small. Throughput over RF, especially HF with a weak path, is far lower than Internet speeds, so large attachments and image-heavy signatures are the usual reason a session drags or times out. Replies from ordinary Internet senders can also be affected by Winlink's whitelist and sender rules. Check the current Winlink documentation for how that works so you do not assume a message is lost.

Step 3: pick one RF mode and get it working locally. The common session types in Winlink Express are Packet, VARA FM, VARA HF, ARDOP and Pactor. They need different hardware and have different strengths.

Packet (1200 baud AFSK, or 9600 baud with suitable radios) is a VHF/UHF mode. It needs a TNC, hardware or software, such as a KISS TNC or a software modem like Direwolf, or an older command-mode TNC supported by Express. It is simple and robust, but limited in speed and dependent on a local RMS Packet gateway.

VARA FM is also for VHF/UHF, uses a sound card, and is faster than packet when the path is good. VARA HF is the HF counterpart and is widely used for gateway sessions. VARA is shareware: the unregistered version works but is speed-limited, and registration lifts the limits. ARDOP is an open sound card mode for HF. It is usually slower than VARA HF but is free and popular as a baseline. Pactor needs a dedicated hardware modem, such as the SCS family. It has a long history on HF gateways, but the hardware cost keeps it out of many home stations.

Step 4: sound card and PTT. Most sound card problems come from levels and the Windows audio stack rather than from the mode software. Use a proper radio interface (a USB interface with its own sound device, or a transformer-isolated box). Turn off Windows sound effects and enhancements on those audio devices, and keep system notification sounds out of the radio path. Set transmit audio so the radio's ALC is barely moving, since overdrive creates splatter and bad decodes. Set the receive level so the modem sees a healthy signal without clipping. PTT can be CAT, serial RTS/DTR, a GPIO method or VOX. Use CAT or hardware PTT where you can, because VOX can clip the start of a transmission.

Step 5: gateways and channel lists. The Channel Selection window in Winlink Express lists RMS gateways by mode. It can be updated over the Internet, so update the table before you need it and keep a cached copy for offline use. Sort by distance and propagation estimates, but treat them as guides, not guarantees. Listen on the frequency before transmitting, and confirm whether the listed frequency is a dial or center frequency in your setup. With radio control configured, Express handles the offset for you. If you tune manually, check it yourself.

Step 6: P2P and radio-only. A P2P session connects two stations directly, with no gateway or Internet. One station listens or accepts a P2P connection and the other calls it, using the same mode on both ends (Packet P2P, VARA P2P, ARDOP P2P and so on). This is useful when infrastructure is down or a served-agency site has no gateway coverage. Radio-only messaging is the related idea of keeping traffic off Internet paths. Check how radio-only messages are flagged and routed in the current Winlink documentation. Do not assume an ordinary message to an Internet address will be delivered during a real outage.

Step 7: forms and ICS-213. Winlink Express includes templates for common forms, including the ICS-213 General Message. Forms open in a browser-style viewer, and the data travels as a small attachment, so the recipient normally needs a compatible Winlink client or viewer to see the form as designed. Keep form versions updated and agree with your served agency which forms they accept. Free-text ICS-213 content should be short and clear.

Step 8: practice on a schedule. The Winlink Wednesday weekly practice exercises are a low-pressure way to test your setup. Check the current instructions from the organizers for the format and any message requirements rather than relying on old notes.

Questions for the thread: Do you test VARA FM before packet for local work, or keep packet as the fallback? What is your preferred ARDOP versus VARA HF decision rule when conditions are poor? And how do you document passwords and account recovery for a shared or club station without leaving credentials in an unsafe place?

  • Replies 2
  • Views 24
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The Telnet-first order is the one worth insisting on, because it separates account problems from RF problems. One addition: after Telnet works, run a Telnet P2P or a local P2P test between two machines before touching a gateway. A gateway can fail for reasons you cannot see, such as the station being busy, a poor path, or a mismatch in bandwidth settings. A P2P link to a second station you control tells you quickly whether your sound card levels, PTT and modem setup are good.

On packet, check the TNC side separately. If you use Direwolf or another software TNC with KISS, confirm the KISS port settings and the callsign/SSID before blaming Express. Many packet problems turn out to be a wrong SSID, a digipeater path that does not exist, or audio levels that are too hot for 1200 baud AFSK. Also keep your packet path short. A gateway reached directly is far more reliable than one that needs digipeaters you cannot verify.

For the password question: keep the account password and the recovery email details in a documented place the club trustee can reach, and avoid putting passwords into message bodies. The password and secure-login options for gateways and P2P are separate from the Winlink account itself, so write down which one a given station is using.

  • Moderators

On ARDOP versus VARA HF: a practical decision rule is to pick the mode the gateways near you actually offer, then test it, rather than choosing on theory. VARA HF generally gives higher throughput when the path supports it, but a mode that connects reliably at low speed beats one that keeps failing. ARDOP is worth keeping configured as a fallback because it is free and has no registration speed limit to think about. Pactor only matters if you already have the modem or your area relies on Pactor gateways.

On HF, the most useful habit is to try more than one gateway rather than retrying the same one. Check the channel list for several candidates at different distances, since a closer gateway is not always the best on a given band at a given hour. Listen first, and if the channel is busy or you can hear another session, wait. Winlink Express reports the connect attempts in the session log, so read what it says. A failure to get a link is different from a link that drops during transfer, and the fix is different too: the first suggests frequency, path or power, the second suggests noise, levels or message size.

For forms and ICS-213, the thing that bites people is the recipient end. Before an exercise, send a test form to the person who will receive it and confirm they can read it in their client. If the served agency only uses webmail, plain text may be safer than a form, so agree on that in advance. And keep attachments minimal, especially over HF. A short ICS-213 is a few kilobytes, while a photo can take far longer than the operating window allows.

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.