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

Rachel Green

Members
  • Joined

  • Last visited

Solutions

  1. Rachel Green's post in studying for general, few questions about what to expect was marked as the answer   
    the jump from tech to general is noticeable but its not like crazy hard if youve been actually doing radio stuff for a while. the electrical theory and the propagation questions tripped me up at first but honestly once you get through the pool a few times it clicks. i used ham study dot org to drill questions and that helped way more than just reading the book cover to cover
    as for 40m, yeah you get a good chunk of it as a general. techs get a tiny sliver up around 7.225 or so for phone i think, but as general you get phone from 7.175 up to 7.300 and cw/digital below that. 40m is great for regional stuff in the daytime and can go pretty far at night, you picked a good band to start with. just be aware it gets crowded on weekends especially during contests, which can be either annoying or fun depending on your mood
  2. Rachel Green's post in N1MM vs Log4OM for general logging when you also do FT8 contests occasionally was marked as the answer   
    yeah the two-software thing is what most serious contesters do and honestly its not as bad as you'd think once you get the ADIF import dialed in. N1MM is just in another league for contesting, theres really no comparison when it comes to rate display, the function key macros, the networked multi-op stuff if you ever get to that point. Log4OM is great but its trying to be a general logger and a contest logger and kind of does both okay instead of one thing really well
    for the WSJT-X to N1MM UDP thing, go into WSJT-X settings under the Reporting tab and set the UDP server to 127.0.0.1 port 2333, and in N1MM make sure UDP is enabled under config. it should just start populating. i had it working in maybe 10 minutes once i actually read the N1MM documentation instead of just guessing at it
    duplicates between the two logs are annoying but not a disaster, i usually just do an ADIF merge in Log4OM and let it skip dupes by callsign and band. never had a serious problem with it
  3. Rachel Green's post in confused about what i can and cant transmit on as a tech — Part 97 stuff was marked as the answer   
    yeah the third party thing trips up a lot of new hams. basically your friend can talk through your radio as long as you're the control operator and you're present and responsible for what gets transmitted — you cant just hand someone the mic and walk away. the country thing is a separate issue, it means if youre trying to pass a message to a ham in say Brazil or wherever, there needs to be a formal third party agreement between the US and that country or you technically cant do it. most major countries have agreements, you can find the list on the ARRL site.
    the music thing — yeah you just cant broadcast music as content, like playing songs intentionally. incidental background noise generally isnt gonna get you in trouble, the FCC isnt sitting there with a stopwatch waiting for someone to sneeze on the air. use some common sense and youll be fine. the rules sound scarier than they are in practice, most hams never hear from the FCC in their entire lifetime.
  4. Rachel Green's post in first POTA activation went way better than expected was marked as the answer   
    so i finally pulled the trigger and did my first ever parks on the air activation last weekend at a state park about 45 minutes from my house, K-4566 if anyone knows it. i had been putting it off forever because i kept convincing myself i wasn't ready or my setup wasn't good enough or whatever excuse i could come up with.
    ended up throwing my end-fed halfwave up between two trees, ran about 15 watts on 40m and a little on 20m, and honestly i got my 10 contacts in like 25 minutes. i was not expecting hunters to just be waiting like that. every time i put out a spot on the POTA app someone came back almost immediately. had a few guys who clearly do this all the time, very patient with me when i fumbled my callsign exchange a couple times.
    the only thing that tripped me up was logging. i was using paper in the field which was fine but then uploading to the POTA website afterward was a little confusing at first, the adif format thing. figured it out eventually but maybe someone has tips on making that part smoother. anyway if you've been on the fence about doing one just go do it, the community is super welcoming
  5. Rachel Green's post in how do people actually learn morse code, like from zero was marked as the answer   
    the thing that actually made it click for me was the Koch method, specifically using a program called LCWO dot net, its free and you basically learn one character at a time but always at full speed — like 20wpm character speed — instead of slowing the dashes and dots way down. slowing it down is what messes people up because then when you try to copy real signals your brain cant recognize anything
    took me about four months of maybe 20-30 minutes a day to get to where i could copy 15wpm solid enough to have a slow ragchew. some guys get there faster. honestly the biggest thing is consistency, even just 15 minutes every day beats an hour on the weekend. once you get to maybe 10 characters down, go find some slow CW nets on 40m and just listen, even if you cant copy most of it your brain starts making connections you dont even notice
  6. Rachel Green's post in SO2R finally clicked for me this weekend — some thoughts was marked as the answer   
    yeah the "background process" mental model is exactly right and i wish someone had explained it to me that way earlier. i spent way too long trying to do SO2R like i was actually operating two stations and it just doesnt work like that for most people.
    one thing that helped my rate a lot on the run radio — and this is kind of boring but it works — is getting really disciplined about your exchange. like trimming every unnecessary word. you dont need to say your callsign twice on every contact if the band is decent. develop a feel for when the other station has you and just move on. sounds obvious but in the heat of a contest you slip into habits.
    for your shared antenna situation, whats your isolation setup? if youre bleeding into yourself on adjacent bands thats gonna kill you. even with band separation you want to know whats actually getting through. i ran a similar mixed rig setup for a few years and the K3's receiver is so good it actually made the problem more obvious because it could hear its own bleedthrough that the older rig would've just masked.
  7. Rachel Green's post in struggling with my paddle technique, hand keeps tensing up was marked as the answer   
    yeah the hand tension thing got me too for a while. someone at my club told me to try operating with my elbow resting on the table rather than my wrist and it made a huge difference, less strain on the tendons i guess. also are you using the paddle on a slippery surface? i had mine sliding around and i didnt realize how much energy i was wasting just trying to keep it in place until i stuck some rubber feet on the base
  8. not a dumb question at all, took me forever to feel comfortable with all of it. yeah QTH is your location, you got that one right. QSL means basically confirmed or understood, like when someone says QSL that they got your message. QRM is interference from other stations, like man made noise, whereas QRN is natural static and noise. QSY means change frequency, so if someone says QSY to 14.255 they want you to move there. QRZ is asking who is calling, you hear that a lot at the end of a CQ.
    73 means best regards, its one of the old numeric codes from telegraph days that stuck around. 88 is love and kisses which you mostly hear people say to their spouses on the air which is kind of sweet honestly. there used to be a whole big list of number codes but most of them died out except 73 and 88.
    ARRL website has a full Q code list, just google ARRL Q codes and itll come up. print it out and keep it near the radio for a while, thats what i did when i was starting out. you stop needing it after a few months of actually getting on the air regularly.
  9. Rachel Green's post in Programming HTs without going insane - tips for new hams? was marked as the answer   
    Getting folks on the air is the important thing - don't feel bad about struggling with manual programming! Start with your most-used local repeater first, then add the 2m and 70cm calling frequencies (146.52 and 446.00). Using CHIRP with a USB cable makes loading a long list of channels much easier.
  10. Rachel Green's post in when do you actually use phonetics vs just saying the letter normally was marked as the answer   
    i had the same confusion when i started. what clicked for me was thinking about it like — if theres any doubt at all whether they got it right, use phonetics. my callsign has a couple letters that sound similar so i basically always phonetic the whole thing when making initial contact. after that if we're chatting and the signal is solid i'll just talk normal.
    the america/alpha thing is def a real phenomenon lol, ive also heard people say "easy" for E instead of echo. drives me a little nuts but you get used to it
  11. Rachel Green's post in Winlink setup questions - RMS gateway keeps rejecting my connection was marked as the answer   
    so ive been trying to get Winlink Express working for a few weeks now and im pulling my hair out. the basic idea seemed simple enough, install the software, configure a soundcard TNC or get a hardware one, point it at a nearby RMS gateway and send email. except nothing is working the way the tutorials say it should.
    my current setup is a IC-7300 feeding into the built in USB audio, VARA HF as the modem, and im trying to hit a gateway thats supposedly about 80 miles away on 40m. i can see the gateway in the map, it shows active, but when i initiate a session i get a connection attempt and then it just times out or i get a partial handshake and then nothing. checked the frequency offsets, made sure VOX or the CI-V PTT is actually keying the radio (it is, i can see the ALC moving), levels seem okay. not sure if its a propagation thing or something wrong with my config.
    also im confused about the whole RMS vs Winlink gateway distinction. like is every RMS node also a full gateway to the internet or are some of them just relay points? i thought they all connected back to the CMS servers but maybe im wrong. and do i need to register my callsign somewhere before i can use the network or does it just work once the software is configured?
    any help appreciated, this is for emcomm work and i'd really like to get it sorted before our next exercise

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.