ronp5683 wrote:There are two ways to have the PI control your lights. You can load the files on the PI SD card and play the output to an Ethernet E1.31 bridge. The forum has a reasonably priced bridge for 6 universes. The other method is to use the I/O expander to directly feed these outputs. It seems that Ethernet is the best route because you can use the bridge with other computers.The SPI output can run fast enough to drive multiple universes. You need a part to convert the output to the muliple data streams, which is doable. You could also feed the data out the digital I/O pins as parallel data, I believe that there are at least 11 pins for this. Either way would work well. RobG is right that the LVC buffers make good converters from 3.3V to 5.0V. The E1.31 bridge uses a WIZNET chip that converts ethernet to SPI, which they use to run six universes.
Do you have a preference?
Again my thoughts - but I think we will have to go down the SPI route as the GPIO have some speed linitations.
Hi all, after a long week of stuff to do, I finally got two hours in the office/workshop.
Connected the pixels up to the PI and – nothing 🙁 so after an hour on the net it turned out that spidev is “blacklisted” in the version of kernel that I am running. So un-blacklist it and Blinky Flashy (20 sec video –not exciting, unless your me).
OK it was only 3 WS2801 pixels, but everything starts somewhere. Just over 2 weeks ago the PI was sat under a tree in wrapping paper and the two of us had never met.
I’m off to bed now happy that I have stuff that works and a base to build on. I’ll have more time tomorrow and will follow up on previous posts.
The SPI should be fast enough for most people. The E681 uses an SPI to ethernet interface, and it works fine for the four universes. If all you want to do is talk to the simple WS2801 RGB pixels, using the PI, you can build a simple buffer board, schematic enclosed. This would allow you in software to select each string with the chips selects or GPO outputs. With 2 CS, and 11 GPO available this would talk to 13 strings. Also, I forgot to put resistors from the GPO/CS to power to hold the outputs off while the PI operating system loads. The resistors to ground on the outputs hold each line inactive as you cycle through the outputs. The series resistor is for source termination and should reduce the ringing on the output signals. I like the LV/LVC family since you can use either 3.3V or 5.0V, and the are slower drivers so the output is cleaner. Also, I would run each of the outputs with ground as twisted pairs to reduce noise on the lines.
If this is all you envision then you can probably manage on your own.
So I am open to the idea of either doing an SPI or E1.31 bridge to drive WS2801 strings, DMX, serial, etc. I think I can mange to make each output type programmable under software control. Firmware updates would allow future changes for other formats. Does this interest you?
For the last post. You probably can't use the CS for the buffer output enables. The buffer enables should just be form the GPO pins.
ronp5683 wrote:The SPI should be fast enough for most people. The E681 uses an SPI to ethernet interface, and it works fine for the four universes. If all you want to do is talk to the simple WS2801 RGB pixels, using the PI, you can build a simple buffer board.
Caveat - I'm not much of a hardware person, more of a software person.
So I'm currently just working with a project that generates E1.31 running on a Pi, and sends it via Ethernet to an adjacent E680 - other than just the fun of hacking - what are the main advantages of something like the above described buffer board?:
Cost of the buffer board I assume would be less than an E680
overhead of sockets and ethernet I doubt would be much more than controlling the pin hardware at a lower level?
These are some very exciting projects, and I am hopefully getting my first Pi by the end of the month.
-P

