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 141
A 10
K 2 Quiet
X-Ray C1.0
Wind 400.7 km/s
Aurora 1
Updated 06: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

JS8Call vs FT8 for actually having a conversation — am I missing something

 Loading...

so ive been running FT8 for about a year now and yeah its great for racking up contacts and working new countries but lately i feel like im just clicking buttons and not actually doing any ham radio if that makes sense. its like a video game almost. anyway someone at our club mentioned JS8Call as a way to have real qsos on weak signal and i installed it last weekend but im a bit confused about how the timing works compared to WSJT-X. like with FT8 everything is locked to the 15 second cycles and you cant really deviate but JS8Call seems more freeform? i tried calling CQ for like 20 minutes on 14.078 and got nothing, not sure if i was doing something wrong or if the band was just dead or if nobody monitors that freq.

also wondering if the SNR sensitivity on JS8Call is anywhere close to FT8. i know FT8 can decode stuff way down in the noise like -20dB or whatever and thats half the reason it works so well on marginal conditions. does JS8Call get close to that or is it more like PSK31 territory in terms of what it needs to work. been running 100w into a trapped vertical if that matters

  • Replies 1
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah JS8Call is definitely more freeform, thats kind of the whole point of it. its based on FT8 encoding but the way it handles messaging is asynchronous so you dont have to be on at the same time as the other station which is a cool concept. the sensitivity is decent but not quite FT8 levels, i want to say its something like -24dB for FT8 vs maybe -18 or so for JS8Call depending on speed setting. theres actually three speed modes, normal, fast, and turbo i think, and the slower ones get you better weak signal performance but its a tradeoff.

14.078 is the right freq but honestly activity is pretty sparse compared to the FT8 watering holes. i tend to have better luck on 40m in the evenings, 7.078 i think is the standard spot. stick with it though because when you do get a contact its a lot more satisfying than the usual 73 and done you get on FT8

I had the same feeling about FT8 honestly, feels automated after a while. I went back to RTTY for contesting because at least you're typing stuff yourself even if it's still kind of a macro fest. PSK31 on 14.070 used to be where all the ragchewing happened but that seems pretty quiet these days, at least on my end. might be a time of day thing but i dunno it feels like everyone just moved to FT8 and stayed there

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