Everything posted by Mod_Chrissy
-
Choosing between J-pole, slim jim, collinear and 5/8 mobile antennas: what matters more, gain or feedline and installation?
For most installs the first money should go to the feedline and the mounting position. A 3 dB gain antenna on 100 ft of RG-58 at 70 cm can easily lose more than that gain in the cable. Dropping to a low-loss cable, or moving the radio closer to the antenna, often does more than swapping antennas. The second thing is clearance. A collinear sitting right next to a mast, a gutter, a metal roof edge or a TV antenna will not have the pattern in the data sheet. On a vehicle the same applies: a 5/8 whip off-center on the roof will have a lopsided pattern, and a mag mount on a small flat spot will not behave like a roof-center NMO. The antenna can tune to 1.3:1 and still not perform well. For J-poles, a simple choke on the coax near the feedpoint (ferrite beads, or several turns of coax in a coil) is cheap, and it can make the antenna's SWR less sensitive to cable placement. If the SWR shifts when you touch or move the coax, common-mode current is a likely cause.
-
Band plans vs. FCC rules: how do you decide where to operate, and how close to the band edge is safe?
Start with the legal/voluntary split, because it makes everything else easier. Part 97 (sections 97.301 to 97.305 and related rules) is the law. It defines which frequencies each license class can use, which emission types are allowed in which segments, and power limits. The ARRL band plan is not law. It is a consensus on how to share space between modes (weak-signal CW, SSB, digital, beacons, repeaters, etc.). Ignoring it won't earn a citation by itself, but it will get you QRM and bad feelings. Going outside your privileges is a violation. On HF, think in layers. CW and narrow digital modes sit at the bottom of each band, with phone higher up. In the US, General and Extra phone segments are: 80 m: General 3.800-4.000, Extra 3.600-4.000 40 m: General 7.175-7.300, Extra 7.125-7.300 20 m: General 14.225-14.350, Extra 14.150-14.350 15 m: General 21.275-21.450, Extra 21.200-21.450 160 m (1.800-2.000) and 10 m (28.000-29.700) are open to General and Extra with the usual mode rules. 30 m (10.100-10.150) is CW and data only, 200 W PEP. On 17 m and 12 m, phone is allowed only in the upper part of the band, and the lower part is CW/data. Technicians get CW-only segments on 80, 40 and 15 m, plus CW/RTTY/data on 10 m from 28.000-28.300 and SSB from 28.300-28.500 with a 200 W PEP limit. Always check the current FCC chart, because I'm quoting from memory. For band edges, remember that your signal occupies bandwidth around the dial frequency. In USB (normal on 20 m and up), the signal extends above the dial, so keep the dial about 3 kHz below the upper limit. In LSB (normal on 160/80/40 m), the signal extends below the dial, so keep the dial at least 3 kHz above the lower limit. For example, if you're a General on 75 m phone, don't park an LSB signal at 3.800.0 kHz, because part of it is outside your privileges. Allow a margin for rig calibration error too. With digital modes like FT8, the transmitted signal is the dial frequency plus the audio offset (maybe 200-3000 Hz), so check the whole range. Common digital watering holes are the FT8 dial frequencies, such as 7.074 and 14.074 MHz. Those are usage conventions, not regulations, but they work only if everyone sticks to them.
-
Getting from 5 to 20 WPM: what actually moves the needle, and where people stall
On the plateau around 12-15, one thing worth separating is whether you're stuck on recognition or stuck on writing. If you can copy a recording at 18 WPM character speed with wide spacing but fall apart when the spacing tightens, it's a word-level problem, so more whole-word and call sign practice is the answer. If you can hear the characters fine but your hand can't keep up, it's a transcription problem, and trying to copy only the last letter or number in each word, or just listening for a few minutes, may help. Different cause, different drill. For call signs, the most useful trick is varying the material. Practicing only ones you already know teaches you to recognize those. Random or randomized call signs, preferably with realistic prefixes and suffixes, force you to listen to every character. Contest-style simulators and call sign trainers are good for this, since you can raise the speed a notch after you hit about 90% accuracy. Also, check your paddle setup if sending feels clumsy. Contact spacing set too wide or too tight causes false or missed elements, and that's often blamed on 'hand speed' when it's really a mechanical adjustment.
-
SOTA basics: summit refs, points, spotting, lightweight kits and safety for new activators and chasers
For a first kit I'd split it into a VHF-only option and an HF option, because the weight and complexity differ a lot. A VHF FM handheld with a decent antenna, spare battery, a printed summit reference and a pen is enough to make four contacts on many summits, provided there are enough chasers or local operators within line of sight. That makes it a good low-pressure way to learn the routine of spotting, calling and logging. The weakness is population: in sparsely populated areas, FM simplex can leave you short of the four QSOs, so check the alerts and ask whether anyone is likely to be monitoring. For HF, the usual approach is a compact QRP transceiver, a lightweight coax run, and either an end-fed wire or a linked dipole on a light pole. HF reaches chasers well beyond line of sight, so it's the more reliable way to get your four contacts. It also brings more to go wrong: tuning, wire handling in wind, battery capacity and logging while cold. Practice the whole setup in a park or backyard first. Time it, so you know how long it takes to be on the air, because summit time and daylight are the scarce resources. Whatever you take, bring more battery than you think you need and test it in cold conditions if you'll be out in winter. Lithium and LiFePO4 packs sag differently, and a rig that works on the bench can misbehave at low voltage.
-
Planning a multi-day field comms deployment: generator vs. LiFePO4 vs. solar, and where noise and grounding bite
On the cycle versus continuous question, I'd lean toward cycling if the deployment allows it. An inverter generator is cleaner than the old open-frame type, but "cleaner" doesn't mean RF-quiet. The inverter electronics, the engine ignition, and the output cables can all radiate. The usual fixes are distance, orientation, and chokes. Put the generator well downwind and away from the operating tent, and keep its cord away from the coax and antenna wire. Clamp ferrites on the AC output cord and on any DC cable run near the radio. A mix 31 type is common for HF. Do a noise check before you commit to a layout. With the generator off, tune across the bands you expect to use and note the S-meter noise floor with the preamp off. Then start the generator and charger and look at the same frequencies. Do the same with the solar controller connected, then with the laptop supplies and any LED lighting. Switch loads one at a time so you can identify each source. Cheap USB chargers and LED lamps are frequent offenders, and some DC-DC converters make a rough noise on 40m and 80m. A safety point that gets glossed over: carbon monoxide. Keep the generator outdoors, well away from tent openings, doors, and vents, and never run it under a shelter, however it is open. Think about wind direction as well as distance, because exhaust can drift toward a tent when the wind shifts.
-
Building an HF shack around a 100 W rig: what matters more than the radio model?
The power supply point deserves a bit more. People often pick a supply by the continuous current rating and forget what happens on the transmit peaks. If a 100 W rig is drawing about 20 A and the supply sags or goes into current limiting, you get distorted SSB and possible ALC chatter. A bit of margin, a proper fuse close to the supply, and short, heavy DC cabling go a long way. If you're using a switching supply, also watch for hash on 160 to 40 m. A quick check with the supply on and off, or with a battery, tells you whether it's the culprit. For the lower-power rigs, the KX3 and G90 shift the priorities. You don't need a huge supply, and a small battery or compact switcher is fine, but antenna efficiency and the choke at the feedpoint matter even more because there are fewer watts to spare. A built-in or external tuner is useful, but it only matches the radio to the line. It doesn't make a poor antenna radiate better. For layout, one thing I'd plan early is how the amplifier will be wired. Keep its AC and RF paths physically separated from the rig's CAT and audio cabling, and leave space to access the rear panels. It's much easier to design that in than to rework a crowded desk later.
-
Breaking pileups on rare DX: split, timing, tailending and what changes on the low bands
On the low bands, receive often matters more than the transmit signal. On 160 and 80 meters, many stations can be heard by the DX station only because they are quiet enough to be copied on the noise floor. That means a receive antenna such as a Beverage, loop, or flag can be worth more than a few extra dB on transmit. If you can hear the DX but not the stations he is working, the problem may be your local noise or your antenna pattern, not your power. It is worth testing your station's receive performance toward the target area before the DX is on the air. Timing also changes with the band. On top band especially, the opening may last only a short time around the gray line at one end or both. If the DX is at the right sunrise or sunset window, don't waste it by chasing a single contact on the wrong mode or frequency. Also respect the local band plan and any DX window recommendations. Operating in the wrong part of the band can cause trouble even if the DX station is well placed. For FT8 and similar modes, remember that DXpedition operation is not the same as normal operation. If the DX is using WSJT-X Fox and Hound mode, you need to be in Hound mode and follow the instructions. The Fox generally transmits in the lower part of the passband, and Hounds should call above that range, not on the Fox frequency. Calling on the wrong frequency or in the wrong mode can slow everyone down. Also keep in mind that digital modes often make pileups feel more orderly while still being very competitive, so make sure your clock, audio level, and software settings are correct.
-
Radio mods that are worth doing, and the ones that cause trouble: expanded RX, MARS/CAP, TCXO, filters, power and noise
For noise reduction, I'd start at the power and cables before touching the radio. Run it from a battery for a few minutes and compare the noise floor. If the noise drops, look at the supply and its leads. If it stays, it's coming in on the antenna or feedline, and a common-mode choke near the radio or at the feedpoint is the next thing to test. Changing one thing at a time matters, otherwise you can't tell which fix worked. On battery upgrades, voltage range is the big issue. A rig that is rated for 13.8 V may behave differently, or protect itself, when the supply sags under transmit. A fully charged pack can also be higher than the radio expects, depending on chemistry. Check the manufacturer's rated input range and watch the voltage under load, not just at rest. A fuse close to the battery is cheap insurance, and so is a wire gauge that's generous for the current. For fans, the sneaky problem is the fan or its controller adding hash to the receiver. If the noise appears or changes when the fan spins up, try filtering its supply lead or powering it separately from the radio.
-
Dual-band mobile rigs: FTM-500D vs ID-5100A vs TM-D710G, plus how to wire and run them properly
Start with power, because most mobile problems trace back to it. Run the supplied fused power cable directly to the battery rather than tapping an accessory circuit or using a cigarette lighter socket. A 50 W radio can draw roughly 10 to 12 A at full transmit power, and the voltage drop on a thin or shared circuit shows up as a weak signal or random resets. Keep the fuse holder close to the battery terminal on the positive lead, since its job is to protect the wire. Use the fuse rating in the radio's manual, and do not replace a blown fuse with a bigger one just to stop it blowing. Use a rubber grommet where the cable passes through the firewall so the insulation does not chafe. Route the cable away from sharp edges and hot parts, and crimp or solder connectors rather than twisting wires together. If you use a fused distribution block or a relay-switched feed, follow the radio manufacturer's guidance and keep the connections short and clean. Check your connections after a few weeks, because vibration finds loose terminals. For mounting, use a bracket that bolts to something solid and keep the radio away from the airbag zone. A head unit on a remote cable needs to be positioned so you can operate it without looking away from the road for long. The Kenwood and Yaesu have detachable faceplates or control heads, so measure the available space before you commit to a location.
-
How should I study for the Technician exam (Element 2)? Pool structure, weak spots, and practice test habits
The two areas that usually need the most deliberate practice are the math-flavored questions and the rules or operating-practice questions, because they feel different from each other. For the electronics, you don't need advanced math. You need Ohm's law (E = I × R) and the power formula (P = I × E), and you should be comfortable rearranging them. For example, 12 volts across a 4 ohm resistance gives 3 amps, and 12 V × 3 A is 36 watts. The wavelength rule of thumb also shows up: wavelength in meters is roughly 300 divided by frequency in MHz, so 146 MHz is about 2 meters. That's where the band name 'two meters' comes from. Practice these a few times by hand, and ask the volunteer examiner team ahead of time what calculators are allowed. For repeaters, learn the vocabulary as a set: input and output frequencies, offset (typically 600 kHz on 2 meters and 5 MHz on 70 cm), CTCSS or PL tones for access, and why you identify and listen before transmitting. Also know simplex versus repeater operation and the basics of how to make a call without interfering with others. For RF exposure, you generally won't be asked to do heavy calculations. The questions center on concepts: exposure limits are set as maximum permissible exposure, they depend on frequency, power, antenna type and location, and duty cycle matters, and operators are responsible for evaluating whether their station meets the limits. Safety questions are mostly common sense plus specifics, such as proper grounding, working safely around towers and ladders, staying clear of power lines, and using the right fuse in power circuits. As for practice tests, take them in two modes. First, do untimed topic quizzes while you're learning. Then take full 35-question mock exams drawn randomly from the whole pool. Keep a list of the questions you missed and revisit it a day or two later, since that's what shows whether you actually learned it. If you're consistently scoring well above 26 on fresh random tests, you're probably ready. If you hover near the line, go back to the weak subelements instead of taking more full tests.
-
Getting a handheld tracker, a Direwolf iGate and aprs.fi to agree on 144.390
Start by separating RF problems from internet problems. In Direwolf's console output, check whether the tracker's packets are decoded at all. If they are, the RF side is fine and the question becomes whether the iGate is logged in. Look for a successful APRS-IS connection message. A wrong passcode is a classic cause. Direwolf can connect and sit there, but the server won't accept the packets. If the packet is decoded and the login is good, look at the raw packet on aprs.fi. The path shows the q-construct that was added at the server. Something like qAR followed by your iGate callsign means a gateway heard it directly on RF. qAO marks a receive-only iGate. Digipeaters in the path are marked with an asterisk once they've repeated the frame. That lets you see whether a packet reached you directly or through a digipeater. On audio level: Direwolf prints an audio level figure for each decoded frame, and a decode that is clipped or very low is more fragile than it looks. Set the sound card input so typical packets sit comfortably mid-range. Also keep in mind that the shared channel is mostly a collision game. A weak iGate that hears every second packet won't give you a clean track no matter how good the config is. On IS-to-RF: leave it off until the RX side is solid. Gating internet traffic to RF should mostly be limited to messages for stations the iGate has recently heard locally. It is not a way to rebroadcast position data to the channel, and Direwolf's gating rules are written with that in mind. A full iGate also needs to be configured carefully so it doesn't create duplicate traffic.
-
ARES, RACES, MARS, SKYWARN and CERT: how do you sort out the roles, training and activation paths?
One thing that helps newcomers is to separate the license from the role. Your amateur license lets you operate on the amateur bands, but your authority to support an agency comes from that agency's acceptance of you, which often means a registration, an ID badge, a background check or a signed agreement. Ask your Emergency Coordinator or Radio Officer what your served agency requires before you show up anywhere. Showing up uninvited at an EOC or shelter, even with good intentions, can create problems for the people running it. On the training side, it also helps to practice the boring parts: filling out an ICS-213 cleanly, copying a message exactly, and keeping a station log with times. Those skills get exercised far more often than exotic antenna setups. If your group runs weekly nets, rotate the net control job so more people get comfortable with it. A net that depends on one or two people is fragile.
-
How do you filter ham radio news? New rigs, firmware notes, band-opening reports and FCC/ARRL items
My rule of thumb for gear news is to wait for the second wave of information. The first wave is the manufacturer's press material and a few hands-on impressions. The second wave is where you start to see measurements, owner reports about quirks, and comparisons with the radio you already have. If receiver performance is the main question, look for independent numbers such as third-order dynamic range at close spacing, not just the sensitivity figure on the brochure. On band openings, I'd add that the mode matters when interpreting spots. A burst of FT8 spots on 10 m can mean a marginal path that's workable with weak-signal digital but not for a casual SSB call. Check the spot SNRs and how many distinct stations are reporting before you assume it's an easy opening.
-
Field comms setup: what order do you build power, antenna, and noise control for an EMCOMM deployment?
The mast and shelter side tends to cause the most avoidable mistakes because people treat them as an afterthought. A fiberglass push-up mast is fine for lighter wire antennas and small verticals, but it is only as good as its guying and base. Use non-conductive guy line, stake or ballast every guy point, and keep the load light at the top. Wind loads on a mast with a beam or a heavy coax run add up quickly. If a thunderstorm is approaching, the plan should be to disconnect coax from the radio, lower the antenna, and move people away from the mast. A short ground rod in the field is not lightning protection. For coax runs, make a drip loop where the cable enters the tent or vehicle, and keep the feedline away from tent poles and metal stakes where it can be tripped on or chafed. Choke the line, label each cable end so teardown is quick, and avoid coiling excess coax tightly unless it's a deliberately made choke. Running the coax perpendicular to a horizontal wire for the first stretch helps avoid coupling to the radiating element. For EMCOMM specifically, I'd add three checklist items that often get skipped: spare power and a second antenna option for the primary band, a printed copy of frequencies, net procedures, and forms (such as an ICS 309 communications log), and a handoff plan for operator rotation so one person isn't running the station for the entire shift. The best station design is the one a relief operator can sit down at and understand within a minute or two.
-
Getting from 5 to 20 WPM: what actually moves the needle, and how do you break a plateau?
I'd push back a little on treating software decoding as something to avoid altogether. It depends on how you use it. Used as an answer key after a practice session, it is useful, because you can compare it against your own copy and see exactly where you went wrong. Used live as a replacement for your ears, it will probably slow you down. Also keep in mind that decoder output is often wrong on weak or fading signals, so a mismatch does not always mean you made the mistake. For getting onto the air, I'd suggest a stepped approach rather than waiting until you feel ready. Start by listening to real QSOs and copying only the callsigns and the signal reports. Then answer a slow CQ. Many CW operators will slow down for a newcomer if you tell them you are still learning. A short exchange with a standard structure (callsign, RST, name, QTH) is a good first target, because you already know what is coming and can focus on hearing it. Contests are worth trying early for the same reason. The exchange is predictable and repeated hundreds of times, which makes them one of the better ways to build callsign copy at speed. Just don't set a speed goal for your first one. Treat it as listening practice and log whatever you can.
-
Part 97 compliance Q&A: station ID, third-party traffic, power limits, RF safety, remote control and renewal
Picking up the rest, with the same caveat that you should read the current rules. RF safety (§97.13(c) and the FCC's exposure limits). This is one of the most overlooked parts of Part 97. Stations above band-specific power thresholds must be evaluated for RF exposure. The thresholds are in a table in §97.13(c), and they vary by band. They're quite low on some VHF and higher-frequency bands, and higher on HF. The evaluation compares estimated exposure against the maximum permissible exposure limits, which differ for controlled and uncontrolled environments and use different averaging times. Practical tools include the FCC's OET Bulletin 65 and its amateur supplement, plus an antenna modeling program. Duty cycle matters, since SSB voice, CW and FT8 average very differently. Keep your calculations. If neighbors can reach the area near the antenna, the uncontrolled limit applies there. Spurious emissions (§97.307). Your emissions must be confined to the bandwidth necessary for the mode and must not cause harmful interference. The rule also sets attenuation levels for spurious emissions that vary by frequency range and power. HF transmitters need to be at least 43 dB below the mean power of the fundamental. VHF has a stricter standard for higher-powered transmitters. A properly working modern radio normally meets this. Problems tend to come from overdriven amplifiers, linears with bad filtering or poor tuning, and poor audio processing. The FCC can require you to correct a problem station, and you remain responsible for what your station radiates. Auxiliary and control operation. The licensee is responsible for proper operation (§97.103). A station needs a control operator, and the privileges used are those of the control operator's class. Automatic control (§97.109) is limited to specific station types, such as repeaters, auxiliary stations and beacons. An auxiliary station (§97.201) is typically a link or remote-base-type station, and it has restrictions on which bands it may use. Remote control (§97.213) means the control operator is at a control point and must be able to terminate transmissions. This applies to internet-controlled stations too: you can't just leave a remote station running with no way to shut it down. License classes. Technician, General and Amateur Extra are the classes currently issued. Novice and Advanced licenses are no longer issued but remain valid for existing holders and can be renewed. Operating privileges depend on class, and you may operate only in the segments and modes your class allows. Enforcement. The FCC Enforcement Bureau can issue warnings or notices of violation and, in serious cases, proposed forfeitures or license action. Volunteer monitoring programs, such as the one run by the ARRL, don't have FCC enforcement power. If you get an official letter, read it carefully, respond by the deadline, and keep your records. Term and renewal. A license term is 10 years. You can file for renewal in ULS within the 90 days before expiry. After expiration, there is a grace period during which you can still renew without retesting, but you cannot transmit while the license is expired. After the grace period, you must apply as a new licensee. Keep your mailing address and email current in ULS, as the rules require. Check the FCC's current instructions and any fee information before filing, since procedures can change.
-
Hamfest game plan: how do you handle swap meets, used gear, VE sessions and club stuff in one trip?
I'd treat the flea market as a two-pass job. First pass, walk the whole thing without buying much, just noting what's where and roughly what things are going for. A lot of the same items show up at multiple tailgates, so you get a feel for the going rate on common stuff like power supplies, tuners, and older HF rigs. Second pass, go back for the things on your list. One caution for new buyers: test the whole signal chain, not just whether it powers on. A radio can display fine and still have a dead final or a receiver that's deaf. A dummy load and a known-good antenna or signal source helps. Also ask about the manual, the mic, the power cable and the original accessories, because missing proprietary connectors can cost more than the radio is worth. For anything expensive, search the model's known issues before you leave the house, since some rigs have well-known failure points like capacitors or display problems. On the club side, a visible sign that says "Ask me about getting licensed" or "Free Elmer help" does more than a stack of flyers. People will walk up and ask a question if you make it easy.
-
POTA activation checklist: park references, 10 QSOs, spotting, and logging two-fers and roves
For a first activation, I would pick a park with easy access and a flat open area, and plan for roughly one band you know well. A simple wire antenna and 5 to 20 W are plenty if you spot early and call CQ patiently. If the first spot brings only a handful of callers, that is normal. A second spot, a band change, or a switch from SSB to CW or FT8 can fill the log, depending on what you are comfortable with. Also check your logging approach before you start. Some people log directly in an app, others use paper and enter it later. Either works, but paper needs a clear note of the UTC time and the park reference. If you rove, write down when you pack up and when you restart at the next park so you do not mix up the logs. On the hunter side, hunting from home is a good way to learn how spots and pileups work before you activate. Listen first, copy the callsign fully, and send only the minimum exchange the activator asks for.
-
Building a sane ham radio tool stack: spots, lookups, reception reports and propagation
On question 3, I'd put live evidence first and indices second. Solar flux and the K index describe general conditions, but they can't tell you whether 15 meters is open from your location to a specific place right now. RBN and PSK Reporter can. A quick test is to call CQ on CW or run a digital mode for a few minutes and see who spots you. Then compare that with your expectations from the indices. Just remember what these reports measure. Each one shows the signal at a specific receiver, with that receiver's antenna, noise floor and decoder. A strong report from one skimmer doesn't guarantee a human operator in that region could copy you. A lack of reports can also mean few skimmers or monitors nearby, not a dead band. I'd use the maps to compare band to band and antenna to antenna, and not as an absolute measure of your signal. For the cluster, the most useful setup is filtering by band and mode at the node or in your logging software, so you only see what you can work. Without filters, the feed is mostly noise.
-
Planning a dual-band mobile install: FTM-500D vs ID-5100A vs TM-D710G, and how to wire it so it stays quiet
Start with the power wiring, because most mobile problems trace back to it. The radio's supplied power cable is usually designed to go directly to the battery, with a fuse in each leg. Leave those fuses in place. A 50 W FM mobile draws on the order of ten-plus amps at full transmit power, so the wire must be sized for the current and for the length of the run. Voltage drop on a thin or overly long cable shows up as a radio that misbehaves on transmit peaks, so don't extend the supplied cable with something thinner. If you must lengthen it, use the same gauge or heavier and make the joints solid, not twisted and taped. The important safety point is the fuse placement. The fuse protects the wire, so it should sit close to the battery on the positive lead. If a fuse is only at the radio end, a short in the cable between the battery and the radio has nothing to stop it. Pass the cable through a firewall grommet, keep it away from sharp edges and hot components, and don't leave slack bundles loose. Many modern vehicles have a battery current sensor on the negative terminal, and some have start-stop systems. For these, check the vehicle manual or a service source for the correct place to connect the negative lead, because grounding it in the wrong place can confuse the vehicle's charging management. A switched circuit through a relay or a properly rated fuse block can work too, but a radio that powers down with the ignition may lose settings or behave differently, so check the manual for your chosen radio. On the radio choice, check the specific manual for each model's feature list rather than relying on forum summaries. Compare things like cross-band repeat support, the head separation kit, the display visibility in direct sunlight, how each handles the microphone, and what you will actually use: APRS, D-STAR, Fusion or plain FM. If your local repeaters are mostly FM, the digital features may not matter much for you. If a regional digital network is active near you, that's a strong reason to pick the matching radio.
-
Dynamic range vs. noise floor on budget SDRs: gain staging, upconverters and antenna choices for HF through VHF
A quick way to check whether a signal is real or an overload product is to change the attenuation by a known amount and see how it moves. A genuine signal drops by roughly the same number of dB as the attenuation you add. Intermod and image products usually drop faster than that, often by two or three times the change, because they depend on the strong signals nonlinearly. Detuning the receiver slightly or inserting an FM notch or bandpass filter, then seeing whether the suspect signal vanishes, is another useful test. On filters, the order I would usually think about is: remove the strongest out-of-band signal first, then adjust gain. For an RTL-type dongle that often means an FM broadcast notch in front of it. For HF with an upconverter or direct sampling, a low-pass or band-specific filter keeps broadcast stations from overloading the converter. A big wideband antenna with no filtering is convenient but can force you to run very low gain.
-
Remote station design: rig-side hardware, VPN vs. port forwarding, latency budgets, and rule compliance
One thing worth separating is the CW question. Streaming key-down and key-up over a jittery link produces uneven timing, which is why a lot of remote setups send text or timing packets to a keyer at the station instead. If you're mostly SSB or digital, that matters less, but the same logic applies to PTT: put the sequencing (PTT, amp relay, antenna switching) at the remote end so a late packet can't leave you transmitting into the wrong antenna. On rules, I'd also suggest keeping a short written operating plan for the station: who the control operator is, how it shuts down on a link failure, and how you'd reach someone physically at the site. It isn't a legal requirement everywhere, but it forces you to answer the questions a regulator, a contest committee, or a landlord might ask. And if you plan to use a hosted service or operate in another country, read the host's terms and that country's license conditions first, because a remote contact doesn't change which rules apply.
-
Planning a WWFF activation (and a POTA double): KFF refs, the 44-QSO line, logging, and operating tips
On the 44 QSOs: plan for it rather than hoping it happens. A few things help with a longer run. Get spotted and re-spotted. Both programs have spotting, and WWFF hunters watch for it. Put the reference, frequency and mode in the spot, and update it if you move. If you are on a double, mention both references in your comments so hunters from either side can find you. Self-spotting rules vary by platform, so check them before using a spotting tool. Choose bands for the time of day. Under a canopy or in a valley, a compromise antenna will favor some bands. A lower band like 40 m is good for regional contacts at times, while 20 m and up open further out later in the day. Moving up or down when your rate slows is often better than calling CQ into a dead band. If you are running CW or SSB, be ready to change mode once things quiet down. FT8 and other digital modes can add contacts when the voice rate drops, if the program accepts them. Check the mode rules for the reference you are using. Keep exchanges short and clean. Say your callsign and the reference at regular intervals, and don't make every QSO a long chat. Hunters often need only the call and a report, and a faster rate gets you to the threshold sooner. Write down when the UTC day changes: if you are close to midnight UTC, contacts on either side of it may not count together toward one activation, so be careful. Confirm the current day-boundary rule in the official text. Finally, remember why these references exist. Stay on established paths or parking areas, follow the reserve's rules on antennas, masts, fires and wildlife, and get any permission you need. Your amateur licence conditions still apply in the area, including power and band limits. If a site does not permit what you plan, pick another reference.
-
Getting started on LEO satellites: FM birds vs. linear, Doppler handling, and whether an Arrow or a rotator-driven Yagi makes sense
On rotators, the useful question is whether you want to hold an antenna or operate the radio. With a handheld Arrow, one hand is on the antenna, one on the radio or PTT, and you may also be adjusting Doppler and logging. A rotator frees you up for the radio and the QSO. A small az/el rotator with a pair of modest Yagis is a common step up, and it also lets you work lower passes more consistently because you aren't fighting your own pointing. If you go that route, spend time on the software side. Check that your az/el limits and calibration match what the rotator reports, and decide in advance how to handle overhead passes, especially if the rotator has a 180° flip or a limited elevation range. Gpredict and SatPC32 both can drive hardware, but neither fixes mechanical limits or cable wrap. A short test on a pass where you can see the satellite's predicted track versus your actual pointing will show if the setup is lagging. For QO-100, I would treat it as a separate project rather than an extension of the LEO station. The tracking problem disappears, but frequency accuracy, LNB drift, feedline loss at 10 GHz and 2.4 GHz safety become the main concerns. Many operators use a GPS-disciplined or drift-compensated LNB to keep the downlink stable, and the narrowband transponder is sensitive enough to reward that effort.
-
Q codes and ham radio shorthand: what QRM, QRN, QRL, K vs KN, SK and RST mean, and when to use them
Q codes started as three-letter shorthand for CW. Each one can be a question or an answer depending on whether a question mark follows. "QRL?" asks "Is this frequency in use?" and "QRL" alone says "It is busy." Here are the ones you listed. QRM is interference from other stations or man-made sources. QRN is natural noise such as static and lightning crashes. The line blurs in practice. Power-line or switching-supply noise is often just called noise, and some operators call it QRM because it is man-made. The core distinction is nature versus other signals and devices. QRP means low power, and as a question it means "Should I reduce power?" Operators usually mean 5 W or less on CW and 10 W PEP or less on phone, though that is a community convention, not part of the code itself. QRO means high power, or increase power. Neither says what your legal limit is. QRT means "I am stopping transmission," which in practice is "I'm shutting down." QRZ? means "Who is calling me?" Operators use it after a pile of stations answers a CQ, or when they only caught part of a call. Don't confuse it with the website QRZ.com, which borrowed the name. QSL means "I acknowledge receipt" or "understood." It is also the word for a confirmation, including paper cards and electronic confirmations like LoTW or eQSL. QSO is simply a two-way contact. QSY means change frequency, as in "Let's QSY to 7.040." QTH is your location, so "What's your QTH?" means where you are operating. QSB is fading signal strength, which is common on HF. QRL is the polite one. Before calling CQ on a frequency, ask "QRL?" on CW or "Is this frequency in use?" on phone, and wait for any reply. Silence usually means it's clear, but listen first, because you may not hear both sides of a QSO. A few related codes show up constantly: QRS (send slower), QRQ (send faster), QRX (stand by, I'll call again), and QRV (I am ready). On voice, QTH, QSL, QSY, QRM, QRN, QRP and QSB are all common. Many operators prefer plain language where it's clearer, such as "Is this frequency in use?" instead of "QRL?" Either is fine as long as the other person understands you. Most operators avoid dropping a long string of codes on a new ham.