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 147
SN 157
A 10
K 1 Quiet
X-Ray C1.1
Wind 429.1 km/s
Aurora 1
Updated 20: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

js8call vs ft8 for low power stuff — which are you actually using

 Loading...

so ive been running FT8 for about two years now mostly on 20m and 40m with a dipole in the attic and around 50w, and yeah it works great for getting contacts but lately i feel like its kinda... hollow? like you just exchange grid squares and signal reports and thats it, nobody actually says anything to each other

started looking at JS8Call because at least you can have a real conversation and it still has decent weak signal performance, the protocol is built on the same foundation as FT8 basically but slower and you can actually type a sentence. has anyone run both for a while and can tell me if JS8Call is actually usable for ragchewing or is it just too slow to feel natural

also curious how it compares on like actual sensitivity, i know FT8 gets down to like -24dB or whatever but does JS8Call get close to that or do you give up a lot there. running WSJT-X for FT8 right now and the waterfall setup is already there so the jump to JS8Call hopefully isnt too bad

  • Replies 1
  • Views 32
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

JS8Call is genuinely usable for conversation but you have to adjust your expectations — it's not IRC, more like texting someone who replies every 30 seconds or so depending on which speed setting they're using. Normal mode is 15 seconds per transmission, slow is 30, there's a turbo mode that's faster but noisier. Most people i've talked to are running normal speed.

Sensitivity-wise you're giving up a little compared to FT8 but honestly not as much as you'd think. I've had contacts through some pretty rough conditions with maybe 10w into a PAR end-fedz. The bigger thing is there's just way fewer people on it so if you're in a rural area you might be calling CQ into the void for a while, especially on anything other than 40m or 20m. There's a relay feature that lets messages hop through other stations which is cool in theory but ive never actually needed it.

Point is if you want actual communication with weak signal capability it's probably your best option right now, FT4 is even more stripped down than FT8 so that's not gonna scratch that itch either.

i switched from ft8 to js8call for basically the same reason and yeah i like it a lot more but the activity thing is real, some days on 20m i'll sit there for an hour and maybe get two or three responses. 40m evenings are better. if you want guaranteed contacts ft8 is still king but if you want to actually talk to someone js8 is worth learning

  • Guest pinned, unpinned, locked and unlocked this topic
  • Guest pinned, locked, unpinned and unlocked this topic
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.