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: a setup order that works, from Telnet test to RMS gateway and P2P

ci_cover.jpg

This is a discussion starter for anyone setting up Winlink Express for real RF use. Most failed first attempts come from doing the steps out of order, so here is an order that isolates problems. I'd like to hear where people's own workflows differ.

Step 1 is the account and the Telnet session. Install Winlink Express, enter your callsign and password, and do a Telnet Winlink session first. Telnet goes over the internet to the Winlink system, so it proves the account, password, and mailbox work before any radio is involved. Passwords are case-sensitive, so check capitalization before you blame the radio. Keep your recovery email current, because resetting a forgotten password is much easier with it. On RF the password is only used for authentication. Amateur rules still forbid obscuring the meaning of a message, so nothing you send should be treated as private.

Step 2 is choosing a mode, which is mostly a question of band and hardware.

On VHF/UHF you have Packet Winlink (AX.25) and VARA FM. Packet needs either a hardware TNC or a software TNC such as Dire Wolf, reached through KISS or AGWPE. VARA FM runs on a sound card interface, and its wider mode really wants a radio with a flat-audio data port rather than the microphone path.

On HF the main choices are VARA HF, ARDOP, and Pactor. VARA HF and ARDOP both use a sound card. Pactor needs a dedicated hardware modem, and gateway availability for it varies by area. Check the gateway list for what is actually reachable from you before buying anything.

Step 3 is gateway selection. In the Winlink Express session window, open the channel selection list and update it over the internet while you still have a connection. The list shows RMS gateways with frequency, mode, distance, and on HF a propagation estimate. Treat the estimate as guidance, not a promise. The frequency shown for HF is usually the center frequency, so make sure your CAT control or manual dial setting accounts for the USB offset. Listen before you transmit, and if a channel is busy, pick another gateway.

Step 4 is a local test. Before relying on a distant gateway, try a nearby one, or run a P2P session with another station. P2P connects two stations directly with no gateway or internet. Both sides need compatible software, the same mode, and one station listening while the other initiates the connection. Messages in the outbox addressed to the peer are exchanged. P2P is also a good way to isolate whether a failure is your audio chain or the gateway path.

Step 5 is messages and forms. Winlink Express includes templates, including ICS-213. A form opens in a browser, you fill it in, and it is attached to the message so the receiving station's Winlink Express can display it. Keep messages short, especially over HF.

Questions for the thread: which part of this order trips people up most, and how do you handle sound card level setting on shared-use PCs? How do you structure regular practice, such as the Winlink Wednesday habit?

  • Replies 2
  • Views 36
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On sound card setups, the usual culprit is audio level, not the software. Most problems come from too much drive. With VARA HF, ARDOP, or VARA FM, use the software's tuning display to set receive level, then set transmit drive so the radio's ALC barely moves. Overdriven audio makes splatter and lowers decode success for the other station, and the symptom is often repeated retries, not an obvious error.

A few other practical points. Make sure the sound device used for the radio is not also your Windows system sound device, or notifications can go out over the air. Turn off audio enhancements on that device. On HF, set the power below the radio's maximum, because these modes have a high duty cycle and many rigs run hot in continuous transmit. PTT can come from CAT, a serial RTS/DTR line, VOX, or an interface's own PTT. Pick the one that gives the least delay and stays stable.

If you run VARA HF and VARA FM on one PC, check their TCP command and data ports so they don't collide. The defaults are commonly 8300 and 8301, so you may need to change one. In Winlink Express, the VARA settings and the program's configured ports must match.

For gateway choice on HF, try a couple of different gateways and bands instead of retrying one that fails. A clear propagation prediction is nice, but noise at the gateway's end can still ruin the connection.

  • Moderators

On message handling, I'd add two points. First, the Radio-only option. A message flagged that way is meant to stay on radio paths and not be delivered through internet email routes. Check the current Winlink documentation for how to set it and what addressing it requires, because it is easy to assume it behaves like an ordinary message. Also remember that email from outside the Winlink system may need whitelisting to reach your Winlink address, so test inbound mail from a normal email account before an exercise, not during one.

Second, forms. ICS-213 is the most common one because it is the general message form used in many served-agency exercises. Fill it in with the template, and don't paste a long narrative into it. If the form view doesn't open on the receiving side, the usual causes are the template version, the attachment being stripped, or the recipient reading it in a plain email client instead of Winlink Express. Check what the receiving station actually uses.

For regular practice, Winlink Wednesday is a good slot. Check your local group's guidance for the current format and any check-in address. Use a different mode each week, such as a Telnet test one week, a local packet or VARA FM gateway another, then HF, and keep a log of which gateways worked.

For P2P, agree on the mode and frequency by voice first. Then decide who listens and who connects. Mixing up those roles is the most common reason a P2P session never starts, and neither station has to be a 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.