User Tools

Site Tools


announce

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
announce [2010/08/12 08:43]
twdorris
announce [2014/12/08 21:43]
twdorris removed
Line 1: Line 1:
-====== Product Announcements ​ - August 12, 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.
- 
- 
  
 ===== Release date ===== ===== Release date =====
 I know the first question coming is "​when"​. ​ As soon as we know, we'll post it.  I promise. ​ I'd rather wait until we are sure about a release date than to keep posting made-up dates and missing them.  The very minute we feel comfortable enough with a release candidate to schedule a date, we'll post it up. I know the first question coming is "​when"​. ​ As soon as we know, we'll post it.  I promise. ​ I'd rather wait until we are sure about a release date than to keep posting made-up dates and missing them.  The very minute we feel comfortable enough with a release candidate to schedule a date, we'll post it up.
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
- 
-===== Individual deadtime controls ===== 
-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. 
- 
-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 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. 
- 
-===== Boost controls ===== 
-Yes, we are finally working on boost control logic inside the ECU (actually, it's working already...we'​re just fine tuning it and writing the application pieces now).  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 we're working on it now, so expect some cool things soon. 
- 
-The functionality will be 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're also working on an "auto adjustment"​ tool to make it painfully simple to dial in. 
  
  
 ===== 2G DSM non-EPROM conversion ===== ===== 2G DSM non-EPROM conversion =====
-{{http://​www.ecmtuning.com/​images/​photos/​noneprom2g.jpg?​95x100 ​ }}Yes, we'​re ​finally nearing completion of this project. ​ We've had the 1G DSM non-EPROM ​conversion out for a whilebut the 2G version was really MUCH more difficult in terms of both design ​and fabrication. ​ Unfortunately,​ I don't expect we'll be able to offer this conversion at the same price as the 1G.  The component costs are just astronomical. ​ But, we're at a point where it doesn'​t make sense to halt the project, so we'll push it through and when someone really needs it, we'll be able to help them out. +{{http://​www.ecmtuning.com/​images/​photos/​noneprom2g.jpg?​95x100 ​ }}  We can FINALLY say we'​re ​able to convert ​non-EPROM ​9596 and 97 2G DSM ECUs!  This has taken LOOONG ​time to complete, but we're finally ​there! ​ ​The ​result is work of art and we hope will provide ​some much needed help to those looking for 2G ECUs to use with ECMLink.
- +
-Click image to enlarge. +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
-===== Native ​2G MAF connector ===== +
-{{http://​www.ecmtuning.com/​images/​photos/​2gmafconnectors.jpg?​200x130 ​ }}IMO, this is one of the coolest things we've done in long time.  It seems so simple at first, but nobody else in the world has this wire-side connector. ​ We had to custom design, prototype and mold this piece ourselves. ​ It's basically the mating piece to the 2G MAF connector on the car's wiring harness. ​ It's a properly sealed solution that doesn'​t exist anywhere else. +
- +
-We will be using this connector on our GM MAF adapters to finally ​provide a true plug-n-play solution for 2G DSMs.  ​The ​1G guys already have this because their mating connector already exists. ​ We're finally catching the 2G guys up.  :-P +
- +
-Prior to this connector we (and everyone else) had been using Delphi equivalent that just happened to sorta shove into place but was seriously lacking in a number ​of ways including the lack of a locking tab, improper fit and no sealing mechanism at all. +
- +
-We may even start providing plug-n-play SD harness conversions too.  Not sure on that one, though, because the cost gets a little crazy when you consider that we have to incorporate a buffer board of some sort at the same time due to [[2gbaroinputworkaround|compatibility issues]] with the 2G ECU's baro circuitry.+
  
 Click image to enlarge. Click image to enlarge.
Line 66: Line 15:
  
 One of the next items on our to-do list is a quick-connect feature to provide for near instant connect speeds with the ECU by caching configuration data on the laptop. ​ The application will always know whether its cache of data matches the ECUs by a complex checksum algorithm. ​ But details aside, the idea is to reduce that lengthy configuration read step to near zero. One of the next items on our to-do list is a quick-connect feature to provide for near instant connect speeds with the ECU by caching configuration data on the laptop. ​ The application will always know whether its cache of data matches the ECUs by a complex checksum algorithm. ​ But details aside, the idea is to reduce that lengthy configuration read step to near zero.
- 
- 
  
 ===== Live edit ===== ===== Live edit =====