Everything posted by Mod_Mike
-
Studying for the Technician exam (Element 2): how should I use the question pool without just memorizing letters?
For understanding versus memorizing, I'd build study around a few mental pictures that cover many questions at once. Repeaters: a repeater listens on one frequency (its input) and retransmits on another (its output). The difference is the offset, which is conventionally 600 kHz on 2 meters and 5 MHz on 70 centimeters. Some repeaters need a CTCSS (sub-audible) tone on your transmit signal before they open. Once you see that, questions about offsets, tones, and why you might listen on the input frequency to check whether you can reach someone directly on simplex become easy to reason out. Privileges: Technicians have full privileges on amateur bands above 30 MHz, plus limited HF privileges. Learn the VHF/UHF bands as named bands (6 m, 2 m, 1.25 m, 70 cm) and the general idea of which modes are allowed. Check exact band edges and the HF segments against a current FCC Part 97 summary, because the exam often asks what you may do where. License terms and operating practices: licenses last 10 years and have a grace period for renewal, and you should know the ID requirement (call sign at the end of a communication and at regular intervals during it). These are a handful of facts, so flashcards work well here. RF exposure and safety: know what an RF exposure evaluation is for, that limits depend on frequency and power, and the standard safety habits around towers, grounding, lightning and batteries. This is the kind of material that sticks better if you picture an actual station. For practice tests, take one early and untimed to find weak subelements, then study that section, then retest. If you keep getting the same question right only because you recognize its wording, rewrite the question in your own words and see whether you can still explain it.
-
SSB audio checklist: mic gain, ALC, compression, EQ and bandwidth for clean signals and weak-station work
On filters, there's a trade-off. A 2.4 kHz receive filter is a good default, but if the band is busy and the weak station has an adjacent strong one, narrowing to around 1.8 to 2.0 kHz may help more than any noise reduction. The voice will sound duller, but it is often more readable because the interference is lower. Try shifting the passband too: with LSB or USB, the low-frequency edge often has more effect on how "boomy" a voice sounds, while the high edge affects clarity and sibilance. For DX, a flatter, lightly processed signal with the low end cut generally gets through better than one with a lot of boosted treble. If you hear that a strong station near you is wide, don't copy the sound, copy the habit: check your own signal with a receiver or SDR, because splatter is easier to see on a waterfall than to hear on your monitor.
-
Field station layout for a 24-48 hour deployment: what order do you set up power, antennas and noise control?
I'd do the noise survey earlier than the post suggests. Put the receive antenna up at a temporary low height first, with every power source and accessory running, and look at the S-meter or an SDR waterfall before committing to the full mast. If the generator or a charger is raising the floor on 40 m, it is much cheaper to move a power cord or swap a charger now than to relocate the antenna after it is guyed. On LiFePO4, check three things before the event. First, charge termination voltage: most packs expect about 14.2 to 14.6 V, so make sure the generator charger and the solar controller are both set to a LiFePO4 profile and not an AGM one that might overcharge or undercharge. Second, cold: many BMS units refuse to charge below freezing, which can leave you with a bank that discharges fine but won't accept solar. Third, the BMS current limit: a pack rated for continuous 100 A is fine for a 100 W rig, but if you add an inverter, check the surge rating too. One more small point: with a LiFePO4 bank, voltage is a poor gauge of state of charge because the curve is so flat. A shunt-based monitor is worth having so you know how much capacity is left when the sun disappears or the generator runs out of fuel.
-
Pi, Pico or ESP32 for shack automation? Where to split rig control, SWR sensing, rotator and antenna switching
RF immunity should probably be the first design criterion, ahead of which board is faster. A microcontroller that works on the bench can misbehave with a few hundred watts on HF a few meters from it. The usual suspects are common-mode current on USB, serial and sensor cables, and RF getting into ADC inputs and I2C lines. Some habits help regardless of platform. Put the board in a metal enclosure where practical, and bond it to the station ground. Put ferrite chokes on every cable that leaves the box. Add small bypass capacitors at ADC pins, and keep sensor leads short or twisted. Run I2C at a modest speed and keep the wiring short, since long I2C runs to a display or an Si5351 board pick up junk easily. Relays and motors need flyback diodes or snubbers, and they should have their own supply path rather than sharing a rail with the ADC reference. For the CAT cable, a USB-serial adapter is convenient, but the USB cable is also an antenna. Galvanic isolation (an isolated USB hub or an optoisolated serial stage) is worth considering if you see decode errors or dropouts only while transmitting. Dropouts that correlate with transmit are almost always RF, not software.
-
VHF/UHF antenna choices: J-pole vs slim jim vs 5/8 wave vs collinear, and where the feedline and connectors fit
The mixed-use question usually comes down to which job is hardest. For local FM and repeaters, an omni on a mast works for most people. A J-pole or slim jim is a good place to start, as long as the feedline exits the antenna cleanly and does not run along the mast for the first several feet. Add a choke at the feedpoint and see whether the SWR still changes when you touch or move the coax. If it does, the coax is radiating. For satellites, I would not try to make the same antenna do both. LEO FM passes are short and the signals are weak, so the gain and polarization handling of a handheld yagi or a dedicated circularly polarized setup is worth having separately. A fixed vertical omni can still catch the high part of a pass on strong satellites, but the nulls will be obvious.
-
EME from 2 m to 10 GHz: what each band asks of your station (JT65/Q65, polarization, libration, skeds)
On minimums, it helps to separate the two goals you mentioned. Working stations with huge arrays is a different problem from working other modest stations, because in the second case both ends are weak and neither can carry the link. A smaller station can often get a first contact by choosing the right partner, while a large station on the other end adds margin without changing what you need to fix at your end. The biggest hidden losses are usually in the receive chain. Coax loss between the antenna and the preamp adds directly to noise figure, so on 2 m and 70 cm the preamp belongs at the antenna or array, not at the shack. On 23 cm and up the preamp should be right at the feed. The relays that switch it also have loss. Sequencing is the other trap: the preamp relay must be isolated before the PA keys, and the PA must stop before the relay releases. Many preamp failures come from hot-switching, not from age. On dishes, spillover noise and feed illumination are the two things people tend to underestimate. A feed that is too wide sees warm ground, which looks like extra system noise, while one that is too narrow wastes gain. The rule of thumb that surface errors should stay below roughly a sixteenth of a wavelength is a good sanity check. At 23 cm that is a few millimetres, which most builds can manage. At 10 GHz it is around 1.8 mm, which is much harder. For power, the legal limit varies by country, so plan the station around what is allowed where you are, and don't assume 1 kW. Measure power at the antenna feed, after the harness, the relays and the cable, because the number at the amplifier output is not the number the array sees. With long runs of hardline, 100 W at the amp and 100 W at the feed are not the same thing. Finally, a system check on the higher bands is to compare moon noise against cold sky, and sun noise if you have it. On 2 m the moon noise increase is too small for most stations to see, but on 23 cm and above it is a meaningful test of the whole chain, feed and dish included. If the measured number is off from what you expect, work out why before you start trying to make contacts.
-
Building a first go-kit for SOTA/POTA: EFHW or linked dipole, and what else goes in the bag?
On EFHW versus linked dipole, I'd split it by how much time you expect to spend on the hill. If you plan to work two or three bands and then leave, a linked dipole for 40 and 20 is hard to beat for efficiency and simplicity, and there's no matching box to fail. If you want to hop around looking for the best band as conditions change, the EFHW wins because you can just retune at the radio. With the EFHW, the counterpoise and choke details matter more than people expect. A coax run that isn't choked can become part of the antenna, which shows up as RF in the shack (or on your hands) and SWR that shifts when you move the cable. Putting a choke at the rig end and keeping the feedline routed away from the radiator usually calms things down. Also test the antenna at home and write down the resonant points for each band, so you aren't trimming wire on a windy ridge. For the pole, guying at about two-thirds height with light cord and a few small stakes is usually enough. If there's no ground to stake into, you can lash the base to a fence post, a tree or a pack with the extra weight on top.
-
Planning a first POTA activation: park references, 10 QSOs, spotting and what to log
On antennas and power, a lot of activators run 5 to 20 watts on CW or SSB with a simple end-fed halfwave, a linked dipole or a vertical with a few radials. POTA has no minimum power, so a modest rig works as long as the band is open and you're spotted. A common beginner mistake is spending all the setup effort on a fancy antenna and then not self-spotting. Without a spot, hunters often don't know you're there. For band choice, 40 m and 20 m are common starting points because they usually give a good mix of nearby and distant hunters. Pick the band by time of day and by your equipment. If the first band is slow, move rather than calling CQ into dead air. If you're on SSB or CW, say the reference clearly, for example 'CQ POTA' plus your call, and repeat it often so stations tuning past can catch it. Read the park's own rules before you go, because they vary a lot. Some places don't allow stakes, wires in trees or blocking roads, and some restrict activity to certain areas. Being inside the park boundary is required, so check the map rather than assuming the parking lot counts.
-
Organizing an award chase: DXCC, WAS, WAZ, WPX, IOTA, POTA and SOTA without drowning in logs and QSLs
I'd keep the awards in tiers instead of chasing everything equally. WAS and WAC are quick wins and good for learning the application workflow. DXCC and WAZ are the long-term core. WPX tends to come along on its own through general operating, and IOTA and the Marathon can be 'when the opportunity appears' goals. One thing about WAZ versus DXCC: the lists overlap but don't match. Some DXCC entities span more than one CQ zone, so a single entity may not give you the zone you need. For big countries you need to know the actual location. A rare-zone chase can be a different plan from a rare-entity chase, with different targets. For POTA and SOTA, I'd treat them as separate from the QSL-based awards. They're about the activity and the logs in the program's own system, so the question is whether the activator has uploaded and whether your details match. Chasing a DXCC entity by hunting a park or summit is a nice side effect when the activation is from a new entity, but it only counts for DXCC if the contact is confirmed in a way ARRL accepts, such as LoTW. A POTA log alone won't do that. Finally, read the application instructions once before you apply. The documentation requirements for paper cards, LoTW and any special endorsements are all spelled out, and a minute spent there is much cheaper than a returned application.
-
Q codes and ham shorthand: what QRM, QSY, QTH, 73, K vs KN and RST actually mean on the air
Here is a pass through the Q codes. The formal rule is that a Q code followed by a question mark asks the question, and the same code without it answers or states it. So QRL? means "is this frequency in use?" and QRL means "yes, I'm busy, please don't transmit here." QRM is man-made interference, such as other stations or electrical devices. QRN is natural noise, mainly static from thunderstorms. QRP means low power, and QRO means high power. QRP is usually taken as 5 watts or less on CW and 10 watts PEP on SSB, though that is a convention rather than a legal definition. QRO has no firm number. It generally means you're running more power than usual, or the legal maximum. QRT means stop sending, and in practice "I'm shutting down the station." QRZ? means "who is calling me?" and you hear it when someone catches a weak or partial call and wants a repeat. QSL means "I acknowledge receipt" or "I confirm." It also means the confirmation card, which is why people say "QSL card." Confirmations today are often electronic, through services like LoTW or eQSL. QSO is a contact, a two-way conversation. QSY means change frequency, so "QSY 14.250" is a proposal to move there. QTH is your location. QSB is signal fading, the rise and fall in strength you hear on HF. Some others are worth adding to the sheet. QRS means send more slowly, QRQ means send faster, QRX means stand by, QRV means I'm ready, and QRG is your exact frequency. Q codes also work on phone, but only a handful are common there: QTH, QSL, QSO, QRM, QRN, QRZ and QSY. For 73 and 88: 73 means best regards and is a standard sign-off. It is already plural, so "73s" is generally frowned on. 88 means love and kisses. It is traditionally affectionate or jokey, and often goes to a spouse, a friend or a YL, so use it with care on a casual contact.
-
LoTW, eQSL, Club Log OQRS, bureau or direct: how are you confirming contacts, and what actually counts for DXCC?
On the paper side, the thing that saves the most grief is reading the QSL route before spending a stamp. Some stations only want bureau, some only direct, some say "LoTW preferred, no cards", and some run everything through a manager. Sending a direct card with the wrong return postage to a station that only uses the bureau is an easy way to get nothing back. Many operators publish exactly what they want, including how much to include. If it says OQRS only, use Club Log and do not mail anything blind. For direct requests, keep the package simple. Put your card with all QSO details filled in, a clean SASE with your address legible, and the postage they asked for, and write the callsign you worked in a way the manager cannot misread. A short note can help, but do not make it long. For bureau, remember that cards are sorted by the suffix or prefix of the callsign, so your outgoing cards should be sorted according to your bureau's rules, and you should expect incoming cards in batches. Do not worry if you wait many months. Treat anything quicker as a bonus, and keep the QSO in your log until the confirmation actually arrives.
-
EME station planning: what 2 m, 70 cm, 23 cm and 10 GHz really require (JT65/Q65, polarization, libration, skeds)
On 2 m and 70 cm, the first thing I would put on the checklist is receive noise, not just gain. Four good Yagis behind a lossy feedline, or a preamp behind a slow relay, can easily give up what you gained by adding two more antennas. Put the preamp at the array, keep the pre-preamp path as short as practical, and treat every tenth of a dB of loss ahead of it as a real cost. Run a proper sequencer, with a clear order for unmuting the preamp and switching relays so nothing hot-switches and you do not damage the front end. For arrays, stacking distances and the phasing harness matter, but so does keeping the mechanical build realistic. Elevation capability is essential for EME. If you can only point at the horizon, you lose most of the Moon window. A mechanically simple array with reliable az/el and enough pointing resolution usually beats a bigger array you cannot keep aligned. On polarization, 2 m Faraday rotation can change the apparent polarization quickly, and there is also a spatial offset between two stations that depends on where the Moon sits relative to each of them. Fixed horizontal-only stations will therefore see deep fades even when everything else is right. Options are rotatable Yagis or cross-polarized arrays with a way to phase or switch between them. Even a simple H/V switch gives you something to experiment with, and you can see on the waterfall which setting is better. Note that the Moon window with the best polarization match for one partner may be poor for another, which is something to bring up when planning skeds. Also, do the own-echo test early if your power and gain allow it. WSJT-X has an echo mode for exactly this. It tells you whether your system is hearing the Moon at all, and it is a good way to check frequency calibration and pointing. Without echoes, it is hard to know whether a failed sked is a station fault or the other end.
-
Building a remote HF station: radio-side options, VPN vs. port forwarding, latency budgets and what the rules expect
Adding to the fail-safe point: don't rely on the same network path for both operating and emergency shutdown. A remote power switch or relay on a separate connection, such as a cellular modem or a second ISP, means you can still kill the station if the main link or a PC hangs. An ATU or amp that remembers a bad state after a reboot is another thing to plan for, because the station may come back up in a configuration you didn't choose. On the licensing side, it's worth asking explicitly whether the control operator must be at a specific location, and what the rules say about operating a station in another country. Some regulators treat this differently from local operation, so a quick check of the regulator's published guidance, or a question to the national society, is better than assuming the home-country rules carry over.
-
Getting past the CW plateau: Farnsworth, keyer mode, filters, QSK and where decoders fit
On decoders: CW Skimmer and similar software are excellent at spotting. The Reverse Beacon Network, for example, relies on skimmer-style decoding to show who is on the air and where. But decoding quality depends heavily on signal-to-noise ratio, fading, and how consistent the timing is. Hand-sent CW with irregular spacing, a bug with varying dahs, or a signal in QSB can all produce wrong characters. For a callsign in a contest, a decoder is a useful hint but I would still confirm by ear or ask for a repeat before logging a doubtful call. Contest CW has its own conventions. Cut numbers are common in exchanges, so 9 becomes N and 0 becomes T, and 599 is often sent as 5NN. When you ask for a repeat, ask for only the part you missed instead of sending a full question or repeating the whole call back. If someone is calling you faster than you want to run, you can slow down, but staying near the caller's speed usually keeps the rate up. For search-and-pounce operating, listen to a couple of exchanges before calling so you know the format and the speed on that frequency. Back on QSK: it is great for contests and DX because you catch someone calling over you or hear a station asking for a repeat. If you use an amplifier, check that its relay and your T/R sequencing can really handle full break-in, or you will clip the first elements or hear relay noise.
-
CQ World Wide RTTY DX Contest 2027
until
The CQ WW RTTY DX Contest is listed on the official contest site for September 25-26, 2027, starting at 0000 UTC Saturday and ending at 2359 UTC Sunday. It is held each year on the last full weekend of September and draws participants from around the world. The aim is to work as many stations as possible using the RTTY digital mode. The contest is worldwide and on the air, so there is no physical venue.Location: Worldwide (on the air, amateur HF bands) Organizer: CQ World Wide RTTY DX Contest (World Wide Radio Operators Foundation) Source: Event information -
Planning a homebrew QRP station from scratch: build order, test gear, and where each project teaches you something
I'd keep the order roughly as proposed, with one change: build the dummy load and a basic RF probe before the first transmitter. A 50 ohm load made from several non-inductive resistors in parallel is cheap. Without it, early tests end up on an antenna, which confuses everything. You can't tell whether a poor result comes from the circuit or from the antenna, and you may be radiating something you haven't checked. The Pixie family is worth building mostly for what it demonstrates. In the usual versions, one transistor oscillator serves as the transmitter and also as a detector on receive, followed by an audio amplifier such as an LM386. It is not a good receiver. There is almost no selectivity, and strong out-of-band signals get through. But it shows how crystal-controlled keying works and how little a simple CW transmitter needs. The Tuna Tin 2 is the better lesson on transmitter basics. It is a crystal oscillator with a power stage, and it makes you think about the output network, supply decoupling, and why the key line should have some shaping. Without shaping you get key clicks that spread across the band. Output on these simple designs is typically in the low hundreds of milliwatts, so the stage-by-stage voltages are easy to check with a multimeter and a probe. For direct conversion receivers, the usual problems are worth knowing before you build. You hear both sidebands, because there is no sideband rejection unless you add a phasing network. Strong AM broadcast stations can break through if the front end has no filtering. Audio-stage hum and microphonics show up, especially with high gain after the mixer. A bandpass filter at the input and a sensible audio low-pass go a long way. A diode ring mixer or an NE602/SA612-style mixer is a reasonable choice. Use an LNA only if you can handle the extra overload risk. On soldering: use a temperature-controlled iron with a clean tip, use flux freely, and clean the board afterward when you can. Many 'dead' kits turn out to have cold joints, solder bridges between pads, or an electrolytic installed backwards. Inspect every joint before you power anything up.
-
Building a first field kit: EFHW or linked dipole, which pole, and how much battery do you really need?
On batteries, do the math before buying. A QRP rig at 5 W on SSB averages well under an amp when you factor in receive time, so a small LiFePO4 pack of a few amp-hours covers several hours of operating. A 100 W rig can pull 20 A or more on transmit peaks, and the duty cycle on SSB is lower than people assume, but you still need a pack and a fuse rated for the load. Put an inline fuse close to the battery, use Powerpoles or similar for the connectors, and check what the pack's BMS does at its current limit. Some cut out suddenly, and that looks like the radio dying mid-QSO. Solar is nice for longer stays, but it adds the charge controller to the equation. Some MPPT controllers generate noticeable hash on HF, so test with the receiver on before you rely on it. And don't connect a panel straight to the rig. Run it through a controller with a LiFePO4-appropriate charge profile. For logging, paper is still the fallback that never runs out of battery. A pencil works in drizzle where a pen doesn't. For the digital side, a phone or tablet in airplane mode with offline software keeps the battery from draining searching for signal. Write the date, time (UTC), call, band, mode, and reports, then clean up and export the log afterwards when you're warm and dry. On safety, set your turnaround rules before you leave. Building cumulus, thunder, or rising wind means the antenna comes down and you leave the exposed spot. A fiberglass pole is not lightning protection. Carry water, layers, a basic first-aid kit and a way to call for help, and make sure someone knows where you are and when to expect you back. For Field Day style setups the same ideas scale up: separate power from the generator where possible, keep antennas well apart, use band-pass filters if stations share a site, and plan for the weather your tent will actually face.
-
Baseline field station for a 12-hour EMCOMM shift: power, antennas, grounding and noise. What would you change?
Good starting list. Here are some points I would add or push back on. First, the noise check. Don't only test with everything on at once. Turn items on one at a time and watch the S-meter on a quiet band, because a single bad wall-wart can mask what else is going on. If the noise is on the feedline, a choke may help. If it comes in through the power leads, a ferrite on the DC cable or a different supply is usually the fix. Moving the antenna farther from the shelter often does more than any filter. Second, I'd soften the grounding statement slightly. A single-point bond is sensible, but what that point is connected to depends on the setup. A battery-only station has different needs from a generator-fed one, and a vehicle can be part of the system. Follow the generator manufacturer's instructions and whatever the served agency requires, and don't assume one ground rod fixes noise or safety. Also, a long ground wire can act as an antenna at HF, so keep bonds short. Third, for EMCOMM specifically, the checklist should include the non-radio items: a copy of the communications plan, frequencies and net procedures, ICS-style message forms, spare pens, a log, and a relief schedule for operators. Many deployments get stuck on people and paperwork rather than on hardware. A full test of the station before leaving home, including one transmit on every band and mode you might need, will find a lot of problems.
-
Dead rig triage: what do you check first when there is no TX and no RX?
Your skeleton is close to how I'd order it. I'd put the shared-resource check even earlier. When both TX and RX are dead, the usual culprits are DC input, a regulator rail, or the PLL/reference oscillator. Measure at the rig, under load if you can, because a supply that reads 13.8 V open-circuit can sag badly through a corroded fuse holder or a worn Anderson/Powerpole contact. A voltage drop measured across the connector or fuse holder while the rig is drawing current finds this quickly. If there's a current-limited bench supply, watch what the rig draws at power-up. Almost no current, or a hard limit, tells you a lot before you open the case. After that, open the manual's block diagram and look for the common rails: 5 V, 8 V, 9 V and so on. Check each at the regulator output and at the far end of its run, since a regulator that is fine at the pin can still be pulled down by a shorted bypass cap downstream. A failed ceramic or tantalum cap on a rail is a classic dead-board cause, and a warm part on a current-limited supply will often point to it. The PLL is the other shared item: if the VCO doesn't lock, many rigs mute RX and inhibit TX together. The manual usually names a lock-detect voltage, so you can test it with a multimeter before reaching for a scope. For receive-only dead, I like working backwards from audio. Inject a tone at the volume control or the AF amp input, then work toward the antenna with a signal generator at IF and then RF. Before assuming a bad IC, check the speaker jack and headphone-switch contacts. A contact cleaner suited to switches and pots, applied sparingly and kept off plastics, solves more of these than it should.
-
Hamfest game plan: what to bring, how to vet used gear, and how to get more out of the club side of things
One thing I'd add to the kit: a printed list of what you actually need. Hamfest tables are designed to make everything look like a bargain, and a list helps you tell the difference between a part you need and one you just like. Put a rough price ceiling next to each item, and leave a little room for "surprise finds" so you aren't tempted to blow the budget on the first table. For testing, a simple antenna analyzer is handy if you're looking at antennas, tuners, or coax. A quick sweep tells you if a dipole is in the right band, or if a length of coax is shorted or open before you take it home. For used test equipment and older gear, ask whether it has been calibrated, and remember that a nice case doesn't mean the insides are in good shape. Old electrolytic capacitors in vintage gear are a classic issue, so if the price assumes it works perfectly, it's reasonable to ask what's been replaced. Also, walk the whole venue once before buying anything big. If you see three of the same radio on different tables, you've just learned what the going price is, and you can negotiate with some leverage.
-
Where exactly do I operate? Sorting out band plans, band edges, and calling frequencies from 160 m to 33 cm
Start by separating the two layers. FCC Part 97 is the law: frequency segments, emission types, power limits, and which license class gets what. The ARRL band plan is voluntary. It says things like "digital modes cluster here, CW and weak-signal work lives there." You can break the band plan and still be legal, but you'll step on people and they'll tell you. You can also follow the band plan perfectly and be illegal if you're outside your class's segment. For HF privileges, remember the pattern rather than every number. Extra gets everything. General gets most of each band but leaves out the bottom of the phone segments on 80, 40, 20, and 15 m, where Extra phone starts lower. Technicians get HF only in small segments: CW on parts of 80, 40, and 15 m, plus 10 m, where they have CW/data and SSB phone at 28.300–28.500 MHz. They also have a lower HF power limit (200 W PEP). Technicians don't get 160 m. Verify exact numbers against the current ARRL privilege chart or Part 97.301–97.305. Don't trust a number from a forum post, including this one. The 30 m band is the odd one: 10.100–10.150 MHz, CW and data only, no phone, 200 W PEP limit. People often assume it works like the others, and it doesn't. On band edges, don't forget that your signal has width. SSB takes roughly 2.7 to 3 kHz. Convention is LSB below 10 MHz and USB above it. If you're on LSB and your dial reads 3.800 MHz, the energy is spread below the dial frequency, so part of your signal falls outside the General segment. Move up so the whole signal clears the edge, and give yourself some margin for dial calibration error. The same logic applies on USB at the top of a segment. On 20 m, Extra phone starts at 14.150 MHz, and the USB signal extends upward from the dial, so you're fine there. At the upper edge of a band, USB would reach past it. Check your rig's accuracy against a known signal. For digital, the common FT8 dial frequencies are conventions, not rules. The usual ones are 1.840, 3.573, 7.074, 10.136, 14.074, 18.100, 21.074, 24.915, 28.074, and 50.313 MHz. They fall inside the data segments, but it's the shared habit that makes the calling frequencies work.
-
On-air etiquette basics: listening first, calling CQ, breaking in and running a tidy net
On nets, the difference between a smooth one and a messy one is usually discipline at check-in. A typical directed net has a net control station (NCS) who opens with a preamble stating the purpose, the frequency and the format, and then calls for check-ins. As a participant, wait for the call, give your callsign with phonetics once and clearly, and add only what the NCS asks for, such as a name, a location or "short-time" if you have to leave early. Don't give a long greeting, and don't answer other stations' check-ins. The NCS is building a list, and a second voice makes that harder. If you have traffic or an emergency, say so at check-in so the NCS can prioritize it. Without the NCS's invitation, don't start side conversations on the net frequency. If you want to talk to another station after the net, wait until it closes and then move to a different frequency. For anyone thinking of running a net: write a short script and use it every time. Participants quickly learn the pattern when the opening, the check-in call, the traffic call and the closing always come in the same order.
-
Making SET and Field Day count: designing exercises that expose real communication gaps
On the served-agency question, the biggest improvement is usually getting the agency to give you the messages, or at least to approve what you send. If the exercise messages are all written by the radio group, you're testing the radio group's own assumptions. A message written by someone who doesn't think in radio terms will include abbreviations, internal jargon, and unclear locations, which is exactly what you'll receive in a real event. Also decide in advance what you will and won't do. Does the agency want messages signed by a specific person? Who is authorized to send traffic on their behalf, and who confirms receipt? Amateur operators generally shouldn't be deciding the content or priority of an agency's message. They should be moving it accurately. If an operator thinks a message needs clarification, the right move is to ask the originator, not to rewrite it. One easy drill: have the agency originate a message that needs a reply, and see how long the round trip takes. Not just delivery, but the full cycle of send, deliver, answer, send back. That number is often a surprise, and it's more convincing to an agency than a list of capabilities.
-
Before you key up a new repeater: offsets, tones, linking and etiquette checklist
On linked systems, the biggest thing is that you may be talking to far more people than the local frequency suggests, and delays can be long. Here is how the main ones differ. EchoLink connects through the internet to PC, phone and repeater nodes. Repeater nodes usually carry an -R suffix and simplex link nodes an -L, and users must be validated amateurs. IRLP is a separate VoIP system for repeater and simplex nodes, controlled with DTMF commands and node numbers. AllStar Link is based on Asterisk and links nodes by node number, and many hubs or networks are built on it. Wires-X is Yaesu's system for System Fusion (C4FM) repeaters and nodes, organized around rooms. DMR and D-STAR work differently from analog FM linking. DMR uses two timeslots per channel, color codes, and talkgroups. The talkgroup you key decides where your audio goes, so programming the wrong talkgroup or timeslot can put you on a busy network instead of the local channel. D-STAR routes by callsign and uses RPT1, RPT2 and UR settings, plus gateways and reflectors. Many new D-STAR users get stuck on those routing fields rather than on frequency and tone. For etiquette, a few habits help everywhere. Listen before you transmit and give your callsign clearly. Leave a longer pause between overs on linked systems so others can break in, and especially so people connected through delays or a slow link can join. Keep transmissions short and mind the time-out timer, which varies by repeater and is there to stop a stuck or long-winded transmission. Don't wait for the timer to run down before you unkey. Don't kerchunk to "test" the repeater; say your callsign instead. And don't send control commands (DTMF) on a repeater you haven't read the rules for, since the owner may restrict link commands. Finally, if you are only a mile or two from the person you want to talk to, move to simplex. That keeps the repeater clear for people who actually need it.
-
Run, S&P or SO2R? A practical way to decide when a multiplier is worth leaving your run frequency
Two things that get less attention than SO2R: antennas and endurance. For antennas, what matters in contesting is how well the system fits the way you will operate. A stacked yagi system on 20, 15 and 10 meters gives gain at several takeoff angles, and being able to switch between stack combinations is a real advantage when openings change. A rotator with slow turn time is a rate killer when you are alternating between directions. Fixed antennas or beams with wide patterns can be better for rate in some cases. On the low bands, receive performance often matters more than transmit gain. A receiving antenna with a good front-to-back ratio, such as a Beverage or other directional receive antenna, lets you hear stations you would otherwise miss in the noise. Your multiplier count on 160, 80 and 40 often depends on what you can hear. Band-change timing is largely a propagation question, but the rules matter too. Some multi-operator categories limit how often you can change bands, so check the rules for your category and plan your schedule around them. In single-operator entries, remember that a band change costs you the run frequency you built up. When the new band is likely to pay off with a better rate or new multipliers, go. If it is only a guess, S&P first on a second radio or the bandmap before committing the main radio. On fatigue, the risk is gradual and easy to miss. Typical signs are more busted calls, repeated exchanges, missed multipliers on the bandmap and slower reactions. A simple approach is to plan your off-times around the hours when rate is naturally lowest on your best bands, instead of taking breaks at random. Eat and drink on a schedule, keep the shack temperature comfortable and stand up periodically. If you notice more errors, it is usually time for a break even if the rate is good. A short, planned rest often costs less than hours of sloppy operating and log checking penalties afterward. One more habit that helps with scoring: after the contest, review your rate sheet and band-by-band breakdown. It shows where you lost time and where multipliers came from, which helps you adjust next time.