I agree, the wiki should be improved a bit.
As for knowing the pin, instead of using GPIO (directly controlling the pin) this method uses the SPI pins on the pi. Which means that you are using either /dev/spidev0.0 or /dev/spidev0.1 which are connected to pins 19 and 21 for /dev/spidev0.0 and to pins 24 and 26 for /dev/spidev0.1
By default the /dev/spidev0.0 device is used which uses pin 19 and 21.
It seems you're using the wrong type actually @Alex B. Goode 
The general case for this driver is actually quite simple. Here's my config:
{
"name": "MyHyperionConfig",
"type": "ws2812spi",
"colorOrder": "grb"
},I'm happy to say that the driver has been running very stable on a Pi2 with 518 leds for a couple of days now. No issues whatsoever and more than fast enough
Not sure if this kernel has the DMA driver by default but I'm running this one: Linux raspberrypi 4.4.19-v7+ #906 SMP Tue Aug 23 15:53:06 BST 2016 armv7l GNU/Linux
Seems pretty recent
Nevermind, I found it
The Raspberry Pi SPI buffer is set to 4k by default: http://stackoverflow.com/quest…i-buffer-size-in-raspbian
I have everything set up on a Pi2 now and it appears to be working
The only problem I have right now is that it appears to be limited to 341 leds. Since leds * colours per led * spi bytes per colour = 341 * 3 * 4 = 4092 I'm guessing there is some 4k limit somewhere in the SPI code but I haven't been able to find it yet.
Do you have any idea @penfold42 ?
Ah, thanks These are my first ventures with Pi GPIO... so far I've only used arduino's and custom eeproms to control electronics so it's a bit of a slow start.
Anyway... I've tried the loopback test and it indeed confirms that the Pi is at least partially dead. No useful output whatsoever from the SPI device.
I think I may have simply fried something on this Pi along the way. It's an old one anyhow so I've ordered a new pi to test.
Hyperion Ambilight Deamon (710)
Version : V1.03.0 (GitHub-b8f7642/c5d5f2d-1465599599
Build Time: Jun 11 2016 01:39:39
INFO: Selected configuration file: /etc/hyperion/hyperion.config.json.ws281x_spi
HYPERION INFO: ColorTransform 'default' => [0; 49]
HYPERION INFO: ColorCorrection 'default' => [0; 49]
HYPERION INFO: ColorAdjustment 'default' => [0; 49]
LEDDEVICE INFO: configuration:
{
"colorOrder" : "grb",
"name" : "MyHyperionConfig",
"output" : "/dev/spidev0.0",
"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 'Rainbow swirl' EFFECTENGINE INFO: run effect Rainbow swirl on channel 0
BLACKBORDER INFO: threshold set to 0 (0)
BLACKBORDER INFO: mode:default
started
INFO: Json server created and started on port 19444
INFO: Proto server created and started on port 19445
EFFECTENGINE INFO: effect finishedI'm thinking of buying this little device to check: https://www.saleae.com/
I've triple checked the wiring so I'm certain that's not the problem. Right now I'm actually thinking the SPI part of my Pi might be fried due to all my messing around.
I'll test with a different header to be sure but I'm fairly certain it's connected properly. I'm using the Adafruit Prototyping Pi shield which makes it quite difficult to pick the wrong connection
https://www.adafruit.com/product/801
Unfortunately I don't have a scope to check... perhaps I should just order one as I've missed it quite often
Since I'm unable to get it do do anything (besides a randomly colored first led) I have ordered a few level shifters just to be sure.
@penfold42 could it be that I'm setting an incorrect rate? Is there any way to debug why it's not working properly? I'm currently using the config from your commit message: https://github.com/hyperion-pr…29edb413685e700d2f1714212
Interesting - I've never test on openelec.
I'm actually running Raspbian 8 (Jessie). A stock install specifically for Hyperion a few weeks ago so it shouldn't contain anything out of the ordinary..
ZitatDoes configuring fewer LEDs work better ? Maybe the OE kernel has SPI issues with more LEDs.
I am abusing the SPI device a bit - there's an assumption the kernel will use DMA and send all the led data in one continuous burst
Just for completeness I've tried with 32 leds and I'm not able to get it to do anything anymore unfortunately.
Could it be that I need a level shifter for it to work through the MOSI pin?
Oops, forgot about that. It's mostly stock though, with the suggested changes from this topic: [MEDIA=gist]3dde4e42a3d710eba1f5e152161682f4[/MEDIA]
I've been fiddling around with the config quite a bit and I'm currently trying this device but it appears to be doing nothing at all. I should note that I'm running a Pi-1B here.
"device" :
{
"name" : "MyHyperionConfig",
"type" : "ws2812spi",
"colorOrder" : "grb",
"output" : "/dev/spidev0.0",
"rate" : 3800000
},The output when hyperion is and isn't running is currently:
# vcgencmd measure_clock core
frequency(1)=250000000I'm unable to produce any output using SPI at the moment. To be sure the led strip is functioning correctly I have tried the strip on pin 18 using this device which works:
{
"name" : "MyHyperionConfig",
"type" : "ws2812spi",
"colorOrder" : "grb"
},I've just tested a bit and similar to cbabbman I had the flashing results. After rebooting it usually doesn't start flashing but after restarting hyperion it generally starts flashing again.
When using many leds (over 300) it appears to be doing nothing but I haven't debugged that yet.
dat werkt helemaal bagger net als de libreelec add-on.
na update geen errors te zien.
het log kan hij niet schrijven de map bestaat niet.
Goed, dus je moet even een map aanmaken om het te fixen? Gelukkig is het een wiki, update de uitleg als er nog iets mist
dan hebben ze nog wat werk want ik kan ssh hyperion wel stoppen maar als ik op start druk doet hij niets.
een config file maken kan ik niet omdat ik 2 x 50 leds heb die ik niet gelijk heb gekocht de eerste 50 leds hebben een ander wit balans als de laaste 50 leds.
Eenvoudige optie, backup je huidige config, test of het dan werkt en werk vanuit dat punt?
