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.
Solar
SFI 118
SN 152
A 3
K 0 Quiet
X-Ray A0.0
Wind 300.8 km/s
Aurora 1
Updated 10: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 setup is confusing me, keep getting RMS connection timeouts

so ive been trying to get winlink going for a few weeks now and i just cant figure out what im doing wrong. i have pat installed on a raspberry pi and im using a SignaLink USB with my 897D on 40m. the issue is whenever i try to connect to a gateway it just times out, every single time. i can hear the gateway beaconing, my waterfall shows the signal fine, but when i try to initiate a session nothing happens. or actually sometimes the session starts and i hear the warble tones go out but then it just hangs and eventually drops.

i went through the RMS list and sorted by distance, im hitting stations that should be well within range. im in the mountain west so RF path isnt exactly flat but i can hear these guys clearly. audio levels in the SignaLink look right to me, i have the TX knob around 11 oclock which is where most people say to set it for VARA or Winmor. running VARA HF in the free version right now.

one thing im not sure about is how the message routing actually works after you successfully connect, like does pat handle that automatically or do you have to configure something on the CMS side? i kind of assumed it was automatic but maybe i am missing a step somewhere. any help appreciated, this has been frustrating

  • Replies 1
  • Views 32
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

the timeout thing with VARA free vs paid is a real issue a lot of people hit and dont realize. free version is rate limited pretty heavily and on a marginal path it will just give up before completing a handshake. that said if you can hear the gateway clean it should at least negotiate. what does the VARA modem window actually show when it fails, is it connecting at all or just sitting there? also check that your soundcard sample rate is set to 12000hz and not auto, that trips up a lot of people on linux installs.

on your question about message routing - yeah its basically automatic once you connect. the CMS handles the mailbox stuff, pat just tells it your callsign and it syncs whatever is pending. you dont have to do anything special on the CMS web side unless you want to set up position reports or forwarding rules, which is optional.

had the exact same problem last year, turned out my TX audio was actually way too hot despite looking normal on the SignaLink meter. the problem is the 897 has a menu setting for the data port input level and mine was cranked up which meant i was overdriving the modulator even though the SignaLink looked fine. overdriven VARA sounds absolutely terrible on the other end and gateways will just drop you. try pulling the SignaLink TX knob down to like 9 oclock and bump it up slowly while watching ALC on the radio, ALC should barely move, if its pumping at all youre overdoing it. took me embarrassingly long to figure that out.

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.