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 201
SN 126
A 14
K 1 Quiet
X-Ray C2.5
Wind 391.2 km/s
Aurora 2
Updated 15:30 UTC HamQSL · N0NBH
Day 80/40m Poor 30/20m Good 17/15m Good 12/10m Good
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

JS8Call vs FT8 for actually having a conversation — worth the tradeoff?

 Loading...

so ive been running FT8 for about a year now and honestly it scratches the DX itch pretty well but theres something that bugs me about it — like yeah i worked 87 countries and whatever but i never actually talked to anyone. its just grid squares and signal reports flying around and you close WSJT-X feeling like you ran a database query not had a QSO.

anyway somebody at my club mentioned JS8Call a few months back and i finally got around to setting it up last weekend. its basically running on top of the same weak signal foundation as FT8 but you can actually type messages back and forth, relay stuff, even do store-and-forward messaging which is kind of wild. the tradeoff is its slower obviously and the band has to cooperate a bit more but on 40m last night i had like a 20 minute back and forth with a guy in New Mexico and it felt more like ham radio to me than anything ive done in a while.

my question is whether anyone is running both regularly or if you kind of pick one and stick with it. also curious if the JS8Call nets are actually active enough to be worth monitoring — i havent found a ton of activity on 20m during the day. the heartbeat stuff is cool but only if theres people sending them

  • Replies 1
  • Views 7
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah i run both, keep WSJT-X open on one radio and JS8Call on another when i can. FT8 is basically just a point scoring thing at this point, nothing wrong with that but you nailed it — its not a conversation. JS8Call has a totally different feel. slower yes, and you do need a reasonably clean signal path or the decodes get choppy, but when it works its genuinely satisfying.

activity on 20m can be hit or miss depending on time of day. i find the 14.078 spot has decent traffic in the early evening UTC, and 40m overnight is usually pretty good in North America. the relay and aprs-like messaging stuff is where it gets interesting if you want to do something more than ragchew — ive seen people use it for lightweight emcomm stuff and it makes a lot of sense for that. not as fast as packet but way more robust on marginal paths. worth keeping in the rotation for sure, just dont expect it to replace FT8 for working new entities or anything like that

honestly same experience here. i tried JS8Call for a few weeks and liked it but the activity in my region was just really sparse, kept calling CQ and getting nothing back for like an hour at a time. might depend a lot on where you are. i drifted back to FT8 mostly because at least something always happens when you turn it on. still have JS8Call installed though, might fire it back up and give it another shot on 40m like you mentioned

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.