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

Building a Winlink station from scratch: Telnet first, then gateways, modes, P2P and forms

ci_cover.jpg

This thread is for sorting out a sensible order of operations for a Winlink setup, and for comparing notes on where things tend to go wrong. The software and gateway lists change, so treat specifics here as a starting point and check them against the current Winlink documentation. The outline below is the order that tends to cause the fewest headaches.

Step 1: Winlink Express and a Telnet session. Install Winlink Express on Windows and enter your callsign, a password and a recovery email address. Then do a Telnet Winlink session before touching a radio. Telnet connects over the internet straight to a CMS (Common Message Server). It confirms that your account works, that your password is typed correctly (it is case-sensitive), and that you can send and receive. Passwords are not sent in the clear during sessions. The server issues a challenge and the client answers it, but a mistyped or stale password still shows up as a failed login on every mode. Fix it on Telnet, where the failure can only be the account.

Step 2: understand the chain. A radio session goes from your station to an RMS (Radio Message Server, usually just called a gateway). The gateway has an internet link to the CMS, which stores and forwards your mail. When you connect, the gateway delivers your outbound messages and pulls down anything waiting for your callsign. Gateways are not the mailbox, and you do not leave mail on them. The CMS holds it, which is why a message sent while you are off the air will be waiting when you next connect through any gateway.

Step 3: pick the mode for the band. Winlink Express can use several modems. Packet (RMS Packet) is AX.25 on VHF/UHF, normally 1200 baud AFSK, sometimes 9600. VARA FM is the higher-speed VHF/UHF alternative, using your sound card or an interface. VARA HF and ARDOP are sound card modems for HF. Pactor needs an SCS hardware modem and is used on HF gateways too. Which one you need depends on what is actually listed near you, not on which one looks fastest on paper. Open the Channel Selection window in Winlink Express, update the channel list while you still have internet, and look at which modes and bands the nearby gateways support.

Step 4: gateway locations and the channel list. The Channel Selection window lists gateways with distance, bearing, mode and frequency. For HF it can also show propagation estimates. Two practical points. First, the list is cached on your computer, so refresh it before a deployment where internet may not exist. Second, the frequencies in the list are generally center frequencies, so if you tune by hand, remember the dial setting in USB is offset below that (about 1500 Hz below for modems centered at 1500 Hz). With CAT control configured, Winlink Express handles the math. A gateway being listed does not mean it is on the air and workable from your location right now, so have several candidates.

Step 5: TNC and sound card setup. For Packet you can use a hardware TNC or a software TNC like Dire Wolf, usually through a KISS connection (serial, Bluetooth or TCP). For VARA HF, VARA FM and ARDOP, the modem is a separate program that talks to Winlink Express over local ports, so the setup has two halves. First, get the modem alone to key the radio and see audio. Pick the correct sound device (a USB interface or the rig's built-in codec, not the computer speakers), choose a PTT method (CAT, serial RTS/DTR, VOX or the interface's own), and set levels. Second, point Winlink Express at the modem's host and port in its session settings. Keep transmit audio low enough that there is no ALC action. A clean, lower drive level beats a loud distorted one on every one of these modes. Turn off Windows sounds and any audio enhancements on the interface, or they will end up on the air.

Step 6: Radio-only, P2P and forms. Those need their own discussion. I will leave them to the replies, but the main questions are: when does Radio-only make sense, how does a P2P session differ from a gateway session, and how should ICS-213 and other forms be handled? Also, is anyone using Winlink Wednesday as a weekly drill, and how do you structure it?

A reminder on compliance: Winlink compresses data, but the protocol is published and the content must remain plain and legal for amateur service. The control operator is responsible for what goes out over the air, so no business traffic, and no content that violates local rules.

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On modes: for VHF/UHF the practical split is between Packet and VARA FM. Packet is the more widely supported on gateways and tolerates modest gear, and a software TNC makes it cheap to try. VARA FM is much faster when both ends support it, and it has narrow and wide variants, so check that your radio's audio path can actually pass the wide one. A rig's 9600 data port is flat enough, but a mic-input connection often is not. VARA's free version is speed-limited and a registration key unlocks full speed, so a slow session on an unregistered install is not necessarily a propagation or setup problem.

On HF it is mostly VARA HF versus ARDOP versus Pactor. ARDOP is free and open and is a decent fallback. VARA HF generally gets the higher throughput and is common on gateways. Pactor is hardware-dependent (an SCS modem such as the PTC series or P4dragon), so it makes sense if you already own one or need to reach Pactor-only gateways. Check the list for what your nearby HF gateways really offer before spending money.

One suggestion for debugging: when a connection fails, work out which layer failed. If the modem never keys the radio, it is PTT. If the radio keys and the gateway never answers, it is frequency, offset, propagation or level. If it connects and then drops at login, it is credentials. If it connects, logs in and stalls partway through, look at signal quality and bandwidth choice. Switching to a narrower bandwidth for a weak path is often the cheapest fix. Also listen first. Most gateways are shared, and if the channel is busy and you start transmitting anyway, you will get nowhere and annoy other users.

  • Moderators

On Radio-only, P2P and forms. Radio-only is a message option in Winlink Express meant for situations where you want the message to travel only over radio paths and not through internet-connected delivery. It is aimed at emergency use where you do not want traffic exposed to or dependent on internet routes. It limits who you can address (Winlink users, not arbitrary internet email), so read the current help text on how it handles addressing before relying on it in an exercise.

P2P (peer to peer) is different. Two stations connect directly with no gateway and no CMS, so it works with the internet down and no RMS in range. One station listens and the other initiates, in Packet, VARA, ARDOP or Pactor. It is a good fit for a served-agency site talking to a net control station. Test it before you need it, and confirm how outbound messages are selected for the P2P session (for example, addressed to the peer's callsign) in the current docs. Messages exchanged P2P also don't reach the CMS unless one end later forwards them, so if a message must leave the area, someone has to send it through a gateway.

For forms, Winlink Express includes templates, including ICS-213 General Message. The form opens in a browser, you fill it in, and Winlink Express builds the message with the form data attached. The receiving station needs Winlink Express with the matching templates to see it rendered properly, so update templates while online, and make sure both ends have the same set. Keep form messages short and avoid large attachments, because every byte costs airtime, especially on a weak HF path or a busy packet channel.

Winlink Wednesday is a good habit as a weekly practice. The exact format varies by group, so go by the instructions from whoever organizes it rather than assuming. A useful drill is to refresh the channel list, run a Telnet check, try one radio gateway session on each mode you own, and send a short ICS-213 to a known test address. That catches expired passwords, stale templates, sound card drift after a Windows update, and a missing PTT setting while the stakes are low.

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.