Modify code for 64*64 pixel, HUB75E, 1/32 Scan led panels

To be safe, don’t use set panelType to MOD32SCAN when connected to a MOD16 panel. I should probably put a current limiting resistor between the level shifter and the panel on the next rev of the shield, to prevent accidentally burning out that driver if accidentally driving that pin high when connected to ground.

I hooked up a SmartMatrix Shield V4 and Teensy 3.2 to a /16 panel that had the E line grounded, and had it run a sketch with panelType=SMARTMATRIX_HUB75_64ROW_MOD32SCAN for 8 hours. I switched back to a /32 panel after, and the shield was able to drive all the rows, so no critical damage to the driver after 8 hours.

Still probably a good idea not to use MOD32 paneltype on a /16 panel

I just received my matrices from China this week and I couldn’t resist adding one more reply to this thread. I now have a panel that is 256x64 functioning on the teensy. Gif playback is a little slower and I could only do 24 bit color refresh, but it works and looks better than I thought it would.

Now to find a clean way to mount these. :slight_smile:

4 Likes

Looks great! Thanks for posting

Hi all! I am currently working on a project and trying to connect two 64x32 boards (https://www.adafruit.com/product/2277), to form a 64x64 board. Although it says that the scanrate is 1/16, I have tried the FeatureDemo example on one board with SMARTMATRIX_HUB75_64ROW_MOD32SCAN and that worked fine. In the images the boards are next to each other, but I would like to create a square. However, the cables that I am currently using are not long enough for that. :wink:

I am using a Teensy 3.2, with the 5th ADDX connected to pin 15 (PTC0). The others are connected to PTC1, PTC2, PTC3 and PTC4. I do not have a SmartLED shield and I hope that I can make it work without it.

I have changed the code as described above, but when I plug in the second screen, it does some weird things (see image). It copies the first screen to the second and only half of the rows are working. Also the letters are not displayed correctly.

Does anyone know what could be wrong?
Thanks in advance!

Hi, did you modify the SmartMatrix Library code to drive the 5th address pin?

Did you change the width and/or height in featuredemo drive the second panel?

I have made some changes to the code, I will list them underneath.

FEATURES DEMO
First line is commented out, width, height and kPanelType are adjusted.

// #include <SmartLEDShieldV4.h>  // comment out this line for if you're not using SmartLED Shield V4 hardware (this line needs to be before #include <SmartMatrix3.h>)
#include <SmartMatrix3.h> 
#include "colorwheel.c"
#include "gimpbitmap.h"

#define COLOR_DEPTH 24                  // known working: 24, 48 - If the sketch uses type `rgb24` directly, COLOR_DEPTH must be 24
const uint8_t kMatrixWidth = 64;        // known working: 32, 64, 96, 128
const uint8_t kMatrixHeight = 64;       // known working: 16, 32, 48, 64
const uint8_t kRefreshDepth = 36;       // known working: 24, 36, 48
const uint8_t kDmaBufferRows = 4;       // known working: 2-4, use 2 to save memory, more to keep from dropping frames and automatically lowering refresh rate
const uint8_t kPanelType = SMARTMATRIX_HUB75_64ROW_MOD32SCAN; // use SMARTMATRIX_HUB75_16ROW_MOD8SCAN for common 16x32 panels, or use SMARTMATRIX_HUB75_64ROW_MOD32SCAN for common 64x64 panels
const uint8_t kMatrixOptions = (SMARTMATRIX_OPTIONS_NONE);      // see http://docs.pixelmatix.com/SmartMatrix for options
const uint8_t kBackgroundLayerOptions = (SM_BACKGROUND_OPTIONS_NONE);
const uint8_t kScrollingLayerOptions = (SM_SCROLLING_OPTIONS_NONE);
const uint8_t kIndexedLayerOptions = (SM_INDEXED_OPTIONS_NONE);

MatrixHardware_KitV1.h
Added line 4 to define the 5th pin (at PTC0 in Teensy), changed last part of last line: 1 << ADDX_PIN_3 into 1 << ADDX_PIN_4.

#define ADDX_PIN_0  3
#define ADDX_PIN_1  4
#define ADDX_PIN_2  1
#define ADDX_PIN_3  2
#define ADDX_PIN_4  0
#define ADDX_PIN_MASK   ((1 << ADDX_PIN_0) | (1 << ADDX_PIN_1) | (1 << ADDX_PIN_2) | (1 << ADDX_PIN_4))

SmartMatrix_Impl.h
I added this part:
#ifdef ADDX_PIN_4
if (i & 0x10) addressLUT[i].bits_to_set |= (1 << ADDX_PIN_4);
#endif

#ifndef ADDX_UPDATE_ON_DATA_PINS
    int i;
    // fill addressLUT
    for (i = 0; i < matrixRowsPerFrame; i++) {
    // set all bits that are 1 in address
    addressLUT[i].bits_to_set = 0x00;
    if (i & 0x01)
        addressLUT[i].bits_to_set |= (1 << ADDX_PIN_0);
    if (i & 0x02)
        addressLUT[i].bits_to_set |= (1 << ADDX_PIN_1);
    if (i & 0x04)
        addressLUT[i].bits_to_set |= (1 << ADDX_PIN_2);
#ifdef ADDX_PIN_3
    if (i & 0x08)
        addressLUT[i].bits_to_set |= (1 << ADDX_PIN_3);
#endif
#ifdef ADDX_PIN_4  
if (i & 0x10) addressLUT[i].bits_to_set |= (1 << ADDX_PIN_4); 
#endif 
    // set all bits that are clear in address
    addressLUT[i].bits_to_clear = (~addressLUT[i].bits_to_set) & ADDX_PIN_MASK;
}
#endif

I’m having a hard time following everything you changed going from it working to not working.

When it “worked fine” is that after you “changed the code as described above”?

If you remove the second screen, and keep the code the same, does it work better (at least filling the first panel)?

Hi…I have a setup with teensy 3.6+ smartmatrixV4 running a 196x64 display…1/32 refresh rate. Is it possible to add another 196x64 display showing same content simultaneously from the same ribbon cable output from snartmatrix shield ? In short, can one snartmatrix shield can show same content from teensy on two displays side by side ?? Curious to know. Or what could be the best way to do something like that. If some one can share some ideas, highly appreciate. Thanks.

Most likely, you have problems if you directly connect two screens to the same output. The output cables should be as short as possible, and if you want to share the same output with several screens, the total length of the cable increases.

You could do this by adding a buffer with a pair of 74LS245 per screen, to isolate and amplify the signals on each screen.

I already tried this a long time ago and it worked well, in my case it was not to share an output with several screens, but to connect a relatively long cable, I think was about 60cm. Connected directly, the screen worked badly, the signals suffered many interferences, when I added the buffer with a pair of 74LS245 everything was solved.

I agree with @pinballsp, but it’s worth a try at least to see if you can wire up two screens without issues.

@marcmerlin drives two displays on his wearable LED screen setup with nearly identical content by feeding the output of one display into the other. The colors might be a bit off by doing this, but he can’t see the difference, and neither can I in the videos he’s shown this.

Yeah, I can confirm it just works, plug your last panel from the first set of displays into the first panel of the 2nd set.
The 2nd set will be one frame refresh behind, but at 100Hz+, you won’t be able to see it.
Only thing to keep in mind is to re-inject power. On a long run, I also had to re-inject ground to make sure ground was exactly the same on all panels (both across the data plug, which does send ground, but also the power plug)

@Louis Sure, expecting the displays to arrive this week. Will share the results.

Thanks @marcmerlin, @pinballsp for the inputs. Hopefully it will work as you mentioned.

Hey all, Apparently it worked like you all suggested.

I have more displays with me now, all 64x64 chinese ones. Is there a way to add more displays in one chain, like i got it running till 250x64, but iam looking at 5 screens together, which is 320x64. Is there any way i could still play around with teensy+smartshield or something like that to get this size working ??

Thanks a ton for the response. Really appreciate it.

You can go chaining all the panels you want, to get a higher resolution screen, but the performance will get worse.

To improve performance you can compile by applying overclocking. With a teensy 3.6, you can raise the clock frequency to 192, 216 and 240 Mhz.

@pinballsp i tried that with different configurations while compiling. My teensy 3.6+smartmatrix setup is currently running @240Mhz for 192x64 size. But till 250x64, its working out, more than that the displays wont even turn on. I am looking at 320x64 configuration. Also is there a way to reduce the scan rate of 64x64 from 1/32 to 1/16 ? Thanks for the suggestion.

The scan rate is set in hardware on the panel you purchase, it’s not configurable.

250x64 is too many pixels for SmartMatrix Library to handle, I don’t know what the exact limit is, but I believe 128x64 is towards the upper limit with a Teensy 3.6

@karakbot: 128x64 is the limit on teensy 3.6 if you use ABCD panels, and with ABCDE, you can go up to 128x128 but the refresh rate will suffer and you’ll have almost no RAM left for anything else.
ESP32 is similarly limited to 128x64.

@Louis @marcmerlin I was running a custom sketch for few images displayed with an interval. Its running upto 250x64 with teensy without much issues. I am also running a stepper motor sequence in between the image changes. I am playing with hzeller setup now with raspberry pi. Thanks for the help. Will try smartshield again soon.

With ABCDE panels, teensy 3.6 barely supports 128x128. 250x64 is more or less the same amount of pixels, so I can see how it would work too, but you’re likely quite close to the limit.