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 go-kit setup order: modes, gateways, sound card/TNC settings and message handling

ci_cover.jpg

I'm putting together a checklist for a Winlink station that can run HF, VHF and a local-only fallback, and I'd like feedback on the order of operations. The pieces I'm trying to fit together: Winlink Express on a Windows laptop, a sound card interface for VARA HF/VARA FM/ARDOP, a KISS or software TNC for packet, Telnet for when the internet is up, and P2P sessions for station-to-station work. Pactor is on the list only if someone has the SCS hardware.

My current plan is: (1) register the callsign and set the Winlink password, (2) run a Telnet session to confirm the account works, (3) update the channel list and form templates while still online, (4) configure the sound card and PTT, (5) test VARA FM or packet to a nearby gateway, (6) try HF, (7) practice P2P, (8) practice forms like ICS-213 and send them in a drill such as Winlink Wednesday. Is that sensible? What do you do differently, and which settings trip people up most?

  • Replies 2
  • Views 27
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The order is good. I'd move the Telnet test even earlier and treat it as the account check. If Telnet Winlink connects and your outbox clears, the callsign, password and Winlink Express install are fine. Any later failure is then a radio, audio, PTT or propagation problem. Keep a record of the password somewhere that doesn't depend on the laptop, and watch case and stray characters when typing it. If it's lost, the recovery route goes through the email address on the account, so make sure that address is still reachable.

Before you go offline, update the channel list in Winlink Express and open the channel selector for each mode you plan to use. The gateway list is downloaded from the internet and cached. If you only ever look at it during an emergency, you may be looking at stale data. The HF channel selector can also show propagation estimates for your location, which saves time when you're choosing between several gateways. Treat it as a guide, not a guarantee.

On HF, remember the listed frequency for VARA HF, ARDOP and Pactor gateways is the center frequency. If you're setting the radio by hand in USB, the dial frequency is normally the center minus 1500 Hz, assuming the modem is centered at 1500 Hz. With CAT control, Winlink Express usually handles this for you, but verify it once with a known gateway.

For the sound card setup, the common failures are overdriven transmit audio and the wrong audio device selected in the modem. Turn off any processing on the radio, set the Windows playback level so the ALC stays at or near zero, and don't compensate for a weak signal by raising drive. For PTT, pick one method and test it with the dummy load first: CAT, serial RTS/DTR, a CM108-style GPIO, or VOX. VOX is the one most likely to clip the start of a packet or drop out in the middle of a connection.

VARA HF and VARA FM are separate modems that Winlink Express calls. The unregistered versions are speed limited, and registration removes that limit. VARA FM has narrow and wide modes, and the wide mode needs a radio and interface that pass the wider audio bandwidth cleanly. If the VHF setup is flaky, start with the narrow mode. ARDOP is free, and many people keep it as a second option when VARA isn't available, for example on platforms where VARA is awkward to run.

  • Moderators

Adding to the packet and message-handling side. For packet, Winlink Express can talk to a hardware KISS TNC, to some TNC-specific interfaces, or to AGWPE-compatible software. Dire Wolf is a common software TNC for the sound card, and it exposes an AGW and a KISS port you can point Winlink Express at. Check the baud rate matches the gateway. A lot of VHF packet is 1200 baud AFSK, and some places run 9600. Many gateways use an SSID like -10, but don't assume that. Copy the call exactly as listed in the channel selector, including any digipeater path if the gateway needs one.

Don't skip P2P. A peer-to-peer session uses the same modems (packet, VARA, ARDOP, Pactor) but connects directly to another station instead of an RMS gateway, so it works when no gateway is reachable. Set up one station to listen and the other to call, using the P2P session types in Winlink Express, and make sure the listener is actually in the listening mode before you start debugging audio. There is also Telnet P2P for local network exchange, which is useful for testing and for a served-agency location with no internet gateway.

Radio-only needs a clear explanation for a team, because it's easy to misread. A message marked radio-only is meant to travel only over radio paths and not be delivered through internet-based routes. That's useful when you want a message to prove the radio path or when an agency doesn't want the content moving over the internet. The trade-off is that it may not be retrievable the way a normal message is, so don't mark routine traffic that way without a reason.

For forms, the ICS-213 General Message is part of the standard templates in Winlink Express. The form opens in a browser, you fill it in, and when you submit it, the data goes into the message. Keep templates updated before an exercise, because a mismatch can make the sender's form look different from what the recipient sees. A short, plain-text description of the key content in the message body is also worth adding.

On message size, keep HF messages small. Skip photos, big PDFs and anything else that eats up airtime. If the content isn't needed, don't attach it. For messages to a normal internet address, use the SMTP: prefix in the To field when needed. Internet senders replying to a Winlink address may be filtered, which is why the subject prefix //WL2K is sometimes used. That's worth testing before you rely on it.

For Winlink Wednesday, I'd confirm the current details with the organizer or the group running it, since I can't verify a schedule from here. As a drill, a good one is a short check-in message using the radio mode you actually plan to use in an emergency. Record which gateway you reached, the mode, the time and any errors. That log gives you the real list of what works from your location.

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.