Patricia Lee

i just passed mine like six weeks ago so this is fresh. the oscillator stability questions and the stuff about op-amp circuits was the part that got me, had to watch a bunch of youtube videos to even get close to understanding it. but yeah once i actually had the ticket and jumped down into the extra portion on 17m during a contest weekend it immediately felt worth it. stations i could never work before just sitting right there.

not a dumb question at all, this trips up a lot of new hams. so the CTCSS tone (some people call it PL tone, same thing basically) is what you transmit to open the repeater's squelch on the input side — without the right tone the repeater just ignores your signal. if you can hear traffic on it then your receive is fine, the issue is almost definitely your transmit tone setting. on the baofeng you need to make sure the tone is set on the TX side specifically, not just decode/receive. there's a setting in the menus where you can have it encode, decode, or both — you just want encode for most repeaters. as for nobody responding, that's honestly just how it is sometimes. some repeaters are pretty quiet during the day and then come alive around commute hours. try calling out around 5-6pm local time and you'll probably get a response. just say your callsign and that you're monitoring or looking for a chat, keep it simple. the echolink thing is separate — some repeaters are connected to the internet and can link to other repeaters or stations worldwide, but that doesn't change how you access it locally, you still need the right tone. some linked systems have their own etiquette about pausing between overs to let linked stations come back but you'll pick that up as you go.

ok so ive been doing single op for a few years now, mostly phone contests, did some CW last cycle and got serious about rate after watching some of the top scores come in. decided this year i was finally gonna try proper SO2R during the ARRL DX contest and honestly it went... mixed. like i had the radios set up, two amps, the band decoder doing its thing, but i kept fumbling the timing of when to actually fire up the second radio without stomping on my own run frequency. what i found was that i kept losing my run QSO momentum because i was so focused on what was happening on radio 2 that id come back too slow on radio 1 and guys would move on. my rate ended up being maybe 10-15% better than last year which i guess is something but i expected more from SO2R. is there a mental model or a workflow that clicked for you guys when you first started doing it for real? like do you just S&P on 2 while running on 1, or are you actually CQing on both? also running N1MM and the SO2R setup in there is fine but im still fumbling the Alt+Q and stuff when im tired. any advice appreciated, been chewing on this since the contest ended

for the pi web interface thing — look up hamlib and flrig, you might be able to tie into those rather than writing everything from scratch. i have a pi zero w sitting between my rig and the network mostly for remote operation stuff and it wasnt that hard to get a basic control page going with flask. nothing fancy but it works over the local network just fine. the tricky part for me was getting the serial timing right so commands didnt stack up and cause the arduino to miss inputs.

Don't overthink the battery choice for your first activation. The 12V 12Ah lithium battery, when paired with a small solar panel, offers a lightweight, off-grid solution if you want some backup charging. But honestly, 6Ah should be plenty for QRP work.

yeah i went through basically this exact thing last winter. ended up with the RSP1A and havent looked back for receive. the HackRF transmit capability sounds cool until you realize what you actually need an SDR for day to day, which is listening. if you ever do want to experiment with transmit down the road a LimeSDR might be worth a look too but thats a whole other rabbit hole and the price reflects it one thing nobody mentioned -- SDRAngel is worth trying with the RSP1A if you havent seen it, does a lot more than SDR# out of the box and has some decent decoding built in for various modes. little rough around the edges UI wise but functional

Most of the time I stick to ITU phonetics, but may use DX phonetics for contests. My callsign ITU is 'Kilo Zero November Romeo' but I'll switch to 'Kilo Zero Norway Radio' which is a syllable shorter. You're encouraged but not required to use NATO phonetics - many operators use informal alternate words for part or all of their call sign.

ok so ive been licensed for about 8 months now and i keep seeing all these weird abbreviations everywhere. like QSO, QRM, QSB, QTH and a bunch of others. i know QSL means like... confirming a contact? but the rest i have to keep googling every single time and its getting old. is there like a short list of the ones that actually matter day to day because the full list of Q codes is like 200 entries long and most of them seem to be old maritime stuff that nobody uses anymore. also whats the difference between 73 and 88, i see those too. just trying to get my bearings here