Sensor Debugging

Posted by on Jan 11, 2022 in Design, Environmental | No Comments

This has been a back-bench project for a couple of months but I thought I’d share some progress on how difficult physical computing can be.

Here’s an example of sensors going bad:

Notice all the bouncing of CO2 and tVOC?  That’s not good.  Is the CCS881 dying?  Did a software update to linux break something?

Things I tried, and more importantly, in the order I tried them:

  • Reset the baseline every 10 minutes, every 5 minutes.  No change.
  • Swap in a spare sensor.  No change.
  • Noticed a slight breeze while I’m swapping sensors.  Did I rearrange the room on 9 Nov?  I dunno.  Block the breeze with some paper.  Slight improvement
  • Put a glass over the sensor.  No improvement.  Ok, so it’s certainly not the breeze or disturbed air, something is really wrong here.
  • Detach the PM25. CCS881 works as expected.  WTF?
  • Reattach the PM25, turn it off in software.  CCS881 is bouncing again.  Glass is still covering the sensor.
  • Set up an entirely new Pi from scratch, used the CCS881 solo, no problems.  Added the PM25 and the fluctuations returned.

So how is the PM25 interfering with the CCS881, even when it’s not being read?

This is one downside to using someone else’s API. Is there an I2C bug?  Is the PM25 dying?  How could it alter the values returned by the CCS881?

“To be continued…”

« | »

Leave a Reply