Beiträge von Zoltán Varga
-
-
https://www.aliexpress.com/ite…042311.0.0.27424c4dAZm0nm
(btw, dont use my color settings. you should open a full white/red/green/blue/cyan/magenta/yellow 1920x1080 picture on your screen, and then use the remote controll page to adjust each color to your wall. set each color to its default value, and then adjust white to white picture green to green etc. onyl that color what you seen on the screen. and when its ok to your eyes, you should save those values at the Configuration/Image Processing page.)
-
The vibrancy is great!. Would you mind detailing your LED strip type and image processing settings.
My vibrancy and intensity is very dull compared to yours.I had to set my gamma on R,G, B to 2.9 in order for my set up to identify black correctly. ie no light on when black. This really reduced the effect.
Would appreciate any tips and advice.
-
Externer Inhalt www.youtube.comInhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.
Just a quick POC video, maybe its a bit distracting, the sides being mirrored on the bottom too, so probably im gonna turn them off,
but the point here is the speed, how smooth and fluid it is.
i set everything that is about FPS or HZ to 60, and its perfectly in sync.thanks hyperion team for the software!
RPi4 drives the 228 leds behind the TV and a NodeMCU drives 180 leds on the bottom connected via USB to the rpi4. (i tried with 4m, 240 leds too, nodemcu had no problem with it, its just too long for my furniture)
-
hi, id ilke to ask someone, to reproduce this:
turn off the rpi, unplug the usb power supply.
and plug in again, while the nodemcu/wled is connected to the USB port (and the nodemcu is also connected to the leds and leds' power supply)mine wont turn on, while nodemcu is connected to the usb, however reboot works just fine.
is it just my rpi4 with libreelec or its the same for you too?
-
Thank you!!!
the key was "auto" and not /dev/ttyUSB1 and 115200 not 1000000.
thanks again!
(now could you redirect me somwhere where i can find a proper how to on installing hyperion o raspbian?
funny thing that i did a few weeks back, and worked, now, after sudo dpkg -i Hyperion-2.0.0-alpha.6-Linux-armv7l.deb,
it installs, but never runs, also no webinterface available - on LibreElec everything works perfectly) -
The log output currently matters... everything else is guessing...
surewhen i save to adalight:and lleave everything as it is preset i got this:
Code[hyperiond LEDDEVICE] (INFO) LedDevice 'adalight' found. [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:56:init()) Adalight header for 240 leds: Ada 0x00 0xef 0xba [hyperiond LEDDEVICE] (INFO) Opening UART: /dev/ttyACM0 [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Error opening device!' [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000
im guesssing:) its bc the device is connected to /dev/ttyUSB1 and not to /dev/ttyACM0so i set to usb1 and i got this:
Code[hyperiond LEDDEVICE] (INFO) LedDevice 'adalight' found. [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:56:init()) Adalight header for 240 leds: Ada 0x00 0xef 0xba [hyperiond LEDDEVICE] (INFO) Opening UART: /dev/ttyUSB1 [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:219:tryOpen()) Setting baud rate to 1000000 [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:235:tryOpen()) Device blocked for 1500 ms [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000
changig back to udpraw (works):
Code[hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:152:closeDevice()) Close UART: /dev/ttyUSB1 [hyperiond LEDDEVICE] (INFO) LedDevice 'udpraw' found. [hyperiond LEDDEVICE] (DEBUG) (ProviderUdp.cpp:40:init()) Successfully parsed 192.168.2.202 as an ip address. [hyperiond LEDDEVICE] (DEBUG) (ProviderUdp.cpp:70:init()) UDP using 192.168.2.202:19446 [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000
BTW:
Hyperion:~ # dmesgCode[ 3793.768653] usb 1-1.3: new full-speed USB device number 8 using xhci_hcd [ 3793.865108] usb 1-1.3: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.54 [ 3793.865117] usb 1-1.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 3793.865123] usb 1-1.3: Product: USB2.0-Ser! [ 3793.869775] ch341 1-1.3:1.0: ch341-uart converter detected [ 3793.874488] usb 1-1.3: ch341-uart converter now attached to ttyUSB1
Hyperion:~ # lsusb
CodeBus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter Bus 001 Device 008: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter Bus 001 Device 006: ID 534d:2109 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-
i dont know it it matters, im on libreelec, rpi4, does it?
(i cant get hyperion up and running on raspbian, i did install the hyperion alpha 6 deb file, but wont start.)
-
How, how did you setup with the nodemcu wled via usb?
What are the exact settings on both end?
I csn manage it work via Wifi, but not via usb, so inneed a step by step guidence.
When i select adalight at configuration/led hardware/led controller
No lights on wled.
Also hyperion turns off led device switch at remote control page.Only updraw works with wled for me
What did you put here on adalight:
Specific Settings
Output pathDefault is /dev/ttyACM0 if i change it to
/dev/TTYUSB01 led device switch stays on, but still no lights on wled side:/Thanks.