waveshare 1.5inch RGB OLED Display Module 128x128 Pixels 16-bit High Color (65K Colors) with Embedded Controller Communicating via SPI Interface.

Planning to use this display type in a product, so this little board was a great way to breadboard the design without having to make your own PCB. Nice that it has both a pigtail and pin header option for connecting to your project. The colors are not super bright, but they are nicely saturated. Of course the OLED has great black levels because it doesn't use backlighting. There's also no viewing angle limitations like a TFT display. The only complaint is the controller on these displays have no native screen rotation. On the plus side, it does have buffering (single) so no flicker.

UPDATE: See attached photo of parameter mod-menu attached to synthesizer sequencer project that can be found on you tube on channel moeller's workshop. Assembly details are documented there.Hi, this is nice display yes? Ah, but a wang-doodler bad-time to make work... Why yoo ask? Well, I tell you.. listen close, because I'm only going to type this once, okay here goze...There are a lot of pins, and they all have to be hooked to the right ones on your controller of choice, but the real pain comes when you try to compile the code and get errors like "Can't compile for Arduino"... yikes! What do you doo?Well, I tell you, so pay attention! I type only once okay? Look at narrative preceding error in the little black box area of your IDE, the spot you never pay attention to, and read what it says... I agree, it's all nonsense, but you may notice a message like "Multiple libraries exist, IDE chose: blaablaablaa.h" (Probably the GFX library) if this is the case you MUST delete all the other instances of that library and use the LATEST & GREATEST version, by doing this you force the IDE to choose it, if you doo that? Man you be back in BIZZZ... trust me.

In short: stay away unless you have time to burn or are an MCU genious.This board is overly complex and does not work with the latest Arduino IDE with an Arduino Uno. The driver code is buggy, as shown by the 4th parameter to print_String(...) - this is not opinion, this is fact, with the latest Arduino (1.8.12) and Arduino Uno. If another Arduino board should be used for the demo, then the vendor should state this - generic Arduino is is a myth.To assist developers, the vendor should clearly describe what this board is and come clean about the lack of I2C support. This aspect is rather deceptive to buyers. There's lots of chatter and implication about I2C, but no real substance. I cannot search all of the 4MB of the product info (let me repeat, 4MB!).It would be very nice if the vendor could provide a Hello World example, with no other look-what-i-can-do functionality in the code. Developers want to interface the board (to some? MCU) and see HelloWorld work - we all know that pixels can dance, we'll get to that later if HelloWorld works.I am a developer of 30+ years with 5 or so years of MCU experience - mainly AVR, Esp8266 and Esp32. I make the bulk of my living now with Esp32 and Azure, I am not a newbie to MCU's but I am also not an MCU genius.IMO, this board is too convoluted at this time. If you have a day or more of time to burn, have at it. My suggestion is that the vendor create a clean Hello World that (here's the key) actually works - a 2-minute test with the latest Arduino will prove this (don't assume, actually do the test). One should not have to back 20 versions in the Arduino IDE to get a demo to work - just test, test and then test again - quite simple actually. The sloppy pointer casting is not a good sign - C, C++, pick one, but do it right.I have not investigated as to whether this display with work with the Adafruit or U8G2 libraries. I tend to think it will not - but I don't know this to be true. If I discover that this display is supported in those libs, I will update my review - based on the efforts of those libs. If it did work, the vendor would probably promote that, somewhere.I usually like products from this vendor, and I hate to write a review this bad, but this display is not ready for general consumption (perhaps beta testing for those inclined). IMO, there's too much of the "get it in the door, and toss it against the wall and see if it sells", going on here.If I discover, at some point, some improved docs that TRULY have a working example, I will try them, and then update my review. The point of these reviews is to tell people how useful, or how miserable a product is - AS IS (not what it hopes to be one day). In my opinion, this product is not useful to me at this time. For now I'll keep going with the 0.91" and 0.96" popular 1306 displays as I need to produce, not tinker endlessly.Good luck

Customer service was very helpful in getting this working. Part of the problem was the fairly primitive example library provided. I strongly recommend using the Adafruit_SSD1351 library instead. It works perfectly and has several advantages:1) Allows definition of CS, DC, RST pins through constructor, not directly editing the library2) 4x faster due to bit-banging of CS/DC pins rather than digitalWrite()3) Uses progmem for fonts. The WaveShare driver takes up about 1.5k of RAM for fonts, which is a killer on a UNO.4) Properly uses the CS pin, allowing multiple SPI devices. The WaveShare driver never de-asserts CS.

As someone new to the Arduino hobby, I've been able to wire up basic circuits, light LEDs, etc. However, when it came to this display, I was completely lost. I'm an applications developer, so coding is familiar to me, but I just could not find adequate sample code to make this work. I was ready to send it back as defective, as I couldn't get it to respond at all. Luckily I found a tip from someone online to use the Adafruit libraries and suddenly everything worked.The display looks great. Just do yourself a favor and look to Adafruit for libraries and sample code for their 1.5" OLED RGB display to get you started.

Works as intended. No issues with Raspberry PI Pico.

Hooked up to the SPI pins of my raspberry pi zero - thanks to the included cable there is no soldering required at all on the display side. Enabled SPI on the pi, downloaded the waveshare python sample from the waveshare wiki and it worked right away. The display is very bright and clear. For my project all I needed was the small OLED_Driver.py file. It has been running for several days now with no problems at all. It draws about an extra 100mA while on and can be switched on and off from software.

I ordered one and it didn't work. Got a replacement that also doesn't work. there defective.