Yet another noob th...
 
Notifications
Clear all

Yet another noob thread...

13 Posts
5 Users
0 Reactions
8,400 Views
Posts: 13
 v3x
Topic starter
(@v3x)
Eminent Member
Joined: 8 years ago
[#50309]

Greetings from Canada! (Montreal)

I like noob threads. I have read most of them and they always seems to answer most questions I might of had. I went though this exact same process when I started my last (I have many) project of RC rock crawlers last year and noob threads helped a lot. Same thing with DIY electronic drums 3 months ago. My wife keeps telling me I start thing and never finish. She is 60% right.

So anyways... I have always liked Christmas lights (since Christmas vacation movie). When I moved to this new place I live, I just went crazy. I mapped out the whole area I wanted to cover with lights and purchased like 500$ worth of LED strings at my local Canadian Tire. These were Noma brand. I was under the impressing that LED lights would last like 20 years so this was a future proofing investment in awesomeness. Boy was I wrong! Every single year I need to replace some. Some only light up half way, others not at all. Very frustrating. So after about 6 years, only 1 of the original 20 sets actually still works. 5% success rate.

So started looking into making my own seemed like a logical response. Did a google search and found this forum. Have been reading on and off for about 2 months, very overwhelmed by all the information. I am so happy that a place like this exists. Someone linked me to the 101 on ACL forum which was a huge help in understanding the basics.

Now I am pretty confident on getting rid of all my AC lights and completely converting to pixels for next year. Just had some questions that I have not seen an answer to yet...

At first I chose the PiCap +PI3 route but then decided to go big with the F16v3. Just seemed easier for a beginner and also future proofs.

Also only buying WS2811 12v pixels. Will have some Ray Wu customs made.

7 x 57 nodes
2 x 35
4 x 65

I know these seems like weird lengths but my goal was to mount everything on boscoyo strips and use 2" spacing. I then want to mount these sections on something more sturdy (wood maybe?) and be able to have plug n play sections to make installation/removal (or fix) easy each year. I'm assuming it would be anyways...

Now some actual questions:

1- If a single pixel dies, what happens to the whole string?
IF the whole string stops, how do I determine which is bad?
My understanding was that only the burnt pixel would stop but then I read someone talking about his mega tree having a whole string shut off. I just needed some clarification on this.

2- Assuming the controller is within 5m of all the strings, could I avoid using null pixels or famp's?
3- Also could I just not use any power injection at all and power from the controller itself? I'm trying to avoid anything complicated here. I really suck at electricity and will most likely make something explode like when trying to fix my LED lights.

4- If all my strings are on individual ports/channels of the F16, would I need to change the fuse since I'm way under the max rated amps per port? (to be safe and protect my investment)

My understanding so far of universes is that they are individual sections I want to control. (I think)

5- If I want the 7x57 nodes to do the exact same thing, would these be 1 universe or would I need to make 7 universes and just repeat the same thing in the sequence program?

The 2x35 and 4x65 will create a big rectangle (over a balcony), I'm assuming this would be 1 universe also.
6- Can I have 1 universe use 6 different ports on the controller? Or would I really need to make 1 big long string and power inject?

Obviously it would make more sense to make a long string, but the way I visioned it made more sense to me, just seemed easier for a first year project.

7- Can the SD card feature on the F16v3 be used to put the sequence job on and not actually need an ethernet connected to the controller? Or do I really need it connected for Vixen to be able to work? I kinda suck at networking and switches so less reading of stuff I don't know is always welcome...

So far I have installed Vixen and xLights and after like 30 mins of using each, was not able to do a single thing. I though maybe I needed the controller to do anything but not sure. I have not looked at any youtube videos though so I'm sure I'm just a few videos away from actually learning them. Kinda focusing on the hardware side of things right now.

Things I need to order:

13 custom strings, 729 nodes WS2811 12v (first year only as beta test, this will grow a lot once I'm comfortable)
Falcon F16v3
Falcon mounting plate
CG-1500 enclosure
2 x 12v 350w Mean Well PSU's
Many Boscoyo strips
Ray Wu Pigtail connectors (2 lots(20))
Ray Wu 3-core extensions (2 lots)

Did I miss anything to get me started?

Thank you so much for reading and for possible input and I hope to be able to make something very great for next year!!!


12 Replies
Posts: 602
Guest
(@bwinter)
Honorable Member
Joined: 10 years ago

Generally, when one pixel goes out, the remaining pixels AFTER it also go dark. Thus it’s simple to narrow down the culprit: the bad node is either the first dark or the last lit one (not sending data out)—most people just replace both at the same time.

Are custom length pixels necessary, when it’s so easy to just cut/splice standard 50-pixel sets together? I know you think you don’t want splices—but you will have them.

You don’t need active controllers to start modeling your props and designing sequences in either Vixen or Xlights


Reply
Posts: 13
 v3x
Topic starter
(@v3x)
Eminent Member
Joined: 8 years ago
Bwinter wrote:Generally, when one pixel goes out, the remaining pixels AFTER it also go dark. Thus it’s simple to narrow down the culprit: the bad node is either the first dark or the last lit one (not sending data out)—most people just replace both at the same time.

Are custom length pixels necessary, when it’s so easy to just cut/splice standard 50-pixel sets together? I know you think you don’t want splices—but you will have them.

You don’t need active controllers to start modeling your props and designing sequences in either Vixen or Xlights

Thanks for the info. It actually does seem pretty simple to just cut and splice wires. I'm surprised I have not thought of that. I just remember reading multiple times that Ray does customs so I sticked to that thought.

Again, thank you for clarifying the dead pixel question. Should be pretty easy to find the culprit and I will have a bunch of leftovers from the splicing.

Will change my order to 8 x 100 and add some pigtails.


Reply
Posts: 602
Guest
(@bwinter)
Honorable Member
Joined: 10 years ago

Ray does custom orders—but I think it’s mainly used for custom *spacing* between nodes (I.e., 3”, 6”, or something random or variable).


Reply
MartinMueller2003
Posts: 7613
(@martinmueller2003)
Illustrious Member
Joined: 14 years ago

First: Welcome. Next: I just wrote a getting started response to a new member earlier this week. You might want to look at it. You do not need a controller to get started looking at the sequencers.

  1. All of the pixels AFTER a broken pixel will either stop working or behave oddly. However, since each pixel regenerates the data signal, you cannot tell if the first non working pixel is causing the issue or is a victim of something wrong on the last pixel that looks like it is working. I replace both and dont worry about it. If the first pixel in a string is bad or the wire length is too long, then the entire string will behave badly.
  2. depends on wire quality, first pixel quality and the environment. Sometimes one meter is too long. Sometimes 10 meters works.
  3. It is up to you. I do NOT supply power from my controllers. I use 100% power injection. The wire size from the controller to the first pixel would need to be thicker on such runs to provide adequate power to drive the pixels.
  4. You are mixing wiring and effects in your mind. Make each bulb unique. You can apply the same effect to each element in your show and they will do what you are looking for.
  5. On the F16, a universe is just a way to get data to the controller. Once the data is on the F16, you can send it to as many ports as you like. The F16 does not enforce hard mappings.
  6. See 5
  7. See 5.

Reply
Page 1 / 3
Share: