Verify the OPS243 firmware version 1.5.2 documented in ops243-uart-migration.md

[HuggeK]

Summary

docs/ops243-uart-migration.md:148 documents a real OPS243 reporting firmware 1.5.2, but OmniPreSense's published version matrix has no 1.5.x on the OPS243-A line. The number should be re-verified against hardware.

Where it appears

• docs/ops243-uart-migration.md#L148 — expected diagnose.py output: /dev/ttyAMA0 • firmware 1.5.2 • 230400 baud • dump ~2.0s
• tests/test_ops243_uart.py#L50, #L352, #L368 — {"Version":"1.5.2"} used as the ?V fixture

It reads as real captured output rather than a placeholder: scripts/hardware-test/diagnose.py#L269 builds exactly that string from radar.get_firmware_version().

Why it looks wrong

AN-010 rev AE Table 9 (OPS243-A Doppler Radar Feature versus Code Version Matrix) lists the OPS243-A line as:

1.2.3 → 1.2.4 → 1.2.5 → 1.2.6 → 1.3.0 → 1.3.1

1.3.1 is the newest column, and there is no 1.5.x anywhere in it. Table 7 covers OPS241-A/OPS242-A (1.3.1 → 1.4.0) — a separate numbering line that reuses the same numbers for different code, which makes cross-referencing versions easy to get wrong.

So 1.5.2 is either a build OmniPreSense doesn't document publicly, a value from a different product line, or a transcription error.

Why it matters

PR #221 gates --trigger hardware on exactly 1.3.1, because the SWn/SFn/STn/SMn rolling-buffer enhancements it drives appear only in that column. Anyone comparing their board against this doc will draw the wrong conclusion about whether they need a firmware update.

Suggested fix

1. Run ?? on the board (returns Product and Version together) and record both.
2. Update ops243-uart-migration.md#L148 and the test_ops243_uart.py fixtures to the confirmed value.
3. If it really is 1.5.2, worth asking OmniPreSense which line that build belongs to and noting it in the doc — it would be useful context for the feat(ops243): add internal hardware trigger #221 firmware gate.

_{Permalinks pinned to 2e8b611.}