MediaWiki For Hamradio Analog/Digital and Debian v13 software/Raspberry PI v3/4/5 howto - Recent changes [en]

Hamradio/svxlink node/sv

FuzzyBot — Sun, 18 Oct 2026 16:15:42 GMT

Updating to match new version of source page

← Older revision		Revision as of 16:15, 18 October 2026
Line 183:		Line 183:
	</div>		</div>

	~~<div lang="en" dir="ltr" class="mw-content-ltr">~~		<div style="border-left:4px solid #5fd38a; background:#12211a; padding:10px 16px; margin:14px 0; border-radius:6px;">📥 '''Vill du ha hela?''' Ladda ner en komplett, sanerad uppsättning exempel-configar — <code>svxlink.conf</code>, <code>node_info.json</code>, <code>gpio.conf</code> och modulfilerna, alla hemligheter borttagna: [https://sa7aux.se/svxlink-config-example.zip svxlink-config-example.zip]. Packa upp i <code>/etc/svxlink/</code> och byt anropssignal, reflektor-host, <code>AUTH_KEY</code> och position till dina egna.</div>
	<div style="border-left:4px solid #5fd38a; background:#12211a; padding:10px 16px; margin:14px 0; border-radius:6px;">📥 '''~~Want the whole file~~?''' ~~Download the complete sanitised example config~~ — ~~all sections~~, ~~secrets blanked~~: [https://sa7aux.se/svxlink.~~conf.~~example ~~svxlink.conf~~.~~example~~]. ~~Save it as~~ <code>/etc/svxlink/~~svxlink.conf~~</code> ~~and change the callsign~~, ~~reflector~~ host ~~and~~ <code>AUTH_KEY</code> ~~to your own~~.~~</div>~~
	</div>

	Andra sektioner att titta på:		Andra sektioner att titta på:

Hamradio/svxlink node/en

FuzzyBot — Sun, 18 Oct 2026 16:08:45 GMT

Updating to match new version of source page

← Older revision		Revision as of 16:08, 18 October 2026
Line 155:		Line 155:
	EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>		EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>

	<div style="border-left:4px solid #5fd38a; background:#12211a; padding:10px 16px; margin:14px 0; border-radius:6px;">📥 '''Want the whole ~~file~~?''' Download ~~the~~ complete sanitised example ~~config~~ — all ~~sections,~~ secrets blanked: [https://sa7aux.se/svxlink.~~conf.~~example ~~svxlink~~.~~conf.example~~]. ~~Save it as~~ <code>/etc/svxlink/~~svxlink.conf~~</code> and change the callsign, reflector host ~~and~~ <code>AUTH_KEY</code> to your own.</div>		<div style="border-left:4px solid #5fd38a; background:#12211a; padding:10px 16px; margin:14px 0; border-radius:6px;">📥 '''Want the whole thing?''' Download a complete, sanitised set of example configs — <code>svxlink.conf</code>, <code>node_info.json</code>, <code>gpio.conf</code> and the module files, all secrets blanked: [https://sa7aux.se/svxlink-config-example.zip svxlink-config-example.zip]. Unzip into <code>/etc/svxlink/</code> and change the callsign, reflector host, <code>AUTH_KEY</code> and position to your own.</div>

	Other sections to glance at:		Other sections to glance at:

Hamradio/svxlink node

Sa7aux — Sun, 18 Oct 2026 16:08:12 GMT

Sa7aux marked Hamradio/svxlink node for translation

Hamradio/svxlink node/en

FuzzyBot — Sun, 18 Oct 2026 16:04:53 GMT

Updating to match new version of source page

← Older revision		Revision as of 16:04, 18 October 2026
Line 154:		Line 154:
	NODE_INFO_FILE=/etc/svxlink/node_info.json		NODE_INFO_FILE=/etc/svxlink/node_info.json
	EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>		EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>

			<div style="border-left:4px solid #5fd38a; background:#12211a; padding:10px 16px; margin:14px 0; border-radius:6px;">📥 '''Want the whole file?''' Download the complete sanitised example config — all sections, secrets blanked: [https://sa7aux.se/svxlink.conf.example svxlink.conf.example]. Save it as <code>/etc/svxlink/svxlink.conf</code> and change the callsign, reflector host and <code>AUTH_KEY</code> to your own.</div>

	Other sections to glance at:		Other sections to glance at:

Hamradio/svxlink node/sv

FuzzyBot — Sun, 18 Oct 2026 16:04:51 GMT

Updating to match new version of source page

← Older revision		Revision as of 16:04, 18 October 2026
Line 181:		Line 181:
	NODE_INFO_FILE=/etc/svxlink/node_info.json		NODE_INFO_FILE=/etc/svxlink/node_info.json
	EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>		EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>
			</div>

			<div lang="en" dir="ltr" class="mw-content-ltr">
			<div style="border-left:4px solid #5fd38a; background:#12211a; padding:10px 16px; margin:14px 0; border-radius:6px;">📥 '''Want the whole file?''' Download the complete sanitised example config — all sections, secrets blanked: [https://sa7aux.se/svxlink.conf.example svxlink.conf.example]. Save it as <code>/etc/svxlink/svxlink.conf</code> and change the callsign, reflector host and <code>AUTH_KEY</code> to your own.</div>
	</div>		</div>

Hamradio/svxlink node

Sa7aux — Sun, 18 Oct 2026 16:04:44 GMT

Sa7aux marked Hamradio/svxlink node for translation

Hamradio/svxlink node

Sa7aux — Sun, 18 Oct 2026 16:04:28 GMT

Sa7aux marked Hamradio/svxlink node for translation

Hamradio/svxlink node/en

FuzzyBot — Sun, 18 Oct 2026 15:54:49 GMT

Updating to match new version of source page

New page

{{DISPLAYTITLE:Build a SvxLink node from scratch (Raspberry Pi)}}
<languages/>

''A complete, hand-held walkthrough: from a blank microSD card to a working '''SvxLink''' node on a Raspberry Pi — download the OS, flash it with Wi-Fi and SSH already set, find the Pi on your network, log in, build SvxLink, drop in a config, and add a web dashboard. No prior Linux experience needed. Copy-paste friendly.''

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''What you'll end up with:''' a Raspberry Pi running SvxLink, connected to a '''SVXReflector''', with Swedish and English voice prompts, that you can see and control from a browser. Allow about an hour (most of it is the Pi compiling by itself).</div>

[[File:Svxlink_node_flow.png|center|frameless|920px|alt=Eight steps: download Raspberry Pi OS, flash with Pi Imager (hostname/SSH/Wi-Fi), boot, find IP, connect over SSH/PuTTY, install SvxLink, edit svxlink.conf, start it and add the dashboard.]]

__TOC__

== What you need ==

* A '''Raspberry Pi 3, 4 or 5''' (a Pi Zero 2 W works but is slow to compile).
* A '''microSD card''', 16 GB or larger, and a card reader on your PC.
* A '''sound interface''' for the radio side (USB sound card, a hat like the WM8960, or a DRA/repeater board) — not needed just to get the software running.
* Your '''callsign''' and a '''reflector login''' (host + AUTH_KEY) for the SVXReflector you want to join.

== Part 1 — Download Raspberry Pi OS ==

Get the '''64-bit Lite''' image of '''Raspberry Pi OS 13 (Trixie)''' — "Lite" has no desktop, which is what you want for a node.

* Easiest: install '''Raspberry Pi Imager''' (it downloads the OS for you): https://www.raspberrypi.com/software/
* Imager runs on Windows, macOS and Linux.

== Part 2 — Flash the SD card (with SSH + Wi-Fi pre-set) ==

This is the step that saves you a keyboard and monitor. In '''Raspberry Pi Imager''':

# '''Choose Device:''' your Pi model.
# '''Choose OS:''' ''Raspberry Pi OS (other)'' → '''Raspberry Pi OS Lite (64-bit)'''.
# '''Choose Storage:''' your SD card.
# Click '''Next''' → '''Edit Settings''' (the gear / "would you like to apply OS customisation?"). Set:

{| class="wikitable" style="width:100%;"
|-
! Setting !! What to put
|-
| '''Hostname''' || e.g. <code>svxnode</code> — you'll reach the Pi as <code>svxnode.local</code>.
|-
| '''Enable SSH''' || Yes → "Use password authentication" (simplest).
|-
| '''Username / password''' || pick your own, e.g. user <code>pi</code>. '''Write it down.'''
|-
| '''Configure wireless LAN''' || your Wi-Fi SSID + password, and your '''Wi-Fi country''' (important or Wi-Fi stays off).
|-
| '''Locale / timezone / keyboard''' || your country.
|}

Save, then '''Write'''. When it finishes, eject the card.

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ If you skip the Wi-Fi/SSH customisation, the Pi boots with no way in. Either redo this step, or plug in an Ethernet cable (SSH is still enabled only if you ticked it).</div>

== Part 3 — Boot the Pi ==

Put the card in the Pi, connect the radio/sound hardware if you have it, and power it on. The first boot takes '''a minute or two''' (it expands the filesystem and joins Wi-Fi). Give it time before looking for it.

== Part 4 — Find the Pi's IP address ==

You need the Pi's IP (or its <code>.local</code> name) to log in. Pick whichever works:

* '''Hostname (easiest):''' just use <code>svxnode.local</code> (the hostname you set + <code>.local</code>). Works on most home networks.
* '''Your router:''' open your router's admin page → the '''DHCP client / connected devices''' list → find <code>svxnode</code> and note its IP (e.g. <code>192.168.1.42</code>).
* '''Scan the network''' from your PC:
<pre>ping svxnode.local
# or scan the subnet (Linux/Mac): nmap -sn 192.168.1.0/24</pre>

== Part 5 — Connect over SSH ==

'''Windows:''' download and run '''PuTTY''' — https://www.putty.org/ . In '''Host Name''' type <code>svxnode.local</code> (or the IP), '''Port''' 22, '''Open'''. Accept the key warning the first time, then log in with the username/password you set.

'''macOS / Linux:''' just use a terminal:
<pre>ssh pi@svxnode.local</pre>

Once you're in, bring the system up to date:
<pre>sudo apt update && sudo apt full-upgrade -y</pre>

== Part 6 — Install SvxLink ==

SvxLink isn't in the Pi's default repos as a current build, so you compile it (the Pi does the work). This one script installs the build tools, fetches the source from GitHub, builds and installs it, and downloads the '''Swedish (sv_SE)''' and '''English (en_US)''' voice prompts. Paste it into the SSH session:

<pre>#!/bin/bash
set -e
cd ~
mkdir -p ./projects/svxlink
cd ./projects/svxlink

sudo apt update
sudo apt dist-upgrade -y
sudo apt autoremove -y

sudo apt install -y \
build-essential cmake git wget \
libgpiod3 libgpiod-dev \
alsa-utils \
libsigc++-2.0-dev libgsm1-dev libpopt-dev \
tcl8.6-dev \
libgcrypt20-dev libspeex-dev libasound2-dev libopus-dev librtlsdr-dev \
doxygen groff vorbis-tools curl \
qtbase5-dev qttools5-dev-tools qttools5-dev \
libjsoncpp-dev libcurl4-gnutls-dev libogg-dev \
sox

# system user for svxlink (ignored if it already exists)
if ! id -u svxlink >/dev/null 2>&1; then
sudo useradd -r -G audio,plugdev,dialout svxlink
fi

# fetch the source
if [ ! -d svxlink ]; then
git clone https://github.com/sm0svx/svxlink.git
fi

mkdir -p svxlink/src/build
cd svxlink/src/build
cmake -DCMAKE_INSTALL_PREFIX=/usr -DSYSCONF_INSTALL_DIR=/etc \
-DLOCAL_STATE_DIR=/var -DWITH_SYSTEMD=yes ..
make -j"$(nproc)"
make doc
sudo make install
sudo ldconfig

# voice prompts: Swedish + English
cd ~/projects/svxlink
cp svxlink/src/svxlink/scripts/filter_sounds.sh ./
cp svxlink/src/svxlink/scripts/play_sound.sh ./
[ -d svxlink-sounds-en_US-heather ] || git clone https://github.com/sm0svx/svxlink-sounds-en_US-heather.git
[ -d svxlink-sounds-sv_SE-elin ] || git clone https://github.com/sm0svx/svxlink-sounds-sv_SE-elin.git
sudo ./filter_sounds.sh svxlink-sounds-en_US-heather en_US
sudo ./filter_sounds.sh svxlink-sounds-sv_SE-elin sv_SE
cd /usr/share/svxlink/sounds
sudo tar xvjf ~/projects/svxlink/svxlink-sounds-en_US.tar.bz2
sudo tar xvjf ~/projects/svxlink/svxlink-sounds-sv_SE.tar.bz2</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 <code>make -j"$(nproc)"</code> builds on all CPU cores. On a Pi 3 the compile can take 20–40 minutes — that's normal. Go get a coffee; it's working.</div>

== Part 7 — Configure svxlink.conf ==

The config lives in <code>/etc/svxlink/svxlink.conf</code>. Edit it:
<pre>sudoedit /etc/svxlink/svxlink.conf</pre>

The parts you '''must''' set are the logic sections. The most important is the reflector connection — here is a working '''<code>[ReflectorLogic]</code>''' (secrets replaced with <code>CHANGE_ME</code>):

<pre>[ReflectorLogic]
TYPE=Reflector
ID=9
HOSTS=svx.sa7aux.se ; your reflector's hostname
CALLSIGN="MYCALL" ; your callsign
AUTH_KEY="CHANGE_ME_long_random_secret" ; the key your reflector expects
CERT_EMAIL=you@example.org ; for the auto TLS certificate
DEFAULT_TG=0
MONITOR_TGS=9,240,24016,24020,24021 ; talkgroups you want to hear
UDP_HEARTBEAT_INTERVAL=5
NODE_INFO_FILE=/etc/svxlink/node_info.json
EVENT_HANDLER=/usr/share/svxlink/events.tcl</pre>

Other sections to glance at:

{| class="wikitable" style="width:100%;"
|-
! Section !! What it's for
|-
| '''[GLOBAL]''' || Which logics load (<code>LOGICS=SimplexLogic,ReflectorLogic</code>), and the sound-prompt language — set <code>LANG=sv_SE</code> or <code>LANG=en_US</code>.
|-
| '''[SimplexLogic]''' || Your node's own callsign ID, DTMF commands, and which reflector logic it links to.
|-
| '''[Rx1] / [Tx1]''' || The audio devices and PTT/COS for your radio interface (ALSA device, squelch, CTCSS).
|-
| '''[LocationInfo]''' || Optional APRS beacon (position, frequency) — all commented out by default.
|}

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ '''Never publish your real <code>AUTH_KEY</code>, passwords or e-mail.''' The example above is deliberately blanked. Put your own values in, keep the file readable only by root, and don't paste the real file into forums or chats.</div>

== Part 8 — Start it and verify ==

Enable and start the node, then watch the log:
<pre>sudo systemctl enable --now svxlink
sudo systemctl status svxlink
sudo journalctl -u svxlink -f</pre>

In the log you should see it connect to the reflector and announce in your chosen language. If someone talks on a monitored talkgroup, you'll hear it (and see it in the log). <code>Ctrl-C</code> stops following the log (the service keeps running).

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Setting up a '''reflector''' instead of a node? The same build also installed <code>svxreflector</code> — enable that service (<code>sudo systemctl enable --now svxreflector</code>) and configure <code>/etc/svxlink/svxreflector.conf</code>.</div>

== Add the web dashboard ==

Once the node runs, give yourself a browser page to see status and switch talkgroups — install the '''[[Hamradio/svxspot_dashboard|SvxSpot Dashboard]]''' on the same Pi. It reads this same <code>svxlink.conf</code> and controls the node for you.

== Troubleshooting ==

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Check
|-
| '''Can't reach <code>svxnode.local</code>''' || Use the IP from your router instead. On some networks <code>.local</code> (mDNS) is blocked.
|-
| '''SSH "connection refused"''' || SSH wasn't enabled in Imager, or the Pi isn't booted yet — wait, or re-flash with SSH ticked.
|-
| '''No Wi-Fi''' || Wrong Wi-Fi country in Imager, or wrong SSID/password. Re-flash, or use Ethernet.
|-
| '''<code>make</code> fails''' || Usually a missing build package — re-run the <code>apt install</code> line from Part 6, then <code>make</code> again.
|-
| '''Won't connect to the reflector''' || Wrong <code>HOSTS</code>, <code>CALLSIGN</code> or <code>AUTH_KEY</code> — check with the reflector operator. Watch <code>journalctl -u svxlink -f</code>.
|-
| '''No audio / no voice prompts''' || Check <code>LANG</code> in <code>[GLOBAL]</code>, and that the sound tarballs unpacked into <code>/usr/share/svxlink/sounds</code>.
|}

== See also ==

* [[Hamradio/svxspot_dashboard|SvxSpot Dashboard]] — the browser control panel for this node.
* [[Hamradio/chan_svx|chan_svx]] / [[Hamradio/chan_svx_sat|chan_svx_sat]] — bridge an AllStarLink node to a SVXReflector instead.
* [[Hamradio]] — the rest of the digital-voice how-tos.
* Author: '''SA7AUX''' <bjorne@sa7aux.se>. SvxLink © SM0SVX, GNU GPL.

[[Category:Ham radio]]

Hamradio/svxlink node

Sa7aux — Sun, 18 Oct 2026 15:54:43 GMT

Sa7aux marked Hamradio/svxlink node for translation

File:Svxlink node flow.png

Sa7aux — Sun, 18 Oct 2026 15:52:49 GMT

Sa7aux uploaded File:Svxlink node flow.png == Summary == SvxLink node setup flow

New page

== Summary ==
SvxLink node setup flow

User:Sa7aux/svxspot dashboard/sv

Delete page script — Sun, 18 Oct 2026 15:11:38 GMT

Delete page script deleted page User:Sa7aux/svxspot dashboard/sv moved to Hamradio / superseded

User:Sa7aux/chan svx

Delete page script — Sun, 18 Oct 2026 15:11:38 GMT

Delete page script deleted page User:Sa7aux/chan svx moved to Hamradio / superseded

User:Sa7aux/chan svx sat

Delete page script — Sun, 18 Oct 2026 15:11:38 GMT

Delete page script deleted page User:Sa7aux/chan svx sat moved to Hamradio / superseded

User:Sa7aux/darthvader

Delete page script — Sun, 18 Oct 2026 15:11:38 GMT

Delete page script deleted page User:Sa7aux/darthvader moved to Hamradio / superseded

User:Sa7aux/svxspot dashboard

Delete page script — Sun, 18 Oct 2026 15:11:38 GMT

Delete page script deleted page User:Sa7aux/svxspot dashboard moved to Hamradio / superseded

User:Sa7aux/reflector dashboard

Delete page script — Sun, 18 Oct 2026 15:11:38 GMT

Delete page script deleted page User:Sa7aux/reflector dashboard moved to Hamradio / superseded

Hamradio/svxspot dashboard/en

FuzzyBot — Sun, 18 Oct 2026 15:10:22 GMT

Updating to match new version of source page

New page

{{DISPLAYTITLE:SvxSpot Dashboard — control your SvxLink node from a browser}}
<languages/>

''A beginner's guide to '''SvxSpot Dashboard''': a small web page you install on your SvxLink node (a Raspberry Pi hotspot or an FM repeater) that shows what the node is doing and lets you change talkgroup, edit the config, and more — from a phone or PC. One <code>.deb</code> sets up the whole web stack for you.''

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''In one sentence:''' install one package on your node and you get a web page at '''<code>http://svxspot.local/</code>''' that shows live status / last-heard / current talkgroup and gives you one-click TG switching, a DTMF keypad, and editors for <code>svxlink.conf</code>, EchoLink, RF and audio — plus Wi-Fi setup and reboot/shutdown buttons.</div>

[[File:Svxspot_dashboard_arch.png|center|frameless|920px|alt=Browser talks HTTP to nginx on the node, which runs php-fpm and the PHP dashboard; it reads svxlink.conf and the log, and writes TG/DTMF to the SvxLink control pipe. An optional MQTT agent lets an external portal switch TG too.]]

__TOC__

== Do I need this? ==

* '''You run a SvxLink node''' — a "SvxSpot" hotspot or an FM repeater — and you want to '''see and control it from a browser''' instead of SSH and a text editor.
* It installs on the '''same box as SvxLink''' (a Raspberry Pi or any Debian machine).
* Optional extra: let an '''external portal switch your talkgroup over MQTT''' (handy for a club's control panel). Off by default — a plain LAN dashboard needs none of it.

== What you need first ==

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 The dashboard '''controls''' SvxLink — it doesn't replace it. SvxLink must already be installed and running on the node.</div>

* '''A SvxLink node''' running on Debian 12/13 or Raspberry Pi OS (bookworm/trixie), on a Pi 3/4/5, Pi Zero 2 W, or any Debian box.
* '''SvxLink installed and running''' with <code>/etc/svxlink/svxlink.conf</code> (package <code>svxlink-server</code>).
* For one-click '''talkgroup / DTMF control''' from the web, this line in your logic section of <code>svxlink.conf</code>:
<pre>DTMF_CTRL_PTY=/var/lib/svxlink/dtmf_svx</pre>
* '''(Optional, MQTT only)''' broker host, port (usually 8883) and a username/password — only if you want remote portal control.

'''You do not''' install nginx or PHP yourself — the package pulls them in and configures them for you.

== Install ==

'''Easiest — the one-line installer''' (downloads the newest release and installs it; apt fetches nginx/PHP automatically):
<pre>curl -fsSL https://git.sa7aux.se/bjorne/svxspot-dashboard/raw/branch/main/install.sh | sudo bash</pre>

'''Or install a <code>.deb</code> you copied over:'''
<pre>sudo apt install ./svxspot-dashboard_<version>_all.deb</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Use whatever version the release page shows in the filename (e.g. <code>svxspot-dashboard_1.0.1_all.deb</code>). The package is architecture-independent (<code>_all</code>) — the same file works on a Pi and on x86-64.</div>

=== What the installer asks you ===

A normal install pops up a few questions (debconf). Sensible defaults are offered — you can just press Enter:

{| class="wikitable" style="width:100%;"
|-
! Question !! What to enter
|-
| '''Node callsign''' || Auto-detected from <code>svxlink.conf</code>. Accept it.
|-
| '''Dashboard admin user''' || Login name for the control pages. Default <code>admin</code>.
|-
| '''Admin password''' || Type one, or leave '''empty''' to have a random 16-character password generated and '''printed once''' at the end — write it down.
|-
| '''Enable MQTT remote control?''' || Default '''no'''. Say yes only if a portal will control this node; then it asks for broker host / username / password.
|}

=== What it sets up for you ===

The installer does all the plumbing (and it's safe to re-run with <code>sudo dpkg-reconfigure svxspot-dashboard</code>):

* installs and configures '''nginx''' (a site on port 80) and '''php-fpm''';
* creates the admin login (bcrypt <code>htpasswd</code>);
* installs tightly-scoped '''sudo''' rules so the web user can save config and restart SvxLink — and nothing else;
* adds the web user to the <code>audio, tty, dialout, svxlink</code> groups;
* stages the optional '''MQTT agent''' (a systemd service) — enabled only if you turned MQTT on.

At the end it prints a banner with your '''dashboard URL, admin user, and (if generated) the password'''.

== Open it ==

* In a browser on the same network go to '''<code>http://svxspot.local/</code>''' (or <code>http://<node-ip>/</code> if the <code>.local</code> name doesn't resolve).
* The '''status page needs no login.''' The '''control pages''' (TG, config editor, power, Wi-Fi, …) ask for the admin user/password you set.

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ If you flashed the ready-made '''SvxSpot SD-card image''', the factory logins are SSH <code>svxspot</code> / <code>raspberry</code> and dashboard <code>admin</code> / <code>svxspot</code>. '''Change both immediately''' (see [[#Change the admin password|below]]).</div>

== What's on the dashboard ==

{| class="wikitable" style="width:100%;"
|-
! Page !! What it does
|-
| '''Start / Status''' || Live status, last-heard stations, current talkgroup, quick-button keypad. (No login.)
|-
| '''TG''' + '''DTMF keypad''' || Switch talkgroup with one tap; send raw DTMF.
|-
| '''Config''' || Edit <code>svxlink.conf</code> in the browser with help text; every save makes a timestamped backup and restarts SvxLink.
|-
| '''EchoLink''' · '''RF''' (SA818) · '''Audio''' || Editors for EchoLink, radio-module frequency/squelch, and audio levels.
|-
| '''Wi-Fi / Network''' || Join a Wi-Fi network / set networking.
|-
| '''Power''' || Reboot, shut down, or restart SvxLink.
|-
| '''Remote Control (MQTT)''' || Turn the optional MQTT agent on/off and set the broker.
|-
| '''Node info''' · '''Map''' · '''Log''' || Node metadata, map, and the SvxLink log.
|}

== How it controls SvxLink (plain version) ==

You don't need to know this to use it, but it helps when troubleshooting: the dashboard '''reads''' <code>/etc/svxlink/svxlink.conf</code> and <code>/var/log/svxlink</code> to show status, and '''controls''' the node by writing DTMF strings (e.g. <code>91<tg>#</code> to switch TG) to the control pipe <code>/var/lib/svxlink/dtmf_svx</code>. Config edits are saved and SvxLink is restarted through the narrow <code>sudo</code> rules. That's it — no database.

== Optional: remote control over MQTT ==

If you enabled MQTT, a small systemd agent (<code>svxnode-mqtt</code>) makes an '''outbound TLS connection''' to your broker on port '''8883''' (nothing to open in your router). An external portal publishes a talkgroup command, and the agent writes the same <code>91<tg>#</code> to the DTMF pipe — exactly what the web TG button does. Enable/disable it from the dashboard's '''Remote Control''' page, or re-run <code>sudo dpkg-reconfigure svxspot-dashboard</code>.

== Change the admin password ==

No reconfigure needed — nginx re-reads the file on every request:
<pre>sudo htpasswd -B /etc/nginx/svxspot-dashboard.htpasswd admin</pre>
(Add <code>-c</code> to start a fresh file with only that user.)

== Troubleshooting ==

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Check
|-
| '''Page won't load''' || <code>systemctl status nginx</code>, <code>sudo nginx -t</code>, and <code>ls /etc/nginx/sites-enabled/</code> (should list svxspot-dashboard). Still broken → <code>sudo dpkg-reconfigure svxspot-dashboard</code>.
|-
| '''502 Bad Gateway''' || php-fpm is down → <code>sudo systemctl restart php*-fpm</code> (use your actual version, e.g. <code>php8.4-fpm</code>).
|-
| '''Password refused''' || <code>sudo htpasswd -cB /etc/nginx/svxspot-dashboard.htpasswd admin</code> (<code>-c</code> recreates it).
|-
| '''Status page empty / no callsign''' || SvxLink isn't running or has no config → <code>systemctl status svxlink</code>, <code>tail -n 30 /var/log/svxlink</code>.
|-
| '''TG buttons do nothing''' || Check <code>grep DTMF_CTRL_PTY /etc/svxlink/svxlink.conf</code> and that <code>/var/lib/svxlink/dtmf_svx</code> exists. Then <code>sudo dpkg-reconfigure svxspot-dashboard</code> and restart php-fpm.
|-
| '''“Save” permission error''' || <code>sudo visudo -cf /etc/sudoers.d/svxspot-dashboard</code> must say "parsed OK".
|-
| '''MQTT stays inactive''' || <code>journalctl -u svxnode-mqtt -n 30 --no-pager</code> — usually wrong password, wrong host, or port 8883 firewalled.
|}

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Your installed PHP version isn't fixed — examples here use <code>php8.4-fpm</code> but your box might run <code>php8.2-fpm</code>. Substitute your own: <code>ls /run/php/php*-fpm.sock</code>.</div>

== Removing / starting over ==

* Keep your settings: <code>sudo apt remove svxspot-dashboard</code>.
* Wipe everything (incl. MQTT credentials): <code>sudo apt purge svxspot-dashboard</code>, then reinstall.

== See also ==

* [[Hamradio]] — SvxLink and the rest of the digital-voice how-tos.
* Author: '''SA7AUX''' <bjorne@sa7aux.se>. GPL-3.0-or-later. Based on SVXLink-Dashboard-V2 / Guru-RF.

[[Category:Ham radio]]

Hamradio/chan svx sat/en

FuzzyBot — Sun, 18 Oct 2026 15:10:18 GMT

Updating to match new version of source page

New page

{{DISPLAYTITLE:chan_svx_sat — AllStar ↔ SVXReflector, the easy way}}
<languages/>

''A hand-held, step-by-step guide to bridging an '''AllStarLink 3''' node straight to a '''SVXReflector''' with '''chan_svx_sat''' — install it, get it connected, and get the audio right. No prior SvxLink knowledge needed. Copy-paste friendly.''

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''In one sentence:''' <code>chan_svx_sat</code> is an Asterisk channel driver that lets your AllStar node talk Opus directly to a SVXReflector — so you drop the old <code>chan_usrp</code> → svxlink hop and the extra vocoder tandem that came with it.</div>

[[File:Chan_svx_sat_architecture.png|center|frameless|860px|alt=Before: app_rpt via USRP and svxlink to the reflector. After: app_rpt straight to the reflector over one Opus stream.]]
<div style="text-align:center; color:#9aa0a6; font-style:italic; margin:-6px 0 14px;">One Opus hop instead of two transcodes. Less latency, cleaner audio.</div>

__TOC__

== Do I even need this? ==

* '''You run an AllStarLink 3 node''' (on a Raspberry Pi or x86) '''and''' you want it on a '''SVXReflector''' talkgroup.
* Today you probably bridge it with <code>chan_usrp</code> → <code>svxlink</code>. That works, but it transcodes the audio twice and adds a box to babysit.
* <code>chan_svx_sat</code> replaces that whole hop with '''one''' driver. The audio path becomes just PCM ↔ Opus, once.

If you are '''not''' going to a SvxReflector — e.g. you only link AllStar-to-AllStar, or you use DMR/YSF — you don't need this. See [[Hamradio]] for those.

== Words you'll see (plain-language glossary) ==

{| class="wikitable" style="width:100%;"
|-
! Term !! What it means here
|-
| '''AllStarLink 3 (ASL3)''' || The VoIP linking system built on Asterisk. Your node runs <code>asl3-asterisk</code>.
|-
| '''app_rpt''' || The Asterisk application that '''is''' your repeater/node controller (COS, PTT, IDs, links).
|-
| '''SVXReflector''' || A server that joins many SvxLink-style clients on shared '''talkgroups'''. Your node logs in to it.
|-
| '''Talkgroup (TG)''' || A "channel" on the reflector. You transmit on one TG and hear whoever else is on it.
|-
| '''Opus''' || The audio codec on the wire between your node and the reflector. One transcode, 8 kHz, 20 ms frames.
|-
| '''Trunk''' || One TCP connection (login) to the reflector. Several nodes can share one trunk — see [[#Several nodes on one login|below]].
|-
| '''Section''' || A <code>[block]</code> in <code>svx_sat.conf</code>. '''One section = one node = one TG.'''
|}

== What you need before you start ==

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Tick all four. If one is missing, fix it first — the bridge can't work without them.</div>

# '''A working AllStarLink 3 node.''' Check: <code>asterisk -V</code> shows <code>Asterisk 22.x+asl3-...</code>.
# '''A 64-bit OS.''' Debian 12 (bookworm) or 13 (trixie), on x86-64 or arm64 (Pi 3/4/5). Check: <code>dpkg --print-architecture</code> and <code>. /etc/os-release; echo $VERSION_CODENAME</code>. ''(The Pi Zero 2 W is intentionally not supported — heat + Wi-Fi.)''
# '''A reflector login of your own''' — a dedicated login + auth-key, '''not''' shared with svxlink or another node. Sharing one gets the other kicked off. SvxReflector logins are '''upper-case callsigns'''.
# '''The reflector is reachable.''' Check: <code>nc -vz REFLECTOR_HOST 5300</code>.

The worked example below is a real node: '''AllStar node 1999''' bridging to a reflector at '''172.16.1.1:5300''', talkgroup '''24016'''. Swap in your own host / login / TG everywhere you see them.

== How it all fits together ==

Two small config files on the node, and one matching <code>SECRET</code> line on the reflector. That is the entire wiring:

[[File:Chan_svx_sat_topology.png|center|frameless|900px|alt=rpt.conf points at a section in svx_sat.conf, which logs in to the reflector whose SECRET must match.]]
<div style="text-align:center; color:#9aa0a6; font-style:italic; margin:-6px 0 14px;"><code>rpt.conf</code> → a section in <code>svx_sat.conf</code> → a login the reflector recognises.</div>

== Step 1 — Install the package ==

Pick the <code>.deb</code> that matches your OS '''and''' architecture:

{| class="wikitable"
|-
! OS / arch !! Package
|-
| trixie x86-64 || <code>asl3-chan-svx-sat_<ver>~trixie_amd64.deb</code>
|-
| trixie arm64 (Pi) || <code>asl3-chan-svx-sat_<ver>~trixie_arm64.deb</code>
|-
| bookworm x86-64 || <code>asl3-chan-svx-sat_<ver>~bookworm_amd64.deb</code>
|-
| bookworm arm64 (Pi) || <code>asl3-chan-svx-sat_<ver>~bookworm_arm64.deb</code>
|}

<pre>sudo apt install ./asl3-chan-svx-sat_<ver>~<os>_<arch>.deb</pre>

Dependencies (<code>asl3-asterisk</code>, <code>libopus0</code>, <code>libssl3</code>) resolve automatically. The package installs the module, a sample config, this kind of documentation under <code>/usr/share/doc/asl3-chan-svx-sat/</code>, and adds a '''commented''' load line to <code>modules.conf</code> for you to enable in Step 4. '''Nothing loads or connects yet.'''

== Step 2 — Create the reflector config ==

Copy the sample and open it for editing:

<pre>sudo cp /etc/asterisk/svx_sat.conf.sample /etc/asterisk/svx_sat.conf
sudo chown asterisk:asterisk /etc/asterisk/svx_sat.conf
sudo chmod 640 /etc/asterisk/svx_sat.conf # it holds your reflector password
sudoedit /etc/asterisk/svx_sat.conf</pre>

Make it look like this (name the section after the node — tidy and unambiguous):

<pre>[1999]
host = 172.16.1.1 ; reflector hostname or IP
port = 5300 ; reflector port (default 5300)
login = SA7AUX-AC ; your OWN login, UPPER-CASE, not shared
password = CHANGE_ME ; your reflector auth-key
callsign = SA7AUX ; name shown to the reflector
tg = 24016 ; talkgroup to select (TX + primary RX)</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''The login + password must match the reflector.''' On the reflector's <code>[SATELLITE]</code> section there must be a line <code>SECRET_SA7AUX-AC=CHANGE_ME</code> (case-sensitive). If you run the reflector too: add/change the <code>SECRET_</code> line and '''restart the reflector''' — it only reads secrets at startup.</div>

The <code>callsign</code> is shown as the node's name '''if it is free''' on the reflector right now; on a collision (or if left empty) it falls back to <code>ASL-<section></code> (e.g. <code>ASL-1999</code>), re-checked automatically as names free up.

== Step 3 — Point the node at it ==

In <code>/etc/asterisk/rpt.conf</code>, in your node's stanza, '''comment out the old rxchannel — never delete it''' — and add the SVX line:

<pre>[1999](node-main)
; rxchannel = USRP/127.0.0.1:4001:4002 ; old bridge, kept so you can revert
rxchannel = SVXSAT/1999 ; chan_svx_sat -> section [1999]</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''Want it to survive package upgrades?''' Put the node stanza in <code>/etc/asterisk/custom/rpt.conf</code> instead — ASL3 includes that file and never overwrites it. Use the direct edit above for a quick change; use <code>custom/</code> if you want your config to survive <code>asl3-asterisk</code> updates cleanly.</div>

== Step 4 — Enable the module ==

ASL3 has <code>autoload = no</code>, so the module must be listed by hand. The package added a '''commented''' line — turn it on. '''It must live inside the <code>[modules]</code> section''' (a <code>load</code> line after a later section is silently ignored):

<pre>sudo sed -i 's/^; *load = chan_svx_sat.so/load = chan_svx_sat.so/' /etc/asterisk/modules.conf
grep -n '^load = chan_svx_sat.so' /etc/asterisk/modules.conf # confirm it's active</pre>

== Step 5 — Apply and verify ==

An <code>rxchannel</code> change needs app_rpt to re-init, so restart Asterisk, then check:

<pre>sudo asterisk -rx "core restart now"
sudo asterisk -rx "svxsat show"</pre>

A healthy bridge looks like this — '''<code>CONNECTED</code> means you're done with the basic hookup''':

[[File:Chan_svx_sat_svxsat_show.png|center|frameless|900px|alt=Annotated svxsat show output explaining CONNECTED, txframes, rxframes, starts/stops, fec and plc.]]

Key up on the node → <code>txframes</code> climbs and the reflector opens the talker on your TG. When someone else talks on the TG → <code>rxframes</code> climbs. Done. The rest of this page is tuning and extras.

== Getting the audio right ==

This is where most people get stuck, so take it slow. '''Only the yellow stages have knobs''' — everything grey is automatic.

[[File:Chan_svx_sat_audio_path.png|center|frameless|920px|alt=The TX and RX audio chains showing which stages are tunable (gain, AGC, jitter, tx_hold) and which are automatic (limiter, Opus FEC/PLC).]]

All of these live in the node's section in <code>svx_sat.conf</code>. '''After changing any of them, run <code>sudo asterisk -rx "core restart now"</code>.'''

=== The four audio knobs ===

{| class="wikitable" style="width:100%;"
|-
! Setting !! Default !! What it does
|-
| <code>tx_gain</code> || <code>0</code> || Preamp on TX (node → reflector), in dB. Raise if others say you're quiet; lower if they say you clip.
|-
| <code>rx_gain</code> || <code>0</code> || Preamp on RX (reflector → node), in dB. Raise if the reflector audio is too quiet on your repeater.
|-
| <code>tx_agc</code> / <code>rx_agc</code> || <code>no</code> || Automatic gain control. Turn '''on''' to even out loud/quiet stations. <code>yes</code> or <code>no</code>.
|-
| <code>bitrate</code> || <code>16000</code> || Opus bitrate in bit/s. Leave it unless you have a reason.
|}

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 A '''limiter is always on''' in both directions — it stops the audio clipping even if you raise the gain too far. '''Opus inband FEC + PLC''' are always on too: a lost packet is rebuilt from the next one's FEC, and an underrun is concealed instead of clicking. You don't configure any of that.</div>

=== "My audio is X → do Y" ===

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Fix
|-
| Others say '''you're too quiet''' || Raise <code>tx_gain</code> a few dB at a time (e.g. <code>3</code>, then <code>6</code>).
|-
| Others say '''you clip / distort''' || Lower <code>tx_gain</code> a notch. The limiter guards the peak, but clean input is better.
|-
| '''Reflector audio too quiet''' on your repeater || Raise <code>rx_gain</code> a few dB.
|-
| '''Loud and quiet stations''' are wildly uneven || Turn on <code>rx_agc = yes</code> (and/or <code>tx_agc = yes</code>).
|-
| '''Choppy / chopped''' audio going out || See [[#The link flaps or chops|the tx_hold fix below]].
|-
| Crackle/dropouts coming '''in''' on a poor link || Raise <code>jitter</code> (see below). FEC/PLC already help; this adds headroom.
|}

=== Two more knobs: tx_hold and jitter ===

{| class="wikitable" style="width:100%;"
|-
! Setting !! Default !! What it does
|-
| <code>tx_hold</code> || <code>250</code> || '''TalkerStop hold time''', in ms. A brief unkey/rekey mid-over (COS flicker, link hangtime) would otherwise close and reopen the reflector talker and chop the audio. The hold keeps it open across the gap. <code>0</code> = stop immediately on unkey.
|-
| <code>jitter</code> || <code>40</code> || '''Jitter-buffer prefill''', in ms. Higher = smoother on a poor/long link, but more latency. <code>0</code> = minimal (fine on a clean LAN). Max 500.
|}

<div id="The link flaps or chops"></div>
'''If audio going out is chopped:''' run <code>svxsat show</code> and watch <code>starts</code>/<code>stops</code>. '''One each per over is healthy.''' Many per over means your key is flapping — raise <code>tx_hold</code> (try <code>400</code>).

=== Optional: listen to extra talkgroups ===

<pre>monitor = 24020, 9990 ; extra TGs you HEAR (RX only); TX still goes to 'tg'</pre>

== Keep it up — forever ==

Two independent things stay up: the '''reflector link''' and the '''AllStar node-to-node link'''.

* '''The reflector link is automatic.''' chan_svx_sat reconnects on its own (TCP + UDP heartbeats, backoff after any drop). Nothing to configure; <code>svxsat show</code> goes back to <code>CONNECTED</code> within seconds of any outage.
* '''Keep the AllStar node linked to a hub?''' Use app_rpt's permanent connect, which re-establishes itself:

<pre>sudo asterisk -rx "rpt cmd 1999 ilink 13 403870" # 13 = permanent, transceive</pre>

'''Link automatically at boot''' via the node stanza:

<pre>[1999](node-main)
rxchannel = SVXSAT/1999
startup_macro = *3403870 ; auto-connect to 403870 (transceive) on startup</pre>

'''Belt-and-suspenders cron''' (<code>ilink 3</code> is idempotent — a no-op if already linked):

<pre># keep node 1999 linked to 403870 every 2 minutes
*/2 * * * * /usr/sbin/asterisk -rx "rpt cmd 1999 ilink 3 403870" >/dev/null 2>&1</pre>

== Bonus: change talkgroup from the radio (DTMF) ==

You can move the node to another TG live — over RF with DTMF, gated by a PIN — then drop back. Handy for pushing a bulletin/net out on a different TG, then reverting.

[[File:Chan_svx_sat_tg_control.png|center|frameless|900px|alt=DTMF dial pattern star-855 plus PIN plus action digit, with a table of actions and the control flow.]]

'''Dial pattern:''' <code>*855</code> + '''PIN''' + action. Put the commands in <code>rpt.conf</code> under <code>[functions]</code> (PIN is the control code — a wrong PIN simply does nothing). Default PIN is <code>0000</code> — '''change it before use''':

<pre>; /etc/asterisk/rpt.conf — base 855, PIN 0000 (CHANGE IT!)
[functions]
85500001 = cmd,asterisk -rx "svxsat settg 403872 3149060" ; *855 0000 1 -> bulletin TG
85500002 = cmd,asterisk -rx "svxsat settg 403872 3149070" ; *855 0000 2 -> another TG
85500000 = cmd,asterisk -rx "svxsat revert 403872" ; *855 0000 0 -> default TG
85500009 = cmd,asterisk -rx "svxsat down 403872" ; *855 0000 9 -> link down
85500008 = cmd,asterisk -rx "svxsat up 403872" ; *855 0000 8 -> link up</pre>

Set the default TG and an auto-revert timeout in <code>svx_sat.conf</code>:

<pre>[403872]
tg = 3149050 ; the DEFAULT TG (revert/up target)
tg_timeout = 30 ; minutes on another TG before auto-revert (0 = off)</pre>

A temporary TG '''always''' drops back to default on a reboot, a reconnect, or after <code>tg_timeout</code> — so a forgotten switch never strands the node.

== Several nodes on one login ==

Give several sections the '''same''' <code>login</code> + <code>password</code> (and a <code>tg</code> each) and they multiplex onto '''one''' reflector trunk — one handshake, one heartbeat — while each still appears as its own node with its own callsign and TG. Sections with '''different''' logins open separate trunks.

<pre>[403872]
host = reflector.example.org
login = SA7AUX-N ; SAME login -> shared trunk
password = CHANGE_ME ; SAME secret
callsign = SA7AUX-1
tg = 24016

[403873]
host = reflector.example.org
login = SA7AUX-N ; SAME login -> same connection
password = CHANGE_ME
callsign = SA7AUX-2
tg = 24021 ; different TG per node</pre>

== Troubleshooting ==

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Check
|-
| <code>svxsat show</code> empty / "No such command" / node has no rxchannel || Is <code>load = chan_svx_sat.so</code> enabled '''inside <code>[modules]</code>'''? Did you <code>core restart now</code>?
|-
| <code>down</code> instead of <code>CONNECTED</code> || Host/port reachable? login/password correct? Watch: <code>sudo tail -f /var/log/asterisk/messages.log | grep -i svx</code>
|-
| <code>auth rejected: Invalid callsign</code> || Login must be a valid '''upper-case''' callsign, and the account must exist on the reflector.
|-
| <code>auth rejected: Access denied</code> || Wrong password, or the login isn't registered on the reflector (<code>SECRET_</code> missing / reflector not restarted).
|-
| <code>txframes</code> climbs but nobody hears you || Is the '''listening''' client actually selecting/monitoring the same TG?
|-
| Choppy audio out, <code>starts</code> climbing many-per-over || Key/unkey flapping → raise <code>tx_hold</code> (e.g. <code>400</code>).
|-
| <code>txbadsize</code> climbing || app_rpt is feeding non-slin frames — check the node's audio path.
|-
| Loads but refuses ("compile-time options") || The package must match the installed <code>asl3-asterisk</code> version — install the deb for your exact OS.
|}

== Reverting ==

# Restore the old <code>rxchannel</code> (uncomment it) and comment <code>rxchannel = SVXSAT/...</code>.
# Comment <code>load = chan_svx_sat.so</code> in <code>modules.conf</code>.
# <code>sudo asterisk -rx "core restart now"</code>.

Remove entirely: <code>sudo apt remove asl3-chan-svx-sat</code> (add <code>--purge</code> to also drop the sample config and the <code>modules.conf</code> line).

== See also ==

* [[Hamradio]] — all the digital-voice and gateway how-tos.
* Author / bug reports: '''SA7AUX''' <bjorne@sa7aux.se>. GNU GPL v2.

[[Category:Ham radio]]

Hamradio/chan svx/en

FuzzyBot — Sun, 18 Oct 2026 15:10:18 GMT

Updating to match new version of source page

New page

{{DISPLAYTITLE:chan_svx — AllStar ↔ SVXReflector, the easy way}}
<languages/>

''A hand-held, step-by-step guide to bridging an '''AllStarLink 3''' node straight to a '''SVXReflector''' with '''chan_svx''' — install it, get it connected, and get the audio right. No prior SvxLink knowledge needed. Copy-paste friendly.''

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''In one sentence:''' <code>chan_svx</code> is an Asterisk channel driver that lets your AllStar node talk Opus directly to a SVXReflector — so you drop the old <code>chan_usrp</code> → svxlink hop and the extra vocoder tandem that came with it.</div>
<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ '''Two sister drivers — pick the right one.''' <code>chan_svx</code> (this page) joins the reflector as a '''SvxLink client''' (one login = one TG). Its sibling <code>chan_svx_sat</code> joins as a '''satellite/trunk''' and can carry '''several nodes/TGs on one login'''. If you want the trunk, read [[Hamradio/chan_svx_sat|the chan_svx_sat how-to]] instead.</div>

[[File:Chan_svx_architecture.png|center|frameless|860px|alt=Before: app_rpt via USRP and svxlink to the reflector. After: app_rpt straight to the reflector over one Opus stream.]]
<div style="text-align:center; color:#9aa0a6; font-style:italic; margin:-6px 0 14px;">One Opus hop instead of two transcodes. Less latency, cleaner audio.</div>

__TOC__

== Do I even need this? ==

* '''You run an AllStarLink 3 node''' (on a Raspberry Pi or x86) '''and''' you want it on a '''SVXReflector''' talkgroup.
* Today you probably bridge it with <code>chan_usrp</code> → <code>svxlink</code>. That works, but it transcodes the audio twice and adds a box to babysit.
* <code>chan_svx</code> replaces that whole hop with '''one''' driver. The audio path becomes just PCM ↔ Opus, once.

If you are '''not''' going to a SvxReflector — e.g. you only link AllStar-to-AllStar, or you use DMR/YSF — you don't need this. See [[Hamradio]] for those.

== Words you'll see (plain-language glossary) ==

{| class="wikitable" style="width:100%;"
|-
! Term !! What it means here
|-
| '''AllStarLink 3 (ASL3)''' || The VoIP linking system built on Asterisk. Your node runs <code>asl3-asterisk</code>.
|-
| '''app_rpt''' || The Asterisk application that '''is''' your repeater/node controller (COS, PTT, IDs, links).
|-
| '''SVXReflector''' || A server that joins many SvxLink-style clients on shared '''talkgroups'''. Your node logs in to it.
|-
| '''Talkgroup (TG)''' || A "channel" on the reflector. You transmit on one TG and hear whoever else is on it.
|-
| '''Opus''' || The audio codec on the wire between your node and the reflector. One transcode, 8 kHz, 20 ms frames.
|-
| '''Client''' || chan_svx joins the reflector as a normal SvxLink '''client''' — one login, one TG, one stream.
|-
| '''Section''' || A <code>[block]</code> in <code>svx.conf</code>. '''One section = one node = one TG.'''
|}

== What you need before you start ==

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Tick all four. If one is missing, fix it first — the bridge can't work without them.</div>

# '''A working AllStarLink 3 node.''' Check: <code>asterisk -V</code> shows <code>Asterisk 22.x+asl3-...</code>.
# '''A 64-bit OS.''' Debian 12 (bookworm) or 13 (trixie), on x86-64 or arm64 (Pi 3/4/5). Check: <code>dpkg --print-architecture</code> and <code>. /etc/os-release; echo $VERSION_CODENAME</code>. ''(The Pi Zero 2 W is intentionally not supported — heat + Wi-Fi.)''
# '''A reflector login of your own''' — a dedicated login + auth-key, '''not''' shared with svxlink or another node. Sharing one gets the other kicked off. SvxReflector logins are '''upper-case callsigns'''.
# '''The reflector is reachable.''' Check: <code>nc -vz REFLECTOR_HOST 5300</code>.

The worked example below is a real node: '''AllStar node 1999''' bridging to a reflector at '''172.16.1.1:5300''', talkgroup '''24016'''. Swap in your own host / login / TG everywhere you see them.

== How it all fits together ==

Two small config files on the node, and a login the reflector recognises. That is the entire wiring:

[[File:Chan_svx_topology.png|center|frameless|900px|alt=rpt.conf points at a section in svx.conf, which logs in to the reflector as a client.]]
<div style="text-align:center; color:#9aa0a6; font-style:italic; margin:-6px 0 14px;"><code>rpt.conf</code> → a section in <code>svx.conf</code> → a login the reflector recognises.</div>

== Step 1 — Install the package ==

Pick the <code>.deb</code> that matches your OS '''and''' architecture:

{| class="wikitable"
|-
! OS / arch !! Package
|-
| trixie x86-64 || <code>asl3-chan-svx_<ver>~trixie_amd64.deb</code>
|-
| trixie arm64 (Pi) || <code>asl3-chan-svx_<ver>~trixie_arm64.deb</code>
|-
| bookworm x86-64 || <code>asl3-chan-svx_<ver>~bookworm_amd64.deb</code>
|-
| bookworm arm64 (Pi) || <code>asl3-chan-svx_<ver>~bookworm_arm64.deb</code>
|}

<pre>sudo apt install ./asl3-chan-svx_<ver>~<os>_<arch>.deb</pre>

Dependencies (<code>asl3-asterisk</code>, <code>libopus0</code>, <code>libssl3</code>) resolve automatically. The package installs the module, a sample config, this kind of documentation under <code>/usr/share/doc/asl3-chan-svx/</code>, and adds a '''commented''' load line to <code>modules.conf</code> for you to enable in Step 4. '''Nothing loads or connects yet.'''

== Step 2 — Create the reflector config ==

Copy the sample and open it for editing:

<pre>sudo cp /etc/asterisk/svx.conf.sample /etc/asterisk/svx.conf
sudo chown asterisk:asterisk /etc/asterisk/svx.conf
sudo chmod 640 /etc/asterisk/svx.conf # it holds your reflector password
sudoedit /etc/asterisk/svx.conf</pre>

Make it look like this (name the section after the node — tidy and unambiguous):

<pre>[1999]
host = 172.16.1.1 ; reflector hostname or IP
port = 5300 ; reflector port (default 5300)
login = SA7AUX-AC ; your OWN login, UPPER-CASE, not shared
password = CHANGE_ME ; your reflector auth-key
callsign = SA7AUX ; name shown to the reflector
tg = 24016 ; talkgroup to select (TX + primary RX)</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''The login + password must match what the reflector expects for this login.''' Use a '''dedicated''' login — an upper-case callsign — that no other client (svxlink, another node) already uses; sharing one gets the other kicked off.</div>

The <code>callsign</code> is shown as the node's name '''if it is free''' on the reflector right now; on a collision (or if left empty) it falls back to <code>ASL-<section></code> (e.g. <code>ASL-1999</code>), re-checked automatically as names free up.

== Step 3 — Point the node at it ==

In <code>/etc/asterisk/rpt.conf</code>, in your node's stanza, '''comment out the old rxchannel — never delete it''' — and add the SVX line:

<pre>[1999](node-main)
; rxchannel = USRP/127.0.0.1:4001:4002 ; old bridge, kept so you can revert
rxchannel = SVX/1999 ; chan_svx -> section [1999]</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''Want it to survive package upgrades?''' Put the node stanza in <code>/etc/asterisk/custom/rpt.conf</code> instead — ASL3 includes that file and never overwrites it. Use the direct edit above for a quick change; use <code>custom/</code> if you want your config to survive <code>asl3-asterisk</code> updates cleanly.</div>

== Step 4 — Enable the module ==

ASL3 has <code>autoload = no</code>, so the module must be listed by hand. The package added a '''commented''' line — turn it on. '''It must live inside the <code>[modules]</code> section''' (a <code>load</code> line after a later section is silently ignored):

<pre>sudo sed -i 's/^; *load = chan_svx.so/load = chan_svx.so/' /etc/asterisk/modules.conf
grep -n '^load = chan_svx.so' /etc/asterisk/modules.conf # confirm it's active</pre>

== Step 5 — Apply and verify ==

An <code>rxchannel</code> change needs app_rpt to re-init, so restart Asterisk, then check:

<pre>sudo asterisk -rx "core restart now"
sudo asterisk -rx "svx show"</pre>

A healthy bridge looks like this — '''<code>CONNECTED</code> means you're done with the basic hookup''':

[[File:Chan_svx_svx_show.png|center|frameless|900px|alt=Annotated svx show output explaining CONNECTED, txframes, rxframes, starts/stops, fec and plc.]]

Key up on the node → <code>txframes</code> climbs and the reflector opens the talker on your TG. When someone else talks on the TG → <code>rxframes</code> climbs. Done. The rest of this page is tuning and extras.

== Getting the audio right ==

This is where most people get stuck, so take it slow. '''Only the yellow stages have knobs''' — everything grey is automatic.

[[File:Chan_svx_sat_audio_path.png|center|frameless|920px|alt=The TX and RX audio chains showing which stages are tunable (gain, AGC, jitter, tx_hold) and which are automatic (limiter, Opus FEC/PLC).]]

All of these live in the node's section in <code>svx.conf</code>. '''After changing any of them, run <code>sudo asterisk -rx "core restart now"</code>.'''

=== The four audio knobs ===

{| class="wikitable" style="width:100%;"
|-
! Setting !! Default !! What it does
|-
| <code>tx_gain</code> || <code>0</code> || Preamp on TX (node → reflector), in dB. Raise if others say you're quiet; lower if they say you clip.
|-
| <code>rx_gain</code> || <code>0</code> || Preamp on RX (reflector → node), in dB. Raise if the reflector audio is too quiet on your repeater.
|-
| <code>tx_agc</code> / <code>rx_agc</code> || <code>no</code> || Automatic gain control. Turn '''on''' to even out loud/quiet stations. <code>yes</code> or <code>no</code>.
|-
| <code>bitrate</code> || <code>16000</code> || Opus bitrate in bit/s. Leave it unless you have a reason.
|}

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 A '''limiter is always on''' in both directions — it stops the audio clipping even if you raise the gain too far. '''Opus inband FEC + PLC''' are always on too: a lost packet is rebuilt from the next one's FEC, and an underrun is concealed instead of clicking. You don't configure any of that.</div>

=== "My audio is X → do Y" ===

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Fix
|-
| Others say '''you're too quiet''' || Raise <code>tx_gain</code> a few dB at a time (e.g. <code>3</code>, then <code>6</code>).
|-
| Others say '''you clip / distort''' || Lower <code>tx_gain</code> a notch. The limiter guards the peak, but clean input is better.
|-
| '''Reflector audio too quiet''' on your repeater || Raise <code>rx_gain</code> a few dB.
|-
| '''Loud and quiet stations''' are wildly uneven || Turn on <code>rx_agc = yes</code> (and/or <code>tx_agc = yes</code>).
|-
| '''Choppy / chopped''' audio going out || See [[#The link flaps or chops|the tx_hold fix below]].
|-
| Crackle/dropouts coming '''in''' on a poor link || Raise <code>jitter</code> (see below). FEC/PLC already help; this adds headroom.
|}

=== Two more knobs: tx_hold and jitter ===

{| class="wikitable" style="width:100%;"
|-
! Setting !! Default !! What it does
|-
| <code>tx_hold</code> || <code>250</code> || '''TalkerStop hold time''', in ms. A brief unkey/rekey mid-over (COS flicker, link hangtime) would otherwise close and reopen the reflector talker and chop the audio. The hold keeps it open across the gap. <code>0</code> = stop immediately on unkey.
|-
| <code>jitter</code> || <code>40</code> || '''Jitter-buffer prefill''', in ms. Higher = smoother on a poor/long link, but more latency. <code>0</code> = minimal (fine on a clean LAN). Max 500.
|}

<div id="The link flaps or chops"></div>
'''If audio going out is chopped:''' run <code>svx show</code> and watch <code>starts</code>/<code>stops</code>. '''One each per over is healthy.''' Many per over means your key is flapping — raise <code>tx_hold</code> (try <code>400</code>).

=== Optional: listen to extra talkgroups ===

<pre>monitor = 24020, 9990 ; extra TGs you HEAR (RX only); TX still goes to 'tg'</pre>

== Keep it up — forever ==

Two independent things stay up: the '''reflector link''' and the '''AllStar node-to-node link'''.

* '''The reflector link is automatic.''' chan_svx reconnects on its own (TCP + UDP heartbeats, backoff after any drop). Nothing to configure; <code>svx show</code> goes back to <code>CONNECTED</code> within seconds of any outage.
* '''Keep the AllStar node linked to a hub?''' Use app_rpt's permanent connect, which re-establishes itself:

<pre>sudo asterisk -rx "rpt cmd 1999 ilink 13 403870" # 13 = permanent, transceive</pre>

'''Link automatically at boot''' via the node stanza:

<pre>[1999](node-main)
rxchannel = SVX/1999
startup_macro = *3403870 ; auto-connect to 403870 (transceive) on startup</pre>

'''Belt-and-suspenders cron''' (<code>ilink 3</code> is idempotent — a no-op if already linked):

<pre># keep node 1999 linked to 403870 every 2 minutes
*/2 * * * * /usr/sbin/asterisk -rx "rpt cmd 1999 ilink 3 403870" >/dev/null 2>&1</pre>

== Bonus: change talkgroup from the radio (DTMF) ==

You can move the node to another TG live — over RF with DTMF, gated by a PIN — then drop back. Handy for pushing a bulletin/net out on a different TG, then reverting.

[[File:Chan_svx_tg_control.png|center|frameless|900px|alt=DTMF dial pattern star-855 plus PIN plus action digit, with a table of actions and the control flow.]]

'''Dial pattern:''' <code>*855</code> + '''PIN''' + action. Put the commands in <code>rpt.conf</code> under <code>[functions]</code> (PIN is the control code — a wrong PIN simply does nothing). Default PIN is <code>0000</code> — '''change it before use''':

<pre>; /etc/asterisk/rpt.conf — base 855, PIN 0000 (CHANGE IT!)
[functions]
85500001 = cmd,asterisk -rx "svx settg 403872 3149060" ; *855 0000 1 -> bulletin TG
85500002 = cmd,asterisk -rx "svx settg 403872 3149070" ; *855 0000 2 -> another TG
85500000 = cmd,asterisk -rx "svx revert 403872" ; *855 0000 0 -> default TG
85500009 = cmd,asterisk -rx "svx down 403872" ; *855 0000 9 -> link down
85500008 = cmd,asterisk -rx "svx up 403872" ; *855 0000 8 -> link up</pre>

Set the default TG and an auto-revert timeout in <code>svx.conf</code>:

<pre>[403872]
tg = 3149050 ; the DEFAULT TG (revert/up target)
tg_timeout = 30 ; minutes on another TG before auto-revert (0 = off)</pre>

A temporary TG '''always''' drops back to default on a reboot, a reconnect, or after <code>tg_timeout</code> — so a forgotten switch never strands the node.

== Several nodes or TGs? Use chan_svx_sat ==

<code>chan_svx</code> is '''one login = one TG = one stream''' — one reflector client per section. If you need '''several nodes / talkgroups over a single reflector login''' (a shared '''trunk'''), that is exactly what the sister driver '''chan_svx_sat''' does — it joins as a reflector ''satellite/trunk'' instead of a client. See the [[Hamradio/chan_svx_sat|chan_svx_sat how-to]].

== Troubleshooting ==

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Check
|-
| <code>svx show</code> empty / "No such command" / node has no rxchannel || Is <code>load = chan_svx.so</code> enabled '''inside <code>[modules]</code>'''? Did you <code>core restart now</code>?
|-
| <code>down</code> instead of <code>CONNECTED</code> || Host/port reachable? login/password correct? Watch: <code>sudo tail -f /var/log/asterisk/messages.log | grep -i svx</code>
|-
| <code>auth rejected: Invalid callsign</code> || Login must be a valid '''upper-case''' callsign, and the account must exist on the reflector.
|-
| <code>auth rejected: Access denied</code> || Wrong password, or the login isn't registered on the reflector.
|-
| <code>txframes</code> climbs but nobody hears you || Is the '''listening''' client actually selecting/monitoring the same TG?
|-
| Choppy audio out, <code>starts</code> climbing many-per-over || Key/unkey flapping → raise <code>tx_hold</code> (e.g. <code>400</code>).
|-
| <code>txbadsize</code> climbing || app_rpt is feeding non-slin frames — check the node's audio path.
|-
| Loads but refuses ("compile-time options") || The package must match the installed <code>asl3-asterisk</code> version — install the deb for your exact OS.
|}

== Reverting ==

# Restore the old <code>rxchannel</code> (uncomment it) and comment <code>rxchannel = SVX/...</code>.
# Comment <code>load = chan_svx.so</code> in <code>modules.conf</code>.
# <code>sudo asterisk -rx "core restart now"</code>.

Remove entirely: <code>sudo apt remove asl3-chan-svx</code> (add <code>--purge</code> to also drop the sample config and the <code>modules.conf</code> line).

== See also ==

* [[Hamradio]] — all the digital-voice and gateway how-tos.
* Author / bug reports: '''SA7AUX''' <bjorne@sa7aux.se>. GNU GPL v2.

[[Category:Ham radio]]

Hamradio/reflector dashboard/en

FuzzyBot — Sun, 18 Oct 2026 15:10:05 GMT

Updating to match new version of source page

New page

{{DISPLAYTITLE:R.A.D.A.R. — a live dashboard for your SvxReflector}}
<languages/>

''A guide to setting up '''R.A.D.A.R.''' (Reflector Activity Dashboard And Reporting): a web dashboard that shows, live, who is connected to your '''SvxReflector''', who is talking, and how the network is wired — with user accounts, talkgroup lists and admin tools.''

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''In one sentence:''' R.A.D.A.R. runs on the '''same server as your SvxReflector''', polls the reflector's status, and serves a live web page (nodes, last-heard, talkgroups, topology, CTCSS) with a sign-up/login account system.</div>

[[File:Radar_arch.png|center|frameless|940px|alt=The reflector's /status on port 8099 is polled by svxdr proxy (8090), then svxdr nodelist (8098), served through nginx over HTTPS to the browser; PHP-FPM handles accounts in Redis.]]

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ '''This one is for reflector operators, not beginners.''' Unlike the node dashboard, R.A.D.A.R. is a server install: nginx + PHP + Redis + a Go daemon + a real TLS certificate. If you just run a node, you don't need this — you want the [[Hamradio/svxspot_dashboard|SvxSpot Dashboard]] instead. The authoritative step-by-step is the repo's '''<code>INSTALL.md</code>'''; this page is the friendly overview.</div>

__TOC__

== Do I need this? ==

* '''You run a SvxReflector''' (specifically a '''GeuReflector''' build, which adds reflector-to-reflector trunking) and want a public/at-a-glance '''activity dashboard''' for it.
* You're comfortable setting up a web server with HTTPS. This is a multi-service install on a Debian box.
* If you only run a '''node''' (hotspot/repeater), stop here — use [[Hamradio/svxspot_dashboard|SvxSpot Dashboard]].

== What you need first ==

{| class="wikitable" style="width:100%;"
|-
! Thing !! Why
|-
| '''A running SvxReflector (GeuReflector)''' on the same box || R.A.D.A.R. reads its <code>/status</code> endpoint (example port '''8099''').
|-
| '''A domain name + TLS certificate''' (Let's Encrypt) || Login uses a <code>Secure</code> cookie — '''it does not work over plain HTTP.'''
|-
| '''nginx''', '''PHP 8.4 + FPM''' (redis, mbstring, openssl, json), '''Redis 6+''' || web server, account backend, and account/session store.
|-
| '''An MTA or SMTP relay''' || sign-up verification and password-reset e-mail.
|-
| '''Go 1.24+''' || to compile the <code>svxdr</code> live-data daemon.
|}

Install the packages (Debian 13 / Ubuntu 24.04):
<pre>sudo apt install nginx php8.4-fpm php8.4-redis php8.4-mbstring php8.4-cli \
redis-server certbot openssl rsync curl python3 sudo golang-go</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Debian 12 ships PHP 8.2; R.A.D.A.R. is developed on '''8.4'''. Use Debian 13, or the sury.org PHP repo, and substitute your real version everywhere you see <code>8.4</code>.</div>

== How the data flows (so the ports make sense) ==

The single most common setup mistake is a '''mismatched port chain'''. Data flows:

'''reflector <code>/status</code> :8099''' → '''svxdr proxy :8090''' (caches, enriches) → '''svxdr nodelist :8098''' (builds the API + live SSE stream, reads Redis for node events) → '''nginx''' (HTTPS, reverse-proxies <code>/svxportal/api/</code> to :8098) → '''your browser'''. Accounts live in '''Redis'''; the PHP backend (<code>auth/*.php</code>) talks to it.

Keep those numbers lined up and most of the install "just works".

== Install (overview) ==

Clone the repo and follow its <code>INSTALL.md</code> steps 0–11; the key moves are:

# '''Get the code:''' <code>git clone https://git.sa7aux.se/bjorne/reflector-dashboard.git</code>
# '''Deploy the web files''' with <code>rsync</code> into <code>/var/www/html/svxportal</code> (owned by <code>www-data</code>).
# '''Set up a dedicated Redis''' instance on a unix socket, with a password; add <code>www-data</code> to the <code>redis</code> group.
# '''Add a second PHP-FPM pool''' (<code>svxadmin</code>) used only by the reflector-admin API.
# '''Create the talkgroup-list file''' <code>/etc/svxlink/tglist.json</code> (via the shipped tmpfiles rule).
# '''nginx + TLS:''' install the site template, run <code>certbot</code> for your hostname, enable the site.
# '''Build and run <code>svxdr</code>:'''
<pre>cd svxdr && CGO_ENABLED=0 go build -trimpath -o svxdr . && cd ..
sudo install -m0755 svxdr/svxdr /usr/local/bin/svxdr
sudo cp install/svxdr.json.example /etc/svxlink/svxdr.json # then edit it
sudo cp install/systemd/svxdr.service /etc/systemd/system/svxdr.service
sudo systemctl daemon-reload && sudo systemctl enable --now svxdr
curl -s http://127.0.0.1:8098/healthz # -> ok</pre>

Two config files hold the settings: '''<code>auth/config.php</code>''' (web backend — Redis password, mail, <code>base_url</code>, MQTT) and '''<code>/etc/svxlink/svxdr.json</code>''' (the daemon — Redis, the three ports, federation seeds). Copy each from its <code>.example</code> and edit.

== Create the first admin ==

A bundled CLI makes the first account (and marks its e-mail verified):
<pre>cd /var/www/html/svxportal
sudo -u www-data php svx-mkadmin.php</pre>
It asks for callsign, name, e-mail, location, '''admin level''' and a password. Levels: '''1''' = normal user, '''2''' = admin (accounts, nodes, certificates, talkgroups), '''3''' = super admin (also reflector/MQTT secrets and managing other admins). Everyone else '''self-registers''' on the site and verifies by e-mail.

== Using it ==

Open '''<code>https://YOUR.HOST.NAME/</code>'''. The top navigation has:

{| class="wikitable" style="width:100%;"
|-
! View !! Shows
|-
| '''Nodes''' || Connected nodes, with a pop-up when someone is talking.
|-
| '''Reflector clients''' || Searchable list of all connected clients.
|-
| '''Monitor → Nodes / Trunks / Topology''' || Live monitor; '''Topology''' draws the whole network — your reflector in the centre, other reflectors in a ring, trunk links between them.
|-
| '''TG Monitor''' || Who's on each talkgroup (SVX side and DMR side).
|-
| '''Lastheard''' || Recent activity.
|-
| '''CTCSS Table''' || Per-node TX/RX tones, 2 m vs UHF.
|-
| '''Changelog''' || Project changelog.
|}

A built-in '''Help''' page (<code>/help.html</code>) has tabs for the Portal, SvxLink, SvxReflector, GeuReflector, AllStar and more.

== Good to know / honest caveats ==

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ '''The reflector-admin pages need helper scripts you write yourself.''' The Admin → Reflector / Certificates / Node-control / MQTT pages call root-owned <code>sudo</code> helpers in <code>/usr/local/sbin/</code> (<code>svxreflector-pty</code>, <code>svxreflector-systemctl</code>, <code>svxreflector-users</code>, <code>svx-mqtt-provision</code>) that are '''not shipped''' — they're specific to your box. Everything else works without them.</div>

* '''Login lost after one page?''' You're not on HTTPS (the cookie is <code>Secure</code>) or <code>base_url</code> is wrong.
* '''Live views empty?''' <code>svxdr</code> isn't running — check <code>systemctl status svxdr</code> and <code>curl http://127.0.0.1:8098/healthz</code>. The reflector itself keeps working regardless.
* '''No verification e-mail?''' PHP <code>mail()</code> fails silently without an MTA — configure an SMTP relay.
* '''Admin API says “exec disabled”?''' Never add <code>exec</code> to PHP's <code>disable_functions</code>; the portal needs it.

== Troubleshooting ==

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Check
|-
| '''500 on any <code>auth/*.php</code>''' || <code>/var/log/nginx/svxportal-error.log</code> and <code>journalctl -u php8.4-fpm</code> — usually Redis password wrong, <code>php-redis</code> missing, or <code>www-data</code> not in group <code>redis</code>.
|-
| '''"Not connected" / empty views''' || <code>svxdr</code> down → nothing on <code>127.0.0.1:8098</code>.
|-
| '''Ports''' || Confirm the chain '''8099 → 8090 → 8098 → nginx''' in <code>/etc/svxlink/svxdr.json</code> and the nginx site.
|}

== See also ==

* [[Hamradio/svxspot_dashboard|SvxSpot Dashboard]] — the dashboard for a single node (much simpler).
* [[Hamradio]] — SvxReflector and the rest of the digital-voice how-tos.
* Author: '''SA7AUX''' <bjorne@sa7aux.se>. AGPL-3.0-or-later.

[[Category:Ham radio]]

Hamradio/darthvader/en

FuzzyBot — Sun, 18 Oct 2026 15:10:02 GMT

Updating to match new version of source page

New page

{{DISPLAYTITLE:darthvader — the all-modes digital voice app}}
<languages/>

''A beginner's guide to installing and running '''darthvader''' — one desktop program that puts every ham digital-voice network (DMR, YSF, D-STAR, NXDN, P25, M17, EchoLink, AllStar, SvxLink, APRS, POCSAG) in a single window, on Windows or Linux. Download, install, go.''

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 '''In one sentence:''' darthvader is a '''desktop app for your PC''' that connects to the digital-voice networks you'd otherwise need a hotspot or several programs for. The AMBE vocoder can be a USB stick ('''DV3000/ThumbDV'''), a remote '''AMBEserver''', or '''software''' (no extra hardware).</div>

[[File:Darthvader_hub.png|center|frameless|900px|alt=darthvader at the center of your PC, connecting out to DMR, D-STAR, YSF, NXDN, P25, M17 on one side and EchoLink, AllStar, SvxLink, APRS, DAPNET on the other, with a vocoder bar underneath.]]

__TOC__

== Do I need this? ==

* '''You want to operate digital voice from a computer''' — key up and listen on DMR / YSF / D-STAR / NXDN / P25 / M17, link via EchoLink / AllStar / SvxLink, or send APRS / pager (POCSAG) messages — '''without''' building a separate hotspot for each.
* It runs on a normal '''Windows 10/11''' PC or a '''Linux''' box (Debian/Ubuntu/Raspberry Pi OS).
* You do '''not''' need to install Qt, codecs or anything else first — everything is bundled in the package.

The only thing you might add is an '''AMBE vocoder''' for the modes that need one (see [[#Choosing a vocoder|below]]) — but there's a software option, so you can start with nothing extra.

== Get it ==

Everything is published on the release page:
* '''https://git.sa7aux.se/bjorne/darthvader-dist/releases'''

Grab the file for your system, then follow the matching section below.

[[File:Darthvader_install.png|center|frameless|920px|alt=Two install paths: Windows via .msi or portable .zip; Debian/Linux via a single .deb or the apt repo.]]

== Install — Windows 10 / 11 ==

# Download '''<code>darthvader-<version>-win64.msi</code>'''.
# '''Double-click it''' and follow the installer — you get a Start-menu and desktop shortcut.
# The first time you run it, Windows '''SmartScreen''' may show a blue warning (the build isn't code-signed). Click '''“More info” → “Run anyway.”'''

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ '''It is not a virus.''' Unsigned apps always trip SmartScreen, and a couple of antivirus engines flag unknown programs on reputation alone. If you want to be sure, verify the download against the published '''<code>SHA256SUMS</code>''' (see [[#Verify your download|below]]).</div>

'''Prefer no installer?''' Download the '''<code>…-win64.zip</code>''', unzip it anywhere, and run '''<code>bin\darthvader.exe</code>''' — fully portable, nothing written to the system.

'''Rolling it out to many PCs (silent install):'''
<pre>msiexec /i darthvader-<version>-win64.msi /qn</pre>

== Install — Debian / Ubuntu / Raspberry Pi ==

'''Option A — just install the one file:'''
<pre>sudo apt install ./darthvader_<version>_amd64.deb</pre>
apt pulls in any dependencies automatically.

'''Option B — add the apt repo once, then get updates with normal <code>apt</code>:'''
<pre>curl -fsSL https://debrepo.sa7aux.se/setup.sh | sudo bash
sudo apt install darthvader</pre>

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 Today the Linux package is built for '''Debian 13 (trixie), x86-64'''. '''bookworm''' and '''arm64 (Raspberry Pi)''' are planned — if there's no package for your Pi yet, use a Windows or x86-64 Linux box for now.</div>

== Verify your download ==

Each release ships a '''<code>SHA256SUMS</code>''' file. To check a download is intact and genuine:
<pre>sha256sum -c SHA256SUMS # Linux/macOS
# Windows (PowerShell): Get-FileHash .\darthvader-<version>-win64.msi -Algorithm SHA256</pre>
The printed hash must match the line in <code>SHA256SUMS</code>.

== Choosing a vocoder ==

Several digital modes use the '''AMBE+2''' voice codec. darthvader gives you three ways to provide it — pick '''one''':

{| class="wikitable" style="width:100%;"
|-
! Vocoder !! What you need !! Notes
|-
| '''DV3000 / ThumbDV / DVstick''' (USB stick) || plug it into a USB port || Appears as a serial/COM port (FTDI) and is auto-detected. Best quality, cheapest hardware route.
|-
| '''Remote AMBEserver''' || a reachable AMBEserver over the network (UDP) || Use a shared/remote dongle — no local hardware.
|-
| '''Software vocoder''' || nothing extra || Works with no chip. P25 has a full software IMBE; other modes can use the MD380-firmware software vocoder (see the note below).
|}

<div style="border-left:4px solid #e0b33a; background:#2a2208; padding:10px 16px; margin:14px 0; border-radius:6px;">⚠ The MD380-firmware software vocoder needs the files <code>md380fw.img</code> / <code>md380ram.img</code> placed in <code>share/darthvader/vocoder_fw</code>. Those are Tytera's firmware and are '''not''' shipped with darthvader — you supply them. A DV3000 stick or a remote AMBEserver needs none of this.</div>

== First run ==

<div style="border-left:4px solid #4da3ff; background:#13233a; padding:10px 16px; margin:14px 0; border-radius:6px;">💡 A full first-launch walkthrough isn't in the download package yet. In general: open '''Settings''', add your account/server for each mode you use (DMR master such as BrandMeister/TGIF, a D-STAR/YSF/NXDN/P25/M17 reflector, EchoLink, AllStar nodes, SvxLink reflectors, APRS/DAPNET), pick your '''vocoder''', set your '''audio''' devices, then connect. The status bar shows a coloured dot per mode, and the title bar / About shows the exact build.</div>

For mode-specific details (talkgroups, reflector names, access rights) follow that network's own documentation — see [[Hamradio]].

== Audio ==

darthvader has a per-direction audio chain — '''preamp → 7-band EQ → LADSPA → AGC → limiter''' — configurable per mode/peer, with bundled LADSPA plugins, so a chain you set up on Linux works unchanged on Windows. Start with the defaults; only touch it if others report your audio is too quiet, too loud, or uneven.

== Troubleshooting ==

{| class="wikitable" style="width:100%;"
|-
! Symptom !! Fix
|-
| Windows '''SmartScreen''' / antivirus warning on first run || Expected for an unsigned app → '''“More info” → “Run anyway.”''' Verify with <code>SHA256SUMS</code> if unsure.
|-
| '''DV3000 audio stutters''' || Lower the stick's '''Latency Timer to 1–2 ms''' (Windows: Device Manager → the COM port → Port Settings → Advanced).
|-
| '''Software vocoder won't start''' || The MD380 firmware images aren't present — add <code>md380fw.img</code>/<code>md380ram.img</code>, or use a DV3000 stick / AMBEserver instead.
|-
| No '''.deb''' for my Raspberry Pi || arm64 builds are "to follow" — not available yet. Use x86-64 Linux or Windows meanwhile.
|}

== Updating ==

* '''Windows:''' download the newer <code>.msi</code> and install over the top (or replace the portable folder).
* '''Linux (apt repo):''' <code>sudo apt update && sudo apt upgrade</code>.
* '''Linux (one <code>.deb</code>):''' download the new <code>.deb</code> and <code>sudo apt install ./…</code> again.

The version is shown as <code><number>-<git-hash></code> in the title bar and About dialog.

== See also ==

* [[Hamradio]] — the digital-voice modes darthvader speaks, each in depth.
* Author: '''SA7AUX''' <bjorne@sa7aux.se>. GNU GPL v2 or later.

[[Category:Ham radio]]

Hamradio/reflector dashboard

Sa7aux — Sun, 18 Oct 2026 15:09:59 GMT

Sa7aux marked Hamradio/reflector dashboard for translation

Hamradio/svxspot dashboard

Sa7aux — Sun, 18 Oct 2026 15:09:58 GMT

Marked this version for translation

Show changes

Hamradio/reflector dashboard

Sa7aux — Sun, 18 Oct 2026 15:09:58 GMT

Marked this version for translation

Show changes

Hamradio/svxspot dashboard

Sa7aux — Sun, 18 Oct 2026 15:09:58 GMT

Sa7aux marked Hamradio/svxspot dashboard for translation

Hamradio/darthvader

Sa7aux — Sun, 18 Oct 2026 15:09:57 GMT

Sa7aux marked Hamradio/darthvader for translation

Hamradio/chan svx sat

Sa7aux — Sun, 18 Oct 2026 15:09:57 GMT

Sa7aux marked Hamradio/chan svx sat for translation

Hamradio/chan svx

Sa7aux — Sun, 18 Oct 2026 15:09:56 GMT

Sa7aux marked Hamradio/chan svx for translation

User:Sa7aux/svxspot dashboard

Sa7aux — Sun, 18 Oct 2026 14:48:28 GMT

Sa7aux marked User:Sa7aux/svxspot dashboard for translation

User:Sa7aux/svxspot dashboard/en

FuzzyBot — Sun, 18 Oct 2026 14:38:53 GMT

Updating to match new version of source page

New page

User:Sa7aux/svxspot dashboard

Sa7aux — Sun, 18 Oct 2026 14:35:54 GMT

Sa7aux marked User:Sa7aux/svxspot dashboard for translation

User:Sa7aux/svxspot dashboard/sv

Delete page script — Sun, 18 Oct 2026 14:35:53 GMT

Delete page script deleted page User:Sa7aux/svxspot dashboard/sv replaced by Translate bilingual

User:Sa7aux/ltest/sv

Delete page script — Sun, 18 Oct 2026 14:34:34 GMT

Delete page script deleted page User:Sa7aux/ltest/sv cleanup translate test

User:Sa7aux/ltest

Delete page script — Sun, 18 Oct 2026 14:34:33 GMT

Delete page script deleted page User:Sa7aux/ltest cleanup translate test

User:Sa7aux/ltest/en

FuzzyBot — Sun, 18 Oct 2026 14:33:21 GMT

Updating to match new version of source page

New page

<languages/>
Hello, this is a bilingual test page.

It has two short paragraphs so we can see the language switcher.

[[Category:Ham radio]]

User:Sa7aux/ltest

Sa7aux — Sun, 18 Oct 2026 14:32:32 GMT

Sa7aux marked User:Sa7aux/ltest for translation

File:Darthvader install.png

Sa7aux — Sun, 18 Oct 2026 14:10:28 GMT

Sa7aux uploaded File:Darthvader install.png == Summary == How-to diagrams: darthvader, svxspot, R.A.D.A.R.

New page

== Summary ==
How-to diagrams: darthvader, svxspot, R.A.D.A.R.

File:Radar arch.png

Sa7aux — Sun, 18 Oct 2026 14:10:28 GMT

Sa7aux uploaded File:Radar arch.png == Summary == How-to diagrams: darthvader, svxspot, R.A.D.A.R.

New page

== Summary ==
How-to diagrams: darthvader, svxspot, R.A.D.A.R.

File:Darthvader hub.png

Sa7aux — Sun, 18 Oct 2026 14:10:28 GMT

Sa7aux uploaded File:Darthvader hub.png == Summary == How-to diagrams: darthvader, svxspot, R.A.D.A.R.

New page

== Summary ==
How-to diagrams: darthvader, svxspot, R.A.D.A.R.

File:Svxspot dashboard arch.png

Sa7aux — Sun, 18 Oct 2026 14:10:28 GMT

Sa7aux uploaded File:Svxspot dashboard arch.png == Summary == How-to diagrams: darthvader, svxspot, R.A.D.A.R.

New page

== Summary ==
How-to diagrams: darthvader, svxspot, R.A.D.A.R.

File:Chan svx tg control.png

Sa7aux — Sun, 18 Oct 2026 13:15:14 GMT

Sa7aux uploaded File:Chan svx tg control.png == Summary == chan_svx / chan_svx_sat how-to diagrams

New page

== Summary ==
chan_svx / chan_svx_sat how-to diagrams

File:Chan svx sat topology.png

Sa7aux — Sun, 18 Oct 2026 13:15:14 GMT

Sa7aux uploaded a new version of File:Chan svx sat topology.png == Summary == chan_svx / chan_svx_sat how-to diagrams

New page

== Summary ==
chan_svx_sat how-to diagrams (SA7AUX)

File:Chan svx topology.png

Sa7aux — Sun, 18 Oct 2026 13:15:14 GMT

Sa7aux uploaded File:Chan svx topology.png == Summary == chan_svx / chan_svx_sat how-to diagrams

New page

== Summary ==
chan_svx / chan_svx_sat how-to diagrams

File:Chan svx architecture.png

Sa7aux — Sun, 18 Oct 2026 13:15:14 GMT

Sa7aux uploaded File:Chan svx architecture.png == Summary == chan_svx / chan_svx_sat how-to diagrams

New page

== Summary ==
chan_svx / chan_svx_sat how-to diagrams