UTV007 flips between inactive/active on Rpi zero w

  • I have a UTV007 capture plugged into the OTG port on a raspberry pi zero w, the input keeps turning on and off. When I plug it into an rpi 3 it works fine. I tried powering it separately from the otg plug with no change. It worked before I removed the cases from everything to mount it up

    rpi 3 - works

    new rpi zero w - doesn't work

    rpi zero w w/separate otg power - doesn't work

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.559 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:251:setInputImage() | Priority 240 is now inactive

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.566 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:351:setCurrentTime() | Set visible priority to 255

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.568 hyperiond HYPERION : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[255], previousPriority[240]

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.574 hyperiond HYPERION : <DEBUG> Hyperion.cpp:562:handlePriorityChangedLedDevice() | No source left -> switch LED-Device off

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.787 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:251:setInputImage() | Priority 240 is now active

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.796 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:351:setCurrentTime() | Set visible priority to 240

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.800 hyperiond HYPERION : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[240], previousPriority[255]

    Apr 11 02:44:36 HyperBian hyperiond[468]: 2021-04-11T02:44:36.809 hyperiond HYPERION : <DEBUG> Hyperion.cpp:569:handlePriorityChangedLedDevice() | new source available -> switch LED-Device on

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.692 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:251:setInputImage() | Priority 240 is now inactive

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.699 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:351:setCurrentTime() | Set visible priority to 255

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.703 hyperiond HYPERION : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[255], previousPriority[240]

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.712 hyperiond HYPERION : <DEBUG> Hyperion.cpp:562:handlePriorityChangedLedDevice() | No source left -> switch LED-Device off

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.821 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:251:setInputImage() | Priority 240 is now active

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.827 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:351:setCurrentTime() | Set visible priority to 240

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.835 hyperiond HYPERION : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[240], previousPriority[255]

    Apr 11 02:44:38 HyperBian hyperiond[468]: 2021-04-11T02:44:38.843 hyperiond HYPERION : <DEBUG> Hyperion.cpp:569:handlePriorityChangedLedDevice() | new source available -> switch LED-Device on

  • I think USB ports of Pi Zero have not enough power. Maybe a powered USB hub could help.

    But I would give the RPi3 a chance. More CPU power and performance.

    Grüße aus Österreich / Greetings from Austria !

    - Don't wanna miss it anymore !

  • Tried that, didn't work. I'd rather use the pi zero because it's spare hardware. It worked before so I'm not sure why it isn't working now

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!