← Commit history
docs/HERO.mdadded+8
@@ -0,0 +1,8 @@+Generate `hero.png` for this folder in Hero Studio. It is the page-header image, reused on the homepage and the screensaver; the page overlays live stats on its lower third, so the image carries the title and artwork only.++New app/skill heroes MUST come from Hero Studio (the server rejects anything else with HERO_STUDIO_REQUIRED; the studio stamps provenance into the PNG and exports at 2000x1250):++1. `adom-wiki pkg install adom/hero-studio`+2. start it (`hero-studio`, port 8846) and open the webview so the human sees it+3. pose the hero (the UI, or POST /state), then Generate+4. copy `generated/latest.png` here as `docs/hero.png`
docs/hero.pngadded
⋯ 1 unchanged line ⋯
docs/plan/COMPONENTS.mdadded+20
@@ -0,0 +1,20 @@+# Component register — LED Grid Wall tile (rev A)++| Ref prefix | Part | Role | Wiki page | CAD status |+|---|---|---|---|---|+| D1..D1440 | Dialight 587-1024-147F | 2020 addressable RGB LED (WS2812-compatible, 5mA/ch, no ext cap) | adom/587-1024-147f | **page being authored** (symbol/footprint/STEP/GLB + provenance) |+| U1 | RP2040 | MCU, 4x PIO WS2812 chains, USB CDC | ray/rp2040 | full CAD ✓ |+| U2 | W25Q128FVSIG | 128Mbit QSPI flash, SOIC-8-208mil | adom/w25q128fvsig | full CAD ✓ |+| U3 | AP2112K-3.3 | 5V→3.3V LDO 600mA SOT-23-5 | adom/ap2112k-3.3 | full CAD ✓ |+| U4 | SN74AHCT125PWR | quad 3.3→5V data buffer, TSSOP-14 | adom/sn74ahct125pwr | full CAD ✓ |+| J1 | TYPE-C-31-M-12 | USB-C 16-pin receptacle (data+power) | adom/type-c-31-m-12 (private, adom org) | full CAD ✓ |+| MP1..MP4 | MachineContactLarge | 5V/GND power entry from scaffold (~20A each) | adom/machinecontactlarge | full CAD ✓ |+| Y1 | X322512MSB4SI | 12MHz crystal SMD3225, CL=20pF | adom/x322512msb4si | GLB only — **needs sym/mod/STEP added** (KiCad-official footprint) |+| C* | 0402B104J160CT 100nF, 0402X105K250CT 1uF, CL21A476MQYNNNE 47uF, 0402N330J500CT 33pF | decoupling/bulk/crystal load | Adom Basic Parts | full CAD ✓ |+| R* | 0402 27R (CR0402-FX-27R4GLF?) / 5.1k / 10k / 1k | USB series, CC pulldowns, pullups | Adom Basic Parts | full CAD ✓ |++## Notes+- Mouser sourcing for the LED: 645-587-1024-147F (20,947 in stock 2026-09-28, $0.37@500).+  Worldsemi WS2812B-2020 (existing basic part) is out of stock at LCSC/Adom and not Mouser-distributed.+- 3D discrepancy on adom/ws2812b-2020 filed as issue #1581 (not used in this design).+- USB-C page is private to adom org; fine for an internal build. Mark public later if the tile page goes public.
docs/plan/DECISIONS.mdadded+48
@@ -0,0 +1,48 @@+# LED Grid Wall — design decisions (2026-09-28)++## Goal+A huge contiguous grid of individually addressable mini RGB LEDs in an Adom workcell.+Remote Adom users each "own" one LED and set its color anytime; a live camera watches+the grid so users can find their pixel. Emergent collaborative art.++## Locked decisions (with the user)+1. **LED: Dialight 587-1024-147F** (Mouser 645-587-1024-147F)+   - 2020 package (2.0 x 2.0 x 0.9 mm) — the smallest addressable class, per user+   - Single-wire NRZ 800 kbps, 24-bit GRB — WS2812-protocol compatible (datasheet p.4)+   - No external capacitor required (datasheet p.2: self-contained IC + dies)+   - VDD 3.3–5.5 V, 5 mA/channel (dimmer than WS2812B-2020's 12 mA/ch — accepted tradeoff)+   - Mouser stock 20,947; $0.37 @500, $0.29 @9000+   - Pinout: 1=DOUT, 2=VDD, 3=DIN, 4=GND — NOT WS2812B-2020 footprint-compatible (VDD/GND swapped)+   - Sourcing note: user directed Mouser (in-house build); Mouser does not distribute Worldsemi.+     WS2812B-2020 (existing Adom basic part) is 0 stock at LCSC/Adom inventory, so the+     Dialight 2020 is the only Mouser-stocked 2020 single-wire addressable LED.+2. **Tile: ~160 x 160 mm, 9 tiles (3x3) on a LrgLrg 576x576 scaffold**+   - InstaPCB panel verified 300 x 380 mm (proforma 2026-08-21); with the user's 1" margin+     the max single board is ~249 x 329 mm — a 160 mm tile yields 2 per panel.+   - LED pitch 3.5 mm -> ~44 x 40 = ~1,760 LEDs per tile, ~15.8k total+   - MCU strip on the bottom edge of each tile so the LED field stays contiguous.+3. **MCU: RP2040 + USB-C per tile**+   - ray/rp2040 wiki component page exists; PIO drives 4 parallel WS2812 chains/tile+     (~440 LEDs/chain -> ~75 fps full-tile refresh)+   - Workcell host relays remote color commands over USB CDC; no RF on the tile.++## Support parts (all have wiki component pages)+- RP2040 — ray/rp2040+- Flash W25Q128 (SOIC-8) — adom/w25q128fvsig or jvsniq+- 12 MHz crystal SMD3225 — adom/x322512msb4si (or adom/abm8-272-t3)+- 3.3 V LDO AP2112K-3.3 (SOT-23-5, 600 mA) — adom/ap2112k-3.3+- Level shifter SN74AHCT125PWR (TSSOP-14, quad, 5 V Vcc, VIH=2V) — adom/sn74ahct125pwr+- USB-C receptacle 16-pin — adom/3d-xkb-u262-16xn+- Power entry XT60PW-M — adom/xt60pw-m-208a (20.8 A; firmware caps tile draw to <=20 A)+- Passives — Adom Basic Parts (100 nF/1 uF/10 uF MLCCs, 27R/1k/10k resistors)++## Power budget (per tile, worst case)+- 1,760 LEDs x 15.8 mA (3 ch x 5 mA + 0.8 mA idle) = 27.8 A peak @ 5 V (full white, uncapped)+- Firmware global power cap: <= 20 A/tile (100 W); typical art patterns ~10-20%.+- 9 tiles = 180 W capped, ~1.4 kW theoretical uncapped -> cap is mandatory.+- 4-layer stackup F.SIG / GND / V5 / B.SIG so inner planes carry LED current.++## Known issues found during selection+- adom/ws2812b-2020 page: STEP file header and geometry are a 5.0x5.0 mm 5050 model+  (bounds 6.45 x 6.25 x 1.6 mm), GLB is ~4 x 3.6 x 2.4 mm — neither matches the 2.0x2.0+  footprint. Filed for fixing; not used by this design (Dialight part instead).
docs/plan/GENERATOR-SPEC.mdadded+51
@@ -0,0 +1,51 @@+# Tile generator engineering spec (hand this to the implementer)++## Goal+Generate a complete KiCad 10 project for ONE LED-grid tile: `tile.kicad_pcb` (+ `tile.kicad_pro`, and a presentable hierarchical `tile.kicad_sch`), plus the two aiflow input files `moves.json` (placement) and `route-plan.json` (routing), all from one Python generator. Everything must be regenerable from source.++## Hard geometry+- Board: 160.0 x 160.0 mm. Origin (0,0) = top-left corner of the board outline; +x right, +y DOWN (KiCad pcb convention).+- 4 layers: F.Cu (0), In1.Cu (1) = GND plane, In2.Cu (2) = V5 plane, B.Cu (31) = B.Cu signal/GND rails.+- Stackup in the board file: 4 copper layers, 35um outer / 35um inner copper, 1.6mm total. JLC-style dielectric is fine.+- Edge.Cuts rectangle (0,0)-(160,160). Edge clearance for copper: 0.5mm. Clearance 0.2mm. Track min 0.15mm; via 0.6/0.3mm (0.45/0.2 allowed where tight).+- MCU strip: y in [144, 160] (bottom 16mm). LED field: y in [2.5, 142.5].++## LED field+- LED: Dialight 587-1024-147F, 2020 package. Footprint `Dialight_587-1024-147F`: 4 SMD pads 0.8x0.8mm at (+/-0.45, +/-0.45)mm; pin 1=DOUT, 2=VDD, 3=DIN, 4=GND (pad-to-corner assignment must match the published footprint file, parse it, do not hardcode corners). Courtyard 2.8x2.8mm.+- Grid: 40 columns x 36 rows, pitch 4.0mm. x_i = 4.0 + i*4.0 (i=0..39) -> 4.0..160-4.0. y_j = 2.5 + 2.0 + j*4.0 (j=0..35) -> rows centered in field, exact margin computed by the generator (state it).+- Refs: D1..D1440 numbered in CHAIN order (see below), so firmware index == ref order.+- Chains: 4 chains x 360 LEDs. Chain c (0..3) covers rows 9c..9c+8, serpentine: even global row left->right, odd row right->left. So chain order within chain c: for local row r in 0..8, global row j=9c+r; if j even: i=0..39 ascending, else descending.+- LED orientation: the generator chooses 0/90/180/270 rotation per LED to keep every DOUT->DIN link <= 3.2mm and inside the inter-cell gutters. All LEDs in the field MUST end up with the same visual orientation (lens/pin-1 mark facing the same way) UNLESS a wrap link forces otherwise; prefer uniform 0° with links in gutters; if the pad map makes that impossible, use per-row alternation but keep it consistent within a row and document the pattern.+- Data links: DOUT(k) -> DIN(k+1), straight or single-L traces 0.25mm wide on F.Cu, in the horizontal or vertical gutters between cells. No vias on data links except the 4 chain-input feeds (from U4 outputs on B.Cu up to the first LED of each chain).+- VDD distribution: one horizontal VDD rail per row on F.Cu, 0.9mm wide, running in the 2mm gutter between rows (exact y computed to clear pads by >=0.2mm). Each LED's VDD pad stubs to its row's rail (short vertical stub, part of the rail path or its own tiny path entry). Rails stitch to In2.Cu (V5) with a 0.6/0.3 via every 5th LED position (8 vias per row rail).+- GND: each LED's GND pad gets a via-in-pad-adjacent 0.6/0.3 via to In1.Cu (GND) — one via per LED placed in the gutter 1.1mm clear of everything. If DRC fights this, switch to: GND rails on B.Cu between rows + via per LED to the B rail. Pick ONE scheme, verify with DRC, document it.+- NO silkscreen ref text per LED (1440 labels = unreadable). Set reference hidden on LED footprints; keep a small row/column index silk every 4 rows/cols on F.SilkS if it fits without overlap (optional, else none).++## MCU strip (y 144..160) — parts and fixed placement intent+Left to right: J1 USB-C (TYPE-C-31-M-12) at left edge x~8 (connector overhangs board edge per its footprint), decoupling cluster, Y1 crystal near U1, U1 RP2040 (x~55), U2 W25Q128FVSIG flash, U3 AP2112K-3.3 LDO, U4 SN74AHCT125PWR, MP1/MP2 MachineContactLarge (V5) and MP3/MP4 (GND) at right edge x~130/145. All on F.Cu side.+Schematic connectivity (the MCU section):+- USB-C: VBUS -> V5 net; GND -> GND; CC1/CC2 -> 5.6k to GND each (R); D+ -> 22R -> RP2040 USB_DP; D- -> 22R -> RP2040 USB_DM; shield -> GND via 1Meg || 100nF? NO — tie shield directly to GND (simple, internal fixture).+- U3 AP2112K-3.3: IN=V5 (with 1uF + 10uF to GND), OUT=V3V3 (1uF + 10uF), GND=GND. (EN pin tied to IN per datasheet.)+- RP2040: IOVDD pins -> V3V3 (100nF each to GND, placed adjacent); DVDD pins -> V1V1 (100nF each); VREG_IN -> V3V3; VREG_VOUT -> V1V1 with 1uF; USB_VDD -> V3V3; ADC_AVDD -> V3V3; GND pads + exposed pad -> GND; RUN -> 10k to V3V3 + test pad to GND; XIN/XOUT -> Y1 (12MHz, 2x 33pF to GND); QSPI_SD0..3/SCLK/SS -> U2 pins (SOIC-8: 1=CS#/QSPI_SS, 2=DO/SD1, 3=WP#/SD2, 4=GND, 5=DI/SD0, 6=CLK/SCLK, 7=HOLD#/SD3, 8=VCC->V3V3+100nF). SWDIO/SWCLK -> 2 test pads (bare pads are fine, no purchased part). GPIO0..GPIO3 -> U4 inputs 1A..4A; U4 outputs 1Y..4Y -> chain input nets DIN_C0..DIN_C3; U4 OE pins -> GND (always enabled); U4 VCC -> V5 (100nF), GND -> GND.+- Bulk: 4x 47uF 0805 (CL21A476MQYNNNE) on V5 near the machine contacts.+- Nets: V5, GND, V3V3, V1V1, USB_DP, USB_DM, XIN, XOUT, QSPI_*, DIN_C0..3, GPIO0..3 (net names A1..A4 side), plus DC{c}_{k:03d} chain link nets (k=0..359 per chain: DC0_000 connects D(chain c, idx 0).DOUT? NO — DC{c}_{k} is the net BETWEEN LED k's DOUT and LED k+1's DIN; the first LED's DIN is net DIN_C{c}. The last LED's DOUT is left unconnected (net DC{c}_0359 is just the last DOUT, fine).+- RP2040 symbol pin mapping: READ parts/lib/rp2040.kicad_sym for the real pin numbers/names — do not invent. Same for all symbols.++## Passives+Use Adom Basic Parts values only: 100nF 0402 (0402B104J160CT), 1uF 0402 (0402X105K250CT), 47uF 0805 (CL21A476MQYNNNE), 33pF 0402 C0G (0402N330J500CT), 22R 0402 (CR0402-FX-22R0GLF), 5.6k 0402 (CR0402-FX-5601GLF), 10k 0402 (CR0402-FX-1002GLF). KiCad stock `Resistor_SMD:R_0402_1005Metric` / `Capacitor_SMD:C_0402_1005Metric` / `C_0805_2012Metric` footprints and stock 3D models are acceptable for these (KiCad 10 ships them on the desktop at C:/Users/john/AppData/Local/Programs/KiCad/10.0/share/kicad). Symbols: stock `Device:R` / `Device:C`.++## 3D models+Every footprint needs a 3D binding: wiki STEP files live in parts/lib/*.step — copy them into the project at lib3d/ and reference with project-relative paths (`${KIPRJMOD}/lib3d/...`). For stock passives use the KiCad stock model paths (${KICAD10_3DMODEL_DIR}/...). The Dialight STEP comes from the component page being authored at parts/dialight-587-1024-147f/ (if not ready, generate a placeholder 2.0x2.0x0.9 box STEP and mark it for swap).++## Outputs+1. `tile.kicad_pcb` — all 1440 LEDs + ~35 MCU-strip parts, all pads net-assigned, parts initially PLACED AT FINAL POSITIONS except: ALSO emit `tile-parked.kicad_pcb` identical but with every footprint parked in a tidy holding cluster off the left of the board (x in [-60,-5]) — aiflow `place land` will move them in one at a time on camera.+2. `moves.json` — {"D1": {"x":..., "y":..., "rotation":...}, ...} final position for every ref (aiflow `place land --moves`).+3. `route-plan.json` — aiflow routing plan schema: [{"net": "...", "width": w, "viaSize": 0.6, "viaDrill": 0.3, "paths": [[<waypoints>]]}], waypoint = "REF.PAD" | [x,y] | {"x":..,"y":..,"layer":"B.Cu"} (layer objects are via/transition points). Every LED chain link, every rail (as a path along the rail with via waypoints to In2.Cu), every GND via (as a 2-point path pad->{x,y,layer}), and the whole MCU section, routed with Manhattan geometry, no crossings on a layer except where a via transition is explicitly written. Rails listed as their own paths on the V5/GND nets.+4. `tile.kicad_sch` + `chain.kicad_sch` — root sheet (MCU section, full) + one chain subsheet (360 LED symbols, chained) instantiated 4x. Symbol placement in a readable serpentine grid. This must parse in KiCad (service-kicad sch erc). Consistent refs with the PCB.+5. `gen_tile.py` — the single generator; everything above is regenerated by `python3 gen_tile.py`.++## Validation gates (must all pass before reporting done)+- `service-kicad pcb drc` (or the closest verb) on tile.kicad_pcb: parse OK, and 0 errors in the un-routed state except expected unconnected nets (no clearance violations from placement: courtyards may touch gutters but pads must not violate 0.2mm clearance).+- Open the board on the desktop via the kicad bridge (`adom-bridge --ai-thread "LED grid scaffold" kicad_open_board ...` — read /home/adom/.kimi-code/skills/kicad-bridge/SKILL.md first) and screenshot it in the background: the grid and MCU strip must look right. Save PNG to clips/gen-board-check.png. Do NOT save the board from KiCad (file is generated).+- Run a self-DRC after applying moves+routes LOCALLY (generate tile-routed.kicad_pcb with all tracks/vias written into the file directly — same geometry as route-plan.json): service-kicad DRC must be 0 violations (unconnected=0). This proves the plan is landable before we spend an hour landing it live.+- Report: LED count, net count, via count, any clearance compromises, and the exact rail/via scheme chosen.
package.jsonadded+29
@@ -0,0 +1,29 @@+{+  "slug": "led-grid-wall",+  "title": "LED Grid Wall \u2014 own a pixel in the Adom workcell",+  "type": "hardware",+  "kind": "project",+  "version": "0.1.0",+  "description": "A 12,960-LED addressable wall for the Adom workcell: 9 identical 160x160mm tiles (1,440 Dialight 587-1024-147F 2020 LEDs each, RP2040 + USB-C per tile) on a LrgLrg 576x576 scaffold. Remote Adom users each own a pixel.",+  "tags": [+    "hardware",+    "project",+    "led",+    "ws2812",+    "scaffold",+    "workcell",+    "interactive"+  ],+  "dependencies": {},+  "component": {+    "mpn": "",+    "distributor_links": {+      "digikey": "",+      "mouser": "",+      "lcsc": ""+    }+  },+  "hero": {+    "path": "docs/hero.png"+  }+}\ No newline at end of file