+1 I would like that.
The main concern for me would be the durability of the SD card. I had many cards corrupted by pulling the power on my Pi.
If you have a good quality one or the quality of SD cards has improved in general since my experience then this may not be an issue for you.
To defend against this, it is possible to setup your operating system to be mounted as read-only. So once you get your hyperion settings tuned in exactly how you want, you can set things as read-only and there will be less of a chance of corrupting the SD card.
Here is an example of how to do that: https://email@example.com…bian-stretch-80c0f7be7353
tl;dr Use correct supply voltage or level shifters for your LEDs.
@jeroen warmerdam I don't remember ever having altered boot config and there's no mention of it in the guide I'm following: https://docs.hyperion-project.org/en/user/Installation.html. Please let me know if there's a better guide that mentions this file.
Regardless, I altered it as you recommended and the lights were still dark. Hyperion logs do not complain about anything so I assume this file is not important or not affecting functionality?
@davieboy Thanks, I realized I had to break out the big guns and I went to a friend's who had an oscilloscope.
The GPIO pins were outputting the appropriate signal.
We then removed the power supply and connected a variable one. We started it at 5V and then as we lowered the supply voltage, the lights came on!
I'm not sure what changed as I swear I've been using all the same hardware (that's what they all say). Maybe I was using another power supply that provided slightly lower voltage?
The point of the story is that the diff of signal vs supply voltage was out of spec for the LEDs.
The Vih is 0.7*Vdd and Vdd is +3.5~+5.3.
So with 5V supply voltage the pi needed to output 3.5V but it's 3.3.
I'm buying a level shifter now and this problem is SOLVED.
you can do a GPIO test
This can be used to test SPI send and receive. Put a wire between MOSI and MISO. It does not test CE0 and CE1.
gcc -o spidev_test spidev_test.c
./spidev_test -D /dev/spidev0.0
spi mode: 0
bits per word: 8
max speed: 500000 Hz (500 KHz)
FF FF FF FF FF FF
40 00 00 00 00 95
FF FF FF FF FF FF
FF FF FF FF FF FF
FF FF FF FF FF FF
DE AD BE EF BA AD
example of output after command, source https://www.raspberrypi.org/do…raspberrypi/spi/README.md
@jeroen warmerdam I tested GPIO with instructions here: https://www.raspberrypi.org/forums/viewtopic.php?t=180505
My results were:
Write 1 to gpio 17 failed.
Pull up on gpio 17 failed.
Write 1 to gpio 18 failed.
Pull up on gpio 18 failed.
Skipped non-user gpios: 0 1 28 29 30 31
Tested user gpios: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
Failed user gpios: 17 18
So this makes me think GPIO 12 should still be good.
@davieboy I previously had these same LEDs working on the same pi. I accidentally crossed some wires and the pi fuse blew out. It didn't turn back on for two days.
So when it booted up again I couldn't get things to work and figured I'd upgrade to the latest version of hyperion.
Boot config seems mostly commented:
# For more options and information see
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
# uncomment to force a console size. By default it will be display's size minus
# uncomment if hdmi display is not detected and composite is being output
# uncomment to force a specific HDMI mode (this will force VGA)
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
# uncomment for composite PAL
#uncomment to overclock the arm. 700 MHz is the default.
# Uncomment some or all of these to enable the optional hardware interfaces
# Uncomment this to enable the lirc-rpi module
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
@jeroen warmerdam I am not running Hyperbian, I'm running Raspbian.
I still edited ssh as you said with `sudo vi /etc/ssh/sshd_config`
Then I rebooted and still see no output. Thanks for the suggestion anyways.
@davieboy I was using the default instance which I renamed 2812b Ambilight. I added another instance and clicked "start" but not sure how to tie that instance to settings?
The LED visualization shows that I should be seeing the Xmas effect that I started with Remote Control tab.
I would advise NOT to do the above commands unless you use another user account to SSH into the pi, all that does is block the user root from logging in via SSH so any further access would need to be done the old fashioned way with a keyboard and mouse unless you have another user account that has SSH access.
If its permission problems then tailing the logs and fixing the the permissions would be the best way forward, could sort of see the logic in this if o/s blocks root login by default and you need to enable it if Hyperion is running on another server but not this way round.
Yeah you should be able to use any of these Hardware PWM pins available on GPIO12, GPIO13, GPIO18, GPIO19 instead of 18 (i use pin 12 as 18 is used on IR remote) but should be a case of changing the pin and controller type to RPi PWM in hyperion LED Hardware section an boom
I take it Hyperion is installed locally on the pi2 controlling the strip directly on the GPIO header?
I agree I don’t see the purpose of disabling root but I could try it. I login with “pi” user so it shouldn’t affect me?
yes, Hyperion is installed locally on the pi2 and leds connect directly to gpio header. The Hyperion dashboard loads on local network and when I tail the logs, there is no error when I switch to any of the GPIO pins you listed.
I’ve also tried bypassing the first couple of leds on the data line as they can sometimes be destroyed if I did something wrong previously.
I almost feel like there’s some “turn on” switch in Hyperion dashboard somewhere that I haven’t found yet. I have turned on effects in the Hyperion remote though so I’d assume that would work.
I'm trying to control ws2812b LEDS with a raspberry pi 2.
I've measured ~5v power at both ends of the strip.
I believe I burnt out my gpio18 because I ran a gpiotest which complained about that pin and I also tried using this method of setting pin output with bash: https://raspberrypi-aa.github.io/session2/bash.html
GPIO18 shows .2V regardless of set to high or low.
However, GPIO12 shows 3.3V or 0V when set high or low. It's also labeled as PWM0 here: https://www.raspberrypi.org/documentation/usage/gpio/
Is is possible to use GPIO12?
I've wired it up and changed my settings in Hyperion dashboard but I don't see any light.
I tried changing the effect in the dashboard remote and also using boblight server with the phone app. I see the colors change in dashboard but all LEDs remain off.
What could I be missing?
Solved by running
`sudo apt update`
`sudo apt full-upgrade`
Raspberry Pi 2 B
Raspbian GNU/Linux 9 (stretch)
What I tried
Download install file:
For install I've tried both in different installation attempts:
`sudo dpkg -i Hyperion-2.0.0-alpha.9-Linux-armv7l.deb`
AND after uninstalling
`sudo apt install ./Hyperion-2.0.0-Linux-x86_64.deb`
Then because I found a few mentions of this:
`sudo systemctl disable --now hyperiond@pi`
`sudo systemctl enable --now hyperiond@root`
`sudo reboot now`
After reboot I see:
`Dec 03 07:46:52 raspberrypi systemd: Started Hyperion ambient light systemd service for user root.`
but when I navigate to the rpi's IP on port 8090 or 8091 nothing loads.
I've also tried:
`sudo /usr/bin/hyperiond -d`
The logs hang at ` <DEBUG> Hyperion.cpp:562:handlePriorityChangedLedDevice() | No source left -> switch LED-Device off` and do not proceed.
What else can I try? Did I miss a step in the install? I'm just following this: https://docs.hyperion-project.…n.html#supported-browsers
I would prefer to not use the HyperBian image.