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 C4.3
Wind 398.1 km/s
Aurora 1
Updated 11: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

FT8 vs JS8Call for actual two-way conversation — am I missing something

 Loading...

so ive been running FT8 for about a year now and yeah its great for working new entities and all that but every time i try to actually talk to someone its just the standard exchange and done. i get it thats kind of the point. but lately ive been reading about JS8Call and it seems like the idea is you can have a real QSO using the same weak signal tech underneath it.

tried it last weekend on 40m and the waterfall looked completely dead compared to what FT8 looks like. maybe 3 or 4 signals visible the whole session. so my question is — is JS8Call just not popular enough to be usable or am i looking at the wrong times, wrong bands? i was on around 7.078 which i think is the standard dial freq but honestly not sure if thats even right anymore.

also still have WSJT-X running on the side and i noticed my FT8 decode rate dropped a bit, guessing thats a cpu thing. running on a pretty old laptop. anyway the main thing is i want to know if JS8Call is worth sticking with or if its kind of a dead end activity wise

  • Replies 1
  • Views 4
  • Created
  • Last Reply

Featured Replies

JS8Call is definitely less populated than FT8 but its not dead, you just have to know when to look. 40m is actually decent but i've had better luck on 20m during the afternoon, roughly 14.078. there's also a small but pretty active group that uses it for keyboard-to-keyboard rag chewing, which is honestly what drew me to it in the first place. the whole point is you dont need a full signal to copy each other which is nice when conditions are marginal.

7.078 is correct for 40m so you had the right frequency. might just be a timing thing. also the heartbeat feature where stations beacon automatically helps a lot for finding activity — if you havent turned that on yet its worth doing, basically lets you see whos around without them having to actively transmit a message.

yeah the cpu thing is real, i had the same issue running two WSJT-X instances on an old thinkpad. eventually just set up a cheap mini PC dedicated to digital stuff and that solved it. js8call does run a bit heavier than ft8 because of all the extra framing i think.

honestly though i still go back to PSK31 when i want an actual conversation. i know thats kind of old fashioned at this point but theres still people on 14.070 area and the exchanges feel more like a real QSO. ft8 kind of ruined me for caring about signal reports because nobody actually means anything when they send you a -14

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.