32x64 1/8 Scan P5 Qiangli Panel Problem

[Endorfin35]

The panel I am using is 32x64 pixels. It is selecting the rows with RUL5158C. It is also using SM16208 for pixels.

When I run the SimpleTestShapes example with DP3246_SM5368 (mxconfig.driver = HUB75_I2S_CFG::DP3246_SM5368;), I get the following image. Although there is a problem with the image, I think the row scanning is correct with DP3246_SM5368.

When I wrote a simple code that scans the R1 channel for testing purposes, I saw that the panel scans 32 pixels from the top row, then scans 32 pixels from the bottom row, then finishes scanning with 32 from the top and 32 from the bottom.

I tried the example with ESP32-VirtualMatrixPanel-I2S-DMA.h, but I could only fill 16 rows of the panel. I am not sure if this is the solution I need to achieve. Any guidance would be very helpful.

[mrcodetastic]

Can you post your code?

[Endorfin35]

This is the code I made to fix the scan.

#include <ESP32-HUB75-MatrixPanel-I2S-DMA.h>
#include "ESP32-VirtualMatrixPanel-I2S-DMA.h" 

#define PANEL_RES_X 64      // Number of pixels wide of each INDIVIDUAL panel module. 
#define PANEL_RES_Y 32     // Number of pixels tall of each INDIVIDUAL panel module.

#define NUM_ROWS 1
#define NUM_COLS 1
 
//MatrixPanel_I2S_DMA dma_display;
MatrixPanel_I2S_DMA *dma_display = nullptr;
// placeholder for the virtual display object
VirtualMatrixPanel  *FourScanPanel = nullptr;




void setup() {

    // Module configuration
    HUB75_I2S_CFG mxconfig(
                PANEL_RES_X*2,              // DO NOT CHANGE THIS
                PANEL_RES_Y/2,              // DO NOT CHANGE THIS
                NUM_ROWS*NUM_COLS           // DO NOT CHANGE THIS
                //,_pins            // Uncomment to enable custom pins
    );

    
    mxconfig.clkphase = false; // Change this if you see pixels showing up shifted wrongly by one column the left or right.
    
    mxconfig.driver   = HUB75_I2S_CFG::DP3246_SM5368;     // in case that we use panels based on FM6126A chip, we can set it here before creating MatrixPanel_I2S_DMA object
  
    // OK, now we can create our matrix object
    dma_display = new MatrixPanel_I2S_DMA(mxconfig);

    dma_display->begin();

    // let's adjust default brightness to about 75%
    dma_display->setBrightness8(96);    // range is 0-255, 0 - 0%, 255 - 100%
 
   
    dma_display->clearScreen();
    delay(500);
    
    // create FourScanPanellay object based on our newly created dma_display object
    FourScanPanel = new VirtualMatrixPanel((*dma_display), NUM_ROWS, NUM_COLS, PANEL_RES_X, PANEL_RES_Y);
    
	// THE IMPORTANT BIT BELOW!
    FourScanPanel->setPhysicalPanelScanRate(FOUR_SCAN_32PX_HIGH);    

}

void loop() 
{

 for (int i = 0; i < PANEL_RES_Y; i++)
  {
    for (int j = 0; j <PANEL_RES_X; j++)
    {
      FourScanPanel->drawPixel(j, i, FourScanPanel->color565(255, 0, 0));
      ESP_LOGI("ELR","Scaning Pixel : x=%d (%d) y=%d (%d)",j,tmp_x,i,tmp_y);
      delay(10);
    }
  }    
  
}

I also tried changes in the FOUR_SCAN_32PX_HIGH section in the ESP32-VirtualMatrixPanel-I2S-DMA.h file. tmp_x and tmp_y are ineffective. Now I remember that this panel is 1/8 scan...

  uint8_t pxbase =32;   // pixel base
        if ((virt_y & 4) == 0)
                {
                    //  coords.x += ((coords.x / pxbase) + 1) * pxbase; // 1st, 3rd 'block' of 8 rows of pixels, offset by panel width in DMA buffer
                    coords.x += (coords.x / pxbase) * pxbase; // 2nd, 4th 'block' of 8 rows of pixels, offset by panel width in DMA buffer
                }
                else
                {
                    //coords.x += (coords.x / pxbase) * pxbase; // 2nd, 4th 'block' of 8 rows of pixels, offset by panel width in DMA buffer
                    coords.x += ((coords.x / pxbase) + 1) * pxbase; // 1st, 3rd 'block' of 8 rows of pixels, offset by panel width in DMA buffer
                }

        //coords.y = (virt_y >> 4) * 4 + (virt_y & 0b00000111);
        coords.y = (virt_y >> 4) * 8 + (virt_y & 0b00000111);

        tmp_x = coords.x;
        tmp_y = coords.y;    

panel view: https://www.youtube.com/watch?v=9QAB1VIkdOQ

[board707]

Please show a clear photo of the panel rearside

[Endorfin35]

[Endorfin35]

The shifht register ic 's are 16 bits. UR_X, UG_X, UB_X is coded for each color. I verify that the panel has 1/8 scan with the calculation of 16x16=256bit.

[Endorfin35]

I made a change. The first 16 lines of the panel work fine. Then it overwrites.

I think a correction needs to be made here.
coords.y = (virt_y >> 8) * 8 + (virt_y & 0b00000111);

[Endorfin35]

I made another change and now I am getting successful results. Is this method suitable? I am planning to chain in the next stage.

  uint8_t pxbase =32;   // pixel base
        if ((virt_y & 8) == 0)
                {
                    coords.x += ((coords.x / pxbase) + 1) * pxbase; // 1st, 3rd 'block' of 8 rows of pixels, offset by panel width in DMA buffer                    

                }
                else
                {
                    coords.x += (coords.x / pxbase) * pxbase; // 2nd, 4th 'block' of 8 rows of pixels, offset by panel width in DMA buffer
                }

        coords.y = (virt_y >> 8) * 8 + (virt_y & 0b00000111);
        if(virt_y>15) coords.y += 8;

[board707]

Is this method suitable? I am planning to chain in the next stage.

    coords.y = (virt_y >> 8) * 8 + (virt_y & 0b00000111);
    if(virt_y>15) coords.y += 8;

I am afraid that the lines above won't works with more than one row of chained panels. But in any case, you need a test

Could you try this one? (instead of yours two above)

 coords.y = (virt_y >> 4) * 8 + (virt_y & 0b00000111);

[Endorfin35]

Bunu deneyebilir misin? (yukarıdaki iki tanesinin yerine)

 coords.y = (virt_y >> 4) * 8 + (virt_y & 0b00000111);

it's worked. Thanks.

[Endorfin35]

When I connect the second panel, there is a ghost shadow problem. I took physical precautions against the shadowing problem (short cable etc.). I tried different parameters. However, I could not solve the problem.

There is no problem with a single panel. When I connect the second panel without making a chain in the code, the same image as the first panel is created on the second panel. In this case, there is no problem with the first panel, but there is a problem with the second panel.

Then, when I make a chain for the second panel in the code, the problem starts to occur on the first panel as well.

[Endorfin35]

Is there a way to too much lower speed the panel for testing purposes?

[board707]

Sorry, I can't help you here.

I'm not an expert in ghostings , I only set up pixel mapping :)

[mrcodetastic]

clkphase setting?

[Endorfin35]

I solved the problem.

I chose DP3246_SM5368 as the driver, it gave me a proper line selection scan, but I don't have these chips on my boards. So I looked into the code a little deeper.

As a result, shiftDriver(m_cfg); in begin() is unnecessary. This does not solve the problem, but it is ineffective for SM16208.

To solve the problem, the lines in ESP32-HUB75-MatrixPanel-I2S-DMA.cpp should be changed as follows. several cycles continue latch signal creates ghosting.

// DP3246 needs the latch high for 3 clock cycles, so start 2 cycles earlier
      if (m_cfg.driver == HUB75_I2S_CFG::DP3246_SM5368) 
      {
        row[ESP32_TX_FIFO_POSITION_ADJUST(fb->rowBits[row_idx]->width - 3)] |= BIT_LAT;   //3 DP3246 needs 3 clock cycle latch 
        row[ESP32_TX_FIFO_POSITION_ADJUST(fb->rowBits[row_idx]->width - 2)] |= BIT_LAT;   //2 DP3246 needs 3 clock cycle latch 
      } // DP3246_SM5368

     if (m_cfg.driver == HUB75_I2S_CFG::DP3246_SM5368) 
      {
        row[ESP32_TX_FIFO_POSITION_ADJUST(fb->rowBits[row_idx]->width - 2)] |= BIT_LAT;   //3 DP3246 needs 3 clock cycle latch 
        row[ESP32_TX_FIFO_POSITION_ADJUST(fb->rowBits[row_idx]->width - 1)] |= BIT_LAT;   //2 DP3246 needs 3 clock cycle latch 
      } // DP3246_SM5368

[mrcodetastic]

Good work. So the library should have an option for the SM16208, using your code?