Beiträge von Marxon

    Changes you make on the "Remote Control" settings page are temporarily and lost after restart.

    Activate "Enable screen capturing" under "LED instances" -> "Sources" and

    check "Activate" under "Capturing Hardware"


    Best regards

    Marxon

    Sorry, but i (maybe) found an other issue:

    The 2nd step in the color calibration wizzard allows you to define a name for the color profile

    unfortunately setting a name here causes the leds not to react to the adjustments you do in the next steps.

    You first have to create a custom profile on the image processing settings page!

    Afterwards, the calibration wizzard gives you the option to select one of your created profiles

    and then the rest of the calibration works like expected.


    Marxon

    Hyperion cannot not see what you bought and have connected.... ;)
    There seems to be different strips out there with different datasheet specs, but same protocol. Therefore, you can overwrite it.

    A type-x led is a type-x therefore i select it in settings or not? ;)

    But of course you are right, specs and setups vary, i also forgot that i enabled expert mode :saint:


    Thank you for spending your time to give me support and the Hyperion Project in general! :thumbup:


    Schönen Sonntag noch!

    Marxon

    OK, now i got it.

    "Rewrite Time" is really more intuitive, thats true.

    But you lead me to a next question:

    Due the latch time is specific for the type and amount of Leds,

    then why can i change it? Doesn't Hyperion calculate the minimum latch time itself?

    Increasing the latch time would maybe make sense to lower transmission errors.

    Hi Lord-Grey,

    erstmal Danke für deine Erklärung.

    Leider verstehe ich das immer noch nicht ganz.

    Zitat

    time-frame a device requires until the next update can be processed

    time frame a devices requires to be refreshed


    Ist für mich irgendwie das gleiche :/

    Konkretes Beispiel WS2812b, aus dem Datenblatt:


    Nutze ich 2 Leds sind das:

    minimum (TH+TL-0,6µs) pro Bit x 24bit pro Led x 2 Leds + 50µs Reset = 81,2µs

    Das wäre dann also die Latch Zeit, oder?



    Gruß

    Marxon

    Although it would be interesting to know where the signal come from, I switched from SPI to PWM

    and so far everything seems to work. :)

    Maybe I should ask in a other forum for help to investigate my SPI problem further.

    Thanks a lot.


    Marxon

    Thanks for your response.


    Zitat von Lighting-guy77

    maybe bad PSU or bad grounding.

    No I don´t think so.

    Because like i said, the signal disappears when selecting a none SPI-type led in settings.

    Zitat von Lightning-guy77

    3 line ledstrips are sometimes difficult to run on SPI because of the lack of CLK signal. Then you have to play with baudrate settings and such.

    Yes this is true, but the problem is that unknown signal

    Zitat von TPmodding

    does the signal has 2,72V?

    No it doesn´t.

    2,72V was my trigger voltage.

    The signal has 3,24V.



    Does anybody know how to check in Linux if any other programm in the background is running which uses the SPI port?

    It seems no one else having a similar problem in the forum, but maybe someone can help nevertheless.

    Everything works so far but there is some kind of repeating external signal superimpose (i hope this is the correct english word)

    the communication which causes flickerig and i dont know its source.

    It also occurs when no effect is running but it disappears when selecting a none SPI-type led in settings.

    I checked the signal with my oscilloscope @ 1ms, 50us, 10us, 1us


    Where could this signal come from?


    Best regards

    Marxon

    Hi everybody,


    i use LibreElec on a RPi4 with WS2812B and a 3,3V-5V level shifter.

    Unfortunately the level shifter is not fast enough.

    Is it possible to increase the duration of a high impulse?


    Thanks for any help

    Marxon