Steve Johnson

yeah what the other person said, hamstudy is the go-to. i'd also say dont underestimate the ham radio prep book by Gordon West, some people think its old fashioned but it actually explains the why behind stuff which helps a lot more than just drilling flashcards. the tech exam is 35 questions and you need 26 right to pass so you've got a little wiggle room. one thing i'll mention is once you pass tech you'll probably want to get your general pretty quick because tech keeps you on VHF and UHF mostly and once you catch the HF bug you'll want those privileges. just something to think about down the road

so ive been licensed for about 3 months now (general class) and im still trying to figure out the whole repeater thing in my area. i programmed in a few of the local machines from repeaterbook and some of them i can hear traffic on just fine but when i try to key up nobody seems to hear me or i just get the courtesy beep and then silence. my buddy told me i probably have the wrong CTCSS tone set or maybe dont have one set at all. i thought i understood this but apparently not lol. from what i can tell the tone is kind of like a subaudible signal your radio sends along with your voice so the repeater knows youre a legit user and not just random noise right? but im confused because some repeaters on the list dont have a tone listed and others have like 88.5 or 100.0 and i just cant figure out if i need to set both the transmit AND receive tone or just the transmit one. also while im at it — is there some kind of ettiquette i should know about before jumping on a busy repeater? i dont want to be that guy who steps on someone mid conversation. around here there seems to be a net on tuesday nights and i usually just listen but i wasnt sure if its okay for a newer ham to just check in or if thats more for the established guys.

so ive been listening to a lot of HF lately and people are constantly throwing around stuff like QSL and QTH and QRM and honestly i only know like two of them. i know QSL means like confirmed or acknowledged and thats pretty much it. i tried looking up a list online but there are like a hundred of them and i dont know which ones actually get used on the air vs which ones are just old telegraph stuff nobody says anymore. also people say 73 and 88 sometimes, and i figured out 73 is best regards but what is 88 and are there others like that? and whats the deal with saying things like OM or YL, i assume those are for men and women operators but not totally sure. just trying to get a handle on the common ones before i actually start transmitting myself, dont want to sound like a total idiot

so ive been going back and forth on this for a few weeks now and figured id just ask here. im trying to put up something decent for 40m, mostly for ragchewing and some casual DX when conditions are good. my lot is about 75 feet wide and maybe 120 deep, so not terrible but not huge either. i had a half wave dipole up for a while, fed with 450 ohm ladder line into a balanced tuner, and honestly it worked pretty well but i took it down when i rerouted some stuff in the shack and never put it back up. now im second guessing whether to just redo the dipole or throw up a vertical instead. i keep reading that verticals are better for DX because of the lower takeoff angle but then i also read that they pick up all kinds of noise and you need a good ground system or its all a wash. my ground situation isnt great — i'm in a suburban lot and i cant really run 60 radials without my wife losing her mind. was thinking maybe 8 to 16 radials elevated slightly and just live with whatever i get. or do i just put the dipole back up, maybe try to get the center around 45 feet and call it done. anybody dealt with this kind of tradeoff on 40 specifically?

congrats on the first activation, 31 QSOs is solid especially for a first time out and on a random weekday i'm guessing. the upload is pretty straightforward, you just go to pota.app, log into your account, and there's an upload section right there. just drop the ADIF in and it'll parse everything and show you a preview before it submits. double check that your park reference is in there correctly, sometimes ham2adif doesn't pull that in automatically and you'll need to add it to your log or the website will ask you for it. one thing i'd mention is make sure the date and times are in UTC in your log, that trips people up sometimes when they first start. the system is pretty good about flagging issues before you finalize so you'll see if something's off. and yeah paper logging is totally fine, plenty of people still do it, i just use the notes app on my phone which is probably worse than paper honestly

yeah the 18 day window thing trips a lot of people up. basically when a callsign becomes available — like when someone dies or lets their license lapse — it goes into this quiet period before anyone can grab it. after that window closes all the applications for that specific call get processed at the same time, so its not really first come first served, more like a lottery if multiple people applied for the same one. if nobody else applied for yours you should be fine though. as for listing multiple calls, i believe you can actually put in applications for several different callsigns at once, just separate applications each one. some people apply for like 5 or 6 hoping one sticks. i did mine a couple years back and got my 1x2 in maybe 3 weeks total once i figured out the ULS system. the AE7Q website is your best friend for this stuff honestly, way more useful than the FCC site for checking availability and status. good luck with it

timing is everything honestly. i spent way too long just hammering away and wondering why the amp wasnt helping. what changed things for me was getting a second radio so i could actually listen to the pileup behavior on one while the other was ready to transmit. you can hear the rhythm you're talking about way better when your ears arent on the same radio you're about to key. also one thing most people dont talk about — the split offset. everyone crowds 1-3 up because thats what the clusters say. if the op is working 5 up sometimes and nobody's listening because they all see the cluster spot saying 1-2, you can basically have a conversation with the DX. ive gotten some decent ones that way. basically just listen for a full couple minutes before you even think about calling, figure out where the op is actually pulling people from, not where the cluster says to call. the other dirty secret is antenna. a beam aimed correctly beats 1500w into a dipole in the wrong direction every single time and i say that as someone who ran 1500w into a dipole for longer than i should admit.

honestly RemoteHams server infrastructure has been a bit hit or miss in my experience, there are periods where relay latency spikes and i've seen streams die exactly like you're describing. not saying thats definitely your problem but its worth checking their status page or asking in their forum because sometimes its just their end and there's not much you can do on your side. i moved one of my links over to using a direct connection instead of going through their relay servers and stability got way better, less convenient to set up but it holds together a lot more reliably for longer qsos.

so ive been licensed for about 4 months now and every time i get on HF someone is using phonetics for everything, like even when the band is totally clear and there's no QRM at all. my elmer told me it's just convention but i looked it up and it seems like some people treat it like a rule. is it actually required or is it just something people do out of habit? also i keep messing up and saying things like "D for Dog" instead of Delta which i know is wrong but it just comes out that way. does anyone actually care about that on air or will people just think im a newly licensed idiot

So I've been messing around with automating my antenna rotator for the past few months and finally got something semi-functional. Started with a Raspberry Pi 4 but honestly the Arduino Mega ended up being way more appropriate for the actual motor control side, Pi is sitting upstream handling the logging and the web interface I threw together. Basic setup is the Arduino reading a pot on the rotator shaft for position feedback, then driving a relay board to handle the direction and a PWM signal going into a motor controller for speed. The pot side took forever to dial in because cheap pots are noisy as anything and I kept getting jitter that would make the antenna hunt back and forth. Ended up adding a small cap across the wiper and ground which helped a lot, then just did some software averaging on the ADC readings. The Pi runs rotctld so it integrates with WSJT-X and a few other things automatically which is the part that actually feels like magic when it works. Click a callsign on the band map and the antenna just... moves there. Probably took me 40 hours total to get to this point which is maybe not the most efficient use of my time but here we are. Anyone else doing anything similar or have thoughts on whether I should just have bought a commercial controller to begin with. I know the Yaesu interfaces exist but where's the fun in that.

had almost the exact same thing on a friends 7300 last year. turned out to be the driver stage, one of the small transistors before the finals was running hot and not driving the PA properly. the finals themselves tested fine which is kind of counterintuitive because most people jump straight to blaming the PA transistors. before you open it up though, go into the menu and find the RF power calibration section, theres a way to check if the radio thinks its actually outputting 100w internally vs what youre seeing at the connector. if the radio thinks its doing full power but the wattmeter says otherwise, that rules out a software/settings issue pretty definitively and points you toward hardware. also worth checking the voltage at the finals with a meter under load if you can get to the test points, icom put some decent documentation out on that.

also check if someone messed with the IPO or attenuator settings, i know thats probably obvious but ive seen people waste days on stuff like that lol. probably not your issue if its totally dead though yeah. the relay theory sounds right to me, that or the antenna relay on the RF board. good luck with it, 857s are worth fixing if you can get it sorted.

yeah the actual Part 97 text is pretty rough to read if youre not used to it, dont feel bad. the short version for tech HF privileges is youre allowed CW on a bunch of bands but for phone (like SSB voice) on HF you basically only get 28.300 to 28.500 MHz on 10 meters. thats it for voice on HF as a tech. the ARRL has a band plan chart thats color coded by license class and honestly thats what most people actually use day to day instead of reading the raw FCC document. look up the ARRL frequency allocation chart and just keep a copy of it near your radio until it becomes second nature. the main thing is just dont transmit outside your privileges, obviously, but also be aware that on 10m phone you still have to follow all the usual Part 97 stuff about ID'ing every 10 minutes and at the end of transmission, no music, no broadcasting to the general public, all that. most of it is common sense once you know the basics.

this is making me think i should probably actually test my go-kit before I need it instead of just assuming everything is fine lol. im pretty new to all the emcomm stuff but our club has been pushing us to get involved in ARES and I signed up a few months ago. havent done a real drill yet, just the check-ins. question — when you say simplex do you mean like just picking a standard simplex frequency ahead of time and everyone knows to go there if the repeater drops, or is it more complicated than that? i feel like our group maybe hasnt covered this as clearly as they should have

okay so i just got my technician license about three weeks ago and ive been trying to get on some of the local FM repeaters in my area. i can hear people talking just fine but when i try to key up nobody seems to hear me, or at least nobody responds. i figured out that i probably need to program a CTCSS tone but honestly im still a little fuzzy on how the whole thing works. from what i understand the tone is like a sub-audible signal that tells the repeater to open up and let you through? but my radio is a baofeng uv-5r and i kind of just guessed at some settings. i found the repeater listed on repeaterbook and it shows a 100.0 Hz tone but im not totally sure if that means i transmit with that tone or if its what the repeater sends to me or both. and then theres also the offset — the repeater is on 146.820 and i know i need a minus 600 khz offset but i dont know if ive set that right either. also when i do finally get it working, whats the right way to join a conversation thats already going on? do i just wait for a pause and say my callsign or is there more to it than that? sorry if these are dumb questions i just dont want to be that guy who annoys everyone on the repeater lol