Hello.
I wrote the following code that I use to report sensor data mq-7 (carbon monoxide) and dht11 (temperature and humidity).
The problem is in the dht11 sensor, the display does not show the writing humidity with the value.
checking the code on the arduino idle an error will appear.
Where is the problem?
Kind regards.
P.S: I leave the code file, if you can tell me where I went wrong.
rilevatore_gas_2_2.0.ino (2.58 KB)
Program in text.txt (2.58 KB)
You have lots of "dead" / unused code after the updateMillis() function.
It is all the code starting with:
Serial.println("=================================");
Everything from that line to the end of the file should be deleted to allow the code to compile.
--- bill
digitalWrite(ledPin, ledValue);
delay(100);
} // this closes loop()
void updateMillis()
{
previousMillis = currentMillis;
} // this closes updateMillis
// all of the rest of the code is outside of a function which is illegal.
Serial.println("=================================");
Serial.println("Sample DHT11...");
You need to mind your curly brackets. I don't know what you intend, but all the code needs to be in a function [loop() maybe?]. I would suggest that you move the updateMillis function definition to after the end of the code and clean up the curly brackets and then the code may compile.
You can better see the program flow and the program's blocks of code if you use the autoformat function of the IDE (ctrl-t or Tools, Auto Format).
Please post code and error messages as described in the how to use this forum-please read sticky. Post the entire text of the error message.
read the bottom half of my signature line
what does everything after 0x27 do in an I2C LCD system?
LiquidCrystal_I2C lcd(0x27, 2, 1,0,4,5,6,7,3,POSITIVE);
I'm assuming this is a serious question.
The parameters in the constructor configure the library.
The constructor being used is for a library that provides and i/o class that is for devices that are not really I2C based LCDs but rather a standard hd44780 LCD that is controlled by using i/o pins on an i2c i/o expander.
The library must be told how those i/o expander i/o pins are wired up to the LCD pins and the backlight circuit as well as the active level needed on the backlight control pin to turn on the backlight.
If you use the hd44780 library and hd44780_I2Cexp i/o class, it can figure all that out for you so the constructor for the lcd object does not need any parameters.
--- bill
my I2C library handles that. I never saw it done this way before
Can you provide a link to that library?
So far the only library I've seen that supports using a PCF8574 to talk to a hd44780 LCD and auto locates the i2c address as well as auto detecting the pin mappings is my hd44780 library.
--- bill
the only library that worked for me when I started my project:
I am familiar with that library and while it may work for you, it does not "... handle that .." as you said (auto detect address and pin mappings like the hd44780 library).
LiquidCrystal_PCF8574 requires that the i2c address be specified in the constructor and it hard codes the pin mappings and backlight control to one specific backpack design.
Depending on the backpack that a person has, it may or may not work with their backpack.
Also, that library (LiquidCrystal_PCF8574) has s/w licensing issues. It has both LGPL and copyright violations.
The author has attempted to change the s/w license of the library but since the library was a derivative from a LGPL project, he does have the rights to do so. So regardless of the author claiming to have re-licensed his derivative as BSD, he can't do that as that is not allowed by the code he started with.
For sure the author is aware of this but has chosen to ignore the LGPL/GPL licensing rules / restrictions. (more than once)
While people can use anything they want for their personal projects, using that library for a commercial closed source Arduino based product would put the product at risk since while BSD licensing does allow that, LGPL (which is the real license of this code) requires some additional things be done that are not possible when using Arduino and the Arduino IDE.
i.e. if using LGPL based code in a project, there isn't a way to fully comply with all the LGPL license terms when using the Arduino environment other than to open source the entire project.
--- bill