ProcirelDriving LCD and OLED Displays with Arduino
Displays turn invisible readings into instruments. The classic 16×2 HD44780 LCD is cheap and sunlight-readable; the 0. 96″ SSD1306 OLED draws crisp graphics on I²C. Choosing and wiring them correctly is a rite of passage.
> At a glance: 7 minute guide · part 8 of 10 in the complete Arduino guide track · includes a worked example and a quick-reference table.
## The character LCD
HD44780-based 16×2 modules run in 4-bit parallel mode (six GPIO) or via an I²C backpack (two wires, address usually 0x27). The LiquidCrystal library handles both. Contrast is a trimpot a blank LCD with backlight on is almost always a contrast setting, not a fault.
| D | i | s | p | l | a | y | | |
| — | — | — | — | — | — | — | — | — |
| B | u | s | | | | | | |
| L | i | b | r | a | r | y | | |
| S | t | r | e | n | g | t | h | s |
| 16×2 LCD (HD44780) | Parallel or I²C backpack | LiquidCrystal | Cheap, sunlight readable | | | | | |
| 0.96″ OLED (SSD1306) | I²C / SPI | Adafruit SSD1306 | Graphics, contrast, 2 wires | | | | | |
| TFT 1.8–2.4″ | SPI | TFT_eSPI / Adafruit ILI9341 | Colour, fast updates | | | | | |
| E-paper | SPI | GxEPD2 | Zero-power persistence | | | | | |
## The SSD1306 OLED
What this means at the bench. 128×64 pixels over I²C (address 0x3C) driven by Adafruit_SSD1306 + GFX libraries. You get pixel graphics, custom fonts and scrolling graphs ideal for sensor dashboards. Budget RAM: a full framebuffer costs 1 KB, tight on an Uno.
## Choosing between them
LCD wins in direct sunlight and freezing temperatures at minimal cost. OLED wins for graphical dashboards, tiny wiring and night visibility. For rapid updates, redraw only changed regions full-frame writes over I²C are visibly slow.
## How to apply this in your build
Work through the sequence below each step assumes the previous one passed. For numbers that need calculating, the linked tools at the end of this guide do the arithmetic instantly.
1. Match the module voltage (5 V LCD vs 3.3 V OLED variants)
2. Wire the bus and set the correct I²C address
3. Run the library example sketch first to verify hardware
4. Only then layer your own layout and update logic
### Worked example
A weather station that refreshed a full OLED every second flickered visibly. Redrawing only the temperature digits each cycle and the graph each minute made updates instantaneous. Run the numbers yourself with the related calculator and the result should agree to within rounding.
> Practical note from the bench. Our instrument builds standardise on the 0. 96″ OLED: two wires, instant readability, and the library handles the fussy initialisation.
## Field mistakes we see again and again
– Blank LCD panic adjusting contrast before checking wiring
– OLED and sensor both fixed at address 0x3C conflict
– Full framebuffer graphics on an Uno alongside a big sketch RAM overflow
## Key takeaways
– The character LCD the foundation of this guide; revisit it if any measurement here surprises you.
– The SSD1306 OLED the foundation of this guide; revisit it if any measurement here surprises you.
– Choosing between them the foundation of this guide; revisit it if any measurement here surprises you.
## Prerequisites and preparation
Before starting: match the module voltage (5 v lcd vs 3. 3 v oled variants) and wire the bus and set the correct i²c address. Keep a calculator to hand every number in the worked example is reproducible. Total time including the bench steps: about 6–7 minutes.
## Who benefits most
Hobbyists meeting this topic for the first time, students who want the version with real numbers instead of abstract symbols. Returning engineers refreshing a corner of the craft. The mistake list alone justifies the visit every entry in it was learned the expensive way.
### Quick reference card
| Aspect | Where to find it in this guide |
| — | — |
| Core theory | The character LCD |
| Application steps | How to apply this in your build |
| Worked numbers | Worked example |
| Failure modes | Field mistakes we see again and again |
## How this fits the complete Arduino guide track
This guide is one stop in the structured learning path. Start from the [complete Arduino guide](/tutorial/arduino-complete-guide) pillar page for the full map, or continue with [I2C versus SPI](/tutorial/arduino-i2c-vs-spi) and [serial communication](/tutorial/arduino-serial-communication).
## Frequently asked questions
Do I need pull-ups for the I²C OLED?
The module carries them; adding another pair in parallel just weakens the value fine unless the bus misbehaves.
Which display drains a battery project least?
E-paper by a wide margin, then LCD with backlight off; OLEDs glow every pixel they light.
Where do I go next?
Back to the [complete Arduino guide](/tutorial/arduino-complete-guide) pillar page it indexes every guide in this track and updates as new ones are published.
## Continue this track
– Building a foundation? The [arduino & microcontrollers complete guide](/tutorial/arduino-complete-guide) maps every step in order.
– Next: [Arduino Interrupts: Respond in Microseconds, Not Loops](/tutorial/arduino-interrupts-explained)
– Next: [Arduino IDE 2 Setup: From Download to First Upload](/tutorial/arduino-ide-setup-guide)
– Next: [ESP32 vs STM32: Choosing Your Next Microcontroller](/tutorial/esp32-vs-stm32-comparison)
– Work the numbers: [LED resistor finder](/tools/led-resistor) · [battery runtime estimator](/tools/battery-life) · [555 timer frequency tool](/tools/timer-555-astable)
## Verification routine
The fastest way to internalise this topic is to change one variable deliberately and predict the result before measuring. Wrong predictions are the curriculum, they show exactly which mental model needs revisiting, and the bench grades honestly.
Component substitution is a legitimate experiment as long as it is deliberate. Swap one part, predict the effect, measure, and record. That single habit converts a parts bin into a teaching lab and makes every future guide in this track faster to absorb.
## Formulas and checks from this guide
Verification checklist for this track. Check pin assignments against the sketch header before wiring, confirm supply polarity twice. Serial-print one variable at a time when debugging. Keep each sketch’s pin map in a comment block so the next build inherits working documentation.
Bookmark this page against your next build in the track. The checklist above is the same one used across 15 guides in this series.
## Notes from the bench
Anything with motors, servos or many LEDs needs external supply with common ground. USB is for logic only.
Uninitialised variables and pins left floating. Set every pinMode and initial state in setup.
## Before you close this tab
A note on power, the silent variable in this track: most “code bugs” on microcontroller benches are supply problems wearing a sketch costume. Measure the 5V rail under load before touching firmware.
Working through The character LCDand The SSD1306 OLED with that habit in mind takes minutes, and it is the difference between reading about this topic and owning it.