-
Notifications
You must be signed in to change notification settings - Fork 36
Invalid soil temperature readings #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@caternuson could be related to #23 ? |
I tried some simple changes and it looks like the I2C read for the temperature value is just flaky. I'll do some more testing and provide more details tomorrow. It would be good to know if anyone can reproduce this issue....Just run soil_simpletest.py |
This is all it needed: longer delay in I2C read
PR coming after a few more tests |
Ugh. Just now seeing this for some reason. Sorry. Seems to make sense that a delay was needed. The @ladyada But not sure if it relates to that spurious moisture reading issue, which persisted even with bumps in the delay. Could be related in some tangential way though - like deeper in seesaw? |
possibly but i dont have cycles to debug :/ and this is a good enough fix... |
I'm not sure where this issue belongs, but I'd appreciate it if someone and see if they can reproduce it.
This was originally reported here adafruit/circuitpython#1912 butI think it better addressed independent from that issue. I'n not sure if it is a CP or a seesaw issue.
I had been running this sensor successfully up to a few weeks ago but now when I try to run the soil_simpletest.py I get a temperature reading of 16383 consistently. The moisture value looks OK. If I hold my finger on the sensor SAMD chip, there is sometime a small change in the temperature, but it is still meaningless. It should be ~26. where it is located.
Observation: 16383 would be returned if the value read was 0x3ffffff.
I see this on two different sensors.
I tried the sensors with Arduino and they return good temperature and moisture values.
Note, I am running CP 4.10 beta (current master on 6/20)
I get the same results on a feather_m4_express or Pyportal with the I2C interface set to 3.3 V
Note: this all started when I tried using the PyPortal with the I2C interface at the default 5V. When I saw the bad temperature readings, I thought it was due to the I2V voltage and switched to a PyPortal with the jumper set for 3.3V. The problem has remained.
The text was updated successfully, but these errors were encountered: