James Wilson

so i just upgraded to general last month and im trying to figure out where i can actually operate on 40 meters. i know there are parts of the band i wasnt allowed on as a tech but now im confused because ive been looking at different band plans and they dont all say the same thing. like the arrl chart shows one thing and then i see other charts online that look different and i cant tell if those are just suggestions or actual law or what.
also someone at my club mentioned something about staying away from the band edges and i didnt really understand why. like if my license says i can go down to 7.025 or whatever, why wouldnt i just operate right there if thats where my privileges start? is this an fcc thing or just a courtesy thing people do?
sorry if this is a dumb question, ive been searching around and getting more confused the longer i look

oh man i was in the exact same spot like a year ago. what finally clicked for me was finding a 2m net my local club runs on sunday evenings — super low key, net control just goes around and everyone says hi basically. way less scary than jumping onto HF traffic nets cold.
the special event thing is fun to try even early on, you just call them like any other station. picked up a W1AW operating event contact my second month and they were totally normal about it lol

yeah done almost exactly this with a pi 3 not a zero but the concept is the same. the short answer is you definitely need level shifting between the pi GPIO and the rotator controller — the G-450A runs on 5v logic for its control lines and the pi is 3.3v, so straight connection will either not work reliably or you'll fry the GPIO pins eventually. i used a simple BSS138 level shifter board, cost like a dollar fifty on ebay and does the job fine.
the azimuth sense line from the rotator is actually an analog voltage that varies with position, so you'll also need an ADC since the pi has no analog inputs natively. i used a MCP3008, which is SPI and works great with python. then you just read the voltage, map it to degrees, and close the loop with a little PID controller or even just simple bang-bang control if you dont need it super precise.
hamlib has rotctld which can run on the pi and expose a network interface so your logging software can talk to it. thats honestly the cleanest part of the whole thing once you get the hardware sorted. the $80 adapters are mostly just doing what youre trying to do yourself so yeah, worth building it.

PL tone and CTCSS are the same thing, yeah — PL is just the Motorola tradename that kind of stuck around forever. for accessing the repeater you only need to set the tone on transmit, the receive side CTCSS is a different thing where your radio will squelch until it hears a specific tone coming back at you. most people leave receive CTCSS off so they can hear everything coming through the machine.
as for the no-response thing that's pretty normal honestly. a lot of repeaters especially in smaller areas are just kind of quiet and people monitor but dont always respond to a random callsign. what usually works better is saying something like your callsign and then "monitoring" or asking if the frequency is in use before you start a conversation. some clubs also have specific nets on certain days so you might have better luck catching one of those. dont get discouraged, just takes a bit of time to figure out the local scene

im in pretty much the same boat, just getting into CW for the first time and the iambic modes completely confused me for the first month. ended up just watching a bunch of videos slowed way down to see what my hands were actually doing. one thing that helped me was using the straight key practice mode for a couple weeks before going back to the paddle, just to get my ear back in sync with what correct timing sounds like before i tried to be clever with squeeze keying.

yeah the waterfall on that radio is genuinely addictive, i found myself just watching it for like 20 minutes when i first got mine trying to identify what everything was. the built in scope really does change how you operate, at least it did for me.
for settings i run the TX bandwidth pretty wide on SSB, like around 2.4k, and i backed off the compression to almost nothing because i was getting reports that it sounded processed. if you havent already go into the set menu and mess with the AGC time constants, the default fast AGC on SSB was bothering me on strong signals. slow AGC feels way more natural to my ear. also make sure you updated the firmware if you havent, theres been a few revisions that fixed some minor things.
attic dipole is totally workable by the way, dont let anyone give you grief about it. ive worked europe on 40 from worse situations

so ive been chasing a pretty rare one for a while now, one of those entities that only gets activated maybe once every few years, and the pileup was absolutely insane. we're talking probably 500+ stations calling simultaneously on 17m. i've read all the usual advice about split operating and timing your calls but honestly most of it felt pretty abstract until i actually sat there and worked through it.
what ended up working for me was listening to where the DX operator was actually coming back to — not just the frequency they said they were listening on, but like specifically where in that range they kept pulling calls from. there was definitely a pattern, he kept fishing around 3-4 up from his announced listening freq. so i parked there and cut my call down to just my suffix, sent it once, and waited. took maybe 20 minutes but i got through.
the other thing that helped a lot was just having a decent signal to begin with. im running a TS-890 into a 4 element yagi up about 45 feet and conditions were actually pretty good that day, so that obviously helps. but ive broken pileups with way less too so it's not all about power and antennas.
curious what techniques other people have actually found work in the real world, not just the textbook stuff. especially for ssb pileups which i find way harder than cw honestly.

so the short version is the FCC allocation is the law and the band plan is basically a gentlemens agreement that most people follow. as a general on 40m your phone privileges run from 7.175 up to 7.300 MHz, that's the actual legal limit. anything outside that and you're technically in violation regardless of what anyone tells you.
the band edge thing is about your signal not your carrier. if you're running SSB and you're at 7.300 your signal is going to have sidebands extending above that into territory you're not allowed to operate in. the convention is to stay a few kHz inside the edge just to make sure your whole signal is within your allocation. most people say 7.295 or so to be safe on the upper end, and on the lower end for generals on phone 7.178 or so gives you a little breathing room from the extra class only segment below.
honestly just watch the band for a few weeks and you'll start to see where people actually congregate. the band plan makes a lot more sense once you see it in practice.

100w to a dipole is gonna be tough for the really big pileups like this one. i was struggling too until i switched over to my 3 element yagi, made all the difference. also try listening to exactly where theyre coming back to people - sometimes theyre working a pretty tight split and if you're not in the right window they wont hear you at all
patience is key though, ive spent 3+ hours working some of the bigger dxpeditions before finally getting through