Hello,
I am designing a GPS Wayfinding/Data Logging device using the Teensy 3.2. Currently, I am using 4 LED's that denote the 4 primary cardinal directions, and blinking them at different rates to give a sense of distance...similar to the logic of an old rangefinding device:
slow blink = far away
fast blink = closer
steady light on = at location.
I am using combinations of the LED cardinal direction lights to denote the cardinal directions in between each of the primary directions, so:
North LED on + West LED on = NorthWest, etc...
I would like to indicate even more distinctions in direction and use the color information of RGB LED's for indicating other things as well...which leads me to the NeoPixel Ring as a possible solution (see the attached diagram).
My question is about the very specific timing needed to communicate with the NeoPixels and whether or not this is going to be problematic with running other functions "simultaneously." This thread deals with what I am referring to, and tni's code solution that uses interrupts to solve the blinking issue that I was having works really well for me. https://forum.pjrc.com/threads/36778-Teensy-3-2-Interrups-to-Blink-LED-s-at-Different-Rates
Are the NeoPixels the best way to proceed? Should I be thinking of other ways to address 16 different RGB LED's to implement this part of the project?
Any ideas would be super helpful.
Thanks!
Aaron
I am designing a GPS Wayfinding/Data Logging device using the Teensy 3.2. Currently, I am using 4 LED's that denote the 4 primary cardinal directions, and blinking them at different rates to give a sense of distance...similar to the logic of an old rangefinding device:
slow blink = far away
fast blink = closer
steady light on = at location.
I am using combinations of the LED cardinal direction lights to denote the cardinal directions in between each of the primary directions, so:
North LED on + West LED on = NorthWest, etc...
I would like to indicate even more distinctions in direction and use the color information of RGB LED's for indicating other things as well...which leads me to the NeoPixel Ring as a possible solution (see the attached diagram).
My question is about the very specific timing needed to communicate with the NeoPixels and whether or not this is going to be problematic with running other functions "simultaneously." This thread deals with what I am referring to, and tni's code solution that uses interrupts to solve the blinking issue that I was having works really well for me. https://forum.pjrc.com/threads/36778-Teensy-3-2-Interrups-to-Blink-LED-s-at-Different-Rates
Are the NeoPixels the best way to proceed? Should I be thinking of other ways to address 16 different RGB LED's to implement this part of the project?
Any ideas would be super helpful.
Thanks!
Aaron
Last edited: