Diagram and bin file for ESP-WROOM-32 (CH9102X)

[mhackdo18]

Hi I have,
ESP-WROOM-32 (CH9102X) (30 PIN) with SK6812_RGBW_NEUTRAL can I ask a diagram with and without level shifter, its a short throw I successfully use WLED(no level shifter) but I am planing to migrate to Hyperserial with HYPER HDR Proxmox via USB Pass through, can I get a diagram for pin and I have limited background to compiling I want to compile bin and try to change the baudrate to 400 000 as ESP-WROOM-32 (CH9102X) is capable to 4mbs,

I dont if I need to remove all from " default_envs" and just put (default_envs = SK6812_RGBW_NEUTRAL) only Thanks

[awawa-dev]

Hi

Proxmox via USB Pass through

This can be problematic because it's not a serial port operating at the standard 115200 baud rate, but at a much higher speed. It may be a false alarm but some users have reported problems with the Proxmax, but it's possible the issue was with their pass-through configuration. At the moment I don't know what the status is because the conversations always ended on their side without any conclusion. Anyway in worst case scenariuo direct passthrough should resolve a potential issue.

default_envs = SK6812_RGBW_NEUTRAL

yes, you can force to build only this firmware editing this config value. Otherwise it does nothing for the firmware itself.

its a short throw I successfully use WLED(no level shifter)

you can find diagram on the main page and in discussions, if you skip the level shifter its even simplier: for sk6812 using single segment you need to connect only ground & GPIO2 (D2) to the LED strip.

[mhackdo18]

Hi yes I tried It with 200000 abud rate a bit problematic it took time to detect to hyperhdr ill try the baudrate that you recommend, and ill let you know the what is the status

[awawa-dev]

115200 is too slow and ch9102x CDC driver may ignore the commended speed anyway. Use direct pass-through for the esp32 device (not already connected serial device ex. /dev/ttyACM0) like you would pass-through the SSD drive or GFX.

[awawa-dev]

maybe this one? https://pve.proxmox.com/wiki/USB_Devices_in_Virtual_Machines#Simple_Way:_pass_the_USB_device_ID_to_the_guest But I dont use Proxmox so I cannot guarantee that.

[mhackdo18]

Hi as it is in the container and its on privelege everything is already direct access, yes the hyperhdr detect exactly in /dev/ttyACM0 on the same port, I will try to use to compile and use 400000 rate ill let you know the update, on the other hand I sucessfully run without a level shifter on D2 and the distance from the first led is half a meter

[mhackdo18]

Hi I got success on proxmox with 400000 rate, first instead putting hyperhdr into container(which i have success doing it also) I just installed hyperhdr direct to proxmoxOS on debian13, for grabber hyperion android grabber protocol buffer enable

Recompile hyperserial with RGBNW(sk6812) at 400000 using esp32(30pin) CH9102x

Connection/diagram
Esp32(micro usb) to promox(usba 2.0)
Esp32(VIN 5V) to PSU(5V+)
Esp32(GND) to PSU(5V-)
sk6812(5V) to PSU(5v+)
sk6812(GND) to PSU(5v-)
sk6812(GND) to Esp32(gpio2/D2)

Just searching to fine tune the settings using hyperion android grabber,

And I searching if there is blackbar setting

[awawa-dev]

Since I don't use proxmoxOS on a daily basis and its configuration is still unclear to me, could you tell me if you managed to run HyperHDR in a standard container without super permissions? Meaning, just forwarding the USB device by product ID/vector ID? This seems safer to me than exposing the entire machine.