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

Stephanie Clark

Members
  • Joined

  • Last visited

  1. yeah that timeout thing is almost certainly your problem. a lot of consumer routers will kill UDP sessions that look idle even if they technically arent and RemoteHams uses UDP for the audio stream if i recall correctly. look in your router settings for something like UDP session timeout or NAT timeout and bump it up, some routers have it set to like 30 seconds by default which is absurd. if you cant find it in the GUI you might need to look at flashing DD-WRT or something if the hardware supports it. also worth checking whether your ISP is doing any traffic shaping on that connection. 50/10 cable sounds fine on paper but a lot of cable providers will throttle or deprioritize certain kinds of sustained UDP traffic, especially in the evenings. ive seen this kill remote audio in a really intermittent way exactly like what youre describing.
  2. so i finally got around to building a direct conversion receiver for 40m, been wanting to do this for like two years and just kept putting it off. used the NE602 as the mixer/oscillator and its actually working way better than i expected for a first attempt. picking up SSB signals no problem, can hear CW fine too. the issue im running into is the audio stage is kinda hissy and there's this low frequency rumble that i cant seem to get rid of. i've got an LM386 in there for the final audio amp which i know isnt the most elegant solution but it was what i had on hand. ive tried bypassing various points with caps and moving wires around but nothing really seems to help the hiss much. the rumble gets worse when i touch the enclosure which makes me think grounding maybe? the whole thing is built on a piece of perfboard in an old project box, not exactly ideal for RF stuff. also the VFO drifts quite a bit when it first powers up, like maybe 2-3 kHz over the first 10-15 minutes before it settles down. i assume thats thermal drift from the oscillator? the coil is wound on a piece of PVC which i've read is not great thermally. wondering if i'd be better off rewinding on a toroid or just living with the warmup drift for now since its not the end of the world for casual listening. anyone been down this road with the 602 and LM386 combo? curious what people did about the audio noise specifically
  3. I've got a similar setup but I went with a pi 4 2gb because I got tired of fighting the zero's limitations. cloudlog is actually surprisingly lightweight once you're running it locally, the logging part never really stressed anything. my wsjt-x still runs on a windows machine though because I just got tired of dealing with audio on linux, every distro update seemed to break something with pulseaudio and I gave up honestly. the split approach you're describing is probably the sane call. let the little machine do what it's good at.
  4. 10 QSOs is the minimum to count as a valid activation, yeah. you'll get them faster than you think once you're spotted — hunters are always watching the clusters and theyll pile on pretty quick especially if conditions are decent. self spotting once youre set up is totally fine, most people do it that way. if cell service is sketchy just try to get a spot out before you lose signal, or ask someone on frequency to spot you. theres also the POTA app which sometimes works better than the website on slow data. one thing i wish someone told me — bring more water than you think you need and dont underestimate how long the setup takes when youre doing it for the first time in an unfamiliar spot. i budgeted 20 minutes my first time and it took almost an hour messing with the antenna. once youve done it a few times youll get a system down. have fun with it, first activations are memorable
  5. check the RF power setting in the menu like the other guy said, that trips people up constantly. also worth doing is going into the diagnostics and running the internal checks if you havent already, the 7300 has a decent self-test mode that might throw a flag at something. one more thing — what antenna or dummy load are you testing into? just want to rule out an impedance thing before assuming its the radio. had a guy in my club convinced his radio was broken for two weeks and it was a bad PL connector on his coax the whole time. SWR was spiking and the protection was pulling power back. the 7300 is pretty aggressive about protecting itself from a bad load.
  6. the chirp is almost definitely a keying issue yeah. if youre hard keying the oscillator directly thats gonna cause exactly what your describing — the crystal takes a moment to stabilize under load and you get that frequency wobble at the start of each element. the classic fix is to key the PA stage instead and let the oscillator run continuously. if you want to keep keying the osc for some reason you can add a small delay circuit but honestly its more hassle than its worth. also check if your supply voltage is drooping when you key. even a small sag on the oscillator B+ will pull the frequency a bit. ive seen this cause chirp on otherwise solid rigs, took me forever to figure out the first time. a good bypass cap right at the oscillator and a separate regulated rail for that stage usually sorts it out.
  7. so basically yeah you've got the right idea. LoTW is the one that counts for DXCC and most of the big ARRL awards, the confirmations you get there have actual weight behind them. when both operators upload their logs and the contact details match up within a certain tolerance it just confirms automatically, you dont have to do anything extra. just keep uploading your logs regularly and the confirmations trickle in over time. eQSL is more of a community thing, lots of people use it and its good for some awards but the big dx awards generally dont accept it. i use both honestly. eQSL has that authenticity verified status which matters for some things but a lot of casual operators just use it to share a nice looking card design without worrying about the awards side of it. paper cards i still love them personally. i dont send them for every contact but for anything special, a new country, a nice pile-up i finally cracked, or if someone sends me one first i always respond. the bureau is slow, like really slow, sometimes a year or more, but direct mail is faster if you include a self addressed envelope and some green stamps or an IRC depending where the other station is. dont give up on paper cards, getting one in the mailbox still feels different than a digital confirmation somehow.
  8. So I finally did my first WWFF activation last weekend at a state forest near me (KFF reference) and honestly it went way better than I thought it would. I was super nervous about the whole thing because I'd only done a handful of POTA activations before and wasn't sure how different the WWFF side would be. Set up my little endfed on a squid pole, ran about 25 watts on 40m and picked up 20m later in the afternoon when 40 started dying. Got my 44 contacts which I know is the minimum for a valid activation but now I'm reading that for WWFF the logging requirements might be a little different than what I'm used to with POTA? Like do I need to upload to a specific system or does the ADIF from POTA Hunter work fine? I logged everything in paper first then transferred it but I want to make sure it actually counts. Also noticed a few hunters were asking for my grid square which I wasn't really prepared for, is that something WWFF activators usually give out or is that more of a general thing people ask regardless. The park itself was gorgeous by the way, saw a couple of deer right next to my setup which felt very on-brand for flora and fauna haha.
  9. had something similar on my 7300 a while back, turned out to be the ACC connector itself had a slightly bent pin that was making intermittent contact with the ground line. the radio was seeing the PTT line drop for like a millisecond and that was enough. i only found it because i wiggled the cable while keyed up and could reproduce it pretty reliably once i knew to look there. worth trying to key up with the ACC cable completely unplugged and use the mic PTT instead, just to eliminate that whole circuit. if it doesnt drop out that way then youre probably looking at the connector or the footswitch cable somewhere. those braided footswitch cables can develop internal breaks that are basically invisible from outside.
  10. So ive been on HF for about two years now mostly doing digital modes but lately ive been getting into phone operation and honestly my audio reports have been... not great. people keep telling me i sound like im underwater or that theres a lot of bass and its hard to copy me. im running an IC-7300 into a Heil PR-40 which i thought was supposed to be a pretty solid combo, gain on the mic is set around 50% in the menu, compression is off because i read somewhere that beginners shouldnt use it until they understand what its doing. ive messed with the TX equalizer a little but honestly i have no idea what im doing in there. i tried boosting the mids a bit and someone said i sounded worse so i put it back. my ALC is sitting right at the top of the recommended range, maybe just a tiny bit over sometimes when i talk loud. i think thats probably fine? anyway if anyone has a baseline starting point for SSB audio on the 7300 specifically id really appreciate it. or just general tips on what to listen for. i monitor myself on a second receiver sometimes and i cant really tell whats wrong but obviously other people can hear something
  11. yeah what he said about ALC. also dont overlook where the mic is physically — i used to hold it too close and off to the side because i thought it looked cool or something and my audio was apparently pretty bad lol. straight on, about an inch or two back from your lips makes a big difference, at least with dynamic mics like the stock hm-219 or whatever they ship with the 7300 these days. i switched to an Heil PR-781 a while back and that helped but honestly fixing my mic technique helped just as much for way less money
  12. I had almost the exact same thing happen to me when i first started joining nets. I just started putting my callsign at the beginning of every transmission out of habit and nobody has ever complained about that haha. better to over-ID than under I guess. also some nets are just way more formal than others, the ARES net in my county is pretty by the book but there's a casual ragchew net i join on thursdays that's way more relaxed about it
  13. congrats on your first one, that feeling when you work europe QRP from a summit never really gets old honestly. for the spotting question -- alerting ahead of time definitely helps chasers plan for you, but you still want to self-spot once youre actually on frequency and ready. you can use the SOTAwatch app or if you have cell signal just do it through the website. a lot of activators also text someone at home to spot them if their data is spotty up top, which happens more than youd think. for the summit reference just search it on sotadata.org.uk and if it comes up with a valid reference number and region then youre good. if you activated the wrong peak by accident it happens to everyone at least once, dont sweat it too much just double check next time with the topo maps on the SOTA mapping page and make sure your GPS coords are actually on or close to the summit boundary. on the CW thing -- honestly even at 5wpm youll get contacts, chasers are super patient with slow code especially from a portable station. SSB works fine too, just takes a bit more digging through the noise sometimes at QRP levels. do whatever keeps it fun for you right now.
  14. honest answer: the question pool method works fine and theres no shame in it. the pool is public, the exam questions come straight from it word for word, so if you know the pool you know the exam. hamstudy is what i used and i passed first try no problem. just do the practice tests until youre consistently getting like 85% or better and youll be good, the passing score is only 74% which is 26 out of 35 questions. the electrical theory stuff, yeah theres a handful of questions on ohms law and maybe some basic power calculations but its not a huge portion. i remember maybe 4 or 5 questions out of 35 being actual math. if you just memorize which formula to use for which type of question youre mostly fine even if you dont fully understand why. not saying thats ideal but for getting your ticket it works. once youre actually on the air you pick up a lot more anyway.
  15. yeah i passed mine back in march and honestly hamstudy was the only thing i used, didnt even open a book. just kept doing practice exams until i was consistently hitting like 85-90% and then i went and took the real thing. got a 32 out of 35. the regulations questions are the ones that tripped me up the most because some of them are really specific about frequencies and power limits and stuff, so pay extra attention to those. good luck

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.