Skip to content

Usage

Jump to bottom
KP edited this page May 18, 2025 · 1 revision

This page describes how to operate toc-lp-kit once deployed: launching the JS8Call GUI, monitoring decoded output, and optionally exposing logs.

🖥 JS8Call GUI

After deployment, JS8Call runs in the toc_js8 container but uses the host’s X11 display. To open:

js8call

Alternatively, launch in-container:

docker exec -it toc_js8 js8call

The GUI should appear on the local desktop; audio is automatically piped from the SDR pipeline.

📋 Monitoring Decodes

All decoded messages are written as JSON to:

/home/js8/.js8call/decode.log

To follow in real time:

docker exec -it toc_js8 tail -f /home/js8/.js8call/decode.log

Example output:

{"time":"2025-05-18T13:00:00Z","from":"CALL1","to":"CALL2","message":"Hello","snr":10}
{"time":"2025-05-18T13:00:15Z","from":"CALL3","to":"CALL1","message":"ACK","snr":8}

🌐 Exposing Logs via HTTP

If ground assets need simple web access:

  1. Copy the current log to a host directory:

    mkdir -p ~/alerts && \
docker cp toc_js8:/home/js8/.js8call/decode.log ~/alerts/alerts.txt

  2. Serve via Python HTTP:

    cd ~/alerts && python3 -m http.server 8000

  3. Access from local network:
    http://<host-ip>:8000/alerts.txt

Return to Home

Clone this wiki locally