I have a couple of RHT03 sensors that work with my Uno at 5v, but are providing only 0's at 3.3v. From the data sheet I have, it appears these sensor should be working at 3.3v, but all I am getting from them is 0 value.
I am using the ADAFRUIT DHT library and the problem is occurring with the 3.3V Arduino pro mini. I am wondering if the problem is being caused by the 8MHz clock frequency of this mini? Does anyone have any suggestion
More than 700 posts and you still didn't learn to post the necessary information. Please, please, please, please always add links to the used hardware and libraries. You waste our time if you let us google for that stuff just to find another version of the library or hardware than you're using and in the end we've to do everything twice.
I am wondering if the problem is being caused by the 8MHz clock frequency of this mini?
If you're using this library GitHub - adafruit/DHT-sensor-library: Arduino library for DHT11, DHT22, etc Temperature & Humidity Sensors, specified the correct type in the code and the correct board in the IDE, this shouldn't influence the result. Post your sketch.
Well your 4000+ posts don't appear to have helped your reading comprehension... The code, and the sensor work fine as is with an Arduino Uno. So the CODE is not the problem. Since it works with the UNO none of your comments are relevent.
My question was concerning using this sensor with an 8MHz Pro Mini. Since the data sheet specifies that the device works with 3.3v, the 8mhz speed leads me to believe that the timing (critical for this sensor) in the library is the problem. My QUESTION was concerning anyone else who may have used this sensor in a similar environment, and if they noticed such a problem.
So is that clear enough for you pylon? Since you would need to 'google' the library/setup you don't have the 'experience' my question was asking for.
Well your 4000+ posts don't appear to have helped your reading comprehension... The code, and the sensor work fine as is with an Arduino Uno. So the CODE is not the problem. Since it works with the UNO none of your comments are relevent.
So if the CODE is not the problem, you must have already solved the problem. Because if your idea about the processor clock speed would have been correct, that would have been a code problem. And I checked that with the library I linked, so I'm sorry but my comments are relevant.
So is that clear enough for you pylon? Since you would need to 'google' the library/setup you don't have the 'experience' my question was asking for.
It's not a good idea to affront the people who want to help you in the forum. My starting comment was about something that is clearly mentioned in the sticky note at the top of the forum. If you read it and acted according to it, my comment wouldn't have been necessary.
BTW, I did successfully use a DHT-22 sensor on a 8MHZ 3V3 ATmega328p (OK, it wasn't a Pro Mini but a custom board, I don't think that this difference is relevant), so I had the impression that my experience is not that way out of what you were looking for.
Pylon,
Your assistance (if that is what you want to call it) IS NOT REQUIRED OR DESIRED.
The code works on another platform, with the exact same wiring configuration. To make this clear, I can plug the power, gnd and signal into a Uno, and submit the same sketch and get the proper results. So even you should be able to grasp that code and wiring are not the problem. I suspect I know what the problem is, but before I break out the oscope, I posted a question to see if anyone else had encountered this issue before.
So pylon, please take your attitude elsewhere. Pehaps other can use your 'help'...
The code works on another platform, with the exact same wiring configuration. To make this clear, I can plug the power, gnd and signal into a Uno, and submit the same sketch and get the proper results. So even you should be able to grasp that code and wiring are not the problem. I suspect I know what the problem is, but before I break out the oscope, I posted a question to see if anyone else had encountered this issue before.
I did understand that from your first post but you seem to ignore that a different clock speed has implications on the software and a different voltage on Vcc may need a different wiring.
Your assistance (if that is what you want to call it) IS NOT REQUIRED OR DESIRED.
I accept that and will not post again in this topic.