HUB75 not supporting FM6124 and FM6126A chips

[ondras]

What happened?

My 64x32 HUB75 panel uses the FM6126A driver chip. It currently does not work with WLED. By studying the source code of the WLED/MM fork, I discovered that it is because the chip is not correctly initialized (my panel works with WLED/MM). Apparently, this can be already done in WLED: https://github.com/wled/WLED/blob/main/wled00/bus_manager.cpp#L815

To Reproduce Bug

Connect the Waveshare 64x32 panel.

Expected Behavior

LEDs should turn on.

Install Method

Binary from WLED.me

What version of WLED?

WLED 16.0

Which microcontroller/board are you seeing the problem on?

ESP32-C3

Relevant log/trace output

Anything else?

May I submit a PR that enables this explicit driver assignment, available as another HUB75 panel type? I can add both new options ("new half scan", "new quarter scan") if that is desirable.

Code of Conduct

• I agree to follow this project's Code of Conduct

[softhack007]

This is actually a known limitation - the WLED variant of the HUB75 bus driver currently does not support chipsets that don't work with the standard driver.

The proper solution will be to add a dropdown in LEDs & Harware settings, so users can select the proper chipset driver.

WLED-MM currently uses a simple rule-of-thump: most "outdoor" and 4-scan panels are FM6124 compatible (like FM6126A), while "indoor" 2-scan usually work better with the default driver.

https://github.com/MoonModules/WLED-MM/blob/1f2919e7abf91d045eebb4b8c2499f79f3b94d94/wled00/bus_manager.cpp#L707

Edit: actually we need two driver fields - one for the "shiftregister" chip, and one for the "line" driver chip.

https://github.com/mrcodetastic/ESP32-HUB75-MatrixPanel-DMA/blob/3171232e660e4c2dd43293e8fb2c48e160318032/src/ESP32-HUB75-MatrixPanel-I2S-DMA.h#L232-L253

Edit2: afaik the reason we did not add these yet is that we barely managed to clean to up mess in settings_leds.htm. But we still need a good concept for adding drop-downs for specific led output types.

[netmindz]

That's annoying, it looks like my comment didn't save 😔

Don't have time to write again now, but the short answer is that it is kinda blocked by the need to rewrite the led settings page, but maybe AI can wrangle the code. I do have a draft where I did try and add more settings while trying to add driver and latch settings while trying to test the quarter scan outdoor panels during release testing, but the AI hasn't actually wired up the UI as the settings made zero difference. I've not investigated yet what it's done wrong

[blazoncek]

@ondras see #5617 (comment)

[ondras]

@ondras see #5617 (comment)

Yeah, that is exactly what would work for me.

[softhack007]

we cannot simply port that one over, unfortunately.
But the idea is clear, we need a few extra drop-downs for HUB75.