Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base -Powered By Ham CQ DX

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.
Solar
SFI 128
SN 73
A 6
K 1 Quiet
X-Ray B7.3
Wind 399.5 km/s
Aurora 2
Updated 03:30 UTC HamQSL · N0NBH
Day 80/40m Fair 30/20m Good 17/15m Good 12/10m Fair
Night 80/40m Good 30/20m Good 17/15m Good 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 — getting RMS gateway to actually connect, few questions

so ive been messing with Winlink Express for a few weeks now and i think i mostly understand the concept but actually getting a session to go through has been hit or miss. im using a TNC-Pi with my 2m radio pointed at what should be a local RMS gateway and sometimes it connects fine, sometimes it just sits there throwing errors about no response or session timeout or whatever.

my main question is about gateway selection — i know you can sort by distance in the gateway list but does signal path quality matter more than raw distance? like theres one gateway 12 miles away but its basically line of sight blocked by a ridge, and another one thats like 28 miles but supposedly on a hilltop. been going back and forth on which to set as my default. also not sure if i should be using the VHF-FM channel or trying to set up an HF winlink session for better coverage, i have an HF rig but havent tried to configure a pactor or vara session yet.

also the message handling side is confusing me a bit — i get that its basically email but the addressing with the WL2K suffix and how it routes through the CMS servers, does the gateway forward everything automatically or do i need to trigger that somehow. feels like i set it up right but im not 100% sure messages are actually going anywhere

  • Replies 1
  • Views 77
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the gateway distance thing — yeah go with the hilltop one even at 28 miles, line of sight is everything on 2m. a clear shot at 30 miles beats a marginal path at 10 any day of the week. you can check the gateway's recent activity in Winlink Express, it'll show you last connection times and if its been active you're probably fine.

on the message routing, once your session completes the CMS sync happens automatically, you dont have to do anything. whatever you've queued in your outbox gets pushed to the CMS and from there it routes like normal email. the WL2K addressing is only needed if you're sending to another ham on the winlink system, if youre sending to a regular email address you just use that directly. worth double checking your callsign is registered on winlink.org too if you havent, sessions will kind of half-work without it but messages dont always get delivered right.

for HF and VARA — honestly just get VARA HF set up even if you dont use it right away. its free, way better throughput than Winlink's older modes, and when you eventually want to reach a gateway when local VHF is down or youre out of range it's already there. soundcard interface is all you need if you have a radio with audio out.

yeah i had the same issue when i started, turned out my TNC baud rate didnt match what the gateway was expecting. worth checking that the channel config in Winlink Express actually matches your TNC settings exactly, like even a small mismatch on the packet speed and it just times out without telling you anything useful. kind of frustrating honestly

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

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.