-
Notifications
You must be signed in to change notification settings - Fork 62
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
Does not work with Teensy #9
Comments
The error code 101 is defined:
That because the start high signal is not arrived according to https://cdn-shop.adafruit.com/datasheets/DHT22.pdf If Teensy is more accurate, I think it should work. I will do some research. |
I note that there's a comment:
I think it's because it use for loop to simulate the delayMicroseconds, as the Teensy is a faster chip so it need to change the threshold. But we use delayMicroseconds and now that Teensy is much more accurate, I think the delayMicroseconds is also accurate, why should change the |
I found it, it's because the data format is changed. Read I will fix it in v1.0.5, please try it when released. |
Read #2 |
Hi,
I've got a DHT22, running the DHT22Default example.
I'm trying to get this library to work with the Teensy 3.6 and I'm getting a standard error:
err=101
This is using a cloned library of this git so latest version I assume. The board works with the standard ADAFRUIT library but I'd prefer to use this one as I can access just the simple bits which would speed up the data collection. I've read that the Teensy is much more accurate with its delayMicroseconds and the CPU I'm running clocks at 180MHz whereas an arduino would be around 18MHz, maybe I should just slow down the transfer?
Thanks,
Rowan
UPDATE ***
After reading https://forum.pjrc.com/threads/16806-T3-FYI-Adafruit-DHT22-AM2302
I changed the delayMicroseconds(10) to (15) in your .cpp and (30) to (35) and got this output
Sample OK: 0 *C, 2 %
Now unfortunately I think this data is incorrect as it's definitely not 0*C!
I'll have another go tomorrow
The text was updated successfully, but these errors were encountered: