Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 384.8 km/s
Aurora 1
Updated 13:30 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Admin_Lee

Administrators
  • Joined

  • Last visited

Everything posted by Admin_Lee

  1. For net control, the biggest improvement usually comes from a script. Have your opening, check-in call, break procedure, and closing written down so you can read from them. That is especially helpful when the band is noisy, since a predictable format helps stations copy you through the static. Calling check-ins by category or region can also reduce the pile-up. For SKYWARN and ARES, make sure everyone knows the difference between a routine net and an activation. In a routine session, there is room for questions and practice. During an activation, stations should expect short, formal exchanges and should call only if they have a report or are assigned a task. If your group has a written net procedure, share it with new members before they join their first session, not after they have gotten it wrong on the air.
  2. Adding a few notes on club and special event calls, since those get mixed up. A club call is a normal license issued to the club, with a licensed trustee responsible for it. The trustee is the point of contact with the FCC, so the club should have a plan for what happens when the trustee moves or becomes a silent key. If it's not updated, the license can end up stuck with an unreachable trustee. The club call is also separate from the members' own calls: members still identify with the club call when operating as the club, and they follow the same control operator rules as anyone else. Special event 1x1 calls are a separate system, and they are not what you get from a vanity filing. They are meant for a specific event and a short period. Operators on the air under the special call still need to be licensed, and the special call does not replace the licensing or privileges of the individual operator. If you are planning something like an anniversary or a county celebration, start by checking the program rules for current eligibility, the application timeline, and how the coordinator wants requests submitted, rather than assuming it works like an ordinary callsign change. One more tip on lookups: when someone says 'this call is available,' check ULS directly. Callbook sites are convenient, but they are secondary sources, and the FCC record is the one that counts.
  3. A scheduling habit that keeps things manageable is separating confirmation tasks by speed. LoTW, Club Log and QRZ uploads can all happen from the same ADIF export in one sitting. Paper is the slow queue, so don't let it clog the fast one. Log the QSO, export, sign and upload, then sync to whichever other services you use. Only after that do you decide which contacts deserve a physical card. One caution on matching: if you run FT8 or other digital modes, make sure your logging program exports the mode and submode in a form TQSL maps correctly. A mismatch between the two stations' mode labels is a common reason a contact stays unconfirmed even though both sides uploaded. Check the mode group mapping if a confirmation you expected never shows up. Also, keep your station location in TQSL accurate if you operate portable or from another grid. The location needs to match where the contact actually took place, not where your home station sits.
  4. For anyone asking what to buy first, I'd work backward from what you actually want to do. A handheld makes sense if your local scene is repeaters and simplex. If you want HF, a handheld won't get you there, and you'll need to think about a transceiver and an antenna together. The antenna matters more than most new hams expect. A decent antenna on a modest radio usually beats a fancy radio on a poor antenna. For a handheld, a better whip or a magnetic-mount antenna on a car roof can make a big difference. For HF, a simple resonant wire dipole is a classic starting point because you can build and adjust it cheaply, if you have the space to hang it. Mistakes to avoid: don't skip the manual, and don't program your radio from memory. Look up your local repeater's output frequency, offset direction, and CTCSS tone (sometimes called PL). If you hear the repeater but nobody hears you, the tone or offset is the usual suspect. Also, don't transmit into a poor antenna match. Check SWR at low power first, especially on HF. And buy a decent coax and a few connectors that match your gear, because adapters add loss and failure points.
  5. I'd put the antenna and the ground first and the radio second. A well-installed antenna on a roof center with low-loss coax will do more for your range than the extra features on any of those three radios. A good radio on a bad antenna just gives you a nicer screen to look at while nobody hears you. On the radio choice, I'd base it on what repeaters and nets you actually plan to use. If everything near you is analog FM with a bit of APRS, the TM-D710G is a reasonable fit. If you have a lively D-STAR or Fusion group nearby, buy for that mode. Digital voice only works when other people are on it too. One wiring tip: when you test, measure the voltage at the radio while transmitting, not just with the engine idling and the radio in receive. A voltage drop under load will tell you whether the wire, a connection or the ground is the weak link.
  6. On the 44 QSO target, plan for it from the start. If you only need 10 for POTA, it's tempting to stop as soon as you hit that, but a dual activation needs a longer session. Work out how much time you have and how many contacts per hour you can realistically make on your band and mode. If propagation or crowds look uncertain, a second band or a switch between SSB and CW can add contacts that a single frequency won't. For spotting, make sure the spot names the right reference for the right program. A POTA spot carries the park ID, and a WWFF spot carries the KFF number. Some hunters only watch one program's spots, so in your CQ and on the air say both references clearly, for example "CQ POTA and WWFF" followed by the callsign. Hunters who only chase one program will still know they can call you, and those chasing both will know to log you twice. Remember that a dual-spotted activation can bring a pile-up. Keep your exchange short and use a consistent rhythm. Log as you go rather than saving it for later, because the 44-contact count and the separate uploads are much easier to verify from clean, timestamped records.
  7. One thing that is easy to overlook is the receive side on the low bands. People spend a lot of money on a TX antenna and then try to work a weak Bouvet-type signal on a noisy main antenna. If you can only improve one thing for 160 m or 80 m, a quiet, directional RX antenna usually does more than extra power. It also lets you hear who the DX is actually answering, which tells you how the pileup is being worked. For planning, I would split the effort into two parts: the target entity and the band-mode slot. Check which bands you need and rank them by how reachable they are from your location. A low-band slot may only be possible for a short window around the gray line, so being at the radio at that moment matters more than being there all day. Prediction tools are a guide rather than a guarantee, but they help you decide when to sit on the radio and when to sleep. On etiquette, I would stress the quiet part: if you cannot hear the DX at all, do not call on a guess. Listening for a few minutes costs nothing, and the people who are copying him will not be helped by one more blind call. Use the cluster to find him, confirm by ear, then decide.
  8. Staged testing is usually the better habit, even when the kit manual doesn't require it. With a crystal oscillator or Si5351-based VFO, you can confirm frequency, amplitude and stability before anything else is connected. A counter is ideal, but a general coverage receiver tuned to the signal works too, and so does a scope. If the oscillator is wrong, nothing downstream will make sense. For the transmit side, a current-limited bench supply is very cheap protection. If you don't have one, put a small resistor or a suitably rated fuse in series with the supply for the first power-up. A final transistor drawing far more current than the schematic suggests often means parasitic oscillation, bias trouble or a wrong part value. It is much better to see that on a meter than to smell it. Always do the first transmit tests into a dummy load, never an antenna. Measure output with an RF probe or a scope across the load, and use P = Vrms²/R to estimate power. For a sine wave, Vrms is the peak voltage divided by 1.414, or the peak-to-peak voltage divided by 2.83. Treat the result as an estimate, since probe and scope error add up at RF. For BITX-family boards, alignment can be a long process. Calibrating the Si5351 on a uBITX-style rig, checking the BFO or carrier placement against the crystal filter passband, and setting drive levels to the PA all interact. The order you do them in matters, so follow the documentation for your particular board revision.
  9. On the J-pole point, the common-mode issue explains a lot of the "it works fine until I touch the coax" complaints. If moving or touching the feedline changes the SWR or the reading, the shield is likely part of the antenna. A choke at the feedpoint and keeping the coax leaving at a right angle away from the antenna usually helps. Because there is no ground plane, mounting height and distance from metal masts also shape the pattern, so a plastic or fiberglass standoff above the mast is worth it. For the connector question, I'd use N-type for anything exposed to weather and UHF. If you stay with PL-259s, a wrap of self-amalgamating tape plus a layer of vinyl tape keeps water out. Water in coax is a more common cause of slowly rising loss than any single bad antenna. When testing a new setup, compare SWR with a short jumper and with the full run. If the full run looks much better than the short jumper, that points to a lossy cable masking a mismatch.
  10. Adding the non-F-layer modes, since they break the 'check SFI first' habit. Sporadic E can open 6 m or 10 m when the solar indices say nothing useful, because it comes from patchy ionization at about E-layer height. For those openings, spot networks, beacons in the 50 MHz and 28 MHz segments, and cluster alerts are much more practical than any solar forecast. Short-skip openings on 10 m during the sporadic E season can also be mistaken for F-layer conditions, so note the distance. Consistent hops of roughly 1,000 to 2,000 km point to Es. For tropo, the useful data is weather: surface pressure charts, temperature inversions, and over-water paths. Ducting tends to stay stable for hours, so a signal that is steady and unusually strong from a station far beyond the normal range is a good clue. A signal that flutters or fades fast on HF during a geomagnetic disturbance is a different story and points toward the auroral or disturbed-path side. For NVIS, the question to ask is whether your frequency is under the foF2 for the hour. When the band starts skipping over nearby stations at dusk, the usual remedy is to move down a band. It's also the reason many regional nets use two frequencies, one for day and one for night, instead of a single fixed one.
  11. On the shopping-list question, a list is worth having, mostly because it keeps you from buying a pile of cables and "projects" that never get finished. Write down the one or two things you actually need, such as a mast section, a power supply, or a specific connector type, and set a rough price ceiling. Then leave some budget for something unexpected. For testing gear in the lot, a few small items go a long way. An SWR/power meter and a dummy load can tell you quickly whether a transmitter produces output into a known load, assuming the seller is comfortable with that. A cheap coax tester helps with cables and adapters. For anything with a battery, look for corrosion first, because it often means the gear sat for a long time. Be careful with older tube equipment and anything with high-voltage supplies. If you don't know how to inspect it safely, it's better to ask someone more experienced than to power it up on a folding table. And if a price seems too good, ask politely what's wrong with it. Most sellers will tell you.
  12. The rigctld approach is worth stressing, because it avoids the most annoying shack problem, which is several programs wanting the same serial port. Let the Pi own the radio connection and have everything else be a network client. A small display or band-decoder microcontroller can poll the frequency with a basic TCP request instead of speaking CAT itself, which also removes level-shifting and the RF-on-serial-line issue from that device. For the band decoder, a Pi reading frequency and then driving an antenna switch over a few opto-isolated GPIO lines or a relay board is reasonable. Isolation does help if the switch is near the transmit antenna feedline. Just make sure the relay board's supply is sensible, because cheap boards sometimes have drivers that behave oddly at 3.3 V logic. For the Direwolf side, watch audio levels first. Direwolf reports the audio level it sees, and an overdriven input hurts decoding as much as a weak one. For a tracker you'd pick a different path: a Pico or ESP32 with a GPS and an AFSK modulator or a dedicated module, with a low-pass filter on the output and firmware that obeys local beaconing etiquette and rate limits. Running a full Pi plus Direwolf in a battery-powered tracker is possible, but power draw and boot time usually argue for a microcontroller unless you need receive decoding too.
  13. Good overview. I'd add that how you plan to use the radio should drive the choice more than the spec sheet does. If you mainly want local 2 m and 70 cm repeaters, a simple analog radio like the FT-65R covers most of that, and it is easier to program from the front panel or CHIRP. D-STAR features like the ID-52A's only pay off if there is D-STAR activity within reach, or a hotspot you are willing to set up. On DMR, the learning curve is mostly about the codeplug, not the radio. Color code, time slot and talkgroup all have to match the repeater or the radio will sit silent or key up without being heard. Get the repeater's published settings before you buy. One more thing: after loading CHIRP data, test each memory against a real repeater or a second radio. A typo in a tone or offset is easy to miss on a long list.
  14. On safety, treat the radio part as optional and the mountain part as the real mission. Some practical points: Set a turnaround time before you leave and stick to it, whether or not you've made your four QSOs. Tell someone your route, the summit reference and when you expect to be back.Look at the forecast for the summit, not the trailhead. Wind, temperature drop and storm timing matter far more than propagation.Don't operate with an antenna up if thunderstorms are anywhere near. A pole and wire make a poor choice of lightning rod, so pack up and descend early.Carry warm layers, water, food, a headlamp and a basic first aid kit, even for a short hike. Radio gear is usually the lightest part of the pack. The rest is what keeps you safe.On the chaser side of your question, the same activity is worth knowing about. Chasers work activators from home, upload their own logs, and earn their own points toward awards like Shack Sloth. Summit-to-summit contacts between two activators count for both, which is a nice bonus when you're on the hill. Also, keep your first kit simple. A tested linked dipole or end-fed on a pole, and a rig you already know, beats a cleverer setup you've never deployed in the wind.
  15. On check-in etiquette, the biggest improvement is listening before you transmit. Work out whether the net is in a roll-call phase, taking short-time check-ins, or handling traffic. When net control asks for check-ins, give your call sign once, clearly, using standard phonetics. Add your name and location only if the net's format asks for it. Don't stack extra remarks on top of the check-in. If net control wants more, they'll ask. A few other habits make the net run better. Don't call over someone else, and if you have emergency or priority traffic, say so using the net's procedure. Most formal nets take that first. If you're a late arrival, use the late-check-in procedure rather than interrupting a handoff. If you're asked to act as relief net control, a simple written list of check-ins, in order and with notes, saves a lot of trouble. And if your signal is weak, a relay from another station is often a cleaner solution than repeating your call for ten minutes. For traffic nets in particular, learn the radiogram layout (number, precedence, station of origin, check, place of origin, filing time/date, addressee, text, signature) before you volunteer to take a message. Copy it in order, read it back for accuracy, and don't improvise punctuation or wording. Accuracy matters more than speed.
  16. On plateaus, the common pattern is that progress stalls somewhere around 10 to 13 wpm and again in the high teens. These stalls usually aren't a limit on how fast you can hear. They're a change in how you process. At the first one you're still assembling characters, and you have to shift to hearing whole words and common letter groups such as THE, AND, ING and CQ. At the second, you have to stop writing each letter as it arrives, because pencil speed becomes the bottleneck. Two things tend to help. One is to drill slightly above your comfortable speed in short bursts. Copy at 80 to 90 percent, then run a few minutes at a speed where you catch only fragments, then drop back. The comfortable speed usually creeps up afterward. The other is to change the material when speed stops moving. If you've been on random groups, switch to real words or callsigns. A plateau on one kind of material often disappears on another because the skill being trained is different. For head copy, a simple ladder is to write everything, then write only callsigns and numbers, then write nothing for a short exchange and jot down only what you need to answer. When you miss a character, let it go. Dwelling on it costs you the next two or three. In the early weeks of head copy you'll feel like you're getting less than when you wrote everything down, and that's normal. For drills, callsigns are worth separate practice because they have no context to help you guess. Use a trainer that generates realistic callsigns, with prefixes, numbers and suffixes mixed, and keep the speed at or just above your target on-air speed. Word drills build the rhythm recognition that makes ordinary conversation easier. They do different jobs, so alternate them.
  17. On security, I'd treat the radio and its LAN interface like an IoT device that was never meant to face the internet. Put it on its own VLAN or at least its own subnet, keep the firmware current, and reach it through a VPN endpoint rather than forwarding UDP ports. WireGuard is lightweight and holds up well on mobile and hotel connections. Overlay-network tools that avoid port forwarding also help if you're behind CGNAT, where you can't forward anything anyway. If you must publish a web interface (a RigPi front end, for example), put it behind a reverse proxy with TLS, strong unique credentials and rate limiting. Never expose rigctld or a raw serial-over-IP bridge. Anyone who reaches that port can change frequency or key the transmitter. The other half of security is the physical station. A remote site needs a way to power-cycle gear (a network-switchable PDU on a separate path from the radio's own link), a watchdog that drops PTT if the session ends, and ideally some indication of SWR, temperature and antenna switch state. If an amplifier is involved, think hard about what happens if the tuner or antenna relay is in the wrong position when you connect. On the latency question, SmartLink and RS-BA1 are designed for audio streaming, so they behave better than a generic remote desktop plus a virtual audio cable. But anything that passes the panadapter or waterfall will use much more bandwidth than the audio alone. Lower the display rate if your link is marginal.
  18. I'd add something about the non-ham side of the household. If the plan only works when the licensed person is home and has a radio in hand, it isn't a family plan. FRS handhelds are simple enough for kids and relatives, but keep range expectations realistic. Buildings, hills, and trees cut distance much more than the packaging suggests. GMRS can be a step up with higher power and repeater access, but it requires a license in the US, so check the current FCC rules instead of relying on old forum posts. MURS is worth a look if you want license-free VHF with its five channels, though it's limited to low power and you'll see less gear for it. Whatever you choose, write down the channel and any privacy code settings on a card in the kit, since many handhelds lose their programming or get set wrong by accident. For weather radios, pick one that does SAME alerts for your county and can run on batteries, then test it so you know what a real alert sounds like. And agree on one out-of-area contact before anything happens. It's an easy step and it's the one most families skip.
  19. On the study and calculation side, HamStudy is built around question pools, so the useful habit is to check which pool and which exam element you're studying, since pools are replaced on a schedule. It also helps to read the explanation for questions you miss rather than only memorizing answers. That matters most for things like Ohm's law and power calculations, where a calculator tool like HamCalc or a plain spreadsheet can help you check the math, but you still need to know which formula applies. For grid squares, a Maidenhead locator is a sequence like two letters, two digits, then two more letters. The more characters you give, the smaller the area. Four characters is fine for casual contest exchanges and rough maps, but six is better when you want a more precise location. Map tools that convert between latitude and longitude and grid locators are handy before a portable activation, especially when logging software wants a grid for an exchange. For propagation, I'd treat solar and geomagnetic indices as context, not a verdict. A high solar flux value generally favors the higher HF bands, and a disturbed geomagnetic field, shown by a high K-index, can degrade high-latitude paths. But your actual band conditions depend on time of day, season, antenna and the other end of the path. The cross-check is simple: look at the forecast, then look at live evidence on PSK Reporter or RBN for the band you care about. If the live map disagrees with the forecast, trust the map. For phone apps, pick one for spots and alerts, one for repeaters, and one for logging, rather than trying to find a single app that does everything. When you're on a summit or in a park with limited signal, an app that works offline or caches data is worth more than one with every feature.
  20. One thing that helps on both CW and phone is to treat the pileup as a pattern to decode rather than a crowd to shout over. If the DX is listening up 2 to 5 and picking stations from a narrow part of that range, then calling 3 kHz above that range is just noise. If they are tuning slowly upward, it can pay to move into the area they are about to reach instead of staying where they have already been. If they are consistently answering callers at the lower end, calling on a clean frequency just above them may be better than fighting over the same few hundred hertz. It is also worth being cautious with repeated calling. A common pattern is to send your call a couple of times, listen for a response, and then stop for a few cycles. Continuous calling prevents you from hearing whether the DX is already coming back to you or to someone else. On 160 m and 80 m this matters even more, because a weak DX signal can fade in and out, and you may only hear the operator in short bursts. Listen first, call briefly, and then listen again. For FT8 operations, the DXpedition often uses Fox and Hound mode. The rules there are different, and the instructions are normally published by the team in advance. Follow those instructions exactly and do not treat the mode like normal FT8. That one is more of a software and procedure issue than a technique issue.
  21. I'll start with the paperwork, since that's the part that trips people up. An FRN (FCC Registration Number) is a 10-digit ID you get by registering in the FCC's CORES system. It's free. Register with the same legal name that appears on your photo ID, because the VE team will check that the two match. Get the FRN before exam day and bring it with you. Teams generally need it to file your application, and fixing a missing one on the spot is a hassle. Keep your CORES password somewhere safe too. You'll need it later to update your address or manage the license. The VEs are Volunteer Examiners. They are licensed hams accredited through a Volunteer Examiner Coordinator (VEC), such as the ARRL VEC, Laurel VEC or W5YI VEC. They run the sessions, grade the exam and submit your results. Search for a session on the ARRL's exam-session finder, or check the listings from the other VECs. Local clubs often host sessions and sometimes post them on their own sites. Many teams also run remote sessions over video, so it's worth checking whether that's offered near you. Many sessions list a contact person, and it's worth emailing them. Some require pre-registration, and some are walk-in. On cost, the fee is set by the VE team and the coordinator, so it varies. Check the session listing, and also ask what payment they accept (cash, check, or something else). I won't quote a number, because it can change. As for the FCC's own fees, rules have changed over the years, so confirm on the FCC website rather than trusting a forum post, mine included. On exam day, bring a photo ID, your FRN, a pen or pencil, and a simple calculator if you want one. Ask the team ahead of time what their calculator rules are. The Technician exam (Element 2) has 35 questions, and you need 26 correct to pass.
  22. One thing I'd add for the after-action side: record observations during the drill, not afterward. Assign someone as an observer or evaluator who is not also running a station. Have them note times, such as when a message was originated, when it was received, and when delivery was confirmed. Those timestamps turn a vague "it felt slow" into a finding you can act on, like "the delay was between the shelter and net control, not on the relay leg." For longer scenarios like a grid-failure drill, include things that are easy to forget on a short exercise: a shift change with a written handoff, a fuel or battery check-in, a point where a key operator is declared unavailable, and a station that must be replaced mid-net. Those are the points where real operations tend to break down, and they rarely come up in a two-hour event. For scenario variety, rotate the stressors rather than inventing a new disaster every time. One year the repeater is down and you go to simplex. Another year the net control station has to relocate. Another, traffic volume is higher than your operators can handle and you must apply precedence and say no to low-priority messages. Keeping a short list of "injects" you can pull from also makes it easier for volunteers to run the exercise without a large planning team.
  23. Most Q codes are three-letter signals that mean one thing as a statement and something related as a question. Add a question mark and QRL? asks "is this frequency in use?", while QRL on its own says "this frequency is busy." That's why CW operators send QRL? before calling CQ on a frequency that sounds empty. If someone answers, the frequency is taken, so move on. The ones on your list: QRM is interference from other stations, meaning man-made signals on or near your frequency. QRN is natural noise, mainly static from thunderstorms. A simple way to keep them apart: QRM is people, QRN is nature. QRP means low power and QRO means high power. QRP isn't legally defined, but operators generally treat 5 watts on CW or 10 watts PEP on SSB as the upper limit. QRO has no fixed number and just means running more power than usual. QRT means "I'm stopping transmission", which in practice usually means signing off for the day. QRZ? means "who is calling me?" It's what a station sends when several people answered and it couldn't make out any callsign. QSL means "I acknowledge receipt", and it's also the name for the confirmation card or electronic confirmation of a contact. QSO is simply a two-way contact. QSY means change frequency. QTH is your location. QSB is signal fading, the in-and-out strength you hear on HF. You didn't list them, but QRS (send slower), QRQ (send faster), QRX (stand by) and QRV (I'm ready) turn up often too. One note on QSL: if someone asks "QSL?" they're asking whether you received the message. Saying "QSL" after a callsign or exchange means you copied it. The card or LoTW confirmation is the same word used for the written record.
  24. On trap vs. fan, the practical difference is usually space and the number of supports. A fan dipole can need a spreader at each element and enough room to keep the wires apart. A trap dipole is one line of wire, so it hangs from the same two points as a single-band dipole. The cost is bandwidth and efficiency. Each trap carries some loss, and on the lower band the antenna is electrically shortened, so the lower band tends to be narrower. Fan dipoles keep the full-length wire for the low band, which generally gives better bandwidth there. For the model, a trap in EZNEC or MMANA can be represented with a parallel R-L-C load. The trap inductor's Q sets the loss, so enter a realistic Q or the model will look better than the real antenna. Build the antenna, then measure and trim each band in order, starting with the highest band, since the outer sections only matter on the lower bands. For elevated verticals, the number of radials depends on how they are used. Two to four tuned radials for a quarter-wave with a good rise above ground gives a usable match and solid performance. Radials raised several feet above ground do not need the huge counts that buried or ground-laid radials need. Slope them downward from the feedpoint to raise the feedpoint impedance toward 50 ohms, and model it with the ground type you actually have. If the radial tips are within reach of people or animals, insulate or mark the ends, since the voltage at the tips can be high.
  25. Pick the radio by what your local repeaters and nets actually use. Digital features only matter if people near you are on that system. If your area is mostly analog FM, any of the three will work fine, and ergonomics should decide it. Try to get your hands on each one, or at least study the manuals online. In a moving vehicle you want the volume, squelch, band/VFO and memory controls to be easy to find without looking. Touchscreens look nice, but physical knobs and buttons are generally easier to use while your eyes are on the road. On power wiring, follow the manual for your radio and the fuse values it specifies. A 50 W class mobile can draw a double-digit amount of current on high power, so a thin wire or a poor crimp will drop voltage and can overheat. Run the positive lead to the battery with the fuse holder as close to the battery terminal as practical, because the fuse protects the wire along its whole run. If the radio has separate positive and negative leads with fuses, keep the supplied fuses in place. Use grommets wherever the cable passes through sheet metal. Don't rely on the cigarette lighter socket, since those circuits are shared with other loads and often have inadequate wiring for sustained transmit current. Ground the negative lead to the battery negative or to a proper chassis ground point recommended for your vehicle. Some modern vehicles have battery monitoring systems on the negative terminal, so check the service information before connecting there. Keep the lead short and tidy, and make sure crimped connectors are properly crimped and not just squeezed. For cross-band repeat, check the manual for each model rather than assuming. Not every dual-band mobile offers it, and the setup details differ. If you do use it, remember that the usual licensing and identification obligations still apply, and the licensed control operator needs to be able to monitor and shut it down. It's often used to extend a handheld's reach from a vehicle with a better antenna, but test it on a quiet simplex pair first so you don't interfere with an active repeater.

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.