AUBRIX.SYSTEMS
Back to engineering archive

Record 090 / Sensing and instrumentation

Blood-oxygen module interface draft

An archived vendor-driver integration acquires module fields and temperature, applies display-only validity filters and reports values or unavailable markers over Serial.

Archived integration draft
I2CDFRobot driver APISerial display

Archived source flow

Archived vendor-driver acquisition. Configure I2C, retry begin until success and start module collection. After the update gate, fetch vendor fields and temperature, apply display-only range filters and print values or unavailable markers. No custom medical algorithm or validated measurement is established.
Vendor-API acquisition and display filtering from archived source. Compilation, module identity and hardware operation are unverified. View diagram at full size

Technical notes

Initialization and pacing

The script configures I2C and retries sensor.begin() every 500 ms until it succeeds, without a timeout. It then starts collection and uses a one-second gate before fetching new fields.

Presentation layer

The application asks the vendor API for heart-rate/SpO2 fields and temperature. Out-of-range heart-rate and SpO2 fields become an unavailable marker for Serial presentation; these are display filters, not clinical validation.

Contribution and evidence limits

The module uses DFRobot_BloodOxygen_S_I2C. Its underlying driver version, physical component identity and measurement algorithm are not established by this member. No custom oximetry algorithm, calibration, clinical accuracy or successful hardware test is presented.

Engineering archiveArchive record

Project enquiries

Discuss your project.

Tell us what you’re developing and where you need engineering support.

Discuss your project