Sarah Williams

did my first EME qso about two years ago with a 4x9el array and an old beko amp pushing around 600w. took me probably three months of failed attempts before i actually completed a contact and even then the other guy was running like 4x20el with a kw so he was doing most of the heavy lifting lol. the moon window thing catches people off guard too, you cant just point at the moon anytime, you need it above the horizon for both stations at the same time which depending on where you both are might only be a couple hours. i use WA4NJP's EME planner and the stuff built into WSJT to figure out windows. honestly the community is really friendly about it, there are skeds you can arrange through the moon-net reflector where big gun stations will specifically try to work smaller setups, thats probably how id suggest getting your first contact rather than just calling CQ into the void

so ive been licensed for about 8 months now and i mostly do HF, some 40m and 20m. i get that you're supposed to use phonetics when there's interference or the other station asks you to say again but i feel like half the time people just rattle off their callsign normally and half the time they spell it out phonetically and i cant really figure out the pattern like is there an actual rule about when you use NATO phonetics vs just saying the letters? and does it matter which phonetics you use? i heard some guys using different words than the standard ones, like they'd say something other than Foxtrot for F. is that just a preference thing or are those wrong technically also on SSB specifically it seems like people sometimes do a weird mix where they say their callsign once fast and then spell it out phonetically if asked. is that the right way to do it or am i overthinking this

the cw portions thing is kinda true but also not really — like yeah extra opens up 3.500 to 3.525 on 80m and similar little segments elsewhere but those arent exclusively cw anymore, just traditionally are. i mostly got my extra for the challenge tbh and also so i could stop feeling like a second class citizen during pile-ups lol. whether thats worth months of studying filter theory is a personal call i guess

yeah the switching PSU thing bites a lot of people, i went through two of them before just getting an Astron and being done with it. heavier but no more hash. the 7300 is pretty sensitive to that stuff. the menu depth is real, i've had mine almost two years and still find things occasionally. the scope is worth learning thoroughly though, the mini scope in the corner during a QSO is actually really useful once you set the span right. i keep mine at like 50kHz so i can see if theres activity nearby without going back to the main display. one thing i'd suggest is spend some time with the NR and NB settings if youre on 40m at night, they arent magic but with some tweaking they help with the usual noise mess on that band. enjoy the radio, its a solid rig for the money.

the ICS stuff is what trips up most new folks honestly. knowing the forms is one thing but actually fitting into the incident command structure and understanding who you report to and how information flows, that clicks more once youre actually in the room. just pay attention to who the IC is and follow your EC's lead and you'll be fine for a first drill. baofeng is fine, dont let anyone tell you otherwise for basic VHF/UHF ARES work. i used one for two years before upgrading.

yeah same here, i caught a really long opening into europe last weekend on 10 ssb, worked like 8 or 9 countries in an hour which for me is kind of unheard of. i was honestly just gonna check the band real quick and ended up staying on for two hours lol. my neighbor who got me into the hobby keeps telling me to watch the DX cluster more which i keep forgetting to do but when i finally pulled it up that day there were spots everywhere. if you arent using pskreporter or the dxcluster when the band opens youre missing half the fun honestly

you're definitely not overthinking it, the LoTW setup does look intimidating at first but once you get through the certificate request process it really just kind of runs in the background. the hardest part honestly is waiting for the postcard from ARRL to verify your address, took about a week for mine. after that TQSL (the software you use to upload logs) becomes pretty routine. as for whether you need all three — it depends on what you want. LoTW is the gold standard for DXCC and most major awards so if you ever go down that road you'll want it. eQSL is more casual and a lot of operators use it especially in Europe, the confirmations come fast and its free. physical cards are kind of their own thing, some people love em and collect them, others dont bother. i personally do LoTW for everything and send paper cards for any rare DX i work, just feels right to have something tangible from a tough contact. short answer: get on LoTW first, add eQSL if you want, and send paper cards when it feels special.

honestly i just run three separate logs and gave up trying to make them talk to each other perfectly. WSJT-X for all my FT8 and FT4, N1MM when theres a contest, Log4OM for everything else. at the end of each month i do a manual merge and check for dupes in Log4OM using the ADIF import. its probably not the elegant solution you're looking for but after fighting with UDP ports and ADIF timestamp formats for way too long i just decided my sanity was worth more than a perfectly automated pipeline. the only real problem is when i work the same station on FT8 during a contest and it ends up in both the WSJT-X log and N1MM, those are the ones that sometimes cause issues on import but its maybe 5 or 10 QSOs a month so not really worth stressing over

i dont even have anything to do half the time i just spin the dial on 40 meters after dinner and listen to whatever comes through. caught some guy last night from louisiana telling another guy about his chicken coop situation for like 20 minutes. didnt key up or anything just kind of vibed with it. there's something about the way 40 opens up after dark that i cant really explain to my wife or anyone who doesnt do this hobby. anyway just wondered if anyone else does this or if im weird lol

honest take: if youre doing HF and you want good results, the RSP1B walks all over the HackRF for receive. the HackRF is a great tool but its a swiss army knife and you pay for that versatility with a receive chain that isnt exactly optimized. the RSPdx is even better if you can stretch the budget a little, the switchable antenna ports and the HDR mode below 2 MHz actually make a noticeable difference for MW and 160m SDRuno is... fine i guess, some people hate it because the UI is kind of a lot, but you can run the RSP hardware in SDR# with a plugin and that works well. for WSPR just pipe it into WSJT-X and you're golden. i ran one for about two years before upgrading and it really is a proper step up from dongle territory, not just a marginal thing

the 300-400ms thing is pretty normal unfortunately with RemoteHams depending on where your servers are routing through. one thing that actually helped me was switching from the default opus codec settings to a lower bitrate but also bumping up the buffer size slightly rather than lowering it — sounds counterintuitive but it made the timing more consistent even if the absolute delay was similar. the inconsistency was what was killing me on SSB. also check what your actual round trip time is to the RemoteHams server node you're connecting through. if you're going coast to coast or through a non-optimal route that alone can add 80-100ms before you even account for audio buffering. there's a ping display somewhere in the client, i forget exactly where but it's in there. if that number is already high then no amount of codec tweaking is gonna fix it, you'd want to look at whether there's a closer relay option or set up your own direct connection if you own both ends of the setup. on the echolink bridging thing - honestly i never tried it but i dont see why you couldnt run both on the same remote machine, like have the radio connected to RemoteHams for your own remote access and also keyed into an echolink node independently. they'd just be sharing the same radio which could get weird. might be more trouble than its worth unless you had a really specific use case in mind.