Differences

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

--- v3summary [2009/10/23 07:44]
twdorris
+++ v3summary [2009/10/23 07:47]
twdorris
@@ Line 15: / Line 15: @@
 **DB9 NOTE:** We provided DB9 cables for so long in order to support the use of Palm Pilots and Windows Mobile devices.  We want to continue to provide support for these platforms so we will provide some form of DB9 cables as extra options.  The details simply haven't been defined yet on how these will be made available.
@@ Line 21: / Line 24: @@
 The 1G version of the V2 product included a memory board that not only added much needed additional RAM to the 1G platform but also provided a persistent storage solution.  Changes made by the user to the configuration of the ECU were saved permanently in non-volatile RAM.
-ECMLink V3 takes this a step further with an integrated, drop-in flash device for both 1G and 2G cars.  This device not only provides persistent storage of user configuration changes to the ECU, but it also provides direct reflash access to all the factory code & table areas as well!!  This is one of the more innovative solutions I've ever seen.  I'm biased, of course, but seriously, I've never seen anything this compact and easy to use for any other platform out there.  It's literally the size of a standard EPROM chip, but includes SOOOO MUCH more functionality.  The picture here shows this device installed in a 1G EPROM ECU.
+ECMLink V3 takes this a step further with an integrated, drop-in flash device for both 1G and 2G DSMs as well as EVO1-3 ECUs.  This device not only provides persistent storage of user configuration changes to the ECU, but it also provides direct reflash access to all the factory code & table areas as well!!
+This is one of the more innovative solutions I've ever seen.  I'm biased, of course, but seriously, I've never seen anything this compact and easy to use for any other platform out there.  It's literally the size of a standard EPROM chip, but includes SOOOO MUCH more functionality.
 ===== Direct access =====
-The term "direct access" in ECMLink refers to the ability to directly manipulate table data anywhere in the factory code.  This includes tweaking all the fuel and timing tables as well as various airflow tables and even how the ECU selects which fuel trim value to update!  Basically just about anything that controls factory operation can be adjusted to meet the needs of the user's specific setup.  The following picture shows one such table.  This particular table is the max octane ignition advance table.  The values in this table are actually pulled from a stock 2003 EVO8.  Sharing complete timing and fuel data between platforms has never been so easy.  Other sample files you can try out are listed on our [[v3configs|V3 Configs page]].
+The term "direct access" in ECMLink refers to the ability to directly manipulate table data anywhere in "code space".  This includes tweaking all the fuel and timing tables as well as various airflow tables and even how the ECU selects which fuel trim value to update!
+Basically just about anything that controls ECU operation can be adjusted to meet the needs of the user's specific setup.  The following picture shows one such table.  This particular table is the primary ignition advance table.  The values in this table are actually pulled from a stock 2003 EVO8.
+Sharing complete timing and fuel data between platforms has never been so easy.  Other sample files you can try out are listed on our [[v3configs|V3 Configs page]].
 {{http://www.ecmtuning.com/images/forums/v3peeks/v3preview-maxtmng.png |V3 Direct Access}}

ECMTuning - wiki

User Tools

Site Tools

Differences

Page Tools