HyperHDR won´t connect to HyperSerial via USB/adalight

[Callahan78]

Hi,
I tried since a few days but I can´t get it working . . .
Have a Raspberry Pi 4b with HyperHDR which is connected to a ESP32 with HyperSerialWLED. Via Wifi everything is running fine (SK6812).
But when I connect via USB there no connection will be established.
I made all the recommended settings in HyperHDR (Baudrate 2000000, AWA protocol enabled ...).
No errors in log.
Any ideas what I could try?
Best regards

[awawa-dev]

Hi
In 99% of cases it turns out that ESP doesn't have 2Mb capable chip onboard (for example cp2104, CH340G ...it's written in the requirements). So first thing you should do is to verify it on your board. One chip should have similar marking. If it's popular cp2102 it won't work as it's only 1Mb capable.
Regards
Awawa

[Callahan78]

OK, I wish I had ask some days earlier . . . it´s a CP2102 Chip. So I will order another.
Will "D1 Mini NodeMcu mit ESP8266-12F WLAN Module CH340G" do the job?

[awawa-dev]

ESP8266 wemos D1 mini CH340G works fine. I use it with my setup. It's a bit a pain to provide a system driver for Windows and older macOS but under Linux it works out of box.

[Callahan78]

Ok, I´ll try . . . . :-)
Thank you very much for the quick answers!

[Callahan78]

Back from holidays and in the meantime my "ESP8266-12F WLAN Module CH340G" has arrived. I flashed it with "WLED_0.13.0-b2_ESP8266.bin".
But same here: works fine via Wifi (type "wled") but not with USB (type "adalight").
Any ideas?

By the way: in Wifi-Mode the ESP´s web interface is not reachable while HyperHDR is accessing it ("Connection to light failed!"). Is that correct? With my former ESP (CP2102 Chip) the web interface stays accessible.

[awawa-dev]

If you flashed it with the official WLED release then you can't use 2MB awa protocol. You can use only 115200 adalight with disabled awa protocol. Make sure that it works first with such settings.

[Callahan78]

Damn . . . I screwed up the links . . . you´re right. Now I flashed with "HyperSerialEsp8266.ino.d1_mini_RGBW_FIRSTLED_ENABLED.bin".
But now there is no WLED-AP to configure the device. I reflashed sometimes without any error, but no WLED-AP after flashing.
Sorry for my stupidness . . . .

[awawa-dev]

You should stay with the official WLED as you've already flashed it first and as I suggested. It's not a normal behavior for ESP device, maybe something is wrong with the flash procedure or in the flash memory itself..sometimes WLED-AP doesn't not appear after an upgrade because it remembers some things and the device www panel IP/address name depends then on the router assignment.

[awawa-dev]

HyperSerialEsp8266.ino.d1_mini_RGBW_FIRSTLED_ENABLED.bin is not a HyperSerialWLED...it doesnt have a WiFi interface anyway ;)

[awawa-dev]

You've probably searched for that: https://github.com/awawa-dev/HyperSerialWLED/releases/tag/v3.0.0.0

[Callahan78]

Ok, now I am completely confused . . . . :-p
Which image should I flash for my purpose (SK6812RGBW > ESP8266-12F >USB> HyperHDR)?

[Callahan78]

Just tested with "nodemcuv2_ESP8266.bin", WLED-AP available, Wifi connect works, USB connect doesn´t

[awawa-dev]

OK, there are two different solution to have 2Mb transmission if you have capable ESP with CH340G:

• HyperSerialEsp8266 with no WiFi interface, fast, pure bridge for awa protocol for ws281x and sk6812 (with a calibration for cold or neutral). It has nothing common with a WLED project.
• HyperSerialWLED, fork of WLED with 2Mb awa protocol implemented.

Just to avoid the confusion because I don't know what are your settings now ...

Please first test your setup with the original WLED 0.13 to verify that everything is working OK.
Set speed to 115200 and disable awa protocol.
If that is working then proceed with the next step.

Flash nodemcuv2_ESP8266.bin from https://github.com/awawa-dev/HyperSerialWLED/releases/tag/v3.0.0.0
Set speed to 2000000 and enable awa protocol.
If it doesn't work please provide full logs from that configuration (upload them on pastebin service).

[Callahan78]

Did you disable power limit in WLED?

Can´t find this option, just "Enable automatic brightness limiter", here I tried both.

At the moment there are no entries in HyperHDR-Log, I will switch to debug level and let it run a while.

You should not give up with your current setup.

That would be my favorite :-)

Maybe HyperHDR logs will shows more or maybe it's an electrical issue (no common ground in fact when connected to Rpi?)
If the WLED is working well over Wifi, the ESP is still connected to the RPi (just to get a power supply)? Should try that for a tes

Yes, I leave everything connected as it is (ESP gets power from Raspberry in both scenarios), I just switch in HyperHDR between Wifi and USB.

[awawa-dev]

Yes, it's a brightness limiter.
You must restart HyperHDR after you changed the log level settings. Frankly I'm out of idea now because adalight in such a simply, basic configuration must work...or at least it should work ;) There is a very slim possibility of conflict with other device over serial port (depending on the system configuration), but it's very rare and difficult situation.

[awawa-dev]

Do you have an opportunity to test it from a HyperHDR running on PC or laptop?

[Callahan78]

Yes, it's a brightness limiter.

Ok, I´ll leave it switched off.

You must restart HyperHDR after you changed the log level settings.

will do

or at least it should work ;)

yes, sounds very easy :)
For me it seemes that the ESP didn´t get the right data over USB (what is working over Wifi) . . . could it be a configuration thing in HypherHDR?

There is a very slim possibility of conflict with other device over serial port

Maybe I could try a Raspberry 3 instead 4 . . . (?)

Do you have an opportunity to test it from a HyperHDR running on PC or laptop?

I have many opportunities :-)
What should I do?

I am out for today, will continue tomorrow . . . thank you VERY much for the great support! 👍

[awawa-dev]

It's hard to provide completely wrong data that can be accepted by the other side because adalight has CRC check for a header (data for led aren't protected though). Before jumping to other possible solution logs are necessary ;)

[Callahan78]

Here are some logs:
HyperHDR_Log.txt

By the way, the colors are not all wrong, some of them seem to be correct.

[awawa-dev]

Logs looks OK and now I know device path /dev/ttyUSB0 which will be useful later. Please reduce LED count to 100 LED. We can handle your 300LED later (it's a overkill for adalight at 115200).
If you set a static color from HyperHDR remote control that part of LED strip is OK?

[Callahan78]

Setting static color from HyperHDR works (even with 300 LEDs), all LEDs same color, no flickering

Reducing to 100 LEDs:
no flickering anymore. So 300 LEDs seems indeed too much :-p
(at the end I will need around 220 for my 55" TV, I guess)

[Callahan78]

device path /dev/ttyUSB0 will change if I choose another USB port?

[awawa-dev]

Device path should remain the same if you switch to other USB port.

I run 270 leds using adalight at 2000000 speed (before switching to HyperSPI) so this is not a problem as you have ch340g now.
Can't exclude completely that one of LED in your LED strip is broken and refuses to work under certain circumstances and all the segment behind is affected....personally had that experience multiple times with one of my SK6812 cold white and I needed to repair it. But that can wait.

Now as you have a working setup for the 100 LEDs try to flash nodemcuv2_ESP8266.bin from https://github.com/awawa-dev/HyperSerialWLED/releases/tag/v3.0.0.0
Set speed 2000000 and enable AWA protocol. We want to see that 100 LEDs working again but at higher speed.

[Callahan78]

What happens without HDR tone mapping? Could no see a difference on the first look.
So I should try to get an Ezcap 320 and replace my WisFox . . .

[awawa-dev]

Without HDR tone mapping it's pure video stream recorder by the grabber, without any software tuning.

You grabber is receiving SDR signal, no HDR. Alone it's not a problem, every grabber should handle SDR. But the question is why that happens and if your TV is receiving HDR signal (that's the main goal, you probably want best video quality after all). The problem could be:

• in the player/video source: it doesn't produce HDR but the SDR
• the HDMI splitter (or the grabber with a loop, dont know exactly your grabber model and video setup) on the way that signals no support for HDR...so the player fallback to SDR
• your TV doesn't support HDR and so the player fallbacks to SDR

[Callahan78]

My setup:

Sources:
VU+ 4k Duo Cable Receiver (1080p/4k)
NVIDIA Shield TV Pro (4k, HDR, Dolby Vision)
other non important devices

via HDMI to:

Denon AVRX1300W AV Receiver

via HDMI to:

FeinTech VSP01222 Splitter

via HDMI 1 to LG OLED 55CX8LB TV
via HDMI 2 to Grabber and RPi ....

Playing HDR-Content from NVIDIA Shield TV is no problem. TV displays that it is HDR. Ambilight seemes to be ok, too.
Except Dolby Vision, no problem for TV, but no Ambilight (as discussed).

[awawa-dev]

FeinTech VSP01222 can't do HDR to SDR tone mapping. Denon AVR perhaps, but then TV and the grabber would receive the same SDR signal. But if you are sure that TV is receiving HDR signal, you should not worry about your grabber with the SDR: just disable HDR tone mapping in HyperHDR and it will be fine.

[Callahan78]

This confuses me a bit, but I just can say that TV shows a message, when I start a HDR movie and everything looks good:

(same with Dolby Vision).
So I can keep my grabber? :-)