1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RPi + OSMC Rpi3 + OSMC + ws2812b hyperion wont start

Discussion in 'Software Support' started by TomChicCooky, 28 May 2018.

  1. TomChicCooky

    TomChicCooky New Member

    Messages:
    1
    Hardware:
    RPi3
    Hi i have a problem with getting my LED's to work. I have installed the correct driver for my LED's and installed hyperion through HyperCon with no errors. When i send my config file over and "stop" and "start" it nothing happens. In my log it comes up with:

    hyperion.service: Main process exited, code=killed, status=11/SEGV
    hyperion.service: Unit entered failed state.
    hyperion.service: Failed with result 'signal'.
    hyperion.service: Service hold-off time over, scheduling restart.
    Stopped Hyperion Systemd service.
    hyperion.service: Start request repeated too quickly.
    Failed to start Hyperion Systemd service.
    hyperion.service: Unit entered failed state.
    hyperion.service: Failed with result 'signal'.

    Anyone have any ideas what this could mean and how to fix it?

    Config:

    Thanks

    edit: okay i have the rainbow swirl but only after i press "stop". When i press start it does nothing. The log shows no errors and stays at: "INFO: Frame grabber created and started"
     
    Last edited: 28 May 2018
  2. LunarBlue

    LunarBlue Member

    Messages:
    90
    Hardware:
    RPi1/Zero
  3. Akriss

    Akriss Active Member

    Messages:
    433
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    I have had trouble with ws2812 led's driven from Rpi GPIO's before. Something to do with interrupts and bit-banging, I believe. (I'm not a coder i just read a lot) Most folk seem to use a Arduino with ws2812's. It seems that a Arduino is better at bit-banging and no interrupt problems.

    Just me thinking out loud. :)
     
  4. LunarBlue

    LunarBlue Member

    Messages:
    90
    Hardware:
    RPi1/Zero
    will try tomorrow, I've luckily got an Arduino here
     
  5. Jose Ramon Espericueta

    Jose Ramon Espericueta Member

    Messages:
    66
    Hardware:
    RPi3, +Arduino
    I tried using the ws281x driver but sometimes my SD gets corrupted and the system froze, I could not use ws2812-spi with level shifter , in the end I use an arduino uno
     
  6. BetterBoy08

    BetterBoy08 New Member

    Messages:
    2
    Hardware:
    RPi3
    I've got the same problem. Someone from Hyperion can look in this?
     
  7. fedorin

    fedorin New Member

    Messages:
    3
    Hardware:
    RPi3
    I have same problem. Anyone, help us out!
     
  8. daVid0n

    daVid0n New Member

    Messages:
    14
    Hardware:
    RPi1/Zero, RPi3, +Arduino, +PhilipsHue, +nodeMCU/ESP8266
    corrupted SD card gets resolved by adding "dmanum" :10, to your hyperion config
     
  9. JoeBee

    JoeBee New Member

    Messages:
    4
    Hardware:
    RPi3
    I have the same HW Configuration. Current OSMC Version and current Hyperion.
    And I have the same problem seems to be that Hyperion is not starting. Any Ideas?
    My messages that I get:

    Code:
    [email protected]:~$ sudo systemctl start hyperion.service
    [email protected]:~$ sudo systemctl status hyperion.service
    * hyperion.service - Hyperion Systemd service
       Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled)
       Active: failed (Result: signal) since Sat 2019-01-19 15:18:25 CET; 5s ago
      Process: 1419 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=SEGV)
    Main PID: 1419 (code=killed, signal=SEGV)
    
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    Jan 19 15:18:25 jb-osmc systemd[1]: Stopped Hyperion Systemd service.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly.
    Jan 19 15:18:25 jb-osmc systemd[1]: Failed to start Hyperion Systemd service.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Unit entered failed state.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
    [email protected]:~$
    [email protected]:~$
    [email protected]:~$ journalctl -xe
    Jan 19 15:18:25 jb-osmc hyperiond[1419]:         "type" : "ws281x"
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: }
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: whiteAlgorithm ::
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Creating linear smoothing
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: EFFECTENGINE INFO: Initializing Python interpreter
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Hyperion started and initialised
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Boot sequence 'Rainbow swirl fast' EFFECTENGINE INFO: run effect Rainbow swirl fast on channel 0
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: threshold set to 0 (0)
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: mode:default
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: started
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Json server created and started on port 19444
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Proto server created and started on port 19445
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: DISPMANXGRABBER INFO: Display opened with resolution: 1920x1080
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: threshold set to 0 (0)
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: mode:default
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: Frame grabber created and started
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: width=720 height=576
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: pixel format=UYVY
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: threshold set to 0 (0)
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: BLACKBORDER INFO: mode:default
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: signal threshold set to: {0,0,0}
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: V4L2GRABBER INFO: started
    Jan 19 15:18:25 jb-osmc hyperiond[1419]: INFO: V4L2 grabber created and started
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Main process exited, code=killed, status=11/SEGV
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Unit entered failed state.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    Jan 19 15:18:25 jb-osmc systemd[1]: Stopped Hyperion Systemd service.
    -- Subject: Unit hyperion.service has finished shutting down
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- Unit hyperion.service has finished shutting down.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly.
    Jan 19 15:18:25 jb-osmc systemd[1]: Failed to start Hyperion Systemd service.
    -- Subject: Unit hyperion.service has failed
    -- Defined-By: systemd
    -- Support: https://www.debian.org/support
    --
    -- Unit hyperion.service has failed.
    --
    -- The result is failed.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Unit entered failed state.
    Jan 19 15:18:25 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
    Jan 19 15:18:30 jb-osmc sudo[1426]:     osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/bin/systemctl status hyperion.service
    Jan 19 15:18:30 jb-osmc sudo[1426]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
    Jan 19 15:18:30 jb-osmc sudo[1426]: pam_unix(sudo:session): session closed for user root
    [email protected]:~$
    
     
  10. daVid0n

    daVid0n New Member

    Messages:
    14
    Hardware:
    RPi1/Zero, RPi3, +Arduino, +PhilipsHue, +nodeMCU/ESP8266
    your instance is actually failing on initializing the v4l2-grabber - this maybe related to a bug when switching between pal and ntsc, when I had this error, I resolved it by adding „no-switch“ where „pal“ or „ntsc“ are standing in the config. could you verify this?
     
  11. Akriss

    Akriss Active Member

    Messages:
    433
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Hi,
    This page (Here) has very good info on the potential pitfalls of diving ws2812 leds from Rpi Gpio's.

    Try black listing the "Broadcom audio kernel module" as detailed Here.

    Or try driving the led's via SPI pin's.

    Hope it's of help.
     
  12. JoeBee

    JoeBee New Member

    Messages:
    4
    Hardware:
    RPi3
    No this does't help

    [email protected]:~$ sudo service hyperion status
    * hyperion.service - Hyperion Systemd service
    Loaded: loaded (/etc/systemd/system/hyperion.service; enabled; vendor preset: enabled)
    Active: failed (Result: signal) since Sat 2019-01-19 16:15:47 CET; 13s ago
    Process: 1935 ExecStart=/usr/bin/hyperiond /etc/hyperion/hyperion.config.json (code=killed, signal=ABRT)
    Main PID: 1935 (code=killed, signal=ABRT)

    Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
    Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    Jan 19 16:15:47 jb-osmc systemd[1]: Stopped Hyperion Systemd service.
    Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Start request repeated too quickly.
    Jan 19 16:15:47 jb-osmc systemd[1]: Failed to start Hyperion Systemd service.
    Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Unit entered failed state.
    Jan 19 16:15:47 jb-osmc systemd[1]: hyperion.service: Failed with result 'signal'.
    [email protected]:~$

    I have to say. the screen grab picture in Hypercon works.
     
  13. JoeBee

    JoeBee New Member

    Messages:
    4
    Hardware:
    RPi3
    Well I just tested the configuration: "Test (file)" instead of the WS281x setting.
    This started fine. Hm maybe I should just use an Arduino as an intermediate device.

    Can somebody give me a good link how to configure and what sketch the Arduino needed?
     
  14. Akriss

    Akriss Active Member

    Messages:
    433
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Adding "RestartSec=15" to the [Service] section of the satartup file "hyperion.service" May help. I think.

    The sketch is (Here), It has good comments on how to configure within. If help is needed, just ask the forum.

    Hope is of help.
     
  15. JoeBee

    JoeBee New Member

    Messages:
    4
    Hardware:
    RPi3
    And what about "WS281X-SPI" setting? Is this working or are there also problems expected?
     
  16. Akriss

    Akriss Active Member

    Messages:
    433
    Hardware:
    RPi1/Zero, RPi2, RPi3, 32/64bit, +Arduino, +nodeMCU/ESP8266
    Mmm.
    I would not say problems. More limitations then anything.
    When using SPI It seems the driver needs the cpu at a specific frequency,(as detailed Here ) So no overclocking the Rpi if driving leds from SPI. And you cant use any other SPI gadget at the same time.

    Other then that it should work fine.