The HT16K33 is a sophisticated LED controller primarily designed to drive 7-segment displays. It can however be used to drive any type of LED.
Key Aspects
Here is what sets the HT16K33 apart from other 7-segment display controllers:
- I2C: You can use the I2C two-wire protocol to control the chip
- 128 LED: You can control up to 128 individual segments/LED which is sufficient for displaying up to 16 digits
- Blinking: Supports built-in LED blinking (on, off, 2Hz, 1Hz, 0.5Hz)
- Key Scan: has built-in key scan support for connecting a keyboard or series of input buttons
In contrast to other controllers such as the MAX7219, this controller does not provide a constant current. It provides the operating voltage at its outputs, and it is up to you to choose the appropriate series resistor to provide the required forward voltage for your LED.
LED Driver
HT16K33 lets you flexibly control the connected LED:
| Item | Description |
|---|---|
| Brightness | digital and analog brightness control |
| Segment Control | individual LED segment control: each LED can be controlled individually |
| Blink Mode | 0.5Hz, 1Hz, 2Hz |
| Digits | Can be set to control between 1 (8 LED) and 16 (128 LED) 7-segment displays. |
Brightness Control
LED brightness can be controlled digitally in 16 steps.
Interface
HT16K33 supports I2C interface (two-wire).
Breakout Boards
Typically, the HT16K33 comes ready-to-use with 7-segment and 14-segment displays but is also available as separate controller board without LED:
Data Sheet
Comments
Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.
Here is how your comments are stored
Whenever you leave a comment, a new github issue is created on your behalf.
-
All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.
-
There is no third-party provider, no disrupting ads, and everything remains transparent inside github.
Github Users Yes, Spammers No
To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant utteranc.es the permission to submit issues on your behalf.
If you don’t have a github account yet, go get yourself one - it’s free and simple.
If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.
Discussions
For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.
(content created Mar 28, 2024)