v17 stopped functioning after 2 weeks (no longer detects USB grabber) #135
Replies: 8 comments
-
|
If it worked then must appeared something new that caused this. You missed to attache full HyperHDR logs. Maybe Rpi is broken if it is not detecting USB video grabbers or the power supply is not sufficient. If there video grabber is not visible by the system then it's not related to HyperHDR. Verify |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply. 2021-10-23T01:17:15.885Z [MAIN] Database path: '/home/pi/.hyperhdr/db/hyperhdr.db', readonlyMode = disabled 2021-10-23T01:17:24.709Z [HYPERHDR0] No source left -> switch LED-Device off2021-10-23T01:17:24.710Z [IMAGETOLED0] (ImageProcessor.cpp:180) set hard led mapping to multicolor_mean |
Beta Was this translation helpful? Give feedback.
-
|
OK, the grabber is detected by the system but when HyperHDR tries to initialize capturing then it disappears from the system (timestamp: 2021-10-23T01:17:16.977Z it's not here anymore). Last 'No source left -> switch LED-Device off' is only a consequence that there is no video provider (USB grabber or effect) for HyperHDR. If you didn't update the Rpi system or flash new firmware to the device then in 99% it means problems with a power supply (or damaged grabber, did you test with PC ..not only connect it but try to capture the video stream also?). Verify |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again for the reply. I'm sort of new to all this. When I updated from v16 to v17 I formatted the microSD card and reinstalled HyperHDR v17 on it with a flash imager. Like I said this worked perfectly for a couple of weeks then stopped. What do you mean by verify dmesg sorry? |
Beta Was this translation helpful? Give feedback.
-
|
Restart Rpi to have clean logs. After that make sure that you have errors in HyperHDR logs (other way it should work and the problem is solved by itself). Then connect with ssh (for example using |
Beta Was this translation helpful? Give feedback.
-
|
When the grabbers starts to capture then it goes on full specified power usage, guess your Rpi can't provide enough power. Working rainbow effect doesn't prove anything because the grabber is in stand-by mode then. Does Rpi have it own power supply or it is using LED strip power supply? |
Beta Was this translation helpful? Give feedback.
-
|
The LEDs and pi share a power supply however I am using a 15A 75W power-supply which should be more than enough. I wish I could be more help sorry. |
Beta Was this translation helpful? Give feedback.
-
|
LED strip supply maximum power output is one thing but the voltage is fluctuating, Rpi is very sensitive for that and that configuration should not be used. Moving to the discussion and it's not HyperHDR related. I can provide you further help but first check your dmesg. |
Beta Was this translation helpful? Give feedback.
-
Hi,
Apologies that this isn't this the correct format but I have nothing to show.
I was using HyperHDR v16 with SK6812 LEDs and a pi 3b fine with no issues. I updated to v17 and it worked perfectly for roughly 2 weeks or so. Now it has just stopped acknowledging my capture card exists. I have tried multiple USB capture cards/grabbers and have the same problem and I have also tested the capture cards on my PC and it works so I know its not the problem.
Is anyone else having this issue?
Beta Was this translation helpful? Give feedback.
All reactions