Skip to content
LBZF Design Docs

Pre-Argentina hardware testing

The canonical pre-flight checklist for the 2026-05-15 BA departure lives at the G1 gate. This doc is the hardware-bucket pointer to that gate plus the bench-test environment notes that aren’t gate-checklist material.

Do not duplicate the gate checklist here. If a check belongs to G1, edit G1-argentina-demo.md.

What G1 covers

Section titled “What G1 covers”

The G1 gate tracks pass criteria across four areas:

  • Hardware bench-test (CA, before flight) — Jetson flashed with JetPack 6.0/6.1, root migrated to NVMe, OpenCV+GStreamer, YOLOv8n TensorRT engine compiled on-device, one Amcrest camera streaming, inference at 3–5 fps, dashboard tile + SQLite write + Excel export all working.
  • Network + remote ops — Tailscale ACL with tag:lbzf-jetson + tag:itba-dev, paid Starter tier, cellular-network reachability, Amcrest VLAN + cloud-block verified.
  • BA twin set — ITBA Jetson received, flashed, smoke-tested, ITBA SSH keys collected, Tailscale-authenticated with tag:itba-dev, restore microSD packed.
  • Demo materials + customs/logistics — architecture diagram, 90-second pre-recorded demo video, Spanish hand-off one-pager draft, bilingual customs letters from Mariana (LBZF) and Raul Marino (ITBA), bag split.

Each item maps directly to an ADR or to one of the other hardware docs:

Bench-test environment (CA)

Section titled “Bench-test environment (CA)”

Sophia’s home / lab desk. Set up:

  • A small table for the TL-SG2210MP + 1 Amcrest camera + the LBZF Jetson during single-stream tests.
  • A “pretend workstation”: chair + task light + printed photo of a sewing machine. Aim the camera at this; it’s the operator location for cycle-event tests.
  • A laptop on the same LAN (Wi-Fi or wired) for browser dashboard access.
  • A phone on cellular hotspot (NOT lab Wi-Fi) for cross-network Tailscale tests.

Both Jetsons (LBZF + ITBA twin) get flashed and smoke-tested in this environment between Mon 2026-05-11 and Wed 2026-05-13. The ITBA Jetson then gets hostname itba-jetson-01, ITBA SSH keys, and Tailscale installed but unauthenticated — see argentina-twin-set.md.

Schedule shape

Section titled “Schedule shape”

The bench-test window is compressed but the ADR work landed 2026-05-11, so by the time hardware testing starts the technical decisions are frozen. Schedule:

DayFocus
Mon 2026-05-11Receive last-mile parts (PWM fan, NVMe heatsink, plug adapter, Cat6 patch); flash LBZF Jetson; install packages; build TensorRT engine on-device
Tue 2026-05-12Single-camera RTSP from Amcrest; YOLOv8n inference + SQLite + dashboard end-to-end; Tailscale auth + cellular verification; record 90s demo video
Wed 2026-05-13Flash + smoke-test ITBA Jetson with same image; bake in ITBA SSH keys; differentiate hostname; failure-mode rehearsal (yank Cat6, pull Jetson power); Andrew go/no-go review
Thu 2026-05-14Pack, print customs letters, final tailnet sanity check
Thu 2026-05-15Fly CA → BA

Go / no-go

Section titled “Go / no-go”

Wednesday evening review with Andrew. Go if the G1 gate checklist is green or the open items have explicit acceptance notes (e.g., “ITBA Tailscale auth happens on first boot in BA, not in CA — accepted”).

If critical gate items are red (no Tailscale paid tier upgraded, ITBA Jetson didn’t arrive, TensorRT engine doesn’t compile), postpone the flight 24–48 hours. The Tuesday ITBA presentation is a design-presentation event per argentina-twin-set.md — landing late with working hardware beats landing on time with broken hardware.

Bench-test limitations to call out

Section titled “Bench-test limitations to call out”

The CA bench does not replicate Pereira. Things that will only be validated on-site:

  • Lighting / motion in a sewing factory — fluorescent + LED task light + machine vibration are not the office lighting in CA.
  • Network behavior on the actual plant LAN — Huawei GPON DHCP quirks, broadcast load from POS / ERP traffic, ISP carrier-grade NAT affecting Tailscale DERP relays.
  • Thermal under sustained 24/7 load in 22°C / 70–80% humidity — CA bench is hours, Pereira is months.
  • Operator-presence cycle detection with actual fabric/machine occlusion — bench-test uses Sophia walking in/out of frame, which is much cleaner than a real operator at a station.

These are flagged for the install-day verification (install-runbook.md) and the first post-deploy week of monitoring, not for pre-flight bench testing.

Cross-bucket dependencies

Section titled “Cross-bucket dependencies”
  • G1 gate (../../10-gates/G1-argentina-demo.md) — canonical checklist; this doc points to it.
  • Jetson spec (jetson-edge-compute.md) — every test exercises the spec.
  • Network (network-and-tailscale.md) — Tailscale ACL must be pushed and verified before flight.
  • Backend bucket — lbzf-monitor + dashboard binaries must exist as runnable artifacts by Mon evening or T2-onward bench tests can’t run.
  • Frontend bucket — dashboard HTML/JS for the demo video.