_HOT_ Download Library Liquidcrystal

It appears that the problem is caused by the LiquidCrystal_I2C and liquidmenu libraries.

I have searched on the forum and found that there are many different LiquidCrystal_I2C libraries using the same name but with different functions (so that may well be the problem here). I checked my library folder to make sure that I was not using the wrong one. In there I found that at the time I was coding, I had Newliquidcrystal_1.3.5 and LiquidCrystal_I2C-1.1.2. I tried both with no success. It's very annoying because the original code was compiling and working. I even tried to install the IDE version I was using at the time 1.8.7 but it makes no difference. Any suggestion?

I suggest that you forget about the LiquidCrystal_I2C libraries. One problem is that there are several libraries by that name and they are not, necessarily, compatible. If you try to compile an example and it is not written for the particular library, all sorts of strange errors happen. There is a newer and better library for I2C LCDs. It is the hd44780 library by Bill Perry. It is a current and well maintained library. It uses the same API as the older libraries so you don't have to change much. See the examples included with the library.

Download Library Liquidcrystal_i2c.h

DOWNLOAD 🔥 https://urluss.com/2y4Q2F 🔥

For an I2C LCD display to work, the I2C address and the I2C backpack to LCD pin mapping must be correct. If the library default settings for either or both are not correct the LCD will not work. You can try to figure out the right pin mapping and use an I2C scanner to find the address, but if you install and use the hd44780 library that is done automatically by the library.

Install the hd44780 library. The hd44780 library is the best available for I2C LCDs. The library is available in the Library Manager. Go to Library Manager (in the IDE menus, Sketch, Include Libraries, Manage Libraries) and in the Topics dropdown choose Display and in the Filter your search box enter hd44780. Select and install the hd44780 library by Bill Perry.

The class that you want to use is the hd44780_I2Cexp class. There are examples to show how to use the library. The nice thing about the hd44780 library is that it will autodetect the I2C address and the I2C backpack to LCD pin mapping.

Have you edited the LiquidMenu_config.h file in the library folder to indicate you are using the LiquidCrystal_I2C library instead of the LiquidCrystal library? Would really have been better if the author of the library had put the options in the constructor instead of using a config file.

david_2018:

I did not think about editing the library config file (even though it was clearly written in the error message!!) because I did not remember editing any library before (but I must have done at the time)! I have now edited it and it compiles.

Two "important" LCD libraries seem to cause compatibility issues.

I have a program that works well with this library by malpartida, but as soon as I install this library by F. DE Brabandere, my original program does not compile anymore: library error.

Reason: these libraries use identical files for LiquidCrystal_I2C.h and .cpp

Practical question: what to do if I would like to have both libraries available? Or is this besides the question and should the need for more than one library for the same hardware be solved by "proper" programming?

If you are looking for a good library for I2C enabled LCDs with the hd44780 controller (1602, 2004) the hd44780 library by Bill Perry (@bperrybap) is the best. It is faster, has better features, is currently maintained and the author is often on the forum to answer questions. The library is available via the IDE library manager.

IMO, the ones at fault here that created issues like this are actually the Aduino.cc developers.

They are the ones that, IMO, made some unfortunate design decisions that has created the issues related to library header file name collisions.

Years ago, I had offered advice on some ways to solve this when moving to the 1.5x IDE version and the 1.5x library format but they insisted on a few things that meant the issue can never ever be fully resolved.

If things had been done slightly differently there would never been an issue with collisions since the sketch would be able to fully specify library it wanted by using a better header file name that specifies the library/directly in the header file.

i.e.

#include

It is a very small trivial change.

While the change can be made at any time, the best time to have made it was when when the library format was changing as well, but they didn't want to do it.

Even sadder is if they would make the change the way I recommend, it would not affect any existing sketch or library code.

Sketches could explicitly specify the header using the directory name. IF they didn't specify the leading directory name, the IDE would pick it for them using the "guessing method" just like it does today.

Over the years, there has been quite a bit of work to patch things to try to help the issue, which has made things better, but again, due to some things they have decided to do, it is impossible to ever fully resolve.

There are some additional library issues that are going crop with IDE 2.0.0 given some of the changes / differences on how libraries are handled that IDE.

Currently there is a priority on how the library to use is selected when there are name collisions.

What is creating the issue in this case is that newLIquidCrystal and LIquidCRystal_I2C both have a header file named LIquidCrystal_I2C.h

If a sketch includes the IDE will give priority to a library with the same basename as the header file. i.e. LiquidCrystal_I2C

While I would recommend using the hd44780 instead,

there is a way to game or trick the Arduinoi.cc IDE library system to work with both newLIquidCrystal and LiquidCrystal_I2C installed and yet get it to select the one the sketch wants to use.

A sketch can use this method to select either one, but it will not be able to use both at the same time. Normally that is not an issue.

If you want to force the use of newLiquidCrystal LiquidCrystal_I2C you need to include a header file that is unique to newLIquidCrystal, prior to the i/o class header file that has the name collision.

By doing that the IDE will determine the library to use based on that unique header rather than the header file that has the collision which would cause the IDE to select the other library since its directory name matches the file basename which gets priority in the the "guesing game".

I think you missed the part about how the IDE guesses and finally selects the library when there is a header file name collision. The IDE prioritizes the library that is in a directory name that matches the basename of the header file.

I recently bought an Arduino Nano Every and a 16x2 LCD with I2C interface. I set up the board, I installed it in the "Boards Manager", I downloaded the library from here and I installed the library as instructed. I ran a few codes to test the board (Blink) and after I connected the I2C interface I ran I2C Scanner to find the adress.

cattledog:

You may not be using the hd44780 library correctly. With 1.8.9 compiling for a Nano Every with the AT328 emulation I get no errors with the hello world library example for the i2cexp io class.

Before I realised I was using the wrong library I searched for "hd44780" in the library manager and it said that it was already installed but I couldn't find it so I tought maybe it was installed under a different name (as it says under my username I'm a newbie).

Why a manual install?

I would HIGHLY recommend NOT doing that.

The instructions on the github page even recommend using the IDE library manager for all IDEs beyond 1.6.2 and includes step by step instructions of how to do it.

The hd44780 library is available in the IDE library manager. Use the GUI in the IDE to install it.

It is easier and faster than doing it manually.

There are way too many ways to install the library incorrectly,

This includes when importing it using a .zip file created by github.

So the code using hd44780_I2Cexp is about 7.3k larger vs LiquidCrystal.

Quite a bit of that extra code size is the Wire library.

You can get rough idea by including Wire.h in your LiquidCrystal code

and then somewhere in setup() do:

Same problem as reported here for the LiquidCrystal library, the megaavr core used for the atmega4809 based boards does not include the Print.h class file. Fix is to replace #include with #include in the library header file:

david_2018:

If the library works and you keep in mind that the lack of that architecture being specified in the unmodified library might indicate that the author hasn't made any specific attempts to check whether the library is compatible with ESP8266, I don't see any harm in what you did.

I've seen several libraries that has absolutely no architecture specific code, yet specified the avr architecture. I think a lot of library authors don't actually understand what library.properties does and don't bother to read the documentation. They just copy/paste from some other library, change the obvious parts, and leave the rest as is.

The hd44780 library has been tested on many platforms (avr, esp8266, pic32, samd)

It has no architecture specific code so the properties file is setup to compile with no warnings on any/all architectures.

I don't confirm your experience. I downloaded the library from the library manager, and can run the library examples. You may be seeing some warnings, but the library does function with the YRobot lcd. The original program you posted runs for me with the 1.1.2 version from the library manager and ide v1.8.5 and prints the full "Hello World". e24fc04721