HUB75 RGB LED matrix library utilizing ESP32 DMA Engine

BUILD | EXAMPLES |

Table of Content

• Introduction
  • Features
  • Supported ESP32
  • Supported Panels
  • Panel driver chips known to be working well
  • Panels Not Supported
  • Update for 16x32 Panels
  • Cool uses of this library
• Getting Started
  • 1. Library Installation
  • 2. Wiring ESP32 with the LED Matrix Panel
  • 3. Run a Test Sketch
• More Information
  • Build-time options
  • Memory constraints
  • Can I use with a larger panel (i.e. 64x64px square panel)?
  • Can I chain panels?
  • Panel Brightness
  • Latch blanking
  • Power, Power and Power!
  • Inspiration
• Thank you!

Introduction

This ESP32 Arduino/IDF library for HUB75 / HUB75E connector type 64x32 RGB LED 1/16 Scan OR 64x64 RGB LED 1/32 Scan LED Matrix Panel, utilities the DMA functionality provided by the ESP32's I2S 'LCD Mode'.

Features

• Low CPU overhead - once initialized pixel data is pumped to the matrix inputs via DMA engine directly from memory
• Fast - updating pixel data involves only bit-wise logic over DMA buffer memory, no pins manipulation or blocking IO
• Full screen BCM - library utilizes binary-code modulation to render pixel color depth / brightness over the entire matrix
• Variable color depth - up to TrueColor 24 bits output is possible depending on matrix size/refresh rate required
• CIE 1931 luminance correction (aka natural LED dimming)
• Adafruit GFX API - library could be build with AdafruitGFX, simplified GFX or without GFX API at all

If you wanna ask "...OK, OK, than what's the price for those features?" I'll tell you - "memory, you pay it all by precious MCU's memory for DMA buffer".

ESP32 Supported

Espressif have kept the 'ESP32' name for all their chips for brand recognition, but their new variant MCU's are different to the ESP32 this library was built for.

This library supports the original ESP32. That being the ESP-WROOM-32 module with ESP32‑D0WDQ6 chip from 2017. This MCU has 520kB of SRAM which is much more than all the recent 'reboots' of the ESP32 such as the S2, S3, C3 etc. If you want to use this library, use with an original ESP32 as it has the most SRAM for DMA.

Support also exists for the ESP32-S2.

ESP32-S3 is currently not supported (as of August 2022), but @mrfaptastic is working on this.

RISC-V ESP32's (like the C3) are not, and will never be supported as they do not have parallel DMA output required for this library.

Panels Supported

• 64x32 (width x height) pixel 1/16 Scan LED Matrix 'Indoor' Panel, such as this typical RGB panel available for purchase.
• 64x64 pixel 1/32 Scan LED Matrix 'Indoor' Panel.
• 32x16 pixel 1/4 Scan LED Matrix 'Indoor' Panel using an ingenious workaround as demonstrated in the 32x16_1_4_ScanPanel example.
• 126x64 SM5266P 1/32 Scan Panel

Ones interested in internals of such matrices could find this article useful.

Due to the high-speed optimized nature of this library, only specific panels are supported. Please do not raise issues with respect to panels not supported on the list below.

Panel driver chips known to be working well

• ICND2012
• RUC7258
• FM6126A AKA ICN2038S, FM6124 (Refer to PatternPlasma example on how to use.)
• SM5266P

Panels Not Supported

• 1/8 Scan LED Matrix Panels are not supported.
• RUL5358 / SHIFTREG_ABC_BIN_DE based panels are not supported.
• Any other panel not listed above.

Please use an alternative library if you bought one of these.

Update for 16x32 Panels

• There is a virtual panel class available to work with 16x32 panels (see: examples/16x32 Panel. This Panel includes drawing lines and rectangles, text and scrolling text

Cool uses of this library

There are a number of great looking LED graphical display projects which leverage this library, these include:

• 128x64 Morph Clock
• FFT Audio Visualisation
• Clock, GIF Animator and Audio Visualiser
• Aurora Audio Visualiser
• Big Visualisation
• Clockwise

Getting Started

1. Library Installation

• Dependency: You will need to install Adafruit_GFX from the "Library > Manage Libraries" menu.
• Download and unzip this repository into your Arduino/libraries folder (or better still, use the Arduino 'add library from .zip' option.
• Library also tested to work fine with PlatformIO, install into your PlatformIO projects' lib/ folder as appropriate. Or just add it into platformio.ini lib_depth section.

2. Wiring ESP32 with the LED Matrix Panel

By default the pin mapping is as follows (defaults defined in ESP32-HUB75-MatrixPanel-I2S-DMA.h).

HUB 75 PANEL         ESP 32 PIN
+----------+
|  R1  G1  |    R1  -> IO25    G1 -> IO26
|  B1  GND |    B1  -> IO27
|  R2  G2  |    R2  -> IO14    G2 -> IO12
|  B2  E   |    B2  -> IO13     E -> N/A (required for 1/32 scan panels, like 64x64. Any available pin would do, i.e. IO32 )
|   A  B   |    A   -> IO23     B -> IO19
|   C  D   |    C   -> IO05     D -> IO17
| CLK  LAT |    CLK -> IO16   LAT -> IO 4
|  OE  GND |    OE  -> IO15   GND -> ESP32 GND
+----------+

However, if you want to change this, simply provide the wanted pin mapping as part of the class initialization structure. For example, in your sketch have something like the following:

// Change these to whatever suits
#define R1_PIN 25
#define G1_PIN 26
#define B1_PIN 27
#define R2_PIN 14
#define G2_PIN 12
#define B2_PIN 13
#define A_PIN 23
#define B_PIN 19
#define C_PIN 5
#define D_PIN 17
#define E_PIN -1 // required for 1/32 scan panels, like 64x64. Any available pin would do, i.e. IO32
#define LAT_PIN 4
#define OE_PIN 15
#define CLK_PIN 16

HUB75_I2S_CFG::i2s_pins _pins={R1_PIN, G1_PIN, B1_PIN, R2_PIN, G2_PIN, B2_PIN, A_PIN, B_PIN, C_PIN, D_PIN, E_PIN, LAT_PIN, OE_PIN, CLK_PIN};
HUB75_I2S_CFG mxconfig(
	64, // Module width
	32, // Module height
	2, // chain length
	_pins, // pin mapping
);
dma_display = new MatrixPanel_I2S_DMA(mxconfig);

Various people have created PCBs for which one can simply connect an ESP32 to a PCB, and then the PCB to the HUB75 connector, such as:

• Brian Lough's ESP32 I2S Matrix Shield
• Charles Hallard's WeMos Matrix Shield
• Bogdan Sass's Morph Clock Shield

Please contact or order these products from the respective authors.

3. Run a Test Sketch

Below is a bare minimum sketch to draw a single white dot in the top left. You must call begin() before you call ANY pixel-drawing (fonts, lines, colours etc.) function of the MatrixPanel_I2S_DMA class.

Once this is working, refer to the PIO Test Patterns example. This sketch draws simple colors/lines/gradients over the entire matrix and it could help to troubleshoot various issues with ghosting, flickering, etc...

Note: Requires the use of PlatformIO, which you should probably use if you aren't already.

More Information

Build-time options

Although Arduino IDE does not seem to offer any way of specifying compile-time options for external libs there are other IDE's (like PlatformIO/Eclipse) that could use that. Check Build Options document for reference.

Memory constraints

If you are going to use large/combined panels make sure to check for memory constraints.

NOTE: You cannot use PSRAM to expand the amount of memory available to use by this library. ESP32 hardware only allows DMA transfer from internal SRAM, so you will be limited to the 200KB or so of usable SRAM of the ESP32 regardless of how many megabytes of PSRAM you may have connected.

Can I use with a larger panel (i.e. 64x64px square panel)?

If you want to use with a 64x64 pixel panel (typically a HUB75E panel) you MUST configure a valid E_PIN to your ESP32 and connect it to the E pin of the HUB75 panel! Hence the 'E' in 'HUB75E'

Can I chain panels?

Yes!

Horizontal

For example: If you want to chain two of these horizontally to make a 128x32 panel you can do so by connecting the panels in series using the HUB75 ribbon cable. Than you must provide proper configuration structure to the class constructor letting it know that you use "one long virtual matrix chain". Refer to Pattern Plasma example for all the details about configuration setup.

Finally, if you wanted to chain 4 x (64x32px) panels to make 128x64px display (essentially a 2x2 grid of 64x32 LED Matrix modules), a little more magic will be required. Refer to the Chained Panels example.

Resolutions beyond 128x64 are more likely to result in crashes due to memory constraints etc. You are on your own after this point - PLEASE do not raise issues about this, the library can't magically defeat the SRAM memory constraints of the ESP32.

Panel Brightness

By default you should not need to change / set the brightness setting as the default value (16) is sufficient for most purposes. Brightness can be changed by calling setPanelBrightness(int XX) or setBrightness8(uint8_t XX).

The value to pass setPanelBrightness() must be less than MATRIX_CHAIN_WIDTH in pixels. For example for a single 64x32 LED Matrix Module, a value must be less than 64. For 3 modules 64x32 it must be less than 192. However, if you set the brightness too high, you may experience ghosting.

Also you may use method setBrightness8(x), where x is a uint8_t value between 0-255. Library will recalculate required brightness level depending on matrix width (mostly useful with FastLED-based sketches).

Example:

void setup() {
Serial.begin(115200);
	dma_display->begin(); // setup the LED matrix
    dma_display->setBrightness8(90); //0-255
    dma_display->clearScreen();	
}

Summary: setPanelBrightness(xx) value can be any number from 0 (display off) to MATRIX_WIDTH-1. So if you are chaining multiple 64x32 panels, then this value may actually be > 64 (or you will have a dim display). Changing the brightness will have a huge impact on power usage.

Latch blanking

If you are facing issues with image ghosting when pixels has clones with horizontal offset, than you try to change Latch blanking value. Latch blanking controls for how many clock pulses matrix output is disabled via EO signal before/after toggling LAT signal. It hides row bits transitioning and different panels may require longer times for proper operation. Default value is 1 clock before/after LAT row transition. This could be controlled with MatrixPanel_I2S_DMA::setLatBlanking(uint8_t v). v could be between 1 to 4, default is 1, larger values won't give any benefit other than reducing brightness.

An example:

dma_display->setLatBlanking(2);

Power, Power and Power!

Having a good power supply is CRITICAL, and it is highly recommended, for chains of LED Panels to have a 1000-2000uf capacitor soldered to the back of each LED Panel across the GND and VCC pins, otherwise you WILL run into issues with 'flashy' graphics whereby a large amount of LEDs are turned on and off in succession (due to current/power draw peaks and troughs).

• Refer to this guide written for the rpi-rgb-led-matrix library for an explanation.

• Refer to this example issue of what can go wrong with a poor power supply.

• Refer to this comment in regards to certain panels not playing nice with voltages, and a 3.3volt signal that the ESP32 GPIO can only provide.

Inspiration

This project was inspired by:

• 'SmartMatrix': https://github.com/pixelmatix/SmartMatrix/tree/teensylc
• Sprite_TM's demo implementation here: https://www.esp32.com/viewtopic.php?f=17&t=3188

Thank you!

• Brian Lough (youtube link) for providing code contributions, hardware and suggestions
• Vortigont for his game changing code contributions and performance optimisations
• Galaxy Man for donation of 1/16 scan panels to support the implemenation of led matrix panel chaining (virtual display) support
• Pipimaxi for the donation of a ESP32-S2 to enable support for ESP32 S2/S3's to be implemented
• Mark Donners ('The Electronic Engineer' on youtube) for the donation of a 1/8 scan panel to build and test working support of these led matrix panels!
• And lots of others, let me know if I've missed you.