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: how the pieces fit together (RMS gateways, session types, sound card/TNC setup, forms and P2P)

ci_cover.jpg

Winlink setups tend to go wrong because people mix up the layers. This post lays out the layers, so replies can fill in gaps or correct me where practice differs from the documentation.

The path a message takes. Your client, usually Winlink Express on Windows, builds a message. It then reaches the system either through a radio gateway (an RMS, Radio Message Server) or over the Internet via Telnet. Gateways pass traffic to the Common Message Servers, which handle the mailbox side and Internet email delivery. A Telnet session is the easiest way to confirm that your callsign, password and mailbox work before you involve a radio. If Telnet fails, no antenna change will fix it.

Session types in Winlink Express. Each one is a different transport to the same mailbox.

Packet is 1200 baud AFSK on VHF/UHF, usually through a hardware TNC or a software TNC over KISS or AGWPE. VARA FM is the faster VHF/UHF option and runs on a sound card. VARA HF is the HF equivalent. ARDOP is an open protocol that also uses a sound card and is a common choice on HF. Pactor needs a supported hardware modem, and the higher Pactor levels are proprietary. Telnet is Internet only. Winlink Express also supports other modes, but these are the ones most people meet first.

P2P and Radio-only. A P2P (peer-to-peer) session connects two stations directly with no gateway and no Internet. Both sides need compatible software and the same mode, such as Packet P2P, VARA P2P or ARDOP P2P. It is useful when the infrastructure is gone, and it is a good way to test your radio chain without relying on a gateway being on the air. Radio-only is a different idea. It keeps traffic on the radio network and off the Internet side of the system. Check the current Winlink documentation for how it behaves in your client version before depending on it in an exercise.

Choosing a gateway. The channel selection window in Winlink Express pulls a list of RMS stations by mode and band, and it can show distance and propagation estimates. The list is downloaded over the Internet, so update it while you still have a connection and keep a cached copy. Pick gateways that match your path. For VHF/UHF that means line of sight or a decent repeater-less path. For HF, pick by time of day and band conditions rather than by what is nearest. Listen before you connect. If the channel is busy, wait, because gateway channels are shared and a failed connect on top of someone else's session helps nobody.

Sound card and TNC basics. With VARA or ARDOP, the radio is a USB or data-mode audio path, so the sound card settings matter more than they seem to.

Turn off speech processing, compression and any radio DSP effects on the data path. Set transmit audio so the rig is not showing ALC action. Overdrive creates splatter and lowers decode success. Make sure Windows system sounds aren't going out through the same interface. Pick the correct PTT method: CAT, serial RTS/DTR, or VOX if nothing else works. For packet with a software TNC like Dire Wolf or a hardware TNC, confirm the KISS port and baud rate match what Winlink Express expects.

Passwords. You need your Winlink account password for Telnet and generally for gateway sessions. It is case sensitive, so a mismatch in capitalisation is a classic cause of rejected logins. If a P2P session works but gateway sessions fail, start with the password and callsign entry rather than the audio.

Forms, ICS-213 and Winlink Wednesday. Winlink Express includes a library of templates, including ICS-213, the general message form. A form fills out in a browser-style window and sends as a compact message with the data attached. Update the templates periodically so the form versions match what the receiving station has. Many groups hold a weekly practice often called Winlink Wednesday, where operators send a check-in or a test form and confirm delivery. Local organisers set their own details, so look up your area's net or ARES/emcomm group rather than assuming a schedule.

What are the first things people check when a session connects but never completes? And does anyone have a preferred order for testing: Telnet, then P2P, then a gateway?

  • Replies 2
  • Views 22
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

My checklist for 'connects, then stalls' goes in this order, starting with the cheapest checks.

First, confirm the radio is in the right mode and bandwidth. For VARA FM that means the right wide or narrow setting on the rig and in the software, and for HF it means USB with the filters wide enough for the bandwidth you chose. Second, check the audio levels. VARA gives you level feedback in its own window, and the point is to avoid both clipping and a starved signal. A weak transmit level and an overdriven one both show up as repeated retries, so they look alike from the outside. Third, check PTT timing. A rig that takes a moment to switch can clip the start of every frame.

On HF there's one more thing. Make sure the frequency you enter lines up with how the gateway list expresses it. Dial frequency and centre frequency differ by the audio offset, and entering the wrong one puts you slightly off the gateway's passband. Winlink Express usually handles this once rig control is configured, but it's worth verifying against the gateway's published information when something is off.

As for the test order, Telnet then P2P then gateway is a good one. Telnet proves the account, P2P proves your own audio and PTT chain with a friendly station on the other end, and the gateway test only has to prove the path. Unregistered VARA also runs at a reduced speed, which can look like a poor link when it's really just the licence limit, so factor that in before blaming propagation.

  • Moderators

On the message side, a few habits keep a radio session healthy.

Keep messages small, especially on HF. Skip embedded images and large attachments, and send a plain text body, with a form when the receiving agency expects one. A short ICS-213 transfers quickly and still carries the structure that served agencies want. Remember that a recipient who only has ordinary email sees the text rendering of the form. The full form view needs Winlink Express or compatible form viewing on their side, so tell them what to expect when you send to a non-Winlink recipient.

Inbound Internet email is another point worth knowing. Winlink applies spam controls to mail coming in from the Internet, so a message from an unfamiliar sender may not arrive the way you expect. Check the current Winlink guidance on whitelisting and on the subject-line conventions for mail sent to a Winlink address, because that is policy that can change and I wouldn't rely on memory.

For practice, a Winlink Wednesday style exercise is more useful if you test more than one path. Send one message through a gateway, one by P2P to a nearby operator, and one Telnet message as a baseline for your account. Afterwards, compare the session logs. The log shows whether a failure was at connect, at login or in transfer, and that tells you whether to look at the radio chain, the password or the gateway choice.

Finally, save your gateway channel list and your templates before an event. Both are fetched over the Internet, and the situation where you most need them is the one where the Internet may not be available.

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.