Author Topic: Fake BME680 (Bosh temp/VOC sensor) ? [SOLVED]  (Read 1116 times)

0 Members and 1 Guest are viewing this topic.

Offline Gabri74Topic starter

  • Regular Contributor
  • *
  • Posts: 112
  • Country: it
Fake BME680 (Bosh temp/VOC sensor) ? [SOLVED]
« on: November 08, 2024, 10:21:16 am »
Hi, I was just wondering if anyone has ever been supplied with fake BME680 sensors.
I've just bought two new modules to integrate into an existing project, but the readings are all wrong, to the point they seems fabricated.
(link to the module https://it.aliexpress.com/item/1005007312026696.html )
(I know that the price was a bit to low for this kind of sensor, but being quite old and superseded by the 688 I risked it )

I.e. on the other genuine sensor, those are the readings I get:
IAQ: 83
static IAQ: 52
CO2: 620 (ppm)
VOC: 0.8

On the fake(?) sensor I get completely different readings:
IAQ: 243
static IAQ: 814
CO2: 8140 (ppm)
VOC: 1000

Note that on the fake sensor:
- IAQ and static IAQ are too far apart
- VOC is constant at 1000 (!)
- static IAQ is always equal to CO2 / 10 --> this in particular make me think the values are fabricated

I'm using the official Bosch library.

Those sensors have a settle/burn in period and admittedly I've just stared using them for a few hours... but the values are two wrong to be a genuine part...

Does anyone know if it is possible to detect using some I2C commands if the chip is fake or genuine ?
« Last Edit: November 09, 2024, 04:27:22 pm by Gabri74 »
 

Online wraper

  • Supporter
  • ****
  • Posts: 17953
  • Country: lv
Re: Fake BME680 (Bosh temp/VOC sensor) ?
« Reply #1 on: November 08, 2024, 10:40:16 am »
I would not be surprised if sensor is genuine but screwed up during PCB production.
 
The following users thanked this post: Gabri74

Offline Gabri74Topic starter

  • Regular Contributor
  • *
  • Posts: 112
  • Country: it
Re: Fake BME680 (Bosh temp/VOC sensor) ?
« Reply #2 on: November 09, 2024, 04:26:42 pm »
Thanks for the reply.

I turned out it was my fault all along... I forgot that I did implement calibration saving when full accuracy was reached.
When I swapped the old sensor with the new on my test unit, I forgot to clear the calibration.

It appears that calibration parameters for those sensor could be quite different from one another, and the old
calibration loaded at power up was screwing up the algorithm and giving me saturated values for some parameters.
 
The following users thanked this post: Doctorandus_P


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf