Tag Archives: WPSD

Ohio Section Journal – The Technical Coordinator – February 2025 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Tom – WB8LCD and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the ARRL Ohio Section Newsletter and other Ohio Section news by joining the mailing list. Anyone can join and do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the Ohio section will need to use the mailing list link above.  Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).

  • Go to www.arrl.org and click the Login button.
  • Login
  • When logged in successfully, it will say “Hello <Name>” in place of the Login button where <Name> is your name.  Click your Name.  This will take you to the “My Account” page.
  • On the left hand side, under the “Communication” heading (second from the bottom), click Opt In/Out
  • To the right of the “Opt In/Out” heading, click Edit
  • Check the box next to “Division and Section News.”  If it is already checked, you are already receiving the Ohio Section Journal.
  • Click Save
  • There should now be a green check mark next to “Division and Section News.”  You’re all set!

Now without further ado…


Read the full edition at:

Archive index: https://arrl-ohio.org/ohio-section-newsletter/


THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

Hey gang,

Are you active on DMR and Brandmeister? Have you been inactive on Brandmeister for a time and your ID no longer seems to work? Most importantly, does your DMR ID begin with a “1”? If so, you need to obtain a new DMR ID.

What is a DMR ID? It is a unique subscriber (user) identification mechanism, containing 7 digits, for use on digital radio systems and networks. Ham radio has adopted this commercial standard for use on our own digital networks. Users registered in Ohio are assigned 3139xxx, where ‘xxx’ is a 3-digit consecutive ID. Ohio Statewide DMR talkgroup is 3139 and the first Ohio subscriber IDs began with the same. Though a “DMR ID” is universally accepted on any DMR network, it’s also accepted on other platforms using a 7-digit ID, such as P25.

As the popularity of DMR exploded, Ohio and many other states ran out of the 1,000 available IDs. That is 3139000 – 3139999. When that happened, keepers of the registration system at the time, DMR-MARC, decided to issue IDs beginning with a 1 resulting in IDs: 1139xxx. These IDs were issued about seven years ago. DMR IDs are now managed by RadioID.

IDs beginning with a 1 do not follow the Mobile County Code (MCC) standard and cause issues for some amateur radio DMR network administrators. The first three digits of an ID make up the mobile country code with the first digit identifying the geographic region. “3” identifies communications from North America and the Caribbean. According to the Wikipedia article, 1 and 8 are not used. Others reference 1 (as well as 0) being used for test networks.

Brandmeister’s announcement states 7-digit personal DMR IDs beginning with a 1 (such as 1139xxx in Ohio) will stop working, at the latest, January 1, 2026. If the ID has not been used “for more than a couple months” it will be purged before Jan 1. Analysis using the RadioID database search and dumps show 5,300 DMR IDs assigned in Ohio. 900 of those IDs begin with a 1. Nearly 1-in-5 users in Ohio need their DMR ID updated (as of this writing) before Jan 1, 2026 in order to continue using the Brandmeister network. All DMR IDs starting with a 1 will cease to work at the end of 2025 on Brandmeister.

6-digit repeater radio IDs beginning with a 1 (such as 1139xx in Ohio) will stop working sometime in the future. A date when these IDs will stop working has not been set (as of this writing). RadioID database search shows five repeater IDs are affected in Ohio (as of this writing).

5-digit CAP+ (Capacity Plus) IDs will stop working June 1, 2025. Capacity Plus is a popular Motorola commercial controller-less trunking system. I didn’t know it was used much in ham radio except for areas in Texas. As seen in a database search, five CAP+ IDs are issued in Ohio (as of this writing). Some NXDN IDs are also five digits but they are not the same as CAP+ IDs.

What prompted this change? Aside from not following the MCC standards, this causes problems with Brandmeister’s “operations, scripting, and automation.”

Now, I get it – I have obsessive compulsive tendencies and want everything to fit nicely into a defined structure. I’ve also worked professionally in programming and system administration having the desire for data to be correct only to be overridden in favor of convenience. Instead instructed to ‘make it work’ adapting programs to accept ‘bad’ data. In particular, data generated by other facilities, systems, or means which we did not have control.

Sure, it took extra time to code, test, and validate but far less effort than having a majority of customers redo a set of steps. Shifting responsibility to users will introduce additional errors, users will not want to redo work with no additional benefit gained, time waiting for users to complete, forgotten passwords, not remembering if they have an account. The list goes on. They already did it once, why would they do it again? Users will think they don’t need to complete steps again even when explicitly informed they need to do so.

Is this an issue with the software Brandmeister is using to run the network not accepting IDs beginning with a 1? Don’t know, they didn’t say. Most (ham) networks are built using open-source software and they apparently don’t want to modify it. Their own statements identify 1 as a valid, albeit test, network type. If it’s their “scripting and automation,” why not just change it?

Brandmeister has decided to take the opposite approach and make RadioID correct subscriber data. It’s an easy decision when you’re the 800-pound gorilla and one that doesn’t have to do the work. Brandmeister doesn’t have to get thousands of users to log on, “fix” their IDs and update equipment. RadioID can’t unilaterally fix all IDs that begin with a 1 without notifying users because users will still need to update codeplugs.

RadioID updated their portal to include a self-service way to correct an ID beginning with a 1 just a few days ahead of this publication. Users still need to logon, complete the steps to obtain a new DMR ID, update code plugs, upload the new ID to their radios, and update IDs entered into hotspots and apps, such as DroidStar. If you don’t use Brandmeister, it’s still a good idea to complete these steps because other networks may decide to follow suit since Brandmeister made this a requirement to use their network.

Updating a 1n DMR ID to a 3n ID:

Go to: https://radioid.net/
Click Logon.
Forgot password, click Pass Reset. Enter the callsign associated with the account and follow instructions to reset the password.
Don’t have an account, Register for one. It may take some time to validate license information.
After logging on, ignore/close popups prompting to subscribe unless one wishes to support the work RadioID is doing.

Under the “Your Radio ID’s” section, click the appropriate DMR Radio ID that needs to be changed.

On the “DMR USER ID” popup screen, “If your ID starts with 1n and you need a 3n ID for BM” click Convert to 3n ID.

When the new ID is received, update codeplugs, radios, hotspots, and apps. Get this done sooner-than-later to avoid the end-of-year rush of those who procrastinated avoiding delays associated with a pending deadline.

DMR ID in Connect Systems CPS. Radio -> General Settings -> Setting -> Radio ID. Update with the new DMR ID.

 

DMR ID in MD380 CPS. Radio -> General Setting -> Radio ID. Update with the new DMR ID.

 

DMR ID in Pi-Star (WPSD). Dashboard -> Admin -> Configuration -> DMR/CCS7 ID. Update with the new DMR ID.

 

If there are any issues updating an ID or accessing a RadioID profile, open a ticket with RadioID support. Do NOT create a ticket with Brandmeister Self-Care because they won’t be able to help. Doing so will cause additional delays in obtaining a new ID and they will direct you to RadioID anyway.

I’m not sure if Brandmeister is going to contact users whom are still using IDs beginning with 1 or, more likely, just cut off those users to the Brandmeister network. In the past, it isn’t like them to communicate major system changes to users other than posting on a section of their site users don’t typically visit and users don’t frequently visit the Brandmeister homepage. It may end up being that RadioID might contact users, but I don’t think I’ve ever received communication from them either despite having a current E-mail address on both services.

Make sure to pass the word around to other DMR users, family members on DMR, clubs that have DMR IDs, organizations and clubs that use DMR or have DMR nets. Chances are a number of users will need to complete these steps. 1-in-5 in Ohio alone need to update their ID. One can use the Database Online Search (then click DMR User/RPTR ID Search) searching call signs (or other field) to notify friends/family/club members to update their DMR ID. If your ID is compliant, take this opportunity to log on to RadioID and check the accuracy of profile details.

Thanks for reading and 73… de Jeff – K8JTK

Ohio Section Journal – The Technical Coordinator – November 2023 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Tom – WB8LCD and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Tom has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the Ohio section will need to use the mailing list link above.  Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).

  • Go to www.arrl.org and click the Login button.
  • Login
  • When logged in successfully, it will say “Hello <Name>” in place of the Login button where <Name> is your name.  Click your Name.  This will take you to the “My Account” page.
  • On the left hand side, under the “Communication” heading (second from the bottom), click Opt In/Out
  • To the right of the “Opt In/Out” heading, click Edit
  • Check the box next to “Division and Section News.”  If it is already checked, you are already receiving the Ohio Section Journal.
  • Click Save
  • There should now be a green check mark next to “Division and Section News.”  You’re all set!

Now without further ado…


Read the full edition at:

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

Hey gang,

Pi-Star was great. It solved big problems for hams wanting to use VHF and UHF digital modes around 2016-2017. Personal hotspots were becoming popular. Consisting of a digital interface (modem) board capable of transmitting and receiving digital modes such as DMR, D-STAR, and System Fusion. These transceiver options are low power at about 10mW. The modem interfaced with software to manage network connections. Many devices were created for the popular Raspberry Pi or Arduino single-board computers using the GPIO headers. Others were USB-based devices that could be used with a desktop computer running any operating system or plugged into a Raspberry Pi.

The hardware was pretty solid. Software, not so much. Nearly each group attempted to make their own software distribution. In general, this failed as users couldn’t get the software to work consistently and settings didn’t work as expected – even across users with similar setups. Many didn’t have monitors connected. VNC, a remote desktop sharing application, was used. VNC generally works well desktop-to-desktop, but not desktop-to-mobile. These problems weren’t helping promote digital modes and personal hotspots.

Then along came Pi-Star. Created and maintained by Andy – MW0MWZ, it solved nearly all those problems. On the hardware site, Pi-Star supported every digital modem in a single platform. MMDVM is the software capable of “speaking” different digital mode protocols and managing network connections. It came with a web front-end that did everything needed to configure and manage devices, update network settings, update device firmware, and have a nice usable dashboard. Ultimately, the Pi-Star platform superseded all previous attempts at a viable interface for digital ham radio hotspots.

On the Pi-Star site, version 4.1.5 dated October 2021 is the latest image available for Raspberry Pi. However, 4.1.6 is available through the update sequence pistar-update then pistar-upgrade at the command line, both prefixed with sudo. Pi-Star 4.1.5/6 release is based on Raspbian 10 (buster) which has reached end-of-life. Raspbian, the standard Raspberry Pi operating system, follows the Debian release schedule. Debian 10 is out of standard security updates and into LTS (long term support). Raspbian does not offer LTS.

If you’ve read my column long enough, you know the majority of vulnerability issues can be avoided by keeping systems updated and patched. I’m also reminded of the time when I went searching and found there are Pi-Star’s accessible directly from the Internet, with the default password. What could possibly go wrong?

By all accounts, and as of this writing, Andy is no longer maintaining Pi-Star. Looking at his post count in the forums: zero in 2023 and ten in 2022. There are very few updates to GitHub repositories in the last two years, which are used to update Pi-Star devices. I’ve seen references to lack of updates due to lack of interest. Pi-Star is also lacking the latest additions to MMDVM including M17 and FM for boards that support those modes (usually through firmware updates).

The next iteration of Pi-Star (or fork) comes to us via W0CHP, called “W0CHP-PiStar-Dash (WPSD).” I learned about WPSD when AmateurLogic ran a segment in January on this new offering. I started using it shortly after. Though it was early on in the project, WPSD was labeled “not for the faint of heart” by the author.

It was really rough around the edges. I had to debug scripts in order for updates to run successfully. The dashboard would show the modem in “TX D-STAR” when only P25 was enabled. There were issues with the configuration file manual editor too.

Regardless, development is very active. WPSD has become much more stable and now considered the Pi-Star replacement. Alot has changed in the time I’ve been using WPSD and presume things will continue to evolve.

One such change, there was an option for installing WPSD on top of an existing Pi-Star installation. That option is no longer available or supported. The distribution must be flashed directly to an SD card (flash memory), exactly like Pi-Star.

I always recommend using a new card or different SD card from the current, existing installation until everything is working as the user expects. Having the old (original) card available allows switching back easily in case of problems or need to reference something from the previous installation.

Pi-Star with Nextion display (ailunce.com)

A recent blog post by the author called out people who claim WPSD is an “overlay.” At one point, it could have been installed on top of an existing Pi-Star installation. WPSD is not an overlay. It is its own software distribution.

WPSD works with most Raspberry Pi offerings (Zero, Zero 2, 2, 3, 4, …) including the Orange Pi and Nano Pi Neo variants. The Raspberry Pi Zero W 1.1 is not really recommended for use but it will work. The Zero W 2 is recommended instead. A Zero W 1.1 needs extra configuration steps after flashing the SD card. These include: creating a wpa_supplicant.conf and placing it in the /boot partition. Waiting at least 30 minutes for the image to boot and configure itself before accessing the dashboard. Steps are detailed in the link above.

While using WPSD with my Pi Zero W 1.1 it is quite a bit quicker, taking about a minute to save changes on the configuration page of the dashboard. Compared to the Pi-Star which took two to three minutes to save changes. Pi Zero W 2s are still very hard to find. If you can find one, a male header strip still needs to be soldered to the GPIO. Pre-soldered ones are nonexistent.

Not only is WPSD on a supported operating system (bullseye, Debian 11) but there are a TON of enhancements and updates over Pi-Star. Though the visual layout has changed, it’s intuitive enough for any existing Pi-Star user. Changes I noted right away were the addition of M17 support (though I don’t have any capable devices) and Nextion support built-in. Nextions are displays and/or touchscreens that can be attached to the modem or added through a TTL serial converter, such as those based on the CP2102 chipset. Adding Nextion support to the original Pi-Star was a terrible experience using hacky scripts that had to be run a couple times before the drivers and software could be usable.

WPSD Live Caller mode

Non-exhaustive list of enhancements: full APRSGateway support. DGId support. DMR Roaming Beacon Support for repeaters. Caller details include name and location. Talkgroup names are populated. On the fly changes of talkgroups/rooms/reflectors/networks including ability to pause networks for attending nets or quieting a busy mode. Live Caller mode which is a browser based (virtual) version of a Nextion display. Ability to disable cron (scheduled) updates. Updated dashboard including wider, bigger, updated fonts, user configurable options including CSS styling and fonts. Full dashboard display or Simple View with only RF and gateway activity. Configurable number of last heard stations. Configuration/Profile Manager, similar to OpenSpot, where the user can save multiple versions of a setup and restore them based on use.

A Profile Manager feature was added to WPSD, which did not exist in Pi-Star but exists in the OpenSpot devices. This allows the user to save device settings into a profile to be recalled later. These could be travelling profiles, or ones specific to a mode, network, or configuration for a net. Initial implementation of this feature did not backup saved profiles when using the Backup/Restore feature. Only the current active profile would be backed up or restored. Now, within the last two months, Backup/Restore saves ALL device profiles in the backup archive.

That is an example of the constantly evolving nature of this new WPSD distribution. Updates happen quite frequently. WPSD was updated nearly daily for a long time. Updates still happen quite frequently but at the pace of about once a week, maybe more.

Speaking of backups, it’s not recommended to use migrated configuration files or backups from Pi-Star, due to differences. If Pi-Star files are used with WPSD and there are issues, the user will be required to begin configuration from scratch.

One change I do not particularly care for is the requirement to use DMRGateway. In Pi-Star, I used Direct Mode which is the selection of a single DMR Master. For example: select BM_3104_United_States for Brandmeister and TGIF_Network for TGIF as the DMR Master. I liked this for two reasons: this functionality is similar to how a repeater would operate and it simplifies codeplug programming for talkgroups with the same TG ID across different networks. Ohio Statewide is 3139 on multiple networks meaning I only had to setup Ohio Statewide once. Though it seemed most users did use DMRGateway in Pi-Star.

DMRGateway supports simultaneous connections to six networks. With all those network connections there must be a way to differentiate which network is to receive a transmission. That way is through “prefixes,” a single number prepended to the talkgroup number. DMRGateway doesn’t appear to use a prefix for Brandmeister, 3139 would remain 3139. TGIF talkgroups are prefixed with a 5. 3139 would become 53139. HBLink prefix is 8. My HBLink would be 831983 instead of 31983.

WPSD Dashboard

If you’ve programmed a codeplug for a DMR radio, it’s not as easy as just making a new contact with the prefix. Adding the contact to an RX group, creating new channels, and reorganizing or creating new zones are all needed. Maybe I’ll purge the ‘nice to haves’ in my codeplug as I typically only use a handful of talkgroups or just make a new simplified codeplug for use with WPSD.

Changes have been made to the scripts and tools. Commands rpi-rw and rpi-ro have been removed. These were used to switch between a read/write file system and a read-only file system. There has been debate whether a read only file system corrupts any less or shortens the lifespan of the SD card when left in read/write mode. Pi-Star was constantly changing from read only to read/write during settings changes, updates, and hostfile update cycles. Mine seemed as though it could never successfully change from read/write back to read only after an update. Eliminating those scripts just ‘fixed’ those resource busy messages.

Pi-Star scripts that began with pistar- have all been removed and replaced with a smaller set of wpsd- scripts. It was great because all WPSD updates were taken care of by going to Admin -> Update. Though, a recent change has removed operating system updates from that feature. Admin Update only updates WPSD currently (probably due to those lengthy Raspbian kernel updates). To update the operating system, SSH to WPSD or go Admin -> Advanced -> Tools -> SSH Access. After logging in (same credentials used to login to the Admin or Configuration dashboards), at the command line, enter (capitalization is important):

sudo UP_OS=1 wpsd-update

As with Pi-Star, if an update fails or installation becomes borked, re-flashing the SD card with the latest available image will bring the device to a known working state. Remember to save a new backup before updating! WPSD images are updated more frequently than Pi-Star. Updates released since the image was published won’t take quite as long to apply.

There is a lot to read, including some edge features that have been removed, on the WPSD page (linked above). Comparing WPSD to Pi-Star (‘this used to work on Pi-Star,’ ‘when I revert back to Pi-Star this thing works,’ etc.) is verboten when asking for support. The main page on W0CHP’s site is a blog detailing direction and state of the project as well as reasons for changes. I recommend Pi-Star users update to W0CHP-PiStar-Dash – if nothing else, for the supported operating system and OS package updates though there are many improvements and welcome features.

Thanks for reading and 73… de Jeff – K8JTK