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 B9.3
Wind 401.6 km/s
Aurora 2
Updated 00: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

RemoteHams SDR setup — anyone actually using this for serious HF work?

so ive been messing around with remote station control for about six months now and finally got a decent setup going but im curious if anyone else is running RemoteHams RCForb or the SDR remote stuff for anything beyond just casual listening. my situation is i live in an HOA nightmare so the remote shack at my dad's property about 40 miles out is basically my only option for real HF operation.

the latency isnt terrible on a good day, maybe 150-200ms round trip which is workable for SSB but CW is kinda rough unless you go full QSK and just deal with it or run a keyer at the remote end. i set up a Raspberry Pi out there running a bunch of stuff and the audio path is actually the part that gives me the most headache — the codec settings in RCForb are a bit buried and i never quite know if im optimizing them or just making things worse.

also thinking about tying in some IRLP or Echolink nodes for VHF/UHF linking through the same internet connection out there but not sure if that's going to create a bandwidth nightmare or if it's actually fine in practice. anyone done both at the same site? the upload at that location is only about 15 Mbps which should be plenty but i've been surprised before.

  • Replies 1
  • Views 4
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah 15 up should be more than enough honestly, IRLP and echolink dont use much at all, were talking maybe 8-12 kbps for a connected node in codec2 or GSM mode. the bigger issue you might hit is if the Pi is trying to do too many things at once — audio routing for RCForb, the node software, maybe some CAT control or logging stuff, it can get jittery. i'd almost suggest separating the node onto a cheap second Pi just to keep things clean.

on the CW thing — i moved my keyer to the remote end a while back and that solved basically everything. running the paddles locally and sending keystrokes over the internet is just asking for trouble. if you haven't done that yet its worth the afternoon to set up, made the whole thing way more usable for me at least.

i tried something similar a couple years back with a different remote software and honestly the SDR side of it was what impressed me most — being able to just grab a slice of spectrum and look at whats happening before you transmit is kind of a game changer when youre doing this remotely and cant just walk over and check the antenna or whatever. my setup never got fully stable but that was more a networking issue on my end than anything with the software itself i think.

one thing i'll say is make sure whatever router is out at your dad's place supports proper QoS if you do add the linking node. nothing worse than your echolink audio eating your rig's audio path during a pileup lol

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.