Dear Sparkfun Team,
We are evaluating a development sensor (P/N: 14844) and encountered an issue during use. We would appreciate your insights on possible root causes and whether this may be a defect.
Setup / Configuration:
Host: M5StickC Plus2
Interface: Qwiic (I2C, 3.3V)
Application: Temperature distribution measurement of components
Observed Behavior:
I2C communication is functional:
Device address is recognized
EEPROM readout is successful
However, an error occurs when attempting to acquire a thermal image
No visible physical damage on the device
Usage Conditions:
First-time use (not previously used)
Operated for approximately 3 hours before the issue appeared
No firmware update on the sensor itself (only MCU-side programming)
Standard Qwiic connection (3.3V), no known overvoltage or overcurrent condition
Questions:
- What could cause a situation where I2C communication (including EEPROM access) works, but thermal image acquisition fails?
- Is it possible that only the sensing/imaging function has failed while the digital interface remains operational?
- Could this be related to initialization sequence, timing, or software handling rather than hardware damage?
- Are there known failure modes for this type of sensor after several hours of operation?
- Is recovery possible (e.g., reset, reinitialization), or is this likely a permanent failure?
Based on this behavior, would this be considered an early-life failure / initial defect?
Any guidance or similar experiences would be highly appreciated.
Thank you.
T4914446