- Audio is excellent. Yaesu really did a neat trick with the 'front firing' speakers, which really are not front firing, but downward firing, but into a resonance chamber below the radio that directs the audio forward. I found the audio was loud, clear and distortion free. Good job there, Yaesu
- The screen is very good - clear, crisp and bright, and well laid out
- The configuration soft menu system appears to follow the FT-710 layout, which I thought was pretty good
- The main VFO knob is too big - it gobbles up too much front panel real estate, space that could have been put to use for other purposes like a dedicated sub-VFO knob
- The whole Field package seemed very sturdy. As many have commented, it's not light - it's very brick-like
04 July 2025
Hot Stuff
02 July 2025
Bust
My lovely wife and I recently returned from a 2,100 mile road trip that took us from Atlanta, GA, to Mammoth Cave, KY, to Benton Harbor, MI, to Oregon, OH to Cincinnati, OH and then home again. The objective was Benton Harbor, to attend her nephew's wedding, but the other stops were for pleasure. For example, we both grew up in Maumee, OH, and wanted to visit relatives and old haunts, so we booked a campsite at Maumee Bay State Park in Oregon, OH (a great park, BTW).
We were moving fast - a day or two here and there - and the objective was to visit people and see interesting things. In that sense we weren't really 'camping', we were just hauling our hotel room around behind our F-350. What also worked against us was the heat. Just as we left Atlanta, a near record setting heat dome settled in over much of the eastern US. Here's the temperature in Benton Harbor, on the shores of Lake Michigan, on June 21st at 2:00 pm:
I took along a compact radio setup knowing operating opportunities would be few and far between. I was right on that part. The only chance I got to set up was at our campground in Benton Harbor. This was a KOA, nicely run and well maintained, but campers were stuffed in cheek-by-jowl. This is a 'feature' of every KOA and private campground we've ever stayed at. The owners want to maximize profit, so spaces are tight. Stuff as many in as you can. This arrangement also highlights another problem with camping - RFI from the power inverters, converters and solar charge controllers built into every camper made in the last 20 years. It's a literal RF soup in these campgrounds, and many bands are simply unusable. Your only real defense is to use a radio that has strong filtering, and maybe bring along a set of bandpass filters.
I was using my Elecraft KX3, and much of the 40 meter band was unusable due to RFI (and the KX3 has strong bandpass filters built in), but I did find segments of 20 meters that were usable. Alas, my antenna setup wasn't good enough. I tried two vertical antennas - the desktop Elecraft AX1 you see in the photo, and a larger Chameleon 17' vertical. Alas, I wasn't able to make any Winlink or JS8 connections. I don't blame the campground RFI for this - it was really an antenna issue.
Which brings me to a major point of this post. I'm a big supporter of the 'AM radio in every car' initiative. Both because I do feel AM radio is important, but also because having to incorporate a working AM receiver into vehicles means car manufacturers will have to take the time to 'clean up' their electrical systems designs to minimize RF noise. This goes double for electric vehicles. Then hopefully there will be a trickle-down effect, where the FCC gets off its ass and does its job and starts forcing manufacturers of things like inverters, switch mode power supplies, solar charge controllers, etc. to clean up their products. Then maybe ham radio operators will be able to set up next to their campers and only have to deal with a light sprinkle of RF noise instead of the flood we deal with now.
W8BYH out
12 June 2025
ARES Southeastern US Situational Awareness Map Updates - 12 June 2025
Before diving in to the discussion about changes, I think I'm going to start using this blog as the notification outlet for the Situational Awareness Map. Normally when I do updates and I need to get word out about key changes, I'm cross-posting between a couple of Facebook and Groups.io sites. It gets clumsy, and I have to keep my comments short to fit the various platform restrictions. Using this blog allows me to be a bit more 'expansive' in my comments and discussions about changes.
Now, on with the show!
Yesterday I pushed out a few key changes to the map that wrap up some content updates and a few minor layout changes. Let's have a look.
Since the 2025 Hurricane Season opened on 01 June. I set the NOAA Active Hurricanes layer to on by default. This means any NOAA-released hurricane & tropical storm information (tracks, probability polygons, etc.) will automatically appear and update as NOAA releases information. This layer will stay on by default all the way through hurricane season
Under the Situational Awareness layer group, I added a Current Wildfires layer. This data is hosted by the Department of the Interior, and provides basic information on current wildfires across the US. This layer is off by default:
Let's spend a moment discussing repeaters. After a few years of hosting Repeaterbook.com info in the map, and getting very little feedback on Georgia repeaters (good or bad) - and zero info on repeater data from other states - I've decided to take a different approach. I've dropped the Repeaterbook.com coverage, and have gone back to an internally managed repeater database for just Georgia. This new data can be found in the Georgia Amateur Radio Repeaters layer. What you see in the map today is a slight update to the old Georgia Repeater Database Initiative information. I can take direct updates to repeater information, and can make quick changes - new repeaters, off-line repeaters, changes in repeater location, etc. I will likely put up an on-line form to capture this info, and link it in the map, but that's still a few weeks off. I'm also using a data clustering display tool, which is why you see a bunch of large dots when you turn the layer on. As you zoom into the map, the repeater data will 'dis-aggregate', and you'll be able to get all the way down to individual repeaters. This layer is turned off by default:
Next up... PSAP boundaries. This one caused a slight stir a few months ago when I put out the word that the Dept. of Homeland Security pulled down the national PSAP (Public Service Answering Point) boundaries layer, and I had to take the layer out of the map. Not that anyone actually used the boundary info, they were just incensed that DHS took it down. Conspiracies, and all that. Folks, it happens all the time with this cooperative mapping platform, not just with national level datasets, but with very innocuous local datasets like local bird sightings, or community-level Girl Scout Cookie sales point layer (yes, someone made a cookie sales point map layer). I do it in my regular job as a GIS program manager at a very busy international airport. Data layers often age-out, security restrictions get imposed, or we just come up with new ways to display the data. So we pull down the old and (usually) put up something new. It's not just me and the DHS doing it - NOAA does it, the Georgia Emergency Management Agency does it, local governments do it, DOT does it, FEMA does it - everyone does it. The real issue is that there's no built-in notification system that lets map authors know a data layer is no longer available. The map just throws an error when you try to open it and a data layer is no longer available. So, back to PSAP data. Yesterday I discovered that the State of Georgia has published its own PSAP data layer, and I've added it into the map. You'll find it under the Borders, Operational Boundaries & Geographic Features - Georgia layer grouping. This layer is turned off by default:
Let's wrap this up. The last thing I want to talk about is finding layers in the map. There are over 50 individual data layers in the map, and the layer structure is complex. It can be tough finding the exact layer you want to take a look at. Heck, even I get lost in the layer stack! That's why I've incorporated a search tool in the Data Layers window, to help you find what you are looking for. It's the little search icon in the upper right corner of the window:
Let's say you are searching for a layer that shows lakes in Georgia. You heard the layer is in the map, but you don't know where. Just open the search tool and enter 'lakes'. The search tool will find the layer group that 'lakes' is nested up under. Simply expand the layer grouping to find the Georgia Lakes & Ponds layer and click the check box to turn it on in the map (it's normally off by default):
That's it for this update. As always, if you have any questions, feedback, or would like some instruction on how to use this map just let me know. There is a feedback button in the map, and it's the best way to get my attention.
W8BYH out
31 May 2025
Making Up My Mind
- Icom IC-705
- Elecraft KX3
- Elecraft KX2
- Yaesu FT-818
30 May 2025
Getting To Know The Motorola Micom
'Getting to know you, getting to know all about you'
Fans of Rogers and Hammerstein's 'The King and I' will remember the song. I first heard it when the impossibly beautiful Deborah Kerr sang it to the King of Siam's kids in the movie version of the musical. OK, Ms. Kerr couldn't sing, or couldn't sing good enough, so the undisputed queen of 1950's & 60's female musical over-dubs, Marni Nixon, turned Ms. Kerr into a musical star. I've been smitten with Deborah Kerr (and Marni Nixon) ever since.
Nothing to do with ham radio, but with a look like that, who cares? |
'Getting To Know You' is a tune I often sing to any new radios or accessories that come across my bench, particularly if the device falls outside of what I describe as normal ham radio operational protocols. That would be just about anything not made by Icom, Kenwood or Yaesu. And so it was with a radio I'd had an interest in for years, but didn't know where to start when looking for one - a Motorola Micom commercial HF transceiver. These were (and still are) in common use in the MARS, CAP and SHARES communities, and unlike their L3/Harris, Barrett or Codan brethren, they were relatively affordable on the used market. Motorola stopped manufacturing the Micom line about 8 years ago, but there's still an active user community, swapping advice, radios and components. Good working examples pop up regularly on eBay. So, in terms of availability and price, they are pretty accessible and have a very good reputation for ruggedness and long service life.
I found mine, a 2E model. on a Groups.io site devoted to commercial and military HF rigs. According to the seller it was in excellent condition and had been used in a test environment at a small radio accessory development company he used to own. The radio came with an external long wire tuner (similar to an Icom AH-4), microphone, power cable, programming software and some documentation. On arrival it was clear that the rig really was in very good condition. The microphone was the only real iffy item - it had been in a lot of hands, and it was a bit 'sticky'. The seller dug a new one out of his box of parts and sent it to me for free.
The biggest issue was a programming cable. Motorola did a lousy job of documenting just how to connect this thing to a computer to get it set up. All the instructions say is, 'connect programming cable'. What programming cable? What does it look like? Where do I connect it? There's a 25 pin accessory connector on the back of the rig and, like the rest of the radio world would, I figured that served as the radio programming port. But no. I found out through the user community that programming takes place through the CAT6 microphone connector. What this means is, there's no CAT-like radio control that lets you do voice ops while managing frequency or settings. There are no original Motorola programming cables to be had, at least none I've been able to locate. There is a guy on eBay selling what he claims is a home made programming cable, but what he sells doesn't work. I was saved by an instruction sheet issued by the Civil Air Patrol back in the early 2000's that showed how make a programming cable using CAT6 cable to a DB9 serial connector.
The Motorola software is old, but pretty good. It allows you to set up the channel frequency memories and settings, and configure the radio for ALE. It was written to run on Windows 2000 or Windows 7, and has a distinctive 32 bit Windows XP look and feel, but runs just fine on Windows 11 in compatibility mode. Earlier this year I got the radio programmed with a swath of Georgia ARES, SHARES and other public service frequencies, played around with it a bit, then got distracted by other rigs. The Micom sat unused for months.
A few weeks ago I came upon a Micom video on the LifeIsTooShortForQRP YouTube channel. The host reviewed a Micom 2E - the same model as mine, except his is the remote head version. Other than that, it's the same radio. He reviews and repairs a LOT of commercial and military HF gear, and had nothing but praise for the Micom. The video renewed my interest in the Micom, and I decided to get it back on the air and spend more time learning its capabilities.
I now see why the Micoms were (and still are) so popular. They are a mil-spec chunk of metal that just works. I have mine connected to an LDG Z-100 tuner so I can use to my MyAntennas end-fed in the back yard. The speaker audio is excellent - designed to 'punch through' in noisy environments, and I get consistently great audio reports whether I'm using the hand mic, or the Motorola handset I found on eBay.
W8BYH out
27 May 2025
Fanboys Report!
It's been just a few weeks since the Yaesu FTX-1 Optima and Field models have started to ship. We've had the usual silly and pointless unboxing videos, and only a few in-the-field-making-contacts videos have come out. But there have been enough of those videos to show:
- the firmware is still buggy
- the field version with just the battery is pretty big and heavy; it ain't no Elecraft KX2
- the radio addresses some of the issues that linger with the very good FT-710, such as waterfall display averaging
- audio quality and volume are both good
- the radio naturally 'sits' at a good viewing angle (something Icom blew with the IC-705)
- something I never thought of, but Yaesu botched the placement of the two BNC connectors - the UHF/VHF connector should be at the top of the stack, making it easy to mount a whip antenna for local repeater work and still connect an HF antenna cable
- like all field radios that have come before it in the Yaesu line, it's about as water resistant as a submarine with screen doors
10 May 2025
The Radio As A Box Of Legos
Think your rig is old? Here's a picture of N6CC's field setup, running Winlink using a 70's-vintage military AN/PRC-174 radio. and a SignaLink as the digital interface |
Is your radio's volume output a bit weak? There are plenty of small, lightweight and cheap battery powered speakers on the market.
Need access to GPS to time sync your FT8 session? Remember, the radio doesn't care a wit about a time sync for FT8, it's the WSJT-X application running on your computer that cares. For less than $20 you can buy a USB GPS receiver to plug into your computer and get highly precise location and timing information. There's free software available that will sync your computer's system clock to the GPS timing signal. This is a far more useful solution than a GPS signal that stays locked up inside of a radio.
Here's a nice looking GPS receiver that gets good reviews and uses the ubiquitous uBlox receiver chip. Cheap and effective |
Just add one of several free GPS monitoring applications to your Windows device, and you'll be getting far more useful GPS info than you could ever hope to from a GPS receiver installed in a modern ham radio.