Gate LED controls on rig config (LED-driver present + point to calibration file)

[mbreiser]

Summary

The LED controls we just added are unconditionally enabled and assume a specific driver. They should instead be driven by the rig config file, which should (a) declare whether the rig has an LED driver at all, and (b) point to a calibration file in the repo for the brightness→voltage mapping. (For later — not urgent.)

Current state

• Console LED bar (arena_studio.html, v0.46): data-cmd="cledset" / cledoff — always enabled (placed outside the connect-gated fieldset, not safe-blocked).
• Run-view "TURN OFF LED" button (v0.45): #btnLedOff — always visible, sends SET_AO_VOLTAGE 0xA0 = 5000 mV.
• Both assume:
  • the rig has a BuckPuck LED driver on the Analog Out (0xA0) BNC, and
  • AO is in programmable mode (firmware refuses 0xA0 otherwise), and
  • the % → mV mapping is the hardcoded, approximate BUCKPUCK_CURVE in js/arena-runner-g6.js (digitized off a datasheet figure, ~few % accuracy) via the exported ledPercentToMv.

Desired (later)

1. Rig config declares the LED driver. Extend the rig YAML io: block so a rig can state it has an LED driver (driver type + which AO channel/role). Only show/enable the Console LED bar and the Run-view TURN OFF LED button when the loaded rig declares one; grey/hide otherwise. Parsing lives in parseRigIo (js/plugin-registry.js) + Studio.applyRigIo.
2. Rig config points to a calibration file in the repo. The rig entry should reference a per-rig calibration (measured % → mV, or mV → light) committed in the repo. Load it to drive ledPercentToMv instead of the hardcoded BUCKPUCK_CURVE, so the mapping is real/photometric per rig. Fall back to the current approximate curve when no calibration is declared.
3. Keep one source of truth for the curve (already: ledPercentToMv is shared by the Console bar and the protocol ledDrive command).

Touch points

• js/arena-runner-g6.js — BUCKPUCK_CURVE, ledPercentToMv, LED_OFF_MV
• arena_studio.html — Console led-bar (cledset/cledoff), Run-view #btnLedOff, rig io: application (applyRigIo)
• js/plugin-registry.js — parseRigIo (rig io: schema)
• rig config files + a new calibration file location/format in the repo

[mbreiser]

Also fold ball diameter into this rig-config work. As of v0.50 the oscilloscope's ball-diameter control was removed from the UI and hard-defaulted to 9 mm everywhere (forward-velocity calibration). It should come from the rig config (ball_diameter_mm) alongside the LED-driver + calibration declaration — same mechanism, so the scope's mm/s scaling is per-rig.

Touch points: js/arena-runner-g6.js / js/kinematics.js (forward-velocity calc uses ball radius), arena_studio.html Scope cfg.ballDiaMm / currentBallDia() (currently rig-value-or-9), and the rig io:/config schema.

[mbreiser]

The broader configuration architecture is now tracked in LAB-156: Design composable display, accessory, and physical-rig configuration. LAB-156 treats display geometry/controller defaults, accessory capabilities/calibrations, and physical rig composition as separate reusable layers; this GitHub issue remains the concrete LED gating/calibration and ball-diameter implementation ticket.