Beiträge von Axel Robert

  • Hyperion unreacheble

    @Frogro You sir are a genius, it did the trick and now I have Hyperion running again.
    I realized that the pi some times stops detecting the USBTV007, is there some tests I could run to see what exactly is the problem?



    Update: I have some error showing on my terminal screen when connected through ssh


    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989330] Internal error: Oops: 817 [#1] SMP ARM
    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989459] Process kworker/0:1 (pid: 30, stack limit = 0x821d7de0)
    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989463] Stack: (0xb664fcc0 to 0xb6650000)
    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989471] fcc0: b29ce000 b29ce52c b29ce008 b29ce540 a48a8020 7f205038 b664fd04 b664fce8
    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989478] fce0: 7f2034dc 7f202868 b29ce000 00000000 7f205038 abf29078 b664fd1c b664fd08
    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989485] fd00: 7f202038 7f2034a8 abf29078 00000000 b664fd5c b664fd20 806a6a9c 7f20200c
    Message from syslogd@raspberrypi at Sep 22 13:36:31 ...
    kernel:[ 119.989492] fd20: 808eed14 ffffffed 00000000 a48a8000 b664fd5c a48a8020 00000000 7f205038

  • Hyperion unreacheble

    So after the last update Alpha 8 Hyperion Ng has stopped working.


    I tried re installing everything from scratch, I downloaded Hyperion again, installed it and updated my Raspbian, after which my Hyperion is completely unreachable through the web server.
    I keep getting connection refused.
    Also when I updated to Alpha 7 My usb grabber just stopped appearing on the list though my raspberry 3b+ can clearly see it when using lsusb.


    Any help in solving one or both problems would be very much appreciated would be appreciated.


    Feel free to ask me for any more info if needed.

  • External Grabber no longer showing up on NG

    So everything was working perfectly fine, Led Strip could be replaced but other than that all perfect.


    I updated the Hyperion NG alpha from 5 to 6 and now Hyperion no longer sees the external grabber, I have re installed raspbian and hyperion, and nothing.


    When I check the lsusb, it shows up
    pi@raspberrypi:~ $ lsusb
    Bus 001 Device 004: ID 1b71:3002 Fushicai USBTV007 Video Grabber [EasyCAP]
    Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp.
    Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
    Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


    I try to reset, the raspberry to check if it still shows up, it always does, but hyeprion wont seem to find it.


    Any guess what could be the problem, is it the grabber physically failing?
    A problem with drivers? or a problem with Hyperion itself?


    i have also tried changing the grabber from usb port and nothing seems to work.


    In the Hyperion log I get this:


    [hyperiond V4L2:/dev/video0] (INFO) configured v4l device: /dev/video0 [hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:609:init_device()) Video standard=NTSC [hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:692:init_device()) Set resolution to width=720 height=480 [hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:731:init_device()) Pixel format=YUYV [hyperiond V4L2:/dev/video0] (ERROR) Throws error nr: VIDIOC_STREAMON error code 71, Protocol error [hyperiond V4L2:/dev/video0] (INFO) Started [hyperiond V4L2:/dev/video0] (DEBUG) (GrabberWrapper.cpp:49:start()) Grabber start() [hyperiond BOBLIGHT] (DEBUG) (BoblightServer.cpp:28:BoblightServer()) Instance created [hyperiond HYPERION] (INFO) Hyperion instance 'First LED Hardware instance' has been started [hyperiond ComponentRegister] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) LED device: enabled [hyperiond V4L2:/dev/video0] (ERROR) Throws error nr: VIDIOC_DQBUF error code 22, Invalid argument [hyperiond V4L2:/dev/video0] (INFO) Stopped

  • Utvf007 with Hyperion-ng

    You need to go on the Hyperion web server, from there you go to capture device config, and should see size decimation, you should put that at 1 if you want to see it less blurry, then again the image starts lagging.
    I'm learning as i go pretty much but im sure there is a way around the lag due to size decimation adjusting the frames per second.

  • grabber problem

    I tried both, and turns out my converter was working all along but the strange thing was the order in which cables you connect firstwhich makes absolutely 0 sense to me, if i put rca before hdmi i would get no video through after connecting the hdmi first then video and both audios followed by the power i got an instant signal

  • grabber problem

    I have the exact same problem I re-soldered some parts, connected power to all four corners as I had voltage drops I could see some color changes on the strip. Before this my video grabber was working fine, now that i re soldered it is working fine except the grabber i keep getting a black Image in the log files I can see the grabber starts fine and I don't seem to get any errors, any ideas on what it could be?



    4L2GRABBER INFO: width=720 height=480
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: V4L2GRABBER INFO: pixel format=YUYV
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: BLACKBORDER INFO: threshold set to 0.12 (31)
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: BLACKBORDER INFO: mode:default
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: V4L2GRABBER INFO: signal threshold set to: {0,0,0}
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: V4L2GRABBER INFO: started
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: INFO: V4L2 grabber created and started
    ssh in: Mar 27 13:10:21 Eraser hyperiond[4678]: BORDER SWITCH REQUIRED!!

  • Video grabber no longer working

    So i had managed to get the ambilight working using raspbian and it was all working fine except i hadn't managed to get black border detection.
    I'm using a raspberry pi 3b+ with a splitter which goes to the av converter set to ntsc and to the UTV007 into the pi.
    I had to disconnect it straight from the power source before shutdown and now the video grabber wont work on hypercon.
    I just get a black screen, and when I look at the log I get video grabber started and immediately stopped


    *Update: the hyperion app works fine with every stock effect working fine so its not a faulty LED