Close

First draft of the Neopixel code is kind of done

A project log for E-Zpass Privacy Automation

a project to be in control and notified of what the EZpass is exactly doing in that suspicious little white box

JordanJordan 07/06/2016 at 03:520 Comments

Neopixel code is always hard to figure out for me. I think my head wants to make it harder than it is, except i can't get it to compile. I'm posting it as version 01 in the files section.

I like using the switch cases and calling functions for the events, it gives me some control over what's going on, for example, by excluding the check for a new variable, i can get all the cycles i want on the Larson scanner for the scan indicator, but the arduino IDE doesn't seem to like it. I'm getting a lot of "Not declared in this Scope" alarms

Also, this s the first time I've tried to code with0 the Wire library over the I2C lines between arduinos. Obviously i'm not ready to bench test it yet, as my code is still in need of some lovin', but its been interesting to learn about. I made the decision to have the neopixels be a Master Read/Slave Write relationship with the logic/servo arduino.

Yes, i could try to do all this on one arduino, but i can through a trinket in there to handle my 12 neopixels and simplify this so much. besides, i think this will be great practice for tackling a magnet north belt using very small vibromotors and 12C motor controlloers, but that won't be started until after this project is functional at least, if not finished.

I am going to keep working on this code, and then do up the wiring in fritzing, if i can figure that out, so it'll look spiffy and well documented.

Edit: So figured it out, Fun Fact; Arduino code wants a ; after a got label's :, i.e.

......

Label:

}

throws errors,

Label:;

}

is right, weird, huh? so my code compiles, Yeah! now to make the other side of code, the button, servo, and i2c write side of the comms.

Discussions