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 B7.8
Wind 413.7 km/s
Aurora 3
Updated 00: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

Brian Harris

Members
  • Joined

  • Last visited

Everything posted by Brian Harris

  1. yeah VARA FM is the way to go if you have a choice. i was running plain old 1200 baud packet for like two years on my local RMS connects and then switched and the speed difference on longer messages is pretty noticeable. the paid VARA FM license is like 69 euros or something and if you're gonna use this regularly its probably worth it but the free version works fine for occasional use. one thing that tripped me up early on was the channel selector in Winlink Express — make sure you're actually pointed at the right frequency for your local RMS gateways and that the mode matches what the gateway is advertising. i wasted like an hour once because i was trying to connect VARA FM to a gateway that was only running packet. the winlink RMS list on rf.winlink.org shows you exactly what modes each gateway supports so that's worth bookmarking.
  2. i was in basically the exact same spot last year lol. ended up going with the baofeng uv-5r just to save money and honestly for hitting repeaters around town it works fine. BUT i did eventually pick up a yaesu ft-65 a few months later and the difference in audio quality on receive is pretty noticeable. so kind of wish i just started there. if your budget can handle it i'd probably skip the baofeng this time around since you already know what those are like
  3. oh man i was so confused about this exact thing when i first got my ticket. what finally clicked for me was just sitting on 7.265 one evening and listening to a traffic net go through the whole thing. once you hear net control say "QNI" and people start checking in one at a time it all makes sense pretty fast. also worth knowing — a lot of the 2 meter repeater nets in your area are way more beginner friendly than HF nets honestly. less pressure, people can usually hear you clearly, and net controls on local repeater nets tend to be patient with newcomers. check if your local club has one, mine runs every Tuesday and its genuinely just a bunch of people saying hi and talking about what theyre working on.
  4. Great methodology. I'd add that modern transceivers often have multiple switched supply rails. Signal Tracing: Use a signal tracer or multimeter to trace the audio signal path through the receiver and identify points of failure. Component Testing: Test individual components Don't forget to check the 8V and 5V rails in addition to the main 12V supply.
  5. so ive been chasing rare DX seriously for maybe three years now and pileups have always been the thing that just destroys me. i run a pretty modest station, IC-7300 into a hexbeam at about 30 feet, so im not exactly K3LR here. but last week i finally worked what i think was a 3Y0 operation (one of the recent ones, not gonna say which to avoid drama) and i wanted to write up what actually clicked for me because honestly most of the advice i read online is either obvious or way too vague. first thing i changed was i stopped listening to where everyone was calling. sounds dumb but i used to just throw my call in the middle of the pileup frequency which is exactly where 200 other guys are. started listening more carefully to where the DX station was actually coming back to and trying to figure out the pattern. some ops work up the band, some work down, some are genuinely random but you can usually get a feel after watching for 10 or 15 minutes without transmitting at all. second thing was split discipline. i was being sloppy about my transmit frequency. started parking maybe 3-4 kHz up from where most of the pile seemed to be concentrating. also cut my callsign to just the last two letters when the op was clearly pulling partials, then gave the full call when they came back with something close. third and this is the one that really made a difference — timing. i was transmitting wayyy too long. got my call down to one clean send, maybe 1.5 times at most. the guys working them efficiently were doing single sends and listening immediately. every extra second youre transmitting is a second youre not listening to what the DX is doing. anyway it took about 90 minutes total but got him in the log. just curious what other techniques people have found actually work, especially on SSB because i feel like the CW pileup advice is different enough that it almost doesnt translate
  6. NanoVNA readings at that low a frequency can be a little sketchy if you havent done a proper OSL cal recently or if the cal was done with a short lead and then you added a bunch of coax after. not saying thats the problem but worth ruling out. i had mine reading resonance almost 200 kHz off once and it turned out i just needed to redo the cal at the end of the feedline instead of at the device port.
  7. yeah the business communications thing trips up a lot of new hams. basically the rule is you cant use amateur radio to conduct business — so like calling a customer, coordinating work stuff, anything that substitutes for what youd normally pay for commercially. but just mentioning that you work somewhere or what you do for a living in normal conversation is totally fine, thats not what the rule is going after. the music thing is pretty straightforward, its in there as prohibited obscuring the meaning of transmissions or something like that, and broadcasting in general is prohibited which is the bigger umbrella. nets doing trivia are generally fine because theyre not broadcasting to the general public, theres a two-way communication happening and its incidental. nobody is really worried about that kind of thing. your biggest practical concerns as a new tech are probably just staying in your authorized band segments and identifying properly every 10 minutes and at the end of contact. rest of it kinda becomes second nature.
  8. yeah the QRX thing gets people, it literally means please wait i will call you again in X minutes, so basically just means hold on. i got confused by QRO and QRP for the longest time too. QRP is low power like 5 watts or less and QRO means crank it up, high power. theres also QSL which you probably already know means confirm or acknowledge, like a receipt basically, and thats where QSL cards come from. one thing i'll add is that in contests people shorten even more and it gets wild, you'll hear stuff fly by super fast and it takes a while to parse it. ARRL has a decent list on their site if you want to bookmark something
  9. yeah ive done almost exactly this with a Yaesu G-450A a few years back. used an Arduino Uno at first then swapped to a Mega when i needed more pins for a second display. the position reading is easy if your rotator already has a pot — just tap off it with a voltage divider and feed it to an analog input, took me like 20 minutes to get that part working reliably. the motor drive part is where you need to be careful. i did NOT try to switch the AC motor directly with any Arduino output, thats just asking for smoke. i used a pair of solid state relays rated well above the motor's actual draw, like 25A SSRs for a motor that pulls maybe 3-4A, because i wanted plenty of headroom and SSRs are cheap anyway. the Arduino just triggers the SSR coil side which is low voltage DC and everything stays isolated. worked great, been running it for probably 3 years now with no issues. i can dig up my sketch if you want, its kind of messy but it works
  10. Hey welcome to the hobby, don't get discouraged. A few things — first, the CTCSS setup on the UV-5R can be a little confusing because there's both a transmit tone (T-CTCSS) and a receive tone (R-CTCSS) setting. For accessing a repeater you only need the transmit one set, which it sounds like you did correctly. So that part should be fine. One thing to double-check is your offset. 2m repeaters typically use a 600 kHz offset, so if the repeater output is say 146.940 your radio needs to be transmitting on 146.340. If you programmed it manually make sure the offset direction is right too, some repeaters are minus offset, some are plus. RepeaterBook usually tells you which. As for nobody responding — honestly that's pretty normal depending on the time of day and how active your local repeater is. A lot of them are pretty quiet during work hours. Try evenings or weekend mornings, that's usually when you get more activity. And yeah there is definitely repeater etiquette — most people just wait for a pause and say their callsign, like "W1ABC monitoring" or if a conversation is going on you wait for a gap and just say your call once. Someone will usually come back to you and invite you in. You're not being rude by trying, just don't key up in the middle of someone's sentence and you're golden.

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.