AUBRIX.SYSTEMS
Back to engineering archive

Record 034 / Connected systems

ESP32–Teensy I2C parameter-transfer draft

Paired archived drafts attempt an I2C parameter exchange for a Teensy-side LED consumer. The supplied byte encoding and reconstruction are inconsistent.

Archived integration draft
I2CPaired-controller draftOctoWS2811 API

Archived source flow

Archived paired I2C request paths. A consumer requests two int-sized parameters. A responder queues four duplicated low bytes; the consumer attempts byte-pointer reconstruction and applies one parameter to an LED-channel argument and indicator. No correct transfer or hardware result is established.
Paired request/response paths reconstructed from archived source. Byte encoding, reconstruction, compilation and hardware interoperation are unverified. View diagram at full size

Technical notes

Two source roles

The responder registers requestEvent(); the consumer requests two int-sized parameters. The sender parameters are constants in this archive, with no implemented Wi-Fi control path.

Byte-transfer defect

The sender queues each parameter’s low byte twice, for four bytes total. The consumer reads through byte pointers and shifts into byte-sized storage; it also requests a type-dependent byte count without checking availability.

LED consumer

The consumer passes one parameter into the red-channel argument and a local indicator threshold. The second parameter is reported but does not drive LEDs here. No corrected serialization, board build or observed lighting result is claimed.

Engineering archiveArchive record

Project enquiries

Discuss your project.

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

Discuss your project