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 checklist: Express, RMS gateways, sound card/TNC choices, P2P, and ICS-213 handling

ci_cover.jpg

This thread is for sorting out a Winlink station from scratch. It covers the order to configure things, which session type fits which job, and where messages tend to go wrong. Corrections are welcome. Settings and menu names can change between Winlink Express versions, so check anything critical against the current Winlink documentation.

Start with Telnet. Install Winlink Express, enter your callsign, and set the account password. Then run a Telnet Winlink session over the internet. This proves the account, the password, the forms templates and the basic send/receive path before any radio is involved. A password typo is easy to mistake for a bad RF setup, so rule it out first. Passwords are case-sensitive, and a gateway or CMS rejection at login points to the account, not the modem.

The names are easy to mix up. An RMS (Radio Message Server) is a gateway station that accepts your radio connection. The CMS (Common Message Server) is the internet-side system the gateways talk to. In the Winlink Express session list you pick the transport: Packet Winlink for VHF/UHF AX.25, Pactor Winlink, ARDOP Winlink, VARA HF Winlink, VARA FM Winlink, Telnet Winlink, and the P2P variants. Each needs its own modem or TNC set up in Express before it works.

For the sound card modes (VARA HF, VARA FM, ARDOP, and soundcard-based packet), the usual approach is a rig with a data or audio interface. Use USB or USB-D mode on HF, keep the transmit filter wide enough for the mode, and turn off speech processing, compression and equalization. Disable Windows audio enhancements on the interface device. Set the transmit level so the ALC shows little or no action. Overdriving the audio is a common cause of poor sessions, because it splatters and lowers decode success. PTT can come from CAT, serial RTS/DTR, VOX or a CM108-style GPIO, but pick one deliberately and test it into a dummy load.

Pactor is different. Pactor 3 and 4 need an SCS modem, with a hardware controller and a serial or USB link to the PC. It is a good fit if you already own the modem or need compatibility with the many gateways that support it. For a new station on a budget, VARA HF or ARDOP is usually more practical. VARA is sound card based, and its free, unregistered version runs at a reduced speed. A registration key unlocks the higher-speed modes. ARDOP is free, and its bandwidth setting trades speed against robustness.

For VHF/UHF, 1200 baud packet through a KISS or hardware TNC is the older, widely supported option. VARA FM is a sound card option that suits FM voice radios with a data port, and it is much faster when the link supports it. Whatever you use, check that the TNC type and port settings in Express match the hardware. Software TNCs such as Dire Wolf are popular, but you still have to confirm how Express connects to them.

When choosing a gateway, use the Channel Selector in Express. It shows nearby stations by mode and can estimate how likely a path is to work. Update the list while you have internet, since an offline copy may be stale. Note whether frequencies are listed as dial or center frequency for the mode, and set the rig offset to match. Many HF digital mistakes come from being 1500 Hz off, or from sitting on the wrong sideband.

Message handling matters as much as the link. Keep messages short and avoid large attachments, especially on slow HF links or crowded gateways. Remember that Winlink traffic is not private and that amateur rules still apply, including no obscuring of meaning and no business use. Anything sent through a gateway can also pass through the internet.

Forms are the other big topic. Express has templates, including the ICS-213 General Message, that fill out in a browser-style viewer. The form data travels as an attachment with a text body for readability. A recipient who is not using the matching form viewer may see only the plain text, so tell recipients what to expect. Keep form templates updated, and test with a known partner before relying on a form in an exercise.

Winlink Wednesday is a good place to practice. It is a weekly on-air practice routine, so check the current schedule and instructions from the organizers before joining. Questions for the thread: what do you configure first on a new install, and which mode do you use first for a local emergency communications group?

  • Replies 2
  • Views 26
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd choose by path, not by what's newest. If the nearest RMS is within VHF/UHF range and you have a radio with a good data port, VARA FM or packet is the first thing to test. It's fast, simple and uses a short, predictable airtime window. HF is for when the distance or the local damage means VHF paths aren't available. On HF the choices are usually VARA HF, ARDOP or Pactor, depending on what the nearby gateways actually offer. There's no point setting up a mode that none of the reachable gateways listen for.

On gateway selection, don't just take the top of the list. Look at the distance, the band and time of day, and whether the path prediction is realistic. A closer station is not always easier on HF because of skip zones. Try two or three candidates and watch the session log. If the connection fails, check whether the failure is no answer, a handshake that starts and then dies, or a bad login. Those mean different things: path, level or audio problem, and account problem respectively.

One setup habit that saves time is writing down the radio settings that work: USB or USB-D, filter width, audio level, PTT method and offset. When you need to move to a different band under pressure, you don't want to rediscover them.

  • Moderators

On P2P: it's the mode people forget until the internet or gateways are out. In Express you open a P2P session for the mode you're using, with one station listening and the other calling. The messages go directly between the two stations without a gateway. It's great for an EmComm group that needs a local link between two sites. The catch is that both ends must agree on mode, frequency, and who initiates before the session starts. Practice it on a clear VHF channel first, because it's a different workflow from a gateway connection and the first attempt tends to turn up settings mismatches.

Radio-only messaging is a similar case. It exists for situations where you don't want traffic depending on the internet side, so read the current Winlink documentation on how it behaves and which stations can relay it. Don't assume it works like a normal message that happens to travel by radio.

For ICS-213, the practical advice is to agree in advance on whether the recipient will have Express and the form viewer. If they will, send the form so the fields are preserved. If not, make sure the text body carries the content, because a message that only makes sense in the viewer is a poor fit for a mixed group. Also keep the subject line clear, and confirm the sender, recipient, date and time fields are filled out, since forms are only useful if each field is complete and legible. Finally, keep a local copy of important outgoing messages, because a sent message isn't proof it arrived. A delivery or reply gives that confirmation.

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.