Maestro
Live demo — data resets daily at 03:00 UTC. Nothing you enter is saved.

Collimator LED Control Box

ESH10000672 · Rev R1

in_progresssystemtestAvstämning

Collimator LED Control Box — R1. Unit-level (system) product: a precision current-source hub built on the Accordion M1 platform, trimmed for a customer to control their LED range. Successor to R0 (R0 lived only in the filesystem workbook, not Trace).

Architecture — Accordion M1 platform: a Raspberry Pi 4B on the mainboard hosts the module stack and exposes a C#/Python API over USB. USB-C PD 20 V / 100 W input. Hammond 1455N1201BK enclosure, Phoenix Contact push-in I/O, active cooling, physical power button.

Module stack (each its own Trace project — dependencies): | Role | Project | Rev | |---|---|---| | Mainboard / system controller (RPi4B carrier) | ESH10000597 | R1 | | Precision ADC/DAC (16-bit set / 24-bit readback) | ESH10000590 | R2 | | 8-ch current source (LED outputs) | ESH10000584 | R1 | | Mini-PSU Precision Module (light-table power) | ESH10000690 | R0 |

Capabilities: 8 × LED current channels 0–450 mA (16-bit set / 24-bit readback); 2 × light-table voltage channels 0–24 V at up to 1.5 A; switched external-PSU control; 2-point calibration stored in NVM; software-controllable status LEDs.

This is a unit-level project — requirements are stated from the unit perspective; module/mainboard internal design is owned by the respective ESH projects (linked as dependencies). Requirements REQ-001…026 inherited (Draft) from the R0 baseline. Verification plan and issue list to be rebuilt for R1.

Reports Milestones (5)Audit Log

Everything here lives inside a Project (a code + revision, e.g. ESH10000540 R3). The backbone is the V-model, read top-to-bottom: define what the product must do, plan how to prove it, execute the proof on real units, then learn from the field — and the Loop closes back up to the top.
This map is live: a block is green with a count when this project actually has that entity, and dashed/dim when it’s empty. Click any block to open its tab; hover for details. Arrows are the meaningful links; the implicit “belongs to this Project” edge is left out for legibility.

What each thing means

Requirement
One thing the product must do or satisfy — the “what”.
Test Case
A defined check that proves one or more requirements — the “how we prove it”. A verified_by trace link ties a test case to the requirement(s) it covers; that link is exactly what Coverage % counts. (So: a test case refers to the requirements it verifies.)
Verification Plan
A named grouping of test cases, approved before a test campaign and optionally gated by a milestone.
Verification Record
The result of running one test case against one unit: pass / fail / error / na. This is the evidence a requirement is actually met.
DUT
Device Under Test — an individual physical unit (by serial number) that records and test data attach to.
Deviation
A documented waiver against a verification record (e.g. accept a known non-conformance, with justification).
Entry
A knowledge note: a decision (settled choice), notice (assumption / risk / open question), issue (tracked problem), or concept (idea under exploration). It can attach to any other entity.
Design Rule
A reusable, checkable engineering constraint. Running the checks turns each violation into a Conflict.
Conflict
An open flag raised by a failed design-rule check (or an end-of-life / component-library issue) that needs resolving.
Milestone
A dated gate; verification plans can be tied to it.
Field Issue (RMA)
A failure reported from the field on a returned unit; Root-Cause Analysis explains why it happened.
The Loop (S-16)
loop_trace reconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?). closes_loop records the corrective decision or design rule so the lesson is captured — and clears the project’s open-loop count.
Interface / Port
A contract between projects; each port can be driven by a requirement (and cascade one into the connected project).
BOM Component
A part on this project’s bill of materials, optionally linked to the shared Component Library.
GRR Study
A Gauge R&R study measuring how repeatable a test case’s measurement is.
Test Data
Production / Maestro run results recorded against DUTs — the population behind a single verification record.
0% Coverage
0% Done
26 Requirements
28 Open Entries

Timeline

Color = derived gate state · hover a tile for its note.
marker
Panel tape-out
Jun 26, 2026
marker
Integration build & bring-up
Aug 28, 2026
marker
DVT verification complete
Sep 4, 2026
marker
Customer delivery & sign-off
Sep 18, 2026
achieved
Requirements approved
no date· 1/1
not started
🏁 Release
· 4/6

Status & gates

Chronological — Release is the final gate. Derived & read-only; edit via trace_milestone_* tools.
MS-002Panel tape-out markerdue 2026-06-26
MS-003Integration build & bring-up markerdue 2026-08-28
MS-004DVT verification complete markerdue 2026-09-04
MS-005Customer delivery & sign-off markerdue 2026-09-18
MS-001Requirements approved achieved 1/1 met
met Requirements approved
Release / Readiness not started 4/6 met
met Requirements approved
pending Coverage ≥ 100%
  • 0/26 requirements covered (0%)
pending All test cases pass
  • No test cases in scope
met No blocking issues open
met Deviations resolved
met Interfaces frozen
Composition 2 dependencies need attention: ESH10000597 R1 (amber), ESH10000690 R0 (amber)

Coverage — 0.0% · Done — 0.0%

0 Done 0 Partial 0 Not Started 26 Missing0 Obsolete
Requirements
26 of 26
CodeTitleCategoryCoverageStatus
REQ-001 8 independently controllable LED current channels FunctionalMissing—
REQ-002 LED channel current range 0–450 mA PerformanceMissing—
REQ-003 LED current control resolution 16-bit PerformanceMissing—
REQ-004 LED current measurement 24-bit ADC PerformanceMissing—
REQ-005 LED channel settling time documented PerformanceMissing—
REQ-006 2 independently controllable light-table voltage channels FunctionalMissing—
REQ-007 Light-table regulation 0–24 V at up to 1.5 A PerformanceMissing—
REQ-008 Light-table voltage resolution 12-bit PerformanceMissing—
REQ-009 Switched on/off control of external PSU FunctionalMissing—
REQ-010 C# and Python API over USB InterfaceMissing—
REQ-011 Powered from USB PD 20 V / 100 W InterfaceMissing—
REQ-012 Hammond 1455N1201BK enclosure MechanicalMissing—
REQ-013 Phoenix Contact push-in external connectors MechanicalMissing—
REQ-014 Unique serial number label MechanicalMissing—
REQ-015 Internal temp ≤ 50 °C at full load, 23 °C ambient EnvironmentalMissing—
REQ-016 IR-LED load compatibility FunctionalMissing—
REQ-017 Active cooling (fan) MechanicalMissing—
REQ-018 Physical power on/off button MechanicalMissing—
REQ-019 Clamp voltage 5 V; dissipation ≤ 0.79 W/ch, ≤ 6.3 W total PerformanceMissing—
REQ-020 Light-table current limit 0–1.5 A, 12-bit PerformanceMissing—
REQ-021 2-point calibration of all 8 LED channels FunctionalMissing—
REQ-022 2-point calibration of both light-table channels FunctionalMissing—
REQ-023 Calibration coefficients in NVM, applied at power-on FunctionalMissing—
REQ-024 Post-calibration accuracy PerformanceMissing—
REQ-025 All status LEDs software-controllable, toggle-off via API FunctionalMissing—
REQ-026 Per-channel ADC current readback functional on all 8 channels DesignMissing—