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 Express setup: choosing between Telnet, Packet, VARA, ARDOP, Pactor and P2P, and getting messages through

ci_cover.jpg

This is a working outline for a new Winlink Express station, plus a few open questions at the end. Correct anything I have wrong.

The basic architecture. Winlink is a message system, not a mode. Your client (Winlink Express on Windows) builds a message and connects by some method to a gateway, called an RMS (Radio Message Server). The RMS passes traffic to and from the central Winlink servers over the internet. The gateway is the only part that needs internet. Your station can be completely off-grid as long as you can reach a gateway by radio, or reach another station directly with a P2P session.

Session types in Winlink Express.

Telnet: connects to Winlink over the internet, with no radio involved. Use it to confirm your callsign, password, and message flow before touching a rig. Fix account problems here first, so they are not mixed up with RF problems later.

Packet: AX.25 through a TNC, either a hardware TNC or a software one such as a sound card modem using KISS. This is typically used on VHF/UHF through packet RMS gateways. It is simple and robust, but slow at 1200 baud, and it depends heavily on a clean path to the gateway.

VARA FM: a sound card modem for VHF/UHF FM. It is considerably faster than 1200 baud packet when the path is good. The software needs to be installed and configured separately from Winlink Express.

VARA HF: a sound card modem for HF SSB. The free version is speed-limited, and registration removes the limit. Its strength is adapting to changing conditions.

ARDOP: another open sound card HF mode. It is a common choice when someone wants an alternative to VARA, and it is supported through a separate ARDOP TNC program.

Pactor: needs a dedicated hardware modem (SCS). Pactor 1 and 2 are the older modes, and the faster levels need the matching modem capability. It is common on HF gateways, but it is the most expensive entry point.

P2P (peer to peer): a direct station-to-station connection using Packet, VARA, ARDOP or Pactor. No gateway or internet is involved. The two stations agree on a frequency and mode, and one calls the other. This suits local nets and served-agency work when the infrastructure is down.

Sound card and TNC checklist.

1. Use a data mode (USB for HF; data or FM-data input on VHF/UHF), and turn off speech processing, equalizers and noise reduction.

2. Set the PC audio output so the rig is not driven into ALC. Digital modes are not forgiving of overdrive, and splatter reduces your decode rate and annoys neighbors.

3. Decide on PTT early: CAT, serial RTS/DTR, a VOX-style interface, or a hardware interface. Test PTT with a dummy load before going on the air.

4. Disable Windows sound effects and any other app that might use the same audio device.

5. Set the PC clock accurately. Some modes are sensitive to timing, and a sloppy clock causes odd connection failures.

Passwords. You need your Winlink account password in Winlink Express for Telnet and for gateway sessions. Passwords are case sensitive. Keep a recovery email on the account so you can reset it if you forget it.

Questions for the group.

1. For someone with only one radio and one sound card interface, what is the practical order: Telnet test, then VARA FM to a local gateway, then HF?

2. How do you pick HF gateways when you cannot tell which ones are currently reachable?

3. What is the right way to configure and use Radio-only messages, and when would you use them instead of ordinary messages?

4. Any good practice for ICS-213 forms over low-speed links?

  • Replies 2
  • Views 13
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the gateway question: the channel selector in Winlink Express is the right tool, but it only works well if you update the channel list while you still have internet. Do that before any deployment or exercise. A stale list leaves you guessing, and some of the listed gateways may no longer be active or may have changed frequency.

For VHF/UHF, distance and line of sight matter more than anything else. Pick the gateway with the best path, not just the one that is closest on a map. If you can hear nothing from it on your radio, a packet or VARA FM connection will usually not work either. If one gateway fails, try another before suspecting your setup.

For HF, the channel selector can show propagation estimates, which helps narrow the list. Treat those as estimates, not a promise. Pick two or three candidates across different bands or distances and try them in turn. A gateway that is a long way off may beat a nearby one depending on the band and the time of day, and a very short path can fall inside the skip zone.

One detail that causes mistakes: check how the frequency is presented in the list. HF frequencies for these modes can be given as a center frequency, while your rig is set to a dial frequency in USB. If Winlink Express controls the rig through CAT, it handles this for you. If you tune by hand, work out the offset carefully, or you will be listening in the wrong place.

On audio: set the transmit level so ALC barely moves, then check that the receiving gateway reports a clean link rather than a fast but error-prone one. If you hear a nearby station but the other end cannot copy you, suspect transmit audio, power, or antenna before you suspect the software.

For packet with a software TNC, make sure only one program owns the audio device and that KISS port settings match. A hardware TNC is simpler on the PC side, but the TNC's own parameters (baud rate, KISS mode, flow control) have to match what Winlink Express expects.

  • Moderators

On messages and forms: for anything on a slow link, keep the message short. Avoid images and large attachments. Winlink compresses messages, but a large attachment over a weak HF path will tie up the channel and may not complete. Put the key information in the body text, and send big files only over a fast link such as Telnet.

ICS-213 in Winlink Express is selected from the form templates. The program opens the form in a viewer, you fill it in, and it is attached to the message as form data with the text content included. For another operator to see the formatted form, their client has to support the same forms. If the recipient has no form viewer, the text content in the message body still carries the information. Always make sure the body text is readable on its own.

Radio-only is a message setting meant to keep a message on the radio side of the network, so it is not handled like ordinary email. Check the current Winlink documentation for exact behavior. It is not something to switch on by default, and it matters when you need to keep traffic off general internet delivery. Confirm that the recipient is actually reachable that way, or the message may sit undelivered.

P2P: both operators need to agree on the mode and frequency in advance. One station sets its client to listen and the other initiates the connection to the callsign. Messages waiting in the outbox for that station are exchanged during the session. It works with no gateway, so it is good practice for a local network when the infrastructure is down. Because there is no CMS in the path, there is also no store-and-forward through the wider system. If you need the message delivered elsewhere, you still need a gateway connection afterward.

For practice, Winlink Wednesday is a weekly activity where operators send a check-in through their normal gateway path. Look at the current Winlink Wednesday page for the instructions, since details and addresses are updated by the organizers. It is a low-pressure way to test whether your VARA, ARDOP, Pactor or packet setup actually reaches a gateway, and what your real success rate is, before a real emergency.

One habit worth building: after every session, read the session log. It shows whether the problem was connecting, authentication, transfer, or only the delivery afterward. That log is usually the fastest way to tell an audio problem from a password problem from a gateway that is simply down.

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.