Cameras & sensorsGuide

Small form factor USB camera modules for embedded Linux

Board-level USB camera modules bring small-form-factor imaging to embedded Linux: sizes, UVC versus USB3 Vision drivers and a worked lens example.

LumaSpec Vision9 min read Share on LinkedIn

On this page 8 sections
  1. 01What industry sells in the phone-module role
  2. 02UVC or USB3 Vision: the decision that fixes your driver work
  3. 03Worked example: a 60 mm field of view at 120 mm working distance
  4. 04The lens side: image circle, focus travel and smaller mounts
  5. 05Mechanical fit: measure these before you order
  6. 06Support and supply lifetime: the qualification list
  7. 07When the small module is the wrong tool
  8. 08Questions

You want a camera module the size of a phone camera, a vendor that answers questions, and a clean data path into an embedded Linux board. Industry sells exactly that class of part, just not at phone dimensions. This guide gives you the envelopes to design around, the interface decision that fixes your driver work, a worked lens calculation, and the checks that keep the part purchasable for the life of your machine.

What industry sells in the phone-module role

The industrial counterpart is the board-level camera: sensor, timing and interface on a small PCB, no housing, and optics from bare flex to a threaded barrel. The decision up front: if your design tolerates a 27-30 mm board and a 14-16 mm optical head, a supported standard product exists. Between 25 mm and 9 x 9 mm you move to miniature bare boards and small-mount lenses. Below 9 x 9 mm of front area, no supported standard product exists today; that is custom flex, phone-class optics, or a custom build with the support question left open.

Sizes to design around, from current board-camera lines: bare USB3 boards commonly measure 27 x 27 mm to 30 x 30 mm and weigh about 5 g; versions with a lens socket land near 29 x 29 mm at roughly 15 g; larger series stretch to 36 x 36 mm. The lens often sets the smallest dimension, not the board: an M12 barrel is 12 mm across, and with its lock nut the optical head needs about 14-16 mm of front footprint.

The bare-board style is the closest match to the phone-module idea. The MV-CB060-10UM-B is a 6 MP USB3 bare board with a 1/1.8" IMX178 rolling-shutter sensor and no lens mount, so your flex and optics decide the head size.

Board-level camerasHikrobot MV-CB060-10UM-B 6 MP Board Level Camera, USB3, IMX178, Mono, Bare Board, V4MV-CB060-10UM-B
Sensor format
1/1.8"
Interface
USB3
Resolution
6-10 MP
Shutter
Rolling
$239.00View partBuild a system with it

For the full selection grid behind this class, see the guide to board level camera selection, or filter the cameras finder by USB3 and sensor format.

UVC or USB3 Vision: the decision that fixes your driver work

Both interfaces ride the same cable class; the difference is what your Linux image carries.

A UVC-compliant module enumerates with the kernel's built-in USB video class driver: it appears as a standard V4L2 device, no vendor SDK, no kernel rebuild. You get exposure, gain and format control through the class. Deep sensor features and hardware trigger may not surface, which is the price of the generic driver.

A USB3 Vision module carries the standard's GenICam feature set and needs a GenICam transport layer: the vendor SDK, or an open-source GenICam library that speaks USB3 Vision. You gain full feature access and a machine-vision-style API, at the cost of shipping and maintaining that stack in your image. For everything else that has to match, the interface compatibility checklist covers the verification order.

Bandwidth planning: USB 3.0's 5 Gbit/s line rate leaves roughly 350-400 MB/s of usable image payload after 8b/10b coding and protocol overhead. Budget one SuperSpeed host port per camera.

If the acquisition host is a compact industrial PC rather than a single-board computer, the same footprint-versus-cooling trade-off applies on the host side; the guide to selecting small form factor PCs for CNC motion control walks that decision.

Worked example: a 60 mm field of view at 120 mm working distance

Inputs for a compact station around a 1/1.8" board camera:

  • Sensor width 7.2 mm, the standard 1/1.8" active-area width.
  • Required field of view 60 mm wide: the part plus its locate margin.
  • Working distance 120 mm, what the mechanical envelope allows.

The rule in words: magnification is sensor width divided by field of view, and focal length follows from magnification and working distance.

m = sensor width / field of view f = WD × m / (1 + m)

Arithmetic:

  • m = 7.2 / 60 = 0.12
  • f = 120 mm × 0.12 / (1 + 0.12) = 14.4 / 1.12 = 12.9 mm

No 12.9 mm stock lens exists, so take the 12 mm value and check what it delivers at the same distance:

  • m = 12 / (120 - 12) = 0.111
  • FOV = 7.2 mm / 0.111 = 64.9 mm, call it 65 mm — about 8% over spec, which crops away.

To hit 60 mm exactly, pull the camera in:

  • WD = f × (1 + m) / m = 12 × 1.12 / 0.12 = 112 mm

Decision: a 12 mm M12 lens focused near 112-120 mm meets this spec with margin, provided the barrel's focus travel reaches the 112 mm object distance. Confirm that travel against the mechanical drawing before you lock the design.

How sensor width, working distance and field of view set the focal length Rays from the edges of the sensor pass through the lens and spread to the edges of the field of view. The ratio of sensor width to field of view is the magnification m.CameraField of view (FOV)Working distance (WD)≈ fsensor width slensm = s / FOVf = WD × m / (1 + m)
How sensor width, working distance and field of view set the focal length. Rays from the edges of the sensor pass through the lens and spread to the edges of the field of view. The ratio of sensor width to field of view is the magnification m.
Lens focal length, field of view and working distance
Units
Solve for
Focal length
– mm
Field of view
– mm
Working distance
– mm
Magnification
– x
Angle of view
– °
Pixel on the part
– mm

Thin-lens model: m = sensor width / field of view, f = WD × m / (1 + m). Accurate to a few percent above about 150 mm; check the lens's minimum object distance.

Find lenses with this focal length Open the full calculator

The lens side: image circle, focus travel and smaller mounts

Two optics facts decide whether the head fits your enclosure.

Image circle: the lens must cover the sensor diagonal, about 9 mm on a 1/1.8" format. That is the 8-11 mm image-circle class in the M12 lines; a smaller circle vignettes the corners. The M12 lens selection guide walks format matching and IR-cut choices, and the lenses finder filters by mount, circle and focal length.

Focus travel: an M12 barrel focuses by moving along its thread, typically M12 x 0.5, and the travel on offer limits the closest working distance you can reach. The physics sits in the thread pitch and focus shift guide, and the thread travel guide shows why short threads lock out close focus.

For the example's optics, the LS-MBL-0012 is a 12 mm, 5 MP M12 lens with an 8-11 mm image circle on 1/1.8" format — the exact class the calculation lands on.

M12 board lenses5 MP S-mount low distortion board lens, 12 mm, 1/1.8" (LS-MBL-0012)LS-MBL-0012
Sensor format
1/1.8"
Mount
M12
Resolution
5 MP
Image circle
8-11 mm
$89.00View partBuild a system with it

Wider, shorter heads use short focal lengths on smaller formats. The LS-MBL-0018 is a 2.8 mm, F2.8, 8 MP M12 lens on a 1/2.5" format.

M12 board lenses2.8 mm M12 board lens, 8 MP, F2.8 (LS-MBL-0018)LS-MBL-0018
Sensor format
1/2.5"
Mount
M12
Resolution
6-10 MP
Image circle
Up to 8 mm
$50.00View partBuild a system with it

For heads tighter than a 12 mm barrel, the lens lines also list M6, M8, M9x0.5 and M10 mounts; they trade image circle and optical correction for diameter.

Mechanical fit: measure these before you order

Run this list against your mechanical drawing:

  • Board outline and mounting-hole pattern against your shelf or carrier.
  • Connector stack height and cable bend radius at the flex exit.
  • Barrel height above the board: back focal length plus focus travel.
  • Filter space: an IR-cut window needs its own seat if the lens is not IR-corrected.
  • Clearance around the barrel nut for a focus tool and for thread lock.

If the part moves and you need a global shutter, step up to a housed C-mount module and accept the bulk. The LS-BCM-0003 is a 3.1 MP USB3 board camera with a global-shutter IMX252 sensor on 1/1.8" format, 120 fps at full resolution and a C-mount.

Board-level cameras3.1 MP USB3 board-level camera, IMX252, 1/1.8" global shutter, 120 fps (LS-BCM-0003)LS-BCM-0003
Sensor format
1/1.8"
Lens mount
C-mount
Interface
USB3
Resolution
5 MP
$690.00View partBuild a system with it

For the mounting and adjustment procedure, the M12 lens focusing guide runs the adjust-check-lock sequence.

Support and supply lifetime: the qualification list

The question that separates an industrial module from a hobby board is the roadmap. Ask the vendor in writing for current production status, the end-of-life notice period, and the sensor's own availability beyond your project. Then design the module as a replaceable unit: bracket it, document its format, and keep a second source in the plan. The board camera replacement guide covers the swap mechanics, and the board camera evaluation checklist turns qualification into a pass/fail sheet.

Qualify on your hardware, not on a data sheet:

  1. Probe the module on your exact kernel build and record the driver version it binds.
  2. Capture at every advertised format and frame rate, and note which combination holds under sustained load.
  3. Check the trigger and general-purpose lines on the actual connector, not the block diagram; the USB camera external trigger guide lists what to verify.
  4. Run a thermal soak and re-check focus; the temperature focus drift guide explains why focus moves.
  5. Buy from at least two production lots and repeat the focus check, because M12 barrels vary unit to unit.

Parts we ship carry a 3-year warranty minimum, and in-stock items ship within one business day.

When the small module is the wrong tool

Commit to the small board module when four things hold: your envelope tolerates a 27-30 mm board, one camera fits inside the 350-400 MB/s budget, UVC or the GenICam stack suits your image build, and the vendor commits to availability in writing.

Step up when any one fails. Passive USB3 cable is practical to about 3 m; beyond that, GigE board modules keep the small format and run 100 m on standard Ethernet cable. For severe vibration, heat or timing precision, housed area scan cameras earn their bulk. And for pixel-level accuracy across a large field, a bigger sensor beats a smaller board every time: the extra millimetres buy real resolution.

Next step: set sensor format, mount and interface in the camera configurator, or browse the cameras topic page for the neighbouring guides on boards, lenses and driver bring-up.

Questions

Will a UVC board camera work with OpenCV on embedded Linux?

Yes. The kernel's USB video class driver exposes the module as a V4L2 device, and OpenCV opens it like any other capture source: set the four-character pixel format, resolution and frame rate, then read frames. What UVC will not expose is deep sensor control or hardware trigger, so if the algorithm needs those, shortlist USB3 Vision modules instead.

How small does an industrial USB camera module actually get?

Bare USB3 boards commonly run 27-30 mm square at around 5 g, and versions with an M12 socket land near 29-30 mm, the lock nut giving a front footprint of roughly 14-16 mm. For tighter heads, M6, M8, M9x0.5 and M10 lenses exist. Smaller than that means custom flex and phone-class optics, where vendor support and a roadmap largely disappear.

What USB3 bandwidth should I reserve for one module?

Plan around 350-400 MB/s of usable payload from a USB 3.0 port and give each camera its own host controller port. As a worked check: a 3 MP module at 120 fps in 8-bit mono moves 3 x 120 x 1 byte = 360 MB/s, which nearly fills a port. GigE trades bandwidth for 100 m of cable.

Do these small modules support hardware trigger?

Some do and some do not; the connector decides it. The trigger and general-purpose lines have to be broken out on the board-to-board or flex connector, and generic UVC parts often leave them unused. Read the module's connector pinout before you design the mating cable, and treat an absent trigger line as a disqualifier for stop-motion inspection.

How do I confirm the module will stay purchasable?

Get three commitments in writing: current production status, the notice period the vendor gives before end-of-life, and the image sensor's own availability beyond your project. Qualify the module on your kernel build, then design it as a replaceable bracketed unit with a documented second source, so a future swap touches the bracket, not the whole machine.