Comparison 02 · Audit sample

Robot stereo and depth camera evidence table

Range, resolution, transport and timing claims without collapsing unlike camera architectures.

4 component records6 comparison fieldsUpdated 2026-08-10
Scope

USB active-stereo cameras, a rugged GMSL2 stereo camera and an industrial GigE time-of-flight camera.

Do not flatten

Maximum range, ideal range, optimal range and accuracy-tested range are not interchangeable.

FieldRealSense
D455
Orbbec
Gemini 335
Stereolabs
ZED X
Basler
blaze-101
Published rangeRange wording and conditions are preserved.0.6–6 mMManufacturer-described ideal range; not a hard detection limit.Source ↗0.10–20+ mMOptimal range 0.26–3 m; manufacturer also states a theoretical maximum up to 65 m.Source ↗UnknownNo adequate published value in the selected source set.Short 0.3–1.5; long 0.3–10 mMSeparate short- and long-range modes.Source ↗
Resolution / frame rateMode combinations matter.1280 × 720 up to 30 fps; 848 × 480 up to 90 fpsMMaximum frame rate depends on resolution.Source ↗1280 × 800 @ 30 fpsMMaximum published depth mode.Source ↗1920 × 1200 @ 60 fps; 960 × 600 @ 120 fpsMThe two maxima are separate operating modes.Source ↗640 × 480 at 20 fps default / 30 fps FastModeMFastMode changes the operating mode; it is not the default.Source ↗
Field of view / lensLens option and axis definitions matter.87 × 58 °MHorizontal × vertical.Source ↗90 × 65 °MHorizontal × vertical.Source ↗2 mm wide-FOV or 4 mm long-range lensMField of view depends on ordered lens option.Source ↗67 × 51 °MHorizontal × vertical.Source ↗
Data interfaceGMSL2 and USB require different host hardware.USB-C 3.1 Gen 1MNo extra condition in selected source.Source ↗USB 3.0 Type-CMNo extra condition in selected source.Source ↗GMSL2MRequires a compatible deserializer or capture platform.Source ↗Gigabit Ethernet / GigE VisionM1000 Mbit/s communication interface.Source ↗
Accuracy / precisionOnly comparable with the same distance, target and metric.<2% at 4 mMManufacturer condition shown on the product page; see datasheet footnote for full method.Source ↗≤1.5% RMSEM1280 × 800 at 2 m over a 90% × 90% region of interest.Source ↗UnknownNo adequate published value in the selected source set.±5 mmM0.5–5.5 m; 20-minute warm-up; flat white 90% target; no ambient light; 22°C; central 40 × 40 pixels; 25-image average.Source ↗
Timing / syncFeature support is not proof of achieved multi-sensor timing.Bosch BMI055 IMU; multi-camera use describedMProduct page does not turn this into a universal host-level synchronization guarantee.Source ↗Depth/color sync, multi-device sync and hardware trigger supportedMHost, cable and SDK configuration still determine achieved timing.Source ↗External frame syncMIntegration details depend on host hardware and cable topology.Source ↗PTP IEEE 1588, hardware trigger, software trigger, free runMMulti-camera operation is supported, but achieved timing depends on network and configuration.Source ↗

Values are transcribed from the linked sources and were checked on the date shown by each record. V = independently verified; M = manufacturer claimed; D = RCI derived; C = conflicting; U = unknown.

Interpretation rule

The condition belongs to the number.

RCI does not compute winners from this audit sample. The table’s purpose is to show what can be compared now, what requires a shared test, and which public fields are still missing.

Read the full method →