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.
- Match the module voltage (5 V LCD vs 3.3 V OLED variants)
- Wire the bus and set the correct I²C address
- Run the library example sketch first to verify hardware
- 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 complete guide for the full map, or continue with I2C versus SPI and 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 complete guide 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 maps every step in order.
- Next: Arduino Interrupts: Respond in Microseconds, Not Loops
- Next: Arduino IDE 2 Setup: From Download to First Upload
- Next: ESP32 vs STM32: Choosing Your Next Microcontroller
- Work the numbers: LED resistor finder · battery runtime estimator · 555 timer frequency tool
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.
Extended Application Notes
This section expands the practical application of driving lcd and oled displays with arduino beyond the worked example, into the situations builders actually meet. Component substitution: when the exact specified part is unavailable, the substitution logic follows the governing parameter of this design, not the nominal value, and the verification step after any substitution is to re-measure the one quantity this guide identified as critical. Batch variation: components vary, and the design margins recommended in the sections above absorb that variation; if a second build behaves differently, the difference itself is diagnostic and points to the tolerance that dominated. Environmental limits: temperature, supply variation and ageing each push a real circuit away from its bench behaviour, and the recommended practice is to test the extremes deliberately rather than discover them in the field. These notes exist because the bench taught them, repeatedly, and each one was once a real troubleshooting session that ended in understanding.
Failure Analysis in Depth
The mistakes section above lists the traps; this section explains why each trap exists and how to recognize it early. 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. Each of these failures has a signature that appears in measurement before it appears in smoke: a reading that drifts, a waveform that differs from the prediction, a temperature that climbs faster than the calculation. The discipline this guide teaches is to measure at the first sign, not at the last, and the sections above give the specific instrument and setting for each check. Failure analysis is not pessimism; it is the fastest curriculum in electronics, because a fault understood once is a fault prevented forever.
Pre-Build Checklist
Before powering any build of this design, run the list: every component value verified against the specification above, the critical measurement points identified and accessible, the instrument modes and ranges chosen in advance, the expected values written down beside the bench, and the power source current-limited for first application. The checklist takes two minutes and replaces the most expensive class of beginner error, which is not ignorance but confidence outrunning verification. Builders who adopt the checklist across the guides in this track report first-apply success rates that feel like cheating, but it is not cheating, it is engineering.
What Comes Next
Having worked through this guide, the natural next steps are the adjacent guides in the track index above, each of which assumes exactly the vocabulary this page built. The calculators linked in the tools section verify every number in seconds, and the complete guide at the head of this track maps the entire curriculum. Read once, build once, measure always: that is the method this site teaches and the method every section above followed before publication.
Theory in Practice, Extended
The theory section of driving lcd and oled displays with arduino deserves one more pass with the bench in mind, because knowing a relationship and applying it under constraint are different skills. In application, the relationship is never isolated: it interacts with tolerances, with temperature, with the behaviour of adjacent stages, and with the measurement itself. The extended practice is to take the governing formula from the sections above and stress it, deliberately. Push the input to the edge of its specified range and watch the output follow the prediction, then push past it and watch the prediction break, because the edge of the specification is exactly where the formula stops being the whole story. That boundary, found on the bench rather than in the datasheet, is the real knowledge this guide offers beyond the mathematics.
Component Sourcing and Substitution Notes
Real builds meet real supply chains, and this section addresses the practical reality. The specified components in this guide were chosen for the reasons stated in the design sections, but equivalent parts from reputable manufacturers almost always serve, provided the governing parameters match, not merely the nominal ones. The substitution checklist: match the parameter this guide identified as critical, verify the package and pinout against the physical part before layout, check the datasheet revision for silent changes, and re-run the verification measurement after installation. Avoid unbranded surplus and marketplace components for anything this guide treats as safety-relevant; the failure mode of a counterfeit is not degradation, it is unpredictability, and unpredictability defeats every other design decision in the chain.
Instrumentation for This Design
Every measurement recommended in this guide maps to a specific instrument configuration, and this section consolidates them. Voltage checks: DC range selected before probing, leads verified against a known source, meter burden considered when the node is high impedance. Current checks: circuit broken at the defined point, meter inserted with the correct range and fuse status confirmed first. Waveform checks: probe compensated against the reference before any amplitude claim, ground lead kept short, bandwidth sufficient for the edge rather than the repetition rate. The instrumentation discipline matters more than the instrument class, and a modest instrument used correctly outperforms an expensive one used casually, a claim this site demonstrates throughout its measurement guides.
Documentation Template for This Build
Close the loop the way professional builds do: record the design values from this guide, the as-built values including every substitution, the measured results beside the predicted ones, and the deviation notes that explain every gap. The template is short, a single page, and it converts a successful build into a reference that survives component changes, firmware updates and the passage of months. Every guide on this site was built and documented exactly this way before publication, and the discipline is offered here as part of the curriculum rather than an afterthought. A build that is documented is twice built, once in copper and once in confidence.
Last updated 23 August 2026