Ashley Wilson95

so ive been trying to get winlink going for about two weeks now and im at the point where i just want to throw the laptop out the window. running pat on linux with a signalink usb into my IC-7300, vara fm configured, and i can see the gateway in the map but when i try to connect it just times out every single time. the audio levels look fine to me, the waterfall shows the vara tones going out, but nothing comes back. thing is the RMS gateway i'm trying to hit is only like 12 miles away, line of sight almost, so its not an rf issue. ive double checked the serial port settings and the ptt is definitely keying up the radio, i can see the tx light. not sure if its a vara configuration thing or if maybe that particular RMS node is just down? is there a way to check gateway status somewhere without just blindly trying to connect? also slightly confused about the difference between RMS relay and RMS gateway in terms of what i should actually be targeting as a new winlink user. any help appreciated

honest answer — if you already have the second radio sitting there and you can borrow or buy some bandpass filters, yeah its worth experimenting with, but dont expect it to magically fix your rate. SO2R mostly helps you during the dead spots where your run frequency goes quiet and you can S&P on radio 2 while youre waiting. if you're already running well it can add maybe 10-15% but a lot of that depends on conditions and how smooth your workflow is. the keying interlock issue is real btw. there are a few hardware solutions but a lot of guys just use N1MM with the radio focus stuff set up properly and it handles most of it. you still have to be disciplined about it though, ive def transmitted on the wrong radio more than once in a late night contest moment. the bandpass filters are honestly the bigger deal — running 100w into a tribander on 15 while the other radio is on 20 will destroy your ears and mess with both receivers if you dont have them. Array Solutions or the Dunestar ones are what most people use, not cheap but kinda necessary. your antenna situation is workable for starting out. 40 and 20 are your main contest bands anyway so having separate antennas already is actually decent separation.

the timing thing is really the whole game honestly. took me probably two years of serious DXing before it clicked. what helped me was just spending time listening to big pileups without even transmitting, just watching how the DX op works — some of them have very predictable patterns, like they always come back within a certain window after finishing a log entry, and once you hear that a few times you can start anticipating it. on the tail-ending question, it depends a lot on the op. some DX ops actually appreciate it because you're slipping in right as the previous QSO ends and there's a brief quiet moment before the pile erupts again. but plenty of ops ignore it or it just gets buried anyway. i'd say it works maybe 20-30% of the time in my experience, which is actually not bad compared to just screaming into the pile with everyone else. the guys running split on 17m DXpeditions seem more receptive to it than the big contest-style 15m pileups where everyone is just hammering away. 100w and a 3-el yagi is actually not a bad starting point. ive broken decent pileups with less. the antenna is doing more work than the power in most cases.

could also just be less people on in general, i feel like activity goes in waves. summer always seems slower to me for some reason. also your dipole orientation matters a lot for 40, if youre running it east-west youre gonna miss a chunk of stations. just a thought

yeah the message handling thing is SO real. we did a similar exercise maybe two years ago and our biggest failure was almost identical, people just weren't trained enough on actual NTS formatted traffic to do it under pressure. everyone knows how in a classroom setting and then it all goes sideways when theres noise and stress and someone is standing over your shoulder asking when the medical supply request is going to get relayed what we ended up doing after that was running monthly traffic nets specifically for the ARES members, not just showing up to the regular nets but actually doing practice sessions where we deliberately add distractions and make people handle multiple messages at once. it helped a lot. still not perfect but people are way more comfortable now the coax thing is also something that will never go away i think. doesnt matter how experienced the group is, pre-deployment checklist discipline is really hard to maintain when people are rushing to set up. we literally have a laminated card now that has to be signed off before any antenna goes up at a deployment site. feels a little overkill but after losing time like that during a real activation you start to appreciate the boring stuff

so i finally did my first ever POTA activation yesterday at a state forest about 45 min from me. packed up the ft-891 and my random wire with a 9:1 unun, figured id be set up and making contacts within like 20 minutes. yeah that did not happen lol first the ground was way too rocky to get my stakes in for the antenna, so i ended up just draping the wire over some branches which worked okay i guess. then i realized i forgot the coax adapter i needed so i had to dig through my bag for like 10 minutes to find the backup one i threw in last minute. by the time i was actually on the air it was almost noon and the bands were kind of rough on 40m. managed to squeeze out 11 contacts on 20m before my battery started getting low, so it counts as an activation but barely. still pretty fun though, theres something about just sitting on a rock in the woods making contacts that feels different than operating from home

yeah the visual dots and dashes thing is basically a trap, dont do that, youll just end up translating in your head which slows you way down. the Koch method is what most people actually recommend now, theres a program called LCWO dot net that walks you through it for free. basically you start with just 2 characters at a relatively high speed, like 20wpm character speed, and you dont move on until you can copy them at like 90% accuracy. the idea is you learn the sound of each letter as a whole thing instead of counting dits and dahs. it feels slow at first but it builds the right muscle memory. i spent about 15 minutes a day for maybe 3 months before i felt comfortable enough to actually try a QSO and even then it was brutal but possible. the farnsworth timing thing helps too where the characters are fast but theres extra space between them, gives your brain time to process without teaching you to rely on slow character speed. just dont skip ahead when youre tempted to, that was my mistake the first time i tried to learn

so the band plan vs actual FCC rules thing trips up a lot of people. the short version is the ARRL band plan is voluntary, but Part 97 itself has actual legally binding frequency allocations based on license class. for general on 40m you can operate phone from 7.175 to 7.300, and CW and digital from 7.025 up. so JS8call would fall under the digital/data allocation and youd generally be fine in that lower portion. the thing your friend might be thinking of is the gentlemans agreement that keeps digital stuff below like 7.125 or so to avoid stepping on phone ops, but thats not an FCC rule, thats just how the community operates. 97.305 is the section you want to look at for emission privileges by license class, that one actually lays out what modes are allowed where. worth bookmarking the actual part 97 document honestly, its not as dense as it looks once you get used to how its written as for accidentally transmitting somewhere you shouldnt — one time is not gonna bring the FCC down on you, they have way bigger fish to fry. repeat intentional violations are another story but an honest mistake is an honest mistake

oh man this is such a common thing and honestly the net control guys are used to it, they dont mind at all. when they acknowledge you just say your callsign, your name, your location, and whether you have any traffic or announcements. something like "KD9whatever, this is Mike in Springfield, no traffic" and thats literally it. youre done. net control will say thanks and move on. nobody expects you to give a speech. for the mobile thing, absolutely tell them upfront. most nets have a "mobile and portables" check in round specifically for people who might drop. you just say youre mobile when you check in and any decent net control will note that and not be surprised if you disappear. i did nets for like two years before i felt comfortable and now i net control occasionally and i promise we are rooting for new folks to check in, it makes the net feel alive instead of just the same 6 guys every week.

yeah i went through this same thing about eight months ago. i ended up using an app called Morse-It and also just listened to a lot of slow CW on the bands even before i could copy anything, just to get used to the sound of it i guess. probably didnt hurt. the main thing that tripped me up was i was counting dits and dahs for way too long instead of just hearing the letters as sounds and that slowed me down for a while. still working on getting my speed up but im making contacts so thats something

yeah the analogRead noise on unos is a known thing, the AREF pin is just not great for precision work. one thing that helped me a lot was switching to an external voltage reference — wire a clean 5v reference like an LM4040 or TL431 to AREF and connect it in software with analogReference(EXTERNAL). makes a noticeable difference. also make sure your pot wiper line isnt running near anything switching, even short runs near the H-bridge wires can inject garbage. for the averaging thing, look at exponential moving average instead of a simple rolling average. its basically newValue = alpha * reading + (1-alpha) * lastValue and you tune alpha between 0 and 1. small alpha = smoother but slower, big alpha = faster but noisier. i use something like 0.1 or 0.15 for rotator stuff and it tracks well without being jerky. way less code than storing a ring buffer too. the L298N getting warm is expected honestly, those things drop like 2v across the outputs so theyre burning off a bunch as heat. if you want something cleaner look at the DRV8871 or even just a pair of BTS7960 modules which can handle higher current and run way cooler. depends on what your prop pitch motor actually needs but worth checking.

ok so i just passed my technician exam like two weeks ago and im trying to figure out exactly what the rules are for what i can do. i understand i have HF privileges on 10m and some on 40m i think? but i keep reading different things online and the actual Part 97 document is kind of hard to parse if youre not used to reading legal stuff. my main question is basically around voice vs digital vs CW and where exactly i can operate. also someone at my local club mentioned something about a CSCE and using privileges you havent gotten your actual license for yet and i didnt really understand that. is that a real thing or was he pulling my leg i dont want to transmit somewhere i shouldnt, thats kind of stressing me out honestly

so ive been licensed about 8 months now (general) and just starting to get into DX chasing a bit. everyone keeps mentioning the cluster and DXwatch and QRZ spotting and honestly i wasnt sure if these were all the same thing or totally different tools doing different things spent a couple evenings poking around and i think i get the basic idea now — someone hears a rare station, they post a spot, and that propogates out to whatever network youre connected to. but the part that confuses me is whether QRZ.com's logbook spot feed and DXwatch are pulling from the same underlying cluster data or if theyre separate networks. sometimes i see spots on one that dont show up on the other for a few minutes also is there a way to filter by band on DXwatch? i only run HF and mostly 20m and 40m right now so scrolling through a wall of spots that include 6m and stuff i cant work yet gets a little overwhelming. might be missing something obvious in the settings anyway if anyone has a good explainer on how the whole spotting ecosystem actually works id love to hear it, i kind of learn better from someone just talking through it than reading documentation

so i finally did my first summit activation last weekend, took the ft-818 and a end fed half wave up to a local hill and just threw the wire over a tree branch. wasnt expecting much but managed to get like 14 contacts in maybe 45 minutes which i guess is enough to count. signal reports were all over the place but whatever, people could hear me so thats good enough for a first time the hard part was getting the antenna situated, the tree i wanted to use had all these low branches and i ended up with the wire at kind of a weird angle but it still loaded up fine on 20m. brought way too much stuff in my pack too, definitely leaving the spare battery home next time since the 818 barely touched the internal one anyone else do a lot of local summits? curious what antennas people are running for lightweight stuff

the guy at your club was probably right but also kinda depends on how busy your local digi is. out here in the middle of nowhere nobody cares if i beacon every 20 seconds lol. but yeah in a metro area with a lot of stations on the network you can cause some real collisions and it gets annoying on the RF side. i run SmartBeaconing on my VX-8DR and it works pretty well. one thing tho -- even with SmartBeaconing on you still want to sanity check what its actually transmitting by watching aprs.fi for a bit. sometimes the settings are weird out of the box