Menu — partial
Full Disk Image
Updating and Upgrading Pi–Star
New or updated entries indicated with or . Labels expire in 30-60 days.
And we say…
The CSS Tool enables one to play with the total color schema of the Pi–Star software. The combinations are unlimited. Using a comprehensive color table I chose to only change the "border" color…
… from among the following possibilities. See what you think.
Remember to "Apply Changes" to see results. At the page bottom there is a safety "reset values" to all default colors should your total schema wanders off the rails. Do make a record of your CSS changes as the Pi–Star Configuration > Backup/Restore > Download Configuration ZIP file does not include the color values.
After upgrading and updating Pi–Star on one hotspot's SD card, I made a second SD card for a second hotspot. The first hotspot worked. The second failed to work. It made no sense; I assumed the SD card was the problem. The solution? (Tip of the hat to WB3EHB for suggesting a solution.) Using two Windows SD utilities:
A fringe benefit of this exercise? Making a full SD card image includes all settings and configurations, including those items not saved in a Configuration ZIP file.
If you make additional cards for one hotspot, skip step 4.
Adding remote commands to Pi–Star makes a few things easier. One can remotely restart Pi–Star if a WiFi connection is lost and shut down the hotspot without removing power. Enter the Expert mode.
Modify the sections where the fields are marked in yellow.
# Pi–Star Remote config file
# This config file is desiged for the Pi–Star Keeper remote control
# The remote control system is designed to give repeater keepers an
# RF KillSwitch for their repeaters.
# Is the Pi–Star Remote Enabled? (true|false)
# Keepers Information
callsign=W2AAA ← Enter your call. Use all upper case.
# TG commands
Save and exit. Then make changes in the codeplug.
With my dual VFO MD-UV380, I put these commands into VFO B to join Unlink/4000. Otherwise, add Reboot and Shutdown to whatever Zone List contains an Unlink.
For more information on the remote commands, see Remote Commands in the Pi–Star Notes by KE0FHS.
If after doing a upgrade results in a failure to connect to the master server you use, look at the Configuration/DMR Configuration/DMR Master entry. If the field has changed from the master server of your choosing to DMRGateway, reselect your master server.
I was told that the PiStar image file coding was changed from a default UK host previously in the DMR Master field so as to avoid incessant keyups by persons new to PiStar. I have not verified this, however.
It is normally recommended to use the secure shell (SSH) commands to update both the OS (operating system) and Pi–Star.
If upgrading from 4.0.x or 3.4.x to 4.1.x, download the most recent image file. Enter configuration settings anew, rather than rolling the config ZIP saved settings file from an earlier Pi–Star version forward.