Its been a long time coming! But we're there... or very nearly there anyway.
Testing has not been completed, however because this is mostly an adjustment to the existing firmware (the primary cruise routines were not modified), I believe very little testing is really required. Plus, with a programmer you can always revert back to the original firmware at any time anyway.
"Programmer?", you ask. Yes, the (now ill-fated) V2.00 attempt showed us that packing every conceivable change into a new release - so that customers would not have to ship their units back and forth very often - is problematic because one little bug can really hold things up unnecessarily. So we, in collaboration with SmartieParts, had a batch of inexpensive custom programmers made. Customers can
buy the programmer from SmartieParts, which allows you to then change the firmware of your cruise whenever you want, and as often as you want. So you can try a new release, or a different "flavor" of an existing release, or some custom release that we may come up with... and if you don't like it, change it back! Simple as that.
We had a lot of problems and delays getting the programmers, unfortunately. Initially expected by January, here we are in May and they've only just arrived. And at over double the inital cost expectation! Still, they are relatively inexpensive at $40 (from
SmartieParts), and we feel you'll be happy with what you can achieve with them.
So what
can you do with the programmers? Version 1.30.x of the firmware will be available for download very shortly (before anyone's received their programmer). The "x" in 1.30.x represents a different pedal map. So if you want to try map #13, for example, you'd download 1.30.13 and give it a try. Initially, 15 "flavors" will be available. If you don't want a pedal map of any sort, then it doesn't matter which one you get because by default they are all set to "off" anyway (you have to flip a switch to activate the map - more info to come).
Other than pedal mapping, is there any benefit to 1.30x? Well, there were some other improvements... but for the most part, no. The two other significant changes are: 1) there is now an option (by switch) to retain the last set speed into memory so it will be available when you turn your car on next time - potentially useful for commuters that often use the same speed; 2) the firmware is now functional in all markets. There is no longer a need for distinct "world" and "North American" versions. For those interested, a complete version history is included at the bottom of this post.
Other future changes, improvements, pedal maps, etc may or may not ever come about - that's mostly up to you guys! If there's something you want to see done, and we can do it without physical modification of the unit, then we'll try to accomodate. There are limitiations, of course. I mean, there's only so much that a cruise control can be besides... well, a cruise control
Anyway, I know some of you will really like playing around with the pedal maps. Get your programmer while they're hot and start playing! Give us feedback. Have fun. Be safe.
Art.
Note: For the near future, all new cruise controls will continue to ship with the V1.10 firmware. When we've received enough feedback that V1.30.x is problem-free (or any probems have been fixed) then new shipments will include one [to be determined] flavor of the new firmware only. Different flavors will be available via free download only, and a programmer will be required to use it. In other words, we don't want people asking the retailer for a specific version.
V1.30.x - [May 6, 10]
*internal improvement* use of stop_condition variable rather than complex if statement for better debugging and control of stop events.
*internal improvement* use of flash_slow variable for better debugging and control of non-standard events (going too fast, pedal override, etc).
*internal improvement* transmission signal handling uses 0x418 instead of 0x230 (USA) and 0x418 (world).
*feature removed* No longer necessary to have Euro/World versions. New transmission signal handling covers all situations.
*feature added* option for set_speed to be retained in non-volatile memory so it is available after car is powered down.
*feature added* pedal mapping feature with x pedal maps available. Each map (x) requires a different flavor of the firmware.
*internal improvement* eliminated many extraneous code elements leftover from initial R&D by Craig. Especially relating to CANBUS initialization.
*internal improvement* where practical, moved most variables from global to local scope for better compartmentalizing and efficiency.
*internal improvement* made use of hardware CANBUS filters and masks. Only the data related to the cruise control is processed for much greater reliability.
*feature change* stuck button check no longer performed at startup. LED fast flashes only when brake is pressed simultaneously with cruise button. Resolved when both brake and button are released. Previous implentation was unnecessary and buggy.
V1.20 - Abandoned in favor of V2.00 (later retracted)
V1.10 - [Apr 1, 09] Fixed window wiper bug introduced by V1.01
V1.01 - [Feb 2, 09] Added European functionality for non-North American cars (aka. "World version")
V1.00 - Initial release version
