Can the GL-C-618WL use HyperSerial over USB with Hyperk?

[CurtisB123]

Hi, I'm trying to confirm whether the GLEDOPTO GL-C-618WL can be used with HyperSerial over USB.

I have Hyperk installed on the GL-C-618WL and Serial is enabled in Hyperk. The controller has a CH340K USB-UART interface.

My LG webOS TV detects the controller as:

1a86:7522

I've installed the matching ch341 kernel module on the TV, and the controller now appears as:

/dev/ttyUSB0

HyperHDR can successfully open /dev/ttyUSB0 at 2,000,000 baud. I've also configured Adalight with AWA and the HyperSerial options, but the SK6812 RGBW LEDs don't respond.

The normal Hyperk network/Wi-Fi connection works correctly.

My question is: Is the USB-C port on the GL-C-618WL actually supported for HyperSerial with Hyperk, or is the USB-C port only intended for firmware/programming on this particular controller?

If USB HyperSerial is supported, is there a specific Hyperk firmware/build or configuration required for the GL-C-618WL?

Thanks!

[awawa-dev]

Hi,
Technically & practically, it works. It's capable of a 2M baud rate and the USB-C port seems to be isolated. But take a look at the Gledopto controller case - I believe there is a warning to disconnect the LEDs before connecting it to a PC. I suspect it would try to power them from the USB port if the main LED power supply is powered down for some reason.

[CurtisB123]

Thank you!

I am powering the GL-C-618WL from its normal DC supply, with USB-C connected to the TV. I also tried with the LEDs disconnected and get the same result.

I noticed the case warning says “Type-C Power: 5V 3A Max (USB wall adapter, not PC USB)”. Is that the warning you mean?

The TV now detects the CH341 as "/dev/ttyUSB0", HyperHDR opens it at 2M baud, and Serial is enabled in HyperK, but the lights don't respond.

Is there anything else I need to enable in HyperK for HyperSerial to work, or could it just be the adapter?

[awawa-dev]

I noticed the case warning says “Type-C Power: 5V 3A Max (USB wall adapter, not PC USB)”. Is that the warning you mean?

No, it's on the long small side of the controller. At least it's on 616WL which almost identical (with only 2 outputs).

[awawa-dev]

If you connect the power supply directly to the LED strip instead of through the Gledopto, it should be fine. The Gledopto would then be powered via USB-C, with HyperSerial working properly. From the Gledopto, you just need to connect the data wire and a ground wire to the LEDs to provide a common ground.

[CurtisB123]

Yep, I'd include the warning from the case too, since that's relevant to what Awawa was talking about.

Hi, I think we found the issue.

The TV detects the controller as USB 1a86:7522, but webOS isn't creating a serial device.

My kernel is 4.4.84-229.kcl4tv.5.

modinfo ch341 returns Module ch341 not found, and there is no ch341 module under /lib/modules.

The case also has a warning saying: “Before connecting to PC USB, remove all LED output wires for safety.” I've followed this and currently have only USB-C connected.

Is this simply because the LG webOS kernel doesn't include the CH341/CH340 USB serial driver? If so, is there any way around this on webOS?

[awawa-dev]

You must check logs if HyperHDR detects the board - does it have correct vid/pid (system devices usually have 0, ch340g should have different but it depends on the webos version...could be also 0)? In stats you will find the information (FPS) if the board is receiving frames from PC. Does the static color work fines (Hyperk effect without PC) and LEDs are active?

[CurtisB123]

Hi Awawa,

Thanks. I’ve checked the latest HyperHDR log.

The board is detected as /dev/ttyUSB0 with VID 0x1a86 and PID 0x7522, and HyperHDR is able to open it at 2 Mbps.

However, it then eventually reports:

Timeout after 1000ms: 0 frames already dropped

followed by:

Rs232 SerialPortError: Input/output error

I’ve also tested the Hyperk itself. The LEDs work correctly from the Hyperk web interface, and I can set a static colour, currently red.

HyperHDR is receiving/processsing the video at ~60 FPS, but the LEDs don't react to the video.

I also tried the Hyperk network driver. HyperHDR can reach the Hyperk at 10.69.0.63 and gets HTTP 200 responses, but Hyperk discovery in HyperHDR returns no devices.

So it looks like the Hyperk hardware/LED output is working, but we're having an issue getting the live frames from HyperHDR to the board.

What would you recommend checking next? Is there a specific log or test that would confirm whether Hyperk is actually receiving the frames from HyperHDR?

[awawa-dev]

Did you set HyperHDR as instructed in the 0.0.5 Hyperk release note for HyperSerial?

[CurtisB123]

Yes, that's the release note I'm following. Hyperk has HyperSerial enabled, and in HyperHDR I'm using the Adalight driver with:

AWA high-speed serial enabled
/dev/ttyUSB0
2,000,000 baud
ESP/HyperSerial handshake enabled
Force HyperSerial detection enabled

The latest log confirms all of these settings. However, HyperHDR reports:

Could not detect HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico device

It can open /dev/ttyUSB0, and the board is detected as VID 1a86, PID 7522, but after running for a while it eventually reports:

Timeout after 1000ms

followed by:
Rs232 SerialPortError: Input/output error

Hyperk itself works and the LEDs respond to static colour commands from hyperk.local.

So it seems the USB serial device is detected, but HyperSerial handshake/data communication isn't completing

[awawa-dev]

Does Hyperk reset itself when you start HyperSerial connection? You can try lower speed both in Hyperk and HyperHDR