Calibration Record Management
Store traceable calibration coefficients with units, method, date, equipment and integrity protection.
Arduino-compatible frameworks, ESP-IDF/FreeRTOS, PIC/AVR/STM32/RP-class systems; apply exact vendor documentation for the selected MCU.Architecture
Reference stimulus → raw measurements → coefficients → validation points → versioned calibration record.
Security and recovery risks
- Do not overwrite raw calibration evidence.nUse finite bounds before applying coefficients.nDefine recalibration and invalid-record behaviour.
Implementation procedure
- Define measurand, units and tolerance.nRecord reference equipment ID/date.nCapture raw points and calculate coefficients.nValidate at independent points.nStore schema version and integrity check.
Starter code / configuration
{"schema":1,"serial":"TCSP-000001","channel":"adc1","slope":1.0021,"offset":-0.004}Verification evidence
| Test | Expected | Evidence |
|---|---|---|
| Nominal boot | Correct version and hardware revision reported | Captured boot log |
| Fault recovery | Defined safe state and reset reason | Fault-injection record |
| Power cycle | No corrupt configuration or unsafe output | Repeated-cycle log |
Required release artifacts
- Versioned firmware binary and SHA-256
- Source revision / build identifier
- Board and hardware-revision compatibility list
- Test report and known limitations
- Recovery image and factory-reset procedure
- Provisioning/calibration schema
- Release approval record
Local browser tools
Firmware production workbench
A/B update exercise
OTA and automatic rollback simulator
Advance one validated stage at a time. A failed boot test returns the device to the previous slot.
- Running confirmed firmware from Slot A.
Release gate
Production-readiness checklist
A downloadable release decision is generated only after every mandatory control is confirmed.