YWD//HOTSPOT
YWD-HOTSPOT 0.2.0-RC3 RX MONITOR VOCODER PROTOCOL V1 PI ZERO TESTED PATH
YWD-HOTSPOT · ADD-ON DOWNLOADS

RX Monitor packages and the optional external vocoder backend.

These files are separate from the YWD-Hotspot core factory image. The RX Monitor plugin stays sandboxed and receives PCM only; AMBE49 decoding is handled by the separately installed local backend through YWD Vocoder Protocol v1.

SEPARATE DISTRIBUTION BOUNDARY

The vocoder deployment kit, RX Monitor .ywdplugin, and YWD-Hotspot core are intentionally separate. Normal DMR/RF operation does not require the external decoder. The backend is socket-activated and can remain dormant when RX audio is not being used.

QUICK WALKTHROUGH · VOCODER BACKEND

Install the external backend on the hotspot.

First transfer/download the backend archive to the hotspot and extract it. The extracted directory should be ywd-vocoder-mbelib-backend-0.1.0-alpha1. Internet access is required while installing because the kit fetches the pinned upstream mbelib source and build dependencies.

01

Enter the extracted kit

Open an SSH session or local console on the hotspot and change into the extracted deployment-kit directory.

cd ywd-vocoder-mbelib-backend-0.1.0-alpha1
02

Make the helpers executable

The deployment kit ships install, status, test, benchmark and uninstall helpers.

chmod +x INSTALL.sh STATUS.sh TEST.sh BENCHMARK.sh UNINSTALL.sh
03

Install the backend

The installer validates YWD Vocoder Protocol v1 and the YWD-managed scheduling policy before changing the system.

sudo ./INSTALL.sh
04

Verify transport + decode

Check service state and run the bundled Protocol v1 sanity test. The optional benchmark is useful for transport/decode performance testing.

./STATUS.sh ./TEST.sh # optional ./BENCHMARK.sh
VOCODER QUICK INSTALL
cd ywd-vocoder-mbelib-backend-0.1.0-alpha1
chmod +x INSTALL.sh STATUS.sh TEST.sh BENCHMARK.sh UNINSTALL.sh
sudo ./INSTALL.sh
./STATUS.sh
./TEST.sh
Expected YWD-managed policy: Nice=0 · CPUWeight=200 · socket /run/ywd-vocoder.sock
WHAT THE INSTALLER EXPECTS
REQUIREMENTEXPECTEDWHY
YWD Vocoder ProtocolV1Trusted core/backend transport contract
Preferred live batch10 / 200 ms10 AMBE49 frames per preferred live request
PCM response8 kHz s16 monoCore forwards PCM to the sandboxed plugin
SchedulingNice=0 / CPUWeight=200Owned by YWD-Hotspot core; no realtime or negative nice
QUICK WALKTHROUGH · RX MONITOR PLUGIN

Upload, review, install, then enable.

Plugin Manager keeps package upload, installation and activation as separate decisions. The RX Monitor package should not become active merely because it was uploaded.

01

Download the package

Save dmr-rx-monitor-0.4.0-alpha19.ywdplugin to the phone/computer you use for the hotspot dashboard.

02

Open Plugin Manager

Open the YWD-Hotspot dashboard, unlock write controls, and open the plugin management UI.

03

Upload + review

Choose the .ywdplugin file. Core verifies the archive, hashes, signature, declared capabilities and MMDVM/runtime requirements before installation.

04

Install + enable

Confirm INSTALL, then explicitly ENABLE the package. With the vocoder backend available, open RX Monitor and press START AUDIO.

RX AUDIO PATH

MMDVM-Host remains the sole modem/RF owner. Trusted core performs DMR recovery/FEC and batching, talks to the separately installed vocoder backend, and sends PCM to the isolated browser plugin. The plugin does not directly own the modem, MQTT transport, vocoder socket, or RF transmit authority.

REFERENCE DOCUMENTATION

Need the full details?

The RC3 documentation covers the external vocoder boundary, plugin package lifecycle, runtime requirements and RX Monitor architecture.