O2 sensor calibration drift and lab-side traceability
Posted: 08 Sep 2013, 13:34
Slightly off the usual firmware/hardware topics here, but thought some of you dealing with O2 cell replacement and calibration checks might find this relevant.
On the lab side, we do quality control on the O2 and pressure sensors that end up in dive computers and rebreather setups — mainly tracking calibration drift over time and batch consistency before sensors ship out. One thing that's made a real difference for us is having proper traceability software (a LIMS) to log every calibration run against a sensor's batch and serial number, rather than relying on spreadsheets. It's a lot easier to catch a batch that's drifting early, instead of finding out after units are already in the field.
For anyone curious what that kind of lab tooling looks like, here's an example: Bassetti LIMS.
Not trying to sell anything here — just curious whether any of you have run into O2 cell batches with noticeable drift, and how you handle recalibration/replacement intervals on your end.
On the lab side, we do quality control on the O2 and pressure sensors that end up in dive computers and rebreather setups — mainly tracking calibration drift over time and batch consistency before sensors ship out. One thing that's made a real difference for us is having proper traceability software (a LIMS) to log every calibration run against a sensor's batch and serial number, rather than relying on spreadsheets. It's a lot easier to catch a batch that's drifting early, instead of finding out after units are already in the field.
For anyone curious what that kind of lab tooling looks like, here's an example: Bassetti LIMS.
Not trying to sell anything here — just curious whether any of you have run into O2 cell batches with noticeable drift, and how you handle recalibration/replacement intervals on your end.