RGBD examples not working with OAK-D lite camera

flash

I tried to run these two examples from the docs:

I've installed depthai v3 (following these instructions https://docs.luxonis.com/software-v3/depthai/ ) and have an OAK-D lite camera connected via USB.

Running the code examples in python gives the following error:

[194430108128D32600] [1.1] [16.440] [Camera(2)] [error] Invalid configuration or input image - skipping frame

[194430108128D32600] [1.1] [16.472] [Camera(2)] [error] Not possible to create warp params. Error: WARP_SWCH_ERR_CACHE_TO_SMALL

Could you please help me to fix this?

OskarSonc

Hey flash ,

I tested the examples on a similar RVC2 device and they’re working fine.
Which version of depthai are you using? Could you try updating to the latest version and see if the issue persists?

Best,

Oskar

flash

I'm using:

depthai 3.0.0rce installed in a conda environment

Ubuntu 22.04

Camera is OAK-D Lite fixed focus

Local host shows device not detected even though it is plugged in:

OskarSonc

@flash,

Did you follow our USB deployment guide? On Linux there are a few extra setup steps (like installing udev rules) to get the camera detected properly:
https://docs.luxonis.com/hardware/platform/deploy/usb-deployment-guide/

Once you've gone through that, I recommend testing the camera with the OAK Viewer to confirm everything is working:
https://docs.luxonis.com/software-v3/depthai/tools/oak-viewer/

Thanks
Oskar

flash

Thanks, after installing the udev rules, uninstalling depthai-viewer, and installing the OAK-viewer .deb the original error is still there. Restarting the computer did not help either.

The camera is still not working for both RGBD examples.

Other examples, like capturing a still image (https://docs.luxonis.com/software-v3/depthai/examples/camera/camera_still_max_res/) work fine.

OAK-viewer works as shown below:

flash

I have two OAK-D Lite cameras. Why does the example work on one camera and not the other? Both cameras are new, kept in the box and not used much apart from running some examples a few months back.

Do I need to run some kind of firmware update on the faulty camera?

The error message seems to suggest memory issues on camera 2 (not sure what that means in Luxonis context).

Also, is there a way to check the sensors on both cameras, like if both have an internal IMU?

OskarSonc

Hey @flash,

Sorry for the wait, had to check with the team …
It’s likely the issue is with the calibration on the camera that’s failing.
Could you run this script on both cameras (one at a time) and send us the generated files?

import depthai as dai
from pathlib import Path
import json

def to_obj(x):
    """DepthAI may return a dict or a JSON string depending on version."""
    return x if isinstance(x, dict) else json.loads(x)

with dai.Device() as dev:
    devid = dev.getDeviceId()

    # Effective (user) calib = factory + any user overrides
    eff = to_obj(dev.readCalibration2().eepromToJson())
    # Factory-only calib (read-only from manufacturing)
    fac = to_obj(dev.readFactoryCalibration().eepromToJson())

    bundle = {
        "meta": {
            "deviceId": devid,
            "depthai_version": getattr(dai, "__version__", "unknown"),
        },
        "USER CALIBRATION": eff,
        "FACTORY CALIBRATION":   fac,
    }

    out = Path(f"{devid}_calibration.json")
    out.write_text(json.dumps(bundle, indent=2))
    print(f"Wrote {out.resolve()} "
          f"(effective size: {len(json.dumps(eff))} bytes, "
          f"factory size: {len(json.dumps(fac))} bytes)")

Thanks,
Oskar

flash

The output from the first camera (the one where the examples don't work, yielding the errors above) was generated. However, this forum does not allow uploading of .json files. You can download it from here.

The code failed to run on the second camera (the one where the RGBD examples worked). The error is:

File "/home/main.py", line 15, in <module>

fac = to_obj(dev.readFactoryCalibration().eepromToJson())

^^^^^^^^^^^^^^^^^^^^^^^^^^^^

depthai.EepromError: No or invalid EEPROM configuration flashed, error: EEPROM_INVALID_DATA

OskarSonc

Hey @flash,

Thanks for sending the calibration dump from the camera that’s failing.

Could you please run the updated calibration bundle script below on your working OAK-D Lite as well?

import depthai as dai, json
from pathlib import Path

def to_obj(x):  # dict vs str across versions
    return x if isinstance(x, dict) else json.loads(x)

with dai.Device() as dev:
    devid = dev.getDeviceId()
    eff = to_obj(dev.readCalibration2().eepromToJson())

    fac = None
    try:
        fac = to_obj(dev.readFactoryCalibration().eepromToJson())
    except dai.EepromError:
        fac = None  # factory partition not present/invalid is OK on some units

    bundle = {
        "meta": {"deviceId": devid, "depthai_version": getattr(dai, "__version__", "unknown")},
        "USER CALIBRATION": eff,
        "FACTORY CALIBRATION": fac,
    }
    out = Path(f"{devid}_calibration_bundle.json")
    out.write_text(json.dumps(bundle, indent=2))
    print(f"Wrote {out}  "
          f"(user bytes={len(json.dumps(eff))}, "
          f"factory bytes={len(json.dumps(fac)) if fac is not None else 0})")

Once we have the dump from the working camera too, we can compare the two and confirm the next steps.

Thanks!
Oskar

flash

Do some OAK-D Lite cameras not store calibration data in EEPROM? Where is it otherwise stored?

You can download the generated file for camera 2 here.

OskarSonc

Hey @flash,

Thanks for sending both dumps — they’re quite different, which points to a calibration issue on the camera that fails. This can cause the WARP_SWCH_ERR_CACHE_TO_SMALL errors in the RGB-D examples.

Also, to answer your earlier question: yes, some OAK-D Lite units don’t have a separate factory calibration partition in EEPROM. In those cases, the device only has a user/effective calibration area in EEPROM, which is what DepthAI uses at runtime.

You can try flashing the working camera’s calibration onto the failing one by following our guide here:
👉 https://docs.luxonis.com/software/depthai/examples/calibration_load/

Note: calibration flashing is currently only available with DepthAI v2, but once it’s done you can switch back and use the camera normally with DepthAI v3.

Let us know how it goes after the flash!
Thanks

flash

Looking at the calibration files and also running the IMU example I concluded that:

1. camera 1 (RGBD examples not working) has a built-in IMU

2. camera 2 (RGBD examples working) does not have an IMU since the IMU example code outputs:

RuntimeError: IMU(0) - IMU invalid settings!: IMU not detected. Your board doesn't have IMU or requires firmware update (Set imu.enableFirmwareUpdate(True) explicitly.). 0, 395

Is there a definitive test I should run to confirm the missing IMU for camera 1 (I didn’t buy the camera off Kickstarter)?

Could the IMU be a factor for the original error?

I'm concerned about flashing camera 2’s calibration parameters onto camera 1 since this will effectively erase the IMU calibration parameters on camera 1. I would like to be able to access and use the IMU data for future projects.

How should I proceed?

OskarSonc

Hey @flash,

Here’s a quick code snippet to check if your device has an IMU:

import depthai as dai
with dai.Device() as dev:
    t = dev.getConnectedIMU()
    print("IMU type:", t)  # None/IMUType.NONE => no IMU present

I don’t think the IMU is related to the RGB-D error.

From the calibration dump, the failing camera’s RGB <-> stereo extrinsics look invalid, which explains the warp error. To confirm safely (without touching IMU calibration), please try the temporary load approach from our v2 example:
https://docs.luxonis.com/software/depthai/examples/calibration_load/