0.96" 128x64 OLED Display Module - Blue Pixels, I2C 4-Pin, SSD1306

Specifications

• Display Technology: OLED (Organic Light-Emitting Diode)

• Resolution: 128 x 64 pixels

• Pixel Color: Monochromatic Blue

• Driver IC: SSD1306 (0.96" variants) / SH1106 (1.3" variants)

• Communication Interface: I2C (Inter-Integrated Circuit)

• Pin Count: 4 Pins (VCC, GND, SCL, SDA)

• Operating Voltage: 3.3V to 5V DC

• Logic Voltage: 3.3V to 5V Tolerant

• Viewing Angle: > 160 Degrees

• Default I2C Address: 0x3C (or 0x3D)

Key Applications and Projects

• Wearable Smartwatches: Acting as the primary, low-power display for custom ESP32-based fitness trackers.

• Environmental Dashboards: Rendering real-time temperature, humidity, and barometric pressure data from a BME280 sensor into clean, readable fonts.

• Menu Systems: Combining the display with a rotary encoder to create a deeply nested configuration menu for custom CNC controllers or 3D printers.

Unlock New Capabilities (Project Evolution) The Live Network Monitor: LEDs are great for basic status indicators, but they can't tell you why a system is failing. Evolve your IoT nodes! Connect this OLED to an ESP8266 or ESP32. Instead of just trying to ping your home router, program the ESP to continuously draw a real-time graph of your Wi-Fi signal strength (RSSI) on the OLED. You have just built a portable, battery-powered network diagnostic tool to map out Wi-Fi dead zones in your house!

Downloads:

• SSD1306 Controller _Datasheet
• Libraries

Package Includes:

• 1 x 128x64 OLED Blue Display Module (4-Pin I2C)

FREQUENTLY ASKED QUESTIONS (FAQ)

1. Is this an SPI or I2C display? Despite the product title containing both acronyms, a module with exactly 4 pins labeled VCC, GND, SCL, and SDA is exclusively an I2C display. SPI variants of this screen feature 6 or 7 pins (adding MOSI, CS, DC, and RES).

2. Does it need a backlight? No. OLED technology is self-illuminating. Each individual pixel produces its own light, eliminating the need for a separate backlight component.

3. What voltage does it require? The module contains an onboard voltage regulator, allowing it to be safely powered by either 3.3V or 5V DC supplies.

4. Can I use this with a 5V Arduino Uno? Yes. You can connect VCC to the Arduino's 5V pin, and the I2C logic lines are generally 5V tolerant on these modules, allowing direct connection to the A4 (SDA) and A5 (SCL) pins.

5. Can I use this with a 3.3V ESP32 or Raspberry Pi? Absolutely. It runs natively and highly efficiently on 3.3V logic.

6. What are the SCL and SDA pins? SCL stands for Serial Clock, and SDA stands for Serial Data. These are the two communication lines required for the I2C protocol.

7. What is the default I2C address? The default I2C address for the majority of these SSD1306 modules is 0x3C. Occasionally, they may ship with address 0x3D. You can run an "I2C Scanner" sketch on your Arduino to verify.

8. How do I change the I2C address? If you look at the back of the PCB, there is often a tiny solder jumper. By moving the solder blob from the 0x78 position to the 0x7A position, it shifts the address from 0x3C to 0x3D, allowing you to run two screens on the exact same microcontroller.

9. The image back says 1.30", is it 0.96" or 1.3"? While the listing references 0.96", the PCB photos provided indicate a 1.30" variant. They function almost identically, but a 1.30" screen often uses an SH1106 driver chip instead of the SSD1306. If your screen displays static with the SSD1306 library, switch to the SH1106 library.

10. What color are the pixels? This specific module features single-color Blue pixels against a black background.

11. Can it display colors other than blue? No. This is a monochromatic display. Every pixel on the screen is physically manufactured as a blue LED. It cannot produce red, green, or full RGB colors.

12. Does it support grayscale or varying brightness? While you cannot independently dim individual pixels (they are strictly ON or OFF), you can adjust the overall contrast/brightness of the entire display simultaneously via software commands in your library.

13. What Arduino library should I use? The Adafruit_SSD1306 library combined with Adafruit_GFX is the industry standard and easiest for beginners. The U8g2 library is also highly recommended for more complex text and font support.

14. What is "screen burn-in" and will it happen here? Because OLEDs are organic LEDs, if you leave the exact same static text on the screen at maximum brightness for thousands of hours, those specific pixels will wear out faster and leave a faint "ghost" image. To prevent this, use a screen saver or turn the display off when not actively viewed.

15. Why is my screen showing random static/snow on startup? This is normal. The RAM inside the display driver wakes up in a random state. Once your microcontroller finishes booting and executes the display.clearDisplay() command in your code, the static will vanish.

16. Does the module draw a lot of power? No, it is incredibly efficient. A fully lit screen draws around 20mA, while a mostly black screen with a few lines of text may draw less than 5mA.

17. Do I need external pull-up resistors on the I2C lines? Usually, no. Most 4-pin OLED modules have tiny 4.7K or 10K pull-up resistors pre-soldered onto the back of the PCB for the SDA and SCL lines.

18. Can I display images or logos on this screen? Yes! You can convert small black-and-white JPEG/PNG images into hexadecimal byte arrays using online "image to CPP" converters, and draw those byte arrays to the screen using your display library.

19. What is the refresh rate? Depending on how fast your microcontroller can push data over the I2C bus (standard 100kHz or fast 400kHz), you can achieve refresh rates fast enough for smooth, fluid animations and basic games (e.g., Flappy Bird clones or Pong).

20. Why did my code compile, but the screen remains completely black? Check three things:

1. Ensure SDA and SCL are wired to the correct pins (they are not interchangeable).

2. Ensure you are initializing the correct I2C address in your code (try 0x3C).

3. Ensure you are calling the display.display() command at the end of your loop; drawing commands only update the buffer in memory until you explicitly command the screen to refresh.