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 433.7 km/s
Aurora 2
Updated 23: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

RemoteHams setup with SDR backend — anyone else doing this?

so ive been messing around with running my home station remotely for about 6 months now and finally got something that mostly works but im curious if anyone else has gone down the RemoteHams route with an SDR backend instead of a traditional rig

my setup is kind of weird — i have an RSPdx feeding into SDR++ on the server side and then im bridging the audio through RemoteHams RCForb client on the other end. the latency is actually pretty tolerable on my home fiber connection, like 80-90ms round trip, but when i try to connect from my work laptop on their corporate wifi it gets ugly fast. not sure if thats a QoS thing on their end or if RCForb just handles jitter differently than something like WebSDR would

the internet linking side of things is where it gets complicated. ive got an Allstar node running on the same machine and im trying to figure out if theres a sane way to tie the SDR audio path into the Allstar audio without creating some kind of horrible feedback loop or ground loop nightmare. i know people run Allstar and RemoteHams on the same box but every post i find is like 4 years old and half the links are dead

anyone done something like this recently? what are you using for audio routing on the server side, virtual audio cable type stuff or are you patching it in hardware

  • Replies 1
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah the corporate wifi thing is almost certainly their QoS hammering your UDP packets. voip and gaming traffic gets deprioritized a lot on managed enterprise networks and RCForb is basically indistinguishable from voip traffic as far as any layer 3 switch is concerned. i ran into the exact same thing trying to connect to my station from a hospital network — completely unusable. ended up just using my phone as a hotspot for anything serious

on the Allstar + RemoteHams question i did this about 18 months ago. i used VB-Audio Virtual Cable on windows to route the SDR++ output into a virtual device and then pointed the Allstar chan_usbradio config at that same device as the receive audio source. it works but its finicky as hell, youll want to watch your audio levels carefully because virtual cable doesnt clip gracefully and youll get some nasty distortion going into Allstar if the SDR output is too hot. i had mine set about 6dB lower than i thought it needed to be and it was fine after that

the feedback loop concern is real if youre planning on transmitting through the Allstar node and monitoring through the SDR at the same time but if theyre on different frequencies or youre just using the SDR as a panadapter and transmitting through a separate rig it should be fine

i dont run RemoteHams specifically but ive been doing remote ops with a physical rig (IC-7300) over the internet for a couple years and the latency stuff you're describing sounds pretty normal honestly. 80ms is workable for SSB, gets annoying for CW if youre used to the feel of a real key but you adapt

never tried mixing in an SDR on the server side, thats an interesting idea for using it as a wideband monitor while the main rig does the actual work. let us know how the Allstar integration goes, im kinda curious if it actually hangs together reliably or if its one of those things that works great for a week then randomly dies

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.