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 433.7 km/s
Aurora 2
Updated 23: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

Thomas White

Members
  • Joined

  • Last visited

Everything posted by Thomas White

  1. i was in the same spot last year and kept putting it off. finally just signed up for a session to force myself to study lol. the transmission line questions tripped me up at first but once you get the SWR and reflection coefficient stuff it starts to click. passed with a few to spare. the extra band segments honestly i havent even used that much yet but it feels nice knowing i can if i want to. also full privileges means if you ever get into anything weird like some of the narrower CW allocations or experimental stuff its all open
  2. hamstudy is honestly all you need for most people, especially if you're the kind of person who can just grind through flashcards. the way it tracks which questions you're getting wrong and keeps drilling those is pretty solid. I passed using pretty much just that site over like two weeks of casual studying maybe 20-30 minutes a night. that said I do think understanding the material helps you retain it better even if you're not strictly required to. the electrical stuff like ohms law and the basic circuit questions, once you just get the concepts down the answers kind of make sense on their own instead of just being random letters to memorize. the rules and regs section is where a lot of people just straight up memorize though because some of that is just "what frequency range is this" type stuff and theres not really a deeper why to it the ARRL book is fine but i borrowed it from my library and honestly only read like three chapters before I just went back to the website. depends on how you learn I guess
  3. so this has been driving me nuts for about two weeks now. my 7300 started throwing high SWR warnings on every band, like 3:1 or worse, but when i slap a dummy load on the antenna port it reads flat, 1:1 no problem. transmit power looks normal, receive seems fine too. the antenna system itself checks out — ran a VNA sweep on everything from the feedpoint and nothing changed out there. at first i thought maybe the internal SWR bridge went wonky but im not sure how to even start diagnosing that without schematics. does anyone know if theres a known failure point in the SWR sensing circuit on these radios? ive seen mentions of a directional coupler section somewhere in the RF board but i cant find anything specific. the radio is about 4 years old, out of warranty obviously, and i dont really want to ship it to Icom unless i absolutely have to. happy to get in there with a scope if someone can point me in the right direction
  4. yeah the 30 day thing used to be real but they got rid of that requirement a while back, you can apply for a vanity pretty much right after your license posts to the database. what you do is go into the ULS filing system, log in with your FCC registration number and password, and file a Form 605 — theres an option in there specifically for vanity callsign request as for how it works, you can list up to 25 calls in order of preference and the system processes all applications that come in during the same filing window together. so if two people both apply for the same call in the same batch it goes to whoever has licensing priority — like an extra class can bump a tech for the same call, and then within the same license class I believe it goes to whoever filed first, though honestly that part has tripped me up before too. if your first choice is taken your second choice gets considered and so on down the list the windows close and process on a set schedule, I think its still every couple weeks or so. you can check the AE7Q website, that guy has an amazing tool for looking up what calls are available in your district and tracking application status. made the whole thing way less confusing for me when I went through it a few years back
  5. yeah 10m has been wild lately, you picked a good time to get into HF if you're newer to it. we're sitting pretty close to solar cycle 25 peak right now and honestly the flux has been all over the place — you'll see it jump up then drop back down within a day or two depending on what the sun is doing with active regions rotating into view. for the indices — the simple version is SFI above 150 and you start getting excited about 10 and 12m, K index you want low, like 2 or under ideally, anything above 4 and the higher bands get noisy and the aurora starts eating your signal on paths through the poles. A index is kind of a lagging average of the K so less useful for real time. i mostly just check DXmaps or the cluster and if i see spots on 10m from somewhere interesting i just go listen, that honestly tells you more than staring at numbers. those short openings are totally normal btw, especially on F2 propagation — it can be spectacular for a window and then just snap shut. glad you caught it
  6. so ive been going back and forth on this for like two months now and i need someone to just tell me what to do basically. currently running a random wire out to a tree with a 9:1 unun and its fine but i want something more dedicated for 40m because thats where i spend most of my time these days. the lot isnt huge, maybe 80 feet usable in one direction and i have a chimney on the south end of the house. i was thinking a half wave dipole fed with ladder line into a tuner but my neighbor directly to the east has a two story house and im not sure how much that kills the pattern. the other option is just throwing up a quarter wave vertical with some radials and not worrying about it. i know the textbook answer is dipole wins if you have the space and the height, but my dipole would probably only get to about 25 feet at the apex which feels kinda low for 40. the vertical would let me work more directions without worrying about the pattern being squished by surrounding structures. anyway if anyone has actually compared these in a suburban backyard situation id love to hear real world impressions not just antenna modeling theory
  7. so ive been doing SS phone and CW for about 6 years now and always ran single radio. finally built out a proper SO2R setup this past year, two K3s, a TopTen bandmaster, separate antennas for each radio with decent isolation, the whole thing. spent probably 3 weekends just getting the intermod and RFI under control enough to actually use both radios without one wiping out the other. ran my first real SO2R contest last month during a state QSO party and honestly i'm not sure the rate improvement justified the mental overhead. like yeah i was probably 15-20% higher on contacts per hour during the good runs but i kept fat-fingering the wrong radio, sending on the wrong VFO, that kind of thing. felt like i was flying the airplane AND reading the checklist at the same time. people who have been doing SO2R for a while — does it just click eventually or is there something specific about how you train yourself to manage the second radio without it eating your focus on the run frequency. i'm using N1MM and have the SO2R stuff configured but im wondering if my keyer macros and the way i have my footswitch set up is just not optimized. open to hearing how other people have their workflow set up.
  8. so i've been putting together a go-kit situation for the past few months and honestly the power side of things is where i keep second guessing myself. right now i have a bioenno 30ah lifepo4 that i pair with a 100w panel when the sun cooperates but i keep running into the same problem where i'm burning through it faster than expected, especially if i'm running the ic-7300 at anywhere near full power for extended periods. the antenna situation is a bit of a mess too. i've been using a homebrew EFHW with a 49:1 unun and it tunes up fine on 40 and 20 but i've never been totally confident the feedpoint impedance is actually where it needs to be, like i wonder sometimes if im just masking a mismatch with the atu and wasting power. thinking about picking up a chameleon or something similar but those prices are hard to swallow when you know you can build something for $30 in parts. anyway the generator question is the real one i wanted to ask about. for longer activations or emcomm type stuff where i might need to run for 12+ hours, whats the minimum size generator you'd consider practical? i've been looking at the eu2200i because its quiet enough to not be a nightmare but i keep wondering if theres a better option in that range. dont want to lug around more than i have to.
  9. I just did mine about 3 months ago so I can say from recent experience, dont overthink the electrical theory stuff if it trips you up at first. just keep doing practice tests and eventually the answers start sticking even if you dont fully understand why. I probably did 200+ practice questions total and felt really ready by test day. passed with only 2 wrong which surprised me honestly
  10. the battleborn is fine for 8 hours if you're not running 100w the whole time, i run a similar setup with a 100ah lifepo4 and an 857D on field day type stuff. one thing i'd add is bring a decent clamp meter so you can actually watch your current draw in real time and not just guess. makes a huge difference in knowing when to throttle back the power or switch to the generator before you're in trouble. also on the antenna front — have you looked at a vertical like a Wolf River Coils setup on a drive-on mount? parking lot deployment, no trees, that would actually be pretty slick and quick to get on the air. i've seen guys set that up in under 10 minutes. just a thought.
  11. made almost exactly that swap about two years ago, went from a 590 to the 7300 and honestly it took me a few weeks to stop second-guessing myself. the waterfall alone is worth it for how i operate — i do a lot of casual band scanning and being able to see whats happening without a separate sdr is just way more convenient. the integration is tight, it doesnt feel like an afterthought the way a dongle setup can. rx wise i think theyre pretty comparable in real world use. on paper the kenwood has some advantages in certain blocking situations but sitting in my shack working the pile-ups on 40 i cant say i noticed a meaningful difference. where the icom wins for me is just the overall feel of the thing, the interface is intuitive once you get used to it and the touchscreen actually works well unlike some radios that have screens that feel like they were bolted on as an afterthought. if your g5rv is only at 30 feet the antenna is probably limiting you more than either radio anyway, just saying.
  12. honestly its more of a situational thing than a hard rule. on a clear local repeater with people you know, nobody really cares, your call just needs to be identifiable. but on HF especially when conditions are sketchy or youre working someone far away, phonetics genuinely help because a B and a D can sound identical in noise. NATO phonetics exist for exactly that reason — Bravo versus Delta, no confusion. i'd say get comfortable with the standard NATO set first because if you start making up your own like some guys do it just causes more confusion not less. the FCC doesnt actually require phonetics, just that your call is intelligible, so theres no rule youre breaking either way
  13. yeah the voice discipline thing is so real. we had the same issue at ours a couple years back, people just naturally want to explain everything in long sentences when you really need short formatted traffic. what helped us was doing a short 20 minute tabletop before the actual exercise just to run through message format until it felt a bit more automatic. not perfect but it reduced the chatter noticeably during the real drill. on the simplex getting stepped on — honestly i'd recommend building two or three fallback freqs into the plan and making sure everyone has them written down physically, not just in their phone or whatever. we learned that the hard way during a winter storm actual where one of our guys couldn't pull up the backup freq because his phone battery died. paper wins every time in those situations. for after action reviews we started assigning someone specifically to take notes during the exercise itself, not just after. that way you're capturing real time confusion as it happens rather than trying to remember it all afterward. makes the debrief way more useful.
  14. nice work getting a qso on the first real try tbh. i fumbled around for like three passes before i actually completed anything. one thing i'd add — make sure your TLEs in gpredict are fresh, like updated within the last few days fresh. i had a situation where i was pointing the wrong direction entirely because i hadn't refreshed in a couple weeks and the element set was way off. satellites drift enough that stale TLEs will have you looking in completely the wrong part of the sky especially toward the end of a pass. also re: the 817 for downlink, i used one for a while and found the AGC behavior kind of annoying when signals were fading in and out on a sat pass. might be worth digging into the AGC settings if you haven't already.
  15. so this has been driving me nuts for a couple weeks now. picked up a used 7300 from a guy at the club swap meet, seemed fine when i tested it briefly at his table, got home and after maybe 20 minutes of actual use on 40m the output just dropped to almost nothing. like im getting maybe 2-3 watts on a good day when it should be pushing 100. the weird thing is it doesnt trip the protection or throw any error on the display. SWR looks fine on a dummy load. driver stage seems okay-ish based on what im seeing at the rf board but honestly im not super confident in my diagnosis there. i pulled the lid and nothing looks visibly burned or obviously wrong which i guess is either good or bad depending. before i go ordering finals and regretting it, has anyone seen this specific symptom on the 7300 where it just quietly loses output without actually faulting? wondering if its a bias issue or maybe the ALC is doing something weird. i have a scope i can use but i want to make sure im probing in the right spots before i poke around in there.
  16. not a dumb question at all, this trips up a lot of new generals. so the actual FCC allocation for 40m general class SSB starts at 7.175 MHz and goes up to 7.300. below that down to 7.025 is CW only for general, and technicians dont get anything on 40 HF at all except some CW privileges i think. the band edge thing you mentioned is real. your transmitted signal has to stay within the allocation, not just your carrier. so if you're on USB and your carrier is at 7.300 you've got sideband energy going above that which puts you outside the band. most people just stay at 7.299 or a little lower to be safe. some rigs have a setting that warns you when youre close to a band edge which is handy. the band plan stuff like where digital modes typically live vs phone vs cw is kind of a gentleman's agreement thing, not actually law. the ARRL publishes a band plan that most people follow but strictly speaking nobody's going to lose their license for doing ssb at 7.080 even though that's usually digital territory. people will probably complain on the air though lol
  17. so I've been licensed for about 6 years now mostly doing VHF stuff and some HF SSB but I always told myself I'd eventually learn morse and I keep putting it off. finally ordered a cheap paddle off amazon (yeah I know, I know) and I've been messing around with my old FT-857 using its built in keyer and honestly I'm kind of lost. the paddle itself feels a little mushy and the contacts aren't super crisp but I'm not sure if that's the paddle or if I'm just bad at this — probably both. I've been using lcwo.net for code practice which everyone seems to recommend and I'm working through the Koch method starting slow around 13wpm character speed. my question is mainly about the keyer side of things though. what mode should I have the keyer set to, mode A or mode B, and does it actually matter when you're this slow and still learning? also is there a point where I should get a real paddle before I ingrain bad habits or can I stick with the cheap one for a while? any tips appreciated, I feel like I'm starting completely from scratch which I guess I am
  18. the defaults are mostly fine to start but there's a few things worth digging into. the NR and NB settings are set pretty conservatively out of the box, and if you're on a noisy suburban lot like me you might want to play with the noise blanker level depending on what's causing the noise. also check your RF gain — a lot of people leave it maxed and then wonder why the band sounds rough. one thing i always do on a new 7300 is go into the scope settings and set the waterfall speed and reference level to something that makes sense for your noise floor. takes like 5 minutes and makes the whole display way more readable. other than that yeah the defaults are decent, icom did a reasonable job there.
  19. had something similar on an older 746pro and it turned out to be the power supply not the radio. was a cheap switching supply and when the rig warmed up and pulled a bit more current the voltage was sagging just enough to cause weirdness. probably not your issue if youre on a good supply but worth throwing a meter on the DC input while youre transmitting and see if it dips
  20. okay so the baofeng thing is kind of both actually. they're not terrible radios for the price, ive had a UV-5R sitting in a drawer for years and it still works fine. the issue is the programming software is a pain, the manual is basically useless, and the receive can be a little deaf compared to the japanese radios. but for hitting a local repeater and talking to your buddy a few miles out? it'll do that just fine, especially starting out. that said if you can stretch to like $130-140, the Yaesu FT-65 is just... nicer. feels better in the hand, the menu makes actual sense, audio is clearer. its dual band VHF/UHF which you'll want. i gave one to my daughter when she got her ticket and she had zero issues figuring it out without me hovering over her shoulder. if budget is tight go baofeng and dont feel bad about it, lots of people start there. if you can swing a little more the yaesu is worth it imo.
  21. QRZ is the one that tripped me up forever because i kept thinking it meant the same as QSL. took me an embarrassing amount of time to figure out why people were saying QRZ after already making contact lol. also worth knowing QSB which is signal fading, youll hear that a lot on 40m in the evenings when signals are going up and down. and QTH is your location. theres honestly like a hundred of them officially but maybe 20 that actually come up in regular conversation so dont stress about memorizing the whole list right away
  22. ive been thinking about doing exactly this but i wasnt sure if QRP was worth it for someone who doesnt have a lot of antenna options. like i live in an apartment so my situation at home is kind of rough but a park activation seems doable. what was the battery situation like, did the 9v pack last the whole session?
  23. i asked basically this same question when i got my license last year lol. what i ended up doing was just keeping wsjt-x open on one monitor while i mess with other stuff. the qso automation thing bothered me at first too but honestly i've just accepted that FT8 is basically beacon mode with a logbook attached, which is fine for what it is. havent tried JS8Call yet but this thread is making me want to. does it use the same audio interface setup as WSJT-X or do you have to redo all the CAT stuff? my setup with the IC-7300 and a USB cable was pretty painless for FT8 but i dont want to break whats working
  24. the hum thing is almost certainly a ground loop or your power supply isn't filtered well enough. with DC receivers any ripple on the supply goes straight into the audio, its kind of brutal that way. try running it off a battery and see if the hum goes away — if it does thats your answer. also check that your AF gain pot is grounded at the same point as everything else, floating grounds in the audio section will mess you up every time. on the VFO drift, yeah NP0 caps are basically mandatory if you want anything stable. and the wax potting helps a lot, i use regular paraffin melted down. some guys use hot glue but i find that actually introduces more temp coefficient weirdness. the jfet buffer is a good idea regardless, it isolates the oscillator from load changes. i built a 40m DC receiver about 3 years ago and it drifted horribly until i added a MPF102 buffer stage, after that it settled down to maybe 50hz drift which is livable for casual listening.
  25. ha i did the exact same thing on my first transmission, totally blanked on my callsign and just said "uh over" like i was on a walkie talkie or something. the guy on the other end was super patient about it though. congrats on passing, 33/35 is solid especially if you didnt have any background in electronics. it gets way less awkward after the first few times i promise

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.