Shop by category
Shop all componentsSensors & MCUs
Real I²C transfers are 10–20% slower because of clock stretching and library overhead.
UART: bits = bytes × 10 (start + 8 data + stop)I²C: bits = (bytes + 1 address) × 9 + start/stopSPI: bits = bytes × 8Time = bits ÷ clockA full 128×64 SSD1306 OLED frame is 1024 bytes. On I²C at 400 kHz that is (1024 + 1) × 9 + 2 = 9,227 bits, so 23.1 ms: about 43 frames per second at best.
Serial buses have overhead on top of the data: UART adds start and stop bits, and I²C adds an acknowledge bit after every byte plus the address. SPI has almost no overhead and runs much faster.
Use this to decide whether a display or sensor will keep up. If a screen refresh is too slow, raise the I²C clock to 400 kHz or 1 MHz, send only the part of the screen that changed, or switch to an SPI display.
Each byte is 10 bits on UART, so 1000 bits ÷ 9600 ≈ 104 ms.
I²C runs at 100 or 400 kHz and adds an acknowledge bit per byte; SPI often runs at several MHz with no overhead.
1 KB per frame at 400 kHz I²C takes about 23 ms, so about 40 frames per second at best.
UART: bits = bytes × 10 (start + 8 data + stop); I²C: bits = (bytes + 1 address) × 9 + start/stop; SPI: bits = bytes × 8; Time = bits ÷ clock.
A full 128×64 SSD1306 OLED frame is 1024 bytes. On I²C at 400 kHz that is (1024 + 1) × 9 + 2 = 9,227 bits, so 23.1 ms: about 43 frames per second at best.
Geekobot builds that use it include Laser distance meter, Non-contact IR thermometer, Handheld soil moisture meter and Sound level meter. Each has the full parts list, wiring and code.
Results are estimates for design and learning. Check critical designs against the component datasheet. Made by the Geekobot Learning Team. How we write our calculators