Beiträge von bob21

I've tried without the extension and in all ports but there is no improvement. It's the same as before.

Yes, it has been connected with the short USB extension cable that it came with. Do you think this could be the issue? I can try without and report back.

Are these not the required logs? If not, where can I find them and I will post

[hyperiond V4L2:/dev/video0] (INFO) Signal detection is now disabled
[hyperiond V4L2:/dev/video0] (INFO) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
[hyperiond V4L2:/dev/video0] (INFO) Signal threshold set to: {12, 12, 12}
[hyperiond V4L2:/dev/video0] (INFO) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
[hyperiond V4L2:/dev/video0] (INFO) Signal threshold set to: {12, 12, 12}
[hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:84:uninit()) uninit grabber: /dev/video0
[hyperiond V4L2:/dev/video0] (INFO) Stopped
[hyperiond V4L2:/dev/video0] (INFO) available V4L2 devices:
    /dev/video0    USB2.0 PC CAMERA


[hyperiond V4L2:/dev/video0] (INFO) search for usable video devices
[hyperiond V4L2:/dev/video0] (INFO) test v4l device: /dev/video0
[hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:692:init_device()) Set resolution to width=640 height=480
[hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:709:init_device()) Set framerate to 15 fps
[hyperiond V4L2:/dev/video0] (DEBUG) (V4L2Grabber.cpp:731:init_device()) Pixel format=YUYV
[hyperiond V4L2:/dev/video0] (INFO) found usable v4l2 device: /dev/video0 (USB2.0 PC CAMERA)
[hyperiond V4L2:/dev/video0] (INFO) Started
[hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:238:setInputImage()) Priority 240 is now active
[hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 240
[hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:238:setInputImage()) Priority 240 is now inactive
[hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:333:setCurrentTime()) Set visible priority to 254

It appears to initialise...

But I only see this in preview:

I started on Hyperion old and it never worked. I moved to NG alpha 5 and it worked, then for no apparent reason it stopped. Still on alpha 5.

The preview window is black. Before it showed the stream.

This morning I tried reinstalling on a fresh Raspbian and going through everything to make sure the settings are ok but I cannot get it to work again. So weird because it was working well. Is there anything else I can try before I order another stick?

Marking as solved as have moved to NG and am up and running with LED strip. Ended up using BAT43s as the 54s were very small

Hi

Here you go

Funny thing is, if you use the button to stop / start the USB capture service, the device briefly appears in the source list then vanishes. I am wondering if this is a bug.

So thanks to TPmodding, I am pretty much up and running using WLED (thanks for the suggestion!)

I initially had some issue getting things set up, until I realised that I was running the old version of Hyperion and HyperCon :p

I am currently using 2.0.0 alpha5. To my surprise, my cheapo capture card from Aliexpress which was meant to be an STK1160 and isn't, started working and auto-detected when I installed v2alpha5. I didn't think it was compatible, so it was a nice surprise! After much testing and calibration (and reboots) I shut down and moved everything to it's final resting place, but when I booted up again it doesn't show a signal from the card o_O

It's still listed under lsusb:

Bus 001 Device 005: ID 18ec:5555 Arkmicro Technologies Inc.

And v4l2:

USB2.0 PC CAMERA (usb-3f980000.usb-1.4):
   /dev/video0
   /dev/video1

and in Hyperion:

But no longer in Hyperion's source selector:

But it definitely was before.

I have tried manually entering /dev/video0 and /dev/video1, no joy.

How can I get this card working again? It obviously is capable of working, and it worked really well! I fail to understand how a reboot has killed it from being usable? o_O

So while I wait for a couple of the final components, something did arrive today and that is the vid cap. I think I may have fallen at one of the first hurdles though.. it identifies as:

18ec:5555 Arkmicro Technologies Inc.

Which is not what I ordered.

Looking at other threads like this: https://hyperion-project.org/t…icro-easycap-support.578/

It looks like this is an unsupported chipset. The console shows:

VIDIOC_S_INPUT ERROR 25, Inappropriate ioctl for device

My install is Raspbian Buster and Hyperion installed using the .jar. Am I doing something obviously wrong or is this chipset just outright not supported?

More fun yes, if I can manage to do it right and it works reliably. I am still waiting for some components. I will post back as soon as I have tried. Thanks for the pointers

That would certainly make things simpler. What about lag due to wifi? I guess more stable than 2M DIN cable....

Interesting, I had not considered wifi for the connection. Do you mean direct connection or via an access point (router)?

Like this:

That's a good idea, I have one spare. But, I have a problem. Does the Arduino and D1 connect to the Pi with USB? The wire going from main enclosure to strip is 4 core. If I move the LED controller to the TV end, I have 2 spare wires. Is it possible to communicate from Pi > Di / Arduino with just those 2 wires?

Like this:

If it is, I think the D1 at the TV end is a logical choice. If it's not, I would have to run a separate long USB cable along side it, which I would rather avoid.

I suppose, I could Frankenstein a USB cable... looks like USB data is only 2 wires....

Or can the headers of the Pi and D1 be used?

Because the Arduino is in an enclosure with many other components. I am prepared that it may be problematic and I will either need to:

1. Shorten the wire - due to distance between TV on wall and box, this may not be possible by more than ~30cm
2. Move the Arduino to it's own enclosure behind the TV, but this would require adding another board in the main enclosure because I planned to integrate a screen etc

So my plan is to try these things in this order:

1. Try as is
2. Add level shifter
3. Shorten cable as much as possible
4. Relocate Arduino

Note: it seems BI should not be tied to DI. It is, for each subsequent LED, but for the start of the strip connecting BI to DI will cause a mismatch.

I am not sure if those are the same as I have. They work out at about 72W per 5M strip. Mine are marked as 90W per 5M and seem to fit versions C and D from the datasheet I posted. In any case, here's a look at what I will be doing:

Hopefully this is helpful to someone else. I take no credit for this, I threw this [very bad] diagram up after I got some advice from Ian.M on the EEVblog forums.

Edit: fixed image

Hi! Thanks for replying.

The datasheet doesn't seem to mention connecting BIN and DIN together: https://www.elecrow.com/download/WS2813_LED_Datasheet.pdf

The datasheet (and also this: https://cdn-shop.adafruit.com/datasheets/WS2812B.pdf) also doesn't mention anything of forward voltage (from what I can see) or if resistors are placed before each LED... so it's impossible to calculate the required resistance if the needed information isn't present. Adafruit's recommendation of 100R-500R seems a bit too much like wild guessing to me.