Go Down

Topic: [LIB] Interrupt driven DHTLib (DHT11 & DHT22 = idDHTLib) (Read 8095 times) previous topic - next topic

Dessimat0r

#60
Jul 31, 2013, 09:19 pm Last Edit: Jul 31, 2013, 09:27 pm by Dessimat0r Reason: 1
With delta > 100 I seem to be receiving entirely correct data:

http://paste.ee/p/KeGJr

So it looks like everything is good now? Please check it over just to be sure :D

Edit: it's also working perfectly in my 'big' app where I switched over to the interrupt version of the lib initially, it has LCD output :) There are no CPU holdups.

niesteszeck

SO NICE!!!!! Now I need to try it with my DH11 sensors, reorder the code to b pretty (not messy and for test purpose) and if my DHT11 is still working, we can say that the entire lib is working, really good news!!!!

you just change the 95 for a 100?
This means that the sensor is taking between 90 and 100 us to send a 0. With all the ping pong conversation that we had, I thing the DHT22 (or maybe just yours) is taking like 10us more in signaling.
really strange behavior and against the datasheet, but Arduino and a cheap sensor doesn't guaranties accurate in timing, so I suppose is a expected behavior.

if you use github, you can push the code with the last mods you make to get it working, so in the history will be your effort!


niesteszeck

Before you do it, let me make a branch for that, so is clean and not with all the not making difference commits

niesteszeck


Dessimat0r

Sorry it took so long to get the changes in there :)

Dessimat0r

Is it worth implementing more robustness if the sensors are removed (i.e., some interrupt timeouts) -- experiment with disconnecting/reconnecting sensors and you'll see what I mean -- the Arduino seems to freeze. Could be my code though.

niesteszeck

Can you report on github please, with the structure:

  • How to reproduce

  • What do you espect

  • What really happens


Go Up