Everything posted by Mod_Chad
-
APRS on 144.390: sorting out trackers, digipeater paths, Direwolf iGates and beacon rates
On SmartBeaconing, think about the walking-versus-driving split before you touch the numbers. A single profile rarely suits both. Some radios let you store several beacon profiles, so you can keep one for vehicle use and another for slow movement on foot. Check how your TH-D74, TH-D75 or FT5D handles that in its manual, because the menu structure differs between them. The general shape is: set the slow rate long enough that a stationary radio isn't clogging the channel, and set the fast rate to something like once every minute or two at highway speed. If the low speed threshold is too low, GPS drift while parked can look like movement and trigger beacons you don't want. The turn parameters matter in town: too sensitive, and every lane change sends a packet. Too relaxed, and your track cuts corners on aprs.fi. On iGates, a receive-only one is a good first step. It gets your local RF traffic onto the internet without adding transmissions. If you later want to gate messages from the internet back to RF, that needs more care: you should only gate to RF for stations you have recently heard directly on RF, and avoid gating anything marked NOGATE or RFONLY, or anything that already came from APRS-IS. Direwolf handles a lot of these rules, but you should still read its documentation on transmit gating before enabling it. A practical check for a new iGate is to look at aprs.fi for your own station and for stations you know are nearby. If you see stations appear with the right timing, the RF-to-internet path is working. If nothing appears, check the passcode, the server name, and whether Direwolf says it is connected.
-
Washington's Conference on Horseback in Kingston 250th (special event station W2K)
until
The David Sarnoff Radio Club will run special event station W2K on Jan 3, 2027, from 0000Z to 2359Z, from Kingston, NJ, to mark the 250th anniversary of Washington's Conference on Horseback. Listed frequencies are 14.235 and 14.090 (JTTY). A QSL card is available through W2K c/o Dieterich, PO Box 597, Kingston, NJ 08528.Location: Kingston, NJ, USA (the listing gives no venue name or street address; mailing address for QSL: PO Box 597, Kingston, NJ 08528) Organizer: David Sarnoff Radio Club Source: Event information -
Technician to General: how should I split study time across HF bands, propagation, antennas and the rest of Element 3?
Here's a way to handle the study schedule and the other topics, assuming short daily sessions. Weeks 1-2: take a baseline practice exam from a pool-based site or app, then sort missed questions by topic. Don't just read the explanations. Write one sentence for each missed concept in your own words. Spend most of this stretch on the weakest topic, which is often propagation or electrical calculations for people coming straight from Technician. Weeks 3-4: shift to band privileges, operating practices, and digital modes. For digital modes, understand the concepts as well as the names: FSK versus AFSK, baud rate versus bandwidth, error correction and ARQ, how PSK31, RTTY and FT8-style weak-signal modes differ, and why some modes need accurate computer time. Operating practices include things like calling CQ, using band plans, avoiding interference, net etiquette, and how to identify properly. Those questions often have an answer that sounds courteous and legal, and that is usually the right one. Final week: do full timed practice tests, review only the misses, and re-read your band table. Practice tests are most useful when you ask why each wrong option is wrong. If you can explain that, you're studying the concept and not the answer position. On vanity calls: upgrading doesn't change the main picture much. As I understand the current system, both Technician and General licensees are eligible for the same call sign groups, so a General upgrade doesn't open a bigger menu. Check the FCC's vanity call sign page and the current ULS process for eligibility, fees and available groups before you plan around it. You can also keep your existing call after upgrading, so there's no rush to apply for a new one. Also check Part 97 for what to do about identification after passing but before the upgrade shows in the FCC database, since you'll want to follow that procedure correctly when you first use the new privileges.
-
Contest log workflow: N1MM+ for the run, WSJT-X on the side, then clean ADIF/Cabrillo and uploads to LoTW, QRZ and Club Log
On CAT sharing: the underlying problem is that most radios expose one control channel, and the operating system only lets one program hold that serial port. The usual fix is to put a single program in charge of the port and let everything else talk to it. That can be rigctld from Hamlib, flrig, or OmniRig. A virtual serial port pair or splitter is the other route. A server like rigctld or flrig is generally more predictable than splitting ports, because it queues commands instead of having two programs fight over timing. Whichever you pick, check that each program you run actually supports it. Support varies by program and version, so read each one's documentation instead of assuming. With WSJT-X it helps to separate three things in your head. CAT (frequency, mode, PTT), audio (the sound card path), and the UDP messages it broadcasts to loggers. UDP is how a logger like Log4OM can pick up the decoded callsigns and the logged QSO without parsing wsjtx_log.adi. If both WSJT-X and N1MM+ are open on the same machine, double-check that only one of them is configured to log FT8, or you will end up with duplicates that no dupe check can sort out, because they are legitimately the same QSO entered twice. Clock accuracy deserves a line item of its own. FT8 and FT4 rely on tight time sync, and every log you upload is in UTC. If the PC clock drifts, you get failed decodes, and you also get QSO times that will not match the other station's log. Keep the computer synced to a time source before and during the event. For rotators, the logger usually just sends a bearing computed from the callsign's prefix, a looked-up grid, or a click on the band map. The rotator controller program then does the work. It is the same sharing problem as CAT, so give the rotator its own port and its own program instead of routing it through the rig path.
-
Digital mode station setup: audio levels, CAT, time sync and picking the right weak-signal mode
I would start with the clock, because it is the easiest thing to rule out. FT8, FT4, WSPR, Q65 and MSK144 all depend on both stations agreeing on the start of each period. WSJT-X shows the offset as DT for each decode. If DT values are consistently large across many stations, the error is probably on your side. The program can tolerate a second or so, but marginal decodes are the first thing you lose. Windows does not discipline its clock aggressively by default, so a dedicated NTP client or a GPS source is a sensible fix. Run it before the session and check that it is actually syncing. Next is the audio path. In WSJT-X the receive level should sit in the lower-middle of the meter, and the documentation suggests aiming around 30 dB. Clipping the input does far more damage than a slightly low level. On transmit, set the rig to its data mode (USB-D, DATA-USB or equivalent) and turn off speech processing, compression and any EQ. Then lower the soundcard output or the rig's data input gain until the ALC shows little or no movement. Digital modes have a high duty cycle, so a rig run flat out can overheat, and any distortion splatters beyond the 50 Hz you meant to occupy. Lower power is usually the right answer, and it often reads cleaner on PSKReporter. For CAT, the usual traps are mismatched baud rate or stop bits in the rig menu, two programs fighting over the same serial port, and wrong PTT selection. If you key through CAT, make sure the rig actually routes the audio from the data input. Some radios need the mic gain or the data-port selection changed. In WSJT-X, the Split Operation setting (Rig or Fake It) keeps the audio tones within a clean range, so the rig does not have to be driven from high audio frequencies. Remember that opening a second program on the same serial port can silently break control.
-
First LEO satellite station: FM birds, RS-44 linear, ISS and QO-100 — what matters for tracking, Doppler and antennas?
A few points on the linear side and on QO-100. On an inverting bird like RS-44 the sideband swaps between uplink and downlink, so you typically transmit USB and receive LSB, or the reverse, depending on the band arrangement. If your transmit signal appears at the wrong place in the passband, check the inversion and your tuning direction before you blame the antenna. Also don't pile on power. A transponder is shared by everybody, and a strong signal can desensitise it for others. A good rule is to adjust until your downlink is no louder than the beacon or typical stations. For QO-100, tracking disappears but precision comes in. The narrowband transponder uses a 2.4 GHz uplink and a 10.489 GHz downlink, and the footprint covers only part of the world, so first check that your location falls inside it. The 10 GHz LNB is the usual weak point. A standard commercial LNB drifts with temperature, so many stations use a stabilised or locked unit, or correct it against the satellite's beacons. The dish gain, feed and uplink amplifier matter, but frequency stability is what decides whether SSB sounds usable. If you are curious about it but not ready, listening only costs less than a full transmit setup. It is an easy way to learn whether the satellite is worth the build.
-
How do you separate real ham radio news from hype? Rigs, firmware, FCC items and band openings
On propagation, I'd keep a small routine instead of chasing every alert. Check the current solar flux and K-index to get a rough idea of which bands might be open. Then look at spots on the band you care about. If 15 or 12 meters show stations from the direction you want on PSK Reporter or the Reverse Beacon Network, that's real evidence regardless of what the numbers say. If the numbers look good but nothing is spotted, listen anyway, because the spotting networks only show where people are active. It also helps to separate geomagnetic disturbance from good conditions. A high flux with an elevated K-index can mean disturbed paths, especially near the poles, while a quiet field can make HF steadier. Sunrise and sunset gray-line timing matters too, particularly on the lower bands. For convention coverage such as Dayton Hamvention, check dates, location and ticket information on the official event site before planning travel, since details can change between years. Coverage from the show floor is best for seeing which products and forums attract attention, but I'd treat show-floor pricing and ship dates as claims until the manufacturer confirms them.
-
Part 97 compliance Q&A: ID timing, third-party traffic, power limits, RF exposure, repeater control and renewal
I'll take the first four. Section numbers are from memory, so verify them against the eCFR. Station ID (§97.119): you must identify at the end of each communication and at least every 10 minutes during a communication. There is no requirement to ID when you start, though many operators do. The ID has to be your call sign (or the club or special-event call, if that is the station you're operating), and you send it in the mode you're using, or in another mode the rule allows. Tactical names such as 'net control' or 'shelter two' are fine for operational clarity, but they don't replace the call sign on that 10-minute schedule. On a net, every station is responsible for its own ID. The rule also sets language and code requirements, so check the phone, CW and data subparagraphs. A repeater is a separate station, and its automatic ID is what satisfies the repeater's own identification requirement. Your ID as a user is separate from that. Third-party traffic (§97.115): in general, a control operator can let a non-licensed person participate, provided the control operator is present, monitoring and ready to terminate the contact if it goes outside the rules. International third-party traffic is only allowed with countries that have a third-party agreement with the U.S., or where the third party is eligible to be a control operator. The list of agreement countries changes, so don't hard-code it into a handout. Third-party traffic also can't be used to get around the business-communications limits. There is a separate restriction on third-party messages through automatically controlled stations, with an exception for some data modes. Read the paragraph rather than relying on a summary. Power (§97.313): the general ceiling is 1500 W PEP, and all stations must use the minimum power necessary to carry out the communication. Some segments have lower limits. The 30 m band is capped at 200 W PEP, and Technician HF privileges also carry a 200 W PEP cap. The 60 m allocation is handled differently, with channelized operation and an ERP-based limit. Other rules in §97.303 and §97.305 restrict modes by sub-band, so don't stop at the power section. Prohibited transmissions (§97.113): the main categories are: Communications in which the control operator has a pecuniary interest, or that are on behalf of an employer. There are narrow exceptions, such as some teaching situations and occasional sales of personal station equipment that are not a regular activity. Music, except incidental retransmission from certain space stations. Obscene or indecent language. False or deceptive signals. Messages encoded for the purpose of obscuring their meaning. There are limited exceptions for things like space-station telecommand. Broadcasting, meaning transmissions intended for the general public, apart from the permitted one-way types such as beacons and code-practice transmissions. Willful or malicious interference is handled in the general standards in §97.101. Don't lump encryption in with 'privacy,' because the rule is about obscuring meaning. Standard digital modes with published specifications aren't the issue, but encrypting traffic is. That distinction trips people up.
-
Remote station control compared: vendor LAN solutions, RigPi-style controllers, SDR receivers, and where the rules and security issues bite
I'd stress the licensing and control-operator side more, because it's easy to treat it as a footnote. With a hosted or shared remote station, work out first who the control operator is and whose licence the transmission is made under. In many places the rules of the country where the transmitter sits apply, and your own licence may or may not be recognised there. Don't assume that being able to log in means you may transmit. Check the national regulations and the host's terms. For your own station, the dull safety items matter as much as the software. Have a way to kill transmit and mains power from outside the shack, such as a network power switch on a separate path. Set a transmit timeout, and think about what happens if the VPN drops mid-over. Also decide in advance who can reach the station and how access is revoked, particularly if more than one person uses it. And a small note on the receive-only side. A KiwiSDR or WebSDR is handy as a second opinion on how you sound, but it's one listener at one location. It tells you whether a signal is propagating there, not whether your remote station is performing well. Treat the result as one data point.
-
SSB audio checklist: mic gain, ALC, processor, EQ and bandwidth for clean signals and weak-signal work
For DX, I'd split the problem into the transmit side and the receive side. On receive, the 2.4 kHz filter is a good default, but the useful trick is shifting the passband and narrowing only as much as the QRM requires. Many operators go straight to a very narrow filter, then find they can't tell sibilants apart and end up asking for repeats, which costs more time than the QRM did. Try 2.4 first, then step down to about 2.1 or 1.8 kHz if you need to, and see whether the callsign still comes through clearly. A noise reduction setting that's too aggressive can have the same effect and leave the voice sounding watery. On transmit, the DX operator has to copy you through fading and noise, so consistency matters more than loudness. Speak at a steady level with the mic at the same distance, and avoid trailing off at the end of your callsign. If you're running a processor, use only enough to even out the peaks. Keep the exchange short: callsign, report, and any information required. Longer transmissions leave more room for fading to swallow part of your call. Finally, check which split rules and calling frequencies the DX station is using before you call. A perfect signal on the wrong frequency, or on the wrong sideband for the band, doesn't get you into the log.
-
Breaking pileups on rare DX: split operation, timing, and knowing when to stay quiet
Good list. I would add one point about split. A lot of people set the offset once and never look at it again, but the DX operator's window often drifts. If he starts at "up 5 to 10" and then moves to "up 10 to 15" or says he is working only a specific region, a stale offset keeps you calling into the void. Check your TX frequency regularly, and keep your RX VFO on the DX at all times so you hear the changes. On the pattern point, it helps to separate two kinds of pileup behavior. Some operators are essentially random: the DX picks whoever he can copy. Others are rhythmic and will repeat the same cadence over and over. If you hear a clear pattern in his calls, such as always picking the loudest station or always the one just below the previous call, you can start to predict where to place your call. If you cannot work out a pattern in a minute or two, do not pretend you can. Place your call in a quieter part of the window and call at a different time than the crowd. Also, check your own signal on a reverse beacon or a similar tool if you are on CW or a digital mode. If skimmers are not copying you well, you may be fighting a station problem and no amount of timing will fix it.
-
Before you key up on a linked repeater: offsets, tones, time-outs and what's on the other end
One addition on tones. When a repeater listing shows two tone values, they are often the input (the tone you transmit) and the output (the tone the repeater may send). A lot of directories list only one, and that one is usually the input. If the repeater seems to be working but you can't hear it, check whether your radio is in a decode mode. In some radios the labels are confusing, for example "Tone", "TSQL", "DTCS" and "Cross", so read the manual rather than guessing at the menu names. Offsets are the other frequent trap. Radios that auto-set the shift from the band plan can be wrong for a particular repeater, especially anywhere the pair doesn't follow the local convention. If the listing says the shift is something unusual, set it manually. Also double-check the sign. A plus when it should be a minus will not open the repeater. For linked systems, a rule of thumb that holds up is to assume someone else may be listening far away. Pause longer than you think necessary, particularly on a system running through EchoLink, AllStar or a reflector, because Internet delay can add to the usual gap between overs.
-
POTA activation basics: park references, 10 QSOs, spotting, and logging without headaches
On logging, the main thing is to decide before you leave whether you will log on paper, in a phone or tablet app, or on a laptop. Whatever you pick, make sure it can export ADIF and that it has a field for the park reference (MY_SIG_INFO with MY_SIG set to POTA is the usual approach). Do a test export at home and look at the file in a text editor. It is a lot less stressful to find a missing park reference before the activation than after you have 40 QSOs in the log. For two-fers, the key is to make sure each park reference appears correctly in the log you submit. Different programs handle multiple references differently, so check your software's documentation and the current POTA guidance on log formatting rather than assuming it will split things correctly for you.
-
Starting Morse from zero: Koch vs Farnsworth, which tools, and how do you get past copying letters one at a time?
Koch and Farnsworth aren't really rivals. They solve different problems, and you can use both. Koch is about the order you learn characters. You hear every character at a real speed, usually somewhere around 18 to 20 wpm character speed, but you start with only two of them. When you copy those reliably (about 90% is the common threshold), you add a third, and so on. The point is that you never learn the code as dits and dahs to be counted. You learn each character as a single sound with its own rhythm. Farnsworth is about spacing. 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 your brain time to recognize a character before the next one arrives. A lot of Koch trainers let you set character speed and effective speed separately, so you get both in one tool. On the tools: LCWO.net is a free browser-based Koch trainer. It keeps your lesson progress in an account and later adds practice with words, callsigns, and plain text. It's easy to start with because there's nothing to install.G4FON's trainer is a Windows program that also follows the Koch approach. It's handy if you'd rather work offline or want finer control over settings.CW Academy is a different kind of resource: a structured course run by volunteers through CWops, with advisors and scheduled sessions. Check their site for current course levels and dates, since those change. It's useful if you want accountability and a human to listen to you.I'd put the chart away. If you learn "dah-dit-dah-dit" as a pattern to decode, you'll be translating forever. Aim to hear "C" as one thing, the way you hear a word rather than its letters. For a first-month plan: a short session every day beats a long one twice a week. Around 15 to 30 minutes works well. Pick a comfortable tone (many people use something in the 500 to 700 Hz range), and stick with a single trainer so the characters don't change on you. Don't skip days if you can help it, because the daily repetition does a lot of the work.
-
Planning a first SOTA activation: summit refs, the 4-QSO rule, VHF vs HF, and logging
Your understanding of the basics is right. Four QSOs, once per summit per year for points, and operating inside the activation zone. The one thing I'd add is to read the current General Rules and your association's rules, because details like winter bonus dates and which summits qualify vary by association and get updated. On VHF versus HF, a lot of people start with 2 m FM because the gear is light and there's no antenna to rig, but it depends heavily on where your summit is. A prominent summit near a populated area can give you four contacts easily. A remote one may leave you waiting on a calling frequency with no answer. HF takes more setup, but it lets a wider group of chasers reach you, and a spot on SOTAwatch usually brings callers in fast. A sensible plan is to bring both and use VHF to get the four in the log first, then try HF for extra contacts. For logging, the simplest option is paper or a notes app with UTC time, callsign, band, mode and the report. Write down the summit ref at the top once. Later you can transcribe it into the SOTA database's CSV format or its web entry form. Check the current column layout in the database help pages before uploading, because the format is specific. Don't rely on memory for times, and put a clock on the log sheet.
-
How do you separate real ham radio news from hype? Rigs, firmware, FCC/ARRL notices, and band conditions
The proposal-versus-final-rule problem is the one I'd put at the top of the list. A headline says "FCC wants to change X" and ten posts later people are acting like it's already in effect. The habit that helps is to look for the docket or the official notice, then check whether it's a notice of proposed rulemaking, a comment period, or an order with an effective date. Those are three different stages, and your operating doesn't change until the last one. For gear, I'd add that a trade show demo is a preview, not a review. Prototype units at a big event like Hamvention can change before production, in price, features, and sometimes the whole feature set. Take photos and spec sheets as a snapshot. Wait for shipping units and independent measurements before spending money. On firmware, one practical thing: keep a note of the version you're running and the date you updated, so if a digital mode setup suddenly misbehaves you can tell whether the radio changed or something else did.
-
Getting my first ham license: how do I find a test session, what's an FRN, and what should I study for Technician?
On studying: the exam questions come from a public question pool, so you can practice against the same pool the VEs use. Check which pool is current for your exam date. Pools are revised on a multi-year cycle, and an outdated book or app can leave you studying questions that are no longer on the exam. HamStudy is free and works well for most people. It has flashcard-style study with spaced repetition, plus practice exams that mimic the real format. Whatever app you pick, don't just memorize the letter of the right answer. Answer order can differ on the real test, so you need to know the content. The ARRL Ham Radio License Manual explains the reasoning behind the answers, which helps when a question is worded differently. A common approach is to read a chapter, then drill the matching questions in the app. If you're short on time, practice exams alone can get you through, but the explanations help the material stick. Some topics deserve extra time. Know Ohm's law and the power formula, the basic frequency-wavelength relationship, the amateur band names, and the rules on identification, licensing and operating. Learn the basics of antennas, propagation and RF safety. Take full practice exams until you pass consistently with a comfortable margin, not by one or two questions. After you pass, the VE team submits your paperwork through the coordinator, and the FCC then grants the license. Once it is granted, you can look yourself up in ULS (the FCC's Universal Licensing System) by name or call sign. Don't transmit until your call sign shows up there. The 'official' license is the electronic record, though you can print a copy. After that, a good first step is to listen on a local repeater before you transmit. Find one in a repeater directory and check its offset, tone and any club rules. Then join a local club or net. Technicians get all VHF and UHF privileges, so a handheld is a common first radio. Limited HF privileges are also available, so read the band plan to see exactly what you can use.
-
Picking a VHF/UHF antenna: J-pole, slim jim, 5/8 whip, collinear or yagi, and where the dB really go
On repeaters and satellites, polarization and isolation become the main design issues. Most FM repeaters use vertical polarization, so a vertical omni such as a collinear at the top of the tower is typical, with the duplexer and filtering handling the isolation between transmit and receive. If you use separate transmit and receive antennas, vertical separation is much more effective than horizontal separation at getting the required isolation. A few feet of vertical spacing can be worth a lot more than the same distance sideways. For satellites, linear polarization can be a poor match because the satellite's orientation and the Faraday rotation of the signal change the polarization you see. That is why dedicated satellite antennas are often circularly polarized, or crossed yagis fed to produce circular polarization, with a rotator for azimuth and elevation. For the strong FM satellites, a small handheld yagi with a handheld radio can work, because you can twist the antenna to find the best polarization as the pass goes on. A fixed vertical whip may work for brief high-elevation passes, but expect deep fades and a shorter usable window. Also keep a yagi or any directional antenna well clear of metal masts and other antennas close to it. Mounting the boom behind a metal mast or too close to a rooftop structure can distort the pattern and shift the match more than people expect.
-
Planning a first POTA activation: 10 QSOs, spotting, two-fers and logging habits worth getting right
On mode: if you're going for the first 10, pick the one you're most comfortable running. Phone tends to draw the most hunters, but a clear frequency and a steady rhythm count for more than the mode. CW at QRP can work very well because many hunters and automated spotting networks cover it. FT8 or other digital modes are fine too, but check the current POTA guidance on how digital contacts and spots are handled. For the UTC rollover, write the cut-off time in local time on your plan before you leave, and put a clock set to UTC in your logging screen. If you're a few contacts short close to 0000 UTC, you can either stop and carry on after the rollover or plan for the contacts to count toward the next day. Whichever you choose, decide it ahead of time, not at the last minute.
-
Digital mode station checklist: audio levels, CAT, time sync and what decode thresholds actually tell you
On time sync, FT8 and FT4 depend on all stations agreeing on the start of each period. WSJT-X shows the time offset, DT, for each decode, and consistently large positive or negative DT values across many stations usually mean your clock is off, not theirs. You can often decode with a clock a second or so out, but your sensitivity suffers and your own transmissions may not be decoded by others. On Windows, the built-in time service can drift between syncs, which is why people use a dedicated NTP client or a GPS-based source. On Linux, chrony or ntpd generally do a good job. If the station has no reliable internet, a GPS receiver with a PPS output is the accurate alternative. In all cases, check the offset against a trusted source, rather than assuming the PC is right. Grid squares are the other piece people often leave for last. The Maidenhead locator is a letter-and-number code: two letters for the field, two digits for the square, and optionally two more letters for the subsquare. FT8 and similar modes normally exchange the four-character version, for example FN31, which is plenty for awards and for working out distance, but a six-character grid is more useful for VHF and weak signal work where squares matter. Make sure the grid in your software is the one for the operating location, particularly if you are portable, because wrong grids pollute reports and skew distance calculations. For mode selection on a marginal path, one practical way to think about it is by what the path does. For steady but weak HF signals, FT8 or JS8Call at a slower speed is a good match. For long, patient reporting of propagation, WSPR gives you a map without anyone being at the keyboard. For meteor scatter, MSK144 is built for the short bursts. For EME or troposcatter, Q65 with an appropriate period length and tone spacing is the design target. For email over radio, Winlink can be run over several modems; VARA is widely used but is proprietary and has free and licensed versions with different speed limits, so check the current terms from the author. For casual chat on a quiet band, PSK31 or an MFSK mode in FLDIGI is still fine. For rough conditions where you want to hold a conversation, Olivia is worth trying. The mode that decodes at the lowest SNR is not always the best choice. If you need to exchange information quickly, speed and a clear exchange format count for more than a few dB.
-
Planning a dual-band mobile install: FTM-500D vs ID-5100A vs TM-D710G, wiring, noise and cross-band questions
Adding to the noise, mounting and etiquette side. For noise, work from simplest to hardest. First determine what kind it is. Whine that rises and falls with engine RPM is usually alternator or charging-system related. A ticking that follows RPM is typically ignition. Hash that doesn't change with engine speed often comes from something added to the vehicle, such as LED lighting, USB chargers, dash cams or DC-DC converters. Test by switching accessories off one at a time and see whether the noise changes. Also check the squelch is set above the noise floor, and test with the engine off, then running, then with accessories on. On FM, a noisy received signal on 2 m or 70 cm is often something you can pin down this way. Fixes include a clean power run directly to the battery, a good ground, ferrite chokes on the offending device's cable, and replacing a poor cheap charger. Add filtering only after you've identified the source. For mounting, a roof-center NMO mount usually gives the best antenna performance on VHF/UHF, because the metal roof acts as a ground plane. The coax goes in through a door or trunk seal with a purpose-made pass-through or flat jumper, not pinched. Tune or at least check SWR on both bands with a meter, preferably an antenna analyzer. Mount the radio body or head so nothing obstructs the airbag deployment path, so cables cannot snag the pedals, and so you can operate it without looking down for long. Keep the antenna and the radio's transmit power away from people's heads as sensible RF exposure practice. On etiquette, the legal side varies by location. Some places restrict handheld devices or require hands-free use. Beyond that, the common-sense rules are: keep transmissions short, don't start a conversation in heavy traffic, let a passenger operate the radio if you need to change settings, and be ready to drop out of the QSO if you need to concentrate on driving. On a repeater, listen first, leave a pause between overs, and say your callsign clearly. If you want a contact, saying "mobile" with your callsign is a normal way to announce yourself. Check your local band plan before using a simplex calling frequency, and move off it once the other station answers.
-
Radio mods that are worth doing, and where MARS/CAP, expanded RX and "open TX" mods get legally tricky
My order would be to measure first and mod second. Before opening the case, verify the basics: SWR on the antenna, supply voltage under transmit load, and whether the receive noise changes when you power down nearby gear. A surprising number of "radio problems" are antenna, coax or power problems, and no TCXO or filter will fix those. On expanded receive, I would add a warning about calibration of expectations. Some radios will tune the airband or other services but have poor sensitivity or selectivity there, so the S-meter and squelch behavior can mislead you. If you want serious listening outside the ham bands, a dedicated receiver or SDR with proper filtering is usually the better tool than forcing a ham handheld to do it. For the legal side, I would separate three things clearly: what the hardware can do, what the license allows, and what the agency or net allows. Having an unlocked radio is fine for receiving or for use on bands where you are authorized. The problem starts when someone decides that a capable radio means they are cleared to transmit anywhere. If an organization requires a specific programming procedure or approved equipment, follow their written process rather than a forum recipe.
-
Logging workflow for contests and daily operating: N1MM+, WSJT-X, Log4OM, ADIF, Cabrillo, LoTW and QRZ
On the log-handling side, here is a sequence that limits damage. Contest end: Check the log inside N1MM+ first: dupes, bad callsigns, wrong band or mode, time errors. The clock matters. Cabrillo times are UTC, and a computer clock that has drifted can cause busted-QSO penalties and mismatches in the sponsor's cross-check. Then generate the Cabrillo file for the sponsor. Cabrillo is a contest-submission format with a header (CALLSIGN, CATEGORY-OPERATOR, CATEGORY-BAND and so on) and QSO lines in an exact column layout. It is not an ADIF substitute. Always read the specific contest's rules for categories, exchange format, deadline and upload method, since sponsors differ, and run the file through the sponsor's checker if they offer one. Separate step, ADIF export: Export ADIF for the master logger. Before importing, back up the master log. Look at what the import does with fields like MODE and SUBMODE (FT4, for instance, is represented as MFSK with a submode), band, frequency, and the exchange fields (STX, SRX, SRX_STRING and app-specific tags). Import a small test file first. Most loggers have a duplicate-detection option on import, which usually keys on call, band, mode and time within a tolerance. Use it, and spot-check afterwards. Then uploads: Do LoTW through TQSL. The station location (DXCC entity, grid, CQ and ITU zones) must match where you operated. Portable and contest-expedition logs are the ones that most often get signed with the wrong location. LoTW only accepts files signed by TQSL, so an ADIF cannot be sent raw. QRZ and Club Log accept ADIF uploads or API-based sync, and both can be done from Log4OM, DXKeeper or HRD Logbook. The exact account requirements and API-key setup change over time, so check each service's current help pages. Do a small upload first to confirm the callsign, location and date range, since bad records are annoying to remove from three places. One more tip: keep the country file (cty.dat, and Club Log's exceptions data) updated in each program. Mismatched prefix data is a common reason one program says a QSO is a new multiplier and another disagrees.
-
How do you sort real ham radio news from hype? Rigs, firmware, band openings and rule changes
On propagation news, I'd say stop reading predictions and look at what's happening right now. Spotting networks show real activity: PSK Reporter for digital modes, the Reverse Beacon Network for CW and RTTY, WSPR for low-power path checks, and the DX cluster for what people are working. If 10 meters is "supposedly open" but PSK Reporter shows nothing heard from your area, the forecast isn't helping you. For the numbers, I'd look at the solar flux index and the planetary K and A indices together. High flux generally helps the higher bands, but a geomagnetic disturbance can wipe out a path, especially one crossing the polar regions. Low-band operators often care more about the K-index than the flux figure. Aurora, sporadic E and tropo ducting also all produce openings that have nothing to do with the solar cycle, so "the cycle is up" doesn't tell you everything about 6 meters or VHF. A good habit is to log when and where a band opened, along with the indices at that time. After a few months you have your own data, which beats most headlines.
-
Prepping for the Technician (Element 2) exam: what to study, how to use the question pool, and where people lose points
Your basics are right. Element 2 is 35 questions drawn from the Technician pool, and 26 correct (about 74%) passes. The pool is organized into subelements (T1 through T0), each split into groups, and the exam takes one question from each group. So you can't skip a whole topic and hope the draw goes your way. Every group shows up, and the exam is spread broadly across the material. Memorizing alone is risky for two reasons. The pool is revised on a multi-year cycle, so confirm which pool your exam session uses (your volunteer examiner team or the coordinating organization can tell you). Also, the answer order is usually shuffled, so "the answer was C" doesn't help. You need to recognize the content of the right answer. Where I'd put the time: Rules and privileges (T1): Technicians get all amateur privileges above 30 MHz, plus limited HF access (certain CW segments on 80, 40, and 15 meters, and CW, phone, and digital on parts of 10 meters). Know the general idea of why those allocations exist. Station ID is another reliable question area: give your call sign at the end of a communication and at least every 10 minutes during it.License terms: A license is valid for 10 years and has a grace period after expiration. Be careful with the exact wording of questions about renewal and the grace period.Electronics (T5, T6, T7): The math is light. Ohm's law (E = I × R) and power (P = I × E) cover most of it. Be comfortable rearranging them. Learn component symbols, and know what resistors, capacitors, inductors, and diodes do.Wavelength and frequency: The rule of thumb is wavelength in meters ≈ 300 ÷ frequency in MHz. That explains why 146 MHz is called the 2-meter band, and the shortcut handles several questions.Don't skip safety and RF exposure. They're a small slice, but they're among the more learnable questions.