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

Sarah Collins

Members
  • Joined

  • Last visited

  1. honestly same boat as you a few months back lol. what helped me was just downloading the actual band chart from arrl.org and printing it out and keeping it near my radio. the part 97 document itself is rough reading, i dont think anyone actually reads it cover to cover unless they're studying for general or something
  2. omg i didnt even have my radio on saturday, was doing yard work all afternoon and totally missed it. this is why i need to just leave the thing on in the background more often lol. i only got my tech last year and just upgraded to general a couple months ago so im still figuring out when to even bother checking the higher bands. is there a good way to know when an opening like that is starting without just stumbling onto it?
  3. i cant make it this year but the club president posted on their facebook page that they got more vendor signups than usual so maybe its better this time around. worth checking their page before you commit to the drive
  4. Ha yeah the first few times checking into a net feel exactly like that, you check in and then its like okay now what. Most of the time on a basic traffic net if you dont have any traffic to pass and nobody has traffic for you, youre basically just counted as a check-in and thats it. Which sounds boring but it actually matters for things like keeping the net active and demonstrating that the frequency is being used regularly. The more interesting stuff happens when someone actually has a formal radiogram they need passed down the line toward its destination. If you stick around long enough and learn the NTS format you can start handling traffic yourself and that makes it way more engaging. There are some good resources on the NTS (National Traffic System) if you want to dig into that side of things. For HF nets on 40m with an attic dipole, honestly just try it. Worst case you dont make it in or you get a partial. Most net controls are pretty patient with people. Evenings on 40m can be really good depending on where youre trying to reach.
  5. went through the exact same thing when i first got started haha. the baofeng menu is kind of a nightmare to navigate honestly but once you find the tone settings it makes sense. one thing i'd add is double check the repeater offset too — most 2m repeaters are plus or minus 600 kHz and if thats off you might be transmitting on the wrong frequency entirely without realizing it. the repeater directory should list the input and output so you can verify. good luck, repeaters are a lot of fun once you get everything dialed in.
  6. honestly i just leave mine stock, the 7300 is already pretty decent out of the box for what most people do with it. but i get it if youre doing the wspr and weak signal stuff. my buddy did a similar mod on his 705 and swears by it for portable ops where temperatures swing around. the one mod i actually have done is the simple fan mod where you swap in a quieter fan because the stock one drove me nuts in a quiet shack. not exactly performance but quality of life improvement for sure.
  7. this is gonna sound dumb but did you check the TX/RX relay? on some of the older yaesu gear those relays get flaky and cause all kinds of weird intermittent stuff that doesnt obviously look like a relay problem. i chased a ghost on an FT-100 for weeks and it was the antenna relay contacts getting dirty. just a thought, probably not your issue but worth 5 minutes to clean the contacts if you can get to them.
  8. i was in the exact same spot about a year ago and ended up just grabbing the baofeng to start. no regrets for what it is but i did eventually get a yaesu ft-70dr because i wanted to get into fusion and i wish i had maybe started there instead of spending money twice. just something to think about if you might want digital modes down the road. the dual watch on the ft-70 is also really nice for monitoring a couple repeaters at once which i use all the time now.
  9. so ive been working on this 40m direct conversion receiver for about three weeks now, started from a design i found in an old QST from like 2003 or so. built the VFO around a hartley oscillator, nothing fancy, just whatever toroids i had in the junk box and a 2N3904 for the active part. the product detector is an NE602 which i know some people hate but it works fine for me usually. the problem is the audio out is super noisy, like not just band noise which i'd expect, but this kind of low hiss/buzz that doesnt change no matter what band conditions are. grounded the input, still there. tried a different audio amp stage (LM386 originally, swapped to a little op-amp config i pulled from somewhere) and the noise profile changed a tiny bit but its still there. power supply is a 12v wall wart which yeah i know could be the issue but ive got a cap on the supply rail right at the board. not sure if its oscillator leakage getting into the audio path or just RF getting in somewhere. layout is pretty much dead-bug on a piece of copper clad which probably doesnt help. anyone dealt with this before
  10. i run both actually, keep the RTL dongle on a pi for ADS-B full time and use the RSP1B for actual listening. the difference on MW DX alone made it worth it for me, i was getting splatter from a 50kW station about 30 miles away that basically made the whole band unusable with the dongle and the RSP1B handles it way better. not perfect but way better
  11. so ive been using Log4OM for about two years now and generally like it, does everything i need for day to day logging, the WSJT-X integration works fine most of the time but i keep running into this annoying thing where if i have both WSJT-X and Log4OM open and i try to switch to SSB mid session it just kind of... stops updating the log automatically and i have to restart something, not always sure which one is the culprit honestly anyway a buddy of mine who does a lot of contesting keeps telling me to just switch to N1MM and be done with it, says its the gold standard for contests which yeah i know, but i dont really do that many contests, maybe 3 or 4 a year, mostly CQWW and the occasional state QSO party. is it worth having two separate logging programs just for that or is there a way to make Log4OM work decently for contest operation too also side question does anyone know if Log4OM can export to Cabrillo properly because last time i tried to submit a CQWW log it was kind of a mess and i ended up manually editing the file which felt wrong
  12. QRM and QRN are definitely different things even though they sound similar and i mixed them up for a long time too. QRM is interference from other stations or man made noise, like if someones signal is stomping on yours thats QRM. QRN is natural static, like lightning crashes or atmospheric noise. so if youre in a thunderstorm and the bands are full of crashes thats QRN, if your neighbor fires up some device that wipes out your reception thats QRM. QRP just means low power, like 5 watts or under typically. some people run QRP as a whole operating style and are pretty passionate about it, building tiny rigs and making contacts with almost nothing. its not about signal quality its about transmit power. 73 and 88 arent Q codes at all, theyre what they call prosigns or just traditional abbreviations. 73 means best regards basically, everyone uses it. 88 means love and kisses and is usually used between operators who know each other well or sometimes sent to a YL which is a female operator. old telegraph codes from way back, not ITU Q codes. there is a master list, the ITU publishes it and you can find it all over but honestly you just absorb most of them by listening. the common ones come pretty fast
  13. i went RSP1C about 8 months ago coming from the same v3 direct sampling setup and yeah HF is just... cleaner. like not magic clean but noticeably less garbage. the MW broadcast stations dont splatter across everything the way they used to. one thing nobody mentioned to me before i bought it was to grab a good upconverter even with the RSP if you're serious about the lower HF bands, some people disagree on this but i found it helped with my specific noise situation. might be overkill for you though.
  14. Yeah JS8Call is a bit of a different animal. I use it mostly for the relay and inbox stuff honestly — there's a small group of us that leave nodes running 24/7 on 40m and you can send messages that get stored and forwarded when propagation allows. for actual real-time conversation it can be frustrating like you said, you kind of have to be patient and accept that a short back and forth might take 10 minutes. once you accept that its not trying to be PSK31 it makes more sense. the weak signal performance is real though. ive decoded stations on JS8Call that were completely inaudible, like nothing on the waterfall that i could see, and they were getting through. that part is genuinely impressive. FT4 is worth looking at too if you want something faster than FT8 for contest-style stuff, the timing is tighter and the sequence is shorter, less time per exchange. PSK31 i have a soft spot for too but honestly 20m is so noisy here that anything without that kind of forward error correction just falls apart when conditions dip. RTTY still has a place in contests but for general weak signal work the WSJT modes just eat its lunch at this point
  15. the listening part is so underrated. i used to just jump in and call and wonder why i never got through. took me embarrassingly long to figure out you have to decode the operators rhythm before you do anything. some of them have really distinct patterns too, like theyll work a run of EU stations then flip to NA for a few, and if you can catch that pattern youre golden. the 8-10 up trick is real by the way, especially on crowded bands where everyone is piled into the same 3khz window like they think the DX can only hear one slice. spreading out legitimately helps, the op has to move the RX VFO either way so might as well be where fewer guys are. the power thing i dunno about personally. on the DX expedition side ive been on two trips and honestly the signals that stand out are the ones that are clean and punchy, not necessarily the loudest. so maybe youre onto something with the cleaner 400w vs dirty 700w theory. reciprocal conditions matter too, if the band is marginal they need your signal to be readable not just loud.

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.