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

Building a Winlink station for ARES use: Winlink Express, RMS gateways, VARA/ARDOP/Pactor/Packet, P2P and radio-only

ci_cover.jpg

Our group is putting together a Winlink capability for emergency communications and training. We'd like to agree on one baseline setup before everyone starts building something different. The plan is to use Winlink Express on Windows laptops and cover Telnet, VHF/UHF packet or VARA FM, and HF with VARA HF or ARDOP. A couple of people already own Pactor-capable modems. Here is how I understand the pieces; correct anything that's wrong.

Winlink Express is the client. It holds your mailbox, composes messages, and runs different session types: Telnet Winlink (internet to the CMS), Packet Winlink (a TNC to an RMS packet gateway), VARA FM and VARA HF (sound card modems, to an RMS gateway), ARDOP (also sound card), and Pactor (needs a hardware modem). Each mode also has a P2P variant for working station-to-station with no gateway. I understand a gateway (RMS) is a station that accepts your radio connection and exchanges your traffic with the Winlink system, usually over the internet. Telnet is the easy way to check that the account, callsign, and password work before any radio is involved.

Here are the questions we want to settle:

1. What is the best order for building and testing? I'd like to do Telnet, then local packet or VARA FM to a nearby gateway, then HF.

2. For VARA FM and packet, is it better to use a sound card interface and software modem, or a hardware TNC or radio with a built-in TNC? What are the common PTT and audio level mistakes?

3. How do we choose gateways? We know Winlink Express can show a channel list with distance and propagation estimates. What do we need to do before an event, when the internet may be down?

4. How should we think about radio-only sessions and P2P? I know P2P is useful with no gateway, but I'm not clear on what it means for messages addressed to ordinary email addresses.

5. We'd like to use ICS-213 and other forms, and to join Winlink Wednesday for practice. What should we know about templates, message size, and etiquette?

  • Replies 2
  • Views 92
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Your build order is a good one, and each step isolates one set of problems. With Telnet you only have to get the callsign, password, and account working, and you can also look at the Winlink Express settings. Passwords are case-sensitive, so check for a stray capital or a mistyped character, and set up a recovery email so a forgotten password isn't a crisis in the middle of an exercise. If a Telnet session fails, don't touch the radio settings yet.

For VHF/UHF, the choice between packet and VARA FM is mostly about what the local gateways support. A gateway listening on a 1200 or 9600 baud packet channel won't answer a VARA FM call, so use the channel list rather than guessing. Hardware TNCs and radios with built-in TNCs usually connect through a KISS or TNC-2-style interface in Winlink Express. Software TNCs such as Dire Wolf can present a KISS interface over TCP or serial, if you want to avoid a separate box. VARA FM goes through the sound card, so it needs a clean audio path. Most trouble comes from the same few things: the wrong Windows audio device selected in the VARA settings, a PTT method that doesn't match the interface (serial RTS/DTR, CAT, VOX, or a CM108-style GPIO), and drive levels set too high. Overdriving an FM transmitter makes the signal worse, not stronger. Use the tuning or level indicators in the modem software, and turn off Windows audio enhancements and system sounds, because they can end up on the air.

One licensing point: VARA is a separate download from Winlink Express. The unregistered version works but is speed-limited, and registration lifts that limit, so decide as a group whether that matters for you. ARDOP is free, which makes it an easy option to include as a backup HF mode. Pactor needs a hardware modem, and the faster Pactor levels need more capable ones. They are useful, but don't make them a requirement for your members.

Gateway selection is where a lot of emergency plans fall apart. The channel list has to be downloaded while you still have internet. Update it, and check that the stations you rely on are listed with the modes you plan to use. Then have each operator record the nearby gateways and frequencies on paper or in an offline note, together with their usual modes. For HF, pick several gateways at different distances, because skip geometry changes with the band and time of day. Rank them by how reliable they were in your own tests rather than by the predicted signal-to-noise number alone. A gateway that is 80 km away and can be copied on a clear VHF path is often a better first choice than an HF station a long way off.

  • Moderators

On P2P and radio-only, I'd keep them clearly separate in your training, because people mix them up.

P2P is a direct connection between two stations, using a P2P session type for the mode you're running (packet, VARA, ARDOP, or Pactor). No RMS gateway or internet is involved. One station calls, the other listens in the matching P2P mode, and they exchange the messages queued in their outboxes. It works well for a shelter, a command post, or any place where a gateway is out of reach. Practice it on a simulated loss of gateways, and agree in advance on frequency, mode, bandwidth, and who calls whom. Remember that P2P delivers to the other station's Winlink Express. It does not reach arbitrary internet addresses unless that station later has a gateway or internet path, so don't promise anyone off-site delivery.

Radio-only is a different idea. It is a way of keeping messages off the internet path, so they move only among Winlink radio users. That can matter when the internet is down or when you simply want to avoid internet exposure. Check the current Winlink documentation for how your version of Winlink Express flags and handles radio-only messages, because the menu location and behavior can change between releases. Run a test message through the exact path you intend to use, and confirm that the recipient actually receives it.

For forms, use the Template Manager in Winlink Express to update the templates while you still have internet, then make sure everyone is on the same set. ICS-213 and similar forms open in a local web page, and the data travels with the message so the receiving Winlink Express can display it as the form. A recipient without the templates may only see raw text or an attachment. Keep forms short and attachments to a minimum, because an HF session is slow and the message size directly sets the session length. Remember too that Winlink traffic on amateur frequencies falls under the usual amateur rules: no encrypted content, and identify properly. The account password authenticates you to the system and doesn't hide the message content.

For Winlink Wednesday, treat it as a regular practice event and follow the current instructions published by the Winlink community, since the details of what to send and where to send it are what you most need to get right. Use it to test your setup. Send a short check-in with a form, try each gateway on your list, and keep a simple log of the date, time, band, mode, gateway, and result. After a few weeks that log will show you which paths work and which settings cause trouble. That is more useful than any general advice about which mode is best.

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.