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 146
SN 141
A 6
K 2 Quiet
X-Ray C1.3
Wind 448.0 km/s
Aurora 3
Updated 21: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

RemoteRig CW latency workaround for unreliable internet links

Setting up my RemoteRig 1258MkII units between home and remote QTH (~120ms ping through rural Starlink). Having issues with CW sidetone delay making it nearly impossible to send clean code with the 120ms latency through the link. Started experimenting with the built-in keyer function to generate local sidetone. The audio muting feature (LF delay ms) seems promising to eliminate the delayed radio sidetone. Anyone else working CW through high-latency satellite internet with similar setup?

  • Replies 2
  • Views 98
  • Created
  • Last Reply

Top Posters In This Topic

Most Helpful Posts

  • Amanda Wilson
    Amanda Wilson

    I ran RemoteRig for years through a 40ms cable connection and found setting the LF delay to match your ping time works well. Start with 120ms delay and fine-tune from there. The local keyer makes all

  • David Davis41
    David Davis41

    That latency sounds brutal for CW! Consider adding a remote-controlled power switch at the remote site - learned this the hard way when my IC-7300 locked up during a contest. What's your backup plan i

Featured Replies

I ran RemoteRig for years through a 40ms cable connection and found setting the LF delay to match your ping time works well. Start with 120ms delay and fine-tune from there. The local keyer makes all the difference - you'll send perfect CW once dialed in.

That latency sounds brutal for CW! Consider adding a remote-controlled power switch at the remote site - learned this the hard way when my IC-7300 locked up during a contest. What's your backup plan if the RemoteRig boxes crash?

Are you monitoring your own signal at the remote end? Try using one of the HF WebSDR receivers to monitor your output signal quality - helps verify the CW timing is clean on-air even if it sounds delayed locally.

  • Guest unlocked, unpinned, pinned and locked this topic
  • Guest unlocked, unpinned, locked and pinned this topic
  • Guest unlocked, unpinned, locked and pinned this topic

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...

Account

Navigation

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.