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 C2.6
Wind 419.2 km/s
Aurora 2
Updated 05: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

Sarah Wilson13

Members
  • Joined

  • Last visited

Everything posted by Sarah Wilson13

  1. so ive been licensed about 8 months now and i still get kind of confused about when youre supposed to use the NATO phonetics versus just saying the letter normally. like if someone asks me to confirm a callsign do i always spell it out phonetically or is that just for when conditions are bad? i was on a local 2m repeater the other day and said my call just normally and then the net control asked me to say it again using phonetics and i felt kind of dumb but also wasnt sure if that was just a net control preference thing or like an actual rule also sometimes i hear people using weird phonetics that arent the standard ones, like i heard someone say "sugar" for S the other day and i thought that was just wrong but maybe im the one whos wrong? basically just trying to figure out if theres a correct way to do this or if its more of a situational thing
  2. Oh man yeah this is basically a rite of passage, everybody fumbles their first few check-ins. Dont even worry about it. The thing about saying your callsign too fast is super common, i still catch myself doing it when i get nervous and ive been licensed 11 years now. The basic flow on most directed nets is pretty simple once it clicks — net control calls for check-ins, you give your callsign phonetically at least the first time, they acknowledge you, and then when they come back around to you they'll ask if you have traffic or announcements. "Nothing further" or just "no traffic" is totally fine and most people use that most of the time. You're not obligated to say anything profound every week. As for asking net control questions during the net, id save it for after unless its something that directly affects your participation right then. Most net controls are juggling a lot and mid-net questions can kind of throw off the flow. After the net closes just key up and ask, most of them are happy to help a new op and honestly they probably remember being in your shoes. Your net control might even have a quick reference card or something they can email you.
  3. the path you're using is fine, WIDE1-1,WIDE2-1 is basically the default everyone uses. 5 watts to a decent mag mount should be workable for mobile. couple things worth checking though — first, what's your SmartBeaconing set to if you're using it? if you're mostly parked or moving slowly the beacon interval can stretch out way longer than you'd expect and it kinda looks like gaps on the map even when the radio is technically working. second thing, and this is the annoying one, aprs.fi only shows the last position it received from an igate, it doesnt show every digi hop. so if a digi is hitting your packet but no igate is picking it up downstream you're basically invisible. the three igates you mentioned, do you know if they're actually RF-to-internet or just internet-only? a lot of what shows up on the igate list is receive-only and if they're not running RF input you're not getting gated. worth cross checking against aprs.is directly or using findu.com raw packets to see what's actually being heard.
  4. so i finally did my first WWFF activation last weekend at a local nature reserve about 45 minutes from home. ive been eyeing it for a while since it popped up on the WWFF directory as an unactivated reference here in my country. took my FT-891 and a linked dipole up a little hill inside the reserve and set up near the trailhead where i had decent clearance. managed to get 47 QSOs over about 3 hours which i was pretty happy with for a first go, mostly 40m with a bit of 20m near the end when the band opened up nicely. spotted myself on the WWFF cluster and that definitely helped the pile get going. logged everything in HAMRS which i know some people have issues with but worked fine for me. my question is about submitting the log afterwards. i uploaded to WWFF Logsearch but im not sure if i did it right because it says the reference is still showing as unactivated? i waited like 3 days. do i need to do something else or just wait longer? also wondering if theres anything special about the ADIF tags i should be checking before i upload.
  5. had almost the exact same problem last year. turned out my APRS symbol was set to something the software didn't like and iGates in my area were just not forwarding it for some reason — never fully figured that part out honestly. but the bigger issue for me was that i was too far from an iGate and the two digipeaters between me and the nearest one were both kind of flaky. you can check coverage on aprs.fi by looking at who's actually hitting your area, zoom in and see if theres even an active iGate within a hop or two of you. also try sending a message to SMSGTE or something just to see if messaging works independent of position beacons, sometimes that helps narrow down whats broken.
  6. been trying to work 7x0dx for the past 2 hours and just cant break through. im running 100w to a dipole about 30ft up, hearing them solid 59+ but they just dont hear me. tried calling exactly on their freq, tried splitting up 5-10, even waited for the pile to die down but no luck anyone else having better luck? starting to think maybe my antenna has an issue but it seems to work fine on other contacts. maybe im just not loud enough for this kind of pile
  7. Don't check the "Secondary UDP Server" or "N1MM Logger+ Broadcasts" box in WSJT-X - that's not used when WSJT-X runs from inside N1MM+. Also verify the WSJT Decode List window opens automatically when you launch WSJT-X from N1MM+.
  8. For best conditions, solar flux should remain above about 150 for a few days with K index below 2. When these conditions have been met, check out the bands and expect some good DX to be about! Time of day matters a lot too - try again during peak hours for your target area.

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.