A working color image does not prove that both stereo cameras can deliver usable frames. If depth acquisition fails while other functions continue, isolate the left and right monochrome paths before changing software packages. This procedure helps you distinguish a serviceable connection problem from synchronization, configuration, or processing faults, without disturbing factory calibration or opening equipment that requires authorized service.
1. Define what actually fails
Start by separating camera identification, image acquisition, and depth calculation. These are different milestones, and success at an earlier stage does not prove the next stage works.
A device may identify a sensor through a control interface while failing to receive its image data. Depending on the hardware architecture, those functions can use different electrical paths. A partially seated connection is therefore one possible explanation, not a diagnosis established by device discovery.
Record the following before changing anything:
- Which physical device and camera identifiers the application opens.
- Whether the left monochrome camera delivers changing images.
- Whether the right monochrome camera delivers changing images.
- Whether failure occurs during initialization, initial frame delivery, or sustained acquisition.
- Which operating system, firmware, SDK, and configuration versions are installed.
If your immediate problem is that the application cannot find either monochrome sensor, start with missing monochrome sensors when color acquisition still works. The procedure below concentrates on proving image delivery and isolating the physical path.
2. Capture each monochrome stream independently
Use the manufacturer's documented diagnostic utility or acquisition example. Obtain software and documentation only from the manufacturer or an authorized distributor. Confirm that your device actually exposes individual monochrome streams; some integrated sensors do not.
- Close every application that might own the camera, including background acquisition services.
- Select the left camera explicitly by its documented identifier, rather than assuming enumeration order.
- Disable depth calculation and unrelated streams where the documented interface permits it.
- Capture the left image continuously and save timestamps, frame counters, and error messages.
- Repeat with the right camera using the same supported acquisition settings.
- Finally, capture both monochrome streams together without depth calculation, if that mode is supported.
Begin with a stationary, textured target under steady illumination. Confirm that each image changes when you move the target. A preview window can continue displaying an old frame after acquisition stops, so a visible image alone is insufficient evidence.
For an initial screen, observe each mode for 30 seconds and repeat the sequence three times. These are troubleshooting intervals, not product specifications or acceptance limits.
Do not force unsupported resolutions, frame rates, or independent-camera modes. If the documented interface provides only processed depth, collect its supported diagnostics and request service guidance instead.
3. Read the isolation matrix before opening anything
The combination of independent and simultaneous acquisition narrows the next test considerably.
| Observation | What it suggests | Next discriminating test |
|---|---|---|
| One monochrome camera never appears | Identification, power, configuration, or a physical-path fault | Verify documented camera mapping and startup diagnostics |
| One camera appears but delivers no changing frames | Image-data path, sensor mode, or acquisition configuration | Run that camera alone with a documented supported configuration |
| Each camera works alone, but simultaneous acquisition fails | Shared power, transport capacity, timing, or resource contention | Reduce supported acquisition load and inspect errors |
| Both cameras stream continuously, but depth fails | Stereo configuration, calibration selection, pairing, or processing | Check synchronized inputs and the documented depth example |
| Failures occur when a moving cable changes position | An intermittent external connection is possible | Stop operation and perform a powered-down inspection |
Do not deliberately flex cables or press internal connectors while powered to reproduce a fault. A live disturbance can create damage or confuse the evidence.
If a sensor is absent even before acquisition begins, the camera-module connection diagnostic covers that earlier boundary. If both images arrive but depth startup terminates the connection, use the stereo depth startup crash procedure after completing the physical checks.
4. Inspect only connections designated for service
Stop acquisition, shut down the equipment, and remove every power source according to the manufacturer's procedure. A data connection may also supply power. On installed machinery, follow the site's isolation procedure before accessing the camera assembly.
For an accessible external connection, inspect the plug, receptacle, retention mechanism, strain relief, and cable routing. Look for a plug that is not fully engaged, a damaged latch, or a cable being pulled sideways.
For a documented, serviceable flat-flex connection, follow the specified latch procedure exactly. Connector mechanisms differ: some flip, others slide, and some are not intended for field handling. Never infer the release method from appearance alone.
Check for uneven insertion, folded conductors, damaged contacts, and cable tension near the connector. A cable can appear seated from above while entering at an angle. Do not scrape contacts, add padding, or apply adhesive unless the service procedure explicitly calls for it.
Keep the camera modules, lenses, and stereo mounting geometry untouched. Moving either camera can invalidate calibration even if image acquisition returns. Photograph accessible routing before service, but do not treat that photograph as a substitute for the manufacturer's instructions.
If the connection is inaccessible, damaged, or not designated for service, stop and use the authorized repair route.
5. Change one external variable at a time
A depth-only failure does not automatically identify an internal stereo cable. Starting additional sensors or processing can expose inadequate power, an unreliable host connection, or excessive transport load.
Use a controlled substitution sequence:
- Reconnect the approved external plugs with power removed.
- Test with a known-good, manufacturer-approved host cable of the required interface and construction.
- Remove optional adapters or hubs only where a direct connection is supported.
- Verify the approved power arrangement, including connector retention and cable condition.
- Repeat the same left-only, right-only, and simultaneous capture tests after each change.
Keep the target, acquisition settings, software installation, and host constant during these comparisons. Changing the cable and reinstalling software together prevents you from identifying which change mattered.
Use the camera cable category and accessory finder to identify candidates only after checking interface, connector orientation, pin assignment, power requirements, and motion rating. A matching connector shape does not establish electrical compatibility.
For applications requiring a GigE cable, review LS-CBL-0199 as a cable candidate. Its listing does not establish compatibility with an unidentified stereo camera or an internal ribbon connection.
6. Quantify frame delivery instead of trusting the preview
Measure the failure at the acquisition boundary. Record received-frame counts over a fixed observation window, together with sequence identifiers and device timestamps when available.
For frames with valid timestamps, estimate the delivered rate as follows:
The subtraction matters because there is one fewer interval than frames. Use timestamps from the same clock domain, and distinguish exposure timestamps from host arrival times. The frame timestamp interpretation guide explains why those measurements answer different questions.
Consider a hypothetical test configured for 30 frames per second. The left camera delivers 300 frames, with 9.97 seconds between the first and last timestamps:
Over a separate 10-second observation window, suppose the right camera delivers only 7 frames. Its observed delivery averages approximately 7 / 10 = 0.7 frames per second. That asymmetry identifies the right acquisition path for further testing, but it does not distinguish a cable fault from a sensor-mode problem.
Now repeat after each controlled change. If an approved external cable substitution leaves the same asymmetry, that cable becomes less likely. If documented connector service restores sustained right-camera delivery, the evidence supports a connection-related cause. Continue verification before declaring recovery.
Do not interpret gaps in sequence numbers as lost frames until you understand counter resets, wrapping, intentional decimation, and queue-discard behavior.
7. Know when the physical-path explanation is wrong
If both monochrome cameras deliver continuous, correctly identified images, further connector handling is unlikely to help. Move the investigation to the relationship between the streams.
Check that the depth processor receives the intended left and right inputs, supported image dimensions, and the correct calibration data. Two healthy streams do not necessarily form a valid stereo pair. Timing differences, incorrect camera assignment, or incompatible image modes can prevent useful depth.
If simultaneous acquisition fails but independent acquisition succeeds, test shared-resource limits before replacing a camera module. The multi-camera bandwidth sizing guide explains transport budgeting. Apply that reasoning only to data that actually traverses the host link; internally processed stereo images may not all be exported.
A fresh operating-system installation also warrants a compatibility check. Compare the installed software and firmware combination with the manufacturer's supported configuration. Use the firmware and SDK alignment procedure when version evidence points in that direction.
Avoid repeated reinstalls without a testable hypothesis. They can erase logs and configuration differences while leaving the original physical fault unchanged.
8. Verify recovery without disturbing calibration
Repeat the complete isolation matrix after any repair, not just the demonstration that previously failed.
- Confirm that left and right images update continuously and belong to the expected physical cameras.
- Repeat independent and simultaneous acquisition using the original supported settings.
- Check the documented timestamp or synchronization indicators for the stereo pair.
- Restore depth calculation and compare behavior against the saved failure record.
- Perform three normal cold starts to check repeatability.
- Run through the application's expected acquisition duration and operating modes.
For an initial engineering check, a 10-minute continuous run is more informative than a brief preview. It is not a substitute for application-specific qualification, especially when normal production runs are substantially longer.
If servicing required movement of a camera or lens, follow the manufacturer's recalibration procedure before trusting measurements. The stereo calibration capture guide explains the capture conditions that affect calibration quality.
Save the final configuration, service action, software versions, frame statistics, and verification outcome. That record makes a recurring failure easier to isolate without repeating every experiment.
9. Check the service route before ordering parts
Order a replacement only after identifying whether the failed item is an approved cable, a serviceable module, or the integrated sensor assembly. Internal camera ribbons are not interchangeable with ordinary external camera cables.
If replacing the sensor is justified, the 3D sensor category and camera finder provide a starting point. Compare measurement method, acquisition interface, diagnostic access, calibration handling, and service restrictions before selecting hardware.
The MV-DLS300P-04 is a laser galvanometer stereo camera. The MV-DPS200P-02 is a projected structured-light camera. These are different acquisition approaches, not verified replacements for the equipment being diagnosed. Confirm individual-stream access and integration requirements from their documentation rather than assuming either reproduces a development module's interfaces.
- Type
- Stereo / structured light
- Type
- Stereo / structured light
Before requesting a part or service recommendation, prepare this short checklist:
- Device identification and supported software versions.
- Left-only, right-only, and simultaneous acquisition outcomes.
- Original logs and frame-delivery measurements.
- Approved external cable and power substitutions already attempted.
- Any documented connector service performed.
- Whether camera geometry or calibration was disturbed.
Use application support with that evidence to confirm the service route, or start the cable and accessory configuration step once the required connection is identified.
Questions
Why can color video work while stereo depth fails?
Color acquisition may use a different sensor and data path from the monochrome pair used for stereo depth. A working color image therefore proves only part of the system is operating. Test each documented monochrome stream independently before deciding whether the fault concerns a connection, configuration, or depth processing.
Does detecting both monochrome sensors rule out a connection fault?
No. Sensor identification and image transfer can depend on different interfaces or conductors. Identification establishes that some communication is possible, but not that image acquisition is healthy. Confirm changing frames, timestamps, and sustained delivery before ruling out the image-data path.
Should I reseat an internal camera ribbon myself?
Only perform that operation when the manufacturer explicitly documents the connector as user-serviceable. Remove every power source, follow the specified latch procedure, and avoid moving the camera modules. An inaccessible connection, damaged latch, or undocumented disassembly should go through authorized service instead.
What if each monochrome camera works alone but not together?
Investigate what changes when both paths operate together: shared power demand, transport load, synchronization, and processing resources. Preserve the same supported settings while testing each possibility. Successful independent capture makes a completely disconnected sensor less likely, but does not prove simultaneous acquisition is correctly configured.
Is recalibration necessary after repairing a stereo connection?
A simple cable reconnection does not automatically require recalibration if the optical geometry remains unchanged. Moving a camera module, lens, or stereo mount can invalidate the existing calibration. Follow the manufacturer's service and calibration requirements, then verify measurement performance before returning the system to use.