How can an OAK4 inspection record identify the exact active calibration?
Hi everyone,
I work with ISO management-system documentation and maintain isochecklist.com. I am currently evaluating how an OAK4-based visual inspection system could be structured when its pass/fail decisions are retained as formal manufacturing quality records.
I am researching the architecture and am not describing an existing production deployment.
After reading the recent automated quality-control and Dynamic Calibration discussions, one traceability issue stood out to me.
An inspection result can be linked to a device serial number, application release, model version and confidence threshold. However, the result may also depend on the exact calibration that was active when the image and measurement were produced.
This becomes particularly important when the device contains its original factory calibration as well as calibrations created later through manual or dynamic recalibration.
For example, a retained inspection record might identify:
the OAK device;
the application and model release;
the relevant pipeline configuration;
the inspection timestamp;
the resulting classification or measurement;
the active camera calibration.
The last item is the part I have not been able to resolve from the available material.
What is the recommended method in OAK4, DepthAI v3 or Luxonis Hub for retrieving and retaining a stable identifier for the exact calibration that was active when an inspection result was generated?
Ideally, the identifier would make it possible to distinguish the factory calibration from later manual or dynamic calibrations and determine whether two historical results were produced using the same calibration state.
Should an application retain an existing calibration ID or checksum exposed by the device, or is the safer approach to archive the complete calibration data alongside the inspection configuration?
For context, I maintain this page explaining the underlying requirements for monitoring resources, calibration status and documented-information control. It is my own resource and is included only to explain the quality-management perspective behind the question; it is not Luxonis-specific documentation.
I would appreciate hearing how teams using OAK devices in industrial inspection currently handle this. After testing the recommended method, I will add the resulting record structure and implementation notes to this thread.
