Kevin Anderson

That double-squeal thing is called a double — basically two stations keyed up at the same time and their signals mixed together on the repeater. It happens all the time, especially on busy nets. Totally normal and nobody did anything wrong necessarily, just two people with the same idea at the same moment. Net control handles it, thats literally what theyre there for. And yeah what you did sounds exactly right. You give your callsign, say whether you have traffic or comments, and hand it back. Some nets are a little more formal and want you to say the net name or net controls callsign too but most local Monday night type nets are pretty relaxed. If the net has a specific check-in format they usually announce it at the top before taking check-ins, so just listen for that. Waiting a beat or two before keying up is actually good practice — gives the repeater tail time to drop and makes sure the previous station is really done. You were probably doing it right and it just felt weird because everything feels weird the first few times.

yeah i went through basically this exact thing when i started. what helped me was just listening to a lot of CW — like pull up the W1AW practice broadcasts or even just tune around 40m in the evenings and just listen without trying to copy everything. your brain starts to hear what clean code sounds like and then when you send it you kind of self-correct without even thinking about it. took me a few weeks but it clicked eventually

yeah the message handling thing is a real problem everywhere not just your group. we did a similar drill about two years ago and honestly it was almost embarrassing how fast it fell apart once we simulated the repeater going down and everyone had to go simplex. half the guys didnt even know what frequencies we'd agreed on ahead of time. what helped us a lot was doing short 30-minute nets on a random tuesday evening where the only goal was passing practice traffic. no scenario, no roleplay, just hey here's a message, pass it accurately, let's debrief. kept it low pressure and people actually started showing up more once they realized it wasnt going to eat their whole evening. after a few months the muscle memory starts to build and then when you do the big drill it's one less thing to worry about. also the go-bag thing -- we made a laminated one-page cheat sheet with all our primary and backup freqs, the net control call, and a quick ICS-213 format reminder. took maybe 20 minutes to make and it's genuinely saved us during exercises when someone panics and blanks on procedure.

not lazy at all, i went like 3 months barely keying up last winter. just wasnt feeling it. then one night i randomly called CQ on 17m and worked japan on the first call and suddenly i was back at it every night lol. sometimes you just need a break from the hobby side of it and let yourself just enjoy listening again

yeah the learning curve is real and honestly if you're already feeling shaky on rate management with one radio, adding a second one doesnt magically fix that. what it does is let you work a multiplier on 15 while you're running 20, which over a 48 hour contest adds up to a lot. but you gotta be comfortable enough with logging and frequency control that it becomes almost automatic before the second radio actually helps you. your antenna situation is the bigger concern though. sharing a tribander between two radios on adjacent bands with no real physical separation is going to be rough. you'd want at least the bandpass filters you mentioned, i use the W3NQN style filters and they're pretty solid but even then if both radios are cranking into the same antenna system you're going to hear yourself. some people run bandpass plus a good RF-sensing relay system to handle the antenna switching so only one radio keys at a time, which takes some of the mental load off at least. honestly my suggestion would be to try SO2R lite first — meaning you use the second radio purely for listening and spotting mults, dont transmit on it at all. no filter worries, no coordination headaches. get used to splitting your attention before you try to actually transmit on both. took me probably two full contest seasons before i felt like the second radio was actually helping my score.

yeah the SOTA + contest combo is kind of a thing but its pretty niche. some activators will pick a summit during say the ARRL 10m contest and try to work contest stations from the top but honestly most of the time the contest guys arent looking for your summit reference and you're not really optimized for either activity at that point. i tried it once during a VHF contest and it was more chaotic than fun tbh just do CQ WW on its own first and see if contesting clicks for you. some people love it some people find it kind of soulless after a few hours of 59 5 59 5 over and over. no shame either way.

so i finally worked up the nerve to check into the local 2m net last tuesday and it went okay i guess but i kept second guessing myself the whole time. like when the net control asked for any further traffic i wasnt sure if i was supposed to say something or just wait. ended up just saying my callsign again and saying nothing further which felt weird. also i wasnt sure how long to wait before transmitting after they call for check-ins — i jumped in at the same time as another guy twice and we doubled up. net control was really nice about it but still felt embarrassing. is there like a general rule for how long to pause before you key up? and is it rude to just check in and say nothing further every week or is there an expectation that you actually bring traffic or a comment or something? i dont want to be that guy who just checks in to pad the count but i also dont always have something to say

yeah the rx coverage opening up was the main reason i did it on mine tbh, i use it as kind of a shack receiver when im not actually transmitting. did you do anything to the squelch sensitivity while you were in there? i feel like the VHF squelch on mine has always been a little finicky and im not sure if thats a known thing or just my unit.

congrats on the build and the first qrp contact, that feeling never really gets old. 579 on 5 watts into ohio is solid, you picked a good time to get on 40m. to answer your question yeah band conditions and timing matter way more when youre running qrp, like it magnifies everything. i tend to stick to 40 and 20 mostly, 17m can be really good too when the band cooperates. early morning and late afternoon on 40 is usually where i find the most success for domestic stuff. and if you ever get into digital modes like ft8 the qrp thing almost becomes a non-issue, ive worked europe on 2.5 watts plenty of times. for the antenna honestly for portable use a simple linked dipole is hard to beat, you can roll it up in a bag and its just more predictable than an EFHW in my experience. that said a lot of people swear by the end fed half wave with a 49:1 unun and they work fine too, just more fussy about the feedpoint height sometimes. try both if you can, wire is cheap.

you'll do fine honestly. the hardest part is just getting out there the first time. def spot yourself on pota.app, dont rely on someone else doing it for you especially for your first one. just pull up the app, find your park reference number and log yourself as active, takes about 30 seconds once you know how. and if the frequency is busy just grab something else and respot. one thing i wish someone told me early on — if 20m feels dead try 40m especially if it's later in the day. and sometimes just calling CQ a few times with no response you think nobody's listening but then boom three stations come back at once. give it more time than you think you need before moving on. good luck tomorrow, let us know how it went

i remember my first time, i was so nervous i forgot my own callsign for a second lol. just breathe and go for it honestly. the people on my local repeater were super cool when i introduced myself, one guy even offered to do a proper signal check with me. you'll be fine

honestly you're overthinking it. i came from a completely non-technical background, was an english teacher for 20 years, and i passed General on my first try after maybe 3 weeks of using HamStudy.org every day during my lunch break. the math questions look scarier than they are because you dont actually have to derive anything, you just need to recognize which formula goes with which situation and plug in numbers. if you can do basic algebra you'll be fine. the thing that tripped me up a bit was the band plan and frequency privileges stuff, there's more of it than on the Tech exam and it's easy to mix up which modes are allowed where. but just drill the practice tests and you'll start seeing the patterns. i'd say give yourself 4-6 weeks if youre not in a rush, maybe less if you study consistently. the HF bands are absolutely worth it, 40m at night is a completely different world from anything you can do as a Tech.

i had almost the exact same setup in my old jeep, lip mount and feedline through the door, worked totally fine for like two years. dont stress it too much. the voltage thing yeah thats just startup, my ftm-400 does the same thing every time i crank it, drives me a little crazy but i just ignore it now because everything works fine once its running.

curious what your upstream bandwidth looks like at the rural site. ive found that a lot of these sync/drift issues people blame on software are actually just asymmetric bandwidth doing weird things to the streams — especially if youre on a rural connection that might be satellite or older DSL where upload is really constrained. the SDR stream is pretty greedy compared to just voice audio and if theyre competing for the same upload pipe things get messy fast. also not sure if you tried this but theres a guy on the RemoteHams forums who posted a config a while back for running the IC-7300 USB in a way that uses the radios own panadapter data instead of a separate SDR and apparently it cleans things up considerably. cant remember his callsign but worth digging through the threads over there if you havent already.

so ive been licensed for about 8 months now (general) and keep seeing people talk about cw on the bands and honestly it sounds kind of cool, like theres something about it that seems almost meditative or whatever. anyway i dont really know where to start. i tried just looking up youtube videos but theres so many different approaches and some people say learn the sounds not the dots and dashes and others say use an app and i dont know which way is actually going to stick for someone who has zero background with this. i work a desk job so i could probably practice during lunch or something. is there like a standard way people do this now or is it just whatever works for you

so ive been messing around with this for a few weeks now and i think i finally have something worth sharing, or at least worth getting feedback on before i go too much further down the rabbit hole basically i got tired of manually adjusting my yagi when im trying to track satellites and i had a pi4 just sitting in a drawer doing nothing so i figured why not. wrote a python script that pulls az/el data from gpredict via the rotctld interface and feeds it out through a GPIO expander board to an H-bridge i salvaged off an old printer motor controller. the rotator itself is a homebrew thing i built like 5 years ago with a windshield wiper motor, nothing fancy it actually works pretty well but im having this weird issue where occasionally the az will overshoot by like 10-15 degrees and then hunt back and forth a couple times before settling. my feedback pot is a 10-turn bourns unit so i dont think its resolution, more like my PID loop isnt tuned right or maybe the motor is just too fast for the control loop to keep up with. anyone done something similar and dealt with the hunting issue also thinking about adding an arduino nano as a dedicated ADC front end for the pot since the pi's GPIO is all digital obviously, right now im using an MCP3208 over SPI which works but feels a little clunky in the code

Just got my Tech license and I'm confused about the band plan vs. FCC rules. I see that I have privileges from 28.000 to 28.500 MHz, but I keep hearing about staying away from band edges. Where exactly should I operate as a new Technician on 10 meters, and do I need to worry about getting too close to the band limits? I have an IC-7300 and want to make sure I'm operating legally and following good practice. Any guidance would be appreciated!

yeah the ALC thing is huge and i dont think enough people understand what its actually doing. its not a signal strength meter, its telling you when the radio is pulling back your power to prevent distortion and if its sitting pegged the whole time youre basically running reduced power AND getting bad audio. worst of both worlds one thing i'd add — get someone to give you an honest audio report, not just a signal report. most people will just say you sound fine because they dont want to be rude but if you ask specifically like hey does my audio sound clean or is there anything off, youll get more useful feedback. i had a buddy tell me i had a low hum i couldnt even hear on my end, turned out to be a ground loop from my logging computer. never would have found it otherwise also the bandwidth setting on your radio if it has one. running 2.8 or 3khz for a ragchew is fine but some guys have their TX filter set too narrow and wonder why they sound thin and tinny. the radio's TX EQ if it has one is worth spending an afternoon with too, boosting a little presence around 2-3kHz can really help cut through on a noisy band

the TX bandwidth thing is probably your culprit honestly. a lot of people tighten that up thinking they're being neighborly on the band but if you narrow it too much on SSB you're chopping off the high end presence frequencies and that's exactly what gives you that muffled barrel sound. on the 7300 i'd reset the TX bandwidth to something like 100-2900 hz as a starting point and see how that changes the reports you're getting. also check your mic gain — if you're overdriving it even a little that causes compression artifacts that sound terrible. watch the ALC meter while you're talking and you want it barely moving on speech peaks, not pinned. the built in mic on the 7300 isnt bad honestly, i used mine for about two years before switching and people said it sounded fine. the radio itself has decent processing built in, just dont crank the speech processor too high, that's another thing that'll make you sound like youre in a tin can real fast.

47 on your first activation is really solid, dont sweat the pile up management stuff that just comes with reps. the main thing i tell people is dont be afraid to just take control of the frequency, if it gets messy you can say QRZ once and just wait a second before calling the next station. hunters are generally pretty patient especially with new activators, most of them have been doing it long enough to know. one thing that helped me a lot was switching from logging on my phone to a small paper log when it gets really busy, then i upload to adif later. i know it sounds backwards but when youre in the middle of a pile having one less screen to worry about frees up a lot of mental bandwidth. hamrs is great but sometimes simple is better when youre learning. also if 40 gets really heavy try jumping up to 17 or even 15 if conditions allow, sometimes a thinner pile on a higher band is way easier to work through and you still rack up the contacts pretty quick

im also pretty new to WWFF and just wanted to say this is encouraging to hear. ive been nervous to try an activation because im not sure i can get enough contacts but 44 sounds doable even for me. wait you said 47 sorry. anyway good to know the car thing is ok because i was worried about that same situation, i dont always want to be sitting in the wet lol

same here. been busy with work and dont have the energy to actually ragchew so monitoring is kinda my low effort way to still feel like im in the hobby lol. also helps me learn band conditions without having to do anything

yeah that gap between training and a real activation is real and i dont think there's any way around it honestly. i've been involved with ARES for maybe 12 years now and i still tell new members that the SET exercises are great for muscle memory on procedures but they can't simulate the ambient chaos of an actual EOC with real stress and real served agency staff who have no idea what we do or why we're there. the traffic surge thing you described is super common. what i do now is keep a simple log sheet right in front of me and just write down requests as they come in, numbered, so i dont lose track when things pile up. sounds obvious but in the moment it helps a lot. and yeah, the go bag with food and water and a change of clothes is not optional, that's a lesson everyone learns the hard way at least once. sounds like you handled it well though, the fact that you were self-aware about the radiogram formatting means you were paying attention to the right stuff.

Adjacent channel isn't really a concern within the transponder passband since it accepts FM, CW, SSB, SSTV, PSK, and packet simultaneously. The bigger issue is AGC - strong signals suppress weak ones across the entire transponder.

so i've been meaning to do this for like two years and after the last bad storm season i finally sat down and started pulling stuff together for a proper go-kit. right now i have my FT-891 in an ammo can with a power pole strip, a 40ah lithium battery, and im working on getting a decent antenna situation sorted out. thinking either a EFHW or maybe a vertical that can break down small enough. my question is mostly about what people forget until it's too late. like the radio and the battery stuff seems obvious but what are the little things that bite you when you're actually deployed somewhere and trying to set up in a hurry or in the dark or whatever. i went through a checklist i found online but honestly it felt like it was written by someone who has never actually deployed anywhere, very generic stuff. also not sure how much documentation i should be keeping in the kit itself — like printed freq lists, ICS forms, that kind of thing. is that overkill or do people actually use that stuff in the field?