Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using multiple I2C displays -- different types #206

Closed
pisicaverde opened this issue Jun 26, 2018 · 2 comments
Closed

using multiple I2C displays -- different types #206

pisicaverde opened this issue Jun 26, 2018 · 2 comments
Labels

Comments

@pisicaverde
Copy link

There may be an issue when using an ESP8266 + a SH1106 OLED + an alphanumeric LCD display with i2c adapter, on same pins, but with different adresses. The behavior is somehow similar with issue138 -- both of them are updating only if there is a display.init() and lcd.begin() before any command.

Switching to brzo_i2c has disabled any updates to liquidCrystalDisplay.

#include "SH1106.h"
SH1106Wire display(0x3c, D1, D2);

#include <LiquidCrystal_I2C.h>
LiquidCrystal_I2C lcd(0x27, 20, 4);

void setup() {
  display.init(); display.clear(); display.drawString(0, 0, "OLED ready"); display.display();
  lcd.begin(D1, D2); lcd.backlight(); lcd.setCursor(0, 1); lcd.print("LCD ready");
}

void loop() {
  display.init();
  display.clear(); display.drawString(0, 0, "Hello: " + String(millis())); display.display();

  lcd.begin(); 
  lcd.setCursor(0,1) ; lcd.print("Hello: " + String(millis())); 

  delay(100);
}

But calling display.init() & lcd.begin() flickers the screen and worse, it crashes the ESP8266.

Any ideas/workarounds are greatly welcomed.

@stale
Copy link

stale bot commented May 18, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label May 18, 2019
@marcelstoer marcelstoer added stale and removed wontfix labels May 24, 2019
@stale stale bot removed the stale label May 24, 2019
@stale
Copy link

stale bot commented Nov 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Nov 20, 2019
@stale stale bot closed this as completed Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants