with Firmware >= 1.4.1
PiStar >= 3.4.16 or MMDVM-Host Version ???
Already have a working installation of Pi-Star (Pi*)?
ssh pi-star@pi-star [Enter]
Now you will be asked for the Password - Standard-Password is „raspberry“ without „“ or take the password you have changed in Pi-Star Dashboard.
You will see the Welcome Message in ASCII-Signs
Now you have to Enter the following commands:
1. PI* uses a write protection so the command to unlock the filesystem for editing is:
2. Now get the latest Version of Pi* and all needed software components:
sudo pistar-update [Enter]
3. Upgrade the Pi* Installation to the next following Version:
sudo pistar-upgrade [Enter]
Repeat the last command (
sudo pistar-upgrade) till you get a message „you have installed the latest Version of Pi* - No update needed“ or a similar message.
It is not possible to directly Upgrade to the newest Version! So you have to repeat the pistar-upgrade several times.
For example: You have installed Pi* Version 3.4.13 and want to get onto Version 3.4.16
You have to use the command „sudo pistar-upgrade“ 3 times to get from 3.4.13 to 3.4.14, than from 3.4.14 to 3.4.15 and 3rd time to get from 3.4.15 to 3.4.16.
The last output in terminal should be:
You are already running the latest version… Sleeping a few seconds before making the disk Read-Only… Finished
for Upgrading MMDVM_HS_Hat board conected to GPIO you have to enter the command:
sudo pistar-mmdvmhshatflash hs_hat [Enter]
for upgrading the original MMDVM-HS_DUAL_HAT board (made by Andy, Florian (DF2ET) and DB9HAT) conected to GPIO you have to enter the command:
sudo pistar-mmdvmhshatflash hs_dual_hat
If you get a message that the flashing process was successfull, the hardest part is done. If not, repeat flashing or ask for help in the „MMDVM-BM“ or „DAPNET User“ Telegram-Messenger Groups.
Do a restart now with
sudo reboot now [Enter]
You will get a „DAPNET AuthKey“ by email if your ticket is arranged by a Team-Member.
Now it`s time to Login into the Pi*-Dashboard!
On a Windows, Mac, or Linux-based computer (not the hotspot itself) that has WiFi enabled, open a browser window and navigate to (trailing slash needed):
Windows: http://pi-star/ macOS, iOS, etc.: http://pi-star.local/ On some mobile devices, the url won't work. In that case, try the Auto AP IP address: 192.168.50.1
Go to Admin Area and hit „Apply Changes“ somewhere, like if you would save any changes - even if you did not change anything. This will reload the page and force Pi* to reload store and reload the Configuration. During this process all missing or by update added sections will be loaded and shown correctly.
Now you should still see the Configuration view and in the „MMDVMHost Configuration“ section, switch on „PROCSAC“ and then click „apply changes“.
The Page will reload - now search for the „POCSAG Configuration“ section and fill out the needed values:
Please google for a Pi-Star installation guide. A nice one is written by KE0FHS on https://www.toshen.com/ke0fhs/pi-star.htm or visit the main website of the PI-Star-Project under https://www.pistar.uk/
Sometimes the DAPNETGateway-service got stuck when loosing internet-connection. This results in an error-state on the status-page of the transmitter at hampager.de. Unfortunately the service would be still running but not reconnecting.
If you would like to implement a watchdog that restarts the service, if the transmitter goes into error-state you could use following script, that could be called every 5 minutes for example by crontab:
#!/bin/bash RETVAL=$(curl -u <username>:<password> https://www.hampager.de/api/transmitters/<yourtransmittercallsign> | egrep -h "OFFLINE|ERROR" | wc -c) if [ "$RETVAL" -gt 0 ]; then sudo systemctl stop dapnetgateway.service > /dev/null 2>&1 echo restarting dapnetgateway sleep 5 sudo systemctl start dapnetgateway.service > /dev/null 2>&1 fi
Remember to switch the sd-card to read-write-access with
rpi-rw before creating the file in your home-directory. Also remind to make it executable with
chmod +x yourscriptname.sh