NEWBIE HERE, please help

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

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?

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.

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

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 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

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

EDIT: specific for the ws2812b or ws2813 that is

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

gpio readall:

I borrowed a multimeter. Do you want me to measure some pins?

I searched the web and found someone with a broken pi zero wifi (in fact 2 were broken, the third he got was okay):
https://github.com/PiSupply/PaPiRus/issues/81

So maybe that's the same for me? Could I rule that out measuring voltage on pins?

I measured voltage between din and gnd of the leds, both with pi2 and pi0.

Pi2: about 0.17 most of the time.
Pi0: 0.17 when correct, then about 0.27-0.31 or more after 0,5 second and leds are wrong

I have it setup to boot with knight rider, 10 seconds. Is does start off with that, but only about 4 or 5 seconds. The resulting second the voltage keeps being low, after the then seconds it turns to 0.3 or something and the leds turn white.

Guys, I don't know what to do. Buy a new pi zero? Maybe it has the same problems. Then what? Buy a third one like the guy in this thread?

https://github.com/PiSupply/PaPiRus/issues/81

Wim

Zitat von penfold42

The spi driver should be the same.

The audio doesn't matter - the zero just doesn't have the analog audio output stage on it.

Does /dev/spidev0.0 exist ? It's not enabled by default on some distributions.

What does lsmod show ?

Alles anzeigen

Pennfold,

If you have time, could you please look at my posts #129 and further? I'm getting nowhere without your help.

Wim

I just found this site googling, someone having the same problems, working config on pi2 not working on pi zero. Was supposed to work in 755 but maybe broke again later?

https://github.com/hyperion-project/hyperion/issues/753

Wim

Zitat von penfold42

I'm back (kinda)

Thank God you're back. That "kinda" doesn't sound good, I hope you're okay.

Zitat von penfold42

That issue was to do with the pwm led driver. You're using spi aren't you ?

Yes, I am. I was starting to think whether maybe the pwm driver is better for the pi0.

Zitat von penfold42

I don't have a Pi zero so can't replicate your issues.

One issue with the spi approach is that it relies on a fixed core frequency on the Pi.

Try setting core_freq to a fixed value
https://www.raspberrypi.org/do…onfig-txt/overclocking.md

I added core_freq=400 to config.txt and rebooted, but no change.

Just to be clear on the issue I'm having: when I start all leds are white. I can't turn them off. When I make any change, it lasts about half a second and than all leds are white again.

Wim

Sorry, I forgot to mention this:

When I do:
sudo hyperiond /etc/hyperion/hyperion.config.json

This is what I get:

Hyperion Ambilight Deamon (1081)
Version : V1.03.3 (brindosch-2fbbcff/2f01dfa-1495880388
Build Time: Jun 3 2017 02:06:37
INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
HYPERION INFO: ColorTransform 'default' => [0; 179]
HYPERION INFO: ColorCorrection 'default' => [0; 179]
HYPERION INFO: ColorAdjustment 'default' => [0; 179]
LEDDEVICE INFO: configuration:
{
"colorOrder" : "grb",
"name" : "MyHyperionConfig",
"type" : "ws2812spi"
}

INFO: Creating linear smoothing
HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
EFFECTENGINE INFO: Initializing Python interpreter
INFO: Hyperion started and initialised
INFO: Boot sequence 'Knight rider' EFFECTENGINE INFO: run effect Knight rider on channel 0
BLACKBORDER INFO: threshold set to 0.01 (3)
BLACKBORDER INFO: mode:default
started
INFO: Kodi checker created and started
terminate called after throwing an instance of 'std::runtime_error'
what(): JSONSERVER ERROR: could not bind to port

I hope this tells you what's the problem.

Wim