Depth camera RGB sensor not detected after an ISP update failure

A stereo depth camera that suddenly reports itself as a stripped-down variant of its own model, throws an "ISP update failed" message and refuses to open its colour stream is one of the few faults that looks like software but usually ends in hardware. The good news: the diagnosis is quick. This guide walks the symptom, the causes in order of likelihood, the bench tests that separate them, and the decision between vendor repair and replacement, so you waste neither bench time nor warranty rights on a unit that needs to travel back to the maker.

What the symptom means

A depth camera's model identity is not read from the label; it is reported by firmware at enumeration, after the processor has probed every imager it expects. An ISP update failure means the firmware could not complete the start-up handshake with the image signal processor that serves the RGB sensor. The firmware then falls back to identifying the unit as the stereo-only variant — the same depth pair, no colour imager.

That fallback tells you three things at once: power and USB enumeration work, the depth processors work, and the colour path is dead. Check whether the depth and infrared streams still produce frames. If they do, the fault is confined to the RGB sensor chain: firmware, the ISP, or — rarely — the internal flexible cable between the sensor and the main board. If nothing streams at all, you have a different, broader enumeration problem; start instead with the steps in depth camera firmware mismatch after a shared camera swap.

Likely causes, in order of probability

1. Corrupted or interrupted firmware state. An update that was interrupted by a cable pull, a host sleep or a USB controller reset can leave the ISP configuration half-written. The camera boots, fails the update, and reports the RGB-less variant on every start.
2. Firmware and SDK mismatch. A viewer or SDK that expects a different firmware generation can report a failed update even when the stored firmware is intact. This is the cheapest cause to exclude.
3. Insufficient or noisy USB power. A long or unpowered cable run can drop the colour imager below its start-up threshold while the depth pair, on a different power rail, survives. A powered hub or a shorter, shielded camera data cable excludes this in minutes.
4. Loose internal sensor connection. Documented by vendors as rare: the flexible cable between the RGB sensor and the circuit board works loose, usually after shock or vibration in transit or on a moving fixture.
5. Failed ISP or sensor board. The end of the line. Nothing on your bench fixes it, and opening the housing typically voids the warranty.

Bench tests, cheapest first

Work through these in order; each one either fixes the fault or removes a cause from the list.

1. Swap the cable and the port. Use a different, shorter cable and a port on a different USB controller, not a neighbouring port on the same hub. Add a powered hub for one test.
2. Test on a second host. A different computer, ideally a different operating system, with the vendor's viewer installed fresh. Exclude the host's USB permissions too — on Android hosts, missing USB host permissions produce detection faults of their own, covered in depth camera not detected on Android: check USB host permissions.
3. Re-flash the latest firmware once. Take the file only from the manufacturer's official download channel, follow the release notes exactly, and let it finish without touching the cable. An interrupted flash is a common way this fault starts.
4. Try one rollback. If the fault appeared right after an update, install the previous vendor release once. If the same error appears on two firmware versions, the software causes are excluded — stop here.
5. Record the matrix. Note every host, port, cable, OS and firmware version tried, with the exact error text. This list is what a repair case is built from.

When to stop and send it back

If the camera enumerates as the RGB-less variant on two firmware versions across two hosts and two cables, the fault is inside the unit. At that point the legitimate path is the manufacturer's repair or replacement channel through the seller you bought it from: request a return-material authorization, provide the serial number, the firmware versions tried and your test matrix, and follow their shipping instructions. Cross-border returns may need customs paperwork such as an importer registration number — the vendor's support team will tell you which.

For units already out of warranty, ask the vendor whether a documented board-replacement procedure exists for your model before any internal work — and weigh it against the cost of a replacement.

Planning the replacement cycle

A camera away for repair does not have to stop an inspection line. Two spares strategies work:

• A like-for-like spare of the same model, kept on the same firmware and SDK baseline as the fleet so a swap needs no software change. If the fleet has drifted across firmware versions, read camera firmware version mismatch: fix detection failures safely before mixing units.
• A split set-up that keeps the surviving depth stream and replaces colour with a separate RGB camera. A ToF sensing camera or a projected structured-light unit such as the MV-DPS200P-02 covers the depth side, while any C-mount area scan camera from the area scan camera range covers colour. You will need to re-do extrinsics between the two — the trade-offs are the same as in camera pose initial guess: which reference frame it means.

When the repair or replacement unit arrives, run the full acceptance check below before it goes on the line.

Choosing hardware so this fault costs less next time

Depth and colour fusion on a single unit is convenient until the colour imager fails and takes the whole camera off the line. If your process only needs depth plus a coarse texture, a stereo structured-light camera without an integrated RGB imager has one fewer single point of failure. The 3D sensor category splits into laser profilers, stereo and structured-light units, logistics volume cameras and ToF cameras — pick the simplest sensing type that meets the requirement.

Values as printed in each product's data sheet; open a part for its drawing and full specifications.

If your colour needs are demanding — high resolution, specific colour accuracy — a separate RGB camera with its own lens often outperforms the small integrated imager anyway, and it fails independently. For the underlying trade-off between fused and separate sensors, point cloud with RGB and IR intensity: fuse depth, color and infrared explains the fusion side. The camera configurator walks the resolution and interface choices for the colour side.

Checks before the unit goes back on the line

• Correct model variant reported by the viewer, RGB stream present.
• Firmware version matches the fleet baseline and the SDK release notes.
• Depth, infrared and colour frames time-stamped within one exposure period.
• Cable strain-relieved, no drag across a moving axis; replace any cable that was in circuit during the fault.
• Full inspection-cycle test on real parts, not just a viewer preview.
• Serial number, firmware version and calibration date recorded against the station.

When the usual answer is wrong

The usual answer to a failed update is "flash again". Here that instinct costs time. Re-flashing is worth exactly one attempt after the original failure; if the ISP update fails again, further flashing is unlikely to help and the correct next step is the repair channel. Likewise, a rollback is a diagnostic, not a fix: running a fleet forever on old firmware to avoid the error leaves you without bug fixes and can collide with SDK versions, the failure mode behind 3D camera header version mismatch: fix firmware and SDK alignment.

Finally, if the RGB stream disappears gradually — intermittent colour, then gone — suspect the cable and connector path before the ISP. Intermittent faults follow mechanical movement; a hard ISP failure is consistent from the first power-up after the bad update.

If you are weighing repair against replacement for a specific station, contact us with the camera model, firmware version and your test results, and we will help you pick the shortest path back to production.