New Ambient Lighting system - no knowledge (1 Viewer)

[Rick164]

Yes it is also white, but it could be that it is a little little little lesser white. Maybe too less voltage? Do i need to connect the end of the stripe also to the psu? Right now the power is connected to the mid of the stripe.

Could indeed be power issue if its orange / yellow-ish as that is normally what happens if it can't fully power all 3 RGB leds, would do 2 tests to rule out hardware / power issue:

- Only connect the one led strip where the 1 led is misbehaving and check if it works that way.
- If that doesn't work check connections (soldering / cable) and / or connect power to the end of that led strip.

Btw: Which value do you used for overlap?

Believe the HyperCon default values + 2, prefer it to be slightly more inwards than the default. oops that was for horizontal / vertical depth, for overlap would keep the default.

 

[edsche]

Here are some pictures. The top led is always white in this case.



Tomorrow i will look at my soldering. Thanks rick

 

[Lightning303]

If you set your led count in hyperion a bit lower, does the then last led show the same problem?

 

[edsche]

If you set your led count in hyperion a bit lower, does the then last led show the same problem?

yes, same problem then. The color stays the same as it was before. But sometimes the color of the last led is changing. Right now it is blue.
Yesterday i wanted to disable all leds with the hyperion app, but the last led didn't switched off. It had the same color as before

 

[Rick164]

Might be defective chip as internally every led has its own but would run a few more tests to rule that out, what you could try after that is soldering any remain led strip (small segment) you have just before the defective one and see if those turn on or just cutting out that one and put a new one in once you run out of options

 

[Lightning303]

If you set your led count in hyperion a bit lower, does the then last led show the same problem?

yes, same problem then. The color stays the same as it was before. But sometimes the color of the last led is changing. Right now it is blue.
Yesterday i wanted to disable all leds with the hyperion app, but the last led didn't switched off. It had the same color as before

To make sure we mean the same thing. Now you have a problem with led 222, if you set hyperion to only use lets say 200, then all the sudden the problem appears at led 200, instead of 222?
If so, it could be that hyperion does not have APA102 implemented properly. It needs an end frame to clock through some data, if they dont deliver it, or just use a standard frame size (as wrongly described in the APA102s datasheet) instead of a framesize that fits your setup, errors like these may occur.

 

[Rick164]

Seem they fixed the APA102 end frame last month (or re-introduced it before that not sure):

https://github.com/tvdzwan/hyperion/pull/402

Depending on how Hyperion was installed (compiled versus pre-compiled package) you might have an old packaged version without this fix, most seem to include it already:

https://github.com/tvdzwan/hyperion/tree/master/deploy

Have seen working APA102 setups so not sure when they broke it but seeing no more bug reports after it at least.

 

[edsche]

Seem they fixed the APA102 end frame last month (or re-introduced it before that not sure):

https://github.com/tvdzwan/hyperion/pull/402

Depending on how Hyperion was installed (compiled versus pre-compiled package) you might have an old packaged version without this fix, most seem to include it already:

https://github.com/tvdzwan/hyperion/tree/master/deploy

Exactly this one I've used. So it seems this is the bad one?

 

[Rick164]

This rPI build should have the fix included:

https://github.com/tvdzwan/hyperion/blob/master/deploy/hyperion_rpi.tar.gz

You can check the version by running:

/storage/hyperion/bin/hyperiond.sh -v

OR

/storage/hyperion/bin/hyperiond -v

which will output something like:

Application build time: Mar 6 2015 20:57:44

// Update

Found something that explains why it isn't working even with the last release:

https://github.com/tvdzwan/hyperion/pull/364

Binaries aren't updated yet in the Hyperion repo (missing key patch), there's a APA_102 patch listed there which contains a unofficial patched binary which you can try and is reported to fix it (overwrite hyperiond from zip in your hyperion/bin folder)
This matches your problem exactly so @Lightning303 was spot on , never expected that someone would have screwed up the implementation.

 

[Lightning303]

This matches your problem exactly so @Lightning303 was spot on

Praise your lord!

never expected that someone would have screwed up the implementation.

Well, as i mentioned the datasheet is actually wrong. It states that its expecting a 32bit frame, where every bit is high. However, in reallity you need "Number of leds" / 2 bits for the end frame. For 222 that would of course be 111 bits. For a 1 meter strip however (60 leds) 32 bits is enough though, as only 30 are needed.
Some nice explenation can be found here (part 1 is more general, part 2 goes into detail of the endframe):