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 2 Quiet
X-Ray B6.7
Wind 382.9 km/s
Aurora 2
Updated 05: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

Maria Rodriguez

Members
  • Joined

  • Last visited

Everything posted by Maria Rodriguez

  1. nice, i did my first activation last spring and also kinda just winged it lol. one thing i learned the hard way is bring more water than you think you need especially if youre setting up and tearing down a few times trying to find a spot. also downloaded the SOTA spotter app afterwards and it makes a huge difference for getting chasers lined up before you even key up
  2. so ive been a general for about two years now and honestly i get by fine with the bands i have access to but lately ive been eyeing those extra portions on 20m and 40m especially during contests when everything seems to be packed into the general segments and theres always room down in the extra part of the band my question i guess is more about the exam itself — i remember the general had some theory on it that i kind of memorized my way through without really understanding it, and people keep telling me the extra is a whole different level. like is the math actually hard or is it more just a lot of terms to memorize? im decent with electronics but never took anything past high school physics so im a little intimidated by stuff like filter design and transmission line theory showing up on practice tests also does having an extra actually change how you operate day to day or is it mostly just for the extra band segments and the vanity call thing
  3. so ive been licensed about 2 years now and been doing mostly local stuff and some casual HF but recently got bit by the DX bug pretty bad. started logging contacts more seriously and realized i might actually have enough for a basic DXCC if i dig through my old logs. my question is about submitting for credit - do i need QSLs for every single contact or does LoTW count now for most of them? i know some entities are really hard to get a physical card from. also wondering about WAS vs DXCC - which one do people usually go after first? feels like WAS might be more achievable for me being in the midwest but i dont want to spend all my time on 40m ragchewing when i could be working DX. and WAZ i barely understand honestly, the zones thing confuses me a little. anyway any advice from people whove been through this process would be great, its a little overwhelming looking at the ARRL award pages
  4. so ive been licensed for about 8 months now and people keep telling me i should try a contest but honestly the whole thing feels overwhelming. like i sat down last november during CQ WW and just spun the dial for a while and everyone was going so fast i didnt even try to jump in. i have a technician ticket so i was mostly just listening on HF through a friend's rig anyway. i upgraded to general back in february though so now i at least have some HF privileges. i have a modest setup, just a Yaesu FT-710 and a wire dipole in the backyard. nothing fancy. im curious if something like ARRL Field Day would be a better starting point than CQ WW because it seems more... relaxed? or am i wrong about that. also someone mentioned SOTA to me but that seems like a completely different thing, is it competitive in the same way or more just for the activation points anyway if anyone has advice on what events to try first id appreciate it. dont want to show up to something and make a fool of myself on the air
  5. yeah i had almost the exact same issue when i first got my 7300, turns out i had the mic EQ set to something the previous owner had messed with and never reset. there's a passband tuning thing in there that can really narrow things down without you realizing it. just reset your TX EQ profile to flat and start from scratch, made a huge difference for me. took me like three weeks to figure that out which was embarrassing
  6. so ive been licensed for about a year now mostly just doing voice on 2m and some HF but i keep hearing people talk about CW and how its supposedly way better for weak signal stuff and dx and whatever. i got curious and figured id try learning it but i honestly have no idea where to begin. like do people just memorize the dots and dashes on a chart or is there some better way. i downloaded a couple apps and they all seem different and im not sure which approach is actually worth doing. one of my elmers told me to just listen to a lot of it and my brain would figure it out eventually but that seems like it would take forever. is there like a standard method most people use or is it just whatever works for you
  7. yeah ive done almost exactly this with an IC-7300 and a homebrew 6-port switch. the glitch thing you're worried about is real, my first version would occasionally flicker the wrong relay during a band change and i could actually hear a pop in the audio. what ended up working for me was just a simple timer debounce in the main loop — basically i read the BCD state, wait like 50 milliseconds, read it again, and only act if both readings match. works perfectly now and the delay is so short you dont even notice it operationally. one thing i'd add is put some protection diodes across your relay coils if the ULN2803 board doesnt already have them. the flyback voltage can do weird things to the arduino over time, might not kill it immediately but ive seen people have flaky behavior traced back to that. also worth putting a small cap on the 5v rail near the arduino if youre switching a lot of relays — the current spikes are real.
  8. so ive been putting this off for like a year but i finally got around to building a 40m dipole from scratch. used about 66 feet of 14 gauge stranded copper wire i had laying around from an old electrical project, cut it roughly in half and tied it off to a center insulator i made from a chunk of pvc pipe i drilled through. nothing fancy but it went up yesterday afternoon. heres where im second guessing myself though. the feedpoint is sitting at maybe 25 feet in the middle and the ends are drooping down quite a bit, probably closer to 15 feet off the ground. i know an inverted V isnt ideal but its what i had to work with. the SWR on 40 is reading around 1.8:1 at the freq i cut it for which honestly isnt terrible but i keep reading that a proper dipole should get closer to 1.5 or even lower. im wondering if the droop on the ends is killing me or if its something with the feedpoint connection. also i just twisted the coax center conductor and shield braid around the two wire ends and used some electrical tape to weatherproof it. is that sketchy or does that actually hold up okay? feel like i should solder it but i dont have a good outdoor setup for that right now.
  9. honestly the hamstudy.org route is probably fine for passing the exam, most people i know who got their tech in the last few years just drilled the question pool online until they were hitting like 85-90% consistently and then went and took the test. the ARRL book is good if you actually want context for why the answers are what they are but it can be slow going. what i usually tell newcomers is use both — skim the book for the sections on electrical principles and regs because those tend to trip people up, and then use hamstudy for the daily practice. the pool only has like 400 something questions and once you've been through them a few times it starts to stick. the RF safety and band privileges stuff is worth actually understanding though, not just memorizing, youll need that once youre actually on the air
  10. oh man the small stuff. okay here's what got me: i had everything wired up beautifully but forgot a simple anderson powerpole distribution block so i was trying to run two things off one connector with some janky adapter i made at midnight. also bring way more coax connectors and adapters than you think you need, like PL-259 to BNC, BNC to SMA, whatever you can fit in a little ziplock. you'll need the one you didn't bring guaranteed. the 705 would be a solid choice for a go-kit by the way. i know some people think the power output is low but with a decent antenna it really does fine and the size is just right. the 7300 is amazing but yeah not really practical unless you have a dedicated vehicle setup. one more thing — headphones. actual headphones not earbuds if you can manage it, when youre in a noisy shelter or EOC you'll thank yourself
  11. so ive been running APRS for about 6 months now, mostly just tracking with a TM-D710G and a Mobilinkd TNC hooked to an HT as a backup. everything seems fine, my beacon hits the map fine, i can see myself moving around on aprs.fi when im driving, digi path is WIDE1-1,WIDE2-1 which i thought was pretty standard for my area. the problem is messaging. im trying to send messages to another guy in my club, he's running an FT3D with APRS enabled, and neither of us can get messages through to each other. we can both see each other on the map no problem. ive tried from the radio directly and also through APRS-IS using aprsdroid on my phone. sometimes a message will go through after like 10 minutes and sometimes never. we were literally parked next to each other last tuesday and it still wouldnt work reliably which is what really confused me. is there something specific about how the FT3D handles messaging that might be the issue? or is this just how APRS messaging is and im expecting too much from it
  12. yeah the full ITU Q code list is pretty overwhelming, most of it is irrelevant for amateur use. the ones you'll actually hear or see constantly are probably QSO (a contact/conversation), QRM (interference from other stations, man-made), QRN (natural noise like static from storms), QSB (signal fading, usually propagation related), QTH (your location), QRZ (who is calling me), QSL (confirmed, or the physical card), and QRP which means low power operation though a lot of guys use that loosely. QRT means you're shutting down or going off air. there's also QSY which is changing frequency. 73 just means best regards, it's been around since the telegraph days. 88 means love and kisses, traditionally sent to a woman though honestly you hear it all over the place now without much thought. some old timers get a bit prickly about using 88 casually but most people don't care. also worth knowing - on FT8 and digital modes you'll see a lot of abbreviations that aren't Q codes at all, like RR73 which is just a sign-off that rolled two things together. once you're on the air for a while it just starts to stick naturally.

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.