Hi all! like i promised a bit longer video.  please feel free to comment

Hi all!

like i promised a bit longer video.
please feel free to comment any tips or ideas
the first video is a major part of the standard programming
the second video is a noise matrix. dont know from who i got the code but many many many thanks!
(if the video is not smooth please dowload first)

on 4 dipswitche i can choose. all off means standard programming
dip 1 on = eco mode. brightness go to 20%
dip 2 on = used to be slow but i removed it today
dip 3 on = noise loop
dip 4 on = glamour (only glitter effect)

the suit is on the floor now.powered by a pc cpu to prevent draining of the batterypack and connected to the arduino for programming

in the video we look direct on the leds and cables. the complete suit covers it all and defuses the light

greetings
robbert

im still looking for some pattern to create one or more colored balls to move randon in the matrix

is there any option to split the output in 2 pieces like one 1-100 on pin 6 and 101-250 on pin 7 this would be awesome to have multiple outputs from my controller to prevent broken data wires

Different outputs or mirrored? If it’s mirrored, I’m pretty certain that there is an example in the IDE - yep, lots: MirroringSample, MultiArrays, MultipleStripsInOneArray, ParallelOutputDemo

no i mean. i use 500 pixels. 250 on the front and 250 on the back(both 10x25 matrix). my front and back both have a signal from de arduino. but i like to split my shirt and jeans. so the 250 pixels are split to 100(j eans) on pin 6 and 150 (shirt)on pin 7
so if i get a broken signal cable in my jeans, my shirt wil keep alive.
the only problem is that i love to program them as 250 pixels in a row
hope you know what i mean. i dont have the best english haha

I understand. Sorry. Too advanced for me.

Fantastic suit you have there, though. Very well done.

@Robbert_Loos https://plus.google.com/105445034001275025240/posts/PG727ynmhAJ

@Robbert_Loos ​, yes, you can declare one array and output two signals.

Like this
CRGB pixels[250];
FastLED.addLeds<WS2811, RGB, 6>(pixels, 100);
FastLED.addLeds<WS2811, RGB, 7>(pixels + 100, 150);

yes i found it for fasted. my programming is both fastled and neopixel does it work the same with neopixel?

for those who are interested.
this link allows you to download my programming in a .rar file

Hi @Robbert_Loos , i’ve just been picking through your code.

Very interesting patterns.

What types of LEDs are you using on your suit?

Ws2811 pixels

Ah, ok.

then in that case, i can make the code significantly smaller, which would allow you to add more effects. and easier to read.

also there are a few segments of the code that appear to make little sense, i think these may be cut and paste errors.

I’ll clean it up a bit more, then post it here for everyone to enjoy.

Thank you!. It’s my second project. I’m still busy with the code. The project needs to run in 3 weeks. At me moment I’m creating transitions on the effects. Maybe you can help me on a problem. I use both neopixel and fastled library. On the main ledsuit tab I use 4 dips witches. 1 for eco mode. Dip 4 is glamour mode. Dip 3 will be used for the noise effect (void matrix) when I uncomment the dipsetting the suit doesn’t respond until I switch on dip 3. Then it will run the matrix void. But the code said it has just to pass on when dip 3 is not activated. Hope you understand what I mean. Later today I can paste the part of code here. On dip 2 I want to place a VU meter. But till now no success in creating one. only when I power up the suit it needs to check the dip settings so it has 4 different run modes

Hi,

i’ve had a quick run through your code, and i’ve ripped out the neopixel specific stuff (you dont need it), and changed the neopixel based scenes to use the neopixel equivalent FastLED functions.

Also, you have * bright everywhere in the code. eg, setting RED to 5*bright.

So i’ve taken all of that out. bright can be set globally using the dip switch, it doesn’t need to be set at every colour request. Again it makes it easiier to understand what colour you will end up with, e.g:

CRGB::Red;

is easier to read, than:

(5bright,0bright,0*bright)

I’ve removed the colour specific functions flashRed, flashCyan etc etc, and changed flash() so you can just:

flash(CRGB::Red) or flash(CRGB::Cyan) even flash(CRGB::DarkSeaGreen) - all of the predefined colours are listed here: https://github.com/FastLED/FastLED/wiki/Pixel-reference#colors

Doing it this way means, its just one function to maintain, and its easier to read and understand.

I’m just cleaning up unused variables, that have been declared, and hold a value, but its never used. This will save valuable programming space.

Code compiled to 14,188 bytes currently.

Let me see you code, and i’ll figure out why the dip switches are not working.

Hi Robbert, very impressive suit. Did you use pre-made pixel strings or did you use custom PCBs for the pixels as well? How did you affix them to the suit? Would love to see some close-up photos…

must have been a lot of work!

yes about 3 months, just when i had some time to work on it.
wiring and programming was a lot of work. the suit is fully up and running now. tomorrow will be the first time i wear it in public on a dutch holliday. so new videos will be uploaded soon. was planning to build some extra features like a vu meter and still doesnt have the noise programming working, some error with the code. the code reads a dip setting. with dip off it wil run the programming from the video and with the dip on it will run the noise code. but there is some error, the suit doesnt respond until i flip the dipswitch. after the holliday these features will be added and also bluetooth interface so i can controll it with my phone to changse settings, patterns, and i will be able to scroll massages over the suit

Hi Robbert, i send you a message a while ago on hangouts, did you read it?