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 B9.3
Wind 401.6 km/s
Aurora 2
Updated 00: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

Paul Anderson

Members
  • Joined

  • Last visited

Everything posted by Paul Anderson

  1. not a dumb question at all, part 97 really is written in a way that feels like it was designed to confuse people. for SSB on 40 meters as a general you're fine on everything from 7.175 to 7.300 MHz, the lower portion below that is still CW/digital only for generals so just watch where you're tuning. the ARRL band plan is honestly way easier to read than the FCC doc for day to day operating. the business thing is pretty clear once you get the gist — basically you cant use ham radio for anything that would benefit you financially or that you could otherwise do on a normal commercial service. so calling your coworker to say hey move the meeting to 3pm because your phone is dead, thats probably fine in an emergency but doing it regularly as like a workflow tool, that crosses the line. the rule is there because the spectrum is licensed for personal and public benefit stuff, not so companies get free comms. third party traffic is its own rabbit hole but basically it just means someone unlicensed is using your station to communicate, and there are rules about which countries you can do that with. most of it wont come up in normal operating.
  2. so ive been licensed for about 8 months now and i still feel kind of awkward about when to actually use phonetics. like on 2m FM repeaters most people just say their callsign normally and nobody seems to use NATO phonetics at all, but then i get on HF and people are going full Alpha Bravo Charlie on everything. is there like an actual rule about this or is it just a culture thing depending on what band youre on. i dont want to sound like im overdoing it on the local repeater but i also dont want to sound like i dont know what im doing on HF. my call has a W and a couple letters that sound similar so maybe it matters more for me idk
  3. so ive been trying to learn morse code for about 3 months now and im basically stuck at 5wpm. i can copy at that speed pretty reliably but the moment i push it up to even 7 or 8 it all falls apart and i just hear noise. been using the LC app and doing about 20 minutes a day most days. i know people say just push through but that doesnt really explain HOW to push through you know? my goal is eventually 20wpm so i can actually get on the air and have a real QSO without embarrassing myself. read somewhere about the Farnsworth method but im not totally sure im doing it right. like my letter spacing is set slow but the characters themselves are at 20wpm, is that actually how its supposed to work? feels weird to copy dit-dah-dit at full speed and then wait forever for the next letter anyway if anyone has gone through this process and actually made it to 20wpm id love to hear what worked for you. getting a little frustrated honestly
  4. honestly the baofeng vs yaesu/kenwood/icom debate never really ends lol. i started with a uv-5r and it got me on the air which was the whole point, but the menu system is a nightmare and the receive audio is kinda mediocre. if you can stretch to like 100-130 range the yaesu ft-65r is a solid step up and way easier to program. dual band does matter more than you'd think once you start finding out that some repeaters in your area are on 220 or you want to monitor 70cm while transmitting on 2m for hiking specifically id also look at what kind of battery life you'd actually get. the chirp software makes programming any of these easier once you figure it out, dont let that part scare you off
  5. Just got my General and planning to work some CW on 20M. I understand the basics of Q-codes but get confused when I hear them used as nouns versus statements. Like when someone says "lots of QRM tonight" versus "QRM?" - are both correct? What are the common Q-codes every CW operator should know first? Also, do voice ops use these much or mainly CW? Thanks for any advice!
  6. yeah find a local club that does license classes, a lot of them are free or close to it and the elmers there will walk you through everything. ARRL has a club finder on their site. some clubs even do the exam session right after the class which is handy. one thing i tell people is dont overthink the regulations questions, just read them carefully because the wording is usually the whole trick. and bring a calculator even if you think you wont need it, a few of the tech questions have simple math and it saves you from doing it in your head when youre nervous.
  7. yeah i had the same confusion when i started. what helped me was thinking about it this way -- B and D and E and V all sound pretty similar especially through a noisy repeater or over a pile up, so phonetics just removes the ambiguity. Bravo vs Delta vs Echo vs Victor, no confusion. i think the unwritten rule most people follow is: always go phonetic when exchanging callsigns for the first time in a QSO, and then after that youve established contact and the signal is solid you can relax a bit. but honestly on nets, especially formal ones, the net control usually wants phonetics every time you ID. different nets have different customs too which adds to the confusion lol
  8. yeah what he said about paper notes is no joke, i learned that the hard way at a drill a few years back when the laptop the served operator was using died and suddenly nobody had a backup of anything. now i always keep a paper log going no matter what. also if the EOC uses ICS 214 forms or any specific message forms ask your EC ahead of time so you can print a few and get familiar with them before you show up — it looks really good when you already know the paperwork and it honestly just makes the job easier. have fun with it, drills are low stakes but you learn a ton
  9. 3 miles off sounds like it could be a datum issue honestly. probably not but worth at least ruling out. more likely though is the manual position override thing the other guy mentioned, i did that exact thing when i first set mine up and spent an afternoon confused about why i was apparently operating from a parking lot two towns over.
  10. the clone HackRF situation is actually worse than hit or miss these days, seen a few people get ones that couldnt even do a proper loopback test and the TX power was way off spec. if you go that route just buy from Great Scott Gadgets directly or a known reseller but yeah if youre not transmitting the RSPdx makes more sense for your use case, i mostly just wanted to throw in the clone warning cause i see people get burned on that regularly. 630m is fun if you can ever get a suitable antenna together, theres more activity on that band than most people expect
  11. so ive been running FT8 for about two years now mostly on 20m and 40m and its great for what it is, racking up contacts and all that, but lately ive been reading about JS8Call and the whole store-and-forward mesh relay thing and im honestly not sure if its solving a problem i have or just a cool idea in theory my setup is nothing special, IC-7300 into a fan dipole up about 30 feet, running WSJT-X with a SignaLink and i get decent results even when the band sounds completely dead. but JS8Call seems like it requires more of a active community presence for it to actually be useful, like if nobody is on in your region its kind of pointless right? at least with FT8 theres always somebody in the log i also messed around with PSK31 back in the day and honestly kind of miss it, felt more like actually talking to someone even though the SNR performance is nowhere near FT8. anyway curious if anyone here actually uses JS8Call regularly or if its mostly just guys experimenting and then going back to FT8
  12. honest answer is the difficulty jump is real but its not insurmountable. the general felt like memorization with a little math sprinkled in, the extra actually expects you to understand why things work, at least enough to answer questions about it. stuff like the reactance formulas, the filter response curves, transmission line theory, it comes up in a way where just memorizing the answer sometimes isnt enough because the pool is big enough they can ask it from different angles. that said i studied for about 6 weeks using the ARRL extra manual and hamstudy.org and passed on the first try. what actually surprised me was how much the studying itself changed the way i think about my station. like i never really understood why my antenna tuner was doing what it was doing until i went through that material. so even if you dont care about the extra band segments, and yeah they do matter more than people admit especially on 75m and the low end of 40m where the DX tends to hang out, the knowledge itself is kind of worth it. the prestige thing is real too and theres nothing wrong with admitting that, callsign upgrade is nice if you go that route
  13. had almost exactly this happen on mine about a year ago. turned out to be a cold solder joint on the PA board near the bias transistor, not something you'd see just looking at it, had to actually probe around with the rig keyed up and watch for the dropout to find it. the tricky part is it only showed up when the board was at operating temp. what i'd do first is monitor the drain current on the finals while transmitting if you have a way to do that, either with the internal meters or an external shunt. if the current is collapsing at the same time as the power that points to the driver or bias circuit. if power drops but current stays up that's more of a filtering or impedance issue downstream. the 7300 does have a known thing where the RF board connector can develop intermittent contact but i think thats more of a receive issue than TX. honestly if you're not comfortable reflowing solder joints on SMD boards it might just be worth the service center trip, icom's authorized shops arent too bad on turnaround right now from what i hear.
  14. so ive been at this CW thing for about 4 months now and im stuck somewhere around 8-9wpm and it feels like a wall. when i first started i was using the G4FON trainer and just doing random characters for like 20 minutes a day and honestly the first couple months felt great, went from barely copying anything to being able to pick out words here and there. but now progress feels really slow and i dont know if im doing something wrong or if this is just how it goes. a buddy of mine who got his Extra back in the 80s says i should be doing Koch method and setting my character speed higher than my overall speed — like 20wpm characters but only 5wpm effective speed or whatever that's called. i tried it for a week and it was honestly really frustrating, felt like i was starting over from scratch. did anyone else find that transition rough also i keep second guessing whether i should just jump on the air at my current speed and deal with the embarrassment or keep practicing offline until im more solid. i want to eventually do some QRP /p stuff and actually hold real contacts, not just exchange signal reports.

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.