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 203
SN 101
A 5
K 0 Quiet
X-Ray C5.0
Wind 319.6 km/s
Aurora 1
Updated 22:00 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 — am I missing something

 Loading...

so ive been running FT8 for about a year and a half now and i get it, it does what it does, contact logged, move on. but lately ive been trying JS8Call because i actually want to talk to people not just exchange grid squares and signal reports and then never hear from them again.

problem is i feel like im missing something with JS8Call. the timing windows confuse me a little, like sometimes i see a station calling CQ and i reply and then nothing, and i cant tell if they heard me or just moved on or what. also not sure if im supposed to be watching the waterfall the same way i do in WSJT-X or if its a completely different workflow. my signal reports look fine, im running about 50w into a dipole up maybe 35 feet, works fine for FT8 so i dont think its an antenna issue.

also while im at it — does anyone actually use PSK31 anymore? i fired up fldigi the other night and called CQ for like 45 minutes on 14.070 and heard exactly one station, a Brazilian guy who disappeared after two overs. feels like a ghost town compared to what it used to be. not complaining just wondering if thats everyones experience or if im on at the wrong time.

  • Replies 1
  • Views 7
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

yeah JS8Call is a different beast, the workflow is more like actual keyboard to keyboard chat so you kinda have to get out of the FT8 mindset where everything is automated. one thing that trips people up is that JS8Call has multiple speed modes, normal slow fast and turbo i think, and if you're not on the same speed as the other station you'll see their signal but the decode wont work right. worth checking what mode the other guy is running before you reply.

as for PSK31, honestly yeah it's pretty quiet these days. 40m seems better than 20m for finding activity, at least in my experience, but even then you're not going to find the wall to wall signals we had like 10-15 years ago. FT8 ate everything's lunch basically. i still fire up RTTY during contests and that's still pretty active but outside of contests it's sparse too.

the JS8Call thing with no response might just be propagation timing, ive had that happen a lot where i can see someone fine for a few minutes and then the band shifts and they're gone before the QSO gets anywhere. also some operators set JS8Call to only respond to directed messages not CQ replies so that could be part of it. i dunno i find it frustrating sometimes too but when it works and you actually get a real back and forth going it's way more satisfying than FT8 ever felt to me personally

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.