W0CHP.radio

We frequently see user content starting with “it doesn’t work”, and no other details. We can’t help without more information. This document is intended to inform you how to ask for help in a way that the volunteers, users and developers actually help you.

…or, “R/O no mo, yo.” 😆

Most users are accustomed to W0CHP-PiStar-Dash (and Pi-Star) having a forced Read-Only file system by default. While this can be useful, it’s unnecessary in W0CHP-PiStar-Dash and in fact, is a pain in the ass sometimes.

Soon, when W0CHP-PiStar-Dash automatically updates itself at night, or when users invoke an update, the file-system will no longer be in Read-Only mode by default.

There seems to be lots of confusion with WPSD and DMR functionality. This document serves to hopefully clear that up.

Due to the (honestly, unexpected) growth and popularity of W0CHP-PiStar-Dash, two wonderful users/fans¹ have setup online support and chat communities for users of my software:

• W0CHP-PiStar-Dash Facebook Group (Courtesy of Daren, 2E0LXY)

• W0CHP-PiStar-Dash Discord Server (Courtesy of Mark, 2E1CEQ)

Update 10/7/22:

Network move complete; all systems operational.

Beginning October 5, the various resources hosted on the W0CHP.net network will experience intermittent, and some extended outages and downtime.

The network is moving to a different physical location, but will retain the same asynchronous fiber connections speeds, IPs, etc.

I anticipate the outages lasting no more than 48 hours. Once fully complete, I will update this post accordingly.

Resources that will be affected

• This very website
• Connectivity to the XLX-493 reflector/gateway and its web-based dashboard.
• The W0CHP.net Git Repositories
• The installer program for W0CHP-PiStar-Dash will not be available (hosted on the above Git repo).
• Various backend resources that enable the auto-updates to occur on W0CHP-PiStar-Dash installations.

Greetings gracious hams! As some of you know, I operate the XLX493 Reflector. Currently, it supports both DMR and YSF protocols. However, I do not posses the necessary hardware for trans-coding the D-Star protocol.

And since my reflector has been getting more traffic lately, I’m putting a feeler out there to other hams who run a D-Star-enabled reflector to see if they’d be gracious enough to peer with reflector (more specifically, Module E, since it’s the busiest module.

I keep/use a hotspot in my truck, and I’ve always wanted a way to manage/switch/connect/disconnect from reflectors, talkgroups, etc., hands-free; using only my voice.

I’ve begun work on a small project to allow me to do just that. And no, this is not an April Fool’s joke. 😆

Check it out…

For some time now, I’ve yearned for a way to quickly link to various XLX reflectors and modules on DMR, as well as unlink from modules to “mute” a busy reflector/module.

Recently, I’ve witnessed two networks suffer from loops, caused by mis-configured hotspots. Now while Pi-Star has some rudimentary checks in place (simply a warning message for hotspots configured as “Public Nodes”), I’ve improved W0CHP-PiStar-Dash to help prevent these loops even further.

The original Pi-Star (still) uses myriad HTML tables for layout (non-tabular) data. That’s a Bad Thing^™ And since my W0CHP-PiStar-Dash software is a fork, it inherited lots of that legacy garbage. However, I’ve begun the conversion from HTML tables for layout, to proper HTML(5) and CSS.

This is a UI/UX project that will be completed in phases as I get to them.