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 Express over radio: picking the mode, setting up the TNC or sound card, and avoiding the usual failures

ci_cover.jpg

This thread is meant as a working checklist for getting Winlink Express from installed to actually passing traffic over RF. Details change between software versions, so check anything critical against the current Winlink documentation. The structure below should hold up anyway.

1. Account and passwords. Winlink Express asks for your callsign and a Winlink password on first run. The password belongs to your Winlink account on the central message servers. It is separate from any VARA registration key and from any passphrase you use elsewhere. A Telnet Winlink session over the internet is the easiest way to confirm the callsign and password are accepted before you try RF. If a radio session to a gateway fails at login, suspect the password first. Case, stray spaces, and an old password saved in another profile are common causes. Keep the password somewhere you can get to without the internet.

2. Pick the session type for the path you have. Telnet uses the internet and is good for testing and for checking forms. Packet Winlink uses AX.25 through a TNC, usually on VHF/UHF, to an RMS Packet gateway. VARA FM is a sound-card modem for VHF/UHF and generally runs much faster than 1200 baud packet where the path supports it. VARA HF and ARDOP are both sound-card modes for HF. VARA HF is faster on good paths but needs a registration to unlock full speed. ARDOP is free. Pactor needs a supported hardware modem, such as an SCS unit, and is still common among gateway operators. P2P is station-to-station with no gateway involved, and it works over packet, VARA, ARDOP, and Pactor.

3. Gateway selection. Update the channel list while you still have internet, because the list is cached locally. In the RMS channel selection window you can sort gateways by distance and, for HF, check propagation estimates. Treat the estimates as a guide and not a guarantee. When you set the radio, confirm whether the listed HF frequency is a center frequency or a dial frequency, and how your rig control handles it. With manual tuning in USB for a sound-card mode, the dial is typically set about 1500 Hz below the center frequency. Pick several candidate gateways on different frequencies and bands instead of relying on one.

4. Sound card basics. Use a dedicated audio path for the radio interface. In Windows, disable audio enhancements and keep system sounds off that device. On the radio, turn off speech processing and compression, leave noise reduction and DSP off or minimal, and keep the receive filter wide enough for the mode. Set transmit drive so there is no visible ALC action. Overdriven audio gives splatter and failed connections even when signal reports look fine. PTT can come from CAT, a serial RTS/DTR line, a CM108-type interface, or VOX as a last resort. Always listen first. The busy-channel detection in the modems helps but does not replace listening.

5. TNC setup for packet. With a hardware TNC, match the serial settings, KISS or terminal mode, and baud rate to what Winlink Express expects. With a software TNC such as Dire Wolf, you point Express at the TNC through an AGWPE-compatible or KISS interface and set the radio audio levels in the TNC. Keep the packet speed (1200 or 9600) consistent with the radio's data port and the gateway.

6. Forms and ICS-213. Winlink Express includes form templates, including ICS-213. A form opens in a browser, you fill it in, and when you submit it Express builds the message with the data attached, plus a readable text body. Update templates before a deployment, not during it. Keep messages short and avoid images, HTML bodies, and large attachments, since a few extra kilobytes can mean a very long session on a weak HF path. Check that the recipient can read the form, or at least the text body.

7. Radio-only and P2P. A radio-only message is one you want kept off the internet delivery path. Check the exact wording and behavior of that option in your version of Winlink Express before relying on it in an exercise. P2P needs no gateway. One station starts the session, the other is set to listen on the same mode and frequency, and messages move directly. Agree on the frequency, mode, and callsign or SSID in advance.

8. Practice. Winlink Wednesday is commonly used as a weekly practice exercise. Check the current instructions on the official Winlink site, because the exact format and addresses can change. Use that time to try a different gateway, mode, or form each week.

Which part do you find hardest to get stable: HF level setting, gateway choice, or packet TNC configuration?

  • Replies 2
  • Views 43
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On HF the biggest improvement usually comes from treating the audio chain as part of the transmitter. If the rig has a data mode with a flat audio path, use it. Otherwise USB with the processor off is the next best option. Then set the drive from the software's tuning or test tone and watch the ALC. If the ALC is moving, back off the audio before you touch the power control. A cleaner signal at lower power connects more reliably than a strong, distorted one.

For gateway choice, don't connect to only the closest station. On HF, a gateway a few hundred miles away on a band that is open at that hour can work better than a nearby one on a band with a skip zone. Try two or three from the channel list and note which ones answer. If a gateway never answers, the usual reasons are band conditions, a busy channel, wrong frequency offset, or a rig set to the wrong sideband. Check those before you change the modem settings.

One caution on VARA HF: the free unregistered mode is slower, and what you get depends on the registration state. If you plan to use it in an exercise, test it ahead of time instead of finding out on the day. ARDOP is a good fallback because it has no license cost and works well on weak or noisy paths, even though it is slower.

  • Moderators

On VHF/UHF the practical split is packet, VARA FM, and P2P. Packet is the most compatible with older TNCs and radios with built-in TNCs. VARA FM can move messages faster when the link quality is good, but it needs a sound-card connection to the radio's data or mic/speaker ports, and the audio levels matter in the same way as on HF. If your FM link is marginal, a good antenna and a clean level setting do more than switching modes.

P2P is worth practicing even if you never expect to be out of internet range. With two stations on the same simplex frequency and the same mode, you can pass a message with no gateway. Agree on the callsigns or SSIDs, the frequency, and who is listening. Many failed P2P attempts are a mismatch in one of those, or both stations trying to call at once.

For ICS-213 or other forms, do a test message to yourself or a friendly station and confirm what the recipient sees. If they use Winlink Express, they get the form view. If they use a webmail client, they see only the text body. That matters if a served agency expects the form. Also keep a plain-text fallback ready in case the form data doesn't render, and keep it short, since every extra kilobyte costs airtime.

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.