Two user-facing docs gaps left by #609 / ADR 0027.
1. Troubleshooting: "I changed the lens and now it never solves"
ADR 0027 makes the solver's FOV gate follow the lens the user says is fitted, and deliberately does not recover from a wrong answer — self-healing would add a recovery path through the solver's hot loop for a once-per-device setting. That decision is only defensible if the failure documents cleanly, which is currently doesn't exist.
What the page needs to say:
Suggested home: the troubleshooting section of the user guide, cross-linked from wherever the Lens setting is documented. Worth a mention in the Lens menu documentation itself too, since that is where someone changing the setting will be looking.
The new menu also wants documenting in its own right — Settings → Advanced → Lens, three options (12mm / 16mm / 25mm), defaulting to whatever the device shipped with.
2. docs/source/BOM.rst:96 gives imx462-specific advice
- Other lenses might work here, but something fast with a 10deg FOV is ideal
10° is right for a 16 mm lens on an imx462 (10.40°). It is wrong for the other shipped trains:
| sensor |
shipped lens |
field of view |
| imx296 |
16 mm |
13.71° |
| imx462 / imx290 |
16 mm |
10.40° |
| hq |
25 mm |
10.33° |
Since the same BOM section says you can use either the imx296 or the imx462 module, the advice contradicts the parts list two lines above it. Better framing is probably the focal length (which is what the buyer actually selects) rather than a resulting FOV — the same 16 mm lens gives different fields on the two sensors.
Worth also noting the bundled tetra3 database is built for 10–30°, which is the real constraint on "what lens might work here".
Found while implementing #609 / ADR 0027.
Two user-facing docs gaps left by #609 / ADR 0027.
1. Troubleshooting: "I changed the lens and now it never solves"
ADR 0027 makes the solver's FOV gate follow the lens the user says is fitted, and deliberately does not recover from a wrong answer — self-healing would add a recovery path through the solver's hot loop for a once-per-device setting. That decision is only defensible if the failure documents cleanly, which is currently doesn't exist.
What the page needs to say:
Suggested home: the troubleshooting section of the user guide, cross-linked from wherever the Lens setting is documented. Worth a mention in the Lens menu documentation itself too, since that is where someone changing the setting will be looking.
The new menu also wants documenting in its own right — Settings → Advanced → Lens, three options (12mm / 16mm / 25mm), defaulting to whatever the device shipped with.
2.
docs/source/BOM.rst:96gives imx462-specific advice10° is right for a 16 mm lens on an imx462 (10.40°). It is wrong for the other shipped trains:
Since the same BOM section says you can use either the imx296 or the imx462 module, the advice contradicts the parts list two lines above it. Better framing is probably the focal length (which is what the buyer actually selects) rather than a resulting FOV — the same 16 mm lens gives different fields on the two sensors.
Worth also noting the bundled tetra3 database is built for 10–30°, which is the real constraint on "what lens might work here".
Found while implementing #609 / ADR 0027.