BLACKBOX /Start hereLap timingSensor fusionHow it worksBuildMaths

Blackbox hardware acceptance checklist

Use this checklist for a specific board, wiring revision, GPS receiver, mounting arrangement, browser, and firmware artifact. A passing software build is a prerequisite, not a substitute. Do not label the release hardware-validated until the evidence below is recorded.

Record the test configuration

Wiring gate: the current IMU assignment is RX GPIO19 / TX GPIO18. These overlap native USB. Confirm the actual board routing before connecting the IMU and USB. Do not share these signals. Changing the pin mapping requires matching firmware and wiring changes. Check supply and signal voltages against the actual module specifications; do not assume a breakout label describes every pin's tolerance.

Target gate: current release images target ESP32-C3. The proposed schematic in PR #39 uses ESP32-S3-WROOM-1-N16R8; it requires a separate firmware port and electrical review. Do not flash the C3 image onto that design.

Weekend NEO-M9N data collection

  1. Complete the bench, USB, and axis checks below before driving. Select the M9N firmware variant and record the artifact SHA-256.
  2. Outdoors, wait for a fresh fix; record the Diagnostics GPS rate and satellite count. The configured target is 25 Hz, not proof of the actual delivered rate. Photograph the antenna position and IMU orientation.
  3. While parked, press Record session and confirm REC. An ordinary drive needs no selected track: use the Drive recording panel for duration and partial GPS observed distance. Select and arm a circuit/stage only for a later controlled timing test. Configure the desired display before setting off. Keep the dashboard foregrounded; screen lock or browser suspension can interrupt browser recording.
  4. For a normal neighborhood/highway drive, collect a couple of minutes parked outdoors, the ordinary drive, and a short parked segment at the end. No hard braking, weaving, or special maneuvers are needed. Repeated line-crossing validation belongs at a controlled site with an operator/reference. A passenger/operator should note any missed or unexpected crossing and an approximate time. Do not operate the UI while driving.
  5. While parked, stop recording. Open Saved data, export both Session CSV and GPS CSV (on timestamp-logging firmware), and use Tracks → Export for the track geometry. Keep a short text note with firmware, GPS model, wiring/mounting, browser/phone, weather/obstructions, and observed problems. Export before clearing site data.
  6. An independent timer or timestamped crossing video is needed to measure timing error. Without it, the logs can establish internal consistency and investigate failures, but not absolute lap-time accuracy. Share location-containing recordings privately, not in a public GitHub issue.

1. USB installation and recovery — bench

Pass: successful correct-chip write/reset/boot; cancelled/failed connections recover; no wrong-chip write. Record any configuration reset caused by the full image.

2. Startup, sensors, and stale-data handling — bench/outdoors

Pass: valid data and loss/recovery are distinguishable; no indefinite calibration/network wait; expected receiver configuration is confirmed rather than inferred from the filename.

3. Axes, calibration, and mounting — bench, then controlled motion

Pass: axes/signs and frame conventions agree with the known motion; no nonfinite values or discontinuous corrections. Record residuals rather than claiming a universal g-force accuracy bound.

4. Lap start/finish — controlled site

Use an operator/passenger or inspect logs after each run; do not manipulate the dashboard while driving. Mark a physical reference line and use a sufficiently wide software line spanning the route.

Functional pass: zero unexplained misses/false triggers in the defined valid-signal cases, correct direction and stage behavior, and explicit handling of outages. These sample counts are a minimum smoke test, not a statistical reliability guarantee.

5. Timing accuracy against a reference

Accuracy pass: the predefined budget is met under documented conditions, with no omitted failures. If no budget or adequate reference was defined, report “accuracy not established.”

6. Recording, storage, and export

Pass: stored data survives reload, exports are usable, gaps/failures are visible, and failed writes do not silently report success.

7. Power and endurance

Results record

Test / condition Firmware & hardware Expected Observed Evidence file Pass / fail / untested
USB write / reset / boot
GPS / IMU loss and recovery
Axes / mounting / calibration
Crossings / false triggers
Reference timing error
Recording / export / storage failure
Endurance / power interruption

Keep failures and untested cases visible. Promote a candidate to stable only when its intended hardware configuration meets the agreed acceptance criteria; a different board, mounting change, or GPS configuration needs renewed checks.

Point-to-point stage acceptance

Phone storage and bad-data acceptance

Backup and restore — browser acceptance

Spatial reference acceptance

Landscape cluster and offline fonts

Mount alignment and phone launch acceptance

GPS evidence capture

Mounting tilt consistency acceptance (issue #104)

Software regressions do not close physical incline/mounting validation (#73/#21). Record module identity, WT901 installation-direction settings, firmware commit, mounting photos and measured roll/pitch. Establish the upright, nearly level, parallel-to-car-floor baseline first. In a separate R&D experiment compare modest fixed dash-like pitch/roll, while keeping the road/site conditions comparable. The startup/alignment collection gates are not accepted physical tolerances.

Do not infer arbitrary/inverted mounting support, full 3D vehicle attitude, validated bank/grade compensation or tyre loads from these checks.

Runs chooser phone acceptance (issue #106)

Track suggestion phone acceptance (issue #116)

Drive recording and backup acceptance on both phones

For multipart backups, also run these checks against a disposable destination profile with enough free space. Keep the source untouched.

Run these checks while parked on the actual Android browser and iPhone Safari/Home Screen launch you intend to use. Keep the original recording/browser data and an external backup throughout. Software transaction/replay regressions have passed; a browser-tool file-picker stall leaves the latest real GUI import attempt unverified. Record each phone's observed result rather than treating desktop emulation as acceptance.

These are recovery and usability checks. They do not establish GPS distance accuracy, background recording, force calibration or timing error. Use the ordinary-drive plan first; controlled crossing and mounting experiments remain separate.