Embedded Vision Lenses

Which lens mount fits a board camera?

M12 offers the smallest form factor, threads into a holder soldered or clipped to the camera PCB with no adapter plate, and covers the IMX477, IMX219, and IMX708 sensors used in most Jetson and Raspberry Pi camera modules. Embedded systems do not have the design margin a factory-floor inspection station has: a 150g C-mount lens on a fixed stand is a non-issue, but the same lens on a drone eats into flight time, and on a robotic arm it adds inertia the servo has to overcome. Weight, power draw, and unit cost compound across every embedded design decision.

C-mount and M12 are different optical systems, not two sizes of the same thing. C-mount uses an internal cam: rotating the focus ring moves lens groups relative to each other, which rebalances aberrations across the focus range and allows an adjustable iris. M12 is a rigid assembly with no internal moving groups; focus is set by threading the entire lens in or out of the holder. The tradeoff is cam compensation and iris control versus size, weight, and cost. M8 exists for extreme miniaturization such as endoscopes and micro-inspection probes, typically covering sensors up to 1/3 inch. See the M12 vs C-mount vs CS-mount guide and what is an M12 lens for the mechanical basics.

Match the lens to your sensor before anything else

A lens-sensor mismatch shows up as vignetting, color shading, or wasted resolution. Four parameters need to line up: image circle versus sensor diagonal, CRA versus sensor microlens design, lens MTF versus sensor Nyquist frequency, and back focal length versus your sensor stack.

The lens projects a circular image; your rectangular sensor sits inside that circle. An image circle smaller than the sensor diagonal vignettes the corners. A lens rated for 1/2.5 inch sensors covers any sensor that size or smaller; it will vignette on a 1/1.7 inch sensor. Format labels are not always published with matching precision between vendors, so verify against your sensor's actual diagonal. The coverage math is in sensor size and lens compatibility.

Chief ray angle deserves the same scrutiny on small-pixel sensors. Sensors with 1.4µm-2.5µm pixels use microlenses tuned to a specific CRA curve, typically 20 to 30 degrees at the corners. A lens CRA that does not track the sensor's design CRA produces color shading and corner falloff that software cannot fully correct, because the mismatch is wavelength- and angle-dependent at the pixel level. The failure is easy to miss during bring-up because center-field quality looks fine; verify against both datasheets before committing, per the chief ray angle and mismatch guide.

For focal length, work the math directly: EFL = (WD × sensor_width) / FOV_width. At 0.5m-2m working distance, 4mm-8mm covers general-purpose vision, 2mm-4mm suits obstacle avoidance and surround view, and 8mm-16mm suits inspection and barcode reading. Run your numbers through the EFL calculator or the field of view calculator.

Board-level integration on Jetson and Raspberry Pi

Jetson Nano, Xavier NX, and Orin modules, along with Raspberry Pi and most other MIPI-CSI2 board cameras, connect through M12 holders on the camera PCB. Because M12 has no standardized flange distance, focus is set entirely by how far the lens threads into the holder, and back focal length varies by lens design. That variability is a feature for board-level integration: when you swap camera modules, or one lens design needs to work across two sensor stacks with different cover glass or IR filter thickness, the fix is a holder of the correct height rather than a different lens.

Confirm holder height against the lens's specified back focal length and your full sensor stack, bare sensor plus cover glass plus IR filter plus any spacer, before finalizing the PCB footprint. Multi-camera designs raise the bar further: a stereo pair needs matched focal length and matched back focal length across every module, since a small BFL difference between two nominally identical units shows up as a focus mismatch between the left and right images. Verify focus at the corners of the field on each unit during bring-up, not only at the center. Holder height selection and thread engagement are covered in the M12 lens holder selection guide.

The power, size, and cost tradeoff

M12 lenses sit at the small-footprint, low-cost corner of the design space. A fixed-aperture lens draws no power and costs a fraction of an industrial optic, but gives up the adjustable iris and cam-based aberration compensation C-mount provides. C-mount's iris is only practical in machine vision because illumination is usually programmatically controlled, which lets the system stop down for depth of field without starving the sensor of light. Embedded systems that rely on ambient lighting cannot always make that trade, which pushes the decision back toward a fixed-aperture M12 lens with a fast F-number: an F/1.4 lens admits roughly four times the light of an F/2.8 lens. Most embedded designs default to M12 and accept the loss of iris control, reserving C-mount for the subset of applications where the extra size and cost buy something the application actually needs. Application-specific picks for robotics, drones, and surveillance live in the collections linked below.