These are chat archives for Makuna/NeoPixelBus

6th
Jun 2015
sticilface
@sticilface
Jun 06 2015 01:01
wellcome to the green pixel crew!
Michael Miller
@Makuna
Jun 06 2015 01:05
I like to think of it as the Green Pixel Killing Party. ;-)
sticilface
@sticilface
Jun 06 2015 01:13
yaboom. green pixel killers!! ... I'm confused by it though.. ... today i've tried flirting with implementing an art-net UDP setting... i failed.. managed to get up multicast working. baby steps!
sticilface
@sticilface
Jun 06 2015 01:32
The fact
I just saw your other post in the esp forum. Does the code I sent you reproduce it for you?
Michael Miller
@Makuna
Jun 06 2015 01:57
Not yet, I just asked it there to see if anything stuck.
I still don't have a IO level converter so I run my pixels at 3.7 volts so I don't get the problem of the IO levels being more than 0.5v different from VCC that the pixels require.
sticilface
@sticilface
Jun 06 2015 20:26
right.. some new... after what you said about uninitialised variables... i went hunting and might have made things a lot lot better.... i will let you know s it is early days...
im so new to C, I had to look up exactly what an uninitialised variable actually is...
on another note i may have found a bug / behaviour that is a little unpredictable... if you use setpixelcolor and incorrectly assign a pixel above how many you have... it is fine.. (or seems to be) if you use LinearFadePixelColor and accidentally do that... i assume you get a buffer overrun... and it crashes... but crucially.. only sometimes.. (i guess it depends on adjacent memory..
sticilface
@sticilface
Jun 06 2015 20:44
i realise that if you are a careful / competent programmer then this is not a problem.. but if you are a beginner... it took me a long time to work out why it was crashing!
Michael Miller
@Makuna
Jun 06 2015 21:17
Enter an issue on that fade pixel out of bounds issue, I will go investigate and fix.
Unitized variables is one of the most common bugs in c/c++ code.