-
Notifications
You must be signed in to change notification settings - Fork 227
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
Communication error with the LCD2004 display. #393
Comments
Please show the logging. |
`ets Jun 8 2016 00:22:57 rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) D: Starting ESP32-radio running on CPU 1 at 240 MHz. Version Sun, 18 Oct 2020 10:15:00 GMT. Free memory 287572 Backtrace: 0x4014806a:0x3ffb1c00 0x401490e6:0x3ffb1c20 0x400d2389:0x3ffb1c60 0x400d23d2:0x3ffb1c80 0x400d23ff:0x3ffb1ca0 0x400d2410:0x3ffb1cc0 0x400d2539:0x3ffb1ce0 0x400d276a:0x3ffb1d10 0x400d6191:0x3ffb1d80 0x400d87a9:0x3ffb1ec0 0x400db8e7:0x3ffb1f60 0x400e3cd5:0x3ffb1fb0 0x4008aba9:0x3ffb1fd0 Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) D: Starting ESP32-radio running on CPU 1 at 240 MHz. Version Sun, 18 Oct 2020 10:15:00 GMT. Free memory 287572 Backtrace: 0x4014806a:0x3ffb1c00 0x4014906b:0x3ffb1c20 0x400d2394:0x3ffb1c60 0x400d23d2:0x3ffb1c80 0x400d23ff:0x3ffb1ca0 0x400d2410:0x3ffb1cc0 0x400d2539:0x3ffb1ce0 0x400d276a:0x3ffb1d10 0x400d6191:0x3ffb1d80 0x400d87a9:0x3ffb1ec0 0x400db8e7:0x3ffb1f60 0x400e3cd5:0x3ffb1fb0 0x4008aba9:0x3ffb1fd0 Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) D: Starting ESP32-radio running on CPU 1 at 240 MHz. Version Sun, 18 Oct 2020 10:15:00 GMT. Free memory 287572 Backtrace: 0x4008e498:0x3ffd8140 0x4008e6c9:0x3ffd8160 0x4011b68b:0x3ffd8180 0x4008536b:0x3ffd81b0 0x400861d5:0x3ffd81d0 0x4000bec7:0x3ffd81f0 0x40148f83:0x3ffd8210 0x400d23b7:0x3ffd8230 0x400d23cb:0x3ffd8250 0x400d23f1:0x3ffd8270 0x400d2410:0x3ffd8290 0x400d2516:0x3ffd82b0 0x400d26de:0x3ffd82e0 0x400d46a9:0x3ffd8300 0x400d46d6:0x3ffd8320 0x4008aba9:0x3ffd8340 Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) D: Starting ESP32-radio running on CPU 1 at 240 MHz. Version Sun, 18 Oct 2020 10:15:00 GMT. Free memory 287572 Backtrace: 0x40148f7c:0x3ffd81b0 0x400d23b7:0x3ffd81d0 0x400d23cb:0x3ffd81f0 0x400d23ff:0x3ffd8210 0x400d2424:0x3ffd8230 0x400d245f:0x3ffd8250 0x400d24e1:0x3ffd8280 0x400d276a:0x3ffd82b0 0x400d46a6:0x3ffd8320 0x400d46d6:0x3ffd8340 0x4008aba9:0x3ffd8360 Rebooting... rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) D: Starting ESP32-radio running on CPU 1 at 240 MHz. Version Sun, 18 Oct 2020 10:15:00 GMT. Free memory 287572 |
@hevet comment displaytime part in LCD2004.h. Works for me. |
Pin 21 and 22 are also used for I2C. Please remove them in the config page of the web interface. |
I don't really understand, for me the pins 21 and 22 are I2C, I can't remove them, because then there will be no display support. |
Yes, you are right. LCD2004 is I2C. I forgot. |
Fixed. |
Cool, looks like it's working fine. Unfortunately, the volume level has disappeared. dline[3].str += "\x7F" ; // Add block character and from what I can see it's a blank character, the dash is x2D. Unless it is meant to be? |
I guess it depends on the display. You may use any character you like. |
I did, thanks for the quick fixes. |
Correct. It depends on i2c controller. I couldnt find block and used \x23 (hash char) |
Hello - where do the I2C pins get set? My debug output has: and I believe it should be: |
You can set the pins in the config page of the webinterface. Read the documentation, page 19. |
After uploading the latest version, there is a problem with the LCD2004 display. There is an error comunication error with the display in the terminal. The radio tries to initialize it, after an unsuccessful attempt, it restarts with the network and tries to initialize the display again. After several attempts, it finally succeeds, sometimes it takes a few minutes, but it can also start without a working display. Checked on two displays. I have downloaded an older version and there is no problem, the radio starts up quickly and there is no problem with initializing the display.
The text was updated successfully, but these errors were encountered: