esp Build:68 with problem

[vmfs1968]

Hello
I am testing the version 68, and with this version gives error with the sensor DHT22
It is always wrong data
sometimes fails to detect the sensor
with previous versions worked well

[BertB]

I do not have this problem. Everything works like a charm.

[vmfs1968]

because I give, attested in two esp and gives the same problem
there must be something wrong

DHT : Temperature: -8.40
DHT : Humidity: 30.70
DHT : Temperature: 16.80
DHT : Humidity: 61.50
DHT : Temperature: 16.80
DHT : Humidity: 61.50
DHT : Temperature: 16.80
DHT : Humidity: 61.40
DHT : Temperature: 16.80
DHT : Humidity: 61.40
WD : Uptime 337 ConnectFailures 0 FreeMem 25432
DHT : Temperature: 16.80
DHT : Humidity: 61.40
DHT : Temperature: 16.80
DHT : Humidity: 61.40
DHT : Temperature: 16.80
DHT : Humidity: 61.40
DHT : Temperature: 16.80
DHT : Humidity: 61.60
DHT : Temperature: -8.40
DHT : Humidity: 30.70
DHT : Temperature: 16.80
DHT : Humidity: 61.50

[BertB]

Is that an actual list?
What is the value of sensor delay in Config?

This is what I have:
DHT : Temperature: 21.50
DHT : Humidity: 31.60
DS : Temperature: 19.19 (28-7e-dc-34-5-0-0-99)
WD : Uptime 1 ConnectFailures 0 FreeMem 26400
WD : Uptime 2 ConnectFailures 0 FreeMem 26400
DHT : Temperature: 21.30
DHT : Humidity: 31.80
DS : Temperature: 19.37 (28-7e-dc-34-5-0-0-99)
WD : Uptime 2 ConnectFailures 0 FreeMem 26384
WD : Uptime 3 ConnectFailures 0 FreeMem 26384
DHT : Temperature: 21.20
DHT : Humidity: 31.90
DS : Temperature: 19.56 (28-7e-dc-34-5-0-0-99)
WD : Uptime 3 ConnectFailures 0 FreeMem 26320

[Martinus]

Mine's ok too. Running on R68:

Code: Select all

RX: 8:59:52 PM WD   : Uptime 51 ConnectFailures 0 FreeMem 26176
RX: 8:59:52 PM DHT  : Temperature: 19.40
RX: 8:59:52 PM DHT  : Humidity: 31.40
RX: 8:59:52 PM HTTP : connecting to 192.168.0.8
RX: 8:59:52 PM HTTP : Succes!
RX: 8:59:52 PM HTTP : closing connection
RX: 8:59:52 PM ADC  : Analog value: 8
RX: 8:59:53 PM HTTP : connecting to 192.168.0.8
RX: 8:59:53 PM HTTP : Succes!
RX: 8:59:53 PM HTTP : closing connection
RX: 9:00:22 PM WD   : Uptime 51 ConnectFailures 0 FreeMem 26176
RX: 9:00:22 PM DHT  : Temperature: 19.40
RX: 9:00:22 PM DHT  : Humidity: 31.40
RX: 9:00:22 PM HTTP : connecting to 192.168.0.8
RX: 9:00:22 PM HTTP : Succes!
RX: 9:00:22 PM HTTP : closing connection
RX: 9:00:22 PM ADC  : Analog value: 7
RX: 9:00:23 PM HTTP : connecting to 192.168.0.8
RX: 9:00:23 PM HTTP : Succes!
RX: 9:00:23 PM HTTP : closing connection
RX: 9:00:52 PM WD   : Uptime 52 ConnectFailures 0 FreeMem 26416
RX: 9:00:52 PM DHT  : Temperature: 19.30
RX: 9:00:52 PM DHT  : Humidity: 31.30
RX: 9:00:52 PM HTTP : connecting to 192.168.0.8
RX: 9:00:52 PM HTTP : Succes!
RX: 9:00:52 PM HTTP : closing connection
RX: 9:00:52 PM ADC  : Analog value: 7
RX: 9:00:53 PM HTTP : connecting to 192.168.0.8
RX: 9:00:53 PM HTTP : Succes!
RX: 9:00:53 PM HTTP : closing connection

[CHK_BLN]

I have the same problem as VMFS 1968 describes.
it looks as if the measurement is divided by 2

[BobS]

Hi, I have seen this problem too.
I think it's caused by timing issues when reading the DHT.
Sometimes an extra bit is read before the actual value this results in a measurement with only half the value.

Maybe this can be corrected by changing the value of the pull-up resistor or using another input.

Looking in the code there is a line with a delay of 40 micros in the function that reads the temperature, this line is commented out.
I did some experiments and for me introducing a delay of 5 microseconds works fine.

Hope this helps.

[vmfs1968]

Hello
tou see that there are more people with the same problem
I know that in version 63, this part works well