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: what's a sensible order for setting up Express, gateways, VARA/ARDOP/packet and P2P?

ci_cover.jpg

I'm putting together a Winlink station for a club's emergency communications group. The aim is a station that can pull a gateway session on VHF and HF and also do P2P when the internet is gone. There are many moving parts: Winlink Express, Telnet, RMS Packet, VARA HF and FM, ARDOP, Pactor, Radio-only mode, forms and passwords. What order would you do things in so each piece can be tested on its own, and what usually trips people up?

The rough plan so far is a Windows laptop running Winlink Express, an HF rig with a sound card interface, and a VHF/UHF FM rig. I haven't decided between a hardware TNC and a sound card modem for packet. Pactor is probably out because of the modem cost, unless someone has a good reason to want it. I'd also like the group to practice on Winlink Wednesday and send ICS-213 forms in drills.

I'm after the setup logic and the common mistakes, not a product comparison.

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd start with Telnet, because it isolates the account and software from everything radio-related. Install Winlink Express, enter the callsign, and set the password. Then run a Telnet session to the CMS over the internet. If that works, the account, the password and the message database are fine, so any later failure is down to the radio side. Passwords are case sensitive, and the account password is the one thing to record somewhere safe. Winlink has a password recovery process, but it depends on the contact details on the account, which is a poor thing to discover mid-exercise.

While you're in Telnet, practice message handling. Compose a message, post it to the Outbox, and run a session. Notice that nothing moves until a session connects. Posting to the Outbox only queues the message. The session exchanges whatever is waiting in both directions. Also get the group into the habit of keeping attachments small, since every byte costs airtime on HF. Pictures that are fine over Telnet are a bad idea over a marginal HF path.

Next, do forms. In Winlink Express, templates are under the message composer's template selection, and the ICS USA forms include ICS-213. When you send a form, the visible message text carries the content and the form data travels along as an attachment. A recipient without Winlink Express can usually still read the text, but a recipient with it gets the rendered form view. Test the ICS-213 over Telnet first so people learn the template workflow before they add RF problems.

For the radio side, do VHF first because it's the simplest path. With RMS Packet you need a TNC (hardware, or a software modem like Direwolf feeding Winlink Express through KISS) and an RMS gateway you can reach. Use Channel Selection to list gateways, make sure your grid square or location is set correctly, and sort by distance. Frequency and PTT setup are separate issues from gateway choice, so don't confuse them. A failed connection could be a no-copy, a PTT problem, or bad audio levels.

  • Administrators

One point on HF before you buy anything: Pactor is the only mode in your list that needs dedicated hardware. VARA HF and ARDOP are sound card modes, so a computer, a rig and a decent interface like a SignaLink-style box or a rig's built-in USB audio will do. VARA HF and VARA FM are from the same developer but are separate installs, and Winlink Express has to be pointed at the VARA program in its session settings. The free versions are speed-limited and a registration removes that, which matters on a long HF session. ARDOP is free and open, so it's a good fallback if the group doesn't want to pay for VARA.

Sound card problems are the usual headache. Turn off Windows sounds and any audio enhancements on the interface. Set the transmit level so the ALC barely moves, because overdriving a sound card modem causes splatter and failed connects. Make sure the rig's data mode, filter and speech processor are set the same way every time. For PTT, CAT control is the cleanest option, with RTS/DTR or VOX as alternatives. Write down the settings for each rig once they work, because otherwise they get lost.

On gateway choice: HF gateways are listed with frequencies and modes, and Winlink Express can show propagation estimates alongside the list. Pick two or three candidates at different distances rather than trying one repeatedly. Listen first, and use the busy-channel detection so you don't step on an existing session. Check that the frequency the software tunes your rig to matches what you expect. Dial versus center frequency confusion is a classic source of connects that never happen.

For the emergency scenario, set up P2P as its own exercise. P2P is a direct station-to-station session with no RMS gateway and no internet in the path. One station connects to the other using the same mode, for example VARA FM on a simplex frequency, and the two stations exchange whatever is queued. Radio-only is a different thing: it lets you restrict messages to the radio-only path. Read the current Winlink documentation on its exact behavior before relying on it, since an internet recipient won't see such messages.

For Winlink Wednesday, check the current instructions on the Winlink site each week, because the participation details are set by the organizers and can change. It's still a good routine for the group, since it forces everyone to run a real gateway session regularly. Keep in mind the usual amateur rules: no commercial traffic, no encryption, and the station's control operator is responsible for what goes out.

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.