Beiträge von Wim

Zitat von Wim

I tried ls /dev and spi loopback test (https://www.raspberrypi.org/do…raspberrypi/spi/README.md)
both are okay.

ls /dev:

autofs loop7 ram6 tty2 tty45 urandom
block loop-control ram7 tty20 tty46 vc-cma
btrfs-control mapper ram8 tty21 tty47 vchiq
bus mem ram9 tty22 tty48 vcio
cachefiles memory_bandwidth random tty23 tty49 vc-mem
char mmcblk0 raw tty24 tty5 vcs
console mmcblk0p1 rfkill tty25 tty50 vcs1
cpu_dma_latency mmcblk0p2 serial1 tty26 tty51 vcs2
cuse mqueue shm tty27 tty52 vcs3
disk net snd tty28 tty53 vcs4
fb0 network_latency spidev0.0 tty29 tty54 vcs5
fd network_throughput spidev0.1 tty3 tty55 vcs6
full null stderr tty30 tty56 vcs7
fuse ppp stdin tty31 tty57 vcsa
gpiochip0 ptmx stdout tty32 tty58 vcsa1
gpiomem pts tty tty33 tty59 vcsa2
hwrng ram0 tty0 tty34 tty6 vcsa3
initctl ram1 tty1 tty35 tty60 vcsa4
input ram10 tty10 tty36 tty61 vcsa5
kmsg ram11 tty11 tty37 tty62 vcsa6
log ram12 tty12 tty38 tty63 vcsa7
loop0 ram13 tty13 tty39 tty7 vcsm
loop1 ram14 tty14 tty4 tty8 vhci
loop2 ram15 tty15 tty40 tty9 watchdog
loop3 ram2 tty16 tty41 ttyAMA0 watchdog0
loop4 ram3 tty17 tty42 ttyprintk xconsole
loop5 ram4 tty18 tty43 uhid zero
loop6 ram5 tty19 tty44 uinput

lsmod:

Module Size Used by
bnep 11949 2
hci_uart 21190 1
btbcm 7885 1 hci_uart
bluetooth 374820 22 hci_uart,bnep,btbcm
spidev 7034 2
brcmfmac 213463 0
brcmutil 9063 1 brcmfmac
snd_bcm2835 23131 1
cfg80211 525742 1 brcmfmac
snd_pcm 97825 1 snd_bcm2835
rfkill 21373 4 bluetooth,cfg80211
snd_timer 22706 1 snd_pcm
snd 68784 5 snd_timer,snd_bcm2835,snd_pcm
spi_bcm2835 7424 0
bcm2835_gpiomem 3791 0
uio_pdrv_genirq 3718 0
fixed 3029 0
uio 10166 1 uio_pdrv_genirq
i2c_dev 6642 0
fuse 94600 3
usb_f_ecm 7416 1
g_ether 5037 0
usb_f_rndis 16959 2 g_ether
u_ether 13511 3 usb_f_ecm,g_ether,usb_f_rndis
libcomposite 49619 3 usb_f_ecm,g_ether,usb_f_rndis
dwc2 122113 0
udc_core 40356 5 usb_f_ecm,dwc2,u_ether,usb_f_rndis,libcomposite
ipv6 384468 34

I read somewhere that some zero's have a "improved spi module (spi_bcm2835)". Could that be it?

Wim

I'm thinking maybe the spi-driver isn't suited for the pi zero yet?

EDIT: specific for the ws2812b or ws2813 that is

I found a difference between pi zero and other pi's: pi zero have hdmi audio, while the others have analog audio. Maybe this has something to do with it?

https://socialcompare.com/en/c…berrypi-models-comparison

Well, I've done it differently:

I attached the pi2 with the sd of the pi zero wifi to the leds: everything ok.

So I guess something on the hardware side of the pi zero is different that causes my issues.

Any help appreciated.

Wim

I thought a had a good idea to do some further testing: don't exchange the pi2 for the pi zero, exchange only their sd-cards.

On the pi2, I did:

sudo nano /etc/network/interfaces:

auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
post-up ifdown eth0
iface default inet dhcp

And:
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="xxxxxxxx"
psk="xxxxxxxx"
key_mgmt=WPA-PSK
}

And put the sd-card of the pi2 in the pi zero. Unfortunately, it doesn't boot.
Do I have to sudo raspi-config and set "Wait for network at boot" to 'no'?
I'm afraid to do so and later find out my pi2 doesn't function anymore.

Help, please??

Wim

I undid these things I mentioned in post #117:

-added to the bottom of the config.txt file dtoverlay=dwc2
-inserted in comdline.txt after rootwait: Insert modules-load=dwc2,g_ether

Doesn't seem to make a difference.

Strange thing I now noticed:
The leds start white. When I choose black color for the leds, they do but after half a second they turn white again.
And this seems to happen to all the changes I make. When I choose green, they turn green for half a second and white again. When I choose an effect, it's working for half a second and white leds again.

Is something stopping the signal?? What can I do? Should I measure voltage on pin 19 and GND?
Kodi connection error also still exists.

Update:

I detached all but 1 led strip. Leds are white when everything connected. When I choose an effect, it seems to start but stop and turn to white after half a second. Choosing the same effect does nothing, I have to choose "no effect" first.

With hypercon, I uninstalled hyperion and installed again. Got this log:

ssh out: cd /tmp && wget -nv -N https://raw.github.com/hyperio…r/bin/install_hyperion.sh && chmod +x install_hyperion.sh && sudo sh ./install_hyperion.sh HyperConInstall ; rm install_hyperion.sh
ssh out: Last-modified header missing -- time-stamps turned off.
ssh out: 2017-08-23 14:19:30 URL:https://raw.githubusercontent.…r/bin/install_hyperion.sh [14539/14539] -> "install_hyperion.sh" [1]
ssh in: *******************************************************************************
ssh in: This script will install/update Hyperion Ambient Light
ssh in: Created by brindosch - hyperion-project.org - the official Hyperion source.
ssh in: *******************************************************************************
ssh in: ---> Stop Hyperion, if necessary
ssh in: ---> Install/Update Hyperion dependencies (This may take a while)
ssh in: ---> Raspberry Pi found, but SPI is not set, we write "dtparam=spi=on" to /boot/config.txt
ssh in: ---> Downloading the appropriate Hyperion release
ssh out: 2017-08-23 14:20:35 URL:https://10gbps-io.dl.sourcefor…ease/hyperion_rpi3.tar.gz [1639953/1639953] -> "-" [1]
ssh in: ---> Installing systemd script
ssh in: ---> Starting Hyperion
ssh in: *******************************************************************************
ssh in: Hyperion Installation/Update finished!
ssh in: Please download the latest HyperCon version to benefit from new features!
ssh in: To create a config, follow the HyperCon Guide at our Wiki (EN/DE)!
ssh in: Wiki: wiki.hyperion-project.org Webpage: www.hyperion-project.org
ssh in: *******************************************************************************
ssh in: Rebooting now, we added dtparam=spi=on to config.txt

Connected again:

ssh disconnected
ssh connected
ssh out: sudo journalctl -u hyperion.service 2>/dev/null
ssh in: -- Logs begin at Wed 2017-08-23 14:20:39 CEST, end at Wed 2017-08-23 14:22:04 CEST. --
ssh in: Aug 23 14:20:47 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:20:47 raspberrypi systemd[1]: Started Hyperion Systemd service.
ssh in: Aug 23 14:20:48 raspberrypi hyperiond[361]: Hyperion Ambilight Deamon (361)
ssh in: Aug 23 14:20:49 raspberrypi hyperiond[361]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
ssh in: Aug 23 14:20:49 raspberrypi hyperiond[361]: Build Time: Jun 3 2017 02:06:37
ssh in: Aug 23 14:20:49 raspberrypi hyperiond[361]: ERROR: No valid config found
ssh in: Aug 23 14:20:49 raspberrypi systemd[1]: hyperion.service: main process exited, code=exited, status=1/FAILURE
ssh in: Aug 23 14:20:49 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Aug 23 14:20:50 raspberrypi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in: Aug 23 14:20:50 raspberrypi systemd[1]: Stopping Hyperion Systemd service...
ssh in: Aug 23 14:20:50 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:20:50 raspberrypi systemd[1]: Started Hyperion Systemd service.
ssh in: Aug 23 14:20:50 raspberrypi hyperiond[468]: Hyperion Ambilight Deamon (468)
ssh in: Aug 23 14:20:51 raspberrypi hyperiond[468]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
ssh in: Aug 23 14:20:51 raspberrypi hyperiond[468]: Build Time: Jun 3 2017 02:06:37
ssh in: Aug 23 14:20:51 raspberrypi hyperiond[468]: ERROR: No valid config found
ssh in: Aug 23 14:20:51 raspberrypi systemd[1]: hyperion.service: main process exited, code=exited, status=1/FAILURE
ssh in: Aug 23 14:20:51 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Aug 23 14:20:51 raspberrypi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in: Aug 23 14:20:51 raspberrypi systemd[1]: Stopping Hyperion Systemd service...
ssh in: Aug 23 14:20:51 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:20:51 raspberrypi systemd[1]: Started Hyperion Systemd service.
ssh in: Aug 23 14:20:52 raspberrypi hyperiond[513]: Hyperion Ambilight Deamon (513)
ssh in: Aug 23 14:20:52 raspberrypi hyperiond[513]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
ssh in: Aug 23 14:20:52 raspberrypi hyperiond[513]: Build Time: Jun 3 2017 02:06:37
ssh in: Aug 23 14:20:52 raspberrypi hyperiond[513]: ERROR: No valid config found
ssh in: Aug 23 14:20:52 raspberrypi systemd[1]: hyperion.service: main process exited, code=exited, status=1/FAILURE
ssh in: Aug 23 14:20:52 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Aug 23 14:20:52 raspberrypi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in: Aug 23 14:20:53 raspberrypi systemd[1]: Stopping Hyperion Systemd service...
ssh in: Aug 23 14:20:53 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:20:53 raspberrypi systemd[1]: Started Hyperion Systemd service.
ssh in: Aug 23 14:20:54 raspberrypi hyperiond[597]: Hyperion Ambilight Deamon (597)
ssh in: Aug 23 14:20:54 raspberrypi hyperiond[597]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
ssh in: Aug 23 14:20:54 raspberrypi hyperiond[597]: Build Time: Jun 3 2017 02:06:37
ssh in: Aug 23 14:20:54 raspberrypi hyperiond[597]: ERROR: No valid config found
ssh in: Aug 23 14:20:54 raspberrypi systemd[1]: hyperion.service: main process exited, code=exited, status=1/FAILURE
ssh in: Aug 23 14:20:54 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Aug 23 14:20:55 raspberrypi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in: Aug 23 14:20:55 raspberrypi systemd[1]: Stopping Hyperion Systemd service...
ssh in: Aug 23 14:20:55 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:20:55 raspberrypi systemd[1]: Started Hyperion Systemd service.
ssh in: Aug 23 14:20:55 raspberrypi hyperiond[636]: Hyperion Ambilight Deamon (636)
ssh in: Aug 23 14:20:55 raspberrypi hyperiond[636]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
ssh in: Aug 23 14:20:55 raspberrypi hyperiond[636]: Build Time: Jun 3 2017 02:06:37
ssh in: Aug 23 14:20:56 raspberrypi hyperiond[636]: ERROR: No valid config found
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: hyperion.service: main process exited, code=exited, status=1/FAILURE
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: Unit hyperion.service entered failed state.
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: hyperion.service holdoff time over, scheduling restart.
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: Stopping Hyperion Systemd service...
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: hyperion.service start request repeated too quickly, refusing to start.
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: Failed to start Hyperion Systemd service.
ssh in: Aug 23 14:20:56 raspberrypi systemd[1]: Unit hyperion.service entered failed state.

Copied the hyperion.config.json in with correct kodi ip-adress and restarting hyperion:

ssh in: Aug 23 14:23:55 raspberrypi systemd[1]: Starting Hyperion Systemd service...
ssh in: Aug 23 14:23:55 raspberrypi systemd[1]: Started Hyperion Systemd service.
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: Hyperion Ambilight Deamon (1068)
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: Build Time: Jun 3 2017 02:06:37
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: HYPERION INFO: ColorTransform 'default' => [0; 179]
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: HYPERION INFO: ColorCorrection 'default' => [0; 179]
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: HYPERION INFO: ColorAdjustment 'default' => [0; 179]
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: LEDDEVICE INFO: configuration:
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: {
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: "colorOrder" : "grb",
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: "name" : "MyHyperionConfig",
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: "type" : "ws2812spi"
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: }
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: INFO: Creating linear smoothing
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
ssh in: Aug 23 14:23:55 raspberrypi hyperiond[1068]: EFFECTENGINE INFO: Initializing Python interpreter
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: INFO: Hyperion started and initialised
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: INFO: Boot sequence 'Knight rider' EFFECTENGINE INFO: run effect Knight rider on channel 0
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: BLACKBORDER INFO: threshold set to 0.01 (3)
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: BLACKBORDER INFO: mode:default
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: started
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: INFO: Kodi checker created and started
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: INFO: Json server created and started on port 19444
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: INFO: Proto server created and started on port 19445
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: DISPMANXGRABBER INFO: Display opened with resolution: 720x480
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: BLACKBORDER INFO: threshold set to 0.01 (3)
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: BLACKBORDER INFO: mode:default
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: INFO: Frame grabber created and started
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: KODICHECK ERROR: Kodi Connection error (0)
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: BORDER SWITCH REQUIRED!!
ssh in: Aug 23 14:23:56 raspberrypi hyperiond[1068]: CURRENT BORDER TYPE: unknown=0 hor.size=5 vert.size=3
ssh in: Aug 23 14:24:06 raspberrypi hyperiond[1068]: KODICHECK ERROR: Kodi Connection error (0)
ssh in: Aug 23 14:24:06 raspberrypi hyperiond[1068]: EFFECTENGINE INFO: effect finished
ssh in: Aug 23 14:24:16 raspberrypi hyperiond[1068]: KODICHECK ERROR: Kodi Connection error (0)
ssh in: Aug 23 14:24:26 raspberrypi hyperiond[1068]: KODICHECK ERROR: Kodi Connection error (0)

Kodi error connection (was the same before uninstalling and reinstalling, that's the reason trying to get the android app working first).
I hope this might help analyzing the problem?

Wim
ps Did you see this:
ssh out: 2017-08-23 14:20:35 URL:https://10gbps-io.dl.sourcefor…ject/release/hyperion_rpi3.tar.gz [1639953/1639953] -> "-" [1]

Is this correct for the pi zero wifi?

Zitat von Biggles

I soldered direct to the pi, didn't see any point in adding headers.

Of course, stupid me. But that means that's not the problem here. Did you solder pin 6 and 19?

Zitat von Biggles

The link seems to be to the non WiFi version? How are you going to communicate with it?

Sorry, wrong link. Stupid me (second time...... I turned 50 yesterday, I didn't know this aging process would go that fast!). This is the correct link https://www.kiwi-electronics.n…w?search=pi%20zero%20wifi

Did you do the same I did (see post #117)?

Wim

I tried ls /dev and spi loopback test (https://www.raspberrypi.org/do…raspberrypi/spi/README.md)
both are okay.

There seems to be a little response with pi zero, but very short (some flickering of the leds) when using hyperion-lights app.

I bought this one: https://www.kiwi-electronics.n…rsie-1-3?search=pi%20zero
with an unsoldered 40-pin GPIO header. I soldered pins 6, 19 and 21. Do I need to solder all the pins for hyperion to function (perhaps because of gnd)?

Wim

Zitat von Biggles

Think the moral of this story is start with a directly connected to the strip pi zero w and forget the Arduino

Biggles, did you have to do some specific things for the pi zero?

Wim

Guys,

I need your help, again. Sorry.

While I'm completely done calibrating, working on the frame, kodi add-on etc, my first priority is to exchange the pi2 for a pi zero.

I have no clue why, but I can't seem to get it working for days now.

This is what I've done:
-formatted the sd-card, put the same image of raspbian on the card
-added to the bottom of the config.txt file dtoverlay=dwc2
-empty file ssh
-inserted in comdline.txt after rootwait: Insert modules-load=dwc2,g_ether
-connect the pi via usb to pc, connect with putty via raspberrypi.local
-added into wpa_supplicant.conf:
network={
ssid="*************"
psk="**************"
key_mgmt=WPA-PSK
}
-added into config.txt:
# activate ambilight module
dtparam=spi=on
-curl -k -L --output install_hyperion.sh --get https://raw.githubusercontent.…r/bin/install_hyperion.sh
-chmod +x install_hyperion.sh
-sudo sh ./install_hyperion.sh
-and finally copied the hyperoin.config.json to /etc/hyperion
-restarted hyperion
-connected exactly like pi2.

And then leds are not correct.

Any ideas?

Wim

Well, 1 and 4 are now perfect and the second from each sides: 2 is perfect, 3 isn't great.
You were (of course) wright about the red color meaning low voltage, I'm going to solder the connection early next week.

Strip 1, 2 and 4 are great now. Strip 3 not, so one of the connectors to 3 must be a problem, going to check that further.

Zitat von penfold42

So, 180 leds in total ?
Are you finding that the further from the power input the redder it gets ?
This is a sure sign of voltage drop along the strip.

Absolutely.

Zitat von penfold42

Applying power and ground at both ends usually helps a lot.

I'm running now to try that.

Zitat von penfold42

I suggest starting a new thread for this one with given its a very specific issue.

You're more likely to get the attention of someone who has a shield !

Ok, will do that later.

First |I've got another question. I cut the led strip into 4 and connected them with this kind of connector:

https://ledstrip-specialist.nl…k-hoekconnector-90-graden

Now, when using some colors (red, green, blue) are okay on all 4 parts, but the other colors are only correct on the first 2 parts, a bit off on the third and even more different on the fourth (often red).
In retrospect, in the temporarily setup I had before, I couldn't really see the fourth part very good. So I'm not sure if this started after diving the ledstrip or before.
I have about 60 leds horizontal (no bottom gap) and 30 vertical. WS2813.
This power supply: https://www.kiwi-electronics.n…240-AC-EU-kabel?search=5v

What the best way to check if it's a connector problem or a total voltage problem? Come to think of it, my brother-in-law has a voltage measuring device.
Is there a way to amplify the current perhaps? I already attached the 1000uF capacitor between 5V and GND of the leds.

Wim

I've been working on a frame and testing the kodi-addon. Regarding the last, I have a question.

I've got it setup like this:

but menu and pictures give no lights. Live tv and video's do. Running kodi on nvidia shield tv, all hardware disabled.

Wim
EDIT: kodi 17

Zitat von penfold42

The level shifter doesn't need a 1000uF capacitor - the led strip can benefit from a largish capacitor as a small power top ip reservoir. Think of it like a small rechargeable battery.

The chip should have a 0.01uF to 0.1uF decoupling capacitor.
http://www.ti.com/lit/an/scla007a/scla007a.pdf

Okay, so a 1000uF capacitor between +5V and GND of the led and a 0,01-0,1uF between +5V and GND of the SN74hct125?

What do you guys advise for the leds?
I understand In an angle of 45 degrees, but I don't know if I like seeing the leds from the side.
And with a opaque cover to protect against dust etc or just open (better light)?

Wim

Zitat von Biggles

This is what I built, albeit for apa102s but it might help...

https://hyperion-project.org/t…th-apa102s.822/#post-6165

Lives in a tictac 100 box behind the telly.

Referring to:

Zitat von penfold42

I don't know what page you're referring to so I'll make some guesses...

I'd recommend a capacitor between power and ground to keep the chip happy.

A series resistor on the output is really only helpful if you have a very long wire between the Pi and the 1st led but fitting it probably won't hurt

Did you mean the chip of the leds perhaps?

Zitat von penfold42

Just a small thought on the level shifter.

Most chips don't like have active inputs without power applied.
If you are likely to be powering off the led strip but want the Pi on, you may want to consider powering the level shifter with 5v
from the Pi instead of 5v from the leds.

Thanks! Yes, I was thinking leaving the pi on and the leds powered off when not using them so that's good idea.
I just got back from town to buy a capacitor 1000uF. I'll put that between pin2 of the pi (5v) and gnd of the pi.

I'm thinking of making a frame I can attach to the vesa mount at the back of the tv.
Would you advise a frosted cap over the leds or transparant or nothing at all?

Wim

Zitat von Pedro Domingos

hi, any news? my case is similar to yours, i have a shield a rp2 a ws2812b strip leds but i have dont know how to connect the leds into rp2 (in what pins)? the red cable i connect to my 5v 8a adapter, but the green and white cables iam not sure?

Hi Pedro,

I have my ws2813 (like ws2812b) working with my pi2, without arduino but with a chip. Look at the other thread I mentioned. If you have question regarding your own setup, please post them here, quoting this post of mine (so I'll get a email notification).

Wim