# CLAUDE.md ## Before working on the rig At the start of a session, and before testing anything that needs the pad or the stage view, make sure the MIDI controller is working and the simulator is on: 1. Both user services are running: ```bash systemctl --user is-active padcontroller simulator ``` If either is not `active`, start it with `systemctl --user start `. If the unit is missing, install it with `padcontroller/systemd/install.sh` or `simulator/systemd/install.sh`. Check `journalctl --user -u -n 50` if it won't stay up. 2. The MIDI controller is connected and passed through: ```bash aconnect -l ``` It should list the `SMC-PAD` client (USB `SINCO SMC-PAD-Master` or `SMC-PAD Bluetooth`) and the `padcontroller` virtual port. A service that is active with no `SMC-PAD` client means the pad is off or not paired: ask the user to switch it on rather than carrying on without it. 3. The simulator answers on http://127.0.0.1:8765: ```bash curl -sf -o /dev/null http://127.0.0.1:8765 && echo ok ``` `shows/test.show.json` (and the `shows/test.qxw` built from it) sends Art-Net to 127.0.0.1 only, so testing drives the simulator and never the real rig. Keep it that way; don't point it at a 192.168.1.x node. ## Cans 3–6 are always static The row of 4 (#3–#6, fixture IDs 2–5) never animates. Chases, patterns, loops, strobes and side dimmer holds leave them out, so they keep the Colour 1 scene and their own dimmer knob whatever else runs. Their colour stays HTP, unlike the other cans. When adding an animation for the cans, build it on the other 11 (the groups `Sides` and `Strobe cans` in test.qxw already skip them) and don't write any FixtureVal for IDs 2–5. Tell the user what was down and what you did about it. The preview configurations in `.claude/launch.json` run separate copies on other ports (8770, 8766) and don't count as the services being up.