Posts by Lighting-guy77

    advice is to remove the barreljack connector and instead use electrics clamps or solder the joints, reason is because of resistance barreljack connector gets hot, less current can flow voltage will drop.


    • Make sure gauge of wire used is enough, you can make a calculation about the thickness/gauge AWG18 is not thick enough for 300 led feed.
    • make sure you save the ledconfigurationpage correctly so the leds will be there in the Json file.
    • Make sure grounding (GND) is connected to PI gnd pins/PSU gnd/ledstrip


    and also power the ledstrip from BOTH sides, so beginning and end needs +5volts on VCC and GND on GND

    little note to add;



    he was right and because of one weird reason the spaces where there, ........ anyway

    i have a few pointers.




    Restart=on-failure

    RestartSec=2




    when you want the Hyperion service to shut off but want to still use your PI because you want to do an installation or whatever,

    then you can terminate the function of restart.

    just add =off behind the line Restart on failure, (on-failure becomes off)


    if you want that Hyperion waits with rebooting then extend time only in line RestartSec=digit :)

    i have a step to step plan how i have it myself.



    automatic startup of Hyperion.NG


    With the following command (under Putty) you create a new file called hyperion.service under / lib / systemd / system /


    Code in terminal:

    sudo nano /lib/systemd/system/hyperion.service

    ... and insert the following content.


    [Unit]

    Description = Hyperion ambient light systemd service

    Na = network.target


    [Maintenance]

    ExecStart = / usr / local / bin / hyperiond

    WorkingDirectory = / usr / local / share / hyperion / bin

    User = pi

    TimeoutStopSec = 5

    KillMode = mixed

    Restart = on failure

    RestartSec = 2


    [To install]

    WantedBy = multi-user.target


    edit: don't forget to save (enter and Ctrl + o) and exit (Ctrl + x) from nano.


    Finally, restart the systemd service and activate / start the Hyperion.NG service.

    Code:

    sudo systemctl daemon-reload

    sudo systemctl enable hyperion.service

    sudo systemctl starts hyperion.service

    hello!


    i have a few tips, check the voltage on the PSU under load should not exceed 5.0 volts or drop under 4.99 volts


    For PWM, GPIO 18 put in config.txt file the following line


    dtparam=audio=off


    i can see in the log the PWM ledcontroller is running.

    check in remote control section if leddevice is running also, just to be shure


    Pi1 model B ?


    maybe its time to use something with more power, Pi1 is not powerfull to extract and rendering images from live video feed in high res.

    MS2100E is from Macro Silicon manufacturer, it should work fine as the STK1160


    i would recommend to level up to at least PI3b ( quadcore) or even the Pi4 ( most expensive)

    if you do it thats your own choise ofcourse.

    so nothing spectaculair,



    recommended settings sk9812 RGBW ledstrip;


    • running SPI ledcontroller, device 0 SPI 0
    • GPIO 10
    • baudrate quite high 5900000
    • no levelsifter needed
    • white algorythm, white colour is OFF

    at least something should be showing up in dmesg when i plug it in, right?


    yes you can try this>> in terminal/ssh with screen connected or VNC activated


    sudo apt-get install mplayer



    then,


    sudo mplayer tv:// -tv device=/dev/video0 -hardframedrop



    if the capturing device is working then u should see ( if its device 0 ) the capturing image :)

    the leds that are not programmed in Hyperion.NG waiting for a signal, thats why they are white.

    thats the basic "colour"



    if you really want to have the leds of from 193 pixels then i would say yes there's a way without cutting.

    remove led 194 and see if that works, depends on the schematics how the strip is build.

    the best thing to do is after fresh installation of a build, like 2.01 or 2.06 or whatever build u used,

    is to save the Json configuration in Dashboard and export.

    when the installation goes corrupt then you can import that file again to make the build basic.


    i've used that trick before when using a effect caused the build to be weird, Pacman effect caused the leds to behave weird.

    after i used a new Json with the same settings then everything was back to normal.


    for every build the Json file is diffrent and can not be used ( most of times) in other builds of Hyperion.NG, will corrupt the installation then.

    from the same website, look at reviews


    i think in your case its not difficult to find the problems.


    You have the usb power on in config.txt, still the capturing device is fading after times.



    you can solve this in 2 ways > i watched your logs/config/debug and the only thing you see is the capturing device is failing in the log.



    1. Update libraries in Raspi for use of Hyperion.NG
    Code
    sudo apt-get update
    sudo apt-get upgrade
    
    sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev


    2. buy another USB capturing device that actually works, like this >> https://www.conrad.nl/p/basete…oftware-plug-play-2228152

    this one has a Macrosillicon chipset.


    i have this one for 1.5 years now and still running...





    goodluck! :thumbup:

    Quote

    The SK6812 is very similar to the WS2812B, and can be used as a drop-in replacement in most applications because it features the same interface and color order (so LED strips based on the SK6812 and WS2812B can be chained together). The main difference between the two drivers is that the SK6812 has voltage-independent color and brightness over a wide voltage range, which means that the colors of the LEDs should not be affected by a drop in the supply voltage as much as they are on the WS2812B.

    Looks like sk6812 is a direct clone of ws2812b with some improvements made


    Looks like sk6812 is a direct clone of ws2812b with some improvements made. LED is driven at higher PWM frequency and some variants have separate white die, instead of running RGB channels simultaneously. All existing ws2812 libraries are compatible (commonly refered as ‘NeoPixel’). Sk6812 and ws2812 are actually controler chips, and LEDs you are interested in have chip integrated.

    Normally,we can not distinguish it well,but through the IC shape,we can see it is ws2812b or sk6812.



    i've dived into this and it seems that your ledstrip can run on a diffrent Led controller.


    Can you leave the SPI connection but select the ws2812? so run it first on SPI and set baudrate on 3000000



    if that doesn't do the trick then try to run it on PWM >> the article says the ledstrip is capable to do that so i was wrong first and it seems that it should do fine. :)



    So, for the SPI


    ledcontroller ws2812spi

    GPIO 10

    baudrate 3000000 or higher, just test it out ( article says the ledstrip demands a high frequency)




    so, for the PWM > make sure in config.txt audio =off

    Code
    dtparam=audio=off

    ledcontroller ws281x

    GPIO 18

    DMA 5

    PWM 0