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 2 Quiet
X-Ray B7.0
Wind 387.5 km/s
Aurora 2
Updated 05:00 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 - RMS gateway confusion, am i doing this right?

So ive been trying to get Winlink Express working for the past week and a half and im starting to think im overcomplicating this whole thing. Background: i have a Kenwood TS-590SG hooked up through a SignaLink USB, running Vara HF, and i can see gateways in the list no problem. I can even see RF propagation looks decent on 40m to a couple of the closer RMS nodes.

But here is where it gets weird. I connect, it says session started, and then just... sits there. Sometimes it eventually times out, sometimes it actually pulls a message through but then drops mid-transfer. I checked the VARA waterfall and the signal looks clean to me, no obvious noise floor issues. ALC is behaving, audio levels seem right.

Is there something about how RMS gateways handle the handshaking that i should know about? Like is there a timing thing with how Winlink Express initializes the session versus when VARA actually finishes its negotiation? I swear ive read the documentation three times and it doesnt really address this specific thing. Or maybe im just expecting it to be faster than it actually is and the timeouts are normal? Anyone run into this with VARA HF specifically?

  • Replies 1
  • Views 105
  • Created
  • Last Reply

Top Posters In This Topic

Most Helpful Posts

  • Elizabeth Patel
    Elizabeth Patel

    yeah this sounds like the classic audio level thing even if you think its set right. with the SignaLink on a TS-590 specifically, the receive audio path can be tricky because the 590 has that built in

Featured Replies

yeah this sounds like the classic audio level thing even if you think its set right. with the SignaLink on a TS-590 specifically, the receive audio path can be tricky because the 590 has that built in USB audio but if youre using the SignaLink it should be going through that instead. one thing i had to do was actually go into the VARA HF settings and drop the TX drive way down, like further than felt right, because the ALC was technically in range but VARA was still getting clipped somewhere in the chain.

also worth checking - what RMS gateways are you targeting? some of the busier ones on 40m can have a queue and if youre catching it at a bad moment the session will just stall out. try hitting one thats a little further out or on a less congested band, sometimes 30m is way cleaner for this kind of thing. the handshake timing with VARA isnt something you really need to tune manually, it handles that, but the gateway does need a clean connection to negotiate properly so any hiccup in audio and it just gives up.

one thing nobody mentioned to me when i first started with Winlink was that the RMS gateway list in the program isnt always showing you current status, like a gateway can show up green and be basically unreachable at that moment for various reasons. i started cross-referencing with the Winlink.org map online before i connect and that helped a lot honestly. you can see last activity timestamps and get a better sense of which nodes are actually active versus just listed.

also if you havent already, try Telnet mode just to verify your account and message handling is working end to end before you blame the RF path. if Telnet works fine then you know its definitely something in the VARA or audio chain and not a Winlink account configuration issue.

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.