With the I2C backpack there are three pairs of landings, A0, A1, A2, which determine the 3 LSB of the device's address, using inverted binary.
Left alone, they generate part of the F or 7 part of the address. 0x3F is common, as is 0x27.
To use more than one device it is necessary to jumper them all uniquely.
The upper bits that generate the 0x3 are hard-wired. So is the highest bit of the lower byte. Only the three lowest-order bits can be changed.
Since these address bits are inverted, jumpering the A0 will subtract 1 from the address. 0x3F will become 0x3E, 7 will become 6.
You have control enough to make up to 7 LCD modules on the same I2C bus.
The only caveat is that if you have more than one device writing to the various LCDs you might get collisions, which can mess up the display pretty good.
There are questions on I2C collision avoidance and detection on http://RaspberryPi.StackExchange.com if that is your situation.
Jumpering one or more of them is pretty easy - just pre-tin some wire and solder it quickly then cut off the excess.
Wire the SDA and SCL wires of the LCDs in parallel and to the SDA and SCL pins on the Arduino, usually A4 and A5. (I always begin with a breadboard for this). Make sure you have discrete pull-up resistors (10K is common) on each, in only one place on the bus.
If you have a DS3231 RTC module in the system, you do not need to add pull-ups because it has them internally.
If one LCD is already working then you know you have proper pull-up voltage on the bus. (The signals are switched to the ground state to send data on the I2C bus)
So, to Summarize:
If you have two LCDs in your system you can use LCD modules that already come with different addresses, like
for the first one, then
for the second one.
Note that the parameters for these definitions are
0x27 and 0x3F are the most common stock addresses and 0x27 modules are getting harder to find.
If you have a 0x27 then it is very likely that if you buy a newer one it will be 0x3f. Problem solved.
The d4 and d5 in the definition specifies the pins to use for I2C.
You can run the i2cscanner program to see what it finds, once they are wired together. If you see two different addresses, say 0x27 and 0x3F, then you are good to go.
If only 2F shows, then you want to consider soldering A0 together on one module then run the scanner again to make sure it worked.
Here is how I usually do it when both come set as 0x3f:
I have a Yellow one which is a stock 0x3F and a Blue one where I jumpered A0 to make it 0x3E. They both are 20 x 4 displays.
Here are my definitions: (remember, the 4,5 define SDA, SCL pins)
LiquidCrystal lcdblue (0x3e,2,1,0,4,5,6,7,3,POSITIVE);
Then in setup() I use this:
And it's good to go, using pin A4 as SDA and A5 as SCL.
You know they are working as they wink their backlights at you.
If one of yours is 20 x 2 then use
lcd2.begin(20,2); of course.
If you REALLY want to use other pins for your I2C bus then just change the 4,5 in the
LiquidCrystal_I2C definition to the pins you want to use. I never have met anyone who would want to do this.
Hope this helps.