Christopher Lopez

yeah the doppler thing bites everyone when they start. the tricky part with inverting linear transponders is that you need to correct doppler on BOTH uplink and downlink but in opposite directions - if you just let gpredict do it automatically and you have the mode set right it should handle that, but double check that you actually have the right TLE loaded and that it's current. stale TLEs will make your doppler correction lag and you'll chase the signal all pass. also one thing people miss - on an inverting linear if you tune UP on the uplink your downlink signal moves DOWN. so if you're hearing yourself drift one way, try tuning the other direction than you think you should. takes a while to get your brain used to it honestly. AO-73 has a pretty narrow passband too so even small errors are obvious. what TLE source are you pulling from and how old were they when you did the pass?

yeah the alternator whine thing gets almost everybody at least once. i remeber spending a whole saturday convinced my radio was defective before someone at the club pointed me toward the ground. classic. im running a Diamond NR770HB on a lip mount on the trunk of my honda and honestly its been rock solid for a couple years now. lip mounts get a bad rap sometimes but if you do them right they work fine, the trick is getting a solid ground strap from the mount to the body because the paint breaks the electrical connection. some people run a short piece of braid from the mount down to a bolt under the carpet and that does the job. for what its worth i also ran a dedicated 12v line all the way from the battery on my FTM-400 and used an inline fuse near the battery and near the radio end. belt and suspenders approach but i sleep better knowing its done right especially with all that current draw on transmit.

went through almost the exact same thing when i first set this up for our ARES group. one thing nobody told me that wasted like two days — if you have VOX or any kind of TX delay set weird in your radio it will just blow the handshake timing completely. VARA is pretty sensitive to that. also worth trying a telnet session first just to confirm your WL account and callsign validation is working before you blame the RF path, eliminates a variable.

so i finally got around to building a proper inverted V for 40m instead of using that random wire i had thrown up years ago. used 14awg stranded copper from the hardware store, cut each leg to around 33.5 feet based on the 468/f formula. center fed with a SO-239 chassis connector i had in the junk box, fed with about 50 feet of RG-8X down to the shack. apex is at about 35 feet off a mast i bolted to the back of the garage, legs come down to roughly 45 degree angles tied off to some stakes in the ground. resonant point per my analyser is sitting around 7.080 which is a little high for where i want it (trying to get it centered around 7.050 or so). i know i need to add length but how much are we realistically talking, like an inch per leg or more? feels like every time i try to trim these things i overshoot. also wondering if the 45 degree angle on the legs is hurting me much compared to a flatter angle. i dont have a ton of horizontal space so i'm kinda stuck with it but curious what people's experience has been.

congrats on the first activation, that's awesome. to answer your questions: yes, most chasers are actively watching SOTAwatch and the RBNhole spot aggregator, so when you self-spot they'll often come looking for you pretty quickly. some will also spot you if they hear you on the air even if you didn't self-spot first, which is nice. the summit reference matters — you need the exact one, like W6/NC-042 or whatever it is, because that's how the points get assigned and how chasers log it on their end. if you're not sure which one you were on, just look it up on the summits database at sotadata.org.uk before you submit, it's pretty easy to search by location. as for the antenna shaking around in the wind, yeah that can definitely cause some signal variation but 4 contacts on a dipole between hiking poles is solid for a first time out, dont overthink it. try to get the feedpoint a bit more stable next time if you can, sometimes a short piece of cord to a stake in the ground helps keep it from swinging around too much.

congrats on getting out there, that first one is always the one that takes forever to actually happen lol. so for your logging question - WWFF and POTA are separate programs with separate databases, you upload to each one individually. some references overlap (like if the area is both a KFF and a K- POTA reference) but you have to submit the logs to each program yourself, they dont share data automatically. on the 44 QSO thing - yeah that does matter for WWFF specifically, you need 44 to get the activation counted as a full activation in their system. under 44 and it still goes in the log and hunters get credit for the contact, but it wont show as an activation on your record. not the end of the world at all, just means that one wont count toward your activator awards. totally worth going back and finishing the job sometime, 44 really isnt that hard once you get a decent pileup going. try spotting yourself on the WWFF spotter or POTA app next time and you'll probably hit it in the first hour. and ft8 is absolutely fine, nobody frowns on it, plenty of activators run digital. some purists prefer voice but the program doesnt care how you make the contacts as long as theyre in the log.

so our ARES group has a county-wide exercise coming up and i've been tasked with putting together the portable station for the EOC support role. we're going to be outside for probably 12-14 hours and i'm trying to figure out the best way to handle power because last time we had a real mess with the generator situation. what im thinking is running a 100w HF station (ic-7300) plus a separate 2m/70cm mobile rig for local traffic, maybe a laptop for logging and winlink. estimated draw is probably around 25-30A peak when transmitting on HF. i have a 100ah lifepo4 battery that i built last year and honestly it's been solid but i dont know if it'll last the full stretch especially if we're doing a lot of digital stuff which seems to run the radio pretty hard. the other option is to bring our club's honda eu2200i and just run everything off that but the noise thing is a real concern. last exercise somebody put the generator like 15 feet from the antenna feedpoint and we had so much hash on 40m it was basically unusable. plus depending on where they set us up there might be fuel storage restrictions. for antennas i was thinking a linked dipole for HF since it's quick to deploy and i have enough coax, probably hung between two of the telescoping fiberglass masts. anyone running something similar for emcomm? curious what people are doing for noise isolation if they do use a genny.

the math on the general exam is honestly not that bad, i was dreading it too but most of it you can just memorize the formulas and plug in numbers. like ohms law stuff and a few resonance calculations. hamstudy is genuinely all you need if you go through it enough times, i think i spent maybe 3 weeks on it doing like 20-30 minutes a day on my lunch break and passed no problem. on the privileges thing yeah you dont get the full band, on 20m for example generals get most of it but the extra class guys have a chunk of the lower part of the phone portion. honestly as a new HF op you probably wont even notice for a while, theres plenty of room. 40m and 15m are great bands to start on and you get good chunks of both. just go take the exam, worst case you fail and you can retake it same day at a lot of sessions anyway

yeah WIDE1-1,WIDE2-1 is fine for most situations and its definitely the baseline most people recommend. the reason you'd scale back is if you're like right next to a fill-in digi that's already hearing everyone — in that case WIDE1-1 alone might be plenty to get you into the main network. with 4-5 digis in range you're probably okay where you are but you could experiment, just watch your heard stats on aprs.fi and see how many hops your packets are actually taking. on the messaging thing — yes people do use it but you're right that it can feel laggy. it works best when both stations are actively digipeated and have something like APRSdroid or a D7/D710 style rig that shows incoming messages. ive had decent luck messaging into a net when everyone was set up and paying attention but if someones just running a tracker with no display they'll never see it. its more useful than most people give it credit for honestly, just takes coordination.

ran the DIY route with wireguard vpn + flrig + fldigi for about a year before i switched to a commercial solution and honestly i dont regret moving on from it. the custom setup was cool and i learned a lot but maintaining it was a part time job. every time something updated something else broke the RemoteHams SDR piece is genuinely useful if you already have an SDR at the remote site, being able to see whats happening on the band before you even start transmitting is nice. my one gripe is the windows-only client situation, i spend a lot of time on linux laptops and having to spin up a VM to use RCForb is annoying

honestly the theory is not as bad as people make it out to be if you actually sit down with it. the stuff on reactance and impedance and the smith chart questions looks scary at first but there's really only so many ways they can ask it, and once you work through the question pool a few times it starts to click. i used hamstudy dot org almost exclusively and just hammered it for like three weeks before my session. the transistor and op-amp stuff tripped me up more than i expected, not gonna lie. but even then its not like you need to actually design a circuit, you just need to recognize whats happening in a given configuration. the extra band privileges are real by the way, especially on 40 and 75/80 meters — that extra slice at the bottom where only extras can operate gets way less qrm and you'll notice it during a pileup or a contest weekend for sure

first thing id do before poking around inside any more is rule out the mic itself more thoroughly. multimeter continuity on the element isnt really a full test — plug in a different mic or even just a headset and see if the problem follows the radio or stays with the original mic. sometimes the connector on the hand mic takes a hit when the thing falls and youll get intermittent contact that reads fine cold but acts up under load. if its definitely the radio and not the mic, the most likely casualty from a drop like that on that board layout is going to be around the mic amp stage. on the 7300 the audio processing goes through the FPGA but the analog front end before that is where id be looking. check for any obviously cold or cracked solder joints around the mic input jack on the main board, that area takes mechanical stress pretty directly. reflow anything that looks even slightly suspect. ive seen guys fix similar issues just by reflowing a few joints that looked totally normal to the naked eye but had microscopic fractures.

oh man i did the same exact thing when i first started, two tabs open going back and forth. honestly just get GridTracker if you do any FT8, it shows spots on a map and integrates with WSJT-X and it kind of blew my mind the first time i fired it up. might not be exactly what you need for SSB dx chasing but its worth knowing about. for general cluster stuff a lot of people swear by just using the DX Summit website which has decent filtering options built in, you can filter by band or region which cuts down on noise a bit.

mic placement is definitely worth checking before you go deep into menus honestly. i spent like three weeks tweaking DSP settings on my old 756 pro before i realized i just had the mic too close and was getting all that proximity bass boost. moved it back a few inches and suddenly reports got way better without changing anything in the radio. also what kind of audio are you monitoring on your end? cause sometimes what sounds fine in your headphones is not what's going out over the air, especially with the 7300's monitor function there can be some processing in the monitor chain that doesnt reflect the actual transmitted signal. if you have a second receiver or a friend nearby who can actually listen thats gonna tell you more than any meter.

done a few of these 12-18 hour things with our group and honestly the generator is the safe call like you said, especially in late october in the northeast. you're not getting enough sun to keep up with two radios running all day, and even if the HF rig is sitting in receive most of the time the VHF repeater traffic can keep that second radio busy. the lifepo4 packs are great as a buffer and backup but i wouldnt count on them as primary for that duration. the eu2200i is quiet enough that if you position it downwind and run a decent length of extension cord (keep it to 12 gauge if you're going more than 50 feet) you should be fine at the shelter. exhaust just make sure you're not pointed at the tent or wherever people are congregating. we run ours about 30 feet out with an eco-throttle on and it barely registers over normal conversation. for the antennas, NVIS low dipole is the right call for regional, just watch your height — you want it under about 0.2 wavelengths for the bands you're working, so on 60m or 40m that works out pretty low which is easy to do with shelter poles. jpole for VHF is fine. if you have a short mast you can get it up 10-12 feet which is plenty for local tactical assuming the repeater isnt too far.