CHIMERA v11.0.0

CHIMERA Release Notes

CHIMERA is shipped as two independent downloads — pick the one matching the
machine where you want to run it.

---

chimera-sender-<version>.tar.gz — desktop test rig (linux/amd64)

A self-contained TUI for testing the backend on a regular Linux laptop or
desktop. It does not touch the host network and does not require
sudo (as long as board IPs are loopback 127.x.x.x and TCP ports are
≥ 1024).

Install / run

tar -xzf chimera-sender-<version>.tar.gz
cd chimera-sender
./chimera-sender                     # uses ./config-sender.json
./chimera-sender -config other.json  # custom config

What it does

• Loads the ADJ definition (downloads on first run; falls back to ./adj).
• Spins up one goroutine per board that emits UDP packets to the backend.
• Opens a TCP listener per board and decodes incoming orders.
• Drops you into an interactive TUI (list, set, help, quit).

The TCP-abrupt test is not available in sender mode (it relies on dummy
interfaces, which sender skips for loopback IPs).

---

chimera-raspi-installer-<version>.tar.gz — Raspberry Pi installer (linux/arm64)

A fully offline installer for production deployment on a Raspberry Pi.
The tarball already contains the ADJ tree from the CHIMERA branch — no
internet access is needed at install time or runtime.

Install

tar -xzf chimera-raspi-installer-<version>.tar.gz
cd chimera-raspi
sudo ./install.sh

The installer places:

File	Destination
chimera-raspi binary	/usr/local/bin/chimera
ADJ tree (offline)	/opt/chimera/adj
Config	/etc/chimera/config.json (with adj-path pinned to the bundled ADJ)
systemd unit	/etc/systemd/system/chimera.service

The systemd unit is installed but not enabled. Start it explicitly:

sudo systemctl enable --now chimera     # start now and on every boot
sudo systemctl status chimera           # check it
sudo journalctl -u chimera -f           # follow logs

Or run manually without the service:

sudo chimera                # daemon mode (default)
sudo chimera -mode tui      # interactive TUI on the Pi itself

Connecting from another machine

Once the daemon is running, SSH into the Raspberry Pi and open a remote TUI
that talks to the local daemon over the control port:

ssh pi@<raspi-host>
chimera -mode remote

You get the same list / set / event log experience as the local TUI, but
served by the running daemon — no need to stop the service.

Upgrading to a newer release

Re-running sudo ./install.sh from a newer tarball overwrites the binary,
the ADJ tree and the unit file. The service is not restarted
automatically — do it yourself after the install:

sudo systemctl restart chimera

Note: config.json is also overwritten. Back it up first if you have
manual edits.

---

Full Changelog: https://github.com/Hyperloop-UPV/CHIMERA/commits/v11.0.0