Set up web interface 0.5.10
Extract the ARM64 package on a Raspberry Pi running 64-bit Raspberry Pi OS 13 with an SXceiver HAT. Internet access, at least 4 GiB free storage and 1.2 GiB available memory including swap/ZRAM are required.
Download and verify the package
Run these commands on the Pi. Stop an existing radio cell in the web interface first.
curl -fLO https://dl7olg.de/downloads/tmo/dl7olg-tmo-dashboard-0.5.10-arm64.tar.gz
curl -fLO https://dl7olg.de/downloads/tmo/dl7olg-tmo-dashboard-0.5.10-arm64.tar.gz.sha256
sha256sum -c dl7olg-tmo-dashboard-0.5.10-arm64.tar.gz.sha256 && tar -xzf dl7olg-tmo-dashboard-0.5.10-arm64.tar.gz
cd dl7olg-tmo-dashboard-0.5.10-arm64
Do not continue if checksum verification fails; download the package again. From the extracted directory, run:
sudo python3 scripts/install-all.py
On first setup, the installer asks for an existing Linux login account with a password. It installs dependencies, fetches pinned source revisions and builds the SXceiver driver, BlueStation and voice decoder. The web interface and voice encoder are supplied as ARM64 binaries. It configures HTTPS, the service account, services, log rotation and the default Wi-Fi power-saving setting. It does not perform a general operating-system upgrade.
For an existing public installation, stop the cell first. Running the installer again backs up replaced files and preserves radio parameters, hotspot password, licence, login permissions, certificates and TX calibration. It recognises the private Si570 edition and does not replace it. Only the web interface starts. After an error, the cell stays stopped; OS packages and build tools already installed remain. The file backup and log are stored on the Pi.
Open the displayed HTTPS address, activate the licence and enter your radio settings and TetraPack password. Browser transmission requires importing the local CA as trusted on your operating device. The installer cannot complete browser login or device-specific permission prompts for you. Hardware must be correctly detected; the installer neither writes the HAT EEPROM nor starts a test transmission.
Optional arguments: --login-user NAME avoids the login-account prompt; --plan only displays the steps; --without-decoder skips the decoder if browser listening is not needed or you use your own solution. The decoder is fetched directly from mbelib-neo rather than redistributed in the package; its component notices still apply.
Check hardware first
Generate a report without changing anything:
python3 scripts/detect-hardware.py
python3 scripts/detect-hardware.py --json
Add --lang en for English messages. Detection reads existing system information without opening SPI/GPIO or audio devices. Repeat with sudo if read permissions are missing. The installer performs the same check before package installation and building. On failure, installation stops and the report explains why.
Profiles cover SXceiver 1.0, 1.1 and 1.2, product ID 0x1255, nominally 38.4 MHz. Revision determines GPIO assignments. Required: SPI device 0.0, the appropriate Pi pin controller on GPIO chip 0, and an unambiguous SX1255 sound card with TX device 0 and RX device 1. A different or missing manufacturer name alone does not block a clone. Values come from the Device Tree and driver profile, not a frequency measurement. A copied EEPROM does not prove board compatibility.
If the EEPROM is missing, the revision unknown or interfaces differ, consult the board manufacturer’s documentation first. A missing overlay can prevent detection of a correct board. Do not write another board’s EEPROM image speculatively. 32 MHz variants, different GPIO assignments, amplifiers and filters need separate checks; universal compatibility is not promised. See docs/HARDWARE.md in the package.
Upgrading to 0.5.10
From 0.5.4 or earlier, use the 0.5.10 complete installer. It also installs the hardware check before each radio startup. A web panel update alone is insufficient; the update checker links to this guide. Back up settings and stop the cell first. With unknown hardware, the old installation remains until a suitable profile has been checked. The installer does not adopt different clocks or change private Si570 settings.
From 0.5.5, a web panel update is possible; radio software remains compatible.
Optional: USB Si570 in Pro
Only for a modified SXceiver with its original oscillator isolated, an external CMOS Si570, PE0FKO 15.15 and verified level adaptation. A normal TCXO board does not need this option. Import the Pro licence and stop the cell first. In the extracted 0.5.10 package:
python3 scripts/setup-si570.py --plan
sudo python3 scripts/setup-si570.py --external-clock-connected
The second command confirms that the hardware modification has actually been completed. It configures chrony, the clock check before radio startup and the measurement service. It does not start the cell; automatic control is initially off. Start the cell, wait for sufficient measurement quality, then enable Si570 control under Hardware & Clock. No correction occurs without suitable measurements. Disabling control stops neither chrony nor measurement.
Existing full Pro licences are accepted. Firmware is not updated over USB; EEPROM startup frequency and calibration data are preserved. The complete guide and hardware limits are in docs/SI570.md. Construction and measurements.
Updates in the web panel
From 0.5.1: Advanced → Update web panel → Check for updates. Checks run only when requested and require internet access. Packages are verified by digital signature, checksum and radio-software compatibility. Install update briefly restarts the web interface; sign in again afterwards. The cell must already be stopped and stays stopped. The licence and personal settings are preserved and the previous release is backed up.
If new BlueStation/SXceiver components or startup checks are required, the interface directs you to the complete installer, which also updates radio software. Older releases without an update function need one upgrade through the complete installer. The private station edition does not accept public updates.
The following steps are for manual installation and troubleshooting.
Manual setup: BlueStation, SXceiver and web interface
This describes a new installation on a Pi with 64-bit Raspberry Pi OS, Debian 13, Python 3.11 or later, systemd and SXceiver HAT 1.2. Back up configuration and programs before changing an existing installation; do not blindly replace existing services with these templates.
1. Hardware and operating system
Fit the SXceiver with the Pi powered off. RX and TX have separate connectors. Connect suitable antennas or terminations before starting the transmitter. An external amplifier is not part of this setup.
Use Ethernet for initial tests. A suitable power supply and a short, low-resistance supply cable matter. A USB charger’s advertised total wattage does not tell you its available power at 5 V.
uname -m
vcgencmd get_throttled
ls -l /proc/device-tree/hat
aplay -l
arecord -l
aarch64 confirms a 64-bit system. SXceiver should appear as an audio device. throttled=0x0 means the queried undervoltage and throttling bits are clear. Check again under load.
The HAT used here already had a configured EEPROM. Only if detection is missing or incorrect, follow the manufacturer’s instructions for your revision. Do not write an unrelated EEPROM image as a precaution.
2. Tools and sources
sudo apt update
sudo apt install --no-install-recommends git make g++ cmake pkg-config \
libsoapysdr-dev libasound2-dev soapysdr-tools libssl-dev libgpiod-dev \
python3 openssl libpam0g alsa-utils network-manager iw clang llvm-dev libclang-dev
Install Rust/Cargo through rustup.rs. The tested system used Rust 1.100. On a 1 GB Pi, use a single build job and sufficient swap/ZRAM. Building may take several minutes.
Extract the download. These examples assume $HOME/dl7olg-tmo-dashboard-0.5.10-arm64; adjust the path if needed.
export TMO_PACKAGE="$HOME/dl7olg-tmo-dashboard-0.5.10-arm64"
mkdir -p "$HOME/tmo-src"
cd "$HOME/tmo-src"
git clone https://github.com/tejeez/sxxcvr.git
git -C sxxcvr checkout 9705147dd8c189625071f3f163ea56119bda4a05
git clone https://github.com/MidnightBlueLabs/tetra-bluestation.git
git -C tetra-bluestation checkout 09d4e0d9a0b8cf6c881e77353db325df9a4715aa
3. SXceiver driver
The included patch adds startup with a fixed 38.4 MHz reference and frequencies, digital TX amplitude and DC correction, and their status report. The example configuration and radio-setting controls use these extra driver arguments.
cd "$HOME/tmo-src/sxxcvr"
git apply --check "$TMO_PACKAGE/patches/sxxcvr-dashboard.patch"
git apply "$TMO_PACKAGE/patches/sxxcvr-dashboard.patch"
cmake -S SoapySX -B SoapySX/build
cmake --build SoapySX/build -j1
sudo cmake --install SoapySX/build
sudo ldconfig
g++ -std=c++17 -O1 -g -fsanitize=undefined SoapySX/test_tx_calibration.cpp -o /tmp/test-tx-calibration
/tmp/test-tx-calibration
The clock value refers to the tested HAT. Check the clock source on different hardware first. Successful compilation does not establish correct RF operation.
4. BlueStation with dashboard extensions
cd "$HOME/tmo-src/tetra-bluestation"
git apply --check "$TMO_PACKAGE/patches/bluestation-dashboard.patch"
git apply "$TMO_PACKAGE/patches/bluestation-dashboard.patch"
git apply --check "$TMO_PACKAGE/patches/bluestation-preferred-slots.patch"
git apply "$TMO_PACKAGE/patches/bluestation-preferred-slots.patch"
git apply --check "$TMO_PACKAGE/patches/bluestation-handset.patch"
git apply "$TMO_PACKAGE/patches/bluestation-handset.patch"
git apply --check "$TMO_PACKAGE/patches/bluestation-operations.patch"
git apply "$TMO_PACKAGE/patches/bluestation-operations.patch"
git apply --check "$TMO_PACKAGE/patches/bluestation-private-calls.patch"
git apply "$TMO_PACKAGE/patches/bluestation-private-calls.patch"
CARGO_BUILD_JOBS=1 cargo build --release --locked
sudo install -d /opt/tetra-bluestation/bin
sudo install -m 755 target/release/bluestation-bs /opt/tetra-bluestation/bin/bluestation-bs
The extensions add permanent and temporary group subscriptions and GPS routing. In the licensed edition, the Brew network worker reads talkgroups-effective.json, derived from talkgroups.json.
5. Service account, files and login
These steps apply to a new installation. The tmo account is for the radio service, not web login. Groups audio, spi and gpio must exist on your Raspberry Pi OS.
sudo useradd --system --user-group --home-dir /opt/tetra-bluestation \
--no-create-home --shell /usr/sbin/nologin tmo
sudo usermod -aG audio,spi,gpio tmo
sudo install -d -o root -g tmo -m 750 /etc/tetra-bluestation
sudo install -d -o tmo -g tmo -m 750 /var/lib/tetra-bluestation
sudo install -d -m 700 /var/lib/tmo-dashboard /etc/tmo-dashboard
sudo install -d /etc/systemd/system/bluestation-bs.service.d
sudo install -o root -g tmo -m 640 "$TMO_PACKAGE/config.example.toml" /etc/tetra-bluestation/config.toml
The example configuration contains no working Brew credentials. Licence import fixes the hotspot ID automatically. Set your own network password in the interface afterwards. Check frequencies, duplex table, network identity and codeplug too.
A hotspot identifier combines a seven-digit Radio ID with a two-digit ESSID. Example: 2636912 + 01 = 263691201. BrandMeister uses this extension for multiple hotspots sharing one Radio ID; no additional Radio ID is requested. A second hotspot could use 02. The radio retains the seven-digit participant ID. ESSID and APRS SSID are independent.
Choose an existing local Linux account with a password for web login. Replace meinbenutzer in the following file with its actual username:
sudo nano /etc/tmo-dashboard/environment
Contents:
TMO_LOGIN_USERS=meinbenutzer
Separate multiple authorised users with commas and no spaces. Existing Linux passwords are used. These accounts gain administrative station access through the interface; authorise appropriate operators only.
Create the PAM file with sudo nano /etc/pam.d/tmo-dashboard:
@include common-auth
@include common-account
6. HTTPS certificate
An existing browser-trusted certificate and private key may be stored as PEM at /etc/tmo-dashboard/server.pem. For a new local certificate, use the included setup tool:
sudo python3 "$TMO_PACKAGE/scripts/setup-https.py"
It uses the hostname, its .local name and current IP addresses. You may specify names and addresses explicitly; substitute your own values:
sudo python3 "$TMO_PACKAGE/scripts/setup-https.py" \
--hostname tmostation.local --ip 192.168.1.100
The tool creates a local certificate authority and a one-year server certificate. It validates addresses, names and the certificate chain before saving. Keys stay on the Pi. Existing certificates are backed up and replaced only with --replace-existing; the local CA is retained.
Copy only /etc/tmo-dashboard/local-ca.crt to the devices you use to operate the interface and import it as trusted. Compare its SHA-256 fingerprint with the Pi’s output. On macOS, use Keychain Access; on iOS, also enable full trust under Settings → General → About → Certificate Trust Settings. Other browsers may use their own certificate stores.
Browser microphones need trusted HTTPS. Dismissing a certificate warning is not reliably sufficient. A DHCP reservation in your router helps avoid IP changes. If the IP changes, rerun the tool with --replace-existing and restart only tmo-dashboard. The tool does not stop or restart the radio cell.
7. Configure services
sudo install -m 644 "$TMO_PACKAGE/systemd/bluestation-bs.service" /etc/systemd/system/
sudo systemctl daemon-reload
sudo python3 "$TMO_PACKAGE/scripts/install-licensed.py"
sudo python3 "$TMO_PACKAGE/scripts/register-tx-driver.py" --library /usr/local/lib/SoapySDR/modules0.8/libSXSupport.so
sudo systemctl daemon-reload
sudo systemctl is-active tmo-dashboard.service
The library path must match cmake --install output. For another SoapySDR ABI or installation prefix, use the actual path. Registration preserves existing TX settings. If none exist, it creates neutral values and configures the systemd environment and driver check.
Only the web interface starts. A new installation leaves the radio cell stopped with automatic startup disabled. The supplied radio-service template limits each run to ten minutes.
Open https://PI-IP-ADDRESS:8443/ and sign in with the authorised Linux account. Activation appears first. Enter your base callsign, email and personal seven-digit RadioID.net ID. Download the activation file and upload it at https://dl7olg.de/aktivierung/. Confirm your email, download the licence and import it with the same operator details while the cell is stopped. The licence and device slot determine the fixed hotspot ID. A changed ID removes the old network password; enter your own password and check radio parameters afterwards.
Licences are also checked before systemd starts and automatic startup. Without a valid licence, the interface remains available for activation and stopping remains possible. The protected file is /var/lib/tmo-dashboard/station.license. A new SD card in the same Pi needs no extra slot: reimport the licence or download it again through the same registration. A new Pi needs a free slot or manual approval.
The installation script backs up an existing public interface and integrates licence checking into the radio service. It refuses installation while the cell is running or when it detects the private Si570 edition. It does not reconfigure normal network management or the radio-service configuration.
For first setup:
- Match TX/RX and duplex spacing to the codeplug.
- Set MCC/MNC. TetraPack uses 901/9999.
- Check the assigned hotspot ID under TetraPack and set your own password.
- Subscribe to a suitable talkgroup after connecting successfully.
- Enable GPS redirection to the appropriate service address if needed.
- After a stable test, set automatic startup and run duration as required.
Normal radio/network changes require a transmitter restart. Group subscriptions and GPS routing take effect within seconds.
8. Logs, maintenance and updates
systemctl status bluestation-bs tmo-dashboard
journalctl -u tmo-dashboard -n 50 --no-pager
tail -n 50 /var/log/bluestation-brew-test.log
Set up radio-log rotation for continuous operation; logs can grow substantially. An example is in systemd/. Install with sudo install -m 644 "$TMO_PACKAGE/systemd/bluestation-logrotate.conf" /etc/logrotate.d/bluestation. Install and run logrotate regularly; its check interval determines how far the log may grow beyond 10 MB.
Back up configuration, additional files and binaries before updating. Patches are tied to the listed commits. Compare changes and interfaces before applying them to newer upstream versions. The package contains no Motorola firmware or codeplugs.
Audio monitor and RX display
The overview shows active TGs, sender ISSI and direction: RX is network → radio; TX is radio → network. This is the Brew hotspot’s perspective, not confirmation that a particular handheld received the transmission. Recent calls are retained as metadata in RAM only.
The BlueStation patch sends small local messages to /var/lib/tetra-bluestation/monitor.sock. The supplied services already include the necessary setting and directory access. A slow or stopped interface does not block radio operation.
Listening requires a library implementing the TETRA decoder API from mbelib-neo. The tested commit is ec8f7d1353d2e234daf61790402866d13a5fd706. This decoder is not included in the download. The project notes unresolved redistribution rights for included ETSI codebook data; see its component notices. Therefore neither decoder sources nor binaries are bundled.
The complete installer downloads and builds it directly from the original project. Manual installation is needed only without the complete installer:
git clone https://github.com/arancormonk/mbelib-neo.git
cd mbelib-neo
git checkout ec8f7d1353d2e234daf61790402866d13a5fd706
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build -j1
ctest --test-dir build -R 'tetra_decoder|tetra_shared_api|tetra_tables|fixed_point' --output-on-failure
sudo cmake --install build
sudo ldconfig
sudo systemctl restart tmo-dashboard
The system loader locates the library. Alternatively, set an absolute TMO_VOCODER_LIBRARY=/path/libmbe-neo.so in /etc/tmo-dashboard/environment. The RX display works without a decoder.
Listening starts after a browser click. The monitor decodes ordinary unencrypted full-rate TETRA voice, records no calls and itself provides no transmission function. A short bounded audio buffer exists only in RAM. Volume affects this browser only. You can select one of several simultaneous calls; automatic mode prefers incoming network calls.
Language and backups
Switch between German and English at the bottom right. The choice is stored only in that browser. Settings, help and messages are translated; original technical logs are unchanged.
Advanced → Back up configuration creates a named, timestamped backup on the Pi containing radio/network settings, talkgroups, GPS routing and TX calibration. Download backup exports the selected backup or, if none is selected, current settings as JSON. Import backup file restores such a download. It includes the hotspot password: keep it confidential. The previous state is backed up automatically before restoration.
Automatic startup and run duration remain separate operating settings. Older automatic TOML backups contain only radio/network settings. After restore, radio/network changes take effect at the next transmitter start; talkgroups and GPS routing update within seconds.
TX calibration and updating existing installations
See docs/TX-CALIBRATION.md. The package contains complete patches against unmodified upstream sources. For an older dashboard version, use a separate fresh source tree at the specified commits; do not reapply these patches to already modified sources. Preserve existing configurations and services when updating.
Basic/Pro split from 0.4.0
Before upgrading 0.3.0, review the feature split in README.md. A Basic licence enables free core functions in 0.4.0. Pro settings remain saved but are not passed to the radio service without a matching licence. The installer configures 90-edition.conf and talkgroups-effective.json. Do not edit that derived file manually.
After purchase, stop the cell and import Pro under Manage licence. Import does not start the cell automatically. Unlocked settings then become active. Pro works offline indefinitely. Existing Wi-Fi still works in Basic; manage it through the operating system.
Virtual radio (Pro)
The release includes a separate ARM64 voice encoder and its complete sources. The installer installs it at /usr/local/bin/tmo-tetra-encode, backing up an existing version. The complete installer builds BlueStation with all five supplied patches; the corrected group registration also applies after reconnection.
For version 0.5, download and reimport an existing 0.4 Pro licence so the new virtual-radio feature is signed into it. This uses neither another device slot nor another purchase. Basic stays Basic. Licence management makes the extended Pro licence available for download.
Controls, keypad, TG list, listening and text messages are described in docs/HANDSET.md. Outgoing private calls via TetraPack/BrandMeister automatically enable reception when transmitting. Release the button to hear the reply. Only the connection belonging to that private call is played; unrelated calls stay muted during setup. “Hang up” ends the connection. A real network voice echo test has been confirmed. Browser transmission over the local RF link to a handheld still awaits testing. Local private calls and unsolicited incoming private calls are unsupported.
Wi-Fi power saving
Installation sets NetworkManager’s default wifi.powersave=2 (off), including in Basic. It takes effect at the next Wi-Fi connection. Explicit settings in existing profiles are preserved. Installation does not interrupt a network connection.
In Pro, Wi-Fi → Wi-Fi power saving changes the connected network’s setting immediately on the selected adapter and saves it permanently, across restarts and reconnections. New connections created through the interface start with power saving off.
Off is recommended for radio use because power saving can delay or interrupt voice traffic. It may slightly increase power consumption and does not guarantee flawless audio. Controls stay disabled for adapters that cannot report their state.
iw dev wlan0 get power_save shows the current state. In Basic, permanently change an existing profile with sudo nmcli connection modify uuid PROFIL-UUID 802-11-wireless.powersave 2; apply it immediately without reconnecting using sudo iw dev wlan0 set power_save off. Substitute the actual profile UUID and adapter name.
Si570 startup correction since 0.5.8
For an existing Si570 option, a panel update also installs the corrected persistent measurement service and its radio-start check. The saved control switch is retained; failed services are started again. Large system-time offsets are aligned only while RF is stopped. The cell remains stopped after installation and is started manually as usual. Fresh measurement windows must qualify again before correction resumes.
From 0.5.9, a provisional calculated frequency is also displayed during acquisition when sample windows are available. A displayed value does not enable correction: the current windows must still meet the quality requirements.
Chrony history in 0.5.10
From 0.5.10, chrony saves its source measurement histories on exit and every five minutes, and reloads them alongside the saved Pi frequency calibration at startup. Moving the disk to a different Pi archives the previous crystal model. Without a battery-backed clock, acquisition may still be necessary after power-off; Si570 correction continues to require current qualified measurement windows. Existing Si570 installations receive this configuration with the update; ordinary TCXO installations remain unchanged. A chrony service restart on the operator’s Pi successfully restored all four source histories while the cell remained running. A full power-cycle test is still pending.

