SSD1322 OLED Display and Arduino Nano - Asking for help from A to Z

Other Hardware Displays
21

Hello Olikraus,

I managed to get a refund for the screen by EastRising and ordered a new one, they apologized and promised me the new one will be in 4-wire SPI mode.

I only have to wait for it to arrive now...

22

Hello!
I finally received the new screen in 4-Wire SPI mode this time :slight_smile: .
Thanks a lot for your help, the wiring did work as I can print simples texts on it.

I have still one issue and one need for advice:

The issue: I find the refreshing to be very slow.. I tried your scrolling exemple and the scrolling is very jerky.
Did I use the good constructor?

U8G2_SSD1322_NHD_256X64_1_4W_HW_SPI u8g2(U8G2_R2, 5, 3, 4);

The need for advice:
I would like to print a clock on it, I mean "19:39". I would like the ":" to blink but I don't find how to remove only a small part of the screen. Especially when using .clear() and printing everything again is that jerky.

Thanks a lot for your help so far
Nicolas

23

Hi Nicolas

  1. Do not use .clear(). Just redraw the screen with or without ":".
  2. Your display requires a lot of data transfer, For each refresh you controller needs to calculated and transfer 8KB.
  3. You have a slow 8Bit uC. As I suggested earlier, you could use an MKRZero, which is much faster and would not require the level shifter
  4. If sufficient RAM is there: Use U8G2_SSD1322_NHD_256X64_2_4W_HW_SPI (note: 2 instead of 1). It trades RAM vs speed.

You could also post your code, just to ensure that there are no other bugs/issues in your code.

Oliver

24

Hello Olikraus,

  1. That is what I have been doing but when using a big display of the clock, redrawing "15:18" then "15 18" every second is jerky, you can actually see the refreshing on the screen. (I assume it is due to my slow card?)
    2 & 3. I just ordered a MKR Zero, it still hurt considering the fact that it costed 10x more that the nano clone :stuck_out_tongue:
  2. I had already used that setup (how do you call this line?) but using F instead of 2 wouldn't allow me to compile, too much memory needed.

Will the wiring change on the new board? I mean the 3 random pins are fine, but what about the specific pins SCK, MOSI?

Also, if you could have a look at another problem I got but this time with my code or my screen: Blinking SSD1322 - Displays - Arduino Forum

25

Code look good to me. "F" constructor version might be also possible with MKRZero.
And yes, you need to use special pins also for MKRZero to use HW SPI. Pins are named in the MKRZero documentation.

Oliver