You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Originally running on Feather ESP32v2 latest wippersnapper (and a few versions ago, maybe 60's), also tested on feather s3 tft,
the sensor is set to 30seconds polling period, and after approximately 5minutes of good readings it would stop sending any data back to IO and the serial says data not available. I also another day (not espv2 but s3) saw it repeatedly do it after 11minutes in a later testing session.
What's most annoying is it runs for 5-10minutes before happening, then says nothing except the
if (!_aqi->read(&_data)) {
Serial.println("[UART, PM25] Data not available.");
To Reproduce
Steps to reproduce the behavior:
Add Uart PM2.5 PMS5003 to esp32v2 or s3 tft feathers on wippersnapper device pages
Start logging serial (add timestamps).
Come back in 11 minutes and see whats happened.
The text was updated successfully, but these errors were encountered:
I may try isolating that section out of WipperSnapper, and into an Arduino sketch to see if the UART bus still fails to poll new data from this sensor long-term.
Assigning to myself to retest this sensor on C6 and PicoW.
There has been a commit to extend the delay in the library example before attempting to use the sensor to 3seconds.
We may need similar or to just accept the failed first reading attempts.
Note to self: Remove Alert from Guide page once resolved:
https://learn.adafruit.com/pm25-air-quality-sensor/wippersnapper
Describe the bug
Originally running on Feather ESP32v2 latest wippersnapper (and a few versions ago, maybe 60's), also tested on feather s3 tft,
the sensor is set to 30seconds polling period, and after approximately 5minutes of good readings it would stop sending any data back to IO and the serial says data not available. I also another day (not espv2 but s3) saw it repeatedly do it after 11minutes in a later testing session.
What's most annoying is it runs for 5-10minutes before happening, then says nothing except the
To Reproduce
Steps to reproduce the behavior:
Add Uart PM2.5 PMS5003 to esp32v2 or s3 tft feathers on wippersnapper device pages
Start logging serial (add timestamps).
Come back in 11 minutes and see whats happened.
The text was updated successfully, but these errors were encountered: