+ added code to reflect faulty reading in temperature (-999) and humidity (-999) if there is a timeout. So if a sketch does not test the return value of read11() or read22() you will still see it clearly.

One suggestion for the code is to replace or augment the read11 and read22 routines by one unique read routine that would detect which one it is and return 11 or 22 in chk.

I'm not sure it is _so_ easy, but for example, having both [2] and [4] zero with a DHT22 should almost never happen, right ?

They are the lsB if I get it right, so humidity has to be 25.6, 51.2 or 76.8 for byte[4] to be zero.Then in that case temperature has to be precisely 25.6 etc. Pretty unusual.

To be even more confident, there could be a "confidence" variable based on previous measurements: increase/decrease a uint8_t counter for every non/zero value with saturation @ +127/-128, so DHT11 goes from zero @reset to -128 and DHT22 to +127.

Another thing is to replace the double by an int in tenths of degrees. So for DHT11 it would return array[0]*10;

One suggestion for the code is to replace or augment the read11 and read22 routines by one unique read routine that would detect which one it is and return 11 or 22 in chk

Don't mix error state with configuration information. That said, one could make a function int determine() that does just that. Typically it is called just once and remembered - you just needs one byte to keep the 11/22 flag of 8 sensors.

Quote

I'm not sure it is _so_ easy, but for example, having both [2] and [4] zero with a DHT22 should almost never happen, right ?

possible but one could only account readings for which [2] and [4] are zero AND the checksum is OK.

Assuming a valid reading, both numbers have one decimal place 0..9 =>10 possible values. This implies that the chance would be about one in hundred for an individual reading to have two 0's as decimal. That is a small chance but too big imho to make a reliable determine() function, it is definitely not deterministic. Multiple readings with will improve this number but as the device needs 2 seconds between readings so determine() function becomes quite time consuming.

Note that especially for the DHT11 one can use a (running) average to get a higher precision - and thus decimal places ).

+ added code to reflect faulty reading in temperature (-999) and humidity (-999) if there is a timeout. So if a sketch does not test the return value of read11() or read22() you will still see it clearly.

As allways comments still welcome

I would change the follow code in read22() and read11() functions from

Nice library. However, it does not work correctly for negative temperatures. I'm using version 0.1.04. When a negative temperature is measured the class will return DHTLIB_ERROR_CHECKSUM. The problem is at line 74 in dht.cpp. Here bits[2] is modified, which makes the checksum calculation incorrect. There are, of course, many ways to fix the problem. I have fixed it by changing the code in the following way.

No idea why someone wants to write code if there already exists a perfectly fine library... but... I just checked in a DHT library with the following features: - Support for DHT11 and DHT22, AM2302, RHT03 - Auto detect sensor model - Very low memory footprint - Very small code

Looked at your code and it looks like a decent piece of work. It is similar to a version I'm working on and yes I better stop with that version

The difference between your code and mine is that your code encapsulated an individual sensor while mine encapsulates the handshake so multiple sensors use one instance. Footprint will differ too but not measured. I like the auto-detect functionality, well done

There is one improvement I want to propose to your class which I had build in my draft. If there is a time-out I would return the previous values instead of NaN. The error flag should still be the same. To do this the results temperature & humidity should have class scope.

If the program requests the temperature too fast it just gets the prev value which is seldom far from the actual value (instead of a NaN)

Rob:- Has a delay of 20msec for both DHT11 and DHT22.- Uses a counter in the while to break out of the while in case the pin does not change

Mark:- Has a delay of 18msec for the DHT11 and 800usec for the DHT22.- Uses an endless while loop, so if the pin does not change --> Arduino in endless loop!

Further:- I am using multiple DHT22's on different pins. Which library would be most RAM efficient?- Is the 800usec the right delay for the DHT22? If so, it saves me 5*19msec = 75msec of doing nothing, which is a lot using NilRTOS/ChibiOS RTOSses...

Rob:- Has a delay of 20msec for both DHT11 and DHT22.- Uses a counter in the while to break out of the while in case the pin does not change

The counter makes the loop fool proof. The 20 mSec is to make code as similar as possible for both sensors, Mark optimizes the code to the detail of the datasheet which is good better

Quote

I am using multiple DHT22's on different pins. Which library would be most RAM efficient?

Not tested, I expect the lib from mark be smaller for a single sensor but my lib can support multiple with one instance. Somewhere there must be a break even point.It would be very informative if you could provide some numbers

Quote

- Is the 800usec the right delay for the DHT22? If so, it saves me 5*19msec = 75msec of doing nothing, which is a lot using NilRTOS/ChibiOS RTOSses...

800usec - check datasheet.

In an RTOS one should schedule another thread when delay is called, to return /test later. In pseudocode