ESP32 Rover board missing TRI-LED on io2, ROOM board has TRI-LED on pin 48 and should be on pin2 (aka LED_PIN).

[donwade]

According to your earlier response ...
"Freenove_WS2812_Lib_for_ESP32.zip is not designed for ESP32S3. In fact, it is designed for Freenove_ESP32_WROVER_Board. LEDS_PIN is also used for ESP32."

My Freenove-WROVER board has a dumb mono color LED on pin 2, it must be a manufacturing mistake with the pick and place machine. Can you send me a ESP32-ROVER with a TRI-led attached to pin 2?

Alternately, my Freenove-WROOM-S3 board does have a TRI-led on pin 48 (and on your schematic too)
But according to your response the example source code must be correct and therefore should be on LED_PIN (defined as IO2 in the sample code ).

That would make it a manufacturing mistake as I have a dumb mono-color led on IO2. Please update manufacturing to delete the TRI-led on pin 48 and move it on IO2? Oh my ..... moving the TRI-led to IO2 means re-layout of the top level board traces to accommodate the wider foot print.

In the meantime, I will search for my TRI-led on my WROVER board, and redefine your provided WS2812 code to define "LED_PIN" to be 48 on my WROOM board (that shouldn't have a TRI-led.... but it sure is bright :)

Confusing?

.

[Zhentao-Lin]

First of all, my previous reply was not accurate, this library should be designed for Freenove_Ultimate_Starter_Kit_for_ESP32. It is used by LEDPixel in Chapter 6. https://github.com/Freenove/Freenove_Ultimate_Starter_Kit_for_ESP32

Secondly, don't worry about the problem that the library and hardware do not correspond exactly, because you only need to change the pin number in the code simply, you can solve this problem. This library is based on the RMT functionality of the ESP32, which can be mapped to any output pin. The examples in the library are just to make it easier for users to learn how to use it.

Finally, please refer to the tutorial we provide, which corresponds to the sketch as well as the ESP32.

[Zhentao-Lin]

I seem to have given you the wrong impression by keeping Libraries in Kit. Initially, I kept it to make it easier for people to use later. Next I will consider removing these libraries in order to reduce the confusion of subsequent users.