Everything posted by Mod_Dan
-
APRS on 144.390: choosing paths, iGate settings, beacon rates and Mic-E vs. Direwolf for a tracker and fixed station
On the "heard locally but not on aprs.fi" question, read the raw packet rather than guessing. aprs.fi's raw packet view shows the path and the q-construct the server appended. A qAR entry followed by an iGate callsign means that iGate received it off RF and could transmit. qAO indicates an RX-only gateway. If nothing shows at all, work through the basics. Does your frame actually decode at the iGate, or only at your own radio? Is the destination field legal? Does the path contain TCPIP or NOGATE, which tell iGates not to pass it? Is the iGate's APRS-IS connection even up? For beacon timing, fixed stations sitting in the same spot rarely need to transmit more often than every 10 to 30 minutes. If you are on a digipeated path, a once-a-minute beacon from a house is just noise to everyone else. Weather stations deserve the same restraint, since a packet every few minutes on RF is wasteful when the iGate can see the data. If you have internet at the station, send the frequent weather updates to APRS-IS only, and keep a slow RF beacon for the benefit of people with no network access. Weather reports are fixed-format text. The wind direction field is c, speed s, gust g, temperature t in degrees Fahrenheit, rain fields r, p and P, humidity h (00 means 100%) and barometric pressure b in tenths of hPa. Many first-time weather setups go wrong with the units, so check them before blaming the radio.
-
Combining POTA and WWFF activations: how do you handle KFF references, the 44-QSO rule and logging?
On the logging side, the main thing is to keep the reference fields clean. In ADIF, the activator's own reference goes in MY_SIG and MY_SIG_INFO (MY_SIG set to WWFF, MY_SIG_INFO set to the KFF reference). For a hunter's log the matching fields are SIG and SIG_INFO. Different programs and uploaders have changed what they accept over time, so test with a small file or read the current instructions for the WWFF logger before you upload a whole season of contacts. If you're doing both programs from one site, I'd keep a single master log of the QSOs, then export a version for each program with the right reference. Don't paste both references into one field and hope for the best. Most uploaders will reject it or misread it. Also check that the date and time are UTC and that the callsign you used on the air matches the one on the upload. Mismatches there are a common reason a contact fails to match. One more point is the 44-contact target. If the band is slow, it is worth planning for more than one band or mode instead of staying on a single frequency and calling CQ until dark. Look up the current rule on whether the contacts must fall within one UTC day, because that changes how you split a long activation around midnight UTC.
-
One master log or separate contest logs? Keeping N1MM+, WSJT-X, Log4OM and the online uploads from colliding
For uploads, I'd keep the order simple: finish the contest log, run any dupe or callsign checks, and submit the Cabrillo. Only then push to LoTW, QRZ and Club Log from the master log. Uploading while the log is still being corrected means you have to fix the same QSO in several places. A few details to watch with each service: LoTW needs a TQSL certificate and a station location that matches where you operated. That means DXCC entity, grid, and CQ and ITU zones. If those are wrong, the QSOs still get signed and uploaded but won't confirm the way you expect. Matching also depends on band and a mode group (CW, phone or data), plus a time window. That makes clock accuracy and honest UTC times matter, and WSJT-X users need a properly synced PC clock for decoding anyway. QRZ's logbook upload uses a logbook API key, not your password. Club Log uses its own application password and API setup. Either way, read what your logger does when you re-send a QSO that's already there. Some tools mark QSOs as 'sent' and skip them, while others will happily resend a whole ADIF. For mode mapping, look at what the logger writes for FT4, FT8 and MFSK-family modes. ADIF has MODE and SUBMODE fields, and tools differ in how they populate them. Spot-check a few exported records before trusting a bulk import. On dupes, treat the band map as a helper rather than the rule. Its worked/new-multiplier colors are only as good as the contest definition and the current mode setting. If a contest counts one QSO per band, or per band per mode, check that the logger's dupe setting matches. For rotators, keep the controller (PstRotator, HRD Rotator or whatever you use) separate, and let the logger send only the bearing. That way a rotator program crash won't take the log down with it.
-
Gain, overload and noise floor in budget SDRs: how to tell what your dongle, antenna and software are really doing
One check that is easy to skip is the sample rate versus FFT resolution. Resolution bandwidth is roughly sample rate divided by FFT size, so a 2.4 MS/s capture with a small FFT can hide narrow carriers and make the noise floor look higher than it is. Raising the FFT size or narrowing the span usually gives a more honest picture before you touch the gain. Also remember that the spike at the center of an RTL-SDR display is a DC artifact of the architecture, not a real signal. Offset tuning or an offset in the software avoids mistaking it for a carrier. For decoding, the usual chain is receiver software, a virtual audio cable, then the decoder, for example WSJT-X or fldigi. Set the receiver to USB for most HF digital modes. Keep the audio level moderate so the decoder is not clipped, and make sure the PC clock is accurate for time-synchronized modes like FT8. If decoding fails on a clean signal, check audio sample rates on both ends and the PPM correction, which matters most at VHF and UHF where a small ppm error becomes a large frequency error.
-
ARES, RACES, SKYWARN, CERT: how do the pieces fit, and what should a new volunteer train on first?
For a first 90 days, I'd put the order as: contact the local EC, take the FEMA IS courses, and start checking into the regular nets before buying anything. The paperwork and the net habits take longer to build than a radio setup does, and a lot of groups have requirements like ID badges, background checks for some served agencies, or a signed agreement before you can be deployed. On gear, a dual-band handheld, a spare battery or battery case, a decent external antenna option and a way to power things off a vehicle or portable battery will cover most early needs. Add a notebook, pencils (not pens, since they fail in the cold and when wet), blank message forms, a copy of your repeater and simplex frequency plan, and a simple ID such as a badge or vest if your group uses one. A go-bag should hold what you need for the assignment, plus water, food, medications, and clothing for the duration. It should not be your whole ham shack. Check your group's plan for what's expected and for any shift length limits. The other piece is knowing your local plan. Read the county emergency operations plan if it's public, and ask the EC where the amateur radio annex fits. Knowing who can activate you, and how you'd be called, avoids the situation where a well-meaning operator shows up uninvited.
-
What do you actually check before deciding a band is open? SFI, K-index, VOACAP, or just listening for beacons?
On the VHF side, the indices help less than you would think. Sporadic E and tropo ducting don't follow SFI, and both depend on local atmospheric conditions. For Es, watch the 6 m and 10 m spots and any beacons; once a cloud shows up, the opening can move quickly and shift between regions. For tropo, pressure patterns and inversion forecasts tell you when to listen, but the confirmation is hearing distant repeaters or beacons that you normally can't. Two caveats on WSPR. First, a spot only tells you that a receiver heard a transmitter. A band that looks dead on the map may only mean nobody was transmitting or listening along that path. Second, WSPR signals are weak and narrow (a few Hz of signal in a 200 Hz window), so a WSPR decode does not guarantee an SSB or CW contact is workable. The SNR it reports is helpful, but you need to account for the difference in mode and bandwidth. For NVIS, the useful number is not SFI but the local critical frequency. If you only care about regional coverage, check an ionosonde map if one is available near you, pick a frequency comfortably below foF2, and use a low horizontal antenna. If you are running too high a frequency, you will get a skip zone instead of coverage.
-
Planning a field comms station: power layout, noise control, antennas and checklists for EMCOMM deployments
On noise, the biggest lever is distance and sequencing. Get the generator placed first, downwind of the shelter and well away from the operating position, both for carbon monoxide and for RFI. A CO alarm in the tent is cheap insurance even when the generator is far away, because wind shifts. Keep fuel storage separate, and let the engine cool before refueling. Inverter generators are cleaner than old conventional ones in terms of waveform, but the inverter and engine ignition can still radiate on HF. Test before you commit: tune to a quiet frequency on 80, 40 and 20 m with the generator off, then on, and compare the S-meter and the noise floor. Try with and without eco throttle, since the changing engine speed can turn a steady hiss into something that hunts up and down. If the AC output cord is radiating, ferrite chokes on the cord near the generator, and sometimes near the charger, can help. Use a ground-fault protected outlet for anything outdoors, and follow the manufacturer's guidance on grounding and neutral bonding rather than improvising with a rod and a jumper. Solar is quiet in the sense that panels do not make noise, but the controllers can. Some inexpensive MPPT units put out a lot of broadband hash on HF. Use a controller with a proper LiFePO4 charge profile, keep it and its wiring away from the antenna and receive gear, and check noise with it connected and disconnected. If a controller is a problem, move it, add chokes on both the panel and battery leads, or run the panels disconnected from the station while you operate. One last LiFePO4 point: check the cold-weather charging limits on your battery. Many BMS designs will not accept charge below freezing unless the battery has built-in heating, and a solar plan that ignores this can leave you with a battery that quietly stops charging.
-
J-pole, slim jim, 5/8 wave or yagi? Matching VHF/UHF antennas to polarization, pattern and feedline
On the mobile side, NMO is usually the best choice if you are willing to drill a 3/4 inch hole. It gives a solid mechanical connection and a good ground contact through the body of the mount to the roof. The roof center gives the most symmetrical pattern. Moving the antenna to a fender or trunk lip skews it, and the pattern gets blocked in the direction of the vehicle body. A mag mount is the quick alternative, but a plain magnetic base couples to the metal capacitively. Rust, paint or dirt, or a mount sitting on a ribbed roof, can shift the SWR and cause intermittent behavior. Wiping both surfaces clean before placement is a cheap fix. For 5/8-wave versus quarter-wave, the 5/8's advantage is more about lower elevation angle than a raw gain figure. It also loses much of that edge if the ground plane is small, which is common on small cars and on trunk-lip mounts. A quarter-wave is more tolerant and also much simpler to tune. On 70 cm the whips are short and the ground plane problem is less severe, so a dual-band antenna that uses a longer radiator on 70 cm can have a rather different pattern than on 2 m. Check the manufacturer's pattern notes if you care about it. As for connectors, mag mounts often come with a PL-259 on thin RG-58-type cable. That is fine for short mobile runs at 2 m. At 70 cm the cable loss starts to matter, and an inexpensive PL-259 adds uncertainty. If you are building your own mobile cable, a crimped or well-soldered connector is a more reliable option than a poorly installed one. Route the cable under door seals carefully so it does not get pinched, since a crushed coax is a common cause of a high SWR that 'comes and goes'.
-
Band plan vs. FCC rules: how do you decide where to operate and how close to the band edge is safe?
Start with the distinction: Part 97 is the law, and the ARRL band plan is a voluntary agreement on how to share the space. The FCC defines which license classes may use which segments, the permitted emission types, and the power limits. The band plan tells you where operators conventionally put CW, digital, SSB, beacons, and so on. You can be fully legal and still be parked on top of an FT8 cluster or a net. On privileges, the broad strokes for US licenses are these. Technicians have limited HF: CW on parts of 80, 40 and 15 meters, CW and data on 10 meters from 28.000 to 28.300, and SSB on 28.300 to 28.500, with a 200 W PEP limit. Technicians also have all amateur privileges above 50 MHz. Generals get most of every HF band but not the lower slices reserved for Extras. For example, General phone on 80 m starts at 3.800 where Extra starts at 3.600, on 40 m at 7.175 versus 7.125, on 20 m at 14.225 versus 14.150, and on 15 m at 21.275 versus 21.200. Extras have everything. Check the current FCC chart for exact segments, because it's easy to misremember one edge. For the band edge itself, remember that the dial frequency is not where your signal ends. With suppressed-carrier SSB, a USB signal extends about 2.7 to 3 kHz above the dial and an LSB signal about the same amount below it. So at the bottom of an LSB phone segment, set the dial a few kHz inside the edge, not right on it. At the top of a USB segment, do the same in the other direction. The same goes for digital modes: the whole signal's bandwidth has to fit inside the segment, not just the dial frequency. Common digital spots are worth knowing, since the modes cluster there. FT8 is generally found around 1.840 on 160, 3.573 on 80, 7.074 on 40, 10.136 on 30, 14.074 on 20, 18.100 on 17, 21.074 on 15, 24.915 on 12, 28.074 on 10 and 50.313 on 6 m. These are dial frequencies in USB mode, and activity patterns can shift, so confirm in your logging or decoding software before you rely on them. The QRP CW calling frequencies are also widely known, such as 7.030 and 14.060. For 60 meters, the US doesn't have a continuous band. It uses five channels, and General and Extra licensees may use them under an ERP limit relative to a half-wave dipole, with a narrow bandwidth. The channel centers are 5332, 5348, 5358.5, 5373 and 5405 kHz. For USB the dial is set 1.5 kHz below center, so 5330.5, 5346.5, 5357.0, 5371.5 and 5403.5. Don't just tune a nearby frequency, because the channelization is what makes it legal. Verify against the current rules before transmitting, as the 60 m rules have changed over the years.
-
SSB audio chain: mic gain, ALC, compression, EQ and bandwidth for clean, readable signals
I would be a bit careful with presence boosts. A lift around 2 to 3 kHz can help intelligibility in the right conditions, but on a mic that is already bright it can sound sharp, and a processor can make it worse by emphasizing sibilance. If the audio is hard to listen to on headphones, it is probably tiring for the other operator too. A practical approach is to adjust one thing at a time with the same sentence and the same distance from the mic. Change the low cut, then the EQ, then the processor, and ask for comparison reports instead of a general 'sounds good.' Also remember the receiving side: someone using a 2.4 kHz filter or a narrower one will never hear your extreme highs, so the central part of the voice matters most. When the band is rough, clear articulation and a clean, stable level usually beat aggressive processing.
-
How do you separate real ham radio news from hype? Rigs, firmware, FCC/ARRL notices, and band openings
On propagation, I'd treat the solar numbers as a forecast and the spotting networks as the actual result. If 10 or 12 meters look promising, watch PSKReporter or the RBN for a bit before concluding anything. A few FT8 spots from stations near you tell you more than a headline about the cycle. It also helps to remember that not every opening is F2. Sporadic E can produce short-skip on 10, 6, and sometimes higher, often independent of what the sunspot count is doing. And the geomagnetic indices matter: a quiet-looking flux number with a rising K index can still mean poor conditions on polar paths. Checking NOAA's Space Weather Prediction Center alongside the spotting maps gives a more balanced picture than either one alone.
-
Small lot, HOA, no tower: how do you rank EFHW, OCFD, doublet, vertical and loop options by actual performance, not just SWR?
One thing about the vertical: the radial advice depends on what you can hide. A lawn vertical with buried radials is nearly invisible, and the radials can be put down with a slit trench or just laid on the grass and left to be overgrown. If you can only manage four or so radials, make them resonant and elevate them a few feet rather than lay them on the ground. Elevated radials are less lossy per wire, and drooping them at about 45 degrees brings the feedpoint close to 50 ohms. A ground-mounted vertical with many radials is closer to 36 ohms, and the match is usually fine either way. Verticals are good for low-angle DX and bad for local noise. If the neighborhood is noisy, a vertical will often hear more of it than a horizontal wire does, because of the polarization. That's where a small receive loop or a magnetic loop earns its place. It's a good receiver in a noisy location, even if on transmit it only makes sense on the higher bands or when a larger diameter is possible. On the trap dipole question: traps shorten the antenna and give multiband operation without a tuner, but each trap adds some loss and narrows the bandwidth, especially on the lower band. If you have the room for a full-size wire dipole, it will usually be more efficient than a trapped one. If you don't, a trapped dipole is a legitimate compromise, and the best way to judge it is the height and the length available rather than the label.
-
EME from 2 m to 10 GHz: station requirements, JT65/Q65, polarization, libration and sked planning
I'd add the operating side, because even a good station can waste a lot of time if the setup is wrong. For JT65 and Q65, the tone spacing is set by a submode letter. Wider submodes tolerate more spreading, but they cost some sensitivity. Libration is the Moon's slow rocking, which spreads the echo in frequency and gives fast flutter fading. The spread grows with frequency, from a fraction of a hertz on 2 m to tens of hertz at 10 GHz. This is why the common choice moves from narrow submodes on 2 m towards wider ones on 23 cm and the microwave bands. The exact letter used on each band is set by local practice and by the WSJT-X documentation, so read the current guide and ask on the chat page rather than trusting my summary. Q65 is generally regarded as more tolerant of spread and fading than JT65, and it uses ordinary full messages. JT65 has the shorthand messages for confirming a QSO. For sked planning, check the window when the Moon is above the horizon for both stations. You also want the Moon away from the galactic plane and the Sun where possible, because sky noise rises with both. A planner such as the VK3UM EME calculator, or the astronomical data in WSJT-X, will give you a combined degradation figure. Agree beforehand on the band, mode and submode, the frequencies, and who transmits in the first period. Allow a few minutes of echo testing or alignment before starting. On tracking, work out what your pointing accuracy actually is before you buy a rotator or build a mount. For a dish, take the beamwidth as about 70 times wavelength divided by diameter, in degrees, and you will want to be accurate to a fraction of that. A tracking error that is invisible on 2 m can drop you out of the beam on 10 GHz. Use software that applies Doppler correction, and check the dish's pointing against the Sun (for solar noise) or the Moon itself. Also keep a log of what actually worked on each sked, because that is what will help you plan the next one.
-
Technician to General: how should I split my Element 3 study time (HF sub-bands, propagation, antennas, digital)?
Start with the pass mark, because it shapes the plan. You can miss 9 questions out of 35 and still pass, so you don't need to master every corner of the pool. You do need to avoid giving up whole topics. Read the subelement layout of the current pool and see how the 35 questions are spread across it. Spend your time in proportion to that spread, not in proportion to what feels interesting. Sub-bands: don't memorize them as a flat table. Learn the pattern first. On most General HF bands the bottom segment is CW and data, and phone sits in the upper part. On 30 meters there is no phone at all, only CW and data, and the power limit there is lower than on other bands. Once the pattern is in your head, the numbers are easier to hang on it. For the exact edges, work from the band chart in the current ARRL material or from FCC Part 97.305. Don't rely on a table someone else typed up. Also learn how 60 meters differs from the other bands, because the rules there have a different structure. There is also a practical trap that exams like to test. When you're on SSB, the dial frequency is not the edge of your signal. Use LSB on 80 and 40 meters and USB on 20 meters and above. If you're near a band or sub-band edge, work out where the whole signal sits, not just the suppressed carrier frequency. Propagation is mostly cause and effect, so build a mental model instead of memorizing sentences. The D layer absorbs lower HF frequencies during the day and fades after sunset. The F layer is what carries long-distance signals. MUF is the highest frequency that gets refracted back for a given path. Higher solar activity generally pushes MUF up and makes the higher bands more usable. Know what solar flux, the K index and the A index are measuring and which direction is good or bad for HF. Grayline, long path, NVIS and skip zone also show up regularly. Antennas are worth the time because a lot of the questions are about relationships. A half-wave dipole is roughly 468 divided by the frequency in MHz, in feet. A quarter-wave vertical is roughly 234 divided by the frequency. Practice a few of these by hand. Also know what a balun does, why coax feeds a dipole through a choke or balun, what a trap does, and why SWR is not the same thing as efficiency.
-
Building a Wire Antenna from Scratch: Wire, Insulators, Chokes, Feedline and Modeling Before You Cut
One thing I'd add on trap antennas, since you mentioned them: a trap is just a parallel LC circuit that acts like an insulator at its resonant frequency, so the antenna looks shorter on the higher band. That also means each trap has to handle real voltage and current, and the components need to be rated for your power level. The coil Q sets the losses, and capacitor dielectric matters. Low-loss capacitors such as NP0/C0G ceramic, mica or properly rated coax-stub traps are the usual routes. The wire between traps is also shorter than the free-space length would suggest, because the traps look inductive below their resonance and shorten the physical length needed. That is why a trap dipole rarely follows the plain formula. The practical way to tune a trap is to measure it on its own, with a small loop coupled to an antenna analyzer or a grid-dip-type setup, and set it to the target frequency before it goes into the antenna. Then trim the end sections for the lower band and check the upper band separately. The trade-off is narrower bandwidth and some loss compared with a single-band dipole. A fan dipole or a simple resonant dipole per band fed from one coax avoids trap loss entirely, though the elements interact and need spacing and a bit of trimming.
-
Building a lightweight field kit: EFHW or linked dipole on a telescopic pole, and how much battery do you really need?
For mostly POTA with occasional SOTA, I'd lean toward the EFHW. It's the faster to deploy of the two, and speed matters when you have a limited window or want to start calling CQ before the weather changes. A band change is just a QSY. You do need to be careful about where the matching box sits and how the feedline runs. A short length of coax with a common mode choke near the radio helps keep RF off your rig and your logging device, and if the radio acts up on one band, that is often the first place to look. A linked dipole is still a great choice if you like predictable behavior. You can see exactly what the antenna is, with no transformer to run hot and no feedline interaction. Mark each link clearly and carry a spare bit of cord. If you're mostly on one or two bands, it's very hard to beat for simplicity. On the battery side, a lot of people overbuy. Work out your actual power budget: a 5 to 10 W CW or SSB session of a couple of hours doesn't need a huge pack. A bigger pack is for FT8, higher power, or a long park day with a lot of transmitting. Also check the receive current of your radio, because that's what drains the battery when you're waiting for calls.
-
Keep it, sell it, or fire it up? What makes an old rig worth a spot on the operating desk
Adding some caution on the power-up question. Even a clean-looking rig shouldn't just be plugged in and keyed. Look for bulging or leaking capacitors, check the power cord, and inspect the inside for mouse nests or burnt smells. If the rig has been stored for decades, many people prefer to bring it up gradually or replace the main filter caps first. Opinions differ on variac use, so it's worth reading a couple of repair guides for your specific model rather than copying one forum post. As for operating value, I'd say the receiver is the deciding factor. If you mostly do casual ragchewing on a quiet band, an older receiver can be great. If you're chasing DX in a crowded contest weekend, a modern radio will probably make life easier, and you can still keep the old one for the pleasure of using it. The best compromise I can think of is a modern radio for the real work and a vintage rig on its own antenna switch position. That way the old gear gets used regularly without becoming the single point of failure for your station.
-
Element 4 prep: what's the best way to handle the op amp, filter, and Smith chart questions?
I'd do both, in a particular order. Read a short explanation of a topic first, then do the pool questions for that topic only. If you drill without the explanation, you'll end up memorizing letter choices instead of the reasoning, and the wrong answers in the pool are often built to catch that. For the calculation questions, write the formula down before touching the calculator. Many of them are one-step: resonant frequency, reactance, dB conversion, op amp gain, or modulation index. Most mistakes come from unit errors (kHz vs Hz, pF vs nF), not from the math. It also helps to sanity check the result. If a passive filter answer gives gain above unity, something went wrong. Also check your exam session's calculator rules ahead of time. VE teams usually allow a basic calculator, but they may require memory to be cleared, and that can vary a little by team.
-
Good on-air habits: how do you handle CQ calls, breaking in, nets and shared frequencies?
For new operators, I think the biggest confidence-builder is to listen for a while before transmitting. Listen to a couple of nets, a few CQ exchanges and a roundtable. You'll quickly pick up how people structure an over, where the pauses fall and how they hand off. Writing your own callsign and a few standard exchanges on a card helps too, because the first few times on the air are the ones where people forget their own call. It's also fine to say you're new. Most operators will slow down, repeat information and help you through an exchange. If someone corrects you on air, take it as information, not criticism, and ask them to explain if it isn't clear. On interference, I'd also suggest checking your own station before blaming someone else. Overdriven audio, too much power for the contact, a poor ground or a noisy power supply can all cause problems that sound like someone else's fault. Using the least power needed to complete a contact is both good practice and good neighbourliness.
-
Choosing an SDR for HF through UHF: dynamic range, upconverters, and where the noise really comes from
On the upconverter question: for an RTL-SDR, an upconverter is generally the cleaner route to HF than direct sampling, because the converter gives you proper filtering ahead of the tuner. The cost is an extra oscillator, which adds its own drift and spurs. The software has to know the offset. A common converter uses a 100 MHz or 125 MHz oscillator, so a 7.100 MHz signal appears at 107.100 or 132.100 MHz in the dongle. SDR# has a shift option for this. In HDSDR and similar programs you usually apply the offset through the LO or frequency settings. If the dial reads wrong by exactly the oscillator frequency, the offset has the wrong sign or is missing. If it is off by a few kHz, look at the ppm correction instead. Your gain test is sound as a starting point, but add one more check. Find a strong local signal, such as a broadcast station, and see whether ghost signals appear elsewhere and move when you change the gain. If they do, the front end or ADC is being overloaded, and it is not a real signal. A filter, for example an FM broadcast notch on a VHF dongle, often does more than reducing gain, because it removes the strong signal before it reaches the amplifier. One caveat on ADC bits: the theoretical figure is about 6 dB of dynamic range per bit, but real-world performance depends on the tuner, the filtering, the sample rate and the noise in the system. An 8-bit dongle can be perfectly usable with sensible filtering on a narrow job, and a higher-bit receiver will still overload if you feed it a poor antenna system at the wrong gain.
-
Band plans vs. license privileges: how do I work out where to operate and where the edges really are, 160 m through 33 cm?
For VHF/UHF, here's a rough map. These are the commonly used calling frequencies from the ARRL band plan, but local coordinators can allocate differently, so check your local plan. 6 m (50 to 54 MHz, Technician and up): the bottom of the band is CW and beacons, with SSB above about 50.1. 50.110 MHz is the intercontinental DX calling frequency and 50.125 is the domestic SSB calling frequency. 52.525 MHz is the FM simplex calling frequency, and FT8 is commonly at 50.313. 2 m (144 to 148 MHz): the weak-signal section is at the bottom of the band (CW and SSB, around 144.100 to 144.300), with 144.200 as the SSB calling frequency. Further up are beacons, the FM repeater sub-bands, a satellite section around 145.8 to 146.0, and FM simplex including 146.520 as the national calling frequency. APRS in North America is on 144.390. 70 cm (420 to 450 MHz in the US): 446.000 is the national FM simplex calling frequency. Weak-signal CW/SSB calling is around 432.100, and there are satellite and repeater sections elsewhere in the band. There are geographic restrictions in parts of 420 to 450, especially near the Canadian border and certain radar sites, so check the footnotes in §97.303. 33 cm (902 to 928 MHz): this band is allocated to amateurs in ITU Region 2 only (the Americas), and it's shared with ISM and Part 15 devices, so expect noise. 903.100 is the weak-signal calling frequency. FM simplex use is more local, so check what your area uses. 60 m is different from the other HF bands because it's channelized, not segmented. General and Extra can use five channels with a 100 W PEP ERP limit (relative to a half-wave dipole). The channel center frequencies are 5.332, 5.348, 5.3585, 5.373 and 5.405 MHz, and the USB suppressed-carrier dial settings are 5.3305, 5.3465, 5.3570, 5.3715 and 5.4035 MHz. Rules for this band have been revised over time, including a newer segment under secondary international allocation, so check the current §97.303 text and the ARRL page before you transmit. Internationally, the world is split into three IARU regions, and the allocations differ. Region 2 gets 3.5 to 4.0 MHz on 80 m and 7.0 to 7.3 on 40 m, while Region 1 (Europe, Africa, the Middle East) has 3.5 to 3.8 and 7.0 to 7.2. 2 m is 144 to 148 in the US but 144 to 146 in Region 1, and 70 cm is 430 to 440 there. IARU regional band plans also set their own subdivisions, so a DX contact's idea of 'the phone segment' may not match your chart. If you operate abroad, the rules are the host country's (CEPT or reciprocal arrangements), not your home license class, so check those before transmitting.
-
Building a tiered go-kit: HT, mobile, power, antennas and the family plan. What does yours look like?
On the family plan, I would keep the simplest tool for each person. A licensed ham can carry a dual-band HT, but a younger relative may do better with a basic FRS radio with a clear channel and a laminated card that says what to do. Test it once in your neighborhood and again somewhere with more terrain or buildings so people know what range to expect. Be careful with channel naming too. FRS and GMRS share some channels, but power limits and license rules are different, so confirm what your radios actually allow and what each radio is certified for. If you want to use GMRS with the family, get the license and set up channels in advance. MURS is a good option for simple portable setups, and some people like it for short-range property or neighborhood use, but there are far fewer radio choices. For the first aid kit, rather than buying a huge bag, think about what you would use: bleeding control, bandages, gloves, any personal medications, blister care, and instructions. Take a first aid class so you know how to use the items, and replace expired products on a regular schedule. If you want to serve with a team, find out what your local ARES, CERT, or club group expects you to carry, because their requirements may be more specific than any general list.
-
Which phonetics should I use on air? Standard ITU/NATO vs. "ham phonetics", bad conditions, numbers, nets and emergency traffic
Numbers: in everyday amateur voice operation, plain digits are normal. The special forms you saw come from formal radiotelephony standards. ICAO aviation uses "tree", "fower", "fife" and "niner". The ITU maritime table uses Italian-flavoured forms like "nadazero" and "unaone". Hams rarely use those. The one exception most people adopt is "niner", because "nine" can be misheard (the German "nein" is the usual example). Say "zero" rather than "oh", and be consistent. If 5 and 9 keep getting confused, stress the vowel clearly and don't rush. Names and places: spell only the part that's likely to be misheard. "Name is Joe" usually needs nothing. "Name is Siobhan, Sierra India Oscar Bravo Hotel Alfa November" does. For place names, give the word, then the spelling, then the word again if needed. For grid squares, say the letters phonetically and the digits plainly, e.g. FN31 as "Foxtrot November three one". If you're sending a long string of letters, pause between groups so the other person can copy. Difficult conditions: speak slower rather than louder. Keep your cadence even and don't clip words. Don't run the phonetics together into one stream. Give the information once clearly, then once more only if asked. On SSB with QRM, repeat the callsign in standard phonetics and be ready to answer questions like "was that K or P?" with "Kilo, Papa". Over-emphasised, theatrical pronunciation can make things worse. Clean and measured works best. Prosigns and prowords: prosigns such as AR (end of message), SK (end of contact), BT (break/pause), K (go ahead) and KN (go ahead, named station only) belong to CW. On voice you use the spoken equivalents: "over", "clear", "break", "go ahead", "say again". Avoid mixing them, like saying "AR" on SSB. Also be careful with "Roger". In many contexts it just means "received", not "yes", so use "affirmative" and "negative" for answers. Nets and emergency traffic: nets usually run on a simple structure. Net control gives the callsign, takes check-ins (often suffix only, phonetically), and handles traffic one station at a time. Check-ins are typically short, because net control is writing them down. In formal message handling, a radiogram (as in the ARRL/NTS format) carries a precedence of Emergency, Priority, Welfare or Routine, and numbers or unusual words are often spelled out or confirmed. For emergency traffic, "Mayday" and "Pan-pan" are properly maritime and aviation distress and urgency calls. Ham nets typically use plain terms like "emergency traffic" or "priority traffic", and procedures vary by local group and served agency. Follow whatever your net's script says, and when in doubt, keep it brief, use standard phonetics, and read messages back for verification.
-
Sequential vs. vanity callsigns: how the groups work, what to check in ULS, and what holding a call actually involves
Good overview. One thing that trips people up is the difference between what you're eligible for and what's actually available. A call can look free in a lookup tool and still be unavailable because it's inside the waiting period after expiration or after a holder's death. A call that looks taken can also turn out to be expired and about to clear. The pending and application tools in ULS and the FCC's call sign pages are more reliable than a forum's list. Because you can list several preferences in one vanity application, a sensible approach is to rank them in the order you actually want them. The system works down your list, so putting your safe fallback first means you never get the call you were really after. Also think about how your call sounds on SSB and CW. Some letter combinations are hard to copy in a pileup, and a longer suffix may be easier to send cleanly than a short one that sounds like another call.
-
Getting from 5 wpm to 20 wpm: what actually moves the needle past the plateaus?
On plateaus: the usual advice is to practice slightly above your comfort speed rather than at it. If you can copy 12 wpm at about 95%, try 15 wpm for short sessions where you will miss a lot. Your brain gets used to hearing characters as whole sounds instead of counting dits and dahs. Then drop back to a speed where you are accurate and see whether it feels easier. If you use Farnsworth, keep the character speed fixed at around 18-20 wpm and shrink the extra spacing over time. Dropping the character speed to make things easier tends to teach you to count elements, and that habit is hard to unlearn. A Koch-style trainer, where you add characters one at a time at a fixed fast character speed, builds on the same idea. For head copy, a gradual change is easier than quitting writing outright. Start by copying only the last word or two of each sentence mentally while you write the rest. Then stop writing common words, then whole phrases. Falling a character or two behind the sender is normal and is actually a sign you are starting to copy by sound rather than by stringing letters together. Don't rely on one kind of material. Random characters train accuracy, but real words and QSO text train the rhythm and chunking you need on the air.