Raspberry Pi and wh...
 
Notifications
Clear all

Raspberry Pi and what else?

12 Posts
6 Users
0 Reactions
10.1 K Views
Posts: 10
Topic starter
(@angus37)
Active Member
Joined: 14 years ago
[#52488]

Hi! Long-time subscriber, occasional lurker, first-time poster.

I want to do a "permanent" installation on my house and have the lights on for different occasions (4th of July, kids' birthdays, Denver Broncos winning the Super Bowl). I am planning on running 5V pixels and to that end have purchased a 5V 300W power supply and WS2811 pixel strings enough to do the roof outline.

My to-do list looks something like this:
1. Measure roof lines - DONE
2. Acquire pixels and power supply - DONE
3. Learn to control pixels
4. Attach lights to house
5. Wire lights to power supply/Raspberry Pi
6. Be the envy/bane of my neighbors

Here's where I am getting lost: in my mind I can do this whole thing from a Raspberry Pi. I can connect the strings directly to the Pi and write my code in CircuitPython. But in all my searching I haven't seen anyone actually doing that. So I feel like I am missing something. I see many people talking about the controllers they are using, sometimes with a Pi, sometimes without.

Can someone explain why I might not want to control my lights directly off of a Pi, and the value of the dedicated controller boards? I have this all set in my mind for how to do it and I'm struggling changing my mindset. Anyone with the voice of experience is asked to share their stories.


11 Replies
Posts: 54
(@piense)
Trusted Member
Joined: 14 years ago

The reality of the Pi is that it can't reliably control large numbers of pixels with the built in peripherals and once you get to the point of needing to expand beyond those few strands the dedicated controller boards over ethernet make a lot of practical sense. The Falcon PiCap is a good example of what can realistically be done directly from a Pi. The newest Pi has a few extra peripherals that the old ones don't, I haven't looked at the exact specs but I'd wager you might be able to drive more from them than was possible with older Pis. What's really needed are buffered UART channels (SPI might work too). You can finagle other ports to work with bit bang techniques, but they can get a bit iffy when you start doing other things with the Pi.


Reply
Posts: 672
(@pixelpuppy)
Honorable Member
Joined: 12 years ago
piense wrote:The reality of the Pi is that it can't reliably control large numbers of pixels ....

Well that depends on what you consider to be a "large number of pixels". The Pi can control 3200 pixels at 20fps and 6400 pixels at 10fps. Those are some pretty sizable numbers for a small $35 device


Reply
Posts: 54
(@piense)
Trusted Member
Joined: 14 years ago
pixelpuppy wrote:Well that depends on what you consider to be a "large number of pixels". The Pi can control 3200 pixels at 20fps and 6400 pixels at 10fps. Those are some pretty sizable numbers for a small $35 device

I could've qualified it a bit more. It does depend a lot on the fps you're after and how practical it is in a given layout to keep extending the string as far as power injection and null pixels. I personally prefer more controller ports, shorter strings, and 60 fps. But this is all for fun so if someone else wants to see how much they can push through the Pi's GPIO I'd love to see it, especially with the extra peripherals on the Pi4.


Reply
Posts: 29
(@sroberts1519)
Trusted Member
Joined: 10 years ago

I think alot of people use Falcon Pi Player with alot of success. I have never used FPP, so I can't really comment on it.

I do run my light show with a RPI, but mine is completely home grown. I wrote all of my code, mainly in Python, but also in C++ for the Teensy (arduino).

I believe my system is infinitely scaleable by adding more RPI. Last month, I did some scaling testing and I was able to control 1800 pixels (that is all the loose pixels I had at the time) with one RPI (the RPI was also the director playing the MP3, etc) and one Teensy running with a refresh rate of 25 msec. I bet I can control up to 4000 pixels with 1 Teensy. I am not sure if I can run 2 Teensy on one RPI or not - have not tested that yet.

I have 2 types of controllers - a "incandescent" controller that uses RPI GPIO ports to drive non-dimmable SSR. The other controller has RPI outputing over USB to a Teensy, and I use the OctoWS2811 board on the Teensy to connect to pixels. Starting with 2020, I will be doing a pixel only show.

I should be able to network unlimited number of RPI together to scale large shows. My show is not very large. for 2019, I had approximately 1200 pixels and 46 non-dimmable incandescent channels. For 2020 I think I will have a little over 3000 pixels.

For the pixel controller, I do generic serial communication over USB from the RPI to the Teensy/OctoWS2811.

I use Vixen to sequence, and output a fseq sequence file that the RPI reads and processes.

I don't mind sharing my code, but I really don't want to start providing alot support to people on my code, but I would be willing to provide some assistance on getting it up and running. But, if you dont have basic knowledge of the RPI and linux, then my system might not be for you. PM me if you are interested.

Oh, I use a RPI 3B+ for my light shows and for my scalable testing I did last month. I do have a RPI 4, and I know my software runs on it, and I am sure the RPI 4 will increase capacity.

Shawn


Reply
Posts: 10
Topic starter
(@angus37)
Active Member
Joined: 14 years ago

Okay...if I have done my math right I have two...channels? (Please correct my terminology when needed, I'm still learning to speak this language)

My plan is to have one run of pixels along my top floor roofline and another run along my ground floor roofline. Each will be around 400 pixels and I want to be able to control the two separate from one another. Based on this discussion it sounds like it *could* be done with a Pi, correct? I'm not closing the door on any ideas; right now I am trying to learn as much as I can.

pixelpuppy, I'm curious - do you use a Pi in your setup? Do you use it as we are discussing here or in some other fashion?


Reply
Posts: 10
Topic starter
(@angus37)
Active Member
Joined: 14 years ago
sroberts1519 wrote:I think alot of people use Falcon Pi Player with alot of success. I have never used FPP, so I can't really comment on it.

I do run my light show with a RPI, but mine is completely home grown. I wrote all of my code, mainly in Python, but also in C++ for the Teensy (arduino).

I believe my system is infinitely scaleable by adding more RPI. Last month, I did some scaling testing and I was able to control 1800 pixels (that is all the loose pixels I had at the time) with one RPI (the RPI was also the director playing the MP3, etc) and one Teensy running with a refresh rate of 25 msec. I bet I can control up to 4000 pixels with 1 Teensy. I am not sure if I can run 2 Teensy on one RPI or not - have not tested that yet.

I have 2 types of controllers - a "incandescent" controller that uses RPI GPIO ports to drive non-dimmable SSR. The other controller has RPI outputing over USB to a Teensy, and I use the OctoWS2811 board on the Teensy to connect to pixels. Starting with 2020, I will be doing a pixel only show.

I should be able to network unlimited number of RPI together to scale large shows. My show is not very large. for 2019, I had approximately 1200 pixels and 46 non-dimmable incandescent channels. For 2020 I think I will have a little over 3000 pixels.

For the pixel controller, I do generic serial communication over USB from the RPI to the Teensy/OctoWS2811.

I use Vixen to sequence, and output a fseq sequence file that the RPI reads and processes.

I don't mind sharing my code, but I really don't want to start providing alot support to people on my code, but I would be willing to provide some assistance on getting it up and running. But, if you dont have basic knowledge of the RPI and linux, then my system might not be for you. PM me if you are interested.

Oh, I use a RPI 3B+ for my light shows and for my scalable testing I did last month. I do have a RPI 4, and I know my software runs on it, and I am sure the RPI 4 will increase capacity.

Shawn

Shawn, I like the sound of what you've done. Do you have any posts on the forum about your setup? Perhaps I'll read that first and then send you a PM from there. I wouldn't want for you to be my long-distance tech support. I've done some with Pis and Linux in the past so I'm not afraid of the dirty work.


Reply
Posts: 29
(@sroberts1519)
Trusted Member
Joined: 10 years ago

I have done a few post, but may not have explained a whole lot in posts. I have learned alot on this forum, and then ran with my own ideas.

Warning, how I do things is completely against the norm of how people do things on light shows. Since I like to tinker with things, I am good with that 🙂 I started this light show road a few years ago, and part of it was the challenge of making my own system from the ground up. There are some more "commercially" available stuff such as PiHats like the ESPpixel (or whatever it is called) - which uses universe, etc, where mine is pretty much "serial communication". Those other systems may or may not be cheaper than mine. And obviously, since more people use those other systems, there would be better support on this forum 🙁

So a little bit more about my system. Defining some of my "terms"
Director - the device that "runs" the show.
Controller - a device that controls lights (lol).
There is one director per system, and one or more controllers. A RPI can be a director and a controller at the same time. each RPI has a config.xml file that is used to configure that device. Early on, I did testing with communication between RPI devices with Wifi, and hard-wired ethernet. The results I found were with the python IP stack library that I used, I had random latency between devices of over 50 msec, which really doesnt work very well 🙂 With hard-wired, I found that the IP stack library I used I had a consistant latency between RPI of around 1 msec. I guess what I am saying, is if you run multiple RPI, then a switch/wifi router and cat-5 cable is necessary. I run 2 RPI just because I can have 2 different controllers so that I can locate controllers closer to my pixel strings.

Basically, the hardware is RPI ->USB-> Teensy (with Octo2811 hat) -> pixels
Google OctoWS2811, and you should be able to find the PRJC (I think that is what it is called) website for it - also, I think Adafruit sells the hat also. The Teensy works much better than a mega-ardunio because the mega is very RAM limited where the Teensy is not. The Teensy has 8 channels, that their library controls nicely.

Some of my stuff is really basic. Such as I use crontab to schedule my show 🙂

That being said, I can't readily share my code on this site because of the size of it (like I said earlier, the code is pretty flexiable) - I think I have a couple thousand lines of code I wrote in python, and probably about 50-100 lines of code (C++) for the teensy.

So what questions do you have?

Shawn


Reply
Posts: 629
(@dkulp)
Honorable Member
Joined: 14 years ago

If you are starting out, I don't see why you wouldn't just use FPP on the Pi. You can directly wire 2 strings of ws2811 pixels to the Pi, although a level shifter/buffer is generally recommended (3.3v vs 5v). Each string can be 620pixels (for 40fps) or 1400ish for 20fps so you easily can meet your needs. It obviously "runs" fseq files natively. It has a scheduler built in. Web UI to configure everything. xLights can configure it directly so easy to setup if using xLights. It has full MQTT and Home Assistant integration. All kinds of other types of outputs to drive other types of things like other e1.31 controllers or DMX controllers or servos or gpio's or generic serial, etc.... All kinds of different types of "triggers" (like GPIO, MQTT, or REST triggers) to initiate different things. Full plugin API for more functionality. It's extremely scaleable by adding more Pi's or BBB's. It's been used to drive shows with over a million channels so well battle tested. And you can have it installed and running in a matter of minutes.


Reply
MartinMueller2003
Posts: 7614
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago
pixelpuppy wrote:Well that depends on what you consider to be a "large number of pixels". The Pi can control 3200 pixels at 20fps and 6400 pixels at 10fps. Those are some pretty sizable numbers for a small $35 device

Yes but the practicle limit has nothing to do with a PI. The OP mentioned pixels. THere are lots of pixels that go at different speeds. For clean presentation you are going to want 40FPS operation and that limits you to 680 pixels per string when using WS281x pixels. So with a PI and some sort of GPIO level shifter you get a simple 2 port (1360 pixel) show player with built in controller. For more pixels you need a show player (PI) and some controllers with more ports (lots of choices here). WARNING: Most pixels have tight timing requirements so it gets a bit difficult to "throw something together" using python etc.


Reply
Page 1 / 2
Share: