Paul Wilson

yeah the timing thing is huge and most people never figure it out. ive watched pileups on the SDR panadapter and its actually kind of wild to see — you get guys transmitting over the DX op, before they're done, during the response, all of it. its chaos. the ones who break through are usually the ones who transmit in like a very short window right after the DX finishes and before the pile explodes again. the frequency prediction thing you mentioned is real too. experienced ops on the DX side often have a pattern even if its not obvious. some work up the band, some work down, some go random but even random has tells if you listen long enough. i usually spend at least 5-10 minutes just listening before i ever key up. also running barefoot when everyone else is running amps isnt ideal but a good antenna beats raw power almost every time in my experience. my 3 element yagi at 50 feet does way more for me than when i was on a dipole with a linear.

oh man i went through the exact same confusion when i first started. took me a while to realize that dxwatch is basically just a front end for whats already on the cluster network, its not its own separate thing. once that clicked it made more sense why the spots sometimes feel stale. for the QRZ app specifically i think theres a setting buried in the profile or preferences to enter your grid square, at least there was last time i used it. might be worth poking around in there. and honestly dont stress too much about having the perfect setup right away, half the fun of dx chasing is just spinning the dial after you see a spot and hearing whether the signal is actually there. sometimes it is, sometimes it faded out five minutes ago and thats just how it goes.

yeah you can absolutely log for both at the same time, lots of people do that, especially if the area qualifies under both programs which happens more than you'd think with national forests and refuges. the threshold for WWFF is 44 contacts to count as a valid activation, not 10 like POTA, so you do have to put in a bit more work. some activators find that a little daunting at first but honestly if you're already comfortable running a pileup you'll get there. for logging i use HAMRS for field stuff and it exports adif just fine, then i upload to the WWFF logbook portal separately from whatever i do with pota. a few guys i know use Log4OM which can handle both uploads more or less automatically but i havent messed with that myself. the spotting network is definitely quieter than pota overall, the WWFF community is a bit more spread internationally so you get a lot of European chasers which is actually really cool if you're on HF. dont be surprised if you get a pile from DL and PA stations at weird hours

ok so i just passed my general last month (finally) and i've been reading about vanity callsigns and i'm honestly more confused now than before i started. like i understand you can apply for a specific call through the FCC ULS but i dont really get how the sequential process works if you don't apply for a vanity. right now i have a 1x3 call from when i got my tech a couple years ago and honestly its not the worst but i'd love something shorter eventually. my elmer was telling me about 1x2 calls being available in some districts and how there's a whole system for who gets priority but he kind of lost me halfway through. does the sequential process just automatically assign you the next available call in your district? and if i apply for a vanity do i lose my current call in the meantime or does it stay until the new one is approved? i don't want to be callsign-less even for a day lol. also is there a fee now or did that change again, i've seen conflicting stuff online about this.

In my VE sessions, I consistently see students struggle with the decibel questions and frequency/wavelength conversions. The good news is there's only one possible decibel question from group T5B per exam, and maybe just one decimal conversion math problem. Focus your energy on the rules and operating procedures instead.

could also just be the Flex itself going into some kind of idle state? i dont use RemoteHams but i remote my 6300 over SmartSDR and ive seen it do weird things when the DAX audio pipeline gets confused. probably different issue but worth checking the Flex event log on the remote machine if you have access to it. sometimes theres stuff in there that doesnt show up anywhere obvious