Beiträge von TheCoolDave

TheCoolDave · 3. März 2021

Zitat von davieboy

it does sound power related, I ran mine from an old 2.5A phone charger and they worked fine - Turns out they do not draw anything higher than 2.1A....

I am running the PI and the LEDS off the 30a power supply, I did try to use the OEM PI power supply (I did order it when I got the PI), in case of a lack of enough power, this made no change.

The wiring on the LEDs are perfect(no other way to put it here, I know my last set what good but, not perfect), corners were using the no solder connectors and I even soldered them. Power goes in both sides with with steady voltage all around, checked every point with a voltmeter. This was all setup, soldered, everything OFF the TV, the last one I did was on the TV(what a PIA) This was my primary double check when was seeing LAG using GPIO-18. I've gone through this many times, just to be sure.

I'll check the power supply tonight. Maybe the power supply is a little low ? I know there is an adjustment on it. I guess that is the next step.. If it's outputting a little lower voltage it would cause these problems.

Do you think the random shutting off is due to power or timing ?

TheCoolDave · 3. März 2021

Zitat von davieboy

well on my ws2812b setup Red is my biggest consumer of power if thats any help, but yeah that is strange what it is doing in the vids.

few things tho, if you decrease the overall brightness down does the flicker still happen on the red screen.

Have you tried a fresh flash on another SD card?

Thanks for the idea..

OK, Played with brightness for a bit, jumped to 60%, 80%, 90%, 91%, 93%, 95% and 99%....

Dropped to 90% after all, the flashing has appeared to go away and it still is plenty bright (YEA !!!) over 95% it comes back

The question remands here, I had a 5v 10a power supply running all these, never a problem with it, I NOW have a 5v 30a power supply, should I be dealing with power issues on the LEDs ? As ground and 5v go directly to the LEDs from the 30a supply....I got a larger supply so I didn't need to deal with issues like this.

I still get points where the LEDs just shut off, and when the screen changes (like another view) they come back on.

If you watch the videos I posted again, you can see it on the bottom left of the video where it's clearest. Light will be going around and it gets to that corner and all the lights go off, this could happen for split second, or I have seen it as long as 2 seconds... Light should be going and nothing.

Lowering brightness did no change here. Any idea on that one ? Should/could a screen/LED refresh rate be boosted up a little here so it might not do this ?

The SD card is brand new SanDisk (100mb/s rated) 16gb card. I ordered it just for this project as I could not leave a 64gb or 128gb one for just this project as the PI will only be used for this. During testing this was rebuilt a few times. I did try it on the other card (64gb as well, no change)

TheCoolDave · 3. März 2021

Ok, power cord searches to test to see if adding power to the UNO R3 helps with this flashing... Seeing that the UNO can use anything from a 7-12v as long as it's a center positive. Found a few that would fit. Nothing helped...

here is what I tried

1. DC 12v 0.3a
2. DC 12v 1a
3. DC 12v 1.5a (1.5a to 3.25a)

Not of these had any change at all. I'm thinking about trashing the UNO but, is there a sure way to get rid of all lag ?

Or does anyone have an idea, or have seen this before ?

Here is 2 videos I took so you can get an idea on what is going on here(I'll take them down in a few days)...

https://1drv.ms/v/s!AmHdwDuUvhmjg_VBvvvu1ZQ5l2f5Qg?e=DgXOMy

https://1drv.ms/v/s!AmHdwDuUvhmjg_VCIoppG2nZ6lfUKg?e=OZYQ4n

If you watch carefully you will see at some points the lights just stop working for a second or 2, This happens when watching videos as well. On a full RED screen, the flashing is crazy, and in playing back video, on lighter backgrounds flickering happens..

Don't mind the mess of wires, this will be cleaned up soon once this project is final !

I don't want to drop the resolution to 320 X 240, I want to run it at least at 720p so I can get at least SOME detail...

Any idea ??

TheCoolDave · 1. März 2021

Zitat von TPmodding

you playing with the baudrate, but do you aware of that the baudrate at hyperion AND th baudrate on your arduino uno has to be the same?

Yes, both times I made sure they were exactly the same. As if they are not, nothing happens

TheCoolDave · 1. März 2021

Zitat von davieboy

your not having much luck @TheCoolDave , was hoping to hear you were sorted after using that sketch.

So white is still there with diff sketch so were left with signal to UNO or LED's again :LOL::mad:

ok if its not doing it when connected to the GPIO, it must be voltage related as Uno has an extra few v's over the GPIO, did you fit a resistor into it? Could it be something that simple?

Yea, just not having any luck here... What a PIA LOL

No resistor in my setup... As for the UNO, it's plugged into the PI...Hmmmm... The PI has the Video capture and the UNO... maybe it is a power issue... Maybe ?

Power supply has plenty of Amps left...

It will start to flicker on brighter images but, a whole screen of RED, wow, the whole room is flashing !

This setup has been sitting behind my TV with wires all over the place for months, just trying to get it working solid (including 4K HDR movies, that is another thing I have deal with), then I was going mount it to the back of the TV and clean up wires...

Sigh that is not here yet !

TheCoolDave · 28. Februar 2021

OK, got a chance to play with this. Nope, didn't change anything. Well it's flickering a lot slower and really, really laggy now.

I assume the lower baud rate is the reason for this. I did try to chance it back to 500000 and its not laggy any more but, still flashing like crazy on bright images...

What could be doing this ? I cant see that it's a power issue, I did pick up a 30a power supply, even when I setup the LEDs, it's saying I should have 16.7a power suppy, so plenty left.

This was working perfect (besides very laggy) when using GPIO-18 and I did plenty of tests with bright images and bouncing things to see the lag...I never noticed flashing on it before I went to the UNO..

TheCoolDave · 28. Februar 2021

Zitat von davieboy

try this one mate
https://github.com/hyperion-pr…ino/adalight/adalight.ino

Its the official sketch and @Lord-Grey tweaked it the other day - bonus

change line 21 & 24
comment out 34 and uncomment 35

leave the rest as it is and upload it to the mcu, make sure Hyperion baud is at 115200 in the dashboard, test it out, if all is good then increase the baud rate a stage at a time until your happy.

After i wrote this i noticed this, you originally posted you had WS2812B - 3 wire LEDS but your sketch is for 4 wire LEDS, I do remember you ordering another set but cant remember what you settled with, if you do have the 3 wire strip you only need to alter line 21 in the sketch, the rest should be fine and matches your setup.

Alles anzeigen

Thanks, I'll try that, To be honest with you, I only really knew about using WS2812B as that is all the YouTube videos go with. If I knew about APA102 before ordering them, I would of given them a shot...

I'll try this later today just because I am busy on a project this morning...

Thanks !

TheCoolDave · 28. Februar 2021

Zitat von davieboy

congrats on the delay mate, Does tweaking the smoothing help any?

I tried a bunch of things, lowed the res, the little lag that is left it helped but, doing tests, a red screen leaves the whole room flashing, it's pretty bad.

Zitat von TPmodding

which sketch did you use for the arduino?

I kind of loosely followed this video as he setup the same type of layout. I was reading that some changes needed to be there for 255+ LEDs... this was a updated script for it.

(4) DIY Hyperion Ambient TV Light Project (Raspberry Pi + Arduino) Complete Setup - YouTube

This is the exact code I used in my UNO...

C

// FastLED - Version: Latest
#include <FastLED.h>


#include "FastLED.h"
// How many leds in your strip?
#define NUM_LEDS 255
// For led chips like Neopixels, which have a data line, ground, and power, you just
// need to define DATA_PIN.  For led chipsets that are SPI based (four wires - data, clock,
// ground, and power), like the LPD8806 define both DATA_PIN and CLOCK_PIN
#define DATA_PIN 6
#define CLOCK_PIN 13
#define COLOR_ORDER GRB
// Adalight sends a "Magic Word" (defined in /etc/boblight.conf) before sending the pixel data
uint8_t prefix[] = {'A', 'd', 'a'}, hi, lo, chk, i;
// Baudrate, higher rate allows faster refresh rate and more LEDs (defined in /etc/boblight.conf)
#define serialRate 500000
// #define serialRate 460800
// Define the array of leds
CRGB leds[NUM_LEDS];
void setup() {
      // Uncomment/edit one of the following lines for your leds arrangement.
      // FastLED.addLeds<TM1803, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<TM1804, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<TM1809, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<WS2811, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<WS2812, DATA_PIN, RGB>(leds, NUM_LEDS);
         FastLED.addLeds<WS2812B, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<NEOPIXEL, DATA_PIN>(leds, NUM_LEDS);
      // FastLED.addLeds<UCS1903, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<UCS1903B, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<GW6205, DATA_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<GW6205_400, DATA_PIN, RGB>(leds, NUM_LEDS);

      // FastLED.addLeds<WS2801, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<SM16716, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<LPD8806, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<WS2801, DATA_PIN, CLOCK_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<SM16716, DATA_PIN, CLOCK_PIN, RGB>(leds, NUM_LEDS);
      // FastLED.addLeds<LPD8806, DATA_PIN, CLOCK_PIN, RGB>(leds, NUM_LEDS);

        // initial RGB flash
        LEDS.showColor(CRGB(255, 0, 0));
        delay(500);
        LEDS.showColor(CRGB(0, 255, 0));
        delay(500);
        LEDS.showColor(CRGB(0, 0, 255));
        delay(500);
        LEDS.showColor(CRGB(0, 0, 0));

        Serial.begin(serialRate);
        Serial.print("Ada\n"); // Send "Magic Word" string to host
}
void loop() {
  // wait for first byte of Magic Word
  for(i = 0; i < sizeof prefix; ++i) {
    waitLoop: while (!Serial.available()) ;;
    // Check next byte in Magic Word
    if(prefix[i] == Serial.read()) continue;
    // otherwise, start over
    i = 0;
    goto waitLoop;
  }
  // Hi, Lo, Checksum
  while (!Serial.available()) ;;
  hi=Serial.read();
  while (!Serial.available()) ;;
  lo=Serial.read();
  while (!Serial.available()) ;;
  chk=Serial.read();
  // if checksum does not match go back to wait
  if (chk != (hi ^ lo ^ 0x55))
  {
    i=0;
    goto waitLoop;
  }
  memset(leds, 0, NUM_LEDS * sizeof(struct CRGB));
  // read the transmission data and set LED values
  for (uint16_t i = 0; i < NUM_LEDS; i++) {
    byte r, g, b;  
    while(!Serial.available());
    r = Serial.read();
    while(!Serial.available());
    g = Serial.read();
    while(!Serial.available());
    b = Serial.read();
    leds[i].r = r;
    leds[i].g = g;
    leds[i].b = b;
  }
  // shows new values
FastLED.show();


    }

Alles anzeigen

As I am using 255 LEDs, no more, should go with a different code here ?

TheCoolDave · 27. Februar 2021

Hey all !

In my last thread I, replaced the LEDs. I was using GPIO 18 but, found the delay too much and parts of the time, the lights would just stop working for like 2-3 seconds, and then "catch up". I rebuilt, added in the UNO as the controller and lag seems almost gone. The stop working problem is still there a little but, the flashing on bright images is just crazy.

A full screen of RED will make the whole room flashing because of this... White, yellow, does the same thing but, mixing darker colors seem fine, no flashing till a video with a very light background and flashing returns.

This was not happening when I was using GPIO-18 connection but, the LAG was unbearable.

Hardware for reference...

Raspberry PI 3B
255 W2812b LEDs attached to the TV
5v 30a power supply..
A 4K 60hz grabber ( )
UNO R3

Connectors and wires...
I used these for wires and the connectors to the end to avoid soldering wire to LEDs..

Used these for corners but, soldered them on so they would not slip off (common with these connectors)

Hook up
HDMI from Denon AVR 2nd(set to mirror tv) room out to HDMI grabber, that goes into the PI, USB out of the PI goes the UNO. The data connection is on PIN 6 on the UNO, The connections on the UNO are soldered in, this is ground and data.

The LEDS have power/ground going at the start and the end of the LEDs, so no low points in power in the LEDs. I did use the wire that came with the wire connectors, the start of the LEDs are connected with the factory connection.

Power for PI is run off the 30a power supply (but, also tried the original 2.5a power supply with no change). Ground from the 30a power supply is connected to the UNO and PI. Confirmed connection on ground from the UNO to the middle of the LEDs with no problem (voltmeter)

Hyperion settings are nothing too crazy, Adalight for type of controller, 255 LEDs, and GRB Order.

Capture settings are
Device Resolution: 1280 X 720
Frames per second: 60
Size decimation: 8

Here are the logs. Anyone see anything that could be causing this flashing ? Common fix for this is for a common ground, I did that.

Code

2021-02-27T16:37:48.159Z [hyperiond DAEMON] (INFO) CEC handler created
2021-02-27T16:37:48.183Z [hyperiond EFFECTFILES] (INFO) 39 effects loaded from directory :/effects/
2021-02-27T16:37:48.189Z [hyperiond EFFECTFILES] (INFO) 22 effect schemas loaded from directory :/effects/schema/
2021-02-27T16:37:48.192Z [hyperiond EFFECTFILES] (INFO) 0 effects loaded from directory /home/pi/.hyperion/custom-effects
2021-02-27T16:37:48.281Z [hyperiond SETTINGSMGR] (DEBUG) (SettingsManager.cpp:109:SettingsManager()) Settings database initialized
2021-02-27T16:37:48.287Z [hyperiond BLACKBORDER] (DEBUG) (BlackBorderProcessor.cpp:64:handleSettingsUpdate()) Set mode to: default
2021-02-27T16:37:48.288Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Blackborder detector: enabled
2021-02-27T16:37:48.321Z [hyperiond DAEMON] (INFO) set screen capture device to 'dispmanx'
2021-02-27T16:37:48.321Z [hyperiond DISPMANXGRABBER] (DEBUG) (Grabber.cpp:30:setVideoMode()) Set videomode to 0
2021-02-27T16:37:48.324Z [hyperiond DISPMANXGRABBER] (INFO) Display opened with resolution: 720x480
2021-02-27T16:37:48.324Z [hyperiond DISPMANXGRABBER] (DEBUG) (Grabber.cpp:90:setWidthHeight()) Set new width: 80, height: 45 for capture
2021-02-27T16:37:48.325Z [hyperiond DAEMON] (INFO) DISPMANX frame grabber created
2021-02-27T16:37:48.326Z [hyperiond V4L2:/DEV/VIDEO0] (DEBUG) (Grabber.cpp:30:setVideoMode()) Set videomode to 0
2021-02-27T16:37:48.410Z [hyperiond V4L2:/DEV/VIDEO0] (DEBUG) (Grabber.cpp:90:setWidthHeight()) Set new width: 1280, height: 720 for capture
2021-02-27T16:37:48.411Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal threshold set to: {12, 12, 12}
2021-02-27T16:37:48.411Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) CEC detection is now disabled
2021-02-27T16:37:48.411Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal detection area set to: 0.900000,0.900000 x 0.980000,0.980000
2021-02-27T16:37:48.412Z [hyperiond DAEMON] (DEBUG) (hyperiond.cpp:630:handleSettingsUpdate()) V4L2 grabber created
2021-02-27T16:37:48.413Z [hyperiond JSONSERVER] (DEBUG) (JsonServer.cpp:28:JsonServer()) Created instance
2021-02-27T16:37:48.413Z [hyperiond JSONSERVER] (INFO) Started on port 19444
2021-02-27T16:37:48.337Z [hyperiond LEDDEVICE] (INFO) Start LedDevice 'adalight'.
2021-02-27T16:37:48.337Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Smoothing: enabled
2021-02-27T16:37:48.338Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2021-02-27T16:37:48.338Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:148:init()) deviceConfig: [{"colorOrder":"grb","currentLedCount":255,"delayAfterConnect":0,"hardwareLedCount":255,"latchTime":30,"lightberry_apa102_mode":false,"output":"/dev/ttyUSB0","rate":500000,"rewriteTime":1000,"type":"adalight"}]
2021-02-27T16:37:48.339Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:407:setLatchTime()) LatchTime updated to 30ms
2021-02-27T16:37:48.340Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:428:setRewriteTime()) Refresh interval = 1000ms
2021-02-27T16:37:48.340Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:434:setRewriteTime()) RewriteTime updated to 1000ms
2021-02-27T16:37:48.341Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:36:init()) DeviceType   : adalight
2021-02-27T16:37:48.341Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:37:init()) LedCount     : 255
2021-02-27T16:37:48.341Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:38:init()) ColorOrder   : grb
2021-02-27T16:37:48.342Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:39:init()) RefreshTime  : 1000
2021-02-27T16:37:48.342Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:40:init()) LatchTime    : 30
2021-02-27T16:37:48.342Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:52:init()) deviceName   : ttyUSB0
2021-02-27T16:37:48.342Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:53:init()) AutoDevice   : 0
2021-02-27T16:37:48.343Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:54:init()) baudRate_Hz  : 500000
2021-02-27T16:37:48.343Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:55:init()) delayAfCon ms: 0
2021-02-27T16:37:48.343Z [hyperiond LEDDEVICE] (DEBUG) (LedDeviceAdalight.cpp:59:init()) Adalight header for 255 leds: Ada 0x00 0xfe 0xab
2021-02-27T16:37:48.344Z [hyperiond LEDDEVICE] (INFO) Opening UART: ttyUSB0
2021-02-27T16:37:48.344Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:141:tryOpen()) _rs232Port.open(QIODevice::ReadWrite): ttyUSB0, Baud rate [500000]bps
2021-02-27T16:37:48.351Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) Previous line repeats 1 times
2021-02-27T16:37:48.351Z [hyperiond FLATBUFCONN] (INFO) Connecting to Hyperion: 127.0.0.1:19401
2021-02-27T16:37:48.363Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'System/COLOR' with priority 0 as inactive
2021-02-27T16:37:48.364Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:207:setInput()) Priority 0 is now active
2021-02-27T16:37:48.364Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 0
2021-02-27T16:37:48.364Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[0], previousPriority[255]
2021-02-27T16:37:48.364Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-02-27T16:37:48.365Z [hyperiond HYPERION] (INFO) Initial foreground color set (1 1 11)
2021-02-27T16:37:48.366Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'System/V4L' with priority 200 as inactive
2021-02-27T16:37:48.366Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) V4L capture device: enabled
2021-02-27T16:37:48.435Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) configured v4l device: /dev/video0
2021-02-27T16:37:48.435Z [hyperiond V4L2:/DEV/VIDEO0] (DEBUG) (V4L2Grabber.cpp:582:init_device()) Set device input to: Camera 1
2021-02-27T16:37:48.437Z [hyperiond V4L2:/DEV/VIDEO0] (DEBUG) (V4L2Grabber.cpp:696:init_device()) Set resolution to width=1280 height=720
2021-02-27T16:37:48.439Z [hyperiond V4L2:/DEV/VIDEO0] (DEBUG) (V4L2Grabber.cpp:713:init_device()) Set framerate to 10 fps
2021-02-27T16:37:48.439Z [hyperiond V4L2:/DEV/VIDEO0] (DEBUG) (V4L2Grabber.cpp:735:init_device()) Pixel format=YUYV
2021-02-27T16:37:48.450Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Started
2021-02-27T16:37:48.451Z [hyperiond V4L2:/dev/video0] (DEBUG) (GrabberWrapper.cpp:48:start()) Grabber start()
2021-02-27T16:37:48.367Z [hyperiond BOBLIGHT] (DEBUG) (BoblightServer.cpp:28:BoblightServer()) Instance created
2021-02-27T16:37:48.452Z [hyperiond HYPERION] (INFO) Hyperion instance 'First LED Hardware instance' has been started
2021-02-27T16:37:48.401Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:146:tryOpen()) portName:          ttyUSB0
2021-02-27T16:37:48.402Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:147:tryOpen()) systemLocation:    /dev/ttyUSB0
2021-02-27T16:37:48.402Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:148:tryOpen()) description:       USB2.0-Serial
2021-02-27T16:37:48.403Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:149:tryOpen()) manufacturer:      1a86
2021-02-27T16:37:48.403Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:150:tryOpen()) productIdentifier: 0x7523
2021-02-27T16:37:48.403Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:151:tryOpen()) vendorIdentifier:  0x1a86
2021-02-27T16:37:48.404Z [hyperiond LEDDEVICE] (DEBUG) (ProviderRs232.cpp:152:tryOpen()) serialNumber:     
2021-02-27T16:37:48.407Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: enabled
2021-02-27T16:37:48.424Z [hyperiond FLATBUFSERVER] (INFO) Started on port 19400
2021-02-27T16:37:48.426Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:33:initServer()) Initialize Webserver
2021-02-27T16:37:48.425Z [hyperiond PROTOSERVER] (INFO) Started on port 19445
2021-02-27T16:37:48.427Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:33:initServer()) Initialize Webserver
2021-02-27T16:37:48.555Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:91:handleSettingsUpdate()) Apply Webserver settings
2021-02-27T16:37:48.555Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:91:handleSettingsUpdate()) Apply Webserver settings
2021-02-27T16:37:48.556Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:109:handleSettingsUpdate()) Set document root to: :/webconfig
2021-02-27T16:37:48.556Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:109:handleSettingsUpdate()) Set document root to: :/webconfig
2021-02-27T16:37:48.557Z [hyperiond WEBSERVER] (INFO) Started on port 8090 name 'Hyperion Webserver'
2021-02-27T16:37:48.575Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:175:handleSettingsUpdate()) Setup SSL certificate
2021-02-27T16:37:48.576Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:191:handleSettingsUpdate()) Setup private SSL key
2021-02-27T16:37:48.577Z [hyperiond WEBSERVER] (INFO) Started on port 8092 name 'Hyperion Webserver'
2021-02-27T16:37:48.671Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 200 is now active
2021-02-27T16:37:51.580Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:315:setCurrentTime()) Timeout clear for priority 0
2021-02-27T16:37:51.580Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 0
2021-02-27T16:37:51.581Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[0], previousPriority[0]
2021-02-27T16:37:51.830Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 200
2021-02-27T16:37:51.833Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[200], previousPriority[0]
2021-02-27T16:41:50.762Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.0.37
2021-02-27T16:41:50.763Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.0.37' switch to Hyperion instance 0
2021-02-27T16:42:14.640Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal lost
2021-02-27T16:42:15.489Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 200 is now inactive
2021-02-27T16:42:15.489Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255
2021-02-27T16:42:15.490Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[200]
2021-02-27T16:42:15.490Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off
2021-02-27T16:42:17.437Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal detected
2021-02-27T16:42:17.437Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 200 is now active
2021-02-27T16:42:17.437Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 200
2021-02-27T16:42:17.438Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[200], previousPriority[255]
2021-02-27T16:42:17.438Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-02-27T17:03:18.997Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.0.37

Alles anzeigen

TheCoolDave · 22. Februar 2021

OK, installed the LEDs on Saturday. The problem that I am seeing now is the LEDs a very, very LAGGY. I did go into video capture settings and changed the resolution to 320 X 240 60fps as people said to do, in the preview window, it's just a blurry blob of color. This helped a lot but, still laggy there.

A lot of the time it will look like timing is fine but, all of a sudden it stops(no color) and then catches up. Should I add a Arduino instead of running to the GPIO port ? Will this solve the lag issue here ?

I saw this thread and looks like this could fix this..
Ardruino or GPIO | Hyperion - Forum (hyperion-project.org)

Also, does anyone know of a budget friendly capture device that will do 4K 60 AND HDR (4K video is fine but, as soon as I play HDR content, the LEDs go off) ?

TheCoolDave · 14. Februar 2021

OK, today the LEDs came in, This time I did things a little better, experience here is the key. I won't be soldering directly the strips (if I can completely avoid it), I am going to use the built in clips and solder the wire together with heat shrink it. I am going to use the corner pieces but, I will do a little solder in there, and heat shrink every end. It will be easier due to having my LED count already there.

Well after soldering a lot cable, so I could give myself room to work and be long enough for the back of the TV, I plugged in the LEDs and booted everything up. The LEDs lit up ! Not sure exactly what caused the current LEDs go bad. They were all working before, sigh...

I need to go out and get some double sided tape and some other things before mounting but, looks good so far. Maybe later this week.

I do see one annoyance, when there is no signal, there is a rainbow color that shows, like this...

How to you keep the LEDs off when this is up ?

TheCoolDave · 13. Februar 2021

Zitat von jeroen warmerdam

sometimes hardware just doesn't want to do it, the GPIO you are using is for PWM that is really diffrent than SPI.
i have a tool for testing your SPI 0 device on GPIO MOSI to MISO but you can't use that for PWM GPIO thus its only one PIN going data OUT.

so indeed it looks like all systems is running/ rightfull connected but still no lights.
then i suspect the ledstrip, they are very sensitive / sometimes bad builds or cheap knock offs are the cause of no firing at all.
most people want to have the cheapiest lights possible because they are invested in this setup so much... thats why things go wrong sometimes and they purchase a bad or lesser strip to even out the costs. The vendors are not all selling the same, buy from BTF and you know that you have a good realible quality strip.
A strip for 15 euro, strand of 200 lights cannot be a high quality, its that simple.

i also don't understand why everybody is going for the ws2812b ledstrip ( 3 lines) when a 4 line type like ws2801 or APA102 is much more fluently and capable of calculating the colours much better. Maybe its a personal preference who knows, or its in the Youtube video's....

goodluck with your new ledstrip

Alles anzeigen

Thanks for the info. I came on to this project via YouTube, one of those things I have always wanted from seeing a actual Philips Ambilight TV in person, many years ago.

Every video out there, that I have seen, suggests to use ws2812b LEDs, I've never saw anyone use anything else. Trust me, I looked over a lot of videos to find out EXACTLY what I needed to do here and what is the best hardware. Also looked to find possible issues as well, reading though many comments on it.. I like to do a lot of homework on new projects that I don't know a lot about.

If I saw your post yesterday, I would of looked at other LEDs. It's too late now that they have already shipped.

Thanks again for info, you learn something new every day ! If I end up doing this again, or this does not work, I will look at ws2801 or APA102 LEDs...

TheCoolDave · 13. Februar 2021

Zitat von davieboy

Its looking that way man, I'm out of ideas and swaying back towards hardware

I know. What the heck? Tried Different PI, reinstall the OS about 5-6 times. Settings should be correct, video image and LED placement look perfect, Voltage is there, Tested different cables to the LEDs data, power, nothing. This all worked perfectly before what could of happened ?????

This is what I used to setup the orignal system..

(2) NEW! DIY Ambilight Tutorial, For ANY HDMI Device! - EASY!! The Mad Scientist - YouTube

So, it's not the PI, It's not the cables (as I replaced all and even tried different ways to run the cable), it does not appear to the software.

Only other thing to try is LEDs... $43 later, it will be here tomorrow. Not putting on the TV, will be bench testing before doing anything.

At least one thing, I had the white LED strip, the back of my TV is black, so I ordered black ones... If anything...sigh..

To think, this is a video I took of my system 2 weeks before I attempted the "upgrade"( a few people we asking about what it looks like)... Not sure what could of happened here..

https://1drv.ms/v/s!AmHdwDuUvhmjg_U6o49yzySrwcmLxw?e=1zVggG

Thanks for everyone help, a lot of good ideas here, maybe it will help others

I guess I am done till new LEDs show up

TheCoolDave · 13. Februar 2021

Zitat von Lord-Grey

Unfortunately, I do not spot anything which might be of help from a software point of view (and I am not too familiar with this type of LED).
You might have a latchtime > 0, e.g. 30ms or even higher. Maybe teh LEDs cannot cope with the number of updates.

In addition, if the LED-Device on in the Remote Control?

Plus does it work to run a simple color effect?

Alles anzeigen

On the Latch time, I adjusted from 0 to 30ms, no change.

Only time LEDs have lit up from doing this way, is when I shut power off on the device, red goes around to a bunch of LEDs. Nothing more. Running a simple color effect does nothing.

I double checked voltage on the LEDs, getting 5v across the LEDs fine. Checked at the start and it was around 4.8v at the end of LEDs. I ran a jumper with clip directly from GPIO-18 to data pin on the LEDs and rebooted (just to make sure all wires are connected with no issues), no change, no LEDs are lighting up.

I did order new LEDs from Amazon with all connectors and that, I will test tomorrow when they come in. Not on the TV but, out of the package, if they light up, my LEDs are fried for some reason.. I am running out of options to try here. Not really sure where to go next on this...

The LED device is on

TheCoolDave · 13. Februar 2021

Zitat von davieboy

You must of been editing that 1st post @TheCoolDave I never saw the debug then, hopefully @Lord-Grey or @TPmodding will spot something, looks good to me, unsure if that effect priority would cause problems.

Can you grab a screenshot of your Configuration -> General section

Here you go...Thanks

TheCoolDave · 13. Februar 2021

Zitat von davieboy

@TheCoolDave a picture speaks 1000 words

https://hyperion-project.org/t…p-ideas.11332/#post-33997

We could all spend days beating about the bush as you have already been at it for weeks, but everyone's hardware and setup is different and without actually seeing the hardware or config/logs you are just throwing mud at the wall and hoping one sticks - never a bad thing but you have to draw the line at somepoint

Here is images of my setup, I really didn't change anything anywhere else. I am setup on GPIO-18 tried a few others, noticed that 16 could not be used via the log.

Let me know if you need any other settings
.

TheCoolDave · 13. Februar 2021

Zitat von jeroen warmerdam

maybe i break in in this conversation, but did you ( i dont see it mentioned) power your ledstrip FROM BOTH SIDES??

so beginning and end connected to GND and 5 volt line

No, Just one point of power. All 3 go in on one spot. Should I TRY to run from the start and the end ?

This all worked before like this, so it's why I am not trying rewire the LEDS.

Zitat von davieboy

I was wondering the same @Hocus but @TheCoolDave ran the LibreELEC install

Has anyone tried Platform capture instead of USB just in case?

either way

If you can get to the GUI go to System -> Log
change to Debug -> Save Settings

Reload the page - you should now see a error box appear, check your Configuration Section again, make sure LED Hardware, Controller and Layout are correct, if using USB go into Capturing Hardware then make sure It is enabled in Instance Capture, The USB Capture section you should be able to change from automatic to manually define your device if it is being detected by the o/s. Go to the Remote Control tab and make sure the correct Components are on and not set to off, You should see the Card in the Source Selection Section with a status next to it.

If its not lighting up after that go back to the System -> Log and see what's in that box

The Hyperion android app id try that and see if you can control the LEDS directly from there as its so much easier than using the GUI to set an effect or solid color, connects directly with fast and instantaneous reaction.

Failing that, screenshot your settings and post your logs,
Good Luck

Alles anzeigen

I tried a 2nd PI no change. Here is the logs from booting up with the 2nd PI. No noticed differences between logs for mine or the one I borrowed.

I am going to remove the 2nd PI and put it away, I don't want to damage or anything else, it's from my office.

Checked everything, enabled USB capture, confirmed in preview window that live TV was playing and the led layout look as it should.

Code

2019-04-11T16:28:41.460Z [hyperiond DAEMON] (INFO) CEC handler created
2019-04-11T16:28:41.483Z [hyperiond EFFECTFILES] (INFO) 39 effects loaded from directory :/effects/
2019-04-11T16:28:41.489Z [hyperiond EFFECTFILES] (INFO) 22 effect schemas loaded from directory :/effects/schema/
2019-04-11T16:28:41.493Z [hyperiond EFFECTFILES] (INFO) 0 effects loaded from directory /storage/hyperion/custom-effects
2019-04-11T16:28:41.576Z [hyperiond SETTINGSMGR] (DEBUG) (SettingsManager.cpp:109:SettingsManager()) Settings database initialized
2019-04-11T16:28:41.582Z [hyperiond BLACKBORDER] (DEBUG) (BlackBorderProcessor.cpp:64:handleSettingsUpdate()) Set mode to: default
2019-04-11T16:28:41.582Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Blackborder detector: enabled
2019-04-11T16:28:41.620Z [hyperiond DAEMON] (INFO) set screen capture device to 'dispmanx'
2019-04-11T16:28:41.620Z [hyperiond DISPMANXGRABBER] (DEBUG) (Grabber.cpp:30:setVideoMode()) Set videomode to 0
2019-04-11T16:28:41.622Z [hyperiond DISPMANXGRABBER] (INFO) Display opened with resolution: 720x480
2019-04-11T16:28:41.623Z [hyperiond DISPMANXGRABBER] (DEBUG) (Grabber.cpp:90:setWidthHeight()) Set new width: 80, height: 45 for capture
2019-04-11T16:28:41.623Z [hyperiond DAEMON] (INFO) DISPMANX frame grabber created
2019-04-11T16:28:41.624Z [hyperiond V4L2:AUTO] (DEBUG) (Grabber.cpp:30:setVideoMode()) Set videomode to 0
2019-04-11T16:28:41.626Z [hyperiond V4L2:AUTO] (INFO) Signal threshold set to: {12, 12, 12}
2019-04-11T16:28:41.627Z [hyperiond V4L2:AUTO] (INFO) CEC detection is now disabled
2019-04-11T16:28:41.627Z [hyperiond V4L2:AUTO] (INFO) Signal detection is now disabled
2019-04-11T16:28:41.627Z [hyperiond V4L2:AUTO] (INFO) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2019-04-11T16:28:41.627Z [hyperiond DAEMON] (DEBUG) (hyperiond.cpp:630:handleSettingsUpdate()) V4L2 grabber created
2019-04-11T16:28:41.640Z [hyperiond JSONSERVER] (DEBUG) (JsonServer.cpp:28:JsonServer()) Created instance
2019-04-11T16:28:41.659Z [hyperiond JSONSERVER] (INFO) Started on port 19444
2019-04-11T16:28:41.626Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Smoothing: enabled
2019-04-11T16:28:41.627Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2019-04-11T16:28:41.626Z [hyperiond LEDDEVICE] (INFO) Start LedDevice 'ws281x'.
2019-04-11T16:28:41.629Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:148:init()) deviceConfig: [{"colorOrder":"rgb","currentLedCount":253,"dma":5,"gpio":18,"hardwareLedCount":253,"invert":false,"latchTime":0,"leds":256,"pwmchannel":0,"rewriteTime":1000,"rgbw":false,"type":"ws281x","whiteAlgorithm":"subtract_minimum"}]
2019-04-11T16:28:41.629Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:407:setLatchTime()) LatchTime updated to 0ms
2019-04-11T16:28:41.629Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:428:setRewriteTime()) Refresh interval = 1000ms
2019-04-11T16:28:41.629Z [hyperiond LEDDEVICE] (DEBUG) (LedDevice.cpp:434:setRewriteTime()) RewriteTime updated to 1000ms
2019-04-11T16:28:41.630Z [hyperiond LEDDEVICE] (DEBUG) (LedDeviceWS281x.cpp:59:init()) ws281x strip type : 1050624
2019-04-11T16:28:41.640Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) Previous line repeats 1 times
2019-04-11T16:28:41.640Z [hyperiond FLATBUFCONN] (INFO) Connecting to Hyperion: 127.0.0.1:19401
2019-04-11T16:28:41.660Z [hyperiond EFFECTENGINE] (INFO) Run effect "Rainbow swirl fast" on channel 0
2019-04-11T16:28:41.670Z [hyperiond FLATBUFSERVER] (INFO) Started on port 19400
2019-04-11T16:28:41.672Z [hyperiond PROTOSERVER] (INFO) Started on port 19445
2019-04-11T16:28:41.673Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:33:initServer()) Initialize Webserver
2019-04-11T16:28:41.673Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:33:initServer()) Initialize Webserver
2019-04-11T16:28:41.805Z [hyperiond EFFECTENGINE] (DEBUG) (EffectEngine.cpp:183:runEffectScript()) Start the effect: name [Rainbow swirl fast], smoothCfg [2]
2019-04-11T16:28:41.805Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'System/EFFECT' with priority 0 as inactive
2019-04-11T16:28:41.805Z [hyperiond HYPERION] (INFO) Initial foreground effect 'Rainbow swirl fast' started
2019-04-11T16:28:41.806Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'System/GRABBER' with priority 250 as inactive
2019-04-11T16:28:41.807Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Framegrabber: enabled
2019-04-11T16:28:41.809Z [hyperiond Dispmanx] (DEBUG) (GrabberWrapper.cpp:48:start()) Grabber start()
2019-04-11T16:28:41.807Z [hyperiond BOBLIGHT] (DEBUG) (BoblightServer.cpp:28:BoblightServer()) Instance created
2019-04-11T16:28:41.810Z [hyperiond HYPERION] (INFO) Hyperion instance 'GPIO-18' has been started
2019-04-11T16:28:41.808Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: enabled
2019-04-11T16:28:41.909Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 250 is now active
2019-04-11T16:28:41.910Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 0
2019-04-11T16:28:41.910Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) cfg [2]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2019-04-11T16:28:41.910Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[0], previousPriority[255]
2019-04-11T16:28:41.910Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2019-04-11T16:28:41.924Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:91:handleSettingsUpdate()) Apply Webserver settings
2019-04-11T16:28:41.924Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:109:handleSettingsUpdate()) Set document root to: :/webconfig
2019-04-11T16:28:41.925Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:91:handleSettingsUpdate()) Apply Webserver settings
2019-04-11T16:28:41.925Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:109:handleSettingsUpdate()) Set document root to: :/webconfig
2019-04-11T16:28:41.926Z [hyperiond WEBSERVER] (INFO) Started on port 8090 name 'Hyperion Webserver'
2019-04-11T16:28:42.086Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:175:handleSettingsUpdate()) Setup SSL certificate
2019-04-11T16:28:42.087Z [hyperiond WEBSERVER] (DEBUG) (WebServer.cpp:191:handleSettingsUpdate()) Setup private SSL key
2019-04-11T16:28:42.087Z [hyperiond WEBSERVER] (INFO) Started on port 8092 name 'Hyperion Webserver'
2019-04-11T16:28:42.105Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 0 is now active
2019-04-11T16:28:44.909Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:315:setCurrentTime()) Timeout clear for priority 0
2019-04-11T16:28:44.910Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 0
2019-04-11T16:28:44.910Z [hyperiond SMOOTHING] (DEBUG) (LinearColorSmoothing.cpp:701:selectConfig()) cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2019-04-11T16:28:44.910Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[0], previousPriority[0]
2021-02-13T15:44:41.599Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 250
2021-02-13T15:44:41.601Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[250], previousPriority[0]
2021-02-13T15:46:39.084Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.0.37
2021-02-13T15:46:39.085Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.0.37' switch to Hyperion instance 0
2021-02-13T15:46:55.556Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:161:registerInput()) Register new input 'System/V4L' with priority 240 as inactive
2021-02-13T15:46:55.556Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) V4L capture device: enabled
2021-02-13T15:46:55.558Z [hyperiond V4L2:AUTO] (INFO) available V4L2 devices:
    /dev/video0    USB Video: USB Video


2021-02-13T15:46:55.558Z [hyperiond V4L2:AUTO] (INFO) search for usable video devices
2021-02-13T15:46:55.559Z [hyperiond V4L2:AUTO] (INFO) test v4l device: /dev/video0
2021-02-13T15:46:55.560Z [hyperiond V4L2:AUTO] (DEBUG) (V4L2Grabber.cpp:696:init_device()) Set resolution to width=1920 height=1080
2021-02-13T15:46:55.561Z [hyperiond V4L2:AUTO] (DEBUG) (V4L2Grabber.cpp:713:init_device()) Set framerate to 5 fps
2021-02-13T15:46:55.561Z [hyperiond V4L2:AUTO] (DEBUG) (V4L2Grabber.cpp:735:init_device()) Pixel format=YUYV
2021-02-13T15:46:55.580Z [hyperiond V4L2:AUTO] (INFO) found usable v4l2 device: /dev/video0 (USB Video: USB Video)
2021-02-13T15:46:55.582Z [hyperiond V4L2:AUTO] (INFO) Started
2021-02-13T15:46:55.582Z [hyperiond V4L2:auto] (DEBUG) (GrabberWrapper.cpp:48:start()) Grabber start()
2021-02-13T15:46:55.557Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:270:clearInput()) Removed source priority 250
2021-02-13T15:46:55.557Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255
2021-02-13T15:46:55.557Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[250]
2021-02-13T15:46:55.557Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off
2021-02-13T15:46:55.558Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Framegrabber: disabled
2021-02-13T15:46:55.582Z [hyperiond Dispmanx] (DEBUG) (GrabberWrapper.cpp:58:stop()) Grabber stop()
2021-02-13T15:46:56.013Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 240 is now active
2021-02-13T15:46:56.013Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 240
2021-02-13T15:46:56.016Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[240], previousPriority[255]
2021-02-13T15:46:56.016Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on
2021-02-13T15:47:04.021Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.0.37

Alles anzeigen

TheCoolDave · 12. Februar 2021

Zitat von davieboy

I was wondering the same @Hocus but @TheCoolDave ran the LibreELEC install

Has anyone tried Platform capture instead of USB just in case?

either way

If you can get to the GUI go to System -> Log
change to Debug -> Save Settings

Reload the page - you should now see a error box appear, check your Configuration Section again, make sure LED Hardware, Controller and Layout are correct, if using USB go into Capturing Hardware then make sure It is enabled in Instance Capture, The USB Capture section you should be able to change from automatic to manually define your device if it is being detected by the o/s. Go to the Remote Control tab and make sure the correct Components are on and not set to off, You should see the Card in the Source Selection Section with a status next to it.

If its not lighting up after that go back to the System -> Log and see what's in that box

The Hyperion android app id try that and see if you can control the LEDS directly from there as its so much easier than using the GUI to set an effect or solid color, connects directly with fast and instantaneous reaction.

Failing that, screenshot your settings and post your logs,
Good Luck

Alles anzeigen

I'll enable tonight while doing other testing. Man I want this to work. I did buy replacement LEDs but, if I run into the same problem, I will just return them...

I have the App on my phone from my last setup, I'll try it too...

Did get a PI I could borrow for the weekend...

TheCoolDave · 12. Februar 2021

Zitat von davieboy

idk man, you seem adamant your wiring is good, but i would of expected to see this with the wire unplugged from the gpio - from start of wire to the first connection - something close to zero maybe 0.3ohm, at the 2nd led id expect it to be higher as your also measuring the resistance in the 1st led, touching both leads together should give you 0.00 ohms but there's usually resistance in peoples leads, so you'd take that figure an remove it from the other readings to give you the actual resistance, Again 5 or 8 before the . is resistance in the wire - note my readings would be in Ohms and not Kili or Mega ohms, there is no signals being measured above your purely checking the wire and 1st connection to the strip as any resistance will play a massive part in the data signal you are sending down that wire.

makes no difference if kodi or retropi as it still doesn't work, that was just a quick and easy change of platform to see what happened and it points more and more towards your wiring and or hardware. I take it setting the effect was not a success either

The only reason why I feel the wiring is good, is because it was all working perfectly before. No issues anywhere. I did try to run a new data cable and I didn't get any change in the issue. I disconnected the wire from my Arduino from the last setup, soldered an end on it, and connected it to the PI. No major pulls or damage could of happened.

When I did my checks with the voltmeter, I was confirming continuity around the whole LEDs. I could confirm from the end of the cable that plugs into the PI, all the way to the END of the LEDs. This gave a good signal. This was the extent of the testing I did before. I just kind of figured this would be enough. I'll be honest, I got a new meter and still trying to figure it all out, I'll try to grab my old one and try again.

I'll try to find a clip so I can clip on the LED in assorted spots. Just taking an end and touching the LEDs in assorted spots did nothing(on the center pin). I was assuming I would need to reboot the PI to check that. Or should it be always sending data and if I touch another spot, I should see a result ?

I might just spend the $35 buy replacement LEDs just in case. I wanted to avoid that, it will take a few hours to rip it all out, measure everything out, corners, never mind my TV has a ribbed pattern on the back of it, so I need to buy heavy duty double sided tape to hold it... The LEDs are not sticky enough to stay on. I will bench test to see if the LEDs light up before changing it all out

It's appearing, its' cables (hard to see at this point) or LEDs themselves are the issue (also kind of of hard to see). It could be the PI, I might be able to borrow one.

I'm kind of wishing I never touched it and just dealt with 1080p video with it....sigh..

TheCoolDave · 12. Februar 2021

Zitat von davieboy

Well 05.xx - 08.xx doesn't really mean anything without the other figures!

05.xx - 08.xx was from GPIO-18 to the data cable.

I tried it, at the END of the 253 LEDS, I tried there, the data was between 03.XX and 04.XX. So it's seems it's getting signal, I could see it being a little weak towards the end of it...

I also have run a larger cable from GPIO-18 and cliped it on to the data pin on the leds with no change. Just to make sure that is running fine. Did this just as a quick test.

Remember, this all worked perfectly before and I am using the same exact cable, ACCEPT I soldered in a end so I can plug it into the PI, it's a very solid connection, I assure you. This was used with the Java app before and I did have a Arduino in the mix before. On the Arduino, I had it soldered in due to the pins being kind of shaky and when that happend I would get flashing of the LEDs. Soldered it and it never blinked again.

Not exactly sure what could of happened here.

Zitat von davieboy
Here's a better idea if you have a spare SD card and 15 mins
Flash the latest Libreelec image https://libreelec.tv/downloads_new/
When it boots complete the setup and enable SSH when prompted, when done SSH into the Pi as you done in DrZ tutorial

Run this 1 command taken from @Paulchen-Panther 's Awesome Libre-Elec Tutorial - Its the easiest and fastest way to get Hyperion, Excluding flashing Hyperbian
Code
wget -qO- https://git.io/JU4Zx | bash
It will do all the work and reboot the Pi when done.

Go to the PiIP-Port and If the effects still don't work after setting them up form scratch there's a good chance the 5-8 resistance is the problem or your not setting something up correctly in the UI
Alles anzeigen

I did all this... rebooted, Reconfigured everything, Video was being captured, LEDS setup correctly, 0 from the LEDs... No change. Personally I would prefer RetroPI over Kodi if I was to have it...LOL

What else could I be missing in the UI ?

I am almost thinking of buying new LEDs that there is a problem there because everything else is fine...

Ok, setup..what I did...

LED Hardware, Controller type - set as RPI PWM - WS281X ONLY other change here, Hardware LED count set to 253, confirmed GPIO-18 is set, saved and LED layout. setup the layout, Input position, etc, Saved, Checked LED layout picture, should be perfect.

Capture Hardware - Change check to only have "Enable USB capture" and save. Confirm in Preview, TV is streaming in and LEDs are where they should be.

No other changes, it appears it should be working...unless I missed another step ? ? ?

Beiträge von TheCoolDave

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

Flickering on bright colors.... odd..

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?

No matter what I try, LEDs don't light up...ideas?