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

RPi + Other Software Hyperbian + Hyperion ng + ezcap 269

Discussion in 'Software Support' started by Tyler983, 8 September 2020.

  1. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Ok i will post it tomorrow cause now I'm on the rpi3...
     
  2. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    @Awawa I installed a fresh build of Raspbian lite, your last fork and deactivate bluetooth with the command line you suggested. Ezcap is plugged to the usb3 port but nothing happen... leds are off.
    attached you can find last dmesg and the errors are always the same.
    What to do?
     

    Attached Files:

    Last edited: 21 September 2020
  3. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    These errors are specific for that system/config, if other things work on Rpi3 then you can ignore them on Rpi4 too.
    Try remove console=serial0, console=ttyAMA0 and console=ttyS0 from cmdline.txt.
    Seems that ttyAMA0 is taken over at start up again (not by bluetooth).

    https://www.raspberrypi.org/documentation/configuration/uart.md

    It's highly problematic USB to lightberry converter, sorry.
     
  4. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    I think you’re right, cause I have the same errors on the rpi3 but there less are on...
    Where I can remove those strings?
     
  5. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
  6. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Thx i'll give it a read
    another thing... i generate a lut file, but as you explain in the first post, i haven't : the Hyperion configuration folder.

    Typically /home/pi/.hyperion/.....

    I searched it with cyberduck but folder "pi" is empty.
     
    Last edited: 22 September 2020
  7. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Read hyperion logs
     
    • Like Like x 1
  8. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Good day @Awawa yesterday i deleted the strings you suggested from cmdline.txt but the result is always the same: no leds...I don't know what to do with this rpi4.
     
  9. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Post dmesg after changes
     
  10. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Ok when i'll be at home i'll post it
     
  11. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Hi @Awawa following the dmesg as you asked. This is the ssd with your last fork installed, rpi4, ezcap269, usb3 plugged.
    Nothing to do, leds are all off.
    The same sd go like a charm in the rpi3.
    What to do?
     

    Attached Files:

  12. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    OK, lets try this:

    Code:
    sudo systemctl stop [email protected]
    sudo systemctl disable [email protected]
    sudo systemctl mask [email protected]
    sudo reboot
    If it doesn't help could you provide output after reboot of:
    Code:
    ls -l /dev/ttyACM0
    (try to execute it again with lightberry connected/disconnected to compare, reboot before each action)
    and content of /boot/config.txt and logs from hyperion WWW page to check what's happening inside.
     
    Last edited: 26 September 2020
  13. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Sudo commands doesn't function, so I tried with lightberry connected and this is the result
    [email protected]
    :~ $ ls -l /dev/ttyACM0
    crw-rw---- 1 root dialout 166, 0 Sep 26 16:20 /dev/ttyACM0

    with lightberry disconnected:
    [email protected]:~ $ ls -l /dev/ttyACM0
    crw-rw---- 1 root dialout 166, 0 Sep 26 16:22 /dev/ttyACM0

     

    Attached Files:

  14. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Definitely not good. Forget for now about Lightberry. Did you disabled system/platform grabber as it's completely broken in Hyperion.NG alpha 8 on Rpi4?
    [​IMG]
     
  15. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Tradotto in:
    Italiano
    Spettacolo originale
    Now I've disabled it... there's something other I ca do?
    [​IMG]
    Original text
    Contribute a better translation
     
  16. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Yes, post logs from Hyperion after change ;)
     
  17. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    2020-09-26T15:43:39.709Z [hyperiond DAEMON] (ERROR) The CEC handler can not be instantiated, because it has been left out from the build 2020-09-26T15:44:33.787Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0'
     
  18. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    With your previos log you've got that error ('Timeout writing data to ttyACM0') only when the light-berry was disconnected. Did you connect it again and rebooted? PS: put debug level to DEBUG as now we can see only errors.
     
  19. Tyler983

    Tyler983 Member

    Messages:
    110
    Hardware:
    RPi3, +PhilipsHue
    Yes, I've pugged lightberry and rebooted it.
    this is the log in debug mode:

    2020-09-26T15:43:39.709Z [hyperiond DAEMON] (ERROR) The CEC handler can not be instantiated, because it has been left out from the build 2020-09-26T15:44:33.787Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0' 2020-09-26T15:48:40.024Z [hyperiond V4L2:AUTO] (DEBUG) (V4L2Grabber.cpp:992:process_image()) Video FPS: 29.88, av. delay: 38ms, good: 1773, bad: 20 (60.03,15)
     
  20. Awawa

    Awawa Active Member

    Messages:
    176
    Hardware:
    RPi1/Zero, RPi3, +nodeMCU/ESP8266
    Strange, because there wasn't that error in the log before, maybe it was taken to soon before it occured.
    Anyway it isn't fully log from Hyperion in DEBUG mode but a part of it.

    Summarize:
    1) you took full copy of working system from Rpi3 to Rpi4
    2) Rpi4 doesnt work. In normal circumstances we can exclude Hyperion as a suspected because the config is the same and it works on Rpi3.
    3) But it isn't that case as Alpha 8 has broken system grabber on Rpi4. And system grabber is enabled...
    4) We try to overcome Serial port problem again but it's dead end as the Hyperion isn't working (didnt you notice it in the hyperion log?)
    5) Now we have AMA0 in unknown state after some experiments. Not sure if it isnt problem but the path of changes to make it work was definitely wrong based on wrong diagnosis.

    So I propose to disable system grabber on Rpi 3 then to make a full copy of that working system to another card and try to run it on Rpi 4 again ;)
     
    Last edited: 26 September 2020