Howdy light fans! I'm working with George of TaskLED to come up with a great UI (User Interface - hey, some folks don't know what it means!) for the bFlex LED driver board. We already have two complete UIs on the board (selectable through the menu) - the 'F' mode is optimized for fixed lighting (lanterns, automotive, home) and the 'P' mode is for portable lighting (flashlights). The 'B' mode of bFlex will be specific to bicycle needs. Now is your chance to be heard!
Everything that the uController can do is controlled by a single momentary button that can be mounted remotely, or stay on the board. There are two ways to enter info via that button. A Click and a Press. Two distinct actions, one that releases the button immediately after use, and the other that holds the button down for a moment until the effect is achieved. George and I have spent countless hours, and have refined after many months and even years how the UIF and UIP function with that single button. I've learned quite a bit in this process, and would also like some fresh ideas from folks who aren't as mired in the details as I can get.
My basic outline for the UI so far is that it should have:
High (Level will always be settable in the menu)
Low (Maybe settable, or maybe just a consistent percentage of high, or one low level regardless of High setting)
Strobe. (should this be settable? What are some of the best choices for frequency and "on" duration? We can certainly make this settable in the menu or directly from the UI. Is it something you'd want to change often, or something you'd set once, and leave it alone?)
Let's have your input! There are no promises that your ideas will be incorporated, but I can guarantee that it'll help shape the final product. I have plenty of ideas on how to incorporate some of this, but would like to use you guys as a "clean slate" before putting my ideas up here.
Let me be very clear here that I do not do the coding or the circuit design. That's all George, and he stamps his name on the boards to prove it! Plus he's reading this, so I can't secretly take more than my share of credit. My job is to do all the really hard thinking. I try to figure out what the user will want, and how to make it the most practical to use. Then George translates it into code, and we both program a board and test for hours. Some days we'll go through countless versions of code and too many hundreds of clicks. Eventually we get it right... and that's the process I'd like to start all over again with this new UIB. So bring it on.
And one final note: Who can get some great housings made? We can by the LEDs, we can create and sell the circuit and code - but we have no way of finding that perfect housing that easily and firmly attaches to a bike. Something that could hold 2-3 LEDs, have a magnetic switch, can house a reasonably-sized Li-Ion battery, and has a great bar mount would be the bee's knees. I'd love to discuss that aspect as well, because once we get this UIB done, I'll be sitting here wondering what the hell to do with it!
Ok, NOW bring it on.
Everything that the uController can do is controlled by a single momentary button that can be mounted remotely, or stay on the board. There are two ways to enter info via that button. A Click and a Press. Two distinct actions, one that releases the button immediately after use, and the other that holds the button down for a moment until the effect is achieved. George and I have spent countless hours, and have refined after many months and even years how the UIF and UIP function with that single button. I've learned quite a bit in this process, and would also like some fresh ideas from folks who aren't as mired in the details as I can get.
My basic outline for the UI so far is that it should have:
High (Level will always be settable in the menu)
Low (Maybe settable, or maybe just a consistent percentage of high, or one low level regardless of High setting)
Strobe. (should this be settable? What are some of the best choices for frequency and "on" duration? We can certainly make this settable in the menu or directly from the UI. Is it something you'd want to change often, or something you'd set once, and leave it alone?)
Let's have your input! There are no promises that your ideas will be incorporated, but I can guarantee that it'll help shape the final product. I have plenty of ideas on how to incorporate some of this, but would like to use you guys as a "clean slate" before putting my ideas up here.
Let me be very clear here that I do not do the coding or the circuit design. That's all George, and he stamps his name on the boards to prove it! Plus he's reading this, so I can't secretly take more than my share of credit. My job is to do all the really hard thinking. I try to figure out what the user will want, and how to make it the most practical to use. Then George translates it into code, and we both program a board and test for hours. Some days we'll go through countless versions of code and too many hundreds of clicks. Eventually we get it right... and that's the process I'd like to start all over again with this new UIB. So bring it on.
And one final note: Who can get some great housings made? We can by the LEDs, we can create and sell the circuit and code - but we have no way of finding that perfect housing that easily and firmly attaches to a bike. Something that could hold 2-3 LEDs, have a magnetic switch, can house a reasonably-sized Li-Ion battery, and has a great bar mount would be the bee's knees. I'd love to discuss that aspect as well, because once we get this UIB done, I'll be sitting here wondering what the hell to do with it!
Ok, NOW bring it on.