Bench test · in progress

ToF Distance Test — 50059 & 500214

Controlled test of whether the VL53L1X distance channel returns a reading, and how distance_mm and range_status behave across cap state and medium. This page records conditions, timings and raw readings only. No diagnosis or conclusion is drawn here — that comes after the test.

auto every 60 s

Loading…

1Conditions

Stated by Evan unless marked measured.

2Event timeline

Time (Mountain)	UTC	Sensor	Event	Source

3Distance and range status

Every distance_mm value is plotted, whatever its range_status. Filled circles are range_status = 0, open squares are range_status = 3; the status is also shown on its own strip below. Nothing is filtered or excluded. Vertical dashed lines mark recorded events.

4TLF (mon2)

mon2 at the calibrated operating point: LED 512, sipm_bias nearest 3000 (band 2960–3040), one sample per reading. mon2_dark is the same read with the LED off. Net is mon2 − mon2_dark.

5Return signal

6Response by condition

Every reading, grouped by test condition, split by sensor and by the firmware build running at that moment. Each point is one reading; the bar is the median. Cells are shaded on a per-channel scale (log, spanning every block and condition) — the same value is the same colour everywhere, so blocks can be compared directly. The range column is each row's own max÷min.

7All readings

Every row as recorded. Green rows are range_status = 0.

Time (Mountain)	Sensor	mon2	mon2_dark	net	dist_mm	range_status	signal_rate	sig/SPAD	ambient	amb/SPAD	SPADs	sigma_mm

Data from Pumphaus api_samplesraw, regenerated by scripts/build_tof_experiment.js. Pulled directly from Postgres because the /tof/ proxy does not serve range_status.