Quote: Originally Posted by Canuck_2k
I sorry phroze-zone. I know it's tough to be the super at night and to be a normal human being during the day.
</the incredibles>
but seriously, sorry for bugging ya. I just happen to like your products and they do work really well on my car. Im just really anxious to get another one of your product on my car.
Haha. No problem. I'm excited to finally have all 3 products on my car.
The speed sensor is wired up and getting a good signal. Now I just need to write the code to make it all work. Should be easy from here...
Actually, the only trick left is figuring out how to logically organize the user interaction so that it doesn't drive anyone crazy. There are going to be a lot of features that can be set, so how can I make it easy to set them?
We've got 1 button, 1 LED (that I can't control) and 1 LED display.
So, there might be some kind of menu system where you hold it for 10 seconds to access the menu... the LED display starts flashing to indicate programming mode... You cycle to through the menu items by clicking the button: 0 -> 1 -> 2 -> 3 -> etc... Once you reach the option you want to change, you hold the button... then it gives you the current value of that option, which you set by clicking the button... when you're done you hold the button again and it jumps back to the menu...
The menu options might be:
0: Speed Dependent DAB control (0: disable, 1: enable)
1: DAB 0--> 1 transition speed (10s of MPH)
2: DAB 0--> 1 transition speed (1s of MPH)
3: DAB 1--> 3 transition speed (10s of MPH)
4: DAB 1--> 3 transition speed (1s of MPH)
5: HOM Memory (0: Default OFF, 1: Default ON, 2: Default LAST)
I don't think there's any need for a transition from DAB 1->2, since I think 2 isn't any different than 3 once you get up to speed... But, correct me if I'm wrong and you think I should put it in.
