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 session mode, finding a workable gateway, and keeping messages small

ci_cover.jpg

This is a starting point for a technical discussion of how the Winlink pieces fit together, so setup problems can be sorted into the right bucket. Details change between software versions, so treat the Winlink Express documentation and the winlink.org gateway pages as the final word.

The architecture in one pass. Winlink is a store-and-forward messaging system. Your client, usually Winlink Express on Windows, builds messages in an outbox. A session then moves them to a Radio Message Server (RMS), the gateway, or to another station. RMS gateways are connected to the Common Message Servers (CMS) over the internet, and the CMS is what exchanges mail with the wider system. Telnet sessions skip the radio entirely and talk to the CMS over the internet. That makes Telnet useful for testing your account, templates and message flow before you troubleshoot RF. If Telnet works and RF does not, your account is probably fine and the problem is in the radio path, audio levels, modem configuration or gateway choice.

Session types and what they need. Packet Winlink on VHF/UHF is typically 1200 baud AFSK or 9600 baud, through a hardware TNC in KISS mode or a software modem such as Direwolf. It is simple and robust for local gateways, but throughput is low and hidden-node collisions are common on busy frequencies. VARA FM uses a sound card modem for VHF/UHF and is much faster than 1200 baud packet when the path supports it. VARA HF and ARDOP are both sound card HF modes. VARA is by far the faster of the two when conditions allow, but the free version is rate-limited unless registered. ARDOP is open and free and is a reasonable alternative. Pactor is different because it needs a dedicated hardware modem. The higher Pactor levels require specific SCS hardware, and the cost is the main reason many stations choose a sound card mode instead.

Telnet, Radio-only, and P2P are not the same thing. Telnet is internet to the CMS. A gateway session over RF connects you to an RMS, which exchanges traffic with the CMS. Radio-only is a message or session handling option meant for situations where traffic should travel only over radio paths and not be delivered through the internet. Read the current documentation for exactly how your version handles it before relying on it in an exercise. P2P (peer-to-peer) is a direct station-to-station session with no gateway at all. Both stations must agree on the mode, frequency and who is calling whom. P2P is the useful option when the gateways are unreachable or the internet is down, since neither station needs the CMS.

Finding a gateway you can actually work. Winlink Express has a channel selector that pulls gateway lists from the internet, shows distance and bearing, and lets you sort by mode and path. Update the list while you still have internet and keep a saved copy for field use. Listing a gateway does not mean you can reach it. Check recent status, antenna type, and whether the channel is likely to be busy. For HF, use your own band and time-of-day judgment, and consider more than one gateway per band. Also check whether the listed frequency is a dial frequency or a center frequency, and how your software handles the audio offset. In USB with a typical sound card modem, the audio center is around 1500 Hz. A mismatch of that size will make a path look dead when the problem is the tuning.

Sound card and TNC setup checklist. Most trouble is audio level or PTT, not Winlink itself. Use a clean USB audio interface or the radio's built-in codec, and disable Windows sound effects and any enhancements. Set transmit audio so the radio shows little or no ALC action, and turn off speech processing. Overdriving the rig makes splatter and lowers decode rates. Check receive level in the modem's tuning display rather than guessing. For PTT, pick one method and make sure it is configured once: CAT, serial RTS/DTR, a CM108-type GPIO, or VOX as a last resort. Keep the PC clock reasonably accurate, because message timestamps and some troubleshooting depend on it. For a hardware TNC, confirm the serial or USB port, baud rate, KISS mode, and that the radio's data port levels suit the TNC.

Passwords and account basics. Winlink uses your callsign and a Winlink password. The password is for authentication, not for hiding message content. Do not share it, store it carefully, and set a recovery email so you can reset it. In the US, amateur rules do not allow obscuring the meaning of messages, so the password must not be treated as a way to make content private. Also do not assume the system is appropriate for business traffic or other content amateur rules prohibit. As I understand it, internet senders may need to be whitelisted, or use the documented subject prefix, to reach a Winlink address. Check the current rules for that.

Forms and ICS-213. Winlink Express includes templates, including ICS-213 General Message. A form is displayed in a local viewer, and the data travels as a small attachment rather than a formatted page, which is why forms are efficient. The receiving station needs a compatible template version to see it properly, so agree on the template set before an exercise. Keep attachments small on HF, avoid images unless they are essential, and write the plain-text body anyway so someone without the viewer can still read the content. Use consistent tactical addresses or callsigns, and put the exercise identifier in the subject.

Winlink Wednesday. This weekly practice exercise is a low-pressure way to exercise your whole chain: account, radio, modem, gateway choice and message handling. Look up the current instructions on winlink.org, since the format and addressing can change. Treat it as a chance to log which gateways worked, which mode was fastest, and what failed, so the real deployment is not your first full test.

Questions for the thread: what are you using for packet, a hardware TNC or Direwolf? How do you decide between VARA HF and ARDOP when the gateway offers both? And how do you handle frequency listings when the gateway list and your rig disagree?

  • Replies 2
  • Views 39
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On packet, the choice between a hardware TNC and Direwolf mostly comes down to how many moving parts you want. A hardware TNC in KISS mode is one box with a serial or USB link, and it keeps working without audio drivers. Direwolf adds a software layer but lets you use the same sound interface you already have. In both cases Winlink Express needs the TNC type and port set correctly, and the callsign and SSID need to match what you intend to use. A common mistake is a mismatch between the KISS port in the software and the one the TNC is actually presenting. Another is leaving the TNC in a mode where it adds its own connection handling, so the gateway session never starts properly.

For VHF levels, check the radio's data port deviation too. A TNC that is fed too hot makes a wide, distorted signal, and a gateway several miles out may fail to decode it even though the local monitor sounds fine. Run a test with a nearby station or a gateway you know is reliable before concluding the TNC is bad.

  • Administrators

For the VARA HF versus ARDOP question, the practical answer is that you need to match the gateway. A gateway supports only the modes it advertises, so look at the channel list first and choose the best mode for the path rather than your preferred one. VARA can be significantly faster when the path is good, but its free version is speed-limited and a registration removes that limit. ARDOP is free and works on the same kind of sound card setup, and it has bandwidth settings you can choose to match the band conditions. On a weak or noisy path, a narrower bandwidth often gives a better chance of a completed session than a wider one, even though the nominal speed is lower.

On the frequency mismatch, I would confirm what the list means before touching the radio. If the list is a center frequency and your software expects a dial frequency, you can end up 1500 Hz off, which is enough to cause a failed connect. Test the same gateway on the same mode from the channel selector, so the software handles the offset, and compare that to what you set by hand. If the results differ, you have found the offset problem. Also keep a note of which gateways answered, the time of day, and the mode, because that record is more reliable than any listing next time.

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.