announce
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
announce [2010/05/18 16:42] twdorris |
announce [2010/10/19 06:03] twdorris |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Product Announcements - May 18, 2010 ====== | + | ====== Product Announcements - October 19, 2010 ====== |
| We're constantly working to improve our products and roll in various requests from our users. This page will contain some updates on what we're spending our time on. | We're constantly working to improve our products and roll in various requests from our users. This page will contain some updates on what we're spending our time on. | ||
| Line 20: | Line 20: | ||
| - | ===== V3Lite ===== | + | ===== Individual deadtime controls ===== |
| - | As promised, we have provided [[v3litefirmwarechangelog|RPM-based fuel and timing adjustments]] in V3Lite to match the functionality people loved so much from the full version. We have also added full MAF compensation so you can make use of the [[v3mafadjcombft|Auto MAF Adjust]] function. Both of these functions were immediately requested by all the V3Lite users. We never knew how much people liked those controls until we released a version of our product without them. We've corrected that mistake. :) | + | With the release of [[v3firmwarechangelog|3.20.174]], we have finalized the individual deadtime controls function. |
| + | If you're not familiar with this, we have a video up of some [[http://www.youtube.com/user/ecmtuning#p/a/u/1/cO7fPmAxG50|sample results]]. Basically, you can dial in different deadtime values for each injector. This lets you fine tune the behavior of injector sets that aren't match perfectly at idle pulsewidths. Most places are not able to properly test injectors with our ECU drivers and at our typical idle pulsewidths. So while the injectors they ship may be well matched at 100%, 80% or even 20% duty cycle, they can still be VERY different at idle due to variations in deadtime from one to the next. | ||
| - | ===== Full V3 ===== | + | In addition to controlling individual deadtime, we have increased deadtime resolution as well. The factory 1G ECU runs with a resolution of 24usecs and the 2G runs with 15usecs. In previous releases, ECMLink normalized these so that both are 15usecs, but even this can be too coarse for large injectors. Running 1750s with 15usecs "jumps" in injector pulsewidth at idle is just too much. |
| - | We have nearly completed the release of individual deadtime control. If you're not familiar with this, we have a video up of some [[http://www.youtube.com/user/ecmtuning#p/a/u/1/cO7fPmAxG50|sample results]]. Basically, you can dial in different deadtime values for each injector. This lets you fine tune the behavior of injector sets that aren't match perfectly at idle pulsewidths. Most places are not able to properly test injectors with our ECU drivers and at our typical idle pulsewidths. So while the injectors they ship may be well matched at 100%, 80% or even 20% duty cycle, they can still be VERY different at idle due to variations in deadtime from one to the next. | + | |
| - | In addition to controlling individual deadtime, we have increased deadtime resolution as well. The factory 1G ECU runs with a resolution of 24usecs and the 2G runs with 15usecs. ECMLink normalizes these so that both are 15usecs, but even this can be too coarse for large injectors. Running 1750s with 15usecs "jumps" in injector pulsewidth at idle is just too much. | + | We have increased this resolution to 1 usec (!!) to match the code inside the ECU (hardware limitations still limit this to 4 usecs, but the code tracks pulsewidths down to 1 usec for increased precision). Doing so makes for much nicer idle quality with large injectors. |
| - | We have increased this resolution to 1 usecs (!!) to match the hardware limitations inside the ECU. Doing so makes for much nicer idle quality with large injectors. | ||
| + | ===== Boost controls ===== | ||
| + | With the release of [[v3firmwarechangelog|3.20.245]], we have finalized our gear-based boost control implementnation. | ||
| + | Yes, after many requests we have finally added [[boostcontrol|boost control logic]] inside the ECU. This has been a requested item for *years* and we're sorry it has taken so long to finally free up the time to work on it. But it's done now, so enjoy! | ||
| + | |||
| + | The functionality is modeled after the stock Lancer EVO code, with a few tweaks of our own thrown in. It's basically a full gear-based solution with error correction/learning built in. And unlike the current EVO version, we'll support any number of boost sensors with a simple drop down selection. We also have an "[[bcssetup|auto adjustment]]" tool to make it painfully simple to dial in. | ||
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
