Accordion Beacon Module
ESH10000671 · Rev R0
in_progresselectronics
Battery-powered WiFi module that extends a Raspberry Pi's serial bus (I2C, UART, SPI) over WiFi using MQTT. SX1276 LoRa 868 MHz transceiver supplements WiFi for long-range parallel operation. LiPo powered with USB-C charging (BQ24075), 3.3V LDO (MCP1700), ESP32-C6-MINI-1-N4 MCU.
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_tracereconciles a field issue against that unit’s own verification record (did it pass at the edge of the band?).closes_looprecords 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.
100%
Coverage
35%
Done
34
Requirements
47
Test Cases
2
Blockers
24
Open Entries
Timeline
Color = derived gate state · hover a tile for its note.marker
Bring-up
overdue / blocked
Base Functions Verified
overdue / blocked
WiFi Functionality Verified
overdue / blocked
LoRa Functionality Verified
overdue / blocked
Battery Functionality Verified
overdue / blocked
Verification Wrap-Up
marker
Release
not started
🏁 Release
Status & gates
Chronological — Release is the final gate. Derived & read-only; edit viatrace_milestone_* tools.MS-001Bring-up
markerdue 2026-06-05MS-002Base Functions Verified
overdue / blocked
0/1 metdue 2026-06-12
pending Plan PLAN-001 — Base Functions
- 12/23 passed
- 11 not yet run
MS-003WiFi Functionality Verified
overdue / blocked
0/1 metdue 2026-06-19
pending Plan PLAN-002 — WiFi Functionality
- 2/5 passed
- 3 not yet run
MS-004LoRa Functionality Verified
overdue / blocked
0/1 metdue 2026-06-26
pending Plan PLAN-003 — LoRa Functionality
- 1/4 passed
- 3 not yet run
MS-005Battery Functionality Verified
overdue / blocked
0/1 metdue 2026-07-03
pending Plan PLAN-004 — Battery Functionality
- 0/6 passed
- 6 not yet run
MS-006Verification Wrap-Up
overdue / blocked
0/1 metdue 2026-07-10
pending Plan PLAN-005 — Verification Wrap-Up
- 0/3 passed
- 3 not yet run
MS-007Release
markerdue 2026-07-17Release / Readiness not started 4/6 met
met
Requirements approved
met Coverage ≥ 100%
- 34/34 requirements covered (100%)
pending All test cases pass
- 15/47 passed
- 32 not yet run
pending No blocking issues open
- E-023: open blocker
- E-028: open blocker
met
Deviations resolved
met
Interfaces frozen
Test Cases
15 Pass
0 Fail / Deviated
0 N/A
32 Open0 / 47 Maestro impl.
Coverage — 100.0% · Done — 35.3%
| Code | Title | Category | Coverage | Status |
|---|---|---|---|---|
REQ-001 |
Battery Charging | Functional | Covered | Done |
REQ-002 |
Power Path Output | Performance | Covered | Done |
REQ-004 |
Charge Status Indication | Functional | Covered | Done |
REQ-005 |
Battery Connector | Mechanical | Covered | Not Started |
REQ-007 |
3.3V Rail | Functional | Covered | Partial |
REQ-011 |
Battery Voltage Monitoring | Functional | Covered | Not Started |
REQ-015 |
MCU Boot and USB Detection | Functional | Covered | Done |
REQ-016 |
MCU Supply Voltage | Performance | Covered | Partial |
REQ-017 |
Deep Sleep Current | Performance | Covered | Not Started |
REQ-018 |
WiFi Connectivity | Functional | Covered | Done |
REQ-019 |
BLE Advertisement | Functional | Covered | Not Started |
REQ-020 |
External Serial Bus Connector (J3) | Interface | Covered | Partial |
REQ-021 |
External UART | Interface | Covered | Not Started |
REQ-022 |
External SPI Bus | Interface | Covered | Not Started |
REQ-024 |
USB-C Power Supply | Functional | Covered | Partial |
REQ-025 |
ESD Protection | Safety | Covered | Partial |
REQ-026 |
RF Isolation | Mechanical | Covered | Not Started |
REQ-030 |
Test Point Access | Mechanical | Covered | Done |
REQ-031 |
MQTT Communication | Functional | Covered | Done |
REQ-033 |
Sleep Mode Control | Functional | Covered | Partial |
REQ-034 |
Wake-to-Transmit Time | Performance | Covered | Not Started |
REQ-035 |
Battery Runtime | Performance | Covered | Not Started |
REQ-037 |
GPIO Expander Presence | Functional | Covered | Done |
REQ-041 |
System Monitor Presence | Functional | Covered | Done |
REQ-046 |
Battery Supply | Functional | Covered | Done |
REQ-047 |
Power Source Selection | Functional | Covered | Done |
REQ-050 |
LoRa Transceiver Presence | Functional | Covered | Partial |
REQ-051 |
RF Supply Rail | Performance | Covered | Done |
REQ-052 |
Transceiver Supply Voltage | Performance | Covered | Not Started |
REQ-053 |
Transceiver Clock | Performance | Covered | Not Started |
REQ-057 |
LoRa and WiFi Concurrent Operation | Functional | Covered | Not Started |
REQ-058 |
Voltage Reference | Performance | Covered | Partial |
REQ-059 |
Battery Current Monitoring | Functional | Covered | Not Started |
REQ-061 |
Production Readiness | Functional | Covered | Not Started |