Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neopixel Segment Count #45

Closed
NobAkimoto opened this issue Jan 14, 2018 · 21 comments
Closed

Neopixel Segment Count #45

NobAkimoto opened this issue Jan 14, 2018 · 21 comments

Comments

@NobAkimoto
Copy link

Less an issue but more a question - what's the maximum number of segments a DIYino Stardust or DIYino Prime can handle on a neopixel strip?

I know 120 pixels seems to be the recommended top end limit - but when do the really gnarly effects start showing up in the latest fx-os?

I'd like to try strips of a full meter (144 LEDs) so wasn't sure.

@Protonerd
Copy link
Owner

Only experimenting can tell, honestly. Feel free to increase it until it fails. We made a lot of improvements lately, including freeing up some dynamic memory, but I'm reluctant to relax the limit I feel comfortable with.

@NobAkimoto
Copy link
Author

It starts getting finicky past 120 - and it basically stops functioning properly at ~130. (I was going on groups of 5). So it looks like the blade length limit to about 120 segments is still there for the most part at least if you're aiming for reliability/robustness.

@Protonerd
Copy link
Owner

I guess it is also depending on some other factors. For instance the fire blade effect needs quite a bit of dynamic memory allocated to it. If the fire blade is disabled (which was feasible in LSOS, but I made it a constant part of the neopixel setup), I can well imaging that one could go up to 130+ . When it comes to pixelcount, it's a tradeoff between FX's and count.

@shiryu55
Copy link

test, version of a week ago, with a single button and 120 led, I produced failures, with two buttons, the faults disappear, however, download the latest version and try again.

@Himmiko
Copy link

Himmiko commented Jan 23, 2018

Hi) 120 pixels is the limit. further the tape simply does not work.

@Protonerd
Copy link
Owner

That is more like a problem with your stripe I guess. If the limit is violated, the whole saber will crash.

@Drclic
Copy link

Drclic commented Feb 5, 2018

Hi Protonerd.
How exactly will it crash? Nothing functionnal? No boot? I'm trying to make one and for now nothing happens when i press the main button and I do think my neoixel tripe is too long, but i haven't cut it yet as i'm still in early testing phase, could that be the problem?

@Protonerd
Copy link
Owner

What counts is the definition of the number of pixels in the code. The physical count does not matter, at least as long as you do not switch them on (reason is, if you have too many pixels, upon switching on your blade the high current draw can cause an undervoltage and a subsequent reboot/crash, if your battery cannot deliver the needed juice).

Crash means, the system runs out of dynamic memory and will produce strange effects, sudden reboots, all kind of erratic behaviours.

@Drclic
Copy link

Drclic commented Feb 5, 2018

Ok.
So this could be the reason why nothing happens when I push the main button. I was using a 9v to 5v converter provided with the Arduino starter kit and couldn’t boot properly but managed to boot with the nano connected to usb. The led string (neopixel) is not cut, so it’s 5m long.

@jbkuma
Copy link
Collaborator

jbkuma commented Feb 5, 2018 via email

@Drclic
Copy link

Drclic commented Feb 5, 2018

But what about the usb connector of the nano? Could it power up the pixels? It was the way the saber booted, even if I followed the diagram but the power was coming from the nano itself, connected from 5v to the +row on the breadboard.
I couldn’t read the monitor as I was using my MacBook and for some reason it doesn’t see the com port properly. I’ll try again with the pc.

@Vulkan1
Copy link

Vulkan1 commented Feb 5, 2018

The nano won’t be able to output enough voltage for the pixels to function correctly, I believe I tried that myself some time ago

@jbkuma
Copy link
Collaborator

jbkuma commented Feb 5, 2018 via email

@Drclic
Copy link

Drclic commented Feb 5, 2018

Ok. Duly noted.
I was wondering, would that work with 3 aa or 3 aaa regular batteries ? Like the first sabers replicas?

@jbkuma
Copy link
Collaborator

jbkuma commented Feb 5, 2018 via email

@Drclic
Copy link

Drclic commented Feb 5, 2018

Ok. Thanks for all the information.
I’m not set on anything really, just considering all options. I thought that three 1.5v batteries would be a good option, at least for testing and mostly because I have some at home 😄 but I don’t mind getting 18650 batteries.
And just so I know, how about an external usb battery, connected with a cut wire, just vcc and gnd? Could that work, at least for testing?

@jbkuma
Copy link
Collaborator

jbkuma commented Feb 5, 2018 via email

@Drclic
Copy link

Drclic commented Feb 5, 2018

Thanks a lot for all the informations.
I ordered a couple of 18650 batteries, a charger and a holder that I'll later be able to put in the hilt.
I'll try again when I receive them.

@Drclic
Copy link

Drclic commented Feb 6, 2018

Hi again. I should receive my batteries tomorrow but it just crossed my mind, do all 18650 batteries provide 10A? I ordered batteries with 3400mah as the schematics mention 2200Mah, but is it the same thing? I'm not used to amps.

@jbkuma
Copy link
Collaborator

jbkuma commented Feb 6, 2018 via email

@Drclic
Copy link

Drclic commented Feb 16, 2018

Hi guys.
I tried again now that I have a dc 5v 10a and 18650 batteries.
I managed to boot properly and turn it on. Only thing, I commented the #define GRAVITY_COLOR line in config_SW.h so I could use the color profiles, but when I get to the main color in the config mode, the led strip (ws2812) turns off, not one pixel on and if I push the buttons, I get the sound confirming I'm changing a setting, but the color of the blade stays white.
I did not change the NUMPIXELS in the Config_HW.H is that the problem?

@jbkuma jbkuma closed this as completed Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants