Everything posted by Mod_Dan
-
Getting my first ham license (Technician): how do I find a test session, what's the FRN for, and how should I study?
On finding a session, there are a few places to look. The ARRL has an exam session search, HamStudy has a session finder, and many local clubs post their own schedules. Some VE teams also run remote sessions over video, so check whether your area offers those if in-person dates are scarce. Look at the session listing for registration rules. Some are walk-in, some want you to pre-register so they know how many examiners and test copies to prepare. Bring a government-issued photo ID, your FRN, and a pen or pencil. A basic calculator is fine if you want one, though the Technician test needs very little math. Ask the contact for the session what they accept for payment. Fees are set by the VE team or coordinating organization, not by a single national price, which is why you've seen different numbers. They're typically modest, and the listing or the contact person should tell you. Check the FCC's current fee rules too, in case anything separate applies, rather than relying on old forum posts. A couple of practical tips for test day: read each question twice, because the answer choices often differ by one word. Don't leave blanks, since there's no penalty for guessing. If you pass, you'll receive a Certificate of Successful Completion of Exam (CSCE). If you want to try for General while you're there, the team can often give you the next exam, and a CSCE is time-limited, so keep it safe. Between passing and transmitting: wait until your call sign actually appears in the FCC database before you transmit. In the meantime, listen. Find your local repeaters in a repeater directory, learn how your radio's offset and CTCSS tone settings work, and look up a local club's weekly net so you have somewhere to make your first contact.
-
Keeping RF out of ESP32 and Pico shack controllers: CAT, PTT, antenna switch and rotator interfaces
On the Pi side, Direwolf is mostly about audio levels and PTT discipline. Start by running it with the radio's data or audio output set conservatively and watch the audio level it reports for received packets. The Direwolf documentation gives a rough target for the received level, so check it against your own setup instead of guessing. On transmit, overdriving the audio input is a common mistake. It makes a wide, distorted signal that decodes worse and annoys the neighbours on the frequency. For an antenna switch, a small microcontroller makes sense, but the safe default state matters more than the clever part. Decide what the relays do on power loss or reset, and make sure it can't connect a transmitter to an unintended antenna or leave an open feedline. Switching under power is hard on relay contacts. If your switch doesn't interlock with PTT, add an inhibit line or have the controller only change antennas when the rig is not transmitting. For a Si5351 used as a signal source, remember the outputs are square waves, so they carry strong harmonics. Add a low-pass filter for the band in use before it goes near a receiver or a transmit chain. Calibrate the crystal offset against a known reference, since the default correction is rarely perfect. Keep the I2C lines short, and consider shielding the module if it sits near the LCD and Pi, since both can be noisy. Lastly, for soldering: a ground-plane layout on a proper PCB, or dead-bug construction over copper clad, usually beats a loose perfboard rat's nest for anything RF. A clean joint with the right flux matters more than a very hot iron.
-
Planning your contest year: which major contests fit your station, exchanges to know, and getting logs submitted
I'd add that the difference between 'rules I assume' and 'rules for this year' can matter. Contest sponsors do change categories, bonus points, time limits and band rules, so I'd read the current rules page even for a contest I've entered before. The same goes for QSO parties, where the exchanges and county lists can differ a lot from state to state. On submission, I'd export the Cabrillo file early and look at it in a text editor before sending it. You can check that the header category matches what you intended, the callsign is correct, and the exchange looks sensible on a few lines. Then submit well before the deadline. Many sponsors publish a log checking report or a list of received logs, so look for that to confirm they received yours. If you ran a rover or portable station for a VHF contest, check how grid squares are handled when you move, since each sponsor has specific rules on that.
-
Planning a dual-band mobile install: FTM-500D vs ID-5100A vs TM-D710G, wiring, noise and etiquette
On noise, I'd stress testing in a repeatable order. Check the radio on a weak signal or with the squelch opened, then change one thing at a time: engine on and off, headlights, blower fan, charger, dash cam, USB adapters. If the noise follows the engine RPM, think alternator or ignition. If it appears when you plug in a gadget, that gadget is the first suspect. Cheap USB chargers and dash cams are a surprisingly common source of VHF/UHF hash. On the fusing point, don't replace the supplied fuse with a larger one to stop it blowing. A blown fuse means something is wrong: a short, a bad connection, or the wrong wire. Fix that rather than raising the rating. And don't skip the antenna check. A poorly grounded mount or a damaged coax connector can make a good radio sound bad, and it can stress the final amplifier if SWR is high.
-
Building a 40/20 wire dipole from scratch: wire, feedpoint, choke, and how far to trust the model
On trimming, measure at the feedpoint if you can, or at least use a known length of feedline and keep it the same each time. A NanoVNA lets you see resistance and reactance, not just the SWR dip. The lowest SWR isn't always the exact resonance, especially when the feedpoint resistance is well away from 50 ohms. If reactance crosses zero at 7.05 MHz but you want 7.15, shorten each leg by the same small amount and re-measure. For 40 m, a small number of inches per leg moves the frequency noticeably, so go in small steps. For the choke, a coiled-coax choke is better than nothing and costs nothing, but its impedance depends on the band. It can be good on one band and poor on another because of self-resonance. A ferrite choke on the coax at the feedpoint is more predictable. If your dipole is balanced and the coax drops away at a right angle, you'll see less common-mode current, but a choke is still cheap insurance. One easy test is to move or touch the coax near the shack and watch whether the SWR or reactance reading changes. If it does, the feedline is part of the antenna. Also check your rope and insulators. UV-resistant rope and a simple pulley or weighted line at the far end keep the wire tension steady in wind, which keeps the tuning stable.
-
Making SET and Field Day Count: Scenario Ideas, Net Scripts, and What After-Action Reports Should Capture
One thing that makes Field Day more useful as practice is adding constraints that the contest format doesn't give you. For example, set up one station as an "EOC station" that only handles formatted messages, not contacts. Have a few volunteers write messages in advance, with a mix of precedences and some deliberately awkward text such as numbers, unusual place names, and a few with errors for the receiving operator to catch. Then see how long it takes to get a message from origin to delivery by voice, digital, or both. Another useful constraint is running some of the weekend on emergency power only, with a plan for who is responsible for fuel, batteries, and the changeover. The goal is to see where the weak points are while there's still time to fix them. On net scripts, I'd also add a line for what to do if net control goes silent or loses power. A named alternate net control and a backup frequency, stated at the start, saves a lot of confusion.
-
POTA basics for new activators and hunters: park references, the 10-QSO rule, spotting, and logging
On getting to 10 QSOs, spotting early helps more than anything. Pick a frequency, check that it's clear, call CQ for a minute or two, then spot yourself. Waiting until you've worked a few people before spotting just wastes time. The activity is built around hunters watching the spots page, so being visible matters. On CW, a short call such as 'CQ POTA' followed by your callsign is standard. On SSB, say the callsign clearly and use phonetics, and mention the park reference now and then rather than every transmission. Pileups vary a lot by band and time of day. If the bands are slow, move to another band, because 40 m and 20 m cover different distances and different hours. One logging tip: keep your callsign and park reference in a text file or notes app on your phone. Fat-fingering K-#### into the log is a surprisingly common mistake. Also check that your clock is set to UTC before you start, or at least that you know the offset.
-
Which spotting and lookup tools actually do what? DX cluster vs RBN vs PSK Reporter vs POTA/SOTA spots
A few more notes on the practical side, since the phone-app part of the question hasn't been answered yet. RepeaterBook is useful, but treat it as a starting point. The data is mostly user- and owner-submitted, so tones, offsets and status can be out of date. Check CTCSS or DCS requirements and whether the machine is open or closed before you program it into a radio. Programming software that imports from RepeaterBook saves a lot of typing, but check the import before you transmit. For exam study, HamStudy is built around practice questions with progress tracking and spaced repetition rather than just a block of dumps. Check which question pools and countries it currently covers for your license class, as those change over time. HamCalc and similar calculator collections are handy when you are building antennas or working out coax loss, impedance matching, or similar. Verify results against a second source if the numbers matter for something like a feedline run or a safety calculation. For maps, a Maidenhead grid square map is a good bookmark, especially for VHF contests, satellite work and POTA/SOTA logging, where you often need to give your grid. Many logging programs can work it out from your coordinates, but it is easy to enter the wrong one, so a map check is worthwhile. For propagation, solar flux and K index are quick context, but they are not a prediction for your path. A low K and a decent SFI mean conditions are good on average, but the best evidence is still what PSK Reporter and RBN show for your own location right now.
-
Getting from 5 to 20 WPM: what actually moves the needle, and where people stall
For the jump to real QSOs, there's a case for starting with structured exchanges before ragchewing. A basic contact has a predictable shape: CQ, call signs, signal report, name, location, and sign-off. Once that pattern is familiar, you know what's coming and can concentrate on hearing it correctly. Slow-speed CW nets, where they exist in your area, can be a gentle place to start because the format is predictable and operators usually expect new CW users. Check local club or net listings for current schedules instead of relying on old information. Contests are good for call sign copy and speed under pressure, but a big contest weekend can be a lot at 15 WPM. Many operators start by listening, copying call signs without transmitting, then answer a few stations at the slower end of the band before calling CQ. Staying in the lower-speed segments and asking for QRS ('please send more slowly') is a normal thing to do on the air. On decoders, a middle path: copy by ear and write it down, then turn on a decoder only to check afterward. If it disagrees with you, listen again to find out why. That keeps the ear in charge and still gives you useful feedback, especially on call signs where one wrong letter makes the contact not count.
-
What makes a rig a keeper: boat anchor charm vs. modern SDR convenience?
For me the keeper test is usually whether a radio is still enjoyable when the novelty wears off. A lot of gear is exciting for the first week and then turns into something you tolerate. The rigs that last tend to have good ergonomics: a tuning knob that feels right, audio you can listen to for hours, and controls you can reach without thinking. That's where I think vintage gear gets a lot of its reputation. A dedicated knob for each main function is hard to beat, even when the receiver specs lose to a modern SDR on paper. On the other hand, the waterfall on a modern radio is genuinely useful for finding activity, spotting a drifting carrier or seeing what's causing a local noise problem. I wouldn't call it a gimmick. A good middle path some people take is a modern primary rig plus one older radio kept around for fun, or a vintage receiver paired with a modern transmitter. It's less pure, but it can get you the best of both.
-
Starting Morse from zero: Koch vs Farnsworth, which trainers to use, and how do you stop translating in your head?
Koch and Farnsworth solve different problems, and you can combine them. Koch is about the order in which you learn characters. You start with just two characters sent at a fairly fast character speed, commonly 18 to 20 wpm. You copy random groups until you reach about 90 percent accuracy, then add one new character. The point is that you never learn to count dits and dahs, because at that speed there's no time. Each character is a single sound pattern, like a short word. Farnsworth is about timing. The characters are sent at a faster speed, but the gaps between characters and words are stretched, so the overall speed is lower. This gives you time to recognize each character as a whole. As you improve, you shrink the gaps until the spacing is standard. A common combination is Koch character order with Farnsworth spacing, so you have a fast character speed, extra gap time, and one or two new letters at a time. If you use a trainer that lets you set character speed and effective speed separately, keep the character speed fixed and only change the spacing as you improve. Dropping the character speed to make things easier defeats the purpose. On tools, LCWO.net is a free browser-based trainer built around Koch. It tracks your progress and offers different exercise types such as random groups, words, callsigns, and plain text. That's convenient because you can practice from any device and your lesson level is saved to your account. G4FON's Koch trainer is a downloadable program with similar ideas, and it's good if you want offline practice and fine control over speed and tone. One is enough to start. Pick whichever you'll actually open every day. For apps, check what a given app actually does before relying on it. Some are true Koch trainers and some are just a character chart with audio, and several have similar names. Aim for a sidetone somewhere around 600 to 700 Hz, whatever you find comfortable, and keep it the same so your ear gets consistent patterns.
-
Choosing a handheld: Baofeng vs FT-65R vs ID-52A vs TH-D75, plus what to sort out before an emergency
A useful way to frame it is to decide what you want the radio to do before comparing brands. If the answer is local repeaters, simplex and a basic emergency kit, a cheap analog dual-bander is hard to argue with, and the money saved is better spent on a spare battery, a proper antenna and a programming cable that works. Digital modes are fun, but they only pay off if your area has active D-STAR or DMR repeaters or reflectors you'd use regularly. One caution on CHIRP: the software is only as good as the data you load into it. Before you trust a repeater entry, check offset, tone and any access restrictions against the repeater owner's listing or the local coordinator. Directory data can be out of date, and a wrong offset looks like a dead repeater.
-
How do you separate real ham radio news from hype? Building a routine for gear, band conditions, and FCC/ARRL updates
For band conditions, I'd add that numbers can mislead if you read them alone. A decent solar flux value doesn't guarantee a good path, and a high K-index doesn't always shut everything down. It depends on your latitude, the time of day, and where you're trying to reach. Polar paths suffer first in a disturbed geomagnetic field, while mid-latitude paths can hold up better. My practical check is to look at what is already being heard. Open PSK Reporter on the band you care about, filter by your region, and see whether stations are actually decoding each other. If FT8 spots are appearing on 10 meters across the path you want, that is a real opening, whatever the forecast said. If you can't find evidence, the beacons are a quick sanity check. For FCC and ARRL news, I'd separate "proposed" from "adopted" in your own notes. Comment periods are the part where members can actually take action, so those are worth putting on a calendar. For club news, a simple monthly email or a pinned post with the net schedule, repeater changes, and upcoming field days does more for members than a flood of links.
-
Building a go-kit that works for both SOTA and POTA: where do you trim weight and where do you not?
On the antenna side, the main thing with an EFHW is that the feedpoint impedance is very high, in the range of a couple of thousand ohms, so the transformer and the feedline matter more than people expect. These antennas usually have no true ground or counterpoise, so the coax shield often becomes part of the antenna. That is why you will see common-mode current: RF on the shack side, a rig that misbehaves, or a SWR reading that changes when you touch the coax. A small choke near the transformer, or a few turns of coax on a ferrite, is cheap insurance. Keep the radiating wire clear of the pole where you can, since a wet or lossy fiberglass pole or nearby foliage will pull the resonance down in frequency. Linked dipoles are the other camp. They are resonant on each band with links that you open or close, which means you walk to the antenna to change bands, but you get a balanced antenna with predictable behavior and can often run without a tuner. For a single-band park activation that is fine. For band hopping to chase contacts it gets old quickly. An EFHW with a tuner or one that is cut for 40, 20, 15 and 10 m is more convenient, though it is worth checking the SWR on each band before the hike, since trimming in a field is harder than in a backyard. For the pole, guying at the top section or just below the thinnest joint helps a lot. The upper sections are the weak part, so many people set the pole slightly shorter than its maximum and leave the last section partly collapsed. Hose clamps or tape on the joints keep sections from creeping down. Avoid any overhead power lines, and never put up a pole when thunderstorms are anywhere near.
-
Starting EME: what really limits 2 m, 70 cm, 23 cm and 10 GHz moonbounce stations?
On 23 cm and above, the story shifts from array gain to pointing and feed efficiency. A reasonable dish (a few metres in diameter) with a well-matched feed can give good gain, but the feed has to be placed at the focal point with correct illumination, otherwise you lose gain and add ground noise from spillover. Feed-point preamps are practically standard. At 10 GHz the receiver front end is typically at the feed itself, because even a short length of coax would waste the sensitivity you just paid for. Pointing accuracy rises sharply with frequency. At 1296 MHz, a 3 m dish has a beam of several degrees, so a crude rotator and a well-calibrated tracking program are enough. At 10 GHz, the same dish has a sub-degree beam, and the moon is about half a degree across. You need accurate mounts, encoders or a calibration routine, and typically a way to align on the sun or moon using noise measurements. A common approach is to peak the receiver output on the sun, then use the moon-noise increase over cold sky as a system check. A visible moon-noise increase tells you the antenna, feed and receiver are generally healthy, while being easier than waiting for an echo. Libration spreads the returned signal in frequency, and the spread grows with frequency, from a fraction of a hertz or so at VHF to tens of hertz at 10 GHz. The spread reduces the peak signal-to-noise ratio of narrowband tones and makes the signal flutter quickly. That is why the sub-mode must match the band: a narrow sub-mode may fail on 10 GHz where a wider one succeeds. Check the WSJT-X documentation and the current practice of the stations you want to work, as guidance changes. The spread shown in the Astronomical Data window is useful for deciding how hopeful a sked is. Frequency stability and Doppler also matter. Moon Doppler shifts amount to a few hundred hertz at 144 MHz but several kilohertz at 1296 MHz, and far more at 10 GHz. Use a GPS-disciplined reference for your transverter, and use Doppler tracking in the software so your signal arrives on frequency at the other station. For own-echo testing, remember that a modest 23 cm station may not hear its own echoes reliably, so moon noise or a calibrated test with a known partner is better evidence. For circular polarization, reflection reverses the sense, so stations must agree on a convention for transmit and receive sense. Many choose linear polarization with a rotating feed to deal with the spatial offset instead. Either way, confirm the plan with your sked partner before the window opens.
-
Sorting out QSLs: LoTW, eQSL, QRZ, Club Log OQRS, bureau and direct cards. What do you use for what?
I'd treat it as tiers. Upload to LoTW routinely, because that costs nothing but a few minutes and covers DXCC. Then keep a short list of the entities or stations where LoTW isn't likely to produce a match. Those are the ones where paper makes sense. For that paper tier, check the QSL route before sending anything. Club Log and QRZ pages often list a manager, bureau preference, or direct address, and it's worth confirming the information is recent. Sending a direct card to a stale address wastes postage and creates a slow, avoidable failure. If the page says bureau only, a direct envelope with dollars might even be unwelcome. One more tip on LoTW matching: if a QSO isn't confirming and you know the other station uploads, compare your logged time, mode, and callsign against theirs. Portable and special-event callsigns are a frequent cause, because the certificate has to correspond to the call used on the air.
-
CW toolbox check: what to fix first when your copy or sending stops improving
I'd start with the paddle setup, because it's cheap and it affects confidence immediately. Set the contact gap fairly wide at first and the tension a bit firmer than seems natural. Most unwanted characters come from paddles that are too sensitive, not from bad technique. Then decide on iambic Mode A or B and stick with it for a few weeks so your hands can learn one behavior. If you switch between keyers on different rigs, it's worth checking that they use the same mode, or you'll get odd results on one of them. For receive training, I'd keep the character speed fixed and only shrink the spacing between characters. Changing both at once makes it hard to know why copy broke down.
-
Breaking pileups on rare DX: split, timing, tailending and what changes on the low bands
For DXpedition planning, the most useful way to think about it is as a logistics problem first and a radio problem second. Targets like Clipperton and Bouvet are rare because access is difficult: weather, landing conditions, permits, ship time, and the cost of getting people and equipment there can all decide whether an operation happens. That means the radio plan has to be robust. Typical planning issues include power, spare antennas and cables, band filters, station separation, interference between transmitters, and how to keep multiple bands and modes active without the stations disturbing each other. Club Log is useful on both sides. For chasers, it can help you see which entities are most needed and where your own log has gaps, and many DXpeditions upload logs so you can check whether your contact appears. For planners, it helps show where demand is, which bands and modes may need extra attention, and whether a particular continent is under-served. Still, treat it as one input. Don't send repeated questions on the air asking whether you are in the log. Check the expedition's published log search or OQRS page after upload instead. Etiquette ties it together. Don't tune up on the DX frequency, don't call after you've been logged, and don't answer questions meant for another station. If the operator is asking for a specific call area, stay out unless it is your turn. If you made a mistake, wait a moment and then try again. A pileup that stays orderly has a better chance of making many more QSOs than one that collapses into noise and repeated calling.
-
Making SET and Field Day count: practicing message handling, net discipline and served-agency work before the real event
I'd add a point about scenario design for SET. Exercises that are too clean tend to teach less. Injects help, such as a repeater going offline mid-net, a shelter manager changing the request, a message arriving with an incomplete address, or a station having to switch to battery power with a limited run-time. Keep the injects realistic and within the scenario, and make sure the exercise is clearly marked as an exercise on the air so it isn't mistaken for a real emergency. Many groups use a standard phrase like "this is an exercise" at the start and end of transmissions. For the AAR, collect input from several sides before the debrief: net control, field operators, any agency observers, and whoever managed logs. People remember different things, and operators in the field often see problems net control can't. Writing observations down while they are fresh matters more than writing them up neatly. Then sort the findings into strengths, areas for improvement, and corrective actions, which is the same basic structure many emergency management exercises follow. Check your own jurisdiction's guidance, since served agencies may have specific formats they would like you to use. Finally, test the boring parts: power, antennas, go-kits, logs, forms, pens, maps, and printed copies of the net script. Digital tools are great until a laptop battery dies, so keep a paper fallback for the things you can't afford to lose.
-
Building a wire antenna from scratch: where do you spend effort first, and what do you verify before trusting the SWR?
On the prototype versus model question, one useful approach is to do both and let the model set expectations rather than numbers. A model tells you that a dipole at 30 ft will have a different feedpoint impedance than one at 60 ft. Only the antenna on your lot tells you where it actually resonates. Trees, gutters, and the slope of the land all move things. Cutting a bit long and trimming in small steps, say a few inches per side at a time, avoids chasing your tail, and cutting both legs equally keeps the antenna balanced. Marking the wire with tape or a permanent marker at each trim point makes it easy to retrace your steps. For the choke, a common checkpoint is to measure with and without it, with the coax routed differently. If the analyzer reading shifts when the feedline moves, the choke isn't doing enough. Several smaller chokes spaced along the line can also work better than one big one, though what's best depends on the bands.
-
Matching the digital mode to the path: decode thresholds, time sync, CAT and audio setup
One point worth adding about thresholds: the quoted figure is the limit for decoding, not for a useful QSO. A QSO needs several decodes in a row, and fading can knock out one of them. In practice a path sitting right at -20 dB on FT8 will give you many incomplete exchanges. FT4 is a good fit for contests and busy bands because the 7.5 s period halves the exchange time. You give up a few dB and use more bandwidth. For quiet, long-haul work, FT8 or Q65 on a longer period is usually the better choice. JS8Call uses FT8-style modulation but adds free text, directed messages and relaying. It has several speeds. The slower ones decode weaker signals but take noticeably longer to send a message. If you only want to see who can hear you, WSPR gives you propagation data without a QSO, and the spots can show whether a band is open before you call CQ.
-
New to ham radio? Share your first QSO, first radio, and what you'd tell the next newcomer
On the 'what to buy first' question, I'd gently push back on spending much on the radio before you know what you want to do. A handheld is a fine start for local repeaters, but if your interest is HF, the antenna and feedline will matter more than the transceiver for a long time. A decent dipole or end-fed wire with a proper feedpoint, sensible coax, and a way to keep it away from power lines will do more for your signal than an extra 50 watts. Common early mistakes I see discussed over and over: buying an amplifier before the station is working well, ignoring SWR and feedline loss on higher bands, skimping on safety around power lines and lightning, and skipping RF exposure basics. Another one is never going to a club meeting because you feel you don't know enough yet. That's literally the point of a club. Most have licensed members who like helping with first antennas, radio programming, and field days. For a first contest, a casual one is a good choice. Even making five or ten contacts in a state QSO party or a sprint-style event teaches you exchanges, logging, and listening on a busy band without much pressure. Just check that event's rules and your license privileges first.
-
Studying for the Amateur Extra (Element 4): which topics deserve the most time, and what do the full privileges get you?
On what Extra gets you: it grants all amateur privileges on every band. The most visible change is the Extra-only segments at the low end of 80, 40, 20 and 15 meters, plus some extra phone spectrum on 75 and 40. Exact band edges change with rule updates and I don't want to quote kilohertz from memory, so use the current ARRL or FCC band chart for the numbers. Beyond band edges, a few practical things come with the license: You can serve as a volunteer examiner for all license classes, once you are accredited through a VEC. For many clubs, an Extra is what lets them run enough exam sessions. You become eligible for the shorter-format call signs in the Group A range, either through a vanity application or by upgrading into one. Whether that matters to you is personal preference. The other benefit is the theory itself. The exam material on filters, feedback, mixers, dynamic range, and impedance matching helps if you build or modify equipment. Questions about receiver blocking and intermodulation, for example, map directly onto reading a receiver review or choosing a filter for a crowded contest weekend. For Part 97, don't leave it for the last few days. The questions often test the exact wording of a rule, such as who is responsible for a station's emissions, what a control operator may do, or restrictions on certain operating modes. Read the rule text, not only the pool explanation. And as the other reply suggested, confirm the current question pool effective dates before you buy a study guide, because an outdated book can cost you points.
-
POTA basics and field habits: 10 QSOs, park references, spotting, two-fers and logging, what trips people up?
For the first 10 QSOs, the usual advice is to pick a band and mode that fits your station and the time of day. 40 m can work for regional contacts when 20 m is quiet, and 20 m tends to give wider coverage in daylight. Get your spot out early so hunters can find you, then keep your calls short. A callsign and signal report is all most hunters need, so don't make them wait while you chat. If you are on SSB, say your callsign clearly and use phonetics. On CW, a steady speed you can copy reliably beats going fast and asking for repeats. Also consider a backup plan. If the band is poor or noise is high, a second band or mode can save the activation. Switching bands is often easier than fixing a noise problem at the park. Many people try to log a few more than 10 in case of a bad call, a duplicate or a log problem.
-
Combining WWFF and POTA activations: KFF references, the 44-QSO target, logging and operating tips
For logging, I'd keep one master log and export two ADIFs from it, one for each program, rather than editing a single file twice. Most logging software lets you store the reference in a field that exports as MY_SIG and MY_SIG_INFO, but how it does so varies, so test with a small file first. Run a test upload for POTA and one for WWFF and see what each system flags. Mismatched callsigns, missing reference fields and time zone errors are common reasons for rejected or unmatched QSOs. Also note that the POTA and WWFF reference lists are maintained separately. A park you assume has both may only have one, or the KFF area may cover a different footprint than the POTA park. If the boundary is unclear, look at the map for the reference and pick a spot clearly inside it. Stay within the access rules for the site, and check for any permit or permission requirement before setting up antennas. Some areas restrict where you can put masts, run cables or camp. For hunters, the same habit applies: log the reference exactly as it was sent, and only credit what you actually copied. If a station gives two references, log them as two separate references in the right program, not combined in a single field.