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 setup planning: Winlink Express, choosing a session type, gateway selection, and sound card/TNC pitfalls

ci_cover.jpg

I'm putting together a setup guide for a group that wants a working Winlink capability for training and for backup traffic. Before we settle on hardware, I'd like to check the decision points with people who know the system. This is how I understand the pieces, so correct anything that's off.

The client is Winlink Express on Windows. The session types in the menu are Telnet, Packet, VARA HF, VARA FM, ARDOP, Pactor, and the P2P (peer-to-peer) variants. Telnet goes over the internet to the CMS (Common Message Server). It isn't RF, but it's the easiest way to confirm that the callsign, password, and message flow work before any radio gets involved. The RF sessions connect to an RMS (Radio Message Server) gateway station, which relays the traffic to the CMS over its own internet connection. That means a message can move through the system even when we have no internet, as long as some gateway we can reach does.

For VHF/UHF, the options appear to be 1200 or 9600 baud packet through a hardware KISS TNC, or a software modem like Dire Wolf feeding Winlink Express, or VARA FM through a sound card interface. For HF, VARA HF and ARDOP both use the sound card, and Pactor needs a dedicated modem. I'd like to know where people draw the line between 'cheap and good enough' and 'worth the money.'

Questions I'd like answered:

1. For a first HF station, would you start with VARA HF or ARDOP? I know VARA has a free speed-limited mode and a registered full-speed mode, and that ARDOP is free and open.

2. How do you handle audio levels and PTT so the transmit signal stays clean? I've seen advice to keep ALC from acting, but I'd like the practical version.

3. What is the right way to use the gateway list and propagation predictions in the channel selection window?

4. How should we train people to use forms such as ICS-213, and how do Winlink Wednesday exercises fit in?

5. What's the practical difference between a normal gateway session, a radio-only message, and a P2P session when the internet is down?

  • Replies 2
  • Views 40
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Administrators

On the modem question, VARA HF is the usual first pick for HF gateways because many HF stations support it and it generally moves traffic faster than ARDOP in similar conditions. ARDOP is still worth having configured as a second option. It's free, and some gateways list ARDOP channels where VARA isn't offered. Check the channel list for your area before buying a VARA license. If most of the stations you can reach are on VARA, that answers the question. Pactor is a different decision. Pactor 3 and 4 need an SCS-type hardware modem, so it's a deliberate purchase for people who know they need access to those gateways.

For levels, the simple rule is that you're sending audio tones, not voice. Put the rig in its data mode (USB-D or DATA on most radios, or USB with the right input selected), and turn off speech processing, compression, and any equalizer. Set the TX audio so the radio shows little or no ALC movement, and run power at a level the radio can sustain at a high duty cycle. An overdriven sound card input produces splatter and decode failures at the far end, and the gateway operator can't easily tell you why. Watch the ALC meter and your power meter during a test connection, and back the audio off if either looks stressed. On the receive side, set the sound card input so the software's level indicator isn't clipping, and don't leave Windows 'enhancements' or automatic gain control enabled on the audio devices.

PTT is the other common failure. CAT control is fine if the interface and drivers are stable. Serial RTS/DTR keying is simple and reliable when the interface supports it. VOX is usually the last choice because the first part of a transmission can be clipped. Whichever you choose, test it with the radio in a dummy load before going on the air.

For packet on VHF/UHF, a hardware TNC, or a radio with a built-in TNC and a supported KISS or terminal mode, removes the sound card from the problem. A software TNC works well but adds Windows audio settings that need documenting. In both cases, make sure the TNC type selected in Winlink Express matches the device and that the serial or TCP settings agree. A quick sanity check is to confirm the TNC is keying the radio and that the radio's audio levels (especially for 9600 baud, which needs a data/flat audio path) are right, then try a connection to a nearby gateway.

  • Moderators

I'd begin with Telnet and put off RF until the account side is solid. The Winlink account password is case-sensitive, and it's the thing people most often get wrong. Register the callsign, log in over Telnet, send a message to yourself and one to a second Winlink address, and make sure you set a password-recovery email address in case you lose the password. Don't write the password on a shared sheet or in a group document. Each operator should have their own account, and peer-to-peer sessions don't need the password because they don't involve the CMS.

On gateway selection, Winlink Express lets you download a channel list from the internet, so do that while you still have a connection and keep the list current. Enter your location or grid square so it can sort by distance and, for HF, show propagation estimates. Treat those as guides, not guarantees. The listed HF frequency is generally the center frequency, and if rig control is configured, the software works out the dial setting for you. If you tune manually, you have to account for that offset yourself. Listen before you transmit. If the channel is busy, wait or choose another one, because a gateway can only serve one connection at a time on a frequency.

Regarding messages, the format over RF should be small. Compression helps text, but images and large attachments will be slow on HF and may be refused or time out at some gateways. Keep forms and text short. For people sending from ordinary internet email to a Winlink address, spam controls mean they might need to be on your whitelist, or they can put //WL2K at the start of the subject line. Test that path before you rely on it.

ICS-213 and other forms are in the standard templates in Winlink Express. The form opens in a browser, and the message carries the data as a small attachment with a readable version in the body. The receiving person needs a client that can display the form, so confirm that before using forms with outside agencies. Update the templates periodically so everyone is on the same version.

For Winlink Wednesday, check the current instructions from whoever is running the exercise, because the check-in format and addressing can change. It's a good low-stakes way to practice sending a message through a real gateway.

On your last question: a normal gateway session uses an RMS to reach the CMS, so it depends on that gateway having its own internet link. Radio-only messaging is for traffic that should stay on the radio side and not go out to the internet, so read the current Winlink documentation for exactly how it's flagged and routed. A P2P session is a direct connection between two stations, such as VARA FM, packet, or ARDOP, with no gateway involved. One station listens and the other calls, and you need compatible modem settings on both ends. When the internet is down, P2P is the dependable fallback, but it only moves messages between those two stations. It doesn't deliver anything to the wider system until one of you can reach 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.