A stereo camera can remain connected, deliver frames and advance timestamps while one infrared channel produces no useful image. That combination does not identify the failed component: the fault may be in acquisition, stream routing, pixel interpretation, exposure or rectification. This procedure helps you locate the first stage where image content disappears, distinguish darkness from zero-valued data, and prepare useful evidence before requesting hardware support.
1. Find the first stage that becomes black
Start with the earliest accessible image from each physical sensor. Here, “raw” means the unrectified image before stereo processing, not necessarily an unprocessed sensor encoding. Record exactly which processing stages the camera software applies before delivering it.
Save the left and right unrectified images alongside their rectified outputs. Use the same scene, stable illumination and recorded exposure settings. Compare both the numerical data and their displayed appearance.
| Observation | First area to investigate | Useful next test |
|---|---|---|
| Unrectified image contains detail; rectified image is black | Rectification configuration, output mapping or display | Inspect rectified pixel values and valid-image region |
| Saved image contains detail; preview is black | Display scaling, format conversion or preview routing | Open the saved data with explicit intensity limits |
| Unrectified image is dark but responds to illumination | Exposure, gain, illumination or receiving optics | Run a controlled exposure test |
| Unrectified image remains zero-valued in a minimal capture | Acquisition configuration, decoding or hardware | Repeat with the manufacturer's diagnostic application |
| Black output follows an application stream label | Stream assignment or processing branch | Trace physical sensor identity through the pipeline |
If the image exists but stereo matching fails, use stereo disparity troubleshooting after rectification. A failed disparity calculation is a different problem from an empty input image.
2. Verify physical sensor identity and stream mapping
Do not identify the failing sensor solely by a preview window titled “right.” Applications can assign that label to the wrong queue, duplicate an input or display an unused processing output.
Create a small mapping table containing:
- Device serial number and documented physical sensor identifier.
- Requested stream name, resolution and pixel format.
- Destination queue or callback.
- Delivered dimensions, frame identifier and timestamp.
- Exposure and gain read back from that sensor, where available.
Where the receiving lenses are accessible, move a textured target through one view at a time. Confirm which saved stream changes. Do not touch internal assemblies, disconnect internal cables or obstruct an active illumination aperture.
Inspect the actual delivered stream descriptors rather than trusting the configuration request. A running pipeline may deliver a different format or output than the application expects. The checks in diagnosing missing depth streams and pixel formats help separate stream availability from interpretation errors.
Advancing timestamps establish that messages are arriving. They do not establish that the messages contain valid sensor imagery.
3. Measure the pixels before adjusting the camera
Save several frames from the failing channel without applying contrast enhancement, color mapping or lossy compression. Preserve the original pixel type and record whether the file contains native samples or converted display pixels.
For each frame, calculate the minimum, maximum, mean and fraction of zero-valued pixels. Also inspect a central region, excluding known rectification borders. Count image pixels only: row padding and unused buffer capacity are not image content.
For a hypothetical 640 × 480 image:
- Pixel count: 640 × 480 = 307,200.
- If every sample is zero, the zero fraction is 307,200 / 307,200 = 100%.
- If the maximum is 18 and the mean is 4 in an unsigned 8-bit image, the frame is dark but not empty.
That distinction changes the next test. A dark image that responds to exposure suggests a functioning imaging path. An all-zero buffer still leaves decoding, stream selection and hardware as possibilities.
Check bit depth, byte order, row stride and packed-pixel handling before interpreting the statistics. A higher-bit-depth image displayed with an unsuitable intensity range can look black despite containing valid detail.
4. Test illumination and exposure under controlled conditions
Use a stationary, matte, textured target at a distance appropriate for the camera. Remove any shipping cap from the receiving lens and inspect the external optical window for contamination or damage.
Provide illumination within the sensor's documented sensitivity range. A lamp that appears bright to you is not necessarily a suitable test source for an infrared channel. Likewise, an enabled projector does not prove that useful illumination reaches the target or returns to the sensor.
Use only documented illumination controls and operating limits. Do not increase emitter power beyond those limits, defeat protective functions or inspect an emitter through magnifying optics.
Temporarily disable automatic exposure and gain when the camera supports manual operation. Set supported values, read them back, and wait for the change to take effect before saving frames. See interpreting camera exposure and gain units before treating a raw control value as milliseconds.
For an illustrative test, changing exposure from 5 ms to 20 ms gives:
Choose settings within the device's actual timing limits; readout and processing constraints still apply. Under steady illumination, with gain fixed and pixels below saturation, a longer exposure should generally increase signal. Exact proportionality is not required to establish a response.
If settings revert during capture, resolve that behavior first using exposure resets during acquisition.
5. Separate rectification failures from capture failures
When an unrectified image contains detail but its rectified counterpart is black, stop treating the symptom as proof of a failed sensor. Inspect the transformation and output configuration.
Confirm that calibration belongs to the connected device, sensor pair, image orientation and acquisition resolution. A transformation built for different dimensions can map much of the output outside the source image. Depending on the implementation, those locations may receive a constant border value.
Check these items individually:
- Verify that the intended sensor feeds the rectification branch.
- Confirm input dimensions and orientation before applying the mapping.
- Inspect mapping validity and the expected output region.
- Calculate statistics inside that region, not just across padded borders.
- Display the rectified data without subsequent disparity filtering or masking.
Do not overwrite factory calibration merely to make the preview brighter. Preserve the original calibration and follow the manufacturer's documented procedures for any changes.
The live stereo rectification guide explains the calibration and image-processing checks in more detail. If both rectified inputs are useful but the resulting geometry is incomplete, continue with checking missing XYZ points, rather than replacing the camera immediately.
6. Reproduce the failure with the smallest supported capture
Reduce the system to one camera and the manufacturer's supported diagnostic application or minimal acquisition example. Obtain software, firmware and documentation only from the manufacturer or its distributors.
Disable optional processing branches. Capture the affected unrectified channel directly where supported. Record software and firmware versions, operating system, connection type and power arrangement.
Repeat the same scene and illumination test. If the diagnostic application displays detail but your application does not, compare stream descriptors, buffer handling and processing settings. That result points toward an application-path difference rather than establishing hardware failure.
If both applications produce black frames, the problem is reproducible outside your main pipeline. It still does not identify an internal component. Verify the documented power supply and external connection requirements, then repeat after a normal shutdown and restart.
A documented settings reset can eliminate stored configuration as a variable. Save relevant settings first, and do not keep resetting a device after an unchanged result. For applications that must initialize deterministically, use the approach in resetting camera settings before capture.
7. Check compatibility before ordering replacement hardware
A replacement must satisfy the inspection task and the software interface. Matching a housing style or the general term “stereo” is not enough.
Start with the 3D sensors category and the camera finder when evaluating a different sensing architecture. The catalog identifies MV-DLS300P-04 as a laser galvanometer stereo camera.
- Type
- Stereo / structured light
The catalog identifies MV-DPS200P-02 as a projected structured-light camera.
- Type
- Stereo / structured light
These are architecture examples, not verified replacements for your existing infrared channel. Confirm access to individual images, wavelength sensitivity, working range, synchronization, calibration support and application compatibility before selecting either.
If you are considering a separate-camera design, review area scan cameras. Separate cameras require their own optical selection, mechanical stability, synchronization and stereo calibration; they are not a drop-in repair for an integrated stereo device.
Use the camera configuration starting point only after writing down those requirements. A nominal resolution match does not establish equivalent depth performance or software compatibility.
8. Collect decisive evidence and choose the next action
Prepare a support package that lets another person reproduce the failure without guessing what “black” means. Include both a working channel and the affected channel under the same documented conditions.
Before escalating, complete this checklist:
- Identity: record the device serial number and physical sensor-to-stream mapping.
- Original data: save unrectified samples with pixel format, dimensions and row stride.
- Processing comparison: include corresponding rectified outputs and calibration identity.
- Statistics: report minimum, maximum, mean and zero fraction for the inspected region.
- Exposure response: record commanded settings, readback values and observed changes.
- Test conditions: describe target, distance, illumination and external optical condition.
- Independent reproduction: include the supported diagnostic application's result and full relevant log.
- System state: record software, firmware, power and connection details, plus any documented reset already attempted.
Share logs through the support channel after removing credentials and unrelated sensitive information. Preserve device identifiers needed for service.
A consistently zero-valued unrectified channel, reproduced in supported software under suitable illumination, is strong evidence for vendor investigation. It is not proof of a particular internal fault. Let the manufacturer determine service or replacement eligibility.
If you need help defining a replacement specification, send your capture findings and inspection requirements through technical support. Establish the failing stage first; then choose hardware around the required images, timing and measurement task.
Questions
Can an infrared channel deliver frames while its image stays black?
Frame delivery and image formation are separate checks. A device can send correctly timed buffers containing zeros, incorrectly decoded samples or the wrong processing output. Inspect saved unrectified pixel values and verify the physical sensor mapping before deciding whether the problem is exposure, software or hardware.
Does a black rectified image prove that the sensor has failed?
Not by itself. Rectification can introduce black borders or an entirely invalid output when the input mapping, calibration or dimensions are wrong. Compare the corresponding unrectified image first. Useful detail there directs the investigation toward processing rather than immediately toward sensor replacement.
What should I check before increasing infrared exposure?
Check the delivered pixel format, packing, byte order and row stride before drawing conclusions. Then measure intensity statistics under suitable illumination and several supported exposure settings. A changing signal indicates that the image path responds, while persistent zeros require further acquisition and hardware checks.
When should I request hardware support for a black stereo channel?
Contact support when the fault persists in the manufacturer's supported diagnostic application after mapping, format, illumination and settings checks. Provide original samples, statistics, logs and the working channel comparison. Do not open the housing or attempt internal repairs without an explicit manufacturer service procedure.

