part-specs: obstacle-avoidance camera (OmniVision OV5647)

[OsakaTX]

Summary

Adds part-specs coverage for the obstacle-avoidance camera (OmniVision OV5647) that was added to BOM.md on 2026-07-18 (commit 6b8f59c), bringing the camera to the same spec-coverage level as the LiDAR, ToF, and IMU sensors.

One new file under contributions/part-specs/OsakaTX/, disjoint from the recently merged part-specs work (no README.md edit, no shared-file overlap).

What this adds

obstacle-avoidance-camera-ov5647.md:

• OV5647 sensor-level specs (5 MP / 2592 × 1944, 1/4", 1.4 µm pixels, 3.76 × 2.74 mm image area, MIPI CSI-2 2-lane).
• The BOM module entry (16-pin cable, ~130° wide lens, no IR-cut filter, $6-7 night-vision variant).
• The Raspberry Pi CSI-2 connector pinout (15-pin reference + 22-pin superset), with the third-party 16-pin FPC flagged as vendor-specific.
• Rationale for a no-IR-cut sensor + IR illuminator for low-light obstacle detection, and a "What We Still Need" gap list.

Source verification

• BOM entry quoted verbatim from upstream BOM.md (commit 6b8f59c).
• All sensor specs (OV5647, 5 MP, 1/4", 1.4 µm × 1.4 µm, 3.76 × 2.74 mm) match the official Raspberry Pi camera documentation.
• OV5647 = Camera Module 1 sensor confirmed; the 15-pin CSI pinout + Amphenol SFW15R-2STE1LF part number cross-checked against independent references.
• Items needing physical inspection (exact 16-pin FPC map, lens focal length, IR illuminator wavelength/drive, PCB dimensions, power) are explicitly marked as unverified.

Notes

• Compute module is noted as CM4 or CM5 ≥2 GB per BOM.md (CM4 primary, CM5 alternative); the CSI connector is 15-pin on the CM4 IO board and 22-pin on the CM5 IO board.
• Intentionally disjoint from the merged part-specs files to keep it independently mergeable.

[makers-pet]

Hi OsakaTX, thank you for the PR! The OV5647 content looks great, but the branch is based on old main (re-adds vacuumtiger-verified-specs.md already merged in #25, identical copy). It also re-touches the README, which will conflict.

Could you please git pull/rebase onto current main, drop the duplicate vacuumtiger file, and reduce the README change to just the new camera section?

I couldn't help noticing that PR description says "no README edit / no overlap," but the diff does both - that's the stale branch. This is the same thing that split #22-24, so rebasing would fix that.

[makers-pet]

Hi xbattlax, thank you for the PR! Would you kindly (1) rebase on current main - and (2) scope it to your own namespace?

• the main branch has moved on
• the new io-board-interface module (and your namespaced contract) is a good idea
• can you please drop the dock-cycle edit (that RFC was just updated with the IR-homing design, and the obstacle camera now lives in the new obstacle-avoidance module)
• could you please remove the part-specs/OsakaTX edit (that's another contributor's folder, and it links three files that aren't in the PR)
• ARCHITECTURE/SOFTWARE_INTERFACES/io-pcb touch-ups look good, please leave them as clearly marked proposals. I'll check the serial contract with the PCB designer since it constrains the board.

[xbattlax]

Thanks, fixed on oomwoo#27: rebased on current main, removed the dock-cycle RFC edit, removed the part-specs/OsakaTX edit, and kept the architecture/software-interface/io-pcb changes as draft/proposed notes.

Current PR head is 1d6482f.

[OsakaTX]

Thanks for the catch! Rebased on current main - the branch now contains only obstacle-avoidance-camera-ov5647.md; the already-merged vacuumtiger-verified-specs.md and README changes are removed. Should be a clean single-file diff now.

[makers-pet]

Thank you agian, OsakaTX!