HyperSerialPico for Raspberry Pi Pico (Rp2040) #561

awawa-dev · 2023-05-09T12:34:16Z

awawa-dev
May 9, 2023
Maintainer

I created a new project HyperSerialPico that introduces Adalight AWA HyperHDR protocol for Raspberry Pi Pico (Rp2040) as an alternative to ESP based solutions (HyperSerialEsp8266/ESP32).

What is unique compared to the Esp8266/ESP32/ESP32-S2 boards, Pico thanks to the PIO I/O coprocessor is able to produce a very high quality and precise signal. Which is especially required for the Neopixel sk6812/ws8212b LED strips. The signal from the ESP boards is usually well tolerated by most variants of the Neopixel LED strip, but the emulation of their protocol brings with it various side effects, such as high memory consumption (limitation of the maximum length of the LED strips), slightly drifting I2S data clock (still within LEDs tolerance), IRQ thunderstorm when RMT is used, etc. Preliminary tests of the Pico board together with practical measurements of signal timings allow us to conclude that this board is free of these drawbacks and still it is very cheap: ~$2 for the mini version and $3-4 for the larger version.

The project and firmwares for various LED strips can be found at: https://github.com/awawa-dev/HyperSerialPico Note that the first version of HyperSerialPico was released recently, so it should be treated as a test version: we are still collecting user feedback from various setups. I hope Pico will become the best platform for HyperSerial solution.

Boards with built-in 3.3V to 5V level shifter!

One line output model Pimoroni Plasma Stick 2040 W (link)

Compile with set(OUTPUT_DATA_PIN 15) for data line.
Output is PIXELS connector.

Two lines output model Pimoroni Plasma 2040 (link)

For ws281x/sk6812 led strips:

Compile with set(OUTPUT_DATA_PIN 15) for data line if single LED segment is used.
Output is DA connector.

OR

Compile withset(OUTPUT_DATA_PIN 14) for data line if two LED segments are used.
Output is: CL (first segment) and DA (second segment) connector.

For SPI led strips spi1 interface must be used:

set(OUTPUT_SPI_DATA_PIN 15)  
set(OUTPUT_SPI_CLOCK_PIN 14)  
set(SPI_INTERFACE spi1)

Output is: CL (clock) and DA (data) connector.

Sample of electric results:

sk6812RGBW, logic analyzer set to 400MHz sampling and 4v voltage trigger level

8-lanes output Adafruit Feather RP2040 SCORPIO (link)

Single segment output 0
set(OUTPUT_DATA_PIN 16)

Multi-segment
First segment is using output 0
Second segment is using output 1
set(OUTPUT_DATA_PIN 16)

SPI is using spi0 interface pins: 19(OUTPUT_SPI_DATA_PIN ) and 18(OUTPUT_SPI_CLOCK_PIN ) on output 3 and 2 respectively.

Sample of electric results:

One lane output Adafruit ItsyBitsy RP2040 (link)

Single segment output 5
set(OUTPUT_DATA_PIN 14)

Answered by awawa-dev

Aug 13, 2023

New HyperSerialPico v4.0.0.0

Added direct support for some boards with built-in 3.3V to 5V level shifter: Adafruit Feather RP2040 Scorpio, Adafruit ItsyBitsy RP2040, Pimoroni Plasma 2040 and Pimoroni Plasma Stick 2040 W. You can download ready to upload firmware from the HyperSerialPico release section. Read more: info link and manual link
New workaround option for non-booting devices e.g. old Adafruit revisions: info link
Increase ws2812b timings for better compatibility: info link

⚠️ It turns out that when using bad designed (early revisions of Adafruits boards) or poor quality components, some rp2040s may have problems during startup and may require longer timeout during startup. Use…

View full answer

appleimperio · 2023-05-22T01:17:43Z

appleimperio
May 22, 2023

I installed the firmware verify the os and is mounting the pico the cables are the same as my ESP32 Serial but I only see ESP32, esp8266 handshake no pico at all. HyperHDR v19. What I'm missing?

4 replies

awawa-dev May 22, 2023
Maintainer Author

You need latest HyperHDR v20beta0. The installers can be download from the Github Action tab as usual.

appleimperio May 22, 2023

Thanks

davy932 Dec 9, 2023

Im really struggling to find the v20Beta0 version Anywhere. Could you give further direction

Many thanks

awawa-dev Dec 9, 2023
Maintainer Author

Latest is currently here: https://github.com/awawa-dev/HyperHDR/actions/runs/7153056261

sofakng · 2023-05-22T02:32:20Z

sofakng
May 22, 2023

Does HyperSPI or HyperSerialPico have a big improvement over HyperSerialESP32 (with 2Mbps [CH340]) ?

3 replies

awawa-dev May 22, 2023
Maintainer Author

Features are very similar.

sofakng May 22, 2023

Great, thanks! What about the latency though? I know the features should be the same but I'm wondering if either approach has noticeable better latency (to sync with the video signal).

awawa-dev May 22, 2023
Maintainer Author

Main benefits comes from using multisegments because it improves the slowest part in the chain for ws2812/sk6812: Neopixel data line and doubles it's throughput. Then you can gain few ms using SPI instead of serial port for very large setups. Knowing communication speed and the package size (~3*LEDs number) you can calculate it.

sofakng · 2023-05-23T18:52:19Z

sofakng
May 23, 2023

I'm going to give this a test to see if the latency improves from my current setup (HyperSerialESP32 @ 2 Mbps, 304 LEDs).

I'd also like to use multi-segment (for the lowest latency possible). However, my LEDs are already taped onto the TV.
Can I cut the strip in the middle (to create two segments) and not enable SECOND_SEGMENT_REVERSED? I know I'll need a longer data cable (~2.5 feet) and will also cause a bit of voltage drop.

Does having the LED segments reversed improve latency/performance?

Lastly, can we enable SPI between the Pico (driver) and the RPi (host) for 'ultimate' performance?

3 replies

awawa-dev May 23, 2023
Maintainer Author

You can find the calculation for very similar setup (300leds) and solution for upgrading from single to multi-segment (as you plan to do it) on my blog. latest aricle Note that if you already has a very noticeable lag then the main problem could be in the video source latency, because your setup is not such large.

sofakng May 23, 2023

Thanks as always for the reply.

I'm really not sure what my problem is because the latency is very noticeable. I've tried both LG webOS PicCap and Nvidia Shield w/Hyperion Grabber. (I have an MS2109 USB capture I can try but I think it's probably slower?).

I don't mind upgrading/swapping these components (while troubleshooting) because it should keep decreasing latency anyways.

Is there any benefit to having a reversed multi-segment strip besides the shorter data cable?

awawa-dev May 23, 2023
Maintainer Author

If it's very noticeable, I think updating the LED driver or changing to multi-segment for a rather small setup won't solve the problem, unless you're using a Wi-Fi driver like wled, and the problem is with Wi-Fi quality. Probably the result of using piccap depends on the TV model, e.g. my old LG C9 also had a very noticeable lag when I tested it a year ago. ms2109 USB grabber should be around ~100ms latency if you're using a lowest capture resolution with the highest capture rate. You can measure this with the built-in HyperHDR benchmarking tool. But that is beyond the topic of current thread.

ghost · 2023-05-24T09:28:50Z

ghost
May 24, 2023

Good afternoon dear @awawa-dev

I haven't fully assembled my setup, I soldered my Esp32 (Hyper SPI) and level switch to control the tape.
I saw this new article and was wondering if it's better to use what I currently have or a Pi Pico board?
Perhaps for this board you will create a driver for SPI connection and this will be the best possible solution.

3 replies

awawa-dev May 24, 2023
Maintainer Author

Hi
Your Esp32 is fine, my home setup still uses Esp32 mh-et with HyperSPI uploaded. I plan to support Pico in HyperSPI, but it requires some research how the SPI protocol is implemented for this board in slave mode, e.g. esp8266 and esp32 behave differently and require a different packet size. It also requires a slightly different approach as there is no official support yet for Pico with PlatformIO/arduino (very strange things are going on around this topic) which is used in HyperSPI , not a critical issue as I really liked the Pico SDK/Freertos but it takes some work.

AstaRom May 24, 2023

The fact that it is installed in your home assembly on a permanent basis speaks of its stability and good work.
I recently started creating an example-guide where I described the steps for assembling a Ambilight.
I was also interested in this question.
On one forum, many are interested in the topic of creating a backlight with an image capture via HDMI, but refuse it because of the complexity. In my example, I wanted to show that this is not impossible for a simple user.

ghost May 24, 2023

Your Esp32 is fine, my home setup still uses Esp32 mh-et with HyperSPI uploaded

It's clear. I won't change anything for now.

but refuse it because of the complexity

Yes, for me it was also a difficult process to understand. Of course, you could just buy ready-made kits, but they also had their drawbacks. But I chose a difficult path for myself, I never used a soldering iron and did not know how to solder, now I have learned a little. This will be useful for me. If it wasn't for the help from the @awawa-dev himself and other users in this community, I wouldn't have gotten very far.

awawa-dev · 2023-05-24T12:29:17Z

awawa-dev
May 24, 2023
Maintainer Author

I found and order for testing Rp2040 W board with a built-in level shifter so it's supposed to provide 5V data line for ws281x/sk6812. There is also smaller variant without wifi that supports SPI LEDs. I will try to find out if HyperSerialPico can be adapted (I hope only proper GPIO needs to be changed, from schematic it's GPIO15)

https://shop.pimoroni.com/products/plasma-stick-2040-w?variant=40359072301139

10 replies

awawa-dev May 27, 2023
Maintainer Author

Initial tests went well: they are compatible with HyperSerialPico. Updated first post in thread with details and results.

sofakng May 31, 2023

Great! I've just received mine today. Can I power this board using USB-C and then only connect GND, CL, and DA to the LEDs? (I'm powering my LEDs externally so I won't be using the USB-C (3A max?) to power the LEDs.)

The alternative I believe is connecting 5V, GND, CL, and DA, but then the USB-C cable requires a modification to remove power, right?

awawa-dev May 31, 2023
Maintainer Author

Yes, that's actually the recommended connection: use GND (to make common ground with LED strip ground) and CL/DA/Pixels for LED data output. The Pico +5V should not be used to power the Pico board (using GPIO for power bypasses the protections that are usually present and used when power is supplied via the USB port) and 3A limit is usually too low for the LED strip also.

alienryes Jun 4, 2023

I've used this Pimoroni board too and it works really well. One of the bugs I ran into was the same as @sofakng below, so their advice to downgrade the OS was really helpful. The other weird thing was that I had to change the LED order of my BTF-LIGHTING WS2812B from GRB to RGB. Not sure if this expected behaviour. Previously I was driving direct from the Pi4 PWM with the WS218X driver. Thanks for continuing to make these great tweaks.

awawa-dev Jun 4, 2023
Maintainer Author

Thanks for the feedback. I assume the current Rpi arm64 kernel bug will affect not only rp2040 but also HyperSerialESP32 when esp32-s2 is used. It's probably safer to use a v19 SD image and only update HyperHDR to v20 beta. A typical ws2812b uses the grb order, if the rpi PWM driver doesn't change the order internally, it must be done in the HyperHDR LED render settings. HyperSerialPico uses the correct grb order underneath, so it needs the standard rgb in input: it will change the rgb order for other supported led strips as well if needed.

sofakng · 2023-05-24T20:21:09Z

sofakng
May 24, 2023

Has this been tested for Linux?

I've flashed my Raspberry Pi Pico with the SK6812 cold firmware and when I plug it into my RPi4 it shows the device in the system log:

[  227.479589] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd
[  227.590932] usb 1-1.1: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00
[  227.590950] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  227.590956] usb 1-1.1: Product: Pico
[  227.590961] usb 1-1.1: Manufacturer: Raspberry Pi
[  227.590965] usb 1-1.1: SerialNumber: E66118604B2B7126
[  227.601061] cdc_acm 1-1.1:1.0: ttyACM1: USB ACM device

...but HyperHDR 20. beta doesn't seem to detect it:

2023-05-24T20:21:35.871Z [LEDDEVICE_ADALIGHT] Start LedDevice 'adalight'.
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:171) deviceConfig: [{"awa_mode":true,"colorOrder":"rgb","currentLedCount":304,"espHandshake":true,"hardwareLedCount":null,"maxRetry":0,"output":"ttyACM1","rate":2000000,"refreshTime":0,"type":"adalight","white_channel_calibration":false}]
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:235) RefreshTime updated to 0ms
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:41) DeviceType   : adalight
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:42) LedCount     : 304
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:43) RefreshTime  : 0
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:57) Device name   : ttyACM1
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:58) Auto selection: 0
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:59) Baud rate     : 2000000
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:60) ESP handshake : ON
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:61) Delayed open  : 0
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:62) Retry limit   : 0
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (LedDeviceAdalight.cpp:79) Adalight driver with activated high speeed & data integration check AWA protocol
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (LedDeviceAdalight.cpp:88) Adalight header for 304 leds: Awa 0x01 0x2f 0x7b
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:103) Enable device
2023-05-24T20:21:35.872Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM1
2023-05-24T20:21:35.873Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:216) _rs232Port.open(QIODevice::ReadWrite): ttyACM1, Baud rate [2000000]bps
2023-05-24T20:21:35.913Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:221) portName:          ttyACM1
2023-05-24T20:21:35.914Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:222) systemLocation:    /dev/ttyACM1
2023-05-24T20:21:35.914Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:223) description:       
2023-05-24T20:21:35.914Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:224) manufacturer:      
2023-05-24T20:21:35.914Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:225) productIdentifier: 0x3483
2023-05-24T20:21:35.914Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:226) vendorIdentifier:  0x1106
2023-05-24T20:21:35.914Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:227) serialNumber:      
2023-05-24T20:21:37.220Z [LEDDEVICE_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32 device

18 replies

awawa-dev May 24, 2023
Maintainer Author

Could you test armv6 Raspberry Pi OS?

sofakng May 25, 2023

Yep, that works.

I've installed [Raspberry Pi OS Lite (32-bit)] and your arm6 version [Linux-bullseye-rpi012-armv6l-DEB-installer].

2023-05-25T00:33:48.923Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM0
2023-05-25T00:33:48.923Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:216) _rs232Port.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:221) portName:          ttyACM0
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:222) systemLocation:    /dev/ttyACM0
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:223) description:       Pico
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:224) manufacturer:      Raspberry Pi
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:225) productIdentifier: 0xa
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:226) vendorIdentifier:  0x2e8a
2023-05-25T00:33:48.965Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:227) serialNumber:      E66118604B2B7126

EDIT: The armv7 package also works.

EDIT2: I've installed a fresh copy of [Raspberry Pi OS Lite (64-bit)] and [Linux-bullseye-arm-aarch64-DEB-installer] and it doesn't work. Seems like an arm64 problem?

awawa-dev May 25, 2023
Maintainer Author

@sofakng cannot confirm it. Aarch64 OS is fine at least the version I use in my home system, Rpi4 is also fine. Done a quick test and both types of my rp2040 work good with Raspberry Pi 4 USB3.0 port.

[  432.161655] usb 1-1.1: USB disconnect, device number 9
[  436.735678] usb 1-1.1: new full-speed USB device number 10 using xhci_hcd
[  436.843100] usb 1-1.1: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00
[  436.843119] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  436.843133] usb 1-1.1: Product: Pico
[  436.843146] usb 1-1.1: Manufacturer: Raspberry Pi
[  436.843158] usb 1-1.1: SerialNumber: E660***************
[  436.850735] cdc_acm 1-1.1:1.0: ttyACM1: USB ACM device
pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1a86:55d4 QinHeng Electronics USB Single Serial
Bus 001 Device 010: ID 2e8a:000a Raspberry Pi Pico
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $ udevadm info -n /dev/ttyACM1
P: /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/tty/ttyACM1
N: ttyACM1
L: 0
S: serial/by-id/usb-Raspberry_Pi_Pico_E660D4A0A7385D34-if00
S: serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
E: DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/tty/ttyACM1
E: DEVNAME=/dev/ttyACM1
E: MAJOR=166
E: MINOR=1
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=436898086
E: ID_BUS=usb
E: ID_VENDOR_ID=2e8a
E: ID_MODEL_ID=000a
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
E: ID_PCI_INTERFACE_FROM_DATABASE=XHCI
E: ID_VENDOR_FROM_DATABASE=VIA Technologies, Inc.
E: ID_MODEL_FROM_DATABASE=VL805 USB 3.0 Host Controller
E: ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
E: ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_1_1_0
E: ID_VENDOR=Raspberry_Pi
E: ID_VENDOR_ENC=Raspberry\x20Pi
E: ID_MODEL=Pico
E: ID_MODEL_ENC=Pico
E: ID_REVISION=0100
E: ID_SERIAL=Raspberry_Pi_Pico_E660****************
E: ID_SERIAL_SHORT=E660***************
E: ID_TYPE=generic
E: ID_USB_INTERFACES=:020200:0a0000:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=cdc_acm
E: DEVLINKS=/dev/serial/by-id/usb-Raspberry_Pi_Pico_E660-if00 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:221) portName:          ttyACM1
[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:222) systemLocation:    /dev/ttyACM1
[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:223) description:       Pico
[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:224) manufacturer:      Raspberry Pi
[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:225) productIdentifier: 0xa
[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:226) vendorIdentifier:  0x2e8a
[LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:227) serialNumber:      E660****************

sofakng May 25, 2023

Thanks again for troubleshooting this with me.

What image did you use to flash the SD card? It looks like our kernels are different (and the CPU revision but I doubt that matters)

I used the Raspberry Pi Imager and selected Raspberry Pi OS Lite (64-bit), released 2023-05-03.

EDIT: I've flashed an older Raspberry Pi OS image (from 2023-02-01 that contains kernel 5.15.84 and I can confirm it works. However, the latest image from 2023-05-03 with the newer kernel does not.

awawa-dev May 25, 2023
Maintainer Author

I think you can request an issue to https://github.com/raspberrypi/linux/issues Probably something has gone wrong with Kernel 6.x on Raspberry Pi (e.g. broken internal USB hub driver) because I could not find any breaking changes in the changelog. And it makes their OS release incompatible with both their products: Rpi4 and Raspberry Pi Pico.

sofakng · 2023-05-25T16:52:25Z

sofakng
May 25, 2023

Thanks again and I apologize for so many questions.

I'm now having an issue with the github action to compile HyperSerialPico after modifying the CMakeLists.txt to set SECOND_SEGMENT_INDEX to 146. The github action fails. If I set it back to OFF then it succeeds.

4 replies

awawa-dev May 25, 2023
Maintainer Author

Thanks for noticing. Github Actions are not yet officially fully supported and it is recommended to build the project locally using Visual Studio Code as not all variants have been tested by me when building online. Static variable issue is rather a gray zone, I can compile this without warning using my environment, but I cleaned it up in a recent commit. Please update the fork.

sofakng May 25, 2023

Thanks! It compiles now (on the github action) and also appears to be working in my setup (using multi-segment).

awawa-dev May 25, 2023
Maintainer Author

Great! I thinks there is also possibility for a workaround in HyperHDR for Rpi4 and its USB3.0 hub when aarch64 is used on kernel 6.x, but it would be better if they just fixed it.

sofakng May 25, 2023

Thanks very much for the help! Hopefully they can fix it. I'm not quite sure how to describe the bug but according to the issues list, I see a bunch of USB-related ones anyways.

awawa-dev · 2023-05-31T20:00:26Z

awawa-dev
May 31, 2023
Maintainer Author

I've tested new rp2040 board with built-in level shifter: Adafruit Feather RP2040 SCORPIO

It has 8 LED outputs. On default the 3.3V to 5V level shifter is enabled. On closer look it's cmos type vhct 245:

Seems working fine.

Single segment output 0
set(OUTPUT_DATA_PIN 16)

Multi-segment:
First segment output is 0 connector
Second segment output is 1 connector
set(OUTPUT_DATA_PIN 16)

SPI is using 19(OUTPUT_DATA_PIN ) and 18(OUTPUT_CLOCK_PIN ) on output 3 and 2 respectively.

I plan to release new HyperSerialPico with pre-build firmwares for all three boards with built-in level shifters. Need to finish more tests and add one minor improvement to the project.

6 replies

awawa-dev Oct 23, 2023
Maintainer Author

The colors don't matter because the colors of the cables may change depending on the supplier, what matters is the pinout of the LED strip and Pico... the pinout is described on the HyperSerialPico website, so I don't know if that's exactly where the problem could be, but if you're not sure, make a proper and detailed diagram of how you plan to connect it.

yxtay2324 Oct 30, 2023

I have wired it up but no lights are being shown on my strip. I have hyperHDR20, flashed HyperSerialPico_sk6812Cold.uf2 into my scorpio, can get a livestream from my system video capture. I also tested the strip on a arduino sketchbook with the strandtest adafruit_neopxl8 library, and there are lights. I suspect that the usb cant power enough the entire strip of leds since my strip has 300 LEDs, but I should still see a few light up regardless. Any ideas on what is wrong with my setup?

Also, if I power the led strip and scorpio via an external power supply, how can I feed my system video into hyperHDR/LED driver?

yxtay2324 Oct 30, 2023

nvm i flashed the wrong file... but i would still like to know if i were to power the led strip and scorpio via an external power supply, how can I feed my system video into hyperHDR/LED driver?

awawa-dev Oct 30, 2023
Maintainer Author

There was a very similar topic just a few days ago: #660 Pico usb to the PC/RPi, Pico ground and data line to the LED strip.

yxtay2324 Oct 31, 2023

yes that is the same as my setup now, i was just wondering if i can remotely send data to the scorpio without the usb input from the pc

sofakng · 2023-06-15T15:17:41Z

sofakng
Jun 15, 2023

Is the SECOND_SEGMENT_INDEX zero or one-based?

For example, my set segment has a total of 145 LEDs. Does that mean the SECOND_SEGMENT_INDEX should be set to 146?

5 replies

awawa-dev Jun 15, 2023
Maintainer Author

Zero based. So for 290 LEDs in total set SECOND_SEGMENT_INDEX=145. Then first segment is [0,145) and the second segment is [145,290). [ means the index belongs to the range, ) doesnt belong. for an even number of LEDs, just divide them by 2 (odd number is more complicated).

sofakng Jun 15, 2023

OK - Thanks. I have a total of 304 LEDs. First segment has 145 LEDs and the second segment has 159.

Should I set SECOND_SEGMENT_INDEX=145?

(First segment would be 0-144, second segment would be 145-303 I think?)

awawa-dev Jun 15, 2023
Maintainer Author

I have tested and recommend only segments of equal length. I don't know or test if the combination you propose can work (or even crash HyperSerial). You have the "identify" feature in the LED designer (context menu in v19), so you can test/blink any questionable diode on the border of both segments, whether it is correctly placed and works properly.

sofakng Jun 15, 2023

Ahh OK - Thanks. I'll change my segments to make them have the same number to avoid any issues.

awawa-dev Jun 15, 2023
Maintainer Author

That'll be safer. Although at first glance it should work for segments of different length https://github.com/awawa-dev/HyperSerialPico/blob/3e6b8a4bea6d9eb433c5c8e9e4f0379589134399/include/base.h#L91 and setting each led https://github.com/awawa-dev/HyperSerialPico/blob/3e6b8a4bea6d9eb433c5c8e9e4f0379589134399/include/base.h#L157 as you can see the code depends on whether REVERSing is enabled, but the index should be in the safe range (greater than or equal to zero and less than the maximum length of each segment).

awawa-dev · 2023-06-18T11:48:48Z

awawa-dev
Jun 18, 2023
Maintainer Author

New #583 PR brings a workaround for critical bug in udev module. Already merged.

There is currently a critical bug in the udev module that causes serial devices to be misidentified.
Affects HyperSerial8266/HyperSerialESP32/HyperSerialPico devices especially using Raspberry Pi OS arm64 with kernel 6.
HyperHDR SD v19 images work fine if the system is not updated.
This PR provides a workaround on Rpi4 for 'esp8266/esp32/rp2040 handshake' in the Adalight driver until it is fixed in the upstream.
Automatic device detection will not work, so the correct path for the serial device must be manually selected from the list.
Read more:

0 replies

monpiere · 2023-07-03T05:49:57Z

monpiere
Jul 3, 2023

I was able to get my rpi4 to work with my new adafruit scorpio. but I am only able to get half of my strip working. I am running 2 segments, with second segment reversed. 170 leds total sk6812's. I fork the HyperSerialPico repo and edited CMakeLists.txt (I think I got it right, not sure), but I'm not sure how to recompile it from there. The directions mentions a firmwares folder? I'm not sure how to get it to that point. I assume that once I get it to that point that I just connect the Pico to my computer and copy the file to the RP2 drive, then reconnect it to the rpi4. Is that part correct?

14 replies

awawa-dev Jul 5, 2023
Maintainer Author

@monpiere I took your custom built firmware from here: https://github.com/monpiere/HyperSerialPico/actions/runs/5462078420 (HyperSerialPico_sk6812Cold_rev_multisegment_at_85.uf2), uploaded to it my Adafruit Feather Scorpio board, set total LED number to 170 in HyperHDR , applied the effect (set color to rgb(0,127,255)) and it works as it should. Here is a sample from the logic analyzer capturing output 0 (GPIO16) and 1 (GPIO17) confirming the result:

monpiere Jul 5, 2023

Hey, I have to admit that I'm a moron! Lol I swapped the data lines on 16 and 17, and the 2nd segment lights up, but not the first. I got confused because the wiring at the board looks great. The. I noticed that where my two segments come together at the top, the strips were touching, but just in the middle on the data lines. So it was simply a careless mistake, that could have been much worse! I got that all taken care of and it works great. I'm so sorry for all the trouble and for your time I've wasted! 🤓

phyte22 Apr 28, 2024

hi, I have almost exactly the same setup with the same problem.
I have segment 1 on GPIO-0 and segment 2 on GPIO-1. Unfortunately, only segment 1 lights up.
With a voltage tester I can see current on all three lanes. (GND, DATA, 5V).
Since the connections are already soldered, I would like to ask if there is anything else I can try.

awawa-dev Apr 28, 2024
Maintainer Author

@phyte22 I saw your fork. Do you really have only 80 LEDs configured (two segments of 40 each) in HyperHDR with the second segment connected to GPIO17? What kind of RP2040 board is this? BTW The multimeter usually does not show the current (it's hard because it changes too quickly) or even the average reading from the dataline, you need an oscilloscope.

phyte22 Apr 28, 2024

oh nvm! typical beginner's mistake. I soldered the second segment in the wrong direction...
Now it works! Thanks anyway for the quick help.

awawa-dev · 2023-08-13T12:48:29Z

awawa-dev
Aug 13, 2023
Maintainer Author

New HyperSerialPico v4.0.0.0

Added direct support for some boards with built-in 3.3V to 5V level shifter: Adafruit Feather RP2040 Scorpio, Adafruit ItsyBitsy RP2040, Pimoroni Plasma 2040 and Pimoroni Plasma Stick 2040 W. You can download ready to upload firmware from the HyperSerialPico release section. Read more: info link and manual link
New workaround option for non-booting devices e.g. old Adafruit revisions: info link
Increase ws2812b timings for better compatibility: info link

⚠️ It turns out that when using bad designed (early revisions of Adafruits boards) or poor quality components, some rp2040s may have problems during startup and may require longer timeout during startup. Use the BOOT_WORKAROUND option in CMakeLists.txt when building software for them: symptoms are described here(link) and here(link) ⚠️

0 replies

Val57120 · 2023-11-10T11:15:38Z

Val57120
Nov 10, 2023

Hi everyone, my apologies I'm a beginner when it comes to github or hyperhdr, so pardon my silly questions. I built an HyperHDR setup a while ago and everything went fine but now I want to upgrade it using the RP2040.

My questions are: Will it work with my raspberry pi 3B?
Do I have to compile anything from the default .uf2 file for the feather 2040 Scorpio or are the GPIO pinout the good ones by default? And finally, I'm a noob regarding github and I cannot find HyperHDR v20... Can you indicate me what to do precisely?

Thanks in advance for all the help!

21 replies

Val57120 Nov 13, 2023

Hi, Thanks, I now managed to upgrade to HyperHDR v20beta0, but I cannot see the RP pico type of controller in the controller list... Does it need to be soldered to be detected or something? I assume not, but I'm otherwise clueless about why I can't see it. Thanks again for the help

Val57120 Nov 13, 2023

Never mind, I'm just an idiot; I found your turorial explaining the handshake option etc. I will now finally test the setup! For now thanks again for everything, I'll test my setup and donate as soon as it's done

Val57120 Nov 13, 2023

Okay so extremely stupid question, but I don't wanna fry anything... Which GPIO from the RPI must be used and to which spot d I have to solder it on the RP2040 Scorpio? Thanks already xD

danielbrunt57 Nov 13, 2023

I think the HyperSerialPico connection for SPI to RP2040 board is via USB. It's the HyperSerial solution which uses a jumper wire from rpi SPI pin to ESP32 pin.

awawa-dev Nov 13, 2023
Maintainer Author

Okay so extremely stupid question, but I don't wanna fry anything... Which GPIO from the RPI must be used and to which spot d I have to solder it on the RP2040 Scorpio? Thanks already xD

Why would you want to connect anything from RPi GPIO to Scorpio GPIO? Everything the rp2040 Scoprio needs from the RPI, it receives it via USB (+5V to the power supply board, ground, serial data feed from the RPi to the HyperSerialPico firmware). Take a look at similar solutions and diagrams: #660 (reply in thread)

danielbrunt57 · 2023-11-11T13:51:42Z

danielbrunt57
Nov 11, 2023

I am struggling with my ambilight upgrade from SK6812 + Hyperion on Athom WLED controller to new setup descibed below.
I am only getting 14 LEDS lighting up and they do not change.

I installed Download Pirate brand MicroPython as referenced by the Pimoroni page for Plasma 2040 and could manually control the strip.

I'm using RPI-3B+ with HyperHDR v19.0.0.0

USB video capture is working...

LED hardware:
HD107S (APA107 APA102 Upgrade Version)
Pimoroni Plasma 2040 running:

For some reason, HyperHDR on pi can't access the Plasma 2040: `device 'adalight' signals error: 'Timeout writing data to ttyACM0'`

I've been scratching my head for more than a week now, and of course suffering from Ambient TV Llighting withdrawal!

1 reply

awawa-dev Nov 11, 2023
Maintainer Author

@danielbrunt57
As @AstaRom pointed out: you need HyperHDR v20. An older version like the one you are using does not have the "rp2040 handshake" option available, as you can see in the screenshot provided. And the result is also visible in the logs.

AstaRom · 2023-11-11T14:36:12Z

AstaRom
Nov 11, 2023

I'm using RPI-3B+ with HyperHDR v19.0.0.0

You need to use HyperHDR v20.0.0.0-beta.
The 'Raspberry Pi Pico' controller is only supported in beta versions.

1 reply

AstaRom Nov 11, 2023

davy932 · 2023-12-09T20:23:32Z

davy932
Dec 9, 2023

I'm going to have to wait for the official release. I'm not competent enough find what i need int his. I need a simple Pi Image File to build off. Not to worry Thanks On 9 Dec 2023, at 20:09, Awawa ***@***.***> wrote: Latest is currently here: https://github.com/awawa-dev/HyperHDR/actions/runs/7153056261 — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you commented. Message ID: ***@***.***>

1 reply

awawa-dev Dec 10, 2023
Maintainer Author

If you need v20beta to test Pico you can install LibreElec and HyperHDR v20beta Kodi addon. As for the prepared image of Raspberry Pi OS with HyperHDR, I don't know if the next version will appear at all, because I completely disagree with the direction the OS maintainers have chosen. Anyway currently it is not possible to use these latest images for headless installation without their flasher (removal of wpa_supplicant.conf for wifi configuration with no alternative), which they forcefully promote. I know it can be hacked to enable the functionality that has existed so far, but I don't want to waste time on poor or unfinished concepts in the latest Raspberry Pi Bookworm OS release (and the latest image of Bullseye OS release is buggy with critical udev issue) , because I can spend that time on the new alternative n100 platform.

danielbrunt57 · 2023-12-11T06:02:43Z

danielbrunt57
Dec 11, 2023

I can spend that time on the new alternative n100 platform.

What is "n100 platform"?

1 reply

awawa-dev Dec 11, 2023
Maintainer Author

The Intel n100 single-board computer (mini PC) that was released this year. Some 8GB models are sometimes available on sale for less than $100 (including VAT) on Aliexpress eg. Firebat AK2.

alex-013 · 2023-12-16T01:09:18Z

alex-013
Dec 16, 2023

Hi everyone, after quite some time trying to get my setup to work I can't make it, I would appreciate if anybody have some idea what to try. My setup is: hyperhdr and piccap running on lg webos tv, connected with raspberry pi pico. I've compiled latest version of master branch of hyperhdr and installed on the tv. Overall everything until leds seems to work, i can see live video in the ui etc. Here are some logs:

2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:187) deviceConfig: [{"awa_mode":true,"colorOrder":"rgb","currentLedCount":49,"espHandshake":true,"forceSerialDetection":true,"maxRetry":2,"output":"ttyACM0","rate":2000000,"refreshTime":0,"type":"adalight","white_channel_calibration":false}]
2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:251) RefreshTime updated to 0ms
2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:47) DeviceType   : adalight
2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:48) LedCount     : 49
2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:49) RefreshTime  : 0
2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:64) Device name   : ttyACM0
2023-12-16T01:47:50.556Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:65) Auto selection: 0
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:66) Baud rate     : 2000000
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:67) ESP handshake : ON
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:68) Force ESP/Pico Detection : ON
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:69) Delayed open  : 0
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:70) Retry limit   : 2
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (LedDeviceAdalight.cpp:79) Adalight driver with activated high speeed & data integration check AWA protocol
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (LedDeviceAdalight.cpp:88) Adalight header for 49 leds: Awa 0x00 0x30 0x65
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:88) First enable the device
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:94) Enable the device
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM0
2023-12-16T01:47:50.557Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:227) _rs232Port.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:232) portName:          ttyACM0
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:233) systemLocation:    /dev/ttyACM0
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:234) description:       
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:235) manufacturer:      
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:236) productIdentifier: 0x0
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:237) vendorIdentifier:  0x0
2023-12-16T01:47:50.573Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:238) serialNumber:      
2023-12-16T01:47:50.585Z [LEDDEVICE_ADALIGHT] Force ESP/Pico detection override enabled. HyperHDR skips the reset. State: 1, 1
2023-12-16T01:47:50.589Z [LEDDEVICE_ADALIGHT] DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem1: 0, mem2: 460, heap: 123232  Welcome! Awa driver 9.) at 2 msec
2023-12-16T01:47:50.589Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:349) Switch on
2023-12-16T01:47:50.589Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:425) Power On
2023-12-16T01:47:50.589Z [LEDDEVICE_ADALIGHT] Start LedDevice 'adalight'.
2023-12-16T01:47:50.589Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:160) Flush was successful

note: 2023-12-16T01:47:50.585Z [LEDDEVICE_ADALIGHT] Force ESP/Pico detection override enabled. HyperHDR skips the reset. State: 1, 1
This line is my modification, for some reason webos don't populate productIdentifier and without this change pico wouldn't be detected, here is change

First i tried to drive leds directly from io2 from pico, and it was not working, seems like there were two types of problems:

only first ~10 leds would light up, first ~5 would show correct colour, and rest would show some random or white
whole strip would light up, colours would be correct, but there would be white flashes. Constantly groups of 10-20 leds would flash white.

Then i got SN74HCT125N to use as a level shifter, note it is not one recommended by @awawa-dev because it is hard to get it where i live, and i found online that one i got should work fine. And the problem persisted even after adding level shifter. What i can defiantly say is that now signal is really shifter, i've checked that with oscilloscope (cheap diy dso138, but still it shows raised levels)

All this was tested with 49leds strip. Power supply should be more then enough 100w. Ground of led strip and ground of pico is connected.

Here is a picture of current state:

Thanks for reading!

2 replies

awawa-dev Dec 16, 2023
Maintainer Author

Hi
Usually, if you managed to control the first LED, the signal for the next ones should already be amplified: this does not mean that it will always be stable, but it should not be the case that it always works only for a very small number of LEDs at the beginning. It cannot be ruled out that one of them is damaged (LED 5 or its neighbors?) and requires replacement, but it is better to confirm this by using a regular standard version of HyperHDR, e.g. on a PC with Pico. Unless the Pico board is completely defective, but this requires a logic analyzer to confirm. +5V from the LED power supply is connected only to the SN74HCT125N target input and ground is also connected for both (LED power supply and Pico)?

As for productIdentifier: 0x0, vendorIdentifier: 0x0 indicates incorrect system operation and it affects not only our software. Have you checked the version of udev you have in WebOS, as it may be the unfortunate bug that has affected many distributions based on Debian and others? I don't plan any workarounds on my end here: this should be fixed in OS or udev. It's a bit of pity that you didn't respond earlier, because you didn't have to make changes and compile your own version in this case: just use the standard v19/v20beta with the classic version of the HyperSerialPico firmware (and disabling the AWA protocol in HyperHDR, it is described on the HyperSerialPico website). The classic version ignores productId and vendorId, this should be enough until it is fixed in the system.

awawa-dev Jan 15, 2024
Maintainer Author

I thought about it. It seems that the problem with udev/systemd is bigger, because for a while it also appeared in higher 252 before it was fixed, but it was enough and this bug seems to be circulating everywhere. I will include this patch in PR, if the user wants, let him force detection of the serial port. Thank you.

1943f28

jingato · 2024-01-03T06:08:38Z

jingato
Jan 3, 2024

Hi,

So I am working on putting a new system together. So far I purchased the Raspberry Pi 4 and an Elgato HD60X. I was hoping to use one of these drivers with the built in level shifter to make things a bit more simplified. I will also be going with SK6812 LED strip.

I will be using close to 300 LED's so I read I will need to go with the multi segment setup. I was going to get either the Pimoroni Plasma 2040 or the Adafruit Feather RP2040 SCORPIO (not sure if one has any benefits over the other).

For the interface to use, you mention to use CL for segment 1 and DA for segment 2. (for the Pimoroni) However, for SPI interface you say to use those for clock and data, respectfully. Does that mean you cannot do a multi segment setup with SPI?

How do I know if I should even be using SPI or not? I am looking at a strip from amazon and it says a SK6812 and lists it under "SPI LED Strips", but it has no mention of SPI in its details page.

Thanks :)

1 reply

danielbrunt57 Jan 3, 2024

I finally got my old SK6812 Natural White strip of 221 LEDS working with HyperHDR and Pimoroni Plasma 2040 and I am pleased. Zero visible latency as compared to the same strip before via Hyperion + WLED on Athom LS-4P controller. I was going to use APA102 but the strip I got on Aliexpress was FUBAR...

awawa-dev · 2024-01-03T09:13:55Z

awawa-dev
Jan 3, 2024
Maintainer Author

I will be using close to 300 LED's so I read I will need to go with the multi segment setup. I was going to get either the Pimoroni Plasma 2040 or the Adafruit Feather RP2040 SCORPIO (not sure if one has any benefits over the other).

I never wrote that you have to use a multi-segment for 300LED, but you can consider it taking into account other factors, e.g. a slightly more complicated setup, more cables, etc. Of course, multi-segment will be faster, but for 300 RGBW LEDs it's 100Hz versus 83Hz, which could make a difference if you're building a strict gaming setup. Going above 100-120Hz rarely make sense because the PC/RPi clocks usually do not have required precision.

SK6812 is Neopixel LED strip which require one data line, APA102 is SPI LED strip and requires two data lines: SPI LEDs do not required multi-segment because of very high data line speed nor such multi-segment is supported by the firmware. CL for segment 1 and DA for segment 2 CL/DA are mentioned here because that is how the ports are marked on the Pimoroni board, but they are multifunctional.. not limited to SPI LEDs only.

9 replies

jingato Jan 4, 2024

cool, thanks for the input. I guess I assumed a higher resolution would yield better accuracy. But like I said, perhaps overkill.

danielbrunt57 Jan 4, 2024

144/m simply means you have ~2.5 times more light souces shining on the wall behind the TV so even if you have 144 different colored lines per meter on the screen each illuminating 144 LEDs at different colors, the light diffuses and mixes as they disperse 120° from each LED so they would have to be like little pinpoint laser dots for you to see them individually on the wall, which would defeat the purpose and effect of ambient lighting! Or you could stand behind the TV and watch the lightshow but I prefer to sit in front of it ;)

awawa-dev Jan 4, 2024
Maintainer Author

144/m simply means you have ~2.5 times more light souces shining on the wall behind the TV so even if you have 144 different colored lines per meter on the screen each illuminating 144 LEDs at different colors, the light diffuses and mixes as they disperse 120°

144 LEDs/meter will of course be brighter, rather forcing the use of a multi-segment due to the limited data speed, but this angle does not fully illustrate the situation that all colors will mix terribly: the more LEDs, the smaller the area per LED will be so its average will better reproduce the color in this place, and besides, the highest light intensity is contained in an angle of approximately ~60 degrees. But yes, the closer to the wall, the better. In short: the higher the density LED/meter, the less color mixing in the application when it averages colors, but we risk mixing colors on the wall, especially if it is far from the LEDs.

danielbrunt57 Jan 4, 2024

Huh? LOL! I think that makes sense. @jingato Try it, you might like it!
65" TV's generally have an outer circumference of around 4.57m. My 50" is 3.55m.
Is 4m going to be enough for you?
Measure twice, order once!

danielbrunt57 Jan 4, 2024

I found 5m APA102 SK9822 96 Leds!

awawa-dev · 2024-01-04T10:52:18Z

awawa-dev
Jan 4, 2024
Maintainer Author

@danielbrunt57

I found 5m APA102 SK9822 96 Leds!

I use 96LEDs/meter but sk6812RGBW and I really like it. You wont get APA102 on Ali and it's RGB only. At least I've never heard a success story. All clones with worse specification...if they meet such "tech specification" at all. Sometimes manufacturers enter in non-key parameters what the customer wants to see there, or these parameters change with subsequent revisions.

But if we want to trust such "tech specifications" why not to try new sk6812 RGBW upgraded model which promises 3.3V MCU support. So say goodbye to level shifters (hmm..isn't that what we wanted to get?)
https://www.btf-lighting.com/collections/sk6812-rgbw/products/1-sk6812-rgbw-4-in-1-pixels-individual-addressable-led-strip-dc5v

The “Tech Specs” of new upgraded sk6812 RGBW is currently only available on their YouTube clip. There is no guarantee which version you will get? And not a word about the tolerance/range of the 3.3V data line which is very, very important...

0 replies

thommy86 · 2024-01-22T18:17:56Z

thommy86
Jan 22, 2024

I just received a Pimoroni Plasma Stick 2040 W and flashed it with the latest release. I connected it to my TV (LG with webOS and piccap) and the LEDs wouldn't light up. So I got a test strip (SK6812RGBWN) and did an install on a windows machine. HyperHDR seems to connect fine to the board, but the strip isn't lighting up.

Any way to debug? I don't see any error. I connected the strip to another controller and it does work fine.

Logs

2024-01-22T19:09:51.897Z [MAIN] TTY is not attached to the log output
2024-01-22T19:09:51.897Z [MAIN] Database path: 'C:/Users/Thommy/.hyperhdr/db/hyperhdr.db', readonlyMode = disabled
2024-01-22T19:09:51.897Z [MAIN] Starting HyperHdr - 20.0.0.0beta1, (HEAD detached at v20.0.0.0beta1) (GitHub-ccd22a1/558c7e0-1703192848), built: Dec 23 2023:14:34:46
2024-01-22T19:09:51.897Z [MAIN] Set user data path to 'C:/Users/Thommy/.hyperhdr'
2024-01-22T19:09:51.897Z [INSTANCE_CFG] Loading instance configuration
2024-01-22T19:09:51.897Z [DB] Database opened: C:/Users/Thommy/.hyperhdr/db/hyperhdr.db
2024-01-22T19:09:51.913Z [INSTANCE_CFG] Settings database initialized
2024-01-22T19:09:51.929Z [SOUND_GRABBER] Sound device is disabled
2024-01-22T19:09:51.991Z [JSONSERVER] (JsonServer.cpp:26) Created new instance
2024-01-22T19:09:52.007Z [JSONSERVER] Started on port 19444
2024-01-22T19:09:52.007Z [SSDP] (SSDPHandler.cpp:31) SSDPHandler is initialized
2024-01-22T19:09:52.007Z [MAIN] start systray
2024-01-22T19:09:51.944Z [Media Foundation:auto] (GrabberWrapper.cpp:55) Starting the grabber wrapper
2024-01-22T19:09:51.944Z [MEDIA_FOUNDATION:AUTO] Starting to enumerate video capture devices
2024-01-22T19:09:51.944Z [HYPERHDR0] Starting the instance
2024-01-22T19:09:51.944Z [INSTANCE_CFG0] Loading instance configuration
2024-01-22T19:09:51.944Z [DB] Database opened: C:/Users/Thommy/.hyperhdr/db/hyperhdr.db
2024-01-22T19:09:51.944Z [MEDIA_FOUNDATION:AUTO] (MFGrabber.cpp:427) Detected 1 devices
2024-01-22T19:09:51.944Z [MEDIA_FOUNDATION:AUTO] Found capture device: Integrated Webcam
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] Restarting video grabber is now blocked due to reloading of the configuration
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] (Grabber.cpp:159) Set new width: 512, height: 512 for capture
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] (Grabber.cpp:335) setWidthHeight preparing to restarting video grabber 0
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] Delayed restart of the grabber due to change of the capturing resolution
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] Delayed restart of the grabber due to change of the framerate
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] (DxGrabber.cpp:125) setHdrToneMappingMode to: Disabled
2024-01-22T19:09:51.959Z [SIGNAL_OLD] (DetectionManual.cpp:84) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2024-01-22T19:09:51.959Z [SIGNAL_OLD] (DetectionManual.cpp:74) Signal threshold set to: {12, 12, 12} and frames: 200
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] (Grabber.cpp:380) setDeviceVideoStandard preparing to restart video grabber. Old: '' new: 'auto'
2024-01-22T19:09:51.959Z [DX11_SYSTEM:AUTO] Delayed restart of the grabber due to change of selected device
2024-01-22T19:09:51.991Z [INSTANCE_CFG0] Settings database initialized
2024-01-22T19:09:51.991Z [COMPONENTCTRL0] (ComponentController.cpp:30) ComponentController is initialized
2024-01-22T19:09:51.991Z [BLACKBORDER] Set mode to: default
2024-01-22T19:09:51.991Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:192) Set LED mapping type to advanced
2024-01-22T19:09:51.991Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:176) setSparseProcessing to 0
2024-01-22T19:09:51.991Z [IMAGETOLED_MNG0] (ImageToLedManager.cpp:103) ImageToLedManager initialized
2024-01-22T19:09:51.991Z [MUXER0] (Muxer.cpp:55) Muxer initialized
2024-01-22T19:09:51.991Z [COLORSPACE_CALIBRATION0] classicMode: no, gammas:[1.50, 1.50, 1.50], saturation: 1.00, luminance: 1.00, backLight: [enabled, threshold: 1, colored: yes]
2024-01-22T19:09:51.991Z [LED_CALIBRATION0] (LedCalibration.cpp:101) Calibration config '0' for LED segment: [0, 24]
2024-01-22T19:09:51.991Z [HYPERHDR0] Led strip RGB order is: rgb
2024-01-22T19:09:51.991Z [SMOOTHING0] High resolution clock is steady (good)
2024-01-22T19:09:51.991Z [SMOOTHING0] Clearing queued colors before: enabling
2024-01-22T19:09:51.991Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:09:51.991Z [COMPONENTCTRL0] Smoothing: enabled
2024-01-22T19:09:51.991Z [SMOOTHING0] Creating config (0) => type: Alternative, dirMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-01-22T19:09:51.991Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-01-22T19:09:51.991Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:09:51.991Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-01-22T19:09:51.991Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-01-22T19:09:52.007Z [HYPER_MANAGER] HyperHDR instance 'First LED instance' has been started
2024-01-22T19:09:52.007Z [HYPERHDR0] The instance is running
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] Start LedDevice 'adalight'.
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:310) deviceConfig: [{"awa_mode":true,"colorOrder":"rgb","currentLedCount":25,"espHandshake":true,"maxRetry":0,"output":"COM7","rate":2000000,"refreshTime":20,"smoothingRefreshTime":20,"type":"adalight","white_channel_blue":255,"white_channel_calibration":true,"white_channel_green":255,"white_channel_limit":100,"white_channel_red":255}]
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 50.00 Hz
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:396) Refresh rate = 50.00 Hz
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:346) Device is not ready to start a timer
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:406) Refresh interval updated to 20ms
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:49) DeviceType   : adalight
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:50) LedCount     : 25
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:51) RefreshTime  : 20
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:65) Device name   : COM7
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:66) Auto selection: 0
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:67) Baud rate     : 2000000
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:68) ESP handshake : ON
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:69) Delayed open  : 0
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:70) Retry limit   : 0
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] The refresh timer is enabled ('Refresh time' > 0) and may limit the performance of the LED driver. Ignore this error if you set it on purpose for some reason (but you almost never need it).
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDeviceAdalight.cpp:79) Adalight driver with activated high speeed & data integration check AWA protocol
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDeviceAdalight.cpp:89) Adalight header for 25 leds: AwA 0x00 0x18 0x4d
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDeviceAdalight.cpp:45) White channel limit: 255, red: 255, green: 255, blue: 255
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] Opening UART: COM7
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:206) _serialPort.open(QIODevice::ReadWrite): COM7, Baud rate [2000000]bps
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:211) portName:          COM7
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:212) systemLocation:    \\.\COM7
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:213) description:       USB Serial Device
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) manufacturer:      Microsoft
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) productIdentifier: 0xa
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) vendorIdentifier:  0x2e8a
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) serialNumber:      E6616408433D372A
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] Detected Rp2040 type board. HyperHDR skips the reset. State: 0, 0
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] ESP sent: 'HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem1: 0, mem2: 460, heap: 123232'
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] ESP sent: 'RGBW => Gain: 255/255, red: 255, green: 255, blue: 255'
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (Welcome! Awa driver 9.) at 1 msec
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:63) Switch on
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:139) Power On
2024-01-22T19:09:52.007Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 20ms
2024-01-22T19:09:52.018Z [COMPONENTCTRL0] LED device: enabled
2024-01-22T19:09:52.018Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-22T19:09:52.018Z [EFFECTENGINE0] Run effect "Rainbow swirl fast" on channel 0
2024-01-22T19:09:52.018Z [EFFECTENGINE0] (EffectEngine.cpp:92) Start the effect: name [Rainbow swirl fast]
2024-01-22T19:09:52.018Z [MUXER0] Register new input 'System/EFFECT' with priority 0 as inactive
2024-01-22T19:09:52.018Z [HYPERHDR0] Boot effect: animation set to 'Rainbow swirl fast' [started]
2024-01-22T19:09:52.018Z [EFFECT0(Rainbo...)] Begin playing the effect with priority: 0
2024-01-22T19:09:52.019Z [MUXER0] Priority 0 is now active
2024-01-22T19:09:52.019Z [MUXER0] Set visible priority to 0
2024-01-22T19:09:52.019Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-01-22T19:09:52.019Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:09:52.019Z [SMOOTHING0] Selecting config (2) => type: Linear, directMode: false, pause: false, settlingTime: 200ms, interval: 40ms (25Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2024-01-22T19:09:52.019Z [SMOOTHING0] Using linear smoothing input (2)
2024-01-22T19:09:52.019Z [HYPERHDR0] New priority[0], previous [255]
2024-01-22T19:09:52.019Z [HYPERHDR0] New source available -> switch LED-Device on
2024-01-22T19:09:52.019Z [SMOOTHING0] Clearing queued colors before: enabling
2024-01-22T19:09:52.019Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 25.00 Hz
2024-01-22T19:09:52.019Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:396) Refresh rate = 25.00 Hz
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 40ms
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:406) Refresh interval updated to 40ms
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:421) LED refresh interval adjustment caused by smoothing configuration change to 40ms (proposed: 40ms)
2024-01-22T19:09:52.019Z [IMAGETOLED_MNG0] Total index number is: 320 (memory: 320). User sparse processing is: disabled, image size: 80 x 45, area number: 25
2024-01-22T19:09:52.019Z [SMOOTHING0] Using linear smoothing input (2)
2024-01-22T19:09:52.019Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-01-22T19:09:52.057Z [MEDIA_FOUNDATION:AUTO] (MFGrabber.cpp:466) Device has 'brightness' control => min: -64, max: 64, default: 0
2024-01-22T19:09:52.059Z [MEDIA_FOUNDATION:AUTO] (MFGrabber.cpp:473) Device has 'contrast' control => min: 0, max: 95, default: 0
2024-01-22T19:09:52.060Z [MEDIA_FOUNDATION:AUTO] (MFGrabber.cpp:480) Device has 'saturation' control => min: 0, max: 100, default: 64
2024-01-22T19:09:52.061Z [MEDIA_FOUNDATION:AUTO] (MFGrabber.cpp:487) Device has 'hue' control => min: -2000, max: 2000, default: 0
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 640 x 480 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 160 x 120 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 176 x 144 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 320 x 180 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 320 x 240 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 352 x 288 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 424 x 240 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 640 x 360 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 848 x 480 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 1280 x 720 @ 10 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 640 x 480 @ 30 fps YUY2 (yuyv)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 1280 x 720 @ 30 fps NV12 (nv12)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 1280 x 720 @ 30 fps MJPG (mjpeg)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 960 x 540 @ 30 fps NV12 (nv12)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 960 x 540 @ 30 fps MJPG (mjpeg)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 1280 x 720 @ 30 fps NV12 (nv12)
2024-01-22T19:09:52.062Z [MEDIA_FOUNDATION:AUTO] Integrated Webcam 1280 x 720 @ 30 fps MJPG (mjpeg)
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] Restarting video grabber is now blocked due to reloading of the configuration
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] Cropping image: width=0 height=0; crop: left=0 right=0 top=0 bottom=0 
2024-01-22T19:09:52.064Z [Media Foundation:auto] (GrabberWrapper.cpp:126) CEC keycode. Start: 0, stop: 0
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] (Grabber.cpp:273) setBrightnessContrastSaturationHue nothing changed
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] (MFGrabber.cpp:185) setHdrToneMappingMode to: Disabled
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] (Grabber.cpp:182) setFpsSoftwareDecimation to: 1
2024-01-22T19:09:52.064Z [SIGNAL_OLD] (DetectionManual.cpp:84) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2024-01-22T19:09:52.064Z [SIGNAL_OLD] (DetectionManual.cpp:74) Signal threshold set to: {12, 12, 12} and frames: 200
2024-01-22T19:09:52.064Z [SIGNAL_AUTO] (DetectionAutomatic.cpp:376) Automatic signal detection -> errorTolerance: 9, modelTolerance: 90, sleepTime: 5000, wakeTime: 1000
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] (Grabber.cpp:380) setDeviceVideoStandard preparing to restart video grabber. Old: '' new: 'auto'
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] Delayed restart of the grabber due to change of selected device
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] (Grabber.cpp:200) Force encoding to: NO_CHANGE (old: NO_CHANGE)
2024-01-22T19:09:52.064Z [MEDIA_FOUNDATION:AUTO] setQFrameDecimation is now: disabled
2024-01-22T19:09:52.066Z [WEBSERVER] Initialize Webserver
2024-01-22T19:09:52.066Z [FLATBUFSERVER] Started on port 19400
2024-01-22T19:09:52.067Z [FLATBUFSERVER] Started local domain socket server: 'hyperhdr-domain'
2024-01-22T19:09:52.074Z [WEBSERVER] Apply Webserver settings
2024-01-22T19:09:52.074Z [WEBSERVER] Set document root to: :/www
2024-01-22T19:09:52.075Z [WEBSERVER] Started: 'HyperHDR WebServer (HTTP)' on port: 8090
2024-01-22T19:09:52.075Z [SSDP] (SSDPHandler.cpp:93) The local address is empty
2024-01-22T19:09:52.075Z [WEBSERVER] Initialize Webserver
2024-01-22T19:09:52.075Z [WEBSERVER] Apply Webserver settings
2024-01-22T19:09:52.075Z [WEBSERVER] Set document root to: :/www
2024-01-22T19:09:52.078Z [NETFORWARDER] Forwarder has changed state to disabled
2024-01-22T19:09:52.100Z [SMOOTHING0] Using linear smoothing procedure (2)
2024-01-22T19:09:52.101Z [WEBSERVER] Setup SSL certificate
2024-01-22T19:09:52.101Z [WEBSERVER] Setup private SSL key
2024-01-22T19:09:52.101Z [WEBSERVER] Started: 'HyperHDR WebServer (HTTPS)' on port: 8092
2024-01-22T19:09:52.101Z [SSDP] (SSDPHandler.cpp:42) SSDPHandler is initializing
2024-01-22T19:09:52.107Z [SSDP] (SSDPHandler.cpp:183) The local address is: 192.168.178.186
2024-01-22T19:09:52.107Z [SSDP] (SSDPServer.cpp:95) Initialize the SSDP server
2024-01-22T19:09:52.107Z [WEBSERVER] (StaticFileServing.cpp:68) SSDP description is set up
2024-01-22T19:09:52.107Z [SSDP] Starting the SSDP server
2024-01-22T19:09:52.787Z [WEBSOCKET] (WebSocketClient.cpp:39) New connection from ::1
2024-01-22T19:09:53.116Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::1
2024-01-22T19:09:53.583Z [NET_DISCOVERY] Found Pico/RP2040 at COM7:-1 (USB Serial Device)
2024-01-22T19:09:53.580Z [SERVICE_mDNS] Starting the network discovery thread
2024-01-22T19:09:53.685Z [NET_DISCOVERY] Found WLED at 192.168.178.45:80 (wled-hyperion.local)
2024-01-22T19:09:53.691Z [NET_DISCOVERY] Found Hue bridge at 192.168.178.94:8080 (DIYHue.local)
2024-01-22T19:09:53.699Z [NET_DISCOVERY] Found WLED at 192.168.178.113:80 (wled-koof.local)
2024-01-22T19:09:55.021Z [EFFECT0(Rainbo...)] The effect quits with priority: 0
2024-01-22T19:09:55.021Z [MUXER0] Removed source priority 0
2024-01-22T19:09:55.021Z [MUXER0] Set visible priority to 255
2024-01-22T19:09:55.022Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2024-01-22T19:09:55.022Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:09:55.022Z [SMOOTHING0] Selecting config (0) => type: Alternative, directMode: false, pause: false, settlingTime: 150ms, interval: 20ms (50Hz), antiFlickTres: 32, antiFlickStep: 2, antiFlickTime: 250
2024-01-22T19:09:55.022Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-22T19:09:55.022Z [HYPERHDR0] New priority[255], previous [0]
2024-01-22T19:09:55.022Z [HYPERHDR0] No source left -> switch LED-Device off
2024-01-22T19:09:55.022Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-01-22T19:09:55.022Z [SMOOTHING0] Clearing queued colors before: disabling
2024-01-22T19:09:55.022Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:09:55.022Z [LEDDEVICE0_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 50.00 Hz
2024-01-22T19:09:55.022Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:396) Refresh rate = 50.00 Hz
2024-01-22T19:09:55.022Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 20ms
2024-01-22T19:09:55.022Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:406) Refresh interval updated to 20ms
2024-01-22T19:09:55.022Z [COLORSPACE_CALIBRATION0] (ColorSpaceCalibration.cpp:225) setBackLightEnabled: 0
2024-01-22T19:09:55.022Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:421) LED refresh interval adjustment caused by smoothing configuration change to 20ms (proposed: 20ms)
2024-01-22T19:09:55.022Z [EFFECTENGINE0] Effect 'Rainbow swirl fast' has finished.
2024-01-22T19:09:55.023Z [EFFECT0(Rainbo...)] Effect named: 'Rainbow swirl fast' is deleted
2024-01-22T19:09:55.023Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:270) Disable the device
2024-01-22T19:09:55.023Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-01-22T19:09:55.023Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:89) Switch off
2024-01-22T19:09:55.023Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:517) Set LED strip to black/power off
2024-01-22T19:09:55.024Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:143) Flush was successful
2024-01-22T19:09:55.027Z [LEDDEVICE0_ADALIGHT] Received goodbye: 'HyperHDR frames: 25 (FPS), receiv.: 25, good: 25, incompl.: 0, mem1: 0, mem2: 460, heap: 123232
' (97)
2024-01-22T19:09:55.030Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:161) Serial port is closed: COM7
2024-01-22T19:09:55.030Z [COMPONENTCTRL0] LED device: disabled
2024-01-22T19:09:57.456Z [WEBSOCKET] (HyperAPI.cpp:966) log streaming deactivated for client  ::1
2024-01-22T19:09:57.627Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"adalight","subcommand":"discover","tan":310}]
2024-01-22T19:09:57.628Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"name":"Auto","value":"auto"},{"name":"USB Serial Device (\\\\.\\COM7)","value":"COM7"}],"ledDeviceType":"adalight"}]
2024-01-22T19:10:04.261Z [SMOOTHING0] Clearing queued colors before: enabling
2024-01-22T19:10:04.261Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] Opening UART: COM7
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:206) _serialPort.open(QIODevice::ReadWrite): COM7, Baud rate [2000000]bps
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:211) portName:          COM7
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:212) systemLocation:    \\.\COM7
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:213) description:       USB Serial Device
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) manufacturer:      Microsoft
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) productIdentifier: 0xa
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) vendorIdentifier:  0x2e8a
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) serialNumber:      E6616408433D372A
2024-01-22T19:10:04.262Z [LEDDEVICE0_ADALIGHT] Detected Rp2040 type board. HyperHDR skips the reset. State: 0, 0
2024-01-22T19:10:04.272Z [LEDDEVICE0_ADALIGHT] ESP sent: 'HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem1: 0, mem2: 460, heap: 123232'
2024-01-22T19:10:04.272Z [LEDDEVICE0_ADALIGHT] ESP sent: 'RGBW => Gain: 255/255, red: 255, green: 255, blue: 255'
2024-01-22T19:10:04.272Z [LEDDEVICE0_ADALIGHT] DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (Welcome! Awa driver 9.) at 1 msec
2024-01-22T19:10:04.272Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:63) Switch on
2024-01-22T19:10:04.272Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:139) Power On
2024-01-22T19:10:04.272Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 20ms
2024-01-22T19:10:04.273Z [COMPONENTCTRL0] LED device: enabled
2024-01-22T19:10:04.273Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-22T19:10:04.313Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-01-22T19:10:06.652Z [MUXER0] Register new input 'Web Configuration@::1/COLOR' with priority 1 as inactive
2024-01-22T19:10:06.652Z [MUXER0] Priority 1 is now active
2024-01-22T19:10:06.652Z [MUXER0] Set visible priority to 1
2024-01-22T19:10:06.652Z [HYPERHDR0] New priority[1], previous [255]
2024-01-22T19:10:06.652Z [HYPERHDR0] New source available -> switch LED-Device on
2024-01-22T19:10:06.652Z [SMOOTHING0] Clearing queued colors before: enabling
2024-01-22T19:10:06.652Z [SMOOTHING0] Smoothing queue is cleared
2024-01-22T19:10:06.653Z [SMOOTHING0] Using alternative smoothing input (0)
2024-01-22T19:10:06.653Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-01-22T19:10:06.673Z [SMOOTHING0] Using alternative smoothing procedure (0)
2024-01-22T19:10:12.130Z [MEDIA_FOUNDATION:AUTO] setHdrToneMappingMode to: enable, but the LUT file is currently unloaded
2024-01-22T19:10:12.131Z [COMPONENTCTRL0] HDR (global): enabled
2024-01-22T19:10:20.451Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::1
2024-01-22T19:10:56.608Z [WEBSOCKET] (HyperAPI.cpp:966) log streaming deactivated for client  ::1
2024-01-22T19:11:11.070Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::1

13 replies

thommy86 Feb 6, 2024

So the tests that I did before, were on a windows machine. Now I connected the same setup to the usb of my LG B8 running v20b and piccap. The leds are not working and there is no info in the performance tab like in your documentation. I also see that with the message below, is not capable of the 2mb speed. Should I change settings for the Pimoroni Plasma Stick 2040 W ?

[LEDDEVICE0_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico device

Logs

2024-02-06T00:57:27.938Z [WEBSOCKET] (HyperAPI.cpp:966) log streaming deactivated for client  ::ffff:192.168.178.152
2024-02-06T00:57:28.509Z [WEBSOCKET] (HyperAPI.cpp:1109) message: [{"command":"leddevice","ledDeviceType":"adalight","subcommand":"discover","tan":943}]
2024-02-06T00:57:28.526Z [WEBSOCKET] (HyperAPI.cpp:1133) response: [{"devices":[{"name":"Auto","value":"auto"},{"name":" (/dev/ttyAMA0)","value":"ttyAMA0"},{"name":" (/dev/ttyAMA2)","value":"ttyAMA2"},{"name":" (/dev/ttyAMA1)","value":"ttyAMA1"},{"name":" (/dev/ttyACM0)","value":"ttyACM0"}],"ledDeviceType":"adalight"}]
2024-02-06T00:57:36.140Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-02-06T00:57:36.141Z [LEDDEVICE0_ADALIGHT] Start LedDevice 'adalight'.
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:310) deviceConfig: [{"awa_mode":true,"colorOrder":"rgb","currentLedCount":247,"espHandshake":true,"hardwareLedCount":null,"maxRetry":3,"output":"ttyACM0","rate":2000000,"refreshTime":20,"smoothingRefreshTime":20,"type":"adalight","white_channel_calibration":false}]
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] Ignoring user LED refresh rate. Forcing smoothing refresh rate = 50.00 Hz
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:396) Refresh rate = 50.00 Hz
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:346) Device is not ready to start a timer
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:406) Refresh interval updated to 20ms
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:49) DeviceType   : adalight
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:50) LedCount     : 247
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:51) RefreshTime  : 20
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:65) Device name   : ttyACM0
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:66) Auto selection: 0
2024-02-06T00:57:36.142Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:67) Baud rate     : 2000000
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:68) ESP handshake : ON
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:69) Delayed open  : 0
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:70) Retry limit   : 3
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] The refresh timer is enabled ('Refresh time' > 0) and may limit the performance of the LED driver. Ignore this error if you set it on purpose for some reason (but you almost never need it).
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (LedDeviceAdalight.cpp:79) Adalight driver with activated high speeed & data integration check AWA protocol
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (LedDeviceAdalight.cpp:88) Adalight header for 247 leds: Awa 0x00 0xf6 0xa3
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] Opening UART: ttyACM0
2024-02-06T00:57:36.143Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:206) _serialPort.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:211) portName:          ttyACM0
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:212) systemLocation:    /dev/ttyACM0
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:213) description:       
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) manufacturer:      
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) productIdentifier: 0x0
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) vendorIdentifier:  0x0
2024-02-06T00:57:36.164Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) serialNumber:      
2024-02-06T00:57:37.485Z [LEDDEVICE0_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico device
2024-02-06T00:57:37.486Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:63) Switch on
2024-02-06T00:57:37.486Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:139) Power On
2024-02-06T00:57:37.486Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 20ms
2024-02-06T00:57:38.527Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:57:39.528Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:57:39.623Z [WEBSOCKET] (HyperAPI.cpp:957) log streaming activated for client ::ffff:192.168.178.152
2024-02-06T00:57:40.529Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:57:41.530Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:57:42.531Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:57:43.532Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:57:43.532Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:143) Flush was successful
2024-02-06T00:58:14.135Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:161) Serial port is closed: ttyACM0
2024-02-06T00:58:14.135Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-02-06T00:58:14.135Z [LEDDEVICE0_ADALIGHT] Device 'adalight' is disabled due to an error: 'Timeout writing data to ttyACM0'
2024-02-06T00:58:14.136Z [COMPONENTCTRL0] LED device: disabled
2024-02-06T00:58:16.237Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-02-06T00:58:16.237Z [LEDDEVICE0_ADALIGHT] Opening UART: ttyACM0
2024-02-06T00:58:16.237Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:206) _serialPort.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:211) portName:          ttyACM0
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:212) systemLocation:    /dev/ttyACM0
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:213) description:       
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) manufacturer:      
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) productIdentifier: 0x0
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) vendorIdentifier:  0x0
2024-02-06T00:58:16.254Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) serialNumber:      
2024-02-06T00:58:17.574Z [LEDDEVICE0_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico device
2024-02-06T00:58:17.575Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:63) Switch on
2024-02-06T00:58:17.575Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:139) Power On
2024-02-06T00:58:17.575Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 20ms
2024-02-06T00:58:17.575Z [COMPONENTCTRL0] LED device: enabled
2024-02-06T00:58:18.617Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:19.618Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:20.619Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:21.620Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:22.621Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:23.622Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:23.623Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:143) Flush was successful
2024-02-06T00:58:54.225Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:161) Serial port is closed: ttyACM0
2024-02-06T00:58:54.225Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:354) Stopping refresh timer
2024-02-06T00:58:54.225Z [LEDDEVICE0_ADALIGHT] Device 'adalight' is disabled due to an error: 'Timeout writing data to ttyACM0'
2024-02-06T00:58:54.226Z [COMPONENTCTRL0] LED device: disabled
2024-02-06T00:58:56.243Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:220) Enable the device
2024-02-06T00:58:56.243Z [LEDDEVICE0_ADALIGHT] Opening UART: ttyACM0
2024-02-06T00:58:56.243Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:206) _serialPort.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:211) portName:          ttyACM0
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:212) systemLocation:    /dev/ttyACM0
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:213) description:       
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:214) manufacturer:      
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) productIdentifier: 0x0
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) vendorIdentifier:  0x0
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:217) serialNumber:      
2024-02-06T00:58:56.387Z [PERFORMANCE] [INSTANCE0: FPS = 23.18, processed = 1391]
2024-02-06T00:58:57.580Z [LEDDEVICE0_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico device
2024-02-06T00:58:57.581Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:63) Switch on
2024-02-06T00:58:57.581Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:139) Power On
2024-02-06T00:58:57.581Z [LEDDEVICE0_ADALIGHT] (LedDevice.cpp:340) Starting timer with interval = 20ms
2024-02-06T00:58:57.581Z [COMPONENTCTRL0] LED device: enabled
2024-02-06T00:58:58.623Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:58:59.624Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:59:00.625Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:59:01.626Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:59:02.627Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:59:03.628Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:290) Timeout after 1000ms: 0 frames already dropped
2024-02-06T00:59:03.628Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:143) Flush was successful

awawa-dev Feb 6, 2024
Maintainer Author

If your ttyACM0 is in fact Pimoroni and it produces such logs :

2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:215) productIdentifier: 0x0
2024-02-06T00:58:56.260Z [LEDDEVICE0_ADALIGHT] (ProviderSerial.cpp:216) vendorIdentifier: 0x0

Then you met infamous udev bug (https://bugreports.qt.io/browse/QTBUG-113462 systemd/systemd#25238 ) . Two options:

use classic version of HyperSerialPico firmware (must compile for custom Pimoroni pinout) and disable Awa protocol in Adalight driver (you wont see statistics as a side effect)
compile latest version of HyperHDR that has forced detection (patch provided by @alex-013) or wait a bit for v20beta2

thommy86 Feb 6, 2024

Where can I disable the Awa protocol? I followed the wiki, but don't see anything referring to Awa in the CMakeLists.txt

Do you have an indication when to build v20beta2? For WebOS, I'm not sure how to build.

awawa-dev Feb 6, 2024
Maintainer Author

Where can I disable the Awa protocol?

just in HyperHDR Adalight driver. But choose only one option: use classic firmware (build it from branch classic_adalight on HyperSerialPico) and disable awa protocol in your current HyperHDR OR build latest HyperHDR for webos and use standard firmware with awa protocol. I think users on webos Discord could help how to build it using Github Action.

thommy86 Feb 6, 2024

Thanks for the clarification! The classic_adalight is already building. Will test this first!

asvictory3 · 2024-01-25T15:49:33Z

asvictory3
Jan 25, 2024

I’m working on my second HyperHDR project. Originally have a rooted LG C8 with piccap sending to a pi zero 2W which runs the LEDs on PWM which you typically recommend against. It’s working well. However, I’m doing another project on a new LG C3 and I’m preferring to switch to a RP2040. If I run both PicCap & HyperHDR on my TV itself (rather than HyperHDR on a Pi), how am I to get the data to a RP2040 like the adafruit feather Scorpio? Does it transmit over the TV USB with Adalight protocol? Would I be better with a networked solution such as ESP32/WLED? Thanks.

13 replies

Jerroder Mar 17, 2024

Sorry to hijack the post, I also managed to get it to work with the exact same setup (except I have a CX), but every time I turn off the TV, the USB isn't detected anymore. I need to unplug and replug the RP2040 several times, and sometimes I even have to change port. Any idea what the problem could be?

I remember you mentioned in awawa-dev/HyperSerialESP32#34 (comment) that webos resets the USB bus, can that be a/the problem?

awawa-dev Mar 17, 2024
Maintainer Author

On WebOS USB path could be changed after such reset. Normally HyperHDR 'auto' option should find the device at different location but if ProdoctId/VendorId is incorrect (set to 0) then it needs to be set/update manually.

Jerroder Mar 18, 2024

So what does the workaround in v20beta2 fix? If the ProductId/VendorId are set to 0 because of udev, what's the workaround?

awawa-dev Mar 18, 2024
Maintainer Author

It makes possible for rp2040 to work at all on affected systems

asvictory3 Mar 29, 2024

I updated to V20 release, the usb auto detect on C8 for the scorpio 2040 is still not working. Even with the force hyperserial detection on, It takes a USB unplug/replug to detect on tty/ACM0 and manually setting the output path to work.

satgit62 · 2024-02-29T16:10:06Z

satgit62
Feb 29, 2024

@awawa-dev
Hi,
I have compiled the HyperserialPico for the “Adafruit Feather 2040 Scorpio”, with Data on Pin0 GPIO16 + GND, and it is also recognized correctly by HyperHDR v20.0.0.0beta2 on LG webOS, and works as far as it should. The power supply for LEDs is switched on via an intelligent WLAN socket when required. When the power supply for LEDs is off and the TV is on, the LEDs flash red briefly at regular intervals.(approx. 60 seconds interval, consistent with HyperHDR log. See arrow in picture.) Even if I switch off the webOS HyperHDR Loader daemon, nothing flashes anymore. This does not happen when the power supply is on. When I switch off the TV, the LEDs are off and there is no flashing. The level on the data line measured with a cheap oscilloscope is fairly constant. The -5Volt (GND) of the LED stripe is connected to the GND pair of the data of “Adafruit Feather 2040 Scorpio” and to the -5Volt (GND) of the power supply.
Is this behavior known and is there a workaround?
I'm not sure if it makes sense to connect another resistor between DATA, as GPIO16 already has level shifters.

1 reply

awawa-dev Feb 29, 2024
Maintainer Author

I don't know the cause. Sometimes in cheap "power relays" (smart sockets kind of fall into this category) leakage current happens even when it's turned off/off and strange things can happen. But you would have to measure the current by connecting the plus between the LED power supply and the LED strip.

satgit62 · 2024-03-01T09:23:18Z

satgit62
Mar 1, 2024

@awawa-dev
Hi, thank you for your reply. Yes, the WLAN socket has caused these strange errors. I did not notice it until now because with the ESP32 ETH0-WLED these errors did not occur, very strange. Thanks for HyperHDR and HyperSerialPico. A perfect marriage! Since I have the SK6812RBGW NW, I would have to reduce the “Blue/White channel aspect” to 180 as you recommended. The result is perfect.
The result compared to WLED/ESP is not only measurable with expensive measuring equipment, but you can see it with your own eyes, so that's amazing.

0 replies

Piou338 · 2024-03-02T12:46:19Z

Piou338
Mar 2, 2024

Hello everyone,

I seen some HyperHDR projects and started a few weeks ago my own.
I red a lot but now i put everything together, it's not working even without capturing device.

So my setup is :
WS2812
Adafruit Feather RP2040 SCORPIO with the scorpio ws2812 firmware
Raspberry pi 4 with HyperHDR v20

For now I put a static color and the led hardware configuration is correctly put on adalight with AWA protocol and rp2040 handshake (the device is detected on the output path).

Could someone help a newbie plz ?

9 replies

Piou338 Mar 2, 2024

I tried with one led with the 5v connected on the usb pin form Scorpio but it's not working eather :'(
How could I test the scorpio without the raspberry and HDR (somethink like direct mode or something like that) ?

awawa-dev Mar 2, 2024
Maintainer Author

Notice the arrows on the LED strip

danielbrunt57 Mar 3, 2024

You've connected the data cable to the wrong end of the led strip. The arrows point towards the output end. Try connecting the data signal to the other end, the input end! Power and ground can be either (or both) ends.

danielbrunt57 Mar 3, 2024

I tried with one led with the 5v connected on the usb pin form Scorpio

If you mean just a single plain LED connected to data signal from Scorpio, you can't do that. The data signal pin is not a power pin. Single LEDs only have + and - voltage, no signal.

Piou338 Mar 5, 2024

I receive my new led strip (6812 cold) and it's working :)
I'm starting the configuration

Thank you for your help guys

empakoso · 2024-03-28T10:42:58Z

empakoso
Mar 28, 2024

I am using the Adafruit Feather RP2040 SCORPIO with NeoPixel WS2812B. The plan is as follows:

RP2040 NEOPIXEL0 (OUTPUT_DATA_PIN 16) to WS2818B data
RP2040 NEOPIXEL2 (OUTPUT_SPI_CLOCK_PIN) to Raspberry Pi GPIO11 (SCLK)
RP2040 NEOPIXEL3 (OUTPUT_SPI_DATA_PIN) to Raspberry Pi GPIO10 (MOSI)
RP2040 GND to Raspberry Pi GND (pin#20 for closest convenience)
please confirm that I am not using Raspberry Pi GPIO8 (CEO) or chip select

I've been searching and have not come across any specific diagram which matches these two items together. I am not very strong in understanding SPI Serial, I have dabbled in writing to SD cards using it so I remember a few things about the CEO pin aka Chip Select.

May I have verification to be confident before applying power? Thank you in advance.

5 replies

awawa-dev Mar 28, 2024
Maintainer Author

Are you sure you are using HyperSerialPico from this thread subject? Because it doesnt require SPI connection to Rpi but serial connect via USB.

empakoso Mar 28, 2024

I completely misssed that here somewhere. Sorry about that.

Is there a way to connect using Serial by soldering to the headers of the RP2040 and RPi? (because I don't trust 90% of the cables I have lying around - most are only USB-A to USB-C charge cables) The idea is to fit it all inside the RPi case.

awawa-dev Mar 28, 2024
Maintainer Author

I haven't tried it and I don't recommend it. Use a regular USB cable that has data lines. There is an alternative solution, such as HyperSPI, but I do not recommend it for beginners because if, as you probably wrote, you wanted to connect the output from the Scoprio level shifter GPIO (+5V) to RPi SPI, you will simply fry the RPi GPIO.

empakoso Mar 28, 2024

Well! this is a really really cool project you've created!! I am very impressed with the outcome. It is working. I finally found a USB A to USB C data cable (tested the RP2040 on a windows machine --> checked Device Manager to ensure RP2040 was showing as a Comm Port) I plugged the cable in and set the LED config to adalight then selected the Pico (/dev/ttyACM1) and WOW! Just blown away.

To confirm the only wire I needed to solder to the RP2040 Scorpio is the RP2040 NEOPIXEL0 (OUTPUT_DATA_PIN 16) to WS2818B data

The rest is handled with my USB-A to USB-C data-ready cable (power and data in one convenient connection).

Well done @awawa-dev !! a fine piece of software! Thank you.

awawa-dev Mar 28, 2024
Maintainer Author

Thanks! In typical setups consisting of two power supplies (dedicated to the RPi and a separate one for the LED strip), it will be necessary to connect also the ground from the Scorpio output to the LED strip ground to obtain common ground in the circuit.

kornner · 2024-05-18T15:23:46Z

kornner
May 18, 2024

Hi there. I’m planning to do a multi-segment setup with an Adafruit Feather RP2040 SCORPIO receiving signals from an LG TV via USB. I plan to use it with a set of 4m SK6812 60led/m strip.

I wonder if it is also possible to start two L-shape segments from one corner of the TV instead of from a middle top/bottom edge? I think that would help reduce connection points that I’ll have to use connectors or solder from 2 per segment to one.

Also, if I understand it correctly, the pico board only needs one GND wire linked from one of their neopixel GND pins, so only 2 data lines and 1 GDN (?). Can I connect this GDN line together with the two GDN lines from the LED strips with a wago-type block before running a single line back to the PSU?

This will be my first project and I’m looking forward to it. Thank you very much :)

3 replies

awawa-dev May 18, 2024
Maintainer Author

Hi
Yes, this should work in the SECOND_SEGMENT_REVERSED configuration. One ground for the communication line should be enough when you later connect it to both segments near the data input. Avoid creating loops in the ground connection: https://en.wikipedia.org/wiki/Ground_loop_(electricity)
If both segments start in almost the same place, be careful not to create a short circuit in this place (plus/ground will be on opposite sides for both segments, so the plus of the first segment will be close to the gnd of the second segment and similarly for the second gnd/plus pair). BTW If you use LED connectors, you must bear in mind that such a connection usually will not last.

awawa-dev May 18, 2024
Maintainer Author

4m SK6812 60led/m strip.

That's only 240 LED's. Not sure if the multi-segment is necessary. As I wrote in the tutorial, it is rather useful above 300 RGBW. And for the single segment setup you can also use cheaper Adafruit ItsyBitsy rp2040 (one line) instead.

kornner May 18, 2024

I actually have two corner mounts from my existing pre-made syncbox system I'm replacing that allows the LED strip to go around the corner with a slight bend. If I can repurpose them with the new strip, the multi-segment setup would allow me to use two continuous segments without cutting and reconnecting at the corners. But depending on how the new LED fits, I might go with a single segment instead.

Many thanks for the advice! I truly appreciate it.

Moerill · 2024-05-25T20:09:13Z

Moerill
May 25, 2024

Hi,
I'm trying to set up an Adafruit ItsyBitsy, but it seems to fail at flashing the board properly.
I'm using the packed release for the ItsyBitsy SK6812 Neutral, but tested it with the others as well.
Nothing besides the USB cable is connected to the board and it is connected to my main PC running Endeavor OS.

Here is the dmesg log:

[19583.600798] usb-storage 5-2.3.4.4:1.0: USB Mass Storage device detected  
[19583.600907] scsi host6: usb-storage 5-2.3.4.4:1.0  
[19584.617960] scsi 6:0:0:0: Direct-Access     RPI      RP2              3    PQ: 0 ANSI: 2  
[19584.619320] sd 6:0:0:0: [sdb] 262144 512-byte logical blocks: (134 MB/128 MiB)  
[19584.619799] sd 6:0:0:0: [sdb] Write Protect is off  
[19584.619802] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00  
[19584.621832] sd 6:0:0:0: [sdb] No Caching mode page found  
[19584.621835] sd 6:0:0:0: [sdb] Assuming drive cache: write through  
[19584.634929]  sdb: sdb1  
[19584.634997] sd 6:0:0:0: [sdb] Attached SCSI removable disk  
---- Here the firmware is put onto the device
[19638.981154] usb 5-2.3.4.4: USB disconnect, device number 33  
[19638.981430] device offline error, dev sdb, sector 260 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0  
[19638.981435] Buffer I/O error on dev sdb1, logical block 259, lost async page write  
[19638.987014] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty  
[19639.339423] usb 5-2.3.4.4: new full-speed USB device number 34 using xhci_hcd  
[19639.508798] usb 5-2.3.4.4: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00  
[19639.508802] usb 5-2.3.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3  
[19639.508803] usb 5-2.3.4.4: Product: Pico  
[19639.508805] usb 5-2.3.4.4: Manufacturer: Raspberry Pi  
[19639.508806] usb 5-2.3.4.4: SerialNumber: DF61B0C2233D1938  
[19639.562835] cdc_acm 5-2.3.4.4:1.0: ttyACM0: USB ACM device

And the corresponding HyperHDR (v20) error:

21:48:29.343 LEDDEVICE              : <ERROR> Dummy device type (file) used, because configured device 'adalight' throws error 'unknown device'

And no LED on the board is shining.

Do you have any hint on how to debug this?

Thank you in advance and for all the hard work!

5 replies

awawa-dev May 25, 2024
Maintainer Author

Hi
strange things may happen for a short while when restarting Pico, but it seems to have worked

[19639.562835] cdc_acm 5-2.3.4.4:1.0: ttyACM0: ACM USB Device

you wouldn't normally see a serial port interface without the appropriate firmware.
The question is whether you still see it after reconnecting to USB, because there was a problem with Adafruit boards, but the workaround (BOOT_WORKAROUND option) is enabled by default for their firmware (it is not available in the standard firmware version).

Moerill May 25, 2024

Oh i'm sorry, i forgot to mention that. When trying to reconnect the board, it doesn't seem to be recognized. DMESG doesn't display anything and also no new serial device is connected.
I've been using the firmware provided for the ItsyBitsy cause of the workaround. The workaround is enabled there, or? (At least it seems like it, looking at the GitHub workflow)
Should I maybe try a build without the workaround once?

awawa-dev May 25, 2024
Maintainer Author

This option BOOT_WORKAROUND usually solves our users' problems with these boards and it is rather ultra safe. Turning it off / using the standard firmware probably won't change anything, but you can try the standard firmware to see if the serial port is still there after reconnecting. However, I also came across information that the speed of firmware transfer to the board may be a problem. Or the board may be damaged (rather unlikely). If you have such an opportunity, try to upload the firmware from Windows.

satgit62 May 26, 2024

Hi, I'm trying to set up an Adafruit ItsyBitsy, but it seems to fail at flashing the board properly. I'm using the packed release for the ItsyBitsy SK6812 Neutral, but tested it with the others as well. Nothing besides the USB cable is connected to the board and it is connected to my main PC running Endeavor OS.

Here is the dmesg log:

[19583.600798] usb-storage 5-2.3.4.4:1.0: USB Mass Storage device detected  
[19583.600907] scsi host6: usb-storage 5-2.3.4.4:1.0  
[19584.617960] scsi 6:0:0:0: Direct-Access     RPI      RP2              3    PQ: 0 ANSI: 2  
[19584.619320] sd 6:0:0:0: [sdb] 262144 512-byte logical blocks: (134 MB/128 MiB)  
[19584.619799] sd 6:0:0:0: [sdb] Write Protect is off  
[19584.619802] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00  
[19584.621832] sd 6:0:0:0: [sdb] No Caching mode page found  
[19584.621835] sd 6:0:0:0: [sdb] Assuming drive cache: write through  
[19584.634929]  sdb: sdb1  
[19584.634997] sd 6:0:0:0: [sdb] Attached SCSI removable disk  
---- Here the firmware is put onto the device
[19638.981154] usb 5-2.3.4.4: USB disconnect, device number 33  
[19638.981430] device offline error, dev sdb, sector 260 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0  
[19638.981435] Buffer I/O error on dev sdb1, logical block 259, lost async page write  
[19638.987014] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty  
[19639.339423] usb 5-2.3.4.4: new full-speed USB device number 34 using xhci_hcd  
[19639.508798] usb 5-2.3.4.4: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00  
[19639.508802] usb 5-2.3.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3  
[19639.508803] usb 5-2.3.4.4: Product: Pico  
[19639.508805] usb 5-2.3.4.4: Manufacturer: Raspberry Pi  
[19639.508806] usb 5-2.3.4.4: SerialNumber: DF61B0C2233D1938  
[19639.562835] cdc_acm 5-2.3.4.4:1.0: ttyACM0: USB ACM device

And the corresponding HyperHDR (v20) error:

21:48:29.343 LEDDEVICE              : <ERROR> Dummy device type (file) used, because configured device 'adalight' throws error 'unknown device'

And no LED on the board is shining.

Do you have any hint on how to debug this?

Thank you in advance and for all the hard work!

Hi,
You must also explicitly select and save the ttyACM0 in HyperHDR under LED controller “adalight”, otherwise the message will not appear in HyperHDR Log:

“DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (RGBW => Gain: 179/255, red: 255, green: 255, blue: 180 Welcome! Aw a driver 9.) at 2 msec”

Moerill May 27, 2024

@awawa-dev Thanks for the help! Using windows seems to have fixed it. Now to get everything else to work.

@satgit62 thanks for the hint, but the issue was already beforehand, that the chip didn't want to get properly flashed with the firmware.

grssll · 2024-11-01T08:19:53Z

grssll
Nov 1, 2024

0 replies

HyperSerialPico for Raspberry Pi Pico (Rp2040) #561

awawa-dev May 9, 2023 Maintainer

Boards with built-in 3.3V to 5V level shifter!

One line output model Pimoroni Plasma Stick 2040 W (link)

Two lines output model Pimoroni Plasma 2040 (link)

For ws281x/sk6812 led strips:

For SPI led strips spi1 interface must be used:

8-lanes output Adafruit Feather RP2040 SCORPIO (link)

One lane output Adafruit ItsyBitsy RP2040 (link)

Replies: 33 comments · 162 replies

awawa-dev May 22, 2023 Maintainer Author

awawa-dev Dec 9, 2023 Maintainer Author

awawa-dev May 22, 2023 Maintainer Author

awawa-dev May 22, 2023 Maintainer Author

awawa-dev May 23, 2023 Maintainer Author

awawa-dev May 23, 2023 Maintainer Author

awawa-dev May 24, 2023 Maintainer Author

awawa-dev May 24, 2023 Maintainer Author

awawa-dev May 27, 2023 Maintainer Author

awawa-dev May 31, 2023 Maintainer Author

awawa-dev Jun 4, 2023 Maintainer Author

awawa-dev May 24, 2023 Maintainer Author

awawa-dev May 25, 2023 Maintainer Author

awawa-dev May 25, 2023 Maintainer Author

awawa-dev May 25, 2023 Maintainer Author

awawa-dev May 25, 2023 Maintainer Author

awawa-dev May 31, 2023 Maintainer Author

awawa-dev Oct 23, 2023 Maintainer Author

awawa-dev Oct 30, 2023 Maintainer Author

awawa-dev Jun 15, 2023 Maintainer Author

awawa-dev Jun 15, 2023 Maintainer Author

awawa-dev Jun 15, 2023 Maintainer Author

awawa-dev Jun 18, 2023 Maintainer Author

awawa-dev
May 9, 2023
Maintainer

Replies: 33 comments 162 replies

awawa-dev May 22, 2023
Maintainer Author

awawa-dev Dec 9, 2023
Maintainer Author

awawa-dev May 22, 2023
Maintainer Author

awawa-dev May 22, 2023
Maintainer Author

awawa-dev May 23, 2023
Maintainer Author

awawa-dev May 23, 2023
Maintainer Author

awawa-dev May 24, 2023
Maintainer Author

awawa-dev
May 24, 2023
Maintainer Author

awawa-dev May 27, 2023
Maintainer Author

awawa-dev May 31, 2023
Maintainer Author

awawa-dev Jun 4, 2023
Maintainer Author

awawa-dev May 24, 2023
Maintainer Author

awawa-dev May 25, 2023
Maintainer Author

awawa-dev May 25, 2023
Maintainer Author

awawa-dev May 25, 2023
Maintainer Author

awawa-dev May 25, 2023
Maintainer Author

awawa-dev
May 31, 2023
Maintainer Author

awawa-dev Oct 23, 2023
Maintainer Author

awawa-dev Oct 30, 2023
Maintainer Author

awawa-dev Jun 15, 2023
Maintainer Author

awawa-dev Jun 15, 2023
Maintainer Author

awawa-dev Jun 15, 2023
Maintainer Author

awawa-dev
Jun 18, 2023
Maintainer Author