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 128
SN 73
A 6
K 1 Quiet
X-Ray C2.2
Wind 403.6 km/s
Aurora 2
Updated 23: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

James Anderson

Members
  • Joined

  • Last visited

  1. totally been there, the baofeng menu stuff is confusing at first but you'll get it. so the CTCSS tone you want to set is the transmit tone, sometimes labeled T-CTCS or just TXtone depending on the firmware. the receive tone (R-CTCS) you can usually just leave off or set to the same thing, it doesnt really matter much for getting into the repeater, that's just for your radio to only open its squelch when it hears that tone coming back from the repeater which honestly isnt that useful for most people. as for the courtesy tone thing, when you're done talking on a linked or most standard repeaters youll hear a little beep or series of beeps after you unkey — that's the repeater telling everyone the channel is clear and it's okay for someone else to key up. just wait for that before you start talking. jumping in before it comes up is one of those things that can annoy the regulars even if you dont mean anything by it. keep your transmissions reasonably short too especially if you dont know how busy the repeater is. good luck, once you get that tone sorted you'll be on the air in no time.
  2. so ive been at this for a few months now and i feel like im completely stuck at around 5wpm. i can copy most characters fine when they come in slow but the second someone bumps it up even a little i just fall apart and start writing dashes and dots instead of letters which totally defeats the purpose i've been using the koch method app on my phone and doing maybe 20-30 minutes a day but honestly i wonder if im doing something wrong because i dont feel like ive moved at all in like 6 weeks. my goal is to get to 20wpm eventually, i know thats a ways off but even getting to 10 would feel like progress at this point. anyone been through this and have advice that actually worked for them?
  3. yeah this rabbit hole is deep and i fell into it hard when i first got my 7300 too. honest answer is mic placement makes a bigger difference than most people want to admit — like embarrassingly so. if you're too close to the PR-40 you're going to get proximity effect piling up the bass and no amount of EQ fixes that cleanly, you're just compensating for a problem you created. try backing off maybe 6-8 inches and speaking across the mic rather than directly into it and see if that changes your baseline before you touch another setting. on the compression thing, the guys who say never use it are usually thinking about the bad old days with hardware compressors cranked way up. a little speech processing on the 7300, maybe 2-4 on that internal processer, genuinely does help cut through when the band is rough. i keep mine at 3 and my received audio reports got noticeably better. you dont need to slam it. also worth asking a buddy to actually record your signal with SDR# or something on the other end so you can hear what you actually sound like vs relying on signal reports which are honestly pretty useless for audio quality feedback
  4. yeah jump in on CQ WW, worst case you make a few contacts and have fun. the bands are absolutely wall to wall with signals that weekend, 15 and 20 meters especially. with a dipole you'll still work a ton of DX, propagation tends to cooperate in late october. one thing i'd say — download N1MM or Log4OM before the contest, not during. trying to figure out logging software in the middle of a pileup is not a great time. give yourself a few days to just poke around the interface and do a fake log entry or two.
  5. I went full DIY about two years ago after messing with a couple of the turnkey platforms. I use a combination of flrig, mumble for audio, and a small NUC running ubuntu at the remote end. Took a solid weekend to get right and there was some stuff with the firewall at the remote QTH that drove me nuts but once it was dialed in its been rock solid. Total control, no dependency on anyones servers going up or down. That said I wouldnt necessarily recommend it to someone who isnt comfortable with linux and networking. RemoteHams really does lower the barrier a lot. If you're mainly doing casual ops and the occasional net check-in it's probably fine. The internet linking angle is interesting too if you want to tie in something like EchoLink or IRLP for VHF/UHF remote access but thats kind of a different rabbit hole entirely, I spent way too long getting an Allstar node talking to my remote HF setup and im still not sure it was worth it.
  6. oh man i didnt even know WWFF was a thing until like three months ago and now ive done four activations lol. the pile ups are so much fun, way more chaotic than i expected. people calling from all over the place. do you find hunters are pretty patient when youre still figuring out your operating rhythm? i had one guy get a bit grumpy at me for not sending signal reports fast enough but most people are really nice about it.
  7. honestly in my experience the vertical won out for 40m regional work, i had almost the same setup as you a few years back and built a quarter wave vertical with about 20 radials and the difference on the closer in contacts was noticeable. not night and day but enough that i kept the vertical and only put the dipole back up when i want to work europe in the evenings. that said 8 radials is where it starts getting marginal imo. i wouldnt bother going through all the construction hassle for 8 radials, either commit to doing it right or stick with the dipole and accept its what it is.
  8. So ive been meaning to do this for like two years and I finally sat down last weekend and started actually building out a go-kit instead of just thinking about it. Got a Pelican 1510 case, threw in my FT-857D, a SignaLink for digital, and I've got a little power distribution block in there with anderson powerpole connectors throughout. Packed a coil of RG-8X, my buddipole, and a spare mic. Here's the thing though — I feel like im forgetting something obvious. Like every time I think I have it dialed in I remember something else. Last week I realized I hadnt included any logging supplies, not even a notepad. So now theres a waterproof notebook and a couple pens rubber banded to the inside lid. What did you guys find you kept forgetting or wishing you had when you actually deployed? Especially curious if anyone does ARES or SKYWARN activations regularly and what your kit looks like after a few real deployments vs what you thought you needed when you first built it.
  9. congrats man, that waiting period is brutal, i think mine took about 3 days to show up and i checked constantly. once it posts just jump on a local repeater and say hi, most people are friendly and will ragchew with a new call. dont be nervous about keying up, worst that happens is nobody responds and you try again later. the baofeng will be fine to start, just program it right and youll be good. have fun with it
  10. yeah the gateway selection thing trips a lot of people up at first. the software does show you nearby gateways based on a distance sort but that doesnt mean those are the ones actually hearable on your current band and conditions. what i do is use the propagation beacon data or just look at the winlink maps on the website to see which gateways have had recent activity on 40m — if a gateway shows a connection in the last 30 minutes or so theres a decent chance conditions are workable. your [email protected] address is totally fine for standard use, thats what everyone uses. where message handling gets more interesting is if you want to set up hybrid network stuff or do peer to peer sessions without going through the CMS at all — like for EMCOMM drills where you might be operating in a degraded infrastructure scenario. but for just getting started the CMS-routed path is fine and reliable once you get the RF side sorted. i'd check your vara modem settings too, the soundcard levels matter a lot more than people expect, too hot and you're just splattering noise at the gateway
  11. so ive been running N1MM for probably 4 or 5 years now and its been fine for contests, does everything i need for sweepstakes and the CQ WW stuff, but lately ive been hearing a lot about Log4OM and people saying its better for everyday DX logging and the integration with stuff like WSJT-X is cleaner or something. my current setup is that i use N1MM during contests and then i sort of manually import everything into another log after, which is honestly a pain and i keep putting off doing it so now i have like 3 contests worth of QSOs sitting unmerged. the thing is i dont really want to blow up a workflow thats working right before contest season kicks into high gear again. i messed around with Log4OM a little bit last winter and it seemed nice but i couldnt figure out how to get the WSJT-X integration set up properly, the UDP stuff kept not connecting and i gave up. anybody running both or made the switch? is there actually a reason to bother or am i just chasing something because its shiny
  12. yeah that gap between exercises and real activations is very real. ive been doing ARES stuff for about 12 years now and been through maybe 8 or 9 actual activations, everything from public service events that turned into something bigger to a couple genuine disaster responses. the biggest thing i noticed early on was that training tends to assume everyone shows up with the right gear, the right programming, and actually remembers what they learned. real world, none of those things are guaranteed. one thing our group started doing was unannounced go-kit checks during meetings — just have someone volunteer to dump their kit out and we all look at it together. no shame in it, just makes people actually maintain their equipment. and we added a short radio check at the start of every monthly net specifically to catch programming issues before they matter. sounds basic but it cut down a lot of the on-the-fly chaos we used to see. the ICS forms thing is tougher, honestly the only fix ive seen work is making people actually fill them out during exercises, not just talk about them.
  13. im kind of in the same boat as you, been at it since last winter with an Arrow and a 705. what actually made a big difference for me was setting up two separate VFOs and just pre-loading the center frequencies with rough doppler offsets before the pass starts, like i know where im going to be at AOS, mid pass, and near LOS so i just step through manually at those points instead of trying to continuously tune. its not perfect but its way less chaotic than chasing it in real time. gpredict with hamlib is on my list to get working properly but i havent had time to sit down and configure it right. heard it can be a pain with certain rigs depending on the CAT setup.
  14. went last year, honestly it was smaller than i remembered but still fun. the outdoor tables are still there and i found some decent coax and a few connectors, nothing crazy. indoor stuff is mostly club tables and a couple commercial vendors. worth the trip if you're nearby but maybe not a 90 min drive unless you just like the atmosphere, which i do personally
  15. Periodically update your Go-Kit components to incorporate newer, more efficient equipment and supplies. Don't just check - also review and update. I keep a maintenance log in my kit with dates and what I found. It's saved me from repeating the same mistakes twice.

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

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.