[Arduino] SSD1306 flashes after adding Deep.sleep/Blynk

Question

Hello. Colleagues please help as I have no strength left. Tell me what is wrong in this code that as soon as I add Deep.sleep or initiate Blynk, the display only flashes and displays nothing. Without these functions it works normally and shows measurements from the sensor. . Added after 4...

Marek_Skalski · Answer

And isn't this display from the new series? They need a much higher initialisation delay. Without this, they either display nothing or just flash the image and everything disappears.

pier · Answer

. Not sure about the new series bought this week. So does it initialise and give delaja or how to do it? Some new library maybe?

Anonymous · Answer

Do you have the pin from the display reset connected to the ESP? Code: C / C++Log in, to see the code .

pier · Answer

. This is an I2C display with only four pins, no reset.

Anonymous · Answer

From the examples posted with the library at: Code: C / C++Log in, to see the code .

pier · Answer

. I added, entered -1 as reset and nothing changed.

Marek_Skalski · Answer

New type display: . Display of old type: The main differences are: - the size of the display itself (the new one is smaller) - width of the ribbon connecting the display to the board - the new one is narrower - number of components on the board - the new one has less The old ones start immediately (< 50 ms from power on). The new ones need (in my case) > 400 ms. I bought some of the new ones and thought they were defective. But I was surprised to find that after a reset of the circuit they work without any problem. A while later I figured out that the chip needs more time to start. In tests it came out > 400 ms.

Anonymous · Answer

The problem may also be that the default I2C speed when calling Adafruit_SSD1306 library functions is 400 kHz. I very much doubt that the ESP8266 can handle the calls properly then - there is no I2C hardware controller in the ESP8266. I would suggest calling the constructor with the following parameters:Code: C / C++Log in, to see the code . Or even be tempted to use an even lower speed I2C:Code: C / C++Log in, to see the code

pier · Answer

I have an old-style display. Khoam nothing is achieved by these treatments. After a reset the image shows for a while and disappears....

Anonymous · Answer

. If with the ESP.deepSleep() command at the end of the loop() then I'm not even surprised and I already wrote you about it in another thread.

pier · Answer

. Khoam then where do I place deep.sleep? I put the Blynk initialisation in the setup as you suggested. In general eggs are happening with this display. Wherever I give delay(); for a test, the display is already dead. The rest of the program i.e. BME280, Blynk, Thingspeak are working fine.

Anonymous · Answer

Blynk.run() should be in loop(): ESP.deepSleep() should not be called after every loop() run, but only when you decide to do so and it makes sense. When you return from deep-sleep, the program executes from the beginning, as after a reset.

pier · Answer

Yes Blynk.run() I have in loop(). And now it's like this, when I use the Deep.sleep function the display shows the correct image for a while and that's it, but when I initialise the Blynk the display is completely dead. I don't understand any of this. I don't know how to use ESP.deep.sleep. I read the sensor, display the measurements on the lcd, send to the server and put ESP to sleep why should I spin the loop more times?

Anonymous · Answer

. This is going to be a problem, because Blynk.run() requires this spinning in loop().

pier · Answer

. This will be a problem because Blynk.run() requires this spinning in loop(). Well, not really. Already that two years I have a weather sensor that works according to what I wrote. Now I wanted to make a second one and such eggs I have with this display.

Anonymous · Answer

There is one more thing. In the code you call Wire.begin(D5,D6) because of the pin change for I2C. On the other hand, display.begin(SSD1306_SWITCHCAPVCC, 0x3C) also calls Wire.begin(), but already for the default I2C pins (D1, D2). So try changing this call to:Code: C / C++Log in, to see the code The last parameter (false) means that Wire.begin() will not be called again.

pier · Answer

. I checked for peace of mind but just as I thought it didn't change anything. I repeat the display works if there is no lag, blynk or sleep in the code. For some unknown reason the problem for this display is any delay in the code, just give a delay(); greater than 10 anywhere in the code and already the display is silent. Khoam probably needs to consider that this display is some kind of junk, damaged or has some clone of the SSD1306 driver, give up on it and buy a new one.

Anonymous · Answer

. If you buy a new display and the problem remains, we'll probably come back to the subject.

pier · Answer

And didn't I write you that after uploading this program to another board with another copy of the display everything works as expected. I might be tempted to swap the lcd itself then it will be 100% sure.

Anonymous · Answer

Publish perhaps the latest version of the code with all the fixes I wrote about that is not working properly.

pier · Answer

Code: C / C++Log in, to see the code . Blynk.begin, Blynk.run() and ESP.deep.sleep are commented out because enabling any of them results in the display not working. Added after 8 [hours] 37 [minutes]: I still tried uploading a sample program from the library examples. Of course I changed the SCL SDA pins and what the display does not display anything.

Anonymous · Answer

. Can you check that these pins are connected via resistors to 3V3?

pier · Answer

I connected another copy of the display to this board and it works as expected and blynk and deep.dleep. The conclusion is that these two-colour displays are kind of weird. As it turns out, I'm not the only one who has a problem with this display Link . I also did a trial with adding pullups on the data lines, with no effect.

Anonymous · Answer

When the display is not working, does the message SSD1306 allocation failed appear in the serial port monitor?

pier · Answer

. I'm not likely to see such a message, the question is still what speed do I set the transmission to? But the eggs continue with this display. I've been playing around with the other display for a while, now I've plugged in the faulty one to check that message you wrote about and miracle works with Blynk! In the code I just added the display of one character more. But with sleep it still doesn't work? My hands are falling off. Code: C / C++Log in, to see the code .

Anonymous · Answer

Rather, it should be:Code: C / C++Log in, to see the code .

pier · Answer

. It starts to work and with sleep, although the display does not always get up after deep.sleep. What does this UL give?

Anonymous · Answer

. The fact that the result of the operation will then be a uint64_t, not an int.Code: C / C++Log in, to see the code Added after 13 [minutes]: . And what does this mean specifically? Are you sure the ESP8266 itself is awake?

pier · Answer

. More likely the whole thing is catching a hang because there are no further resets.

[Solved] [Arduino] SSD1306 flashes after adding Deep.sleep/Blynk

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Post #30

Topic summary

define OLED_RESET -1