-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues running the SDK examples with OAK-D-SR #39
Comments
Hey, Thanks for letting us know about the issue. Next release will have a fix where the middle RGB camera (CAM_A) is optional, and I will let you know when the next release is available. |
Hey, SDK version 1.34.0 is now available if you wish to try it out. Feel free to let me know if you run into further issues with OAK-D-SR. |
Works now. Here is the correct IMU-to-camera matrix for the OAK-D-SR (simply using the default value results in a ton of drift):
|
Thanks, your imu->camera matrix will be set by default for OAK-D-SR in next release (1.35.0). |
I'm trying to run the
vio_visu.py
example with the OAK-D-SR and running into some problems.Here's the error message:
SpectacularAI ERROR: invalid or unsupported color input resolution 800p
My workaround was to set it manually back to 800p after constructing the VIO pipeline with 1200p but before starting the DepthAI pipeline:
dai::CalibrationHandler::getCameraExtrinsics
anddai::CalibrationHandler::getDistortionCoefficients
onCAM_A
, which isn't present on the SR (this device only hasCAM_B
andCAM_C
).The error message:
There is no Camera data available corresponding to the the requested source cameraId
My hacky GDB workaround to force it to never call those functions with
CAM_A
:The text was updated successfully, but these errors were encountered: