I have searched, and most deal with code issues and latency, and delays..etc..etc..
A buddy asked me about doing a similar project as noted here:
https://forum.arduino.cc/index.php?topic=411401.0
Custom Tail Light/Blinkers (eventually custom PCB)
and
Eventually something he can use on his helmet/jacket/backpack ..etc.. (whatever)
- Neopixels tail light/pcb
- not sure what will be used for the remote nRF side of things yet
I have no issues with the code portion of things (so far)..
Normal:
Scrolling Leds:
Thanks to @Grumpy_Mike for his Adafruit non-blocking Neopixel pattern approach which I updated (molested) into something that could update multiple (different) patterns at the same time..etc..etc.. using multiple button inputs.
Anyways..
more question is more about the hardware side of things now (my kryptonite always)..
- I'm not sure/clear what kind of 'signal' I'll be dealing with here?
- I mean I know its a 12v system** (more on that below).
- but is the blinker 'signal' a constant 'hi/lo'? is there some sort of board that does the 'blinking'? (should this be bypassed then? or how do you account for multiple 'momentary' inputs then?.. I'm hoping it some sort of constant hi/lo then gone when off.. but that would be wishful thinking Im afraid! lol)
-
As mentioned in the other thread linked to above, I would use a voltage divider to get the 12v signal down to 5v for the I/O pin to detect/check for... but how do I implement the zenier diode to handle the 'full range' of over the 12v at certain times?
-
I'm guessing the constant 'power' (at all) would me running light.. and then another voltage divider to detect a pulse for the 'brake' pumping/pulsing.. that seams pretty straight forward though.. unless I'm missing something?
So I guess the main stuff is:
-
zener diode implementation?
-
if the blinker does have some sort of intermediate 'blinker relay' board, should it just be bypassed? (probably easier NOT to do so I'd imagine as far as final installment)
-
if do-not bypass (or just by design not bypassing for easier final installment), how do you suggest dealing with the 'pulse' burst of the blinker signal? (just treat the 'animation/behavior' part like it should only perform it once upon each 'input'?) like a 'one press' behavior?
*maybe I'm just overthinking most of this? just trying to prepare myself before I can get some actually data/testing done on the bike itself.
Thanks for all feedback!