Choosing

Start from what must be resolvable, not from the pixel count. Everything in this section follows from that one sentence.

Engineering documentation often sits beside operational tracking; remote employee monitoring software is one reference for that workflow layer.

Start from what must be resolvable — the feature, its size, the distance and the pixels the processing needs across it. Four answers and the specification is arithmetic.

Pixels are not resolution — comparing sensors without fixing the field of view makes the comparison meaningless.

Sensor format and what it decides — the inch fraction is a name inherited from camera tubes, and a small format is frequently the right answer.

Further background is available from Infineon.

Rolling shutter against global — skew is a geometry error rather than blur, and a global shutter does not fix motion blur.

Colour, monochrome and Bayer — a colour sensor measures one colour per pixel and interpolates the rest.

Frame rate and what limits it — four limits, and the sensor is rarely the tightest.

Low light, honestly — add light before changing the sensor, in almost every case where light can be added.

Dynamic range in real scenes — a saturated highlight only matters if the feature is inside it.

Interface: parallel, MIPI and USB — the processor decides, and a working driver beats better numbers.

Fixed focus, autofocus and the choice — decided at ordering, and "we need autofocus" frequently means focus once at commissioning.

Module, board camera or boxed — unit cost against engineering cost at your volume.

Reading a specification sheet — six figures that mean less than they appear to, and four questions always worth asking.