Preparations for June’s ARRL VHF contest went well. The car’s annual paint maintenance looked great and the concurrent roof rack inspection revealed no apparent issues. Someone asked how long reinstalling the rack takes. So, I shot a video of me installing just the rack and vertical antennas. In that video’s comments, someone asked me to share the process for getting the tower mounted. I shared this video in response. With the tower mounted, mobile desk installed, software updated, and radios tested, it seemed I was ready for some VHF action… or so I thought!
The Setup – I operate as a Limited Rover, a category of mobile station that changes grid squares while working within the 6m, 2m, 1.25m, and 70cm bands. I use a Yaesu FT-891 HF/6m transceiver for all 6m activity; a Yaesu FT-857D “multi-multi” transceiver for 2m, 1.25m (w/transverter), and 70cm; and an Icom ID-5100 for FM work on 2m and 70cm. My primary antenna array includes a 6m Moxon and Yagis for 2m, 1.25m, and 70cm. I also have 6m-70cm vertical antennas to serve as back-ups.
The Drive – June 13-14 was the first time that I had driven away from my home area since before Memorial Day. West-bound traffic on I-64 was more congested than I expected. The slowdown was compounded by construction near New Kent, VA. Stop-and-go traffic delayed arrival at my first operating position in Louisa, VA, 120 miles away from home and near the grid corners of FM07, FM08, FM17, and FM18. I have four spots within a few miles there. See a map in the photo album below.
Early Problems – This was to be the first contest in which I had planned to make effective use of a software defined radio (SDR) receiver. My goal was to visually monitor for signals in the SSB section of the 6m band while working FT8 data stations. Instead, I had a major problem with the audio interface on the FT-857D “multi-multi” transceiver. I use my FT-857D to handle traffic on 2m, 1.25m, and 70cm. I work 6m on the FT-891. Losing three of four bands is devastating for a Limited Rover. This photo shows early testing of the SDR receiver and audio interfaces.
Digging for Gold – I suspected that something had shifted in the trunk and partially unseated a Digirig device. I had to unload the trunk to access the interfaces, which are located under the electronics panel with the spare tire. This photo shows the electronics panel in its “maintenance position.” I didn’t find any obvious problems with the USB hub or connected devices. Next, I focused on searching for COM port conflicts within the computer. My SDR receiver experiment had added some USB complexity that may have been creating conflicts.
Losing Time – Keep in mind that contesting time was withering away while I worked to find the problem. It was very frustrating! Visitors were more inclined to approach and ask about the car since the doors and trunk were open. I was kind to them and made them feel welcome, but at the cost of further delays. The FT-891 was briefly affected, too. UGH, more time! I managed to resolve that after finding a tiny “Reset to Windows Default” text link at the very bottom of the “Manage Sound Devices” window. But that didn’t fix the FT-857D issue shown in this photo. I even removed the SDR receiver and all associated software to remove them as possible culprits.
The Disorder – “Why not just ditch FT8 and work SSB or CW?” Yes, I could have done that, but there were two issues. First, so much VHF contest traffic has moved to FT8 that I probably would have been scanning dull bands while swinging the Yagis. Sure, I might’ve made a few contacts, but what if I could’ve fixed the problem with that time instead? Regardless, the trade-off didn’t offset the second issue: My personality type prevents me from focusing “over there” when I have such a glaring problem “over here.” I couldn’t stand it! 😀
Phantom Menace – To make matters worse, I also lost control of the FT-857’s display panel at some point. I couldn’t select modes or bands. “What NOW” was my immediate thought! An AI search made the problem look grim. Possible faults listed included worn soft-touch buttons (all four at once?), microprocessor failure, software/firmware crash, etc. I started with disconnecting power. No luck. Next, a factory reset without luck.
A “Key” Oversight – Later, I found a random post via web search. It revealed that the exact problem could be created if something was touching the CW key while not in CW mode. I have a key despite not being a CW operator. A key is useful for certain adjustments such amplifier settings and the fine tuning of beam headings… “sending dashes.” My key had shifted and was active. It was not obvious since the radio was not transmitting. The problem vanished as soon as I cleared the key and gave it a new home. It was good to get that one sorted!
Bed is Calling – I decided to pack-up and drive home after four hours of chasing gremlins in 95°F heat. Spending Saturday night at home was already in my plan. Contest-wise, Saturday was almost a total loss. It didn’t have to be, but what I hoped would be a quick fix eroded my time and plans. The long drive home gave me plenty of time to think about different approaches to resolving the issue. I was tired enough to actually stop for a dinner break! While there, I managed to make a few 6m contacts on FT8. No voice activity, though. I arrived home around 10:30pm and was in bed by 11.
Cock-a-doodle-doo! I was up at 6am Sunday morning for a one-hour drive to my next operating position. Before starting, I connected my wife’s laptop to see if a fresh computer worked when mine did not. No luck! Clearly, something was amiss in the car and not with my computer. I suspected a faulty Digirig interface. My station wasn’t fully capable, but at least I could function with the knowledge that troubleshooting efforts were at a standstill for the time-being.
Refocused – For Sunday, I committed to four grids closer to home, FT8 on 6m, and SSB on the other bands if able. I drove to First Landing State Park in Virginia Beach near the grid corners of FM16, FM17, FM26, and FM27 (FM27 shown here; see map below). I ran FT8 on 6m and checked 2m for activity. I had a few regulars who ran the bands with me. I replicated this process as I moved to the other grids. I’d share more details about my operations, but it was fairly standard business: FT8 on 6m only? Yawn! Working 2m, 1.25m, and 70cm SSB was satisfying. However, the runs were short-lived since I had only three points of contact there. CQ calls on 2m were not productive.
Quick Finish – I finished the contest around sunset as thunderstorms began to arrive on the Colonial National Historical Parkway. While lightning doesn’t particularly bother me, rain presents a somewhat unique problem on the Parkway. Commercial traffic is forbidden; so, tree limbs hang a little lower than on major roads. It’s not a problem during winter months and is manageable on dry summer days. However, rainwater weighs leafy tree limbs and causes them to sag even lower. That creates a huge risk of tree limb strikes with the tower, especially at night when branches are more difficult to see. On top of that, rain and wind storms often topple old trees or cause limbs to fall across the roadway. NO THANKS! I leave when storms come.
Final Score – In the end, I made 81 contacts, worked all four of the Limited Rover bands, operated in five grids (target was seven), and worked stations in 27 grids. I really think this could have been my strongest contest yet if I didn’t have digital challenges! Six meters was open, a strong reason why I should have abandoned troubleshooting and just worked what I had. I suspect there was activity on the other bands, too. Still, I don’t guess I did too bad when considering my limitations. Experienced rovers have told me that each contest brings a challenge: They don’t always go as planned. Apparently, troubleshooting is a common pastime for rovers! 😉
Post-Mortem – What was the problem? Monday brought cooler temperatures and resources at home. I mentioned trying my wife’s computer. Next, I connected my computer directly to the FT-857D’s Digirig. It worked, which indicated a bad USB hub. But why was only the sound on one radio affected? I didn’t suspect the hub because I still had rig control of the FT-857D. I moved the FT-857D to a different port on the USB hub. The problem was resolved after a few sound device settings within WSJT-X. If only I had tried that in Louisa! 🙁 I’m not a “computer guy” despite knowing a little more than the average user (I think). So, that did not occur to me in the heat of the moment. Live and learn!
Upgrade to Come – Oddly enough, my GPS device and ID-5100 programming cable both work fine in that port. It’s marked with an “X” in this photo. I’m still going to replace the hub. I’m looking at hubs that are compatible with an unused Thunderbolt port. I’m new to Thunderbolt technology… yes, my other computers are old! Anyway, Thunderbolt ports have such good throughput that there should be almost no chance of data bottlenecks… should… almost. I always remember the saying, “To err is human. To really mess up requires a computer.” I guess I’m going to test that theory!
Lessons Learned – Here’s what I hope to remember next time:
- Retest all interfaces before driving 120 miles to the starting point. That might have saved $50 in fuel on top of the time lost!
- Keep a backup computer and hub handy. I’ll take my wife’s next time; she’ll love it! 😀
- Don’t let one problem derail the whole operation. Yeah, right! OCD > Self-Control
Looking Ahead – My next VHF contest isn’t until September. I have plenty of time to prepare, though I don’t expect the bands to be as strong as they are in June. My next outings with the rover will be a hamfest in Manassas, VA this weekend (short notice for you), then hamfests in Newport News and Berryville in August. I hope you see you there!
Never As Planned,
Scott
