-
Notifications
You must be signed in to change notification settings - Fork 227
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
[BUG] {OAK-D Calibration Failure} #1091
Comments
Hi @aiManny , |
Use latest depthai library (v2.22.0) and then run examples/calibration/calibration_dump.py example and paste the output |
Here's the raw output: Is EEPROM available: True |
@aiManny add Note, this combination will remove all existing calibration/eeprom info, so use with care |
Is the idea that removing the existing calibration will allow for a smooth recalibration? I ask because as of right now I don't have a way to recalibrate my device if I were to loose it's current eeprom info. |
@aiManny correct + the original calibration is still here in the post so coukd be reconstructed if need may be |
I get the same console output even with the |
I also downgraded to |
@aiManny try with below json (zipped)
Then execute above as Same factory flashing env var should be set. Note, use latest depthai: |
The calibration flash was successful. When I try running a depth preview I'm no longer seeing a CPU trap error, but I'm getting this instead:
Did that |
@aiManny |
Yesterday I tried running the calibration script for my OAK-D with
python3 calibrate.py -s 2.2 -brd bw1098obc -db
. I successfully captured all images and viewed reprojection error however but was then interrupted by this error:My setup uses:
@jakaskerl alluded to possible issues with the script itself. Any thoughts @MaticTonin?
I'm recalibrating to try fixing my depth pipeline failure described on this thread
The text was updated successfully, but these errors were encountered: