Good afternoon. KJ7T is in the booth! This is Tom Salzer with some Random Wire Reflections for Issue 97 of the Random Wire Review that will publish on Friday, July 5th.
And I have to laugh a bit when I saw I'm in the booth, because the reality is I'm at my messy sit-stand workstation at home, early in the morning when it is quiet, and just pretending that I have a recording booth!
I actually recorded this podcast inside the passenger compartment of my Honda Ridgeline truck while waiting for my daughter’s prescription to be filled. I captured audio on my Zoom H4N Pro Handy Recorder with a “dead cat” filter over the sensitive microphones. The audio was later imported into Audacity for final editing. I exported the audio in mono to save space, making this podcast a bit more friendly for folks using cellular bandwidth to listen.
Tom Salzer KJ7T
Overview
OK, let's take a dive into Random Wire Review issue 97.
Topics in issue 97 include:
Independence Day;
a new (to me) Dakota Lithium battery;
the Digirig Mobile and Digirig Lite devices; and
a terminal node controller by MFJ.
I also offer some reflections on encryption of radio traffic and on APRS. The closing notes include a short bit about cloning my hotspot microSD card, a sound clip from an AllStarLink net, and a few photos from the Hillsboro Hops baseball game.
If you are interested in AllStarLink, you’ll want to stay tuned to the very end where late-breaking news is shared about a major version upgrade for AllStarLink!
Independence Day Edition
Since issue 97 will publish on July 5th, I'm calling it the Independence Day Edition.
On July 4th, my wife and I will attend a baseball game that pits the Hillsboro Hops against the Eugene Emeralds. We'll try to eat a few hot dogs, have a beer, and watch the fireworks show that will be featured at this game. Usually we get together with family, but having a night out for the two of us seems like a great way to celebrate Independence Day this year.
In issue 97, I refer readers to a Reddit thread about the First Amendment and ham radio. Reading through those comments helped me appreciate the many privileges we enjoy as licensed amateur radio operators even more.
New Lithium Iron Phosphate Battery
I succumbed to a deal on Facebook for a 12-volt, ten amp-hour battery from Dakota Lithium, for $69. That’s a nice price for a portable battery.
This little guy is a bit larger than my off-brand 12.8V 6 amp-hour battery by TalentCell. I'm surprised the Dakota battery doesn't weigh much more than the TalentCell battery.
I tested the battery by clipping the power leads from my Ten-Tec Scout 555 to the spade lugs on the Dakota battery. It worked great and I can tell this is going to be a mainstay in my ham radio kit.
Digirig Mobile and Digirig Lite devices
I have a Digirig Mobile device that I bought because I couldn't get an MFJ TNC some time ago. The Digirig device works great. It's about the size of a large thimble, as in the protective device you put on your thumb when sewing.
Actually, the Digirig kind of blows my mind. Essentially, it's an external sound card that is just tiny.
The catalyst for me to look again at the Digirig products was an issue of Steve Stroh's great newsletter titled Zero Retries. Steve included a bit about the new Digirig Lite device that incorporates some of the needed cabling into the device.
I love a tiny and complete solution so the Digirig Lite is on my "must acquire" list.
If you like content that is interesting and future focused, produced by an experienced and capable ham, I recommend Steve's newsletter to you. A subscription button is included in issue 97 of the Random Wire.
A New TNC Arrived in the Shack
And speaking of terminal node controllers, Steve's mention of the Digirig Lite caused me to remember why I bought the Digirig Mobile, so I went looking for an MFJ 1270X TNC again. Most vendors I checked list this device as out of stock, but Ham Radio Outlet had some in Sacramento.
I very swiftly logged into my HRO account and ordered up another 1270X. It arrived a few days later. I include unboxing photos in issue 97.
Encryption of Radio Traffic
I overheard an interesting conversation from an east coast reflector while on a morning drive for the coffee that fuels the start of my day. Somehow, those hams got onto the topic of encryption of radio traffic by city, county, and state agencies.
I reflect a bit on this in issue 97. I'm of two minds. Normally I would prefer radio be open to all. But I've been in the public safety arena and I understand the need to protect people, families, businesses, and public officials. If encryption makes public safety officials safer and better able to do their jobs, then I support it.
How Do You Do APRS?
I actually did laugh out loud when this title popped into my head because it echoes a line in the 1980s movie The Last Starfighter. In that scene, an alien astronaut is meeting the hero's friends and family on Earth, and when one of the people asks him "How do you do?" he responds with: "I do WELL! How do YOU do?" That's the intonation I hear in my mind when I read How do YOU Do APRS?
I run APRS in my mobile rig: a Yaesu FTM-300DR on VFO B. I also have APRS enabled on my desktop AllStarLink node and on my Yaesu System Fusion hotspot. These latter two devices simply report the position of the devices. They aren't digipeating or igating APRS traffic.
I'd love to know how you use APRS, and if you don't, why not? The technology has been around for a while but I consider that a strength because it means there are a significant number of APRS digipeaters around the world.
I've been kinda sorta thinking of adding a digi on my home network, and that means either getting a pre-built device like the WX3in1 Plus or building a fill-in digipeater. There are links to some interesting digi projects in issue 97.
Notes
I did clone my hotspot microSD card as I suggested I should a few weeks ago. The clone is currently in the hotspot and running fine. The original card is labeled and in my workstation drawer. The image file that I can use to burn more microSD cards is stored on my file server. That's about as backed up on this system as I need to be.
Something I'd like to do in Random Wire Review issues is include a sound clip of a particular operating mode. In issue 97, I link to a seven-minute clip of an AllStarLink net that let's you hear the wide range of audio quality among the participants. Audio ranges from smooth and clear to completely broken.
One of my goals is to help subscribers who have not used some of these modes experience the kind of audio you might hear.
I think I'll throw in a few photos from the Hillsboro Hops game, just for fun. Getting away from radio for a few hours can be a refreshing change that helps provide a bit more perspective when you come back to it later.
LATE BREAKING NEWS
Hours after Random Wire 96 was published last week, AllStarLink announced the availability of ASL 3. This is presented as a Beta release. If you take a look at the online manual, this is a big step forward for ASL:
Supported Hardware & Software
Any x86_64/amd64 hardware device
Any emulated x86_64/amd64 virtual machine
Any arm64-based device such as Raspberry Pi
Any emulated arm64 virtual machine
Debian 12
I welcome this big version change but I think it should come with a caution. Many of us will want to upgrade to the latest and greatest version which is now ASL 3 Beta. If your node is running fine, I suggest waiting a bit to see if undiscovered bugs or problems come to light, especially if your node is publicly accessible.
Despite my sense of caution, I must say well done to the AllStarLink folks. I feel like my financial support of AllStarLink is helping to make a difference. AllStarLink is a 501(c)(3) nonprofit organization so your donations may be tax deductible.
I’m sure I’ll give it a try soon. My cloud node is definitely a public-facing system so I’ll capture multiple backups of the working node before I go down this path. Step one, though, is to read the user manual!
With that, I'll say thank you for taking the time to listen and to comment. 73 to all. This is KJ7T and I'm clear.
NOTE 1: I’m sitting in my local Honda dealer’s showroom, editing this issue of the Random Wire while my vehicle is being serviced. Many years ago (nearly 50, actually) I sold cars for a Ford dealership. What an eye-opening experience that was for a young, naive fellow! In some ways, showrooms haven’t changed. Salespeople still lurk where they can see the doors and people driving onto the car lot. But in other ways, the showroom is a much more relaxed place with more customer seating and even places to work…almost like being in a hotel. This waiting area even has a snack bar!
NOTE 2: As I prepare to capture some audio clips (I just purchased: Zoom H4n Pro All Black 4-Track Portable Recorder) from various modes to share via my new podcast feed, I am feeling particularly thankful for digital voice modes. As my age (I know, it’s just a number!) continues to creep upwards, I recognize that my hearing is not as good as it used to be. My hearing sensitivity is somewhat reduced so clarity of voices becomes more important. I use DMR, D-Star, AllStarLink (ASL), C4FM/Yaesu System Fusion (YSF), and rarely, Echolink. Of these, I find DMR, ASL, and YSF the nicest to listen to. Of these, YSF is, to my ears, the clearest audio when signals are strong. (I suppose that hearing is personal in the same way that we don’t all see the same colors.) For me, I would rank them with YSF in first, then ASL, with DMR in third place, but truth be told, they are so wonderfully close in audio quality that it doesn’t really matter.
NOTE 3: I pulled out my venerable Tec-Tec Scout 555 transceiver this week. I picked up some CW on 17 meters using a really poor antenna. There is a certain kind of joy to be had when using a very simple radio: power on, rotate the tuning knob, and enjoy!
Ten-Tec Scout 555 on my patio table
NOTE 4: The Fourth of July holiday (aka Independence Day) will occur before the next issue of the Random Wire Review on July 5. I hope you take a moment to reflect on what it meant to form a new country and shape it over the years. It wasn’t easy then and it isn’t easy now. This grand experiment continues to evolve. I wish us all well!
1. WIRES-X Nets
Says Yaesu:
WIRES (Wide-coverage Internet Repeater Enhancement System) is an Internet communication system which expands the range of amateur radio communication. For WIRES-X, an amateur node station connecting to the Internet is used as the access point and connects the wireless communication to the Internet. Users' stations can communicate with other amateur stations all over the world using a node within the radio wave range.
I know this list is woefully incomplete, but here are some of the nets I try to catch when I can. I’ve organized these by day with nets available every day of the week.
You can schedule a few ahead of time on your calendar, or if you pop into this newsletter on a whim, look at today in the list and find some nets! Alternatively, visit the list of active rooms and search for a term that appeals to you, such as “ragchew” or the name of your state.
If all else fails, try a search using WIRES-X NET as the search term. You’ll find some state and country nets that way that are not in my list.
I tag most of the nets in my list in Central time simply because it’s an easy conversion whether you are east or west of that time zone. (United States time zones are shown at https://time.gov/.)
6:00 am UTC (1:00 am Central): Northwest Fusion GroupSquirrel Net, an hour or more of gentle banter to start or end your day. All are welcome.
6:30 pm UK (12:30 pm Central): Northwest Fusion GroupThe Early Evening Net, everyone is welcome.
SUNDAY
10:00 pm UTC (5:00 pm Central): FediHams Net in Fusion room 73737.
MONDAY
8:00 pm Central: The POTA Net on America's Kansas City Wide Digital Network in WIRES-X room 28054. Discuss your POTA gear, your contacts, or tips on activating/hunting!
8:00 pm Central: The Digital Learning Net on Colorado Digital Multiprotocol Network in WIRES-X room 43674. Discuss everything about digital ham radio. Check in online and join the net with HAM.LIVE: https://www.ham.live. (I try to listen in on this net because it is always full of great information and people.)
5:00 pm Central: Food for Talk on America's Kansas City Wide Digital Network in WIRES-X room 28054. This is where farm families around the world share a little bit about who they are, where they live, and how they proudly grow or help feed our hungry world.
8:00 pm Central: America Link’s Round Table Rag Chew in WIRES-X room 21080.
2. Net Question: What is Your Legacy?
A few weeks ago I was listening to the Worldwide Friendship Net (IRLP and Echolink) via the W7RAT repeater in Portland, Oregon. Check out the W7RAT status dashboard at http://www.pdxirlp.net/:
Sometimes a net control operator will pose a question to help get conversation going on a net. It’s usually on a topic that is somewhat banal, like what is your favorite radio or what was your favorite car. However, on June 8th, net control posed a different, deeper question: what is your legacy? What do you want to be remembered for.
That is one thought-provoking question! I pondered this for the rest of my “pick up morning coffee” drive.
During my five-year stint as a volunteer emergency medical technical and mine rescue EMT, I was blessed to be able to save some lives. Who knows what some of those people — and their descendants — will accomplish? Each person you meet may represent unlimited future potential!
For me, though, the legacy I hope will endure is working hard to build a better future for our children and their descendants. I have done this for 32 years through my work for and with conservation districts in the Pacific Northwest. That work continues to this day. I could retire now, but I still get far more joy than pain from my work. As long as that equation holds true, I’ll continue working in conservation.
I know that history will forget my name, but I also know that future generations will benefit from my investment of time, money, and energy today. My words don’t feel quite adequate so I’ll parrot the words of a friend who says it more simply than I can: my goal is to leave the campsite better than I found it.
3. YSF Node Failure and Recovery
Last week, I was away on work travel for several days. When I got home, I noticed my home-built hotspot was not responding. (This is a home-built hotspot that I only use for Yaesu System Fusion.) I think we had a power hiccup while I was away.
Nothing I did seemed to resolve the problem with the hotspot so I pulled out the microSD card and re-imaged it with a fresh image. Once that was done and I restarted the device, I went through several iterations to try to get it to see the Nextion display. Once that was resolved, I restored a previously saved configuration. With just a few more tweaks after that, it was up and working normally again.
I think what I’ll do next, though: make a clone of the working microSD card so that I don’t have to do that dance with the Nextion display again!
UPDATE: Yes, I did it. I cloned my working microSD card. More on this in next week’s Random Wire Review issue 97.
4. Node Remote App for AllStar Nodes
The Node Remote for AllStar Nodes app is available for Android and iOS devices.
I tested this on an Android smartphone. It is working, more or less. I can connect and disconnect to other nodes but the app is not showing any information about my node. That could be something about the way my node is configured, I suppose.
Note that this app does not allow you to transceive using your smartphone. It simply facilitates connecting to, and disconnecting from, other nodes. You can, of course, do this by logging into Supermon (or AllScan if you have that package installed), but it is a convenience to just pull out the phone and connect in moments.
Node Remote feels a little rough around the edges, as if it was a great start but then got set aside. I could be wrong. It does work, and that’s what really counts, right?
5. Meshtastic Base Node Redux
I wanted to connect my small Meshtastic unit without a battery running on my home network with my always-on ThinkStation P510 computer operating as a server. But guess what? No Bluetooth on the P510!
A deeper dive into the Windows Device Manager shows that the wifi card installed is a Dell Wireless 1705 802.11bgn device. Interestingly, Dell shows this card has Bluetooth…but it isn’t running on my system. This is an older card that is limited to 2.4GHz so it might be worth upgrading.
For now, though, I purchased a Bluetooth USB dongle to give me modern Bluetooth capability. The TP-Link device is labeled on Amazon as:
TP-Link USB Bluetooth Adapter for PC, Bluetooth 5.0/5.3 Dongle Receiver, Plug and Play, Nano Design, EDR & BLE, Supports Windows 11/10/8.1/7 for Desktop, Laptop, PS5/PS4/Xbox Controller (UB500)
TP-Link Bluetooth 5.0 USB adapter
The directions said to insert the device into a USB port, then download the driver. However, my Windows 11 Pro machine immediately recognized the device. I did not have to install a driver.
An older version that uses Bluetooth 4 is available but as long as I’m going to shell out a few bucks, I’ll go right to Bluetooth 5 for a few bucks more! A link to the TP-Link dongle is available on the support page.
6. Closing Notes
6.1 SHARI node telemetry
If you have a SHARI node and want to fiddle with whether telemetry announcements are made when the node starts up, you might think those configuration details are contained in the /etc/asterisk/rpt.conf file. Nope. Find them in the /usr/local/etc/allstar.env file. Google is usually my friend when searching for information like this, but I went down the wrong rabbit hole so it took an hour or so to actually find the correct information.
6.2 Field Day photos and audio
RepeaterBook.com trailer at HoodView ARC Field Day event
I used my Zoom H4n Pro to capture an operator calling “CQ Field Day” at the very beginning of the 24-hour Field Day event. You’ll hear other sounds in the background and that’s because not only were there two stations operating in a small trailer, but a tour for visitors was occurring at the same time.
I serendipitously caught someone calling out “Field Day has started!” in the background of this clip:
KJ7T is in the booth! This is Tom Salzer with some Random Wire Reflections for Issue 96 of the Random Wire Review.
Condenser microphone this week
This week, I’m using the Blue Yeti Nano condenser microphone. It is more sensitive. I’m trying to talk across the mic rather than in it to help reduce the sibilants (the hissy “S” sounds) that are normal to my speech. I’m also recording into Zoom instead of Audacity, using the Zoom background noise filter to help quiet the sounds coming in from my environment. The final mix was done in Audacity.
WIRES-X Nets
A schedule of WIRES-X nets will be in issue 96 of the Random Wire Review publishing on Friday, July 28th. I found good nets for every day of the week.
YSF Hotspot Died
When I got home from several days of travel, I found that the hotspot I use for Yaesu System Fusion was not responding. I burned a fresh image to a microSD card and restored a previously saved configuration to get it back on the air.
What is Your Legacy?
“What is your legacy?” was a question posed during the Worldwide Friendship Net on June 8th. This got me thinking about my own legacy and I share my thoughts in this podcast.
Node Remote App for AllStar Nodes
I’m testing the Node Remote app for AllStar nodes. It isn’t working perfectly, but it does work. More on that in issue 96 on Friday.
SHARI AllStar Node Telemetry
I learned a tiny new thing with my SHARI AllStar nodes: the telemetry settings are not where I expected them to be.
Differences in Generations
This topic is not contained in Random Wire issue 96 — it is special to this podcast.
One of the topics in a training last week was about how different generations view the world, how they were shaped by events of the time, and how they think and speak differently. I’ve been thinking about that, and perhaps this helps explain the division that I still hear when people talk about learning CW and about those of us who did not learn CW.
Credits
Intro music: Positive Uplifting Music For YouTube Videos by UNIVERSFIELD — https://freesound.org/s/702873/ — License: Attribution 4.0
Fades between segments: Atmospheric, ambient fade by waveplaySFX — https://freesound.org/s/384695/ — License: Attribution 4.0
NOTE 1:Affiliate links for some products are available on the Support page. I’m not including the Support page link elsewhere in this newsletter because it just seems a bit much. If you are interested, please visit the Support page!
NOTE 2: Thank you to Ken for the coffee! Subscriber support is always appreciated very much. I’m a fan of free content and voluntary support when the spirit moves you.
NOTE 3: I had a long drive from Portland, Oregon to Burlington, Washington on Sunday and returned on Tuesday. I had the best company for both legs of this trip: I listened to Ham Radio Workbench 211 on the way to Burlington and Ham Radio Workbench 212 on the way back to Portland. For me, the Ham Radio Workbench Podcast is one of the highlights of being in our amateur radio community. I enjoy the content and how it is shared. Even my spouse (who is not a ham) enjoys the banter and passion voiced in the podcast. Random Wire Recommended!
NOTE 4: It was great to hear an interview with my home club president, Ben Hicks AB7I, by KMAS radio. Hear the 13-minute interview with Ben about Field Day at https://share.transistor.fm/s/632f251b.
NOTE 6: I’m starting to fiddle with podcasting. As I get this up and running, I’ll be posting audio previews of upcoming issues of the Random Wire. That’s not my end game, though — I’d like to include audio from different radio exchanges and modes so folks can actually hear what these systems sound like. The podcast will be available on Substack and can be found on Spotify and several other services.
1. Meshtastic Node with Rotary Encoder
This device finally looks like something that could be useful without a smartphone. I bought it because the rotary encoder allows me to set some pre-made (“canned”) messages. To reply to a message over Meshtastic, one selects the desired reply from that set of messages. No phone needed.
Meshtastic node with rotary encoder
I can envision a couple of these being useful on trail hikes, SOTA activations, boating, and other outdoor activities. Of course, it also works in conjunction with my cell phone via Bluetooth, but that’s a given.
Unlike most of the Meshtastic devices I’ve purchased, this one has a GPS module. That is a necessary feature for a node that can communicate without using your smartphone’s GPS.
Node internals
Using a Heltec board, plus having a GPS module running, power consumption seems a bit higher than most of my other nodes. Combined with the limited capacity battery, I’m not getting the battery life I’d like to see. This is easily remedied with a small USB power bank.
The seller operates the LayerFabUK store on Etsy. Shipments come from northern Scotland, but that has not been a problem. Shipments have only taken 10 days to two weeks to get to Oregon.
I think my next Meshtastic experiment will be a bigger jump forward, in the form of a Meshtastic T-Deck Lilygo with GPS. I can test sending and receiving messages by using my node with the rotary encoder with the T-Deck.
2. Base Station Meshtastic Node
While I was at it, I picked up a node without a battery. This runs from a USB-C power supply. I feel much more comfortable keeping this running unattended at home because it has no lithium ion battery inside. I run this node around the clock at home as a router-client. It is very lightweight so a small piece of reversed blue painter tape keeps it secure on the shelf.
Base station Meshtastic node
This was sourced from the OVVYS shop on Etsy for $52. Note: I replaced the stock stubby antenna with a longer 915 MHz antenna.
3. How to Manually Change your Hamshack Hotline Number on the Cisco SPA525G
About a month ago, the Hamshack Hotline folks announced the end of 10-digit calling numbers. These numbers are shrinking to seven digits. But what do you do if you have a 10-digit number already? That’s my situation with my Cisco SPA525G phone!
HH suggests re-provisioning the phone. Nope, not going to do that. I have way too many things programmed into my phone. I thought there must be a manual way to update the HH information without affecting my other lines and one-button shortcuts. The procedure I followed should be similar for other Cisco phone models.
For those who prefer a video walkthrough on how to update your number on a Cisco SPA525 phone, Vince VE6LK has just the thing. I wasn’t aware of Vince’s video when I wrote my instructions (such is the downside of preparing written content a few weeks prior to release), but since the process is not hard, what I came up with meshes very nicely with what Vince did. Great minds and all that ;-)
For the Cisco SPA525G phone, here’s how to manually update your 10-digit HH number to bring it in line with the new seven-digit system before the end of June 2024.
I encourage you to backup your configuration before making any changes to your Hamshack Hotline instance. HH recommends you re-provision your phone. I chose not to do this because I have five lines in use on my phone, plus numerous programmed buttons off to the side.
To save your phone’s configuration, access the web interface for the phone, then click Admin login. The URL should look like http://your-phone-ip-address/admin/ once you are there. Add spacfg.xml to the URL, i.e., http://your-phone-ip-address/admin/spacfg.xml, then press Enter. You’ll probably see your browser screen fill up with gibberish for a moment, then it should resolve to show a nicely formatted XML file. Click File, Save As, and save the spacfg.xml file to your computer. Now breath a sigh of relief because you have saved a copy of your phone’s current configuration. This means if you fumble finger the changes, you can revert to your prior working configuration and try it again.
To manually change settings, you’ll want to change how the HH number is displayed on the phone and how it authenticates to the HH system. To change the display, you should be logged into the Admin interface as described above. Then click the Phone tab. I have my HH number on Line Key 1, so find that section and change the information in the Short Name field as you wish.
Changing the Short Name changes the display on your phone
Line Key 1 is extension 1, so now click the Ext 1 tab and scroll down to the Subscriber Information block. Change the Display Name settings as you wish.
Now change the User ID from your 10-digit HH number to your new 7-digit HH number (no dashes or spaces). This changes how your phone authenticates to the Hamshack Hotline system. When you have made these two changes (Short Name and User ID), scroll to the bottom of the page and click the Submit All Changes button.
Changing the User ID changes how your phone authenticates to the HH system
At this point, your phone should reboot and (hopefully!) your new settings are now active. It’s a good idea to test your phone after making changes. Don’t forget to update your HH number in other places if you have included it on a website, signature, or other resource.
4. AllStarLink While Mobiling
For this exercise, I used my new SHARI PiZeroU node from Kits4Hams because it is small. If you are not interested in this content, skip down to Testing a New Phone Service. I have quite a few screenshots in the AllStarLink While Mobiling section so it is a bit long and tedious if it is not something you are interested in. Note that this same configuration will work not only when you are driving but also in a hotel room.
Essentially, I tethered my cell phone to the PiZeroU but there's a twist because the PiZeroU doesn't have an obvious Ethernet port. However, one of the two microUSB ports also functions as an Ethernet port with the correct USB-to-Ethernet adapter.
That still didn't get me quite where I wanted to go, so I picked up a short adapter cable to convert the Ethernet connection to a USB-C plug that goes into my phone. Then I enabled Tethering in the phone and powered up the SHARI node.
Once the node was booted up, I could easily use my handie-talkie to connect. However, since I was mobile, it was more convenient to use the mobile radio. I added a memory in my Yaesu FTM-300DR to connect to the node at low power. With the DTMF microphone in hand, I could easily connect and disconnect from nodes. Audio quality was very good as long as I had a good cell signal.
However (and there always seems to be a however!) this was actually a bit clunky in practice. It’s a bit awkward to manage the multiple bits of gear and connections:
Mobile node configuration with twist ties to make it neater
What I really do is use my phone as a hotspot. It is easier and works fine. To set this up, I added my phone’s wifi information to the SHARI node. Translation: I added a second wireless network to my node’s wpa_supplicant.conf file.
With two networks in the file, the node will look for the one at the top of the file first. If it doesn’t find it, it will then look for the next entry. My top entry is my home network and the second entry is my cell phone in hotspot mode. What this really means is once set up this way, the node automatically picks my phone as the network when I’m in the vehicle.
Select the wifi configuration menu item
Then select the setup option:
Select the wifi setup option
When you click on OK, you’ll be presented with some choices. The first is a sanity check: are you sure you want to do this?
“Do you wish to continue? Yes”
When you answer yes to continuing, you’ll be asked if you want to clear the existing file contents (i.e., start over on configuring wifi) or not. Since we are adding a second wifi network to the file, we select No.
Clear the file? No.
And this brings up another sanity check to make sure you are really doing what you intended. We click OK.
We say OK that the file is not cleared
At this point, you get a slightly veiled choice. You are asked if you want to manually enter the SSID. That’s what I did because it wasn’t very difficult. If you answer Yes, you will get the input screen. If you answer No, you’ll be presented with a screen that shows available access points.
Answer Yes if you wish to manually input the SSID and password of the wifi network
Here’s what that data entry form looks like. You’ll enter your SSID of the wifi network and press OK, then you’ll get another screen where you enter the password for the network.
Wifi network data entry form
Once you’re done, it’s a good idea to take a look at your wpa_supplicant.conf file.
Display the file
Mine looks like this (I’ve hidden the passwords). By viewing the file, you can confirm that both wifi networks are now present.
wpa_supplicant.conf file with two wifi networks
And finally, I always reboot the system after making a significant change. I doubt that I need to do this, but there are a lot of invisible moving parts in this little system and I like to know that I’ve given all those bits a chance to mesh correctly.
It’s a good idea to reboot after making changes
If you chose not to enter the wifi network information manually, you’ll see the screen that says it is scanning for available networks:
Automatic scanning for SSIDs
After a brief delay, you’ll be presented with a list of available networks. Where I live, that list looks like this:
Example of a list of nearby wifi networks
If you are using this method of selecting the network, after selecting the SSID, you’ll get a screen asking for the network password.
In summary, to operate mobile with your AllStar node, you can physically tether your node to your cell phone or you can configure the node to automatically select your phone as the wireless network (once you put the phone in hotspot mode). I hope this content helps the subset of us who like to use AllStar while traveling.
5. Testing a New Phone Service
In May, T-Mobile announced it was raising prices for some legacy plans. I haven’t seen that price increase in my bill, but while investigating this, I discovered that a hotspot that I reported as “lost or stolen” in January has continued to be on my monthly bill. I was told at the time that $50/month charge would come off my bill. It did not. When I inquired, I was informed that they had suspended the line and per policy, continued to charge the monthly fee.
Color me a bit unhappy to have paid $300 over six months for a device I no longer have and cannot use. No relief was offered. This is not the way T-Mo used to operate. Just a handful of years ago, customer service was very flexible in making sure customers were happy. I am not particularly happy now.
So it is time to shop. I use voice, data, and text. Sometimes I use my phone as a hotspot. I am probably above average in data use but my consumption is not extreme. I don’t watch movies or play games on my phone.
Given this kind of use profile, I went looking for unlimited voice, data, and text. I looked online for advice and found some helpful experiences on Reddit that persuaded me to give US Mobile a try.
I have a Google Pixel 4a that can use two SIMs (one eSIM and one physical SIM). I ordered a a discounted three-month plan (US Mobile is a pre-paid provider) for $45 that includes a free starter kit and paid $2 extra for rush delivery.
Since I’m on T-Mo for my main number, I planned to test the US Mobile service on the T-Mo network, thinking this would give me a real-world comparison to “real” T-Mobile service. But that’s not what I did. I selected the “Warp 5G” network which is really Verizon, not T-Mobile. (The “GSM 5G” network is T-Mobile and includes some international time but I don’t travel internationally; the Warp 5G is Verizon and claims it offers priority data which might be useful in crowded places.) The Unlimited Starter plan costs $23/month ($276/year) which is a fraction of my three-line T-Mo bill.
The SIM card should arrive before this issue of the Random Wire is published, so I may have a few very early thoughts below as an update.
The SIM card arrived and I configured the phone late Tuesday night. In so doing, I got a chance to test US Mobile’s customer service because the activation process did not go smoothly. The directions in the starter kit told me to download the app to the phone I was going to activate and to follow the instructions there. Well, those instructions started walking me through setting up a new activation, including paying for it. But I had already done that.
Customer service, via chat, suggested I go to the website and log in. I did that. However, I couldn’t find the activation instructions because the service agent misdirected me to a different menu. I finally found those instructions on my own and selected a new phone number for the phone.
In the mobile app, one instruction was to activate, then insert the SIM card. The website said to just insert the SIM card and I’d be done. I asked support what to do and waited…and waited…and then support asked: “Have you successfully activated yet?”
I gave up waiting, turned off the phone, broke out the nano SIM card, and installed that to the phone. Once I turned it on, it took about a minute before the phone found the cellular network. At that point, I had service on the Verizon network with my new phone number.
So far, so good. The next day, we went out to dinner and I put my T-Mobile phone beside the US Mobile phone. The T-Mo phone had full bars on 5G and the USM phone had 4 bars on LTE. That, of course, is going to vary by location. I tested them side-by-side by loading Facebook, then loaded Google News, then loaded CNN. My T-Mo phone loaded about half a second faster than the Pixel, but that reflectedthe difference in cellular network where I was located and the slight difference in processing speed of the phones. There were no hiccups and service has been continuous since I activate the USM SIM.
Right now I’d give USM an A for cellular service and a B for customer support. Most of us aren’t going to need much customer support, so personally, I put more weight on the quality and distribution of cellular coverage. I anticipate switching my family plan from T-Mo to USM by the end of the three-month trial.
6. XHDATA D808 Radio
As promised last week, here is more information about the XHDATA D808 radio. It arrived the night before issue 94 was published so I only hinted a bit about it last week.
D808 box
The radio came in a brown cardboard box. Inside that was the retail box cover as shown above. Inside that was a white cardboard box as shown below, with the radio wrapped in bubble wrap and foam wrap. In other words, it was protected by multiple layers of material.
D808 unboxing
The D808 in hand feels very nice, rather like the Tecsun PL680 Portable Digital PLL Dual Conversion AM/FM/LW/SW and Air Band Radio with SSB I purchased a year ago for about $36 more than the cost of the XHDATA D808. (Yes, this means I now have two radios that do much the same thing! The D808 will live in the travel trailer and the PL680 will be at home or in my luggage when I travel.)
D808 in hand
Accessories include a brief manual, a leatherette carrying pouch, a USB cord for charging, and a wire antenna that plugs into the 3.5mm external antenna jack.
D808 manual and accessories
A major selling point for me is the use of a standard 18650 battery.
Single 18650 battery
As I write this, my spouse is using the D808 to listen to classical music on a local FM station. Using it on the Air band was simple: push the AIR button then hold the up arrow until the radio begins to scan the frequency range. When it hits the top of the frequency range, it stops scanning. Then hold the down arrow down until it starts scanning. Rinse and repeat. Other bands work the same way.
I only have two negatives to share about the D808. First, I wasn’t aware the wire antenna came with the radio. It was not listed in the “included components” in the Amazon listing, but upon review, I see it listed in the accessories a bit farther down the page. Chalk that up to buyer inattention.
The second item is that I’m not sure the lithium ion battery is protected. If you choose to replace the battery, it’s a 18650 Li-ion battery with a button end, not the flat end. You might already have one of these in your kit somewhere.
7. David Gleason and the World Radio History Website
I became aware of it because of interactions I’ve had with David Gleason NR9V about AllStarLink. He developed a nifty bit of software that makes it easy to keep a list of favorite AllStarLink nodes, but more than that, it shows you which nodes are active. His AllScan software runs on both kinds of nodes in my collection: those that run on AllStarLink and those that run on the HamVoIP distribution.
David encouraged me to try building an AllStar node, even when I was demonstrably awful at soldering. I came close to succeeding but eventually bought a device from him that runs my always-on node 588412. I have continued to appreciate his kindness and mentorship as I worked to improve my skills.
Since then, I’ve learned a bit more about David’s history. He has built one of the most amazing collections of curated radio history. I commend the WorldRadioHistory website to you. Amateur radio operators may wish to start by checking out old publications at https://www.worldradiohistory.com/Home-DX.htm. There you will find scans many old journals such as 73 Amateur Radio Magazine and even The Modulator, the ARRL’s journal in 1923.
There is so much to discover on the World Radio History site that I feel like it should come with a cautionary note:
WARNING! YOU MAY LOSE TRACK OF TIME!
The Library of American Broadcasting Foundation (LABF) has honored David with the inaugural Excellence in Broadcast Preservation Award for his work to preserve broadcast history. What an incredible treasure trove of radio history. Well done, David!
8. Closing Notes
8.1 WIRES-X audio device not found
My WIRES-X Portable Digital Node has been operating very well, but I continue to have occasional problems with the audio device:
Not found the Audio device for the WIRES-X use.
I described this issue here and here in issue 93. As a reminder, I’m running the WIRES-X software on my under-desk server, which I administer from other computers. WIRES-X is forgetting there are audio devices plugged into the computer.
The workaround that is working for me is to reboot the server but I don’t like doing that. Most of the time, if I physically connect a keyboard, monitor, and mouse to the server and then restart WIRES-X directly on the server, WIRES-X finds the audio device and I’m good for two or three days. I tried going through these steps by remoting in from another computer but that doesn’t work. I’ve got to be “on” the real computer that WIRES-X is running on.
After the audio device is found again, I disconnect the keyboard, monitor, and mouse and use WIRES-X remotely…until the audio device is again not found.
8.2 Microphones redux
I’m back to using the Blue Yeti Nano microphone as my daily driver on Zoom and Teams calls. The videoconferencing software seems to do a remarkable job of filtering out background noises. Using the cardiod pattern on the microphone, I’m getting good reports of audio quality from others.
I did try using the Audio-Technica 2005 USB/XLR microphone on my proof-of-concept podcast recording but it picked up every hissy sibilant in my speech. Next time, I’m going to try the Nano, hung upside down above my mouth, with the “dead cat” wind/pop filter. As long as I can choose a quiet time for recording, the sensitive Nano should work fine.
Thank you to current, new and future subscribers! 73 to all,
Note that affiliate links for some products are available on the Support page. I’m not including the Support page link elsewhere in this newsletter because it just seems a bit much. If you are interested, visit the Support page!
I know from reading posts around the interwebs that a significant percentage of amateur radio operators are upset about the Logbook of The World (LoTW) going offline. I use LoTW, too, but I’m not nearly as upset as some folks are.
Those of us with some information technology background seem to be growing more and more appalled as we learn about the archaic systems the ARRL has been depending on for many years. Let me be kind, though, and refer to them not as archaic but as legacy systems.
I happen to have some empathy for the ARRL. This arises from my experience running a statewide nonprofit association where we strive to accomplish as much as we can while spending as little as possible. Such is the nature of nonprofit work: trying to accomplish big outcomes on a shoestring budget. This means some of our IT systems are cobbled together from disparate pieces of software and hardware, and the entire system depends on one or two knowledgeable individuals to keep them running (yes, I am a single point of failure in our system). Some of our bits and pieces are very old (legacy) that were once common but are now uncommon. We know this is not a resilient approach but we just don’t have the funds to outsource much of our infrastructure and support.
I’m guessing the ARRL is in much the same boat. People a few decades ago built systems and since those systems have continued to function, little additional investment was made in the software and hardware. I’m reminded of the plight of an agency in the State of Washington some years ago as they realized their system, which ran on COBOL, was unsupported because all of their COBOL programmers had retired.
I’ve said to others (somewhat tongue in cheek, but with a kernel of truth, too) that information technology moves along in dog years, i.e., for every year we experience as humans, the tech advances seven years. It’s brutally hard to keep up, and it’s ever so easy to fall behind. Once you are behind the curve, it becomes almost impossible to catch up without something drastic happening.
To me, the ARRL’s situation presents a remarkable opportunity for all of us. First, we are all getting a lesson on vulnerability of systems. As we learn more, many of us are certainly looking inward at our own computers, backups, firewalls, and more. I know I’ve turned off some port forwards that I realized I no longer needed. I have some other internet-facing equipment that I could more safely access through a single point of entry over my VPN. Computing is now such a significant part of amateur radio that we can’t afford to be ignorant of security, redundancy, and resiliency. We can’t afford to not keep up.
I think the ARRL has been handed one of the most unique opportunities in its history, and that is: to share with members while they rebuild and upgrade their systems. For those who wistfully recall the days before computers, this information will not be welcome. For the rest of us, we can learn from the ARRL’s experience and regain confidence as we observe how it recovers from this debacle. This is a teachable moment not only for the ARRL but for all of us who depend on internet-connected technology.
I know the accepted wisdom in these situations is to keep information close to the vest because one doesn’t want to hand bad actors more attack vectors. I get it. Nevertheless, the ARRL could have done a little better. Over the past several weeks, real information (not speculation) has been very sparse. (However, this has changed over the past few weeks: https://www.arrl.org/news/arrl-systems-service-disruption.)
In computing terms, whether to support the ARRL or not seems like a binary choice: members can either help them grow and improve, or we turn away, accelerating their demise. I lean toward building on the strong history of the ARRL and supporting a ground-up rebuild, one that doesn’t depend on single points of failure.
In a more tongue-in-cheek vein, let us all hope that they don’t rebuild like this XKCD Circuit Diagram. That style of infrastructure build-out might be how the ARRL arrived at this moment!
2. These Are Some of my Favorite Ham Sites
Below are some of my favorite amateur radio websites and podcasts. This is not intended to be an exhaustive list. I’d love to expand my reading and listening so if you have recommendations, please do share!
If you’ve wanted an informative, attractive dashboard in your ham station, you may want to check out the VA3HDL system.
To get the code, jump to https://github.com/VA3HDL/hamdashboard/ and click the green button labeled <> Code and then select Download ZIP. But before you do that, take a look at the explainer video put together by KMR4ACK.
I used the KM4ACK instructions to make some changes in the code (took about 20 minutes while I was simultaneously on a video call), resulting in my dashboard:
KJ7T Ham Dashboard
The last time I look at the VA3HDL dashboard some months ago, customizing it was not nearly as easy as it is now. Thank you to Ben AB7I for reminding me of this software.
4. First Podcasting Mistake: Wrong Microphone
File this under: I should have known better.
I bought the wrong microphone for podcasting and video conferencing. It is a lovely Blue Yeti Nano. This wonderful device picks up every sound around me and that’s the problem. It would work very well for picking up nature sounds but for my purposes, I don’t want every little sound captured: a toilet being flushed, a crinkle of paper, a dog barking, a car being revved. That level of realism is not really what we expect to hear in most podcasts or during video conferences. We expect to hear clean audio, scrubbed of extraneous, distracting sounds.
The Nano is a condenser mic. I had forgotten that condenser microphones tend to pick up a lot of sound…a LOT of sound. As soon as I plugged it in and started listening on headphones through the monitoring port, I knew what I had done. Oops.
I immediately flipped this script by purchasing an Audio-Technica AT2005USB Cardiod Dynamic USB/XLR Microphone. Not a condenser microphone. A dynamic microphone. I like the idea of having the flexibility of using USB or XLR connections. If you’re curious, Podlad.com presents a nice discussion of differences between these types of microphones. I am finding the dynamic mic works much better for recording and video conferences. (However, truth be told, video conferencing software has become quite adept at filtering out background sound. While using the Nano this week for Zoom calls, nobody said a thing about background sounds. That might be a workaround if you have a condenser mic: use conferencing software to record your audio.)
I know I’ll make mistakes as I get started with podcasting. I did not expect that I would choose the wrong kind of microphone right out of the gate. Despite feeling like I made a silly error, I’ll keep both mics because each has strengths that work well in particular situations.
Next up, I’ll be looking at portable audio recorders and USB audio boards, as well as podcast hosting services. I’ve not done exhaustive research on podcasts hosts. I do rather like the features of SquadCast. The price point isn’t out of reach, at least at the Creator level.
This is an interesting (to me) journey. I’ll gladly take recommendations! Please do send them along if you have advice.
UPDATE: I also bought an off-brand dynamic mic that actually has a slightly darker sound to it. I tested the MAONO USB Dynamic Microphone, Podcast Recording Microphone with Gain Knob on my desk with a “dead cat” fur windscreen over the cardiod element. The MAONO mic is relatively compact, it is not expensive, and the sound characteristics are very nice, especially for my tends-to-be-light voice. After a few days of use, I went back to using the Nano. I need to test various scenarios with the Nano a bit more before recommending it, but I sense that I’ll land there in a few weeks.
UPDATE #2: Something simpler for Zoom and Teams meetings might be the TONOR USB Conference Microphone for Laptop. Again, not expensive. This is described as a supercardiod dynamic mic. Like all of my dynamic mics, distance from the microphone is important. The Nano is a bit less sensitive to distance because it is a more sensitive microphone. This is significant in video conferences where seeing your face is an important part of communicating. With a dynamic mic a few inches from my face, I’m partly hidden. This is one reason I’m leaning toward the Nano as a great all-around choice. (Other factors are: build quality and the ability to select between a cardiod pattern and omnidirectional pattern.)
If you have advice as I start to build out my podcasting suite of tools, please do let me know. I am running Windows 11 Pro machines with Audacity for editing sound files. I have not been a Mac user for about 15 years so I am no longer knowledgeable on that family of platforms.
5. Speaking of Microphones…
Recently, I reached out to a worldwide vendor of microphones and other amateur radio gear. Their products are used in broadcasting and they sell desk mics for amateur radio. (No, I am not talking about Heil Sound.)
I gave them the brand and model of my radio (Yaesu FTM-300DR) and asked which of their desk microphones would work with my device. The answer both surprised and disappointed me:
Our mics won't operate with Yaesu VHF radios - you need an electret element mic. Ours are dynamic.
Uh, the microphone that comes with the FTM-300DR is a dynamic mic. I replied to tech support with this information and that seemed to end our conversation. Well, scratch that vendor off my list.
I may try an XLR microphone (cue the already-in-my-kit Audio-Technica AT2005USB mic with XLR) and some adapter cables from Heil to make my own dynamic desk mic for the FTM-300DR. I haven’t found a plug-and-play desk mic for this radio. I would like to use a desk mic for my Portable Digital Node on my home desk.
6. Pinged by a Radio Vendor
A few weeks ago, I received a request to review a radio in the Random Wire review. I’m sure it was going to be one of those “we’ll send you a radio for free if you’ll review it in the Random Wire” kind of things. I did not take them up on their offer but I did take a peek at their line of radios. There are a couple that look interesting.
6.1 XHDATA D608WB Emergency Radio
Their emergency radio has some features I like. This unit is designed to keep on hand if there is a weather emergency, for example. I like that the battery is a replaceable 18650 battery. Nothing proprietary with that choice!
There is a small solar panel built into the top and a hand crank on the back. There is a flashlight. Nothing unusual there. But the solar panel can be angled upward, and underneath is an LED panel for area lighting. That could be very handy.
It’s got Bluetooth, memories, an SOS alarm, alarm clock, NOAA weather alerts, MP3 player, and more. For me, the only thing it is missing is the ability to listen to air band transmissions. In a disaster, listening in on air traffic could be informative.
The price point at $35 (after clipping a coupon) is very attractive. While I’m usually not attracted to these inexpensive emergency radios, this one doesn’t look too bad for the price.
6.2 XHDATA D808 Portable Radio
Unlike the yellow-colored D608WB emergency radio, the D808 looks more like a retail AM/FM/SW radio you might see on a store shelf. Note that the product number does not include WB, meaning this radio does not include NOAA weather alerts.
But what it does have is the ability to tune upper side band and lower side band signals. For amateur radio operators, that opens up more listening opportunities than a less expensive AM/FM/SW radio and single side band. Like the D608WB, it uses an 18650 battery for portable power.
At about $100, this unit is a bit more expensive. The clincher for me? It includes air band coverage. This looks like a nice, solid radio to put in the corner of my desk at work.
For both radios, some online reviewers have suggested that the 18650 battery included is not a protected battery. One reviewer said he bought name-brand 18650s that were protected and they fit in the battery compartment.
6.3 Tecsun Digital PL330 AM/FM/LW/SW Worldband Radio with Single Side Band Receiver
While Tecsun did not reach out to me, a great alternative to the XHDATA D808 is the Tecsun PL330. I have some Tecsun radios. Not only are they well built, they also perform well. The PL330 is about $20 cheaper than the D808 making this quite a good value. SWLing.com has a solid review of the Tecsun PL330 that also mentions the D808 in several places. That seems particularly apropos here since I mention both the D808 and the PL330.
6.4 Which to choose: the D808 or the PL330?
I don’t have a recommendation for you. If you want to have airband, then you might pick the D808. If you want Tecsun quality, you might pick the PL330. While I really like Tecsun products, I’ve ordered the D808 because of (a) airband coverage, (b) ability to tune single side band, and (c) the battery is an 18650 cell. This will be a throw-in-my-luggage receiver for enjoyment during hotel stays. For $8.30 more, I’m adding the AN-80 Shortwave Reel Antenna FM SW External Antenna Whip Antenna to Improve Signal Reception Suitable for FM SW Radio to my order. Note that the D808 also has a 3.5mm jack for an external antenna, so a small active loop antenna might be something to consider in the future. (A loop with a 3.5mm plug would also fit my ATS-25MAX radio.)
LATE UPDATE: Waiting for me when I got home from my latest trip late last night was the D808 radio. I unpacked it and powered it up to a classical FM station located in the Portland area. The sound was good for the small size of the radio. It is about the size of my hand and feels rather solid. I’ll have more about the XHDATA D808 next week, but on first examination, I’m pleased.
7. Replacement Fan on RPi 4 Case
The Easycargo Cooler Kit worked great when I replaced the noisy fan in my Canakit Raspberry Pi. The lid of the case has a space where a 30mm x 30mm fan fits and is held in place by slightly springy plastic clips. The Easycargo fan was a perfect fit and it is running much quieter than the original fan. The household is happy once again.
CanaKit case for Raspberry Pi 4
You may observe in the photo above one of the less desirable features of this case: it is glossy so it shows fingerprints and smudges very well. I have it stuck out of sight on a shelf so that aspect doesn’t matter to me. It has plenty of openings to help keep the RPi board cool with the assistance of the fan.
8. Closing Notes
8.1 Portable Digital Node now runs from a power supply
I picked up an off-brand bench power supply that has been powered on 24/7 for the past couple of weeks. I didn’t really need it because after three days of the FTM-300DR running as a Portable Digital Node around the clock while attached to the big battery, the input voltage sensed by the radio did not vary. It stayed at 13.4 VDC the entire time. However, the battery really isn’t a great long-term solution so I purchased a power supply to use day to day, with the battery still available as a backup if the power supply lets out the magic smoke. With the addition of fused wiring, Power Pole connectors, and a T-connector, the radio is powered up and working fine.
As a maybe-it-is-interesting aside, my daughter was reading over my should while I typed this. I had originally typed 24x7 and she was mildly offended by it because it looked like math. She believed it should be 24/7. We found a Reddit thread on this very topic! For clarity, I am switching to 24/7 as that seems much less confusing.
8.2 Killing the standby beep on the FTM-300DR
We added a dog to our household a year-and-a-half ago. Mary is part Corgi, part Dachshund. Can you believe that mix is called a Dorgi? I laugh every time I hear that descriptor. Mary has characteristics of both but she leans toward Corgi.
Mary the Dorgi at 3 years old
She is now four-and-a-half years old. What does this have to do with radio? Well, whenever one of my radios beeps, her head and tail drop and she silently disappears. Her body language screams: “I’m escaping something painful or dangerous.” I’ve been having trouble understanding this but at a recent conservation district meeting, a light bulb went off in my mind. The district was talking about virtual fencing for cows. In simplest terms, a geo-fenced perimeter is established and cows with collars get an audible tone, then a vibration, and finally a shock as they approach and reach the perimeter.
It was the description of the collar generating a tone that triggered the connection in my head. One of the district board members is a vet who I talked with after the district meeting. When I described how Mary reacts to my radio beeps, she said: she’s been collared.
Now I’m trying to figure out how to reverse that training. Mary doesn’t bark even though the two breeds in her mix are often quite vocal. She must have been a barky pup and the previous owner used a shock collar to change that behavior.
I did find a way to eliminate the beep on the FTM-300DR at the end of every digital transmission. A few minutes of searching revealed there is a menu setting on the FTM-300DR for something called a standby beep. Turning that off killed the beep following digital transmissions.
I turned off standby beeps in my Yaesu FT3D handie talkie, too, so that when I’m using the HT with my Fusion-only hotspot, the radio won’t beep. M0FXB has a short YouTube on how to turn off the standby beep on a Yaesu FT5D radio. The process is very similar for the FTM-300DR and for the FT3D.
Hopefully Mary will find it a little easier to be around me when I’m playing with radios now that the beeps are gone.
8.3 When do I write this newsletter?
I have found that if I leave content creation to the last minute, I feel stressed. Writing this newsletter then feels like a burden. A few months ago, I changed when I start a new issue by starting on it a few weeks before I publish the current issue. That means I am writing issue #94 before I’ve published issue #93.
That change, by itself, has changed the equation for me. Writing is once again something I look forward to because I don’t feel a clock ticking away toward a deadline.
The downside is that the last few months of Random Wire newsletters have become more like journals. I capture ideas during the days (and nights) when they surface, and sometimes I probably have not been taking enough time to organize my thoughts better in the newsletter (at least that’s how it feels to me when I review an issue a few weeks after it publishes).
9. Coming Next Week
Here are some of the topics planned for next week’s newsletter (Random Wire Review #95):
Meshtastic node with rotary encoder
How to manually update your Hamshack Hotline number on a Cisco SPA525G phone
AllStarLInk while mobiling
I’m also working on a list of WIRES-X nets but I think that won’t be ready until the June 28, 2024 issue (Random Wire Review #96).
This issue of the Random Wire is loaded a bit more heavily than usual. I’ll be traveling again most of next week so I am front loading content in anticipation of having somewhat less meaty content in the June 14, 2024 issue. However, that will be a good issue to talk about Field Day plans!
The other high-level thought I want to share is this: I wish to be a lifelong learner when it comes to radio, and to accomplish this, I try to do something with radio every day. When was the last time you powered up one of those radios on the back shelf, in the closet, or hidden in a box? I learn every time I touch a radio.
1. Configuring the Yaesu FTM-300D as Portable Digital Node
This piece on WIRES-X has been delayed over and over again. Getting my WIRES-X registration approved was delayed, then I was traveling so much for work all I wanted to do was hit the pillow when I got home. Finally, though, the planets have aligned and I was able to get my radio set up on my desk.
By the way, for those of us who have been wondering what WIRES-X stands for, it is an acronym for Wide-coverage Internet Repeater Enhancement System. The first version was called WIRES, then WIRES II. WIRES-X, the successor to the earlier systems, “supports the C4FM digital and voice technology.” Also, you may find (as I did) that many users use Personal Digital Node in place of Portable Digital Node. Since the Yaesu manual calls it Portable Digital Node (PDN), that is the term I use here.
Those of us who have inhabited the world of Yaesu-brand amateur radios know that the menus can be a bit challenging. Settings that ought to be next to, or near each other, in the menus are often widely separated, making the configuration of a Yaesu radio confusing at times.
Setting up my Yaesu FTM-300DR (available at major amateur radio stores) as a Portable Digital Node with WIRES-X was worse than any other Yaesu system I’ve used to date. This was one of the most arcane radio configuration sequences I’ve undertaken. Below, I’ll explain it as simply as I can, but it is peppered with some hints and discoveries that occurred as I worked through the steps necessary to get my radio operating as a PDN.
Please note that I configured the radio to operate without the WIRES-X HRI-200 device. There are different steps to follow if you are using an HRI-200. Yaesu explains the differences between using the HRI-200 and not, which I summarize as: if you want to host a room or control the remote remotely, you need the HRI-200. For most of us, operating as a Portable Digital Node without the HRI-200 is probably fine.
FTM-300D as Portable Digital Node
1.1 What you will need
To configure the FTM-300DR as a Portable Digital Node, you’ll need:
You need a set of Yaesu Interface Cables SCU-58. The manual specifies the SCU-40 cable set but the SCU-40 has been replaced with the SCU-58 set. (It turns out for use as a Portable Digital Node, you don’t need the audio cables that come in the set; more on this in a minute).
The correct COM port driver and the WIRES-X program. Find the WIRES-X Connection Cable Kit Driver Installation Manual 2205A and the PL23XX Prolific Driver Installer (ver. 402) at the bottom of the FTM-300DR Files page. Find the WIRES-X program at the bottom of the list on the WIRES-X Internet Linking page.
Successful registration for WIRES-X (register here).
1.2 Updating and installing
Before installing software and connecting the radio to your computer, you should update the firmware in your radio if needed. To do that, you’ll need to check the firmware version of your radio and compare it to what is available on the FTM-300DR Files page. Finding your firmware version on the radio is explained on page 11 of the WIRES-X Portable Digital Node Function Instruction manual which is not on the FTM-300DR page but rather on the WIRES Internet Linking page.
(Note that at this point, you’ll be powering on the radio. I never turn a mobile or base station radio without an antenna or a dummy load attached. I am using a 25-watt dummy load (affiliate link on the Support page) just in case I mess up and accidentally transmit RF. Better safe than sorry. A dummy load is a lot less expensive than repairing a radio or buying a new one.)
You need to install the correct serial port driver before installing the WIRES-X software on your Windows computer.
Once all of these preparations are complete, you’re ready to make physical connections between the radio and the computer and fire things up.
1.3 Connect the radio to the computer, start it
For a Portable Digital Node, plug the SCU-58 cable into the back of the transceiver then plug the USB end into your computer. After starting the radio by holding down the two orange buttons (GM and DX) while simultaneously holding down the power button, the radio should power on in WIRES-X DIRECT mode. Now go to the Windows Device Manager and make sure you see the Prolific driver in the Ports list. For me, the driver is assigned to COM13.
Prolific driver shows up in Device List
1.4 Start the WIRES-X software
Now you can start the WIRES-X software on your computer. Make sure it is using the correct COM port. Every time I start it, it defaults to COM4 which is not the correct port. I have to manually change it in the software under File —> Communication port. Then wait a minute or so for the software to populate the list of available rooms.
But when I did this, what I saw at the bottom of the WIRES-X application was this message:
Not found the Audio device for the WIRES-X use.
With help from some folks with the Colorado Digital Multiprotocol group (specifically: Chris KB2IDX, Jimi N7VDR, and David WD0HDR), I learned that the audio cables that come with the SCU-58 cable set aren’t really needed when using the FTM-300DR as a Portable Digital Node. All you need is the correct kind of plug stuck in the computer’s microphone jack. On my laptop, it’s a combined mic-and-headphone jack, so I found an old pair of earbuds with a 3.5mm jack and stuck that in. After restarting WIRES-X (and again having to set the correct port), I was good to go.
After learning this tidbit, I found a YouTube that demonstrates this great trick:
You might run into a snag with this workaround. I did. I’m running WIRES-X on a computer I access remotely and the input port seems to go to sleep after some undefined amount of time (usually a couple of days). The solution has been to reboot the server but that is not my happy place. I ought to have WIRES-X running on a computer dedicated to this use but since my server has capacity, I chose to set up my system that way. Meanwhile, I bought a complete set of SCU-58 cables — including the audio cables! — from DX Engineering. This has not solved my problem but at least I know how to fix it: reboot!
1.5 Selecting a room
You would think you would simply scroll to the room you want and maybe double-click on it. Nope. You go to the top menu and select Connect —> Connect To, enter the numerical code of the room, then click OK.
CONNECT TO menu in WIRES-X
Here’s a screenshot of my FTM-300DR connected to the Olympic Mountain Digital room:
WIRES-X connected to Olympic Mountain Digital
To be more clear, you find the number of the room you want in the room list in the lower left pane of the WIRES-X program. You connect to it using the Connect menu at the top of the WIRES-X program. To see the room number, you can expand the DTMF ID field with your mouse. Below, I’ve highlighted 04429 which is the Olympic Mountain Digital room.
Olympic Mountain Digital in the room list
1.6 Ready to transmit
If all has gone well, you should be ready to transmit. There’s only one way to find out. Grab that microphone and try it! I had a brief QSO with Gary AC7VA that showed up in my hotspot web interface:
QSO with AC7VA shows in my hotspot interface
I am no expert on this. This is my first time off the starting line with WIRES-X. I’m comfortable with using my Yaesu HT on my hotspot. Using the FTM-300DR on WIRES-X is a new experience. The best parts: the sound quality is great and the node is always on, ready for me to use.
1.7 Current draw
Constant learning is one of the best things about amateur radio. I am wondering how much current my radio is drawing. I need to figure out how long I can go before charging my big battery. It looks like RX consumption is 500 mA and TX is max 11 A, but a Redditor measured 280 mA for RX and a range for TX from 2.5 A to 9.2 A. (Note that the TX values are for RF transmissions, but with the radio set up as a Portable Digital Node, there should be no RF transmissions.) The takeaway is: if I’m monitoring most of the time, the big battery should last me for days.
I did a very simple test by leaving the node operating overnight on the battery. When I went to bed, the battery voltage was 13.4 volts. When I got up the next day, it was still 13.4 volts. This suggests I can (a) assign the big battery to this use and not worry at all for days or (b) assign one of my smaller LiFePO4 batteries to powering the node and recharge a bit more often. I haven’t decided. (Later, I ran it around the clock for four days and saw no change in the big battery.)
I’m going to reinstall everything on my Lenovo P510 ThinkStation computer (affiliate link on the Support page) that runs 24x7. Right now the node is running off my laptop that I use for video conferences. WIRES-X takes over the sound card in the laptop, meaning sound doesn’t work in other applications while WIRES-X is running. Since the ThinkStation runs around the clock, it seems like the best choice for running the Portable Digital Node. However, this also means I ought to add a larger uninterruptible power supply for the ThinkStation, something that has been on my to-do list for quite some time.
1.8 UPDATE: I moved the node to the ThinkStation
These are the steps I followed to move the radio node to the ThinkStation.
Download and install the Prolific driver, reboot.
Download and install the WIRES-X software.
Find the COM port number in Device Manager.
Start WIRES-X on the computer. Make sure it is connected to the correct COM port (File —> Communication port).
Start WIRES-X on FTM-300DR.
This will populate the serial number field in the WIRES-X app on the computer.
Enter my node and room number (found in the user registration from Yaesu) in the column titled DTMF ID, then click ID Entry, then OK.
Initial WIRES ID Activation screen
That should do it…but it didn’t. I forgot to move my headphones to the ThinkStation. I plugged them into the front mic/headphone jack and restarted WIRES-X. It still didn’t see the headphones. As I thought about this, I remembered there are mic and headphone plug receptacles on the back panel. After plugging the headphones into the mic input on the back of the ThinkStation, WIRES-X detected the audio device and the program started cleanly. My radio display changed to read DIRECT in all caps.
The dreaded “not found the audio device” message
Then I waited for a few minutes for the list of rooms to populate. Once that was done, I entered the DTMF ID of the Olympic Mountain Digital room (04429) in the Connect —> Connect To menu. At that point, I was connected to the W7NEE repeater in Shelton, Washington from my QTH in Portland, Oregon. (Later, I moved the SCU-58 cable to a different USB port on the computer and the “not found the Audio device” message returned. It disappeared after I rebooted the ThinkStation.)
Screenshot of WIRES-X running remotely on the ThinkStation computer
Note that I’m running this on the ThinkStation and accessing the interface from other computers using remote desktop software. This allows me to not use my primary computer (Lenovo ThinkPad X1) to run the WIRES-X Portable Digital Node.
Also, I hope you recognize how much quicker the setup went the second time. Walking through the process the first time is simply confusing. There is no doubt about that. But after taking that walk once, the second time was much, much easier!
1.9 Changing the timeout setting
My last hint is about the timeout setting of WIRES-X. The default timeout is 10 minutes. That means if you have no activity, your node will disconnect from a room in 10 minutes. If you want to remain connected to a room for longer periods of time, change the setting in the WIRES-X app on the computer. Go to File —> Settings —> General settings then check the Unlimited TOT box and click OK.
2. SHARI Node in Kit Form
After the last couple of issues of the Random Wire where I talked about my new “Silver Surfer” SHARI node for AllStarLink, a couple of subscribers asked for more information. Operating under the general rule of thumb that if one person asks, ten people might be wondering, I’m including a bit more information on building a SHARI node in this issue. (SHARI, by the way, stands for SA818 Ham Allstar Radio Interface.)
The closest analogue to the Silver Surfer is the Kits4Hams SHARI PiHat in a Unistorm case. This is available from Kits4Hams for $80, not including the Raspberry Pi 4, power supply, and microSD card. Some soldering is needed. You’ll also need to download the HamVOIP image, install it to the microSD card, and configure the settings.
If that seems like too much work, Kits4Hams can build the node for you. Here is their description from the Kits4Hams website:
Kit – Available as a parts kit for $80 (UHF or VHF, right-angle or straight antenna). You supply the Raspberry Pi, Pi power supply and microSD card to complete your Allstar node . Please be sure to download and study the SHARI PiHat Construction manual to be sure you own the required tools and possess the required mechanical and soldering skills to build the kit. Additional Options: – We will solder the SA818S radio module onto the PCB for an additional $5. – The fan option is $8
Built – We supply all the parts including the Pi4B and Pi4 power supply. You supply the microSD card and perform the setup of Allstar – A complete assembled and tested unit is $205 ($215 with fan). This option is currently available as we have Pi4-2 GB boards.
The $215 built price with fan compares very favorably to what I paid for the Silver Surfer.
One thing I like about the $80 Kits4Hams kit is they will do the most finicky bit of construction for you (i.e., soldering the SA818S module) for only $5 more. That seems like a great option for those of us who want to save some money and who might not do so well at fine soldering but are okay with larger/coarser connections.
Their newest node kit is the SHARI PiHat in a 52Pi case. In this build, the cooling fan is mounted inside the case. The top cover is Lexan so you can see the indicator LEDs. This particular build looks very nice.
Disclaimer: I am a Kits4Hams customer. They have built a shiny new SHARI PiZero node for me and I discuss it in below. I receive no financial benefit from recommending Kits4Hams products and services.
3. SHARI PiZero from Kits4Hams
As noted above, today I write about my newest of AllStarLink nodes, the SHARI PiZero. This was built and programmed for me by Kits4Hams. It was literally plug-and-play: it arrived, I plugged in the power, it joined my home network, and then it showed up on the AllStarLink.org nodes page. Boom, just like that!
This is a small and sturdy build, perfect for tossing into a briefcase or luggage, along with a handie talkie programmed for the correct frequency.
I like that Kits4Hams uses the official Raspberry Pi power supply. My understanding is the official power supply uses a shielded cable. (In my RF-rich environment, that makes a difference.) To that has been added a big ferrite. Whatever they have done, the sound quality I am getting is better than my two other SHARI nodes!
SHARI PiZeroU with Ethernet adapter and power supply
The node is running at about 130° F, comfortably below the maximum temperature for the PiZero board. (After letting it run overnight, it was at 122° F, and the highest temperature I’ve seen after a long set of QSOs was 136° F.) Supermon was properly set up on the unit.
I installed AllScan from the bash shell without much trouble. I did have to enable sqlite in the php.ini file and reboot (I previously documented this) to get AllScan up and running. AllScan does put a bit more load on the PiZero but it seems to be handling it. I’ve detected no hiccups in how it operates in the handful of hours I’ve had it running on my desk.
AllScan on node 588417, the SHARI PiZero
Just like my ClearNode, the SHARI PiZeroU (U for UHF) announces its IP address over the radio when it boots up. To me, the audio quality is better than the ClearNode because I don’t hear nearly as much interference in the audio. That makes me think I should upgrade the power supply on the ClearNode and add a ferrite. It couldn’t hurt.
I am very pleased with this little unit! Thank you, Kits4Hams!
4. Noisy Fan Replaced on RPi 4 Case
While I was traveling last week, my spouse texted that one of my Raspberry Pi devices was making noise. It turns out that the RPi 4 that powers my ADS-B Exchange flight tracking unit was the culprit, and specifically, the fan. The fan is mounted just inside the top cover of the CanaKit Pi 4 case.
When I got home, I confirmed that the fan was noisier than it had been just a few weeks ago. It looks like when I put things together, I powered the 5V fan on the 3.3V GPIO pin. I did this because running the fan on the 5V pin was noticeably loud.
I ordered a couple of new 30mm x 30mm fans from Amazon (affiliate link on the Support page), intending to use one as a replacement and keep one as a spare. This fan model claims it runs on 3.3V and 5V so we’ll see how it does.
The cooler kit includes two fans and several heat sinks
As an aside, I’m realizing that I order so much ham gear on Amazon that perhaps I should just refer to it as Hamazon!
5. Resource Pages?
I am contemplating whether to create some topical summaries to collect and condense some content. For example, a page on AllStarLink would probably be a welcome resource, especially if all of my editorializing was eliminated. These pages would have to be regularly updated. It’s always frustrating to me to find old, out-of-date advice on the net.
The primary focus for pages like this ought to be on answering the question: “What would this look like if it were easy?”
I would like to know if you think this effort would be helpful. Please post a comment or contact me directly. Thank you for your counsel!
For work, we’re going to start experimenting with developing some podcasts. We’re not ready to splurge on a big suite of specialized equipment, so I’m starting my experimentation at home, with equipment selected on inexpensive side of the ledger.
Microphone: Blue Yeti Nano with a furry windscreen muff.
Stand: A simple desktop stand with a shock mount for the Nano.
Headphones: Audio-Technica ATH-M20X Professional Studio Monitor Headphones.
If I go down the XLR microphone pathway, then I’ll need to buy an audio mixer. The Nano essentially contains a USB audio interface. Fingers crossed that it works well enough, at least in the beginning.
I looked and looked at microphone arms but none of them looked like they would work quite the way I wanted. The desktop stand with a weighted base will be good enough for now.
Headphones are always a gamble for me because my head is not as large as some headphones are built for. Again, fingers crossed.
For software, I’ll simply use Audacity for now and see how my practice recordings go.
7. Following Up
The NOMAD Heltec V3 meshtastic device by PacificNorthWest3D has been a solid performer. The Etsy store owner, Zach, wrote a couple of notes on my invoice. Zach noted I was “the first customer to buy the NOMAD since being published one day ago” which was a great surprise. I guess that means I have unit #1! I always enjoy the personal touch that some sellers include. This is part of what makes amateur radio such a great hobby.
Thank you, Lynn, for buying me a cup of coffee! That was a delightful surprise after spending a couple of days tending family gravesites in Pasco, Kennewick, Dixie, and Walla Walla. Also thank you to the couple of hams who purchased items using my affiliate links. I very much appreciate your support.
This is another week “on the road” for me so the content feels a bit light, but that is before I start writing, so maybe by the end of this newsletter the content will be just fine.
My SilverSurfer node is working great. I used it over the Memorial Day weekend from a hotel in Pasco, Washington. The hotspot I used to connect it to the internet has a great feature: an Ethernet port (that’s why I bought the Inseego MiFi X Pro hotspot). I was able to tether the node directly to the cellular hotspot rather than try to connect it to the hotel wifi. (Tethering to a smartphone with a USB-to-Ethernet adapter might be a cheaper way to accomplish the same thing.) By the time you read this, I will have used it in a hotel in Ellensburg, too. In that space, I intend to connect it to a small travel router and use the hotel’s wifi. I’ll write about that next week.
A new Shari node is being shipped. Before the SilverSurfer, I had ordered a PiZero node from Kits4Hams. Over the weekend I was notified it was ready to ship so I paid the invoice. Comparing this node with my ClearNode and the SilverSurfer will be interesting. The PiZero node should arrive before the next newsletter goes to press so expect a few photos and remarks on this device. I’m excited at the prospect of a compact, durable node that “just works.”
My second Yaesu FTM-300DR is giving me looks, wondering why I haven’t connected it to WIRES-X yet. Soon, little radio, soon! As I type this, I’m quietly reviewing the configuration manual for WIRES-X while sitting in a meeting.
While traveling through a more remote part of Washington State, I had my radio tuned to 146.520 MHz. The calling channel is usually completely silent in this part of Washington. All of a sudden, a booming signal came in. I responded and we had a quick QSO while each of us was traveling at a separation rate of about 140 MPH. This, in a mountainous reservation, 30 minutes from any kind of cell signal. The other driver saw my antenna and called out. That was a delightful surprise. I wish this kind of thing happened more often.
When I’m near repeaters I know and like, I listen in. While traveling through and away from Portland this week, I was bouncing between the W7RAT repeater on 440.400 MHz and the national calling channel 146.520 MHz. I checked into the Puget Sound Repeater Group’s 9 am net through the W7RAT repeater and then switched over to 146.520 and was surprised to hear Michael W7RAT on the air…from Austria. It was morning for me and evening for him. He was remoting into his station to visit with folks in the Portland area. I had a very pleasant QSO with him and thanked him for the W7RAT repeater. Michael has quite the amateur radio history as described on his QRZ page. Status of his IRLP node on the W7RAT repeater is available at http://www.pdxirlp.net/. Thank you, Michael!
And a first for me was hearing a CQ on 146.52 MHz from a station identifying as “maritime mobile.” I responded while driving from eastern Washington to Portland and had a very pleasant QSO with Jacob. He was calling from a riverboat on the Columbia River. I’m not sharing his call sign here since he is far from home and enjoying his river cruise. These encounters with hams I’ve met before are wonderful while I’m on long road trips and I thank every ham who monitors 146.52 MHz while mobile.
PRO TIP: When you have many devices that use electrical adapters like wall warts and inline bricks, label them. I have a Brother P-Touch label maker that I pull out whenever I get a new device. Even the chargers for the rechargeable vacuum cleaner and the electric bicycle are labeled. I also label programming cables for various radios. The label maker has saved me a lot of grief.
2. Array of Meshtastic Devices
My array of Meshtastic devices continues to grow. I took the H1 and the TerraNode on my road trip this week and both performed well. The TerraNode stayed in the pickup truck and the H1 was clipped to my briefcase.
The smallest of my Meshtastic devices arrived last week. It is small enough to clip to a belt loop. This one is destined to be my everyday carry node. Shown below is the H1 by @Muzi.Works. It is available on Etsy. I added the small carabiner and split ring to make it easier to snap onto a pack or belt loop.
H1 device is quite small
If you’re curious whether there are Meshtastic nodes published near you, visit the MeshMap and see what gives in your neck of the woods.
The H1 is a very small device
Simon — the H1 maker — will soon be opening his own online store at http://muzi.works. In the meantime, that link will redirect you to his Etsy store.
3. Meshtastic T-Beam Supreme
3.1 Changing from client to router broke it
While fiddling with some settings on my T-Beam Supreme by LILYGO, I managed to mess it up. I had changed it from a CLIENT to a ROUTER and found I could no longer connect to it by Bluetooth or by USB cable. The screen remained blank. I finally concluded I needed to remove the power, but with an internal 18650 battery, that meant opening the case and removing the battery. Once I did that, I made sure I was pressing the correct button while I inserted the USB cable to make sure it would go into programming mode.
(Later, I found a note in the Meshtastic Configuration Tips page that speaks to this particularly instability. Of course, being “he who breaks things,” I discovered this tidbit after breaking the node!)
3.2 Flashing fresh firmware
I knew it worked because the Flasher (https://flasher.meshtastic.org/) then saw my T-Beam Supreme. I selected the target device (T-Beam S3 Core), the firmware (2.3.4ea61808 Beta from the Stable channel), and hit the Flash button. (I have to say that flashing firmware using a web browser and a serial cable is surprisingly pleasant. I don’t have to load a special program and I don’t need to keep that program updated. The hardest part is figuring out which port the serial cable is using. Cue the Windows Device Manager for that!)
Flasher screen
This time, the process worked. I erased the old firmware and replaced it with the 2.3.4 version. Once that was done, the T-Beam screen start working again. Whew.
I quickly reconfigured the long name to my call sign with a number after it. Since this is my most powerful Meshtastic device, I named it KJ7T-0, intending to use it most of the time as a fixed Meshtastic station.
3.3 Configuring the node over WiFi
I learned another trick that had eluded me: how to connect to the Meshtastic node over WiFi. Every time I’ve enabled WiFi in the node settings, I’ve lost the Bluetooth connection and could not reach the node over my wireless network. The problem, as usual, was with me. I found a YouTube that explained how to do it and naturally it is very simple: just type the IP address of the node in the browser window.
With that key piece of intel, I was able to connect to the node over my LAN and go through the rest of the configuration options very quickly (WiFi being much more responsive than Bluetooth). The YouTuber above noted that finding the IP address of the node isn’t obvious. However, I found it very easily by scrolling through several screens on the device.
Network settings for Meshtastic device
Once you have the IP address, you can open the Meshtastic client screen in your web browser. I used both Chrome and Edge to do this.
Node configuration over IP
To go back to seeing the node in the Meshastic app on your smartphone, disable the WiFi radio on the node and hit the save icon in the upper right corner of the node configuration screen. That reboots the node.
While going through these steps, I discovered that the node was still had WiFi enabled. I was able to connect through the Meshtastic phone app by connecting through the app with the node’s IP address. Then I disabled WiFi in the app and saved, the node rebooted, and my Bluetooth connection was restored. I want to use Bluetooth to extend the battery life compared to using WiFi. I also disabled the GPS for now to reduce energy consumption.
Lots of learning with this node!
3.4 Environmental data reported
While I was fiddling with it, I also enabled the Environment module. The information is not particularly useful but it is interesting to consider how one might connect other environmental sensors and have that data reported over the mesh.
Environmental data reported on node
4. Hamword
I am not very accomplished at this Wordle-like game! So far, I have six wins and one loss. Click here to jump to the Hamword site and learn about playing this game via Winlink. For me, this usually means running Winlink Express on my PC. Rarely do I hook up my VHF radio and use Winlink over RF. Nevertheless, I have my Winlink-in-a-box package ready to go at all times.
Tom’s Hamword performance
I learned that an inadvertent extra space after a five-letter word causes the guess to be rejected. It doesn’t appear as if the guess was counted as wrong, rather, it was rejected for having more than five letters. The space counted as a letter.
This week, one person got the Hamword in the first guess! To borrow an exclamation from The Princess Bride: inconceivable! It took me four tries to guess the word.
Each Memorial Day weekend, family members gather to tend gravesites in several cemeteries. For me, it’s about a five-hour drive each way to get there. In years past, several generations of extended family would gather for a reunion, but a few years ago, the family members who had been organizing this event kind of ran out of steam. None of the rest of us felt we could do it, either. (However, I begin to wonder if we should try for a reunion every five years or so. That might be worth doing!)
Dad was a World War II veteran. He had been stationed at the Army base on Adak Island in the Aleutian Island chain. One of our favorite family stories was of a letter he wrote to Mom while stationed at Adak, with lines that demonstrated his dry wit: “Having a great time. There are beautiful women behind every tree on the island.” At that time, there were no trees on Adak Island! (Some reforestation has been attempted, says Wikipedia.)
This year the tending of the graves and sharing of meals were enjoyable moments. It was good to spend time together, honoring those who came before us, and in so doing, remembering how much they continue to mean to us.
L to R: Sister-in-law Heidi, sister Sandra, me, my wife Janis, and brother Eric
Some relatives are veterans. My brother Eric brought flags for them. We cleaned up some neighboring gravesites, too, that usually don’t get much attention.
For this Memorial Day, I offer this original haiku:
Memories of all
Who paid the ultimate price
For our liberty
What a busy couple of weeks! I got a bit behind on my radio hobby while traveling so much but am starting to catch up. Please share this newsletter with like-minded amateur radio friends, and thank you for being a Random Wire community member.
Thank you for reading Random Wire℠. This post is public so feel free to share it.
I took a chance on a new, tiny device that plugs into a Raspberry Pi to create an AllStarLink node. This little fellow is the HotSpotRadio-USB or HSR-USB.
I am using this on a Dell Wyse 3040 thin client platform running Debian 12. To install to the 3040, I used GitHub instructions and files by Allan Nathanson WA3WCO. After the install, I did encounter a permissions problem with the AllScan install (part of Allan’s package) which was easily resolved by changing permissions on the /var/log/asterisk directory (sudo chmod 755 /var/log/asterisk). By the time you read this, it’s entirely possible Allan will have corrected that in his install files.
With regard to the HSR-USB device itself, I struggled for days with it. It would receive audio and send it to my handie-talkie but it wouldn’t hear my HT. Helpful advice in the active Groups.io community got me halfway there but it still wasn’t working for me. Finally, I did a complete reinstall of the operating system and AllStarLink. With one small change in the /etc/asterisk/simpleusb.conf file, the HSR-USB device worked fine. The solution was setting ctcssform to ctcssform=no.
My HT is set to transmit a 67 Hz CTCSS tone. No tone is required on receive. The radio frequency is 439.0000 MHz.
The audio quality seems to be as good as my ClearNode. I can’t opine on the durability of the HSR-USB but I think this small device is going to be a regular part of my travel kit. I particularly like the way the case looks and feels like a miniature C4Labs case. It’s a clean build.
If you have a spare 3040 device or a relatively recent Raspberry Pi platform on hand, I don’t think you can go wrong with this $96 product to create an AllStarLink node.
I’ve shared before that I lean toward open source software. That doesn’t mean I won’t use software that is less than completely open source. If the tool works and I have confidence in both the tool and the support behind it, I’ll use it.
AllStarLink is a wonderful open-source tool and the community support behind it is strong. I have little reason to stray from that path, except…I do like some of the capabilities built into the HamVOIP system. To be clear, my first node was a ClearNode which is built around HamVOIP.
The HSR-USB discussed above was designed to work with HamVOIP but it works just fine with AllStarLink, too. I am noodling about picking up a Raspberry Pi 3B+ or an RPi 4 and using the HSR-USB device to make a relatively compact package with wifi built in.
I’m also thinking about building a desktop version with a touch screen, using the Adafruit Smarti Pi Touch Pro platform. That, with AllScan installed on the RPi, would make a great desktop node that should allow for easy switching between nodes. I have a touchscreen somewhere so perhaps I should try this first to make sure the idea works before plunking down some cash for parts.
I have a built-for-me Shari node on order, the SHARI PiZero from Kits4Hams.com. I submitted my order just over a month ago so I expect it will be going into production in the next couple of weeks. My plan is to make sure it works the way I expect, then use it as a working model to help assemble one of their kits.
2.1 SilverSurfer has arrived!
On Monday, I responded to a QRZ advertisement for a Shari node and pulled the trigger on a VHF model. (All of my RF-based nodes are on UHF frequencies, and since I get a lot of interference at my Portland, Oregon location, perhaps a VHF unit will resolve that issue for me.) This node is built on an RPi 3B+ board with a Shari PiHat, heatsinks, and a cooling fan. The RPi 3B+ has dual-band wifi onboard so I won’t need any external dongle to connect to my wifi network. This will be node 588419 and with this node number, I’ve exhausted my expansion of NNX numbers for 58841. I’m very interested in how this will perform.
The photo below is of the VHF node as depicted by the maker, Rudy N6DOZ. This is a relatively compact, all-in-one build. He calls it a SilverSurfer. I anticipate it is going to be a great device.
Shari node built by N6DOZ (photo used with permission)
UPDATE: Rudy’s Silver Surfer arrived just before I took off on another trip this week. I removed it from a very well packed box, unwrapped it, plugged it in, and within a minute I was on the air. Well done, Rudy! This has been the easiest of all my nodes so far. I am very happy. Here are some quick snapshots:
SilverSurfer removed from box
SilverSurfer unwrapped
SilverSurfer ready to operate
SilverSurfer operating
As I type this, I’m listening to the Puget Sound Repeater Group’s 9:00 pm net on Wednesday evening. I’m hearing less radio frequency interference with the SilverSurfer. It is my only node that operates on VHF instead of UHF.
It worked immediately upon plugging it into my home network. When I unplugged the Ethernet cable, it switched over to wifi very quickly. I am tickled with this device.
I added AllScan to the software running on the SilverSurfer, following the routine specified by David NR9V on his GitHub site. The only hiccup there was having to uncomment a couple of lines in the php.ini file and restart the node. David covers this special case for HamVOIP just below the installation instructions on the GitHub page. AllScan makes it very easy to connect and disconnect from other ASL nodes and keeps your favorite nodes front and center. Very convenient.
AllScan running on node 588419
3.0 Meshtastic Devices
3.1 NOMAD Meshtastic device
A new Meshtastic device arrived last week. It’s smaller than a credit card in length and height, and thicker than a deck of playing cards. So far, it works just as well as my larger node but the battery life is shorter. This small node has a flat 2,000 mAh LiPo battery with a claimed battery life of 10+ hours. I’m not getting that kind of battery life from my unit.
My larger node has an 18650 lithium battery in it. I’m guessing it has an actual capacity of about 3,500 mAh. I can run it all day on a charge.
TerraNode - Complete Meshtastic device
I received great help from the Etsy seller when I first received the TerraNode device.
Battery inside the TerraNode device
Both units use the Heltec V3 module and neither have GPS on board. Wifi is not enabled on either unit. The key difference is the battery capacity.
But wait, there’s more! I expect to receive another pre-built node before this edition of the Random Wire goes to press. It will be even smaller with a 1,200 mAh internal battery. Based on what I’ve learned about battery life, I’ll probably have to disable some functions on this tiniest node (so far) to keep it alive all day.
UPDATE: The Supreme board arrived and I’ve put the node together and booted it up!
Assembly instructions are available at the Rokland.com website. The tiny IPEX antenna connectors are a bit fiddly and I found them a little hard to see with my normal reading glasses. Rather than raid my wife’s sewing kit for the flip-down magnifying visor, I just pop another pair of reading glasses over the first pair to achieve more magnification. It looks silly but it works great.
I’ve not taken it outside yet to make sure it picks up GPS signals. If it doesn’t, I’ll open up the case and make sure the wire to the GPS antenna isn’t pinched and the IPEX connector is properly seated. I have to say the tiny control buttons are also quite fiddly. I may remove them and just use a ballpoint pen tip to activate the buttons.
3.4 Club chats via Meshtastic?
While monitoring chats on the default LongFast channel, I’ve been wondering about the usability of creating a club channel. It might not be particularly practical, but considering that it is radio, it is likely something a small group would enjoy using. I’ve tested my Meshtastic nodes across the east-to-west length of Oregon and Washington and have been surprised at how well they are able to communicate with distant nodes.
To this end, I’ve also ordered a node from the TerraNode maker (LayerFabUK) that features a rotary encoder. What will that do? I can pre-program some responses into the node and by selecting a response with the rotary encoder, I can communicate basic information without needing to be connected to my cell phone. Seems like genius to me.
For several years I’ve been thinking about an APRS node powered by the sun and magnetically adhered to the roof of my vehicle. Meshtastic might be a little easier to try this with so I am visualizing a roof-mounted mobile node for my truck in the future!
4.0 In other news
4.1 ThinkStation server bit the dust…or did it?
I got back from a week of work-related travel to find my ThinkStation computer would not boot up. We must have had a power bump that reset it. I don’t have it plugged into my UPS because it draws too much juice for my little UPS device. When I tried to boot this headless computer up, all I got were activity lights and two beeps.
Two beeps on one of these Lenovo platforms could mean several things, among them, a POST error or a RAM error. My guess is my CMOS battery is getting weak. I turned it off and let it rest overnight, then hooked up a keyboard, monitor, and mouse and powered it up. It booted right up after that nap.
I’ll have to open it up to identify the CMOS battery it needs, then buy a spare to have on hand, just in case. In reality, if I’m going to pop the cover, I’ll find a battery and replace it rather than wait for the system to die. I’ll also make a backup/recovery USB stick for this thing, because my old friend Justin Case might show up again.
This computer is a beast: a Lenovo ThinkStation P510 E5-2690 V4 with 14 cores and 64 Gb of RAM. It is operating as a file server (primarily a backup target for more than a dozen machines) and is running WordPress in an Oracle VirtualBox virtual machine. I’ve been watching the CPU and RAM usage during active backups, and even with WordPress actively serving up pages, it isn’t breaking a sweat. I think the number of cores and the healthy amount of RAM make that possible.
4.2 Had another birthday
I stopped counting forward when I turned 50. Now I count backwards. That means this is my 32nd birthday…again. I’m certain you math wizards can figure out my biological age. I prefer my “counting backwards” age!
4.2.1 Wireless Android Auto device
I got myself a couple of devices for my birthday. The most practical of them? A Motorola MA1 Wireless Android Auto Car Adapter (affiliate link on the Support page). This Bluetooth dongle lets me connect my Android phone to Android Auto in the pickup truck without having to connect and disconnect over and over again a USB cable. This is proving to be a wonderful change and it has, so far, worked very well indeed.
4.2.2 New computer keyboard
The other practical item was a new keyboard for the computer I use the most. Most of my work is done on a Lenovo ThinkPad X1 laptop which rests on a stand on my desk (affiliate link for the this sturdy stand on the Support page). My old Logitech keyboard has started to have trouble with a few letters, by which I mean I have to really pound those keys a few times to get them to work. Keyboards are a tactile thing so the one you pick is a matter of personal taste. I don’t like loud, clacky, mechanical keyboards, but I also don’t like silent keyboards with no “spring” in the return of the keys after typing on them.
In my journey through Best Buy, I tried every keyboard multiple times and finally settled on a Logitech Signature Slim K950 Wireless Keyboard (affiliate link on the Support page). It is a slim design with a 10-key pad. It can be set up to work with three different devices and is compatible with Windows, Apple, and Chrome computers. It’s wireless so there is no cord to navigate around on my always crowded desktop. The best part for me is the keys have a springy feel to them and just the hint of sound as they are depressed. It’s a quiet, but not silent, keyboard, that feels just about right to me.
My family members appreciate me using a quieter keyboard because I tend to pound on my keys and I type quickly. That can be a bit disruptive to their harmony, especially when I’m “in the zone” and really hammering away on the keyboard!
I’m finishing up this Random Wire newsletter with the new keyboard and it is a pleasure to not have to hit the same key two, three, or four times to get it to register.
4.2.3 FreedomLINK+ 4G radios
I splurged on two FreedomLINK+ PG224 PoC/LTE Nationwide Portable Radios. What I was after was a radio I could leave on a shelf when I’m traveling, and be able to transmit to it and my spouse could reply (and vice versa). She is not a licensed ham and never will be, but radio is often the best way to make that connection when we are distant from each other.
I bought the white-and-red model because it doesn’t look like any other radio device in my suite of devices. These aren’t cheap devices but I am hoping they will fulfill my particular need. We’ll test them this week when we drive two vehicles to drop one at my son’s house.
I usually use a pair of FRS radios so we can keep in touch while we’re driving separate vehicles, but a few years ago that backfired on me. My wife’s vehicle had a sudden flat tire and she swiftly navigated across several lanes of traffic to a safe stop at a freeway exit. I did not react as quickly and my way across the lanes was blocked, so I kept driving to the next exit to make a loop back to her. I was quickly out of range of her FRS radio. She felt very alone on the side of the busy freeway. She did not have her cell phone and the low-power radio wasn’t reaching me. This incident is another reason I chose to try the FreedomLINK+ 4G radios.
As I perused the FreedomLINK+ product lines, I found myself leaning toward the FreedomLINK+ PW424 WIFI Nationwide Portable Radio devices but decided against wifi as the voice carrier. While the audio quality might be better over wifi, that solution doesn’t work when I’m on the road where wifi can be a rarity, unless I use my cell phone as a hotspot. For a city-to-city kind of connection, wifi would probably be viable. For the kind of travel I do inside one state and across the country, using 4G as the backbone made the most sense to me.
Personal note: As I review some past issues of the Random Wire, I am recognizing something I had not really verbalized before: if it has to do with radio, I’m all in! Amateur radio is my hobby of choice but I like radio in all of its manifestations. It doesn’t have to be something within my amateur radio license to be interesting.
This is a shorter Random Wire Review. I’ve been on the road for work all week and have had little extra time to delve into amateur radio topics and activities. I’ll have at least two radio topics next week: configuring my Yaesu FTM-300DR as a Personal Digital Node, and a few more Meshtastic devices to get to know.
As an aside, I’ve been running a Meshtastic node in the vehicle while I drove from Portland, Oregon to Pullman, Washington, and back. I wanted to see how well it worked as a tracker. Surprisingly, it appears to be about the same, generally speaking, as running APRS on the Yaesu FTM-300DR radio. The limiting factor with Meshtastic is nodes that can hear my node. The limiting factor with APRS is digipeaters within range of my radio. Of course, running APRSDroid on my smartphone provides good tracking density because of more consistent cellular phone coverage.
Virtual Machines
It’s been a while since I dove into the world of virtual computers. My tool of choice was, and continues to be, VirtualBox. Why? Because I have a sense of familiarity and comfort with it. It may not be the best tool and I look forward to advice from readers about how I can “up” my game with virtual machines.
I loaded a VM with Debian 12 and WordPress, sourced from Bitnami. VirtualBox is running on my big file server. I’m finding that the many cores of the Xeon processor on that server make light work of running VirtualBox, and with this realization I’m pleasantly surprised.
To test WordPress in a VM, I downloaded my entire Random Wire archive and imported it into WordPress. That went pretty smoothly. Right now I’m looking at everything up to Random Wire Review 88 on the VM:
This gives me a platform to play with how the Random Wire might look if I moved to my own WordPress instance. I do have a “kinda sorta” copy running on WordPress.com at https://cupofradio.com/ but I can’t do as much customization of that site as I would like. Note that Cup of Radio lags the Random Wire site hosted on the Substack platform.
I’d also like to explore maintaining a Random Wire store. While Substack does allow authors to use affiliate links, that is an unsupported use of the platform, and Substack enforces some restrictions:
Substack allows content creators to include affiliate marketing links in their newsletters, with some restrictions. For instance, while creators can use affiliate links, it’s important to note that certain platforms, like Amazon, prohibit sharing these links via email. Consequently, Substack automatically removes Amazon affiliate links from email versions of posts to comply with such guidelines. This policy underscores Substack’s support for the monetization of newsletters through affiliate links, as long as they adhere to the rules set by external affiliate programs. For more specifics, one can refer to guidance on Substack and affiliate marketing links.
Currently, I keep a list of items with affiliate links on the Random Wire Support page. That way I don’t run afoul of Substack’s automatic removal of Amazon affiliate links from emailed newsletters.
Hosting a separate site for an online store makes a bit more sense to me.
The most likely scenario is I’ll use a VM to test a storefront and how much work it is to build and maintain. I can’t use randomwire.com for that as that domain is already in use. I do have randomwire.net so perhaps I could use maintain my branding by using that domain for the store.
WooCommerce is the big dog in the WordPress store space.
If you’re interested in pre-built VMs for VirtualBox, check out these links:
In addition, you can use Bitnami virtual machines in VirtualBox by going to File, Import Appliance.
INTERESTING: Meshtastic node blinded my key fob
I have the kind of vehicle key fob where I can walk up to my door, slide my hand inside the door handle, and it automatically unlocks.
I assume the key fob contains an always-on receiver because an always-on transmitter would quickly drain the button battery in the fob. That would mean the vehicle is always transmitting, and when the fob receives the correct signal and sends the proper response back to the vehicle, the vehicle will unlock. (A way to test this would be with an RTL-SDR. I might have to acquire one of these devices to satisfy my curiousity!)
It was a surprise to me last weekend when my door did not automatically unlock. I had my keys in my pocket along with my Meshtastic node. The keys were closest to my body and the node was between the fob and the vehicle. As soon as I removed the node from my pocket, the whole automatic door thing worked. I put the node back in my pocket and it would not work.
At first I thought the node and the fob might be on similar frequencies but that appears to not be the case. In the United States, key fobs are in the 315 MHz range. My Meshtastic node is running at 915 MHz.
Perhaps the small circuit board or the shielding inside the Meshtastic node was sufficient to reduce the signal strength reaching (or coming from) the key fob. It’s interesting to think about. If anyone knows what is really going on, I’d love to learn more.
After my first reaction of “that’s cool!” my second thought was: maybe a Faraday cage made from circuit board material would be a fun project!
As I begin to build this edition of the Random Wire℠, I’m conflicted. Sitting on my desk is the Spring/Summer HRO catalog. I have not opened it yet but I will do so when my writing time today is concluded.
I am recalling the wonderful feelings when, in childhood, the Sears Roebuck catalog would arrive. Even better was the Christmas catalog. I would pore over each and every page, top to bottom. The HRO catalog elicits that same sense of delight when it appears in my mailbox.
It is really rather silly, though, because I’ve seen almost everything in the catalog before. The content doesn’t change all that much, but somehow that doesn’t stop me from spending a few hours slowly flipping from page to page, not stopping until I’ve dog-eared some page corners and examined it from cover to cover.
This catalog arrival is made a bit more poignant by the news that MFJ is ending production. Whether you like MFJ products or not, there is no arguing the huge impact MFJ has had on our amateur radio hobby over more than half a century. For the sake of our amateur radio community, I hope that HRO can continue to be strong and stable.
1.2 Blogs.radio is a tremendous radio resource
The Random Wire is now included in the encyclopedic blogs.radio site! If you’re looking for a particular bit of information about an amateur radio topic, I can easily recommend taking a moment to run a search of blogs.radio.
2.0 YSF: Favorite Repeaters/Nets
As I continue my journey into the world of Yaesu System Fusion and WIRES-X, I have come across a couple of favorite services that host various nets. If you have favorite Fusion repeaters and nets, please share with the Random Wire community.
On my YSF-only hotspot running WPSD, I connect following these steps:
Click Admin in the menu bar.
Click on YSF Manager.
Click on the pulldown menu under Select Reflector.
Select XLX458.
Select Link.
Click Request Change.
(Wouldn’t it be nice to be able to script this process? I am imagining a short list of my favorite reflectors, each accessible with just one or two clicks. Maybe that capability exists and I’m simply unaware of it!)
Being an AllStarLink guy, I do wish they also had AllStarLink as a way to connect to their system but given the scope of connection methods listed above, I really shouldn’t complain.
In Portland, Oregon, I can participate in KC-WIDE conversations through the WA7BND repeater located on the delightfully named Stonehenge Tower.
KC-WIDE has numerous nets Monday through Friday, with a few on the weekend. The Fishsticksnet by David KE0DSV is always interesting, as is the Wake up! With Terri and Ray net by Terri KF0HFI and Ray KF0EBI. Jon KZ4JON facilitates good conversations on the Anything Goes net. I listen in, and occasionally participate in these nets, while I’m mobile in my pickup truck.
The tag line for Colorado digital Multiprotocol is “democratizing digital by bridging modes.” That’s a good summary of the powerful connectivity available through Colorado Digital.
I connect to the Colorado Digital reflector through XLX303. This is where I spend most of my time because one of my “home” hams runs a YSF repeater through the Colorado Digital system. My hotspot is configured to default to XLX303.
Various rooms are available through the Colorado Digital system. These are mainly accessed by setting the DG-ID on your System Fusion radio. For example, to reach the W7NEE repeater, I set the DG-ID to 12 and briefly key up. I can also connect via DMR and AllStarLink. I’ve found the folks on the Colorado Digital system to be very knowledgeable and helpful.
When I’m at home, I’m often connected to Olympia Mountain Digital via the W7NEE repeater using my hotspot or my desktop AllStar node. This repeater is accessible via WIRES-X (04429), AllStar (289802), Brandmeister DMR (314072), and XLX303 using DG-ID of 12.
As an aside, when I use the hotspot and FT3D radio, I usually have a Bluetooth headset on (TECKNET Bluetooth USB Wireless Headset with Mic) because the transmission beeps bother our dog. She runs and hides every time she hears the beep. She is a rescue who was a bit traumatized when we got her a year-and-a-half ago. Even though she is much calmer now, some things instantly trigger strange reactions.
NWFG is an online Radio Society of Great Britain affiliated club. As an online community, we make good use of Facebook Groups, Twitter, and YouTube to share information and knowledge, please use the links at the bottom of the page to access these.
North West Fusion Group operates a network of repeaters and gateways all connected to the NWFG room. This means we can offer superb coverage across North West England as well as enabling radio amateurs access to our infrastructure from anywhere with internet access via Wires-X room NWFG (44222) or a hotspot connected to our reflector YSF44222 (GB NWFG2).
We are primarily based in the North West of England but we do have members all over the world.
3.0 TECH TIP: Booting a Stubborn Dell 3040 Thin Client
Recently, I picked up a couple of relatively late-model Dell Wyse 3040 thin client machines that proved to be stubborn. I call them late-model because they use the newer 12VDC power supply. Older ones use 5VDC power.
After installing Debian 12 on them, I could not get them to boot. This is a well-known problem and usually I would address it by booting into Clonezilla on a USB drive. That did not work this time. I spent much of Saturday, May 4th fighting with the two 3040 units, unable to get Clonezilla to boot the machines. I installed Clonezilla to three different USB thumb drives, thinking that must be the problem.
Eventually, I found another way to boot the 3040 machines. Installing Debian 12 using the Expert Install option allows you to modify how GRUB boots the machine. In essence, when you get to the GRUB installation step, you choose to install in “removable mode” to make the machine bootable. This is explained in the Debian wiki.
What worked for me was choosing “Yes” to the question: “Force GRUB installation to the EFI removable media path?”
I chose “Yes” to the next question: “Update NVRAM variables to automatically boot into Debian?”
I didn’t capture every step of the Expert Install option but my key choices are shown in a Google Photos album at https://photos.app.goo.gl/P3rQuoknSpm2fFb66. Using the Expert Install process yields a bootable install without having to use Clonezilla to modify the installation.
3.1 WiFi adapters for the 3040
And in the good news side of the ledger, this small USB wifi dongle works with Debian 12 in the Dell 3040: Edimax Wi-Fi 4 802.11n Adapter for PC N150 Nano USB Adapter (link is on my Support page). It’s not the fastest device and only seems to work on 2.4GHz wifi, but it works.
Edimax Wi-Fi 4 802.11n Adapter for PC N150 Nano USB Adapter
Other adapters I’ve tried include the Edimax Wi-Fi 5 Nano 802.11ac AC1200 Dual-Band Adapter and the TP-Link Nano AC600 USB Wifi Adapter but they don’t work out of the box. I’ll fiddle with them later to figure out what drivers they need.
4.0 PROJECTS: What’s Ahead
4.1 Shari node (AllStarLink)
I’m having a Shari PiZero node built for me. At this moment in time, I think it is in the queue to be built in about four weeks. If it performs well for me, I’ll then order up a kit and build another one, using the pre-built unit as a guide. (I find that it helps me a great deal to have a visual reference, something I can touch and turn and peer at with a magnifier. This works better for me than reading printed instructions on a sheet of paper.)
My ClearNode has always exhibited some odd artifacts in the audio, sounding like interference. I thought it was my location but I’ve tried the ClearNode in several places and the interference doesn’t change. My test will be the Shari PiZero node. If I get the same kind of interference, then I’ll know it’s something I’m doing, not the hardware.
In any case, having a small, portable AllStarLink node is on my long list of desired bits for my radio kit.
4.2 HotSpotRadio-USB (AllStarLink)
I’ve got a HotSpotRadio-USB on order. For $100 it’s worth taking a chance on a USB device that plugs into a Raspberry Pi running AllStarLink. I’ve got a spare RPi Zero 2 W I’d like to put AllStarLink on, and combined with the HotSpotRadio-USB, this would make a relatively small package. I’m particularly interested in how the audio will sound.
4.3 Radtel multiband radio
I’ve got another radio on order. Here’s the title as listed on Amazon: Radtel RT-890 Multi-Band Ham Two-Way Radio 999 Channels 8 Band Long Range Handheld Walkie Talkie AM Aviation Band Reception Color LCD HT Transceiver Type C Frequency Match DTMF NOAA
Why? For one, I like to listen to air band transmissions. Two, I would like to have a radio that I use primarily for air band, and with the optional air band antenna I ordered, this should check that box.
Also, this is a not-too-expensive hackable radio so I’m looking forward to monkeying with it. Open source firmware is “out there” for the Radtel RT-890. For example:
I was leaning toward the Quansheng’s UV-K5 radio but is was the color screen of the Radtel that tipped me in that direction. If you’re interested in the Quansheng radio, an informative article on it is available at https://spectrum.ieee.org/quansheng-uv-k5-hacking and there are some recent YouTube videos available if you search.
4.4 Meshtastic board and case
I have a LILYGO T-BeamSUPREME Meshtastic ESP32-S3 TTGO Development Board on order. I also ordered a case from Rokland to fit and some spare 18650 batteries from Amazon.
I’ve fiddled with a few pre-built units enough to feel comfortable with trying to put together a node on my own. Last week, I re-flashed my T-Beam node a few times and finally have it running as expected but the 18650 battery is not taking a charge, hence the spare batteries on order.
5.0 MESHTASTIC: What is the Use Case?
5.1 Brief overview contrasting LoRa and Meshtastic
LoRa is a wireless modulation technique derived from Chirp Spread Spectrum (CSS) technology. It encodes information on radio waves using chirp pulses - similar to the way dolphins and bats communicate! LoRa modulated transmission is robust against disturbances and can be received across great distances.
LoRa can be operated on the license free sub-gigahertz bands, for example, 915 MHz, 868 MHz, and 433 MHz.
Think of LoRa as an abbrevation for Long Range. LoRa is the radio and the way the radio works. No license is needed in the United States on a typical Meshtastic band at 915 MHz. (Note that the quote above suggests that 433 MHz is in a license-free band, but 433 MHz is allocated to amateur radio use per the ARRL band plan.)
There is LoRa APRS which uses LoRa spread spectrum in the 433 MHz range to carry Automatic Packet Reporting System data packets. LoRa APRS is restricted to use by licensed amateur radio operators.
In short, Meshtastic on license-free bands is for everyone. By that, I mean you don’t need a license to operate one or Meshtastic devices in a license-free band. Operating a LoRa radio device on an amateur radio band requires an amateur radio license.
Meshmap of nodes my node sees
5.2 Example of APRS-like tracking with Meshtastic
As I source and build my T-Beam Supreme unit, I’ve been thinking about the potential use cases for a Meshtastic node. More than anything, it’s a radio device that invites experimentation and that, by itself, should be enough to interest many amateur radio enthusiasts. The long reach of this low-power system is also a bit mind boggling.
At the most basic level, Meshtastic provides the ability to chat over RF to other Mestastic nodes. I also tested how it might work as an alternative to APRS while I drove and it did a good job of reporting my changing location (my position is shown as “kj7t now”). I purchased my Meshtastic unit on Etsy.
Note that my Meshtastic node was using my cell phone’s GPS for location but not using my cellular service to send and receive data. This point bears repeating because even though the Meshtastic node is linked to my smartphone via Bluetooth, GPS data comes into the phone without using a cellular connection. That means the cellular network could be down and the Meshastic node would still be able to use the GPS on my smartphone.
In the three images below, kj7t now is moving from place to place and those changes are picked up by Meshtastic.
My Meshtastic node is powered by an 18650 battery. Here it is sitting beside my Yaesu FTM-300DR on the dashboard of my pickup truck which is running APRS in the B channel:
Meshtastic node beside FTM-300DR radio
In summary, tracking via Meshtastic seems like a viable adjunct, or supplement, to APRS tracking, so long as there are sufficient Meshtastic nodes within range of the LoRa radio to communicate data. The following video, titled LoRa Propagation, Range, Antennas, and Link Budget, provides a deeper dive into LoRa propagation:
5.3 Identification of possible use cases for Meshtastic
Here are the possible uses cases I came up with. If you have others, please leave a comment or drop me a note. Remember that on license-free frequencies, Meshtastic is available to anyone, no license needed. To me, this means Meshtastic could be a useful tool to help introduce people to radio, and thus serve as a gateway to amateur radio for some users.
Communicating on the trail or when in/around a remote camp.
Communications for remote communities where cell service is unreliable or unavailable
“Out of band” comms if cellular networks become overloaded or unavailable
No audio noise to disturb others
Better range than handheld VHF/UHF amateur radios
Efficient battery usage
License free, so it is potentially available to more people
More resilient in the presence of radio frequency interference
Can improve line of sight by hoisting a lightweight node into a tree
You only need line of sight to another node that can connect to other nodes to reach your intended recipient
Nodes create a self-configured (and thus a self-healing) mesh network
Cost is low compared to purchasing radios and becoming licensed
Opportunities for experimentation
You might make some new friends
Meshtastic can transmit data from sensors
This last point is particularly interesting to me as my sailboat is 135 miles away. I’d like an inexpensive way to keep tabs on the interior temperature and humidity, and even rig a water sensor to let me know if the sump pump fails. Being able to set up one or two nodes to report these data to a node in my Olympia office would ease my mind.
Perhaps you have an RV in storage and want to monitor inside temperatures during the winter. Meshtastic might come to the rescue for you.
5.4 Meshtastic in the context of PACE emergency communications
Few of us probably want to use Meshtastic as a primary means of communication, day in and day out. It could fall into the alternative or contingency categories, especially if primary communication mechanisms fail. For those of us who live in the Pacific Northwest where “the big one” could happen anytime, keeping PACE in mind might be a lifesaver…and if not for you, perhaps it could contribute to saving someone else.
While I’m not a prepper, I like the idea of a network of meshed nodes, powered by sunlight and batteries, as a means of communication if the unthinkable happens in our lifetimes. APRS fills this space for me, too.
Meshtastic seems like a reasonable alternative, or supplement, to using APRS as long as there are other nodes that can hear your node. I look forward to testing this on one of my cross-state trips coming up later this month.
6.0 CLOSING NOTES
6.1 Waiting on WIRES-X
I’m still waiting for my WIRES-X registration to be approved by Yaesu. As this issue goes to press, it has been six weeks to the day since I first submitted my registration. Two weeks ago I re-submitted my registration, and this time I got an acknowledgment of submission, something I didn’t get with the first submission. That makes me think the first submission didn’t really go through. Once I get through the process, I intend to ask Yaesu what the standard workflow is to approve a registration as that kind of information would be helpful to those of us who attempt this process.
I received my node ID and room ID from Yaesu on May 7th. The takeaway from my experience is: make sure you receive an acknowledgment of submission. If you don’t, then perhaps your submission didn’t make it all the way to Yaesu.
I don’t think I’ll have time before this issue of the Random Wire goes to press to set up the Yaesu FTM-300DR radio on my desk as a Personal Digital Node. I should be able to report on that next week. I will be setting this up without the HRI-200 WIRES-X interface.
6.2 WTB: Ten-Tec Scout
I had a line on a nice-looking Ten-Tec Scout transceiver with mic and power cord. I found it on a Craigslist posting and reached out to the seller. Everything was going smoothly until I mentioned I preferred to pay by PayPal and he responded that he wanted a check or a Western Union wire. That was the moment when red flags popped up in my mind. When he said that was all he would accept, that was the trigger that caused me to terminate the conversation.
I’m still in the market for a nice Ten-Tec Scout to go along with the one I already have. I’m also watching for a Ten-Tec Argo, the 10-watt QRP version of the Scout. There is a special kind of joy in operating a very simple radio and I just like the ergonomics of these Ten-Tec units. I’d be just as happy to pick up a Ten-Tec Argonaut VI 539 QRP rig if one becomes available.
1 — QUICK NOTE: Ham Radio Workbench on Coaxial Stub Filters
Given my frequent two-hour-long drives, the Ham Radio Workbench podcasts fill the time for me, bringing me enjoyment and learning. The most recent episode, though, is fascinating. I am finding HRWB 207 - Coaxial Stub Filters and Portable Operating with Daniel Winn WV1T to be a fascinating podcast. I had not thought much about crafting coaxial stub filters to help reduce interference in my apartment. There are some informative links in the show notes for HRWB 207 that will prove helpful if you’d like to learn more.
One of my radio friends runs a Yaesu System Fusion repeater that is bridged to DMR and to AllStarLink. My plan is to record audio over my dedicated-to-YSF hotspot through either my FT3D or FT5D radio, and over my dedicated-to-DMR hotspot through my AnyTone AT-D878UVII Plus radio, and over my desktop AllStar node #588412. If I can align my travel with some transmit time, I might also get an audio sample of the repeater locally over RF through my FTM-300DR in the pickup truck. And when (if?) I finally get my WIRES-X registration so I can finish setting up my second FTM-300DR on my desk, I can grab some audio from that platform, too.
I think it will be interesting to hear the differences between these various ways of accessing the YSF repeater.
Meshtastic
I have a few Meshtastic devices but I’m floundering. I set up one but it isn’t working quite the way I expected, and every time I power it down and then bring it back up, it doesn’t remember any settings. That can’t be right.
To advance, I find that I’m doing what I did with hotspots: I’ve ordered another pre-built device, and I think that’s going to lead me down the path of putting my own devices together. The device I purchased through Etsy is coming from Scotland and uses a Heltec board with GPS. Fingers crossed it makes it across the big water and all the way across the United States in fine shape! I’m looking forward to learning more and sharing that knowledge with you.
After digging through my parts bin, I found a few more old Dell Wyse 3040 thin client computers…but they have problems. One is configured as a backup to my desktop AllStar node #588412 but the password isn’t being accepted. I’ve gone through my list of usual suspects and nothing is working, so I’m going to start over on that unit.
The other 3040 has a bad power switch. Sometimes it works and sometimes it doesn’t. I’ve ordered up another 3040 with 16 gigabytes of storage built in so that I have a good platform for experimenting. At some point, I may need to bypass the bad power switch on the other unit.
Electric bicycles
I recently picked up a couple of electric bicycles. These are new to me so I did not spring for expensive units. We’ll see how well they work. My wife’s bike is a single speed with only a 350-watt motor. I selected a simpler, underpowered bike for her because she doesn’t want to fiddle with gears. My bike is bigger with fat tires and a bigger motor. When I tested it, I realized I’m going to have to be careful with it because it accelerates pretty darn fast!
Both bikes appear to use banks of 18650 batteries for power, something most of us in the amateur radio world are familiar with. I don’t plan on writing about the electric bikes here unless folks want to hear about our learning curves with these two platforms.
3 — NETWORK: LinkStar H68K-V2 OpenWRT Router
I teased this device in Random Wire Review 87 as the LinkStar tiny router. It arrived this week so I stayed up late one night to get it configured.
LinkStar H68K unboxing, quarter shown for scale
The LinkStar-H68K-1432 V2 – $99 from Seeed Studio – is a robust little device. When I unpacked it, I was surprised by how hefty it felt. My anticipated use case was to plunk this into my travel trailer, but I think it’s going to be a regular part of my home network. I can use lighter devices for an RV router. The stout construction, small size, and the multiple operating system options are what attracted me to this device.
The vendor describes the LinkStar as follows:
LinkStar-H68K-V2 router equips quad-core Cortex-A55 RK3568 chip, featuring 4 Ethernet interfaces for dual-2.5G and dual-1G, along with Wi-Fi 6 technology, while providing high storage capacity and media player functionality, functioning recommended for indoor use. Compared with the first H68K generation, it not only has better communication and heat dissipation effect, but also the interface layout is more reasonable and convenient.
LinkStar box top
It arrived without a TF card. After digging around online, I found an OpenWRT router package for it on the Seeed Studio wiki. I downloaded and installed it on a SanDisk microSD card with Balena Etcher to fiddle with the device a bit. Eventually, I pulled the microSD card and installed the package directly to the 32-gigabyte eMMC card inside the unit. More on this in a moment.
These exterior views come straight from the Seeed Studio website:
Living up to my reputation as “he who breaks things,” I opened it up to take a look at the innards. The two heatsinks are affixed with just the right amount of thermal paste, and the heatsinks are pretty large for a single board computer.
LinkStar with cover removed
I am powering the device through the one USB-C port and have a network cable in the ETH0 port connected to a spare port on my GL.iNET Flint 2 router. (I note in passing that my Flint 2 router appears to run OpenWRT in a somewhat customized interface, so what I learn from the LinkStar may directly apply to my home router.)
Getting OpenWRT running on this little beast proved to be a bit finnicky. The installation instructions required more than one download. I’ve played with single board computers with eMMC cards before and had some trouble, so I was a bit hesitant to load the eMMC card on the LinkStar. Sure enough, it didn’t work perfectly the first time through the steps but that was because I accidentally skipped on step. Once I carefully followed the steps in the wiki page, the installation proved successful.
The default configuration screen is accessed at 192.168.100.1, an address that falls outside the range of my home network. I ended up disabling my Ethernet interface on my laptop, instead using wifi to connect to the LinkStar. That worked fine.
The default login credentials are root/password. You can see the default IP address in the browser URL space:
OpenWRT login screen
OpenWRT provides a ton of detailed information. This is not a plug-and-play router solution. If you like to dig your fingers all the way to the bottom of the pie, OpenWRT will let you revel in the details.
Status overview screen
The LinkStar, running OpenWRT, is sitting on my router and modem shelf. I’m going to let it “burn in” for a few weeks to make sure it remains stable.
UPDATE: The unit has been running for several days around the clock. I’ve enabled Adguard Home on it to help block excess ads. The speed test on the left is through the new LinkStar unit. The speed test on the right is through the GL.iNET Flint 2 router. Both results are quite comparable and respectable for Xfinity cable internet in my neck of the woods.
4 — TIP: Fixing a Stalled Upgrade on the Raspberry Pi Zero 2 W
As I was working with a new RPi Zero 2 W this past week, I ran into something I’ve not encountered with other RPi builds. When I ran sudo apt update in a terminal window, all was well, but when I followed up with sudo apt upgrade -y the upgrade process would not complete:
Upgrade stalls
Granted, there were a lot of upgradable files available, but I was stumped for a bit as to why the upgrade process would freeze.
Upgradable file list
I spent a few hours searching the interwebs for answers. As you can imagine, there were several suggested fixes. The one that made sense to me involved increasing a cache limit so I gave that a try:
The Pi Zero 2W has 512M of memory and you may not have enough swap space to do the update.
From a Terminal window, enter the command "swapon". The answer gives the file name, size, and usage of the swap file. The default swap file size is 100M and that probably is not sufficient with 512M memory.
Edit the file /etc/dphys-swapfile and change CONF_SWAPSIZE=100 to 1024. Reboot and then before doing anything enter the command "swapon" in a terminal window to see the swap space usage.
So: sudo nano /etc/dphys-swapfile to change the swap size limit, save, and reboot. That worked perfectly when I ran the upgrade again.
5 — FOLLOWING UP
Flight Tracking with a Raspberry Pi
Regarding the article Flight tracking with a Raspberry Pi, reader Adam K4SPB noted that “if you already feed to one of the services it’s easy to add and upload to the other major ones on the same device.” I did not know that but now I do. I spent some time this week looking into adding a feed for FlightAware to my device. After much thought, I’ve decided not to do this. The feed for ADSBExchange seems good enough for me. I appreciate Adam’s feedback as it presented an opportunity to learn more about flight tracking!
WIRES-X
Several readers reached out to me about getting registered for WIRES-X. Based on what was said to me, I have to say that the registration process appears to be very inconsistent. Some people were successfully registered within a week or two and others have had extended wait times to get registered.
After waiting a month, I repeated the registration process. Interestingly, as I completed the registration form (again), when it got to my email address, there was someone else’s email address already entered into the form and I could not change it. Pausing to consider this, I decided to start over with a completely different browser, using Edge this time.
Unlike my first registration a month ago, this time I received an acknowledgement of submission from Yaesu within seconds:
Part of my frustration has been that I did not get any confirmation after submitting my registration the first time. The notice received when starting the registration process doesn’t mention watching for a confirmation email after submitting the completed registration form. That would have been good information to have, since I did not received that confirmation email with my first registration.
Fingers crossed that it works this time. I’ve got a new Yaesu FTM-300DR and cables sitting on my desk, waiting for my WIRES-X registration to go through. I intent do use the radio as a personal digital node (PDN). Click here to get the special WIRES-X manual from Yaesu in PDF format.
6 — PARTS BIN: Ten-Tec Band Modules Found
I finally found my bag of Tec-Tec band modules for my Ten-Tec Scout. This 10 to 80-meter transceiver is rated to 50 watts of output power. I have a power lead for it but misplaced my plug-in band modules…until this week! I’m looking forward to getting this old rig on the air this summer.
For the record, I’m also watching various websites for Ten-Tec Argonaut QRP rig in good condition. I have an Omni-D transceiver I’ve never fired up. I wonder if it still works?
A reader opened a new account with Mint Mobile and another purchased some items from Amazon using my links. Thank you very much for your support. I appreciate it, and it helps.
I am getting much more enjoyment than I thought I would as I monitor air traffic near me and in other parts of the country. This project is a keeper for me. Below is a screenshot of air traffic over Washington State at 9:15 am Pacific on April 23, 2024.
I will be including Amazon Affiliate links, but not in the newsletter. They will be published on my Random Wire support page for some items discussed in the Random Wire newsletter.
I continue to not see the value in asking you to pay to subscribe. I think there is more value in providing opportunities for you to purchase some of the things presented in this newsletter. This helps to keep this newsletter free of charge.
If you do purchase a product through an affiliate link, I will receive a very small commission. The price you pay for the product is the same as the price without an affiliate link. This is an easy way to help support the Random Wire newsletter at no additional cost to you.
2 – Flight tracking with a Raspberry Pi
I enjoy watching what is going on up in the sky. During my February trip to San Diego, I spent some enjoyable hours using my Yaesu VX-6R to monitor radio exchanges between various aircraft and the San Diego Airport tower.
Now I’ve upped my game by pairing an ADSBExchange SDR dongle with a nice CanaKit Raspberry Pi 4 kit to watch air traffic around Portland, Oregon. (These items are listed on the Random Wire support page.)
Air traffic near Portland, Oregon
With a Raspberry Pi and the ADSBExchange dongle, you’re set to monitor local air traffic. By linking your data feed to ADSBExchange, you also get global access to air traffic. In their terminology, you become a “feeder.”
You can use FlightRadar24.com to monitor air traffic but access is rather limited unless you pay for a license. I like FlightRadar24, and honestly, the low subscription cost is less than what I spent for the Raspberry Pi and ADSBExchange dongle. But I also like fiddling with the technology, so I went with ADSBExchange.com. The map (as shown above) isn’t quite as nice looking as FlightRadar24’s map but it suits me just fine.
The CanaKit kit is a good one, complete with a power supply, heat sinks, and a fan.
CanaKit box top
My one complaint about the CanaKit kit is the black case. The shiny surface attracts fingerprints and smudges. Since I’m not handling it very often, I can live with that. The fitment of the case pieces is very good. The included cooling fan snap fits into the case lid.
Getting this set up couldn’t be simpler:
Setup instructions
The microSD card comes with the software you need already loaded. You simply insert it into the card slot on the Raspberry Pi, attached the ADSBExchange USB stick and antenna, and plug the power in. After a little bit of easy configuration, your device is actively picking up local air traffic.
Raspberry Pi and ADSBExchange dongle (USB stick)
Note that my device is not located outside — it is inside on a corner table. While I would undoubtedly get better performance if I could get the antenna outside, it seems to be working fine placed inside, near an exterior wall.
I did do the sudo apt update / upgrade dance on this unit. It had 130 packages ready to be upgraded, so I proceeded with upgrading. During the upgrade process, I noticed that rendering of air traffic was a bit jumpy.
I’ll close with one feature of ADS-B Exchange: you can filter for kinds of air traffic. In the image below, I filtered for just Military aircraft and noticed a couple of fighters flying in the southwest United States. Very interesting stuff.
Northrop fighters in SW USA
3 – Disappointment with WIRES-X
I write this note hoping that just like getting your car washed sometimes seems to stimulate rain, writing about it will create the magic that help my registration come through.
I am frustrated with the very slow registration process for a WIRES-X account from Yaesu. I submitted my registration on March 29 and as of this issue of the Random Wire, four weeks have passed. I’ve received no acknowledgement that my registration was received. Last week, I submitted a request for information through their contact form but received no reply.
I try to log into the WIRES-X page every morning in case the registration has been processed without notice to me, but the popup I get each time says “Not a valid member ID or password.”
I do like my Yaesu radios. I like how they feel and function. However, the incredibly slow processing for a new WIRES-X account is disappointing. Part of my frustration stems from my wish to write a simple “how to get started with WIRES-X” article, but I’m stymied by the slow processing of my WIRES-X registration. I need to experience it before I can write about it.
4 – LinkStar tiny router
This little guy is on order. I’m pretty excited to give it a try, either in the travel trailer or in my business travel kit. While I do have some small devices from GL.iNet that are quite capable, I like the idea of getting my hands dirty with OpenWRT.
I’d include a picture of this device except for one thing: every site that has a picture of it also has copyright notices posted. I’ll wait until I get it in hand and can take my own photographs for photos to share with you.
The LinkStar H68K-V2 is a 4-port router with two Gigabit Ethernet ports, two 2.5 GbE ports, and support for WiFi 6 and Bluetooth 5.2. It’s also a tiny device that measures just 80 x 60 x 40mm (3.15″ x 2.36″ x 1.57″).
AllStarLink, Inc. is supported by donations. If you would like to help support the AllStarLink system we use and enjoy, please visit the AllStarLink Donations Page and give an amount you are comfortable with. AllStarLink, Inc. is a 501(c)(3) nonprofit.
I do not financially benefit from donations to AllStarLink, Inc. You can help support the Random Wire newsletter if you wish. Thank you for subscribing to the Random Wire!
My latest hotspot project is a Raspberry Pi 3B+ single board computer with a duplex MMDVM hat in a C4Labs case. The featured component is a Nextion screen, making for an attractive unit overall.
Hotspot and HT
However, it runs hot. I did not install a fan inside the case but did add two heat sinks: one on top of the CPU and one on the network chip. Still, the reported temperature under load runs 140°F or more without additional cooling.
Hotspot temperature without fan
To see if a fan on the outside of the case would make a difference, I taped a small USB-powered fan to the unit. That made a big difference. I don’t really like the look of the blue tape on the case, though, so I explored some other options.
One option was a small cooling fan on a flexible gooseneck that is sold as a computer accessory. It plugs into a USB port on the computer and you can aim it where you want the cooling air to go.
However, I ended up selecting something different: an 80mm fan powered by a USB port, with an off-low-medium-high switch inline in the power cord. This $10 fan has silicone rubber feet on the top and bottom of the fan assembly and the hotspot sits on the feet on top of the fan. Cooling air is pushed into the case through a couple of openings in the bottom layer of the case.
Hotspot rests on top of 80mm fan
With the fan, the temperature under moderate load is well below the high temperatures seen without the fan.
Hotspot under load with cooling fan
Does it work? It works as well as the little fan and it does it with no blue tape involved. I find the larger fan is also perceptibly quieter, perhaps because the larger fan doesn’t have to spin as fast to move a good quantity of air. I like simple and this is a very simple fix to the hot hotspot issue.
I let the hotspot run overnight and this morning, at 1% CPU load, the temperature was a nice, cool 100°F.
Hotspot at low load with cooling fan
Overall, it’s an attractive unit and I find I don’t mind the chunky fan sitting underneath it.
Nextion screen on hotspot
2 — Some fun with Winlink: Hamword
I was delighted to get feedback from Rob KM6LBU about another way to exercise your Winlink station by playing a weekly game called Hamword. This is a Wordle-type game in which you submit guesses via Winlink. It’s actually a lot of fun.
I didn’t do exceptionally well on my first outing with Hamword. My first word guess contained none of the letters in the five-letter word for the week. My second guess caught two of the letters but they were in the wrong position. In my third guess, I got the position of one letter correct.
Screenshot of Winlink message
My fourth guess was poorly made, because I already knew the U did not go in the second position of the word. (If the digit below a letter is zero, it means that letter is not part of the correct word. If it is a one, that letter is in the word but in a different position. If it is a two, the letter is correct and in the correct position.) I made up for that with my fifth guess that ended up being correct. With that result, I ended up in 46th position on April 12, 2024.
Hamword position for KJ7T
Just like sending messages via APRS on APRSThursday is a way to make sure your APRS station is operating properly, Hamword lets you have some fun while exercising your Winlink station.
Thank you, Rob KM6LBU!
3 — Hotspots in the KJ7T QTH
Recently, I was reminded by a ham friend that I seem to have plenty of hotspots. I thought it might be interesting to photograph the KJ7T hotspot family:
Hotspots
The top row are units I constructed from parts. The bottom row are hotspots purchased already built and configured.
Top left: My newest build is a Raspberry Pi 3B+ single board computer (SBC), AURSINC duplex MMDVM hat, and Nextion screen in a C4Labs case. This hotspot is set up for Yaesu System Fusion and runs 24x7 at home. This is the unit discussed at the top of this newsletter that rests on top of a cooling fan. I use this with Yaesu radios: an FT3D and an FT5D handie talkie.
Top center: This is a Raspberry Pi Zero 2 W board and MMDVM hat being powered by the USB power bank shown in the photo. This hotspot is set up for Yaesu System Fusion and I use it when traveling. I use this with Yaesu radios: an FT3D, FT5D, and an FTM-300DR mobile rig. I love how compact this is!
Top right: My first hotspot build is a Raspberry Pi 3B+ and duplex MMDVM hat with small display screen in a C4Labs case. This is set up for DMR. I use this with an AnyTone AT-D878UVII Plus DMR handie talkie.
Bottom left: My second hotspot is a SkyBridge unit that appears to be built on a Raspberry Pi 4 SBC with a Nextion screen. It is set up for DMR. I use this with the AnyTone DMR HT.
Bottom right: My very first hotspot is a ClearNode, also built on a Raspberry Pi 4 SBC. Instead of a screen, it has an Android and an iPhone app for control. It is set up for AllStar and is accessed via an analog handie talkie radio.
And then, as I looked at my shelf full of hotspots, I saw one pushed to the back of the shelf: the cheap hotspot! This appears to be a Raspberry Pi 3 board and duplex MMDVM hat. I’ve configured it for both DMR and YSF. This unit is a backup for traveling.
Login
