Hello everyone, I have a few questions regarding some details of the camera calibration of the OAK-D Pro: 1. Each device has at any point two separate calibrations saved in its EEPROM: one factory calibration (**device.readFactoryCalibration()**) for factory resets and one general purpose calibration that is actually used by the device (**device.readCalibration()**)? 2. Is the second calibration the one loaded when the camera boots? What is then the point of the following code in the examples for code examples for the dynamic calibration [link](https://docs.luxonis.com/software-v3/depthai/depthai-components/nodes/dynamic-calibration/#:~:text=calibration%20%3D%20device,(calibration)) ? `calibration = device.readCalibration()` `device.setCalibration(calibration)` 3. After performing a dynamic calibration, the new calibration has to be set with the **DynamicCalibrationControl.ApplyCalibration()** command. Is this permanent, as in is the new calibration saved inside the device EEPROM even after reboots, or do I have to use **Device.flashCalibration()** with the newly obtained calibration? Thank you!

Dynamic Calibration

DanielScho

Hello everyone,

I have a few questions regarding some details of the camera calibration of the OAK-D Pro:

Each device has at any point two separate calibrations saved in its EEPROM: one factory calibration (device.readFactoryCalibration()) for factory resets and one general purpose calibration that is actually used by the device (device.readCalibration())?
Is the second calibration the one loaded when the camera boots? What is then the point of the following code in the examples for code examples for the dynamic calibration link ?

calibration = device.readCalibration()

device.setCalibration(calibration)
After performing a dynamic calibration, the new calibration has to be set with the DynamicCalibrationControl.ApplyCalibration() command. Is this permanent, as in is the new calibration saved inside the device EEPROM even after reboots, or do I have to use Device.flashCalibration() with the newly obtained calibration?

Thank you!

OskarSonc

Hey @DanielScho - each OAK-D Pro stores two calibrations internally. A factory one (read with readFactoryCalibration()) and a user/active one (read with readCalibration()). On boot the device uses the user calibration and only falls back to factory if that’s missing or invalid.
The readCalibration(); setCalibration(); pattern in the examples is mostly just showing how to push a calibration into the running session – on a healthy device it’s effectively redundant.
DynamicCalibrationControl.ApplyCalibration() only updates the calibration for the current run; if you want to keep the new result after a reboot, you need to call device.flashCalibration(newCalib) to store it in the user slot in EEPROM (factory calibration stays untouched).

Thanks,
Oskar