Aquilon VPU Map 1.0.0
First release. Reads an Analog Way LivePremier's VPU mixer allocation and draws it,
so you can see what a configuration is actually spending without walking the Web RCS
a panel at a time.
Everything here was built against a real Aquilon C, read in three different
configurations. Each one broke an assumption the previous had made look settled, which
is why the captures are kept rather than tidied.
What it does
- Reads a live device over AWJ in about a second — 64 mixers, both the running and
the staged mapping. - Chassis view: every mixer, what it serves, what is spare, what is not fitted.
- Link grid: each VPU as the manual draws it (User Manual v6.0 §5.5) — eight layer
links in, eight output links out. Columns are the device's own; rows are packed. - What each screen costs, and whether it fits: output links spent, layers over
outputs, links spare, and a warning when a screen is over budget. Reported by the
device, not inferred. - Optimized mode is detected, and the scaling-engine boundary is not drawn on a VPU
where it does not apply. - Staged changes: what applying the device's pending configuration would do —
including link re-allocations that change no property at all. - Screens are named the way you named them.
- Keep watching re-reads on an interval, stops itself on failure, and leaves the
last good reading on screen. - Save a reading and compare a live device against it.
Reads only
It issues AWJ get and nothing else — not even the Subscriptions write a push-based
client would need. Every property it reads is readOnly in the device's own model.
lib/awj.js has no code path that emits a write.
Also included
scripts/profile-vpu.mjs— a single self-contained file another operator can run
against their own LivePremier to contribute a configuration. Records structure only:
no addresses, serials, device names or screen names.scripts/probe-hardware.mjs— the procedure for exploring a device you have.- Three recorded captures, so the app is useful with no device present.
Known limitations
Row positions in the link grid are packed rather than reported; channel is assumed to
index the Link device; Link setups, DUAL/8K capacities, combined VPUs and Cut & Fill
have never been observed. See docs/ROADMAP.md.
Run it
npm start # then http://localhost:8531or
docker run -d --name aquilon-vpu-map -p 8531:8531 ghcr.io/stoatworks-labs/aquilon-vpu-map:latestNode 18+, no dependencies, no build step. Also available in Unraid Community Applications.