EvoEcu - User contributions [en]

MediaWiki:Common.js

2012-01-19T23:28:55Z

EdwardMarshall: Blanked the page

MediaWiki:Common.js

2012-01-18T06:22:48Z

EdwardMarshall: Add SOPA blackout code.

var rightNow = new Date;
var intlHours = rightNow.getUTCHours();
if( 0 == rightNow.getUTCMonth() &&
2012 == rightNow.getUTCFullYear() &&
((18 == rightNow.getUTCDate() && 13 <= intlHours) || (19 == rightNow.getUTCDate() && 0 >= intlHours)))
window.location = "http://sopastrike.com/strike";

Plugs, Pins, and Connectors

2011-11-18T05:34:11Z

EdwardMarshall: Undo revision 1041 by Newunitedtech (talk)

= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.

Play nice.

== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.

= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-1&RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-2&RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172771-2&RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-1&RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-2&RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-1&RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-2&RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917975''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917975%7FA%7Fpdf%7FEnglish%7FENG_CD_917975_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917975-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=917975

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917981-1-ND
:: www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=917981

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=917989

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=917992

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=178780

''Pins:''
: Small pins (22-18AWG), '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=175265

: Large pins (20-16AWG), '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&keyword=175269

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2317-ND

''Pins:''

: Small pins (tin, 18-20AWG), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2320-ND

: Large pins (gold, 16-20AWG), '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2319-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

[new united race tech]
:i did a bit of research on these connectors, and they are compatible with the Amp / Tyco Multi-Lock 040/070 series.
:i am not sure if the JAE terminals will fit the Tyco parts or vice versa, but the plugs mate the same.

:part numbers can be found in the EVOIII 2g section

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, [http://www.newunitedracetech.com/ New United Race Tech] may have these in stock or can special-order them for you, and carries a large selection of other connectors.

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_554&products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_771&products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

[new united race tech]
:These parts fall in to what we call "2.3 I" several connector companies make a compatible series
::Sumitomo MT Unsealed Series
::Yazaki 2.3 Unsealed Series
::KET 090 Unsealed Series

:it should also be noted, that you can find compatible upgraded parts in the "2.3 II" series.
:they have a newer terminal design, and a secondary locking mechanism. we suggest to our customers they move in to the 2.3II series if possible.
::Sumitomo TS 090 Unsealed Series
::Yazaki 2.3II Unsealed Series
::KET 090II Unsealed Series

:: most of these should have a 5 digit number on the back of the connector, that can be helpful to find a vendor that can supply them to you.

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6897

: Pins Male and Female, separately (are interchangeable):
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=19_36_166_39_40

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: These Pins and Seals are compatible with the Yazaki 2.3II Sealed Series (if you cant find a TS terminal in stock anywhere)
::http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=198_265_763_268_271

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682

[new united race tech]
:the TS 090 (2.3II) is a very popular series and is a made by many companies
:: Sumitomo TS Sealed Series
:: Yazaki 2.3II Series
:: KET KUM Furukawa JST and i hear Delphi all make are similar series, detail to come.
:: all of these will have a 5 digit number on the back of the housing, and can be used to identify the connector.

:also appears in the Sumitomo MT Sealed Series as well, but i suggest the newer TS series if you can get it.
: Keyway left Female
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_937_988_27&products_id=5781

:keyway Right Female
::http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_937_988_27&products_id=5783

:keyway Right Male
::http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_937_988_27&products_id=5780

Main Page

2011-10-07T00:30:02Z

EdwardMarshall: Reverted edits by Luckiong754 (talk) to last revision by EdwardMarshall

'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

{{note|''Editors!'' if you're here to add a new page to the wiki, we appreciate the help! But please, check to see if it doesn't already exist first; we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. Just search for your topic in the sidebar, and see if there's something similar already; if there is, please help us improve by augmenting and cleaning up existing articles. Thanks!}}

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''. If you are not careful you can destroy your ECU or worse, your engine. If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health. Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you. Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM. Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.

Main Page

2011-09-30T00:27:52Z

EdwardMarshall: Reverted edits by Quencha8760 (talk) to last revision by EdwardMarshall

89280002

2011-05-09T14:17:29Z

EdwardMarshall: Add MUT table.

==Information==
Car: Mitsubisshi Lancer Evolution 9

Year: 2005

Market:

Case id:

==Replacements==

==Download files==
[[Image:89280002_EVO9_Stock.zip]]

==RAM Addresses==

;MUT Table
:<tt>35920</tt>

;2-byte load
:<tt>MUT00</tt> = <tt></tt>
:<tt>MUT01</tt> = <tt></tt>

;2-byte RPM
:<tt>MUT02</tt> = <tt></tt>
:<tt>MUT03</tt> = <tt></tt>

;2-byte AirFlow
:<tt>MUT04</tt> = <tt></tt>
:<tt>MUT05</tt> = <tt></tt>

[[Category:ROMs|89280002]]

User:EdwardMarshall

2011-02-16T15:44:11Z

EdwardMarshall:

I am [http://forums.evolutionm.net/member.php?u=9202 logic] on EvoM.

Plugs, Pins, and Connectors

2011-02-14T16:44:51Z

EdwardMarshall: /* Evo IX ECU */ Add AWG info for IX pins.

= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.

Play nice.

== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.

= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-1&RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-2&RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172771-2&RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-1&RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-2&RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-1&RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-2&RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917978-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_120

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917981-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_119

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_122

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_123

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_10_116

''Pins:''
: Small pins (22-18AWG), '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_8_127

: Large pins (20-16AWG), '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_8_126

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2317-ND

''Pins:''

: Small pins (tin, 18-20AWG), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2320-ND

: Large pins (gold, 16-20AWG), '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2319-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, it appears that [http://www.newunitedracetech.com/ New United Race Tech] can special-order these (and carries a limited selection).

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_554&products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_771&products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6897

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682

Plugs, Pins, and Connectors

2011-02-14T16:40:55Z

EdwardMarshall: /* Evo VIII and 2g DSM ECU */ Fix labeling error on VIII/2g pins.

= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.

Play nice.

== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.

= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-1&RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-2&RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172771-2&RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-1&RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-2&RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-1&RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-2&RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917978-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_120

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917981-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_119

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_122

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_123

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_10_116

''Pins:''
: Small pins (22-18AWG), '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_8_127

: Large pins (20-16AWG), '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_8_126

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, it appears that [http://www.newunitedracetech.com/ New United Race Tech] can special-order these (and carries a limited selection).

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_554&products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_771&products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6897

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682

Plugs, Pins, and Connectors

2011-01-26T05:49:43Z

EdwardMarshall: Tried to clean up some of the blatant SEO that New United added to the page. They started off good, but by the time they reached the end, they were just puking links everywhere.

= Notes...=

== ...to vendors ==

I know you guys like google-juice, and adding links to your products here helps with SEO. That's great for you, but this is a resource we use, not your playground. If you want to list ''relevant'' links to items you ''actually have in stock'', especially if you can keep with the spirit of the formatting we've already established here, that's helpful, and we're appreciative.

If you're just wanting to list a bunch of products that you don't stock regularly just to get a little additional brand awareness, they're going to be edited.

And you might not like how we edit them.

And locking the page after we edit them is a right we reserve.

Play nice.

== ...to our users ==

A '''lot''' of these parts are available to hobbyists via sample programs offered by Tyco, JAE, and others. Before spending a large sum importing or otherwise trying to track down a single part commercially, I'd strongly suggest following up on their websites to see if they can offer you a few parts for your project that way. Samples programs have a long history in the electronics industry, and you can save a significant amount of money by taking advantage of them when available.

= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172315

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172316

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=4
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172317

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&N=1
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172319

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-1&RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-2&RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172771-2&RQPN=172771-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=170352

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-1&RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-2&RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-1&RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-2&RQPN=172772-2
:: http://www.newunitedracetech.com/shop/index.php?main_page=advanced_search_result&search_in_description=1&keyword=172772

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)] .

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins, and [http://www.newunitedracetech.com/ New United Race Tech] appears to stock or be willing to special-order the pins, housings, and headers.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917978-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_120

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917981-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_119

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917989-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_122

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917992-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_9_123

: 12/16/22/26 (76) pin female (ie. ECU-side), '''178780''' ([http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F178780%7FP4%7Fpdf%7FJapanese%7FJPN_CD_178780_P4.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=178780-1-ND
:: http://www.newark.com/tyco-electronics-amp/178780-1/040-070-hybrid-cap-assy-76p/dp/12H0013
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_10_116

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175265-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_8_127

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175269-1-ND
:: http://www.newunitedracetech.com/shop/index.php?main_page=index&cPath=1_79_7_82_8_126

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178), however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these in quantity. ([http://forums.evolutionm.net/3935684-post42.html citation]).

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]; no, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors. They sell a complete kit (male and female housings, plus enough pins to fully-populate). Also, it appears that [http://www.newunitedracetech.com/ New United Race Tech] can special-order these (and carries a limited selection).

Connectors:

: Male 12-pin connector, '''M(6244-1121)''' or '''M(6520-0178)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23

: Female 12-pin connector: '''F(6244-5121)'''
:: http://www.easternbeaver.com/Main/Elec__Products/Connectors/090_Connectors/body_090_connectors.html#HRRule23
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_554&products_id=9058

Pin options:

: Gold-plated, 0.2-0.5mm cable size), '''F(8240-4849)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_25_552_553_771&products_id=9836

: Tin-plated, 0.2-0.5mm cable size, '''F(8240-4412)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5853

: Tin-plated, 0.5-1.25mm cable size), '''F(8240-4422)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5856

: Tin-plated, 2.0mm cable size, and cables are to be AVSS, '''F(8240-4652)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_31&products_id=5855

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, Ballenger Motorsports carries (as a special order item) the female plug in either an "assembly", a "kit", or as a complete pigtail, along with the pins and seals individually. New United Race Tech appears to carry (or can order) individual components as well, and Spoolinup.com (Matt Szabaga) carries either kits or pigtails.

([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors])

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

: Female plug, ''Evo'': '''F(6188-0624)'''
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6899

: Female plug, ''WRX'': '''F(6189-0249)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6235

: Male plug, ''Evo'': '''M(6189-0264)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6879

: Male plug, ''WRX'': '''M(6188-0266)'''
:: http://www.newunitedracetech.com/shop/index.php?main_page=product_info&cPath=19_36_166_39_41&products_id=6897

: Pins, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/1567

: Seals, separately (should be interchangeable):
:: http://www.bmotorsports.com/shop/product_info.php/products_id/940

: Evo kit (housing, ping, seals):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681

: Evo pigtail (assembled plug with wire, "ready-to-solder"):
:: http://www.szabaga.com/store/diyconn.html
:: http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682

Development Tips

2010-12-27T01:43:06Z

EdwardMarshall: Fix a few URLs.

This is a stream-of-consciousness document right now; edits (or comments in the Discussion tab above) are very welcome, if they can help to turn this into something a new developer can use to bootstrap. Windows-related commentary would be especially appreciated.

----

Most developers working on Evo ECU disassembly use some version of [[IDA Pro]] Advanced (the Standard and Freeware editions do not contain processor support for the SH processors in Evo ECUs).

Since most people aren't superhuman geeks, they tend to rely on an assembler for writing new code. KPIT Cummins provides a pre-built version of [http://www.gnu.org/ GNU] [http://www.gnu.org/software/binutils/ binutils] on [http://www.kpitgnutools.com/ their website], and on Windows, it integrates with their HEW environment nicely.

The KPIT tools also come with a program called <tt>sh-elf-objdump</tt>, which you may be able to use to do some VERY rudimentary disassembly.

Good reading on using IDA Pro would be [http://www.amazon.com/gp/product/1593271786?tag=edwardsmarsha The IDA Pro Book: The Unofficial Guide to the World's Most Popular Disassembler], ISBN 1593271786.

----

For those just getting started with IDA, these tools may be useful (please note: they were developed on Linux, and assume a UNIX-like command line is available; on Windows, you will need something like [http://www.cygwin.org/ Cygwin]):

;sh7052.idc
:http://dev.logic.net/hg/esm/file/tip/evo/IDA/sh7052.idc
:Following the instructions at the beginning of the file should result in an IDA database that can be used to produce a <tt>.ASM</tt> file that GNU <tt>as</tt> can use, once you run it through <tt>pcrel_filter.sh</tt>.
;pcrel_filter.sh
:http://dev.logic.net/hg/esm/file/tip/evo/IDA/pcrel_filter.sh
:An sh/awk script that reads in an IDC-produced .ASM file, and produces (hopefully) output that GNU [http://www.gnu.org/software/binutils/ binutils] can parse and re-assemble.

Once you have a workable <tt>.ASM</tt> output from <tt>pcrel_filter.sh</tt>, simply running <tt>sh-elf-as -o rom.o (filename.asm)</tt> (where <tt>(filename.asm)</tt> is your produced assembly output) will create a file named <tt>rom.o</tt>.

Then, run the linker: <tt>sh-elf-ld -o rom rom.o</tt>.

Finally, you'll need to use a command like <tt>dd if=rom of=rom.hex bs=1 skip=132 count=262144</tt> to extract the ROM image you'll want for writing to your ECU.

To ensure that your resulting output is the same as the original input, you can run the command <tt>cmp rom.hex (original ROM image)</tt>, where <tt>(original ROM image)</tt> is the filename of your original source data that you imported into IDA.

Other useful UNIX commands are <tt>hexdump</tt> (a flexible program for displaying binary data in a more useful format) and <tt>hexedit</tt> (a binary file editor).

----

For looking up additional information about the platform used in the Evo ECUs, both the Evo VIII and IX processors are based on SH-2, with the IX processor being a SH-2E variant; specifically, VIIIs use the SH7052F platform, and IXs use SH7055F. The primary difference is that the Evo VIII ECU (SH7052F) has a 256KB ROM image and 12KB of RAM, while the IX ECU (SH7055F) has a 512KB ROM image and 32KB of RAM; otherwise, the hardware is essentially the same.

; SH-2 Software Manual:
: http://documentation.renesas.com/eng/products/mpumcu/rej09b0171_superh.pdf

; SH7052F Hardware Manual:
: http://documentation.renesas.com/eng/products/mpumcu/e602185_sh7052f.pdf

; SH7055SF Hardware Manual:
: http://documentation.renesas.com/eng/products/mpumcu/rej09b0045_sh7055s.pdf

----

In addition to the GNU binutils build they provide, KPIT Cummins also provides a simulator as part of their HEW (High-performance Embedded Workshop) tool. Also, [http://www.lauterbach.com/ Lauterbach] also makes a Super-H simulator called "simsh" available as a demo for free download. Both tools are Windows-only.

EcuFlash

2010-11-30T19:57:27Z

EdwardMarshall: Added 1.24, plus a few 1.41 and 1.43 betas.

[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** First official release
** Command line supports read / flash / compare
** Supports 2001-2005 WRXs
** [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91, 2005-10-25
** This version has been created to support the new OpenPort 1.2. The OpenPort 1.2 has a 12V reflashing voltage that is controlled by RTS line of the virtual serial port which is off by default. EcuFlash now switches this voltage on at the appropriate times.
** This is intended to be the last command line version of EcuFlash. Future versions under development use a GUI and are supported under Windows / OS-X / linux.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2005-11-14
** First GUI version of EcuFlash using the [http://trolltech.com/ Qt Toolkit]
** (We only have the executable, and it might not be the official one at that.)

* 1.21, 2006-04-15
** Add support for drive by wire Subarus (STi,Forrester XT,Legacy GT,Baja,2006+ WRX)
** Switch to 'Mac' styled UI
** Add table view / editing with infinite undo
** Add user definable color maps
** Make 68HC916Y5 (WRX) kernel deal with bad serial data better

* 1.22, 2006-04-16
** Add flipx/flipy to axes widgets
** Change default color map

* 1.23, 2006-04-29
** Fix bug in SH7055 kernel that caused incorrect FMCLR register to be chosen
** Table checkboxes now single click and only hot within checkbox

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup124.exe 1.24], 2006-04-30
** Fix bug causing crash when ROM images are closed out of order

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25], 2006-05-01
** Add user level option to hide obscure tables

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26], 2006-05-10
** This is the first version to officially support Mitsubishi vehicles (Evo 7/8,Eclipse,Lancer). Some ROM definitions are included, more will be added later
** Added driver installer to EcuFlash installation
** Installer backs up your current metadata to 'backupXXX'
** Removed option to delete maps until it works
** Added a needed checksum module for DBW Subarus
** Added support for float and double data types in scalings
** Added idle category
** Improved help in scalings editor
** Adaptive cell sizing in tables
** Map windows have ROM file in the title
** Added procedure steps for connecting to Mitsubishis
** Added directory browsing to options

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27], 2006-05-15
** Some new maps added to Evos
** Improved programming voltage messages for Subaru
** Fixed bug in tracking open map views when metadata view changed
** Expanded table cell sizing a bit to prevent ellipses

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28], 2006-06-20
** Evo 9 reflash support added
** Eclipse AT reflash support added
** Evo 9 map support improved
** Update all Mitsubishi XML definitions to use new reflash tool names
** Improved cell sizing further
** Fix problem of options changing when browsing options menus and canceling
** Add support for hex data entry when editing
** Switch to Qt 4.1.3
** Remove need for C runtime DLLs
** Fix update logic when editing map definitions
** Reset reference ROM data when reading a ROM
** Fix crash on edit of table with no parent

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org
** Added some Mitsubishi ROM definitions
** Added auto-selection of OpenPort cables
** Added descriptive icons to tables in metadata view
** Fixed bug with tables having 2 generations of parents
** Fixed bug with incorrect XMLID in new ROM wizard
** Added ability to load a ROM file from the command line
** Improved color scaling handling
** Changed table to show only units for main data
** Improved table layout
** Added help text to tables
** Fix metadata ordering to match XML file order
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a], 2006-10-03
** fixed bug in install preventing driver installer from running

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. [http://forums.nasioc.com/forums/showthread.php?p=14207760#post14207760 Change of heart] from [http://forums.nasioc.com/forums/showthread.php?p=14204135#post14204135 a few months prior], yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31], 2007-08-24
** added Mac OSX (intel) support! - still some minor Qt issues on the mac...
** moved to Q 4.3.0
** 2D and 3D graphing features working
** task pane is hideable and has resizing splitter
** significant improvements to the Subaru ECU defintions thanks to merchgod
** add better visibility options for invalid or higher user level tables
** faster on-demand XML parsing
** add relative directory support in the options
** read only support for H8/539 based mitsubishis - flashing disabled due to lockout problem
** switch to true kwp2000 protocol stack for Subarus
** fix endian reversal in metadata parser - old metadata files are no longer compatible!
** add shbootmode for SH705x processor recovery
** fix asymmetry error in substeps for undo and redo. undo now does steps in exact reverse order, in case two or more substeps operate on the same data (as happens in a 2D interpolation)
** fix crash on editing of static values
** automatically detect and warn if Subarus are not in the test mode when flashing

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]2007-09-06
** removed test mode detection for 2005+ DBW Subarus because some models do not have a test mode connector

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34], 2007-11-05
** fixed crash which occurred when using older OpenPort 1.2 cables
** added automatic notification when new version is released

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35], 2007-05-15
** this is a minor update to support some recent cable changes - a major release is coming soon!
** FTDI drivers updated to CDM 2.02.06
** Qt updated to 4.4.0
** Qwt updated to 5.1.0
** bitfields now supported in bloblists ("blobbits", ie. for periphery bit editing)
** Subaru definitions update to merchgod's 0.8 release

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* 1.40.2173, 2007-10-21 (??)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178], 2007-10-??
** this release fixes a bug in op20pt32.dll which can allow older firmware to be used if the firmware update fails. using older firmware can lead to flashing failures

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412343_win.exe 1.41.2343], 200?-??-??

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412432_win.exe 1.41.2432], 200?-??-??

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483], 2009-01-29
** EcuFlash Related Changes
*** add support for EVO X CAN reflash
*** add DTC clear option for Evo X
*** add flash recovery mode option and flash recovery mode for Evo X
*** H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000b_win_beta.exe 1.43.3000b] (beta), 2010-05-23

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433095_win_beta.exe 1.43.3095] (beta), 2010-06-10

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150b_win_beta.exe 1.43.3150b] (beta), 2010-09-03

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433172_win_beta.exe 1.43.3172] (beta), 2010-10-12

OBD-II Protocol

2010-11-06T19:07:23Z

EdwardMarshall: /* Timing (in ms) */

(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from
various public internet sources. I have been successful building an ODB interface with this information,
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

:; 0-20 : Inter byte timing in ECU response
:; 25-50 : Time between end of tester request and start of ECU response or between ECU responses
:; 25-5000 : Extended mode for "rspPending"
:; 55-5000 : Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
:; 5-20 : Inter byte time in tester request

==Initialization==

===Fastinit===

_________ _____ ____ ____
\_____/ \/\/\/\/ \/\/\/\/
300ms 25ms 25ms packet response

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

_________ S ___ 2 3 ___ 6 7 ___ ____ ____
\_/0 1\___/4 5\___/P \/\/\/\/ \/\/\/\/
300ms 200 400 400 400 400 250 packet response

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit: 200ms low
#:; databit 0, 1: 400ms high
#:; databit 2, 3: 400ms low
#:; databit 4, 5: 400ms high
#:; databit 6, 7: 400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below]
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

cmd0 cmd1 ... -> result0 result1 ... comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

yy 00 -> xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

01 00 -> xx xx xx xx capabilites
01 01 -> [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
01 03 -> xx xx Fuel System Status bitmap b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
01 04 -> xx Calculated Load Value % x*100.0/255
01 05 -> xx Engine Coolant Temperature C x-40
01 06 -> xx Short term fuel trim Bank 1 % x*(100.0/128)-100
01 07 -> xx Long term fuel trim Bank 1 % x*(100.0/128)-100
01 08 -> Short term fuel trim Bank 2 % x*(100.0/128)-100
01 09 -> Long term fuel trim Bank 2 % x*(100.0/128)-100
01 0a -> Fuel Pressure kPaG x*3
01 0b -> xx Intake Manifold Pressure kPaA x
01 0c -> xx xx Engine RPM RPM x*0.25
01 0d -> xx Vehicle Speed km/h x
01 0e -> xx Ignition timing advance Cyl #1 deg X*0.5-64
01 0f -> xx Intake Air Temperature C X-40
01 10 -> xx xx Air Flow Rate gm/s X*0.01
01 11 -> xx Absolute Throttle Position % X*(100.0/255)
01 12 -> xx Commanded secondary air status
01 13 -> xx Oxygen sensor locations bitmap b0=sensor1, b1=sensor2, ..., b7=sensor8
01 14 -> xx yy Bank 1 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 15 -> xx yy Bank 1 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 16 -> Bank 1 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 17 -> Bank 1 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 18 -> Bank 2 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 19 -> Bank 2 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1a -> Bank 2 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1b -> Bank 2 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1c -> xx Auxiliary Input Status bitmap b0:PTO Active
01 20 -> xx xx xx xx capabilities
01 21 -> xx xx

02 00 00 -> xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
02 02 00 -> [dtc1h] [dtc1l] DTC that caused freezeframe

03 -> [dtc1h] [dtc1l] 00 00 00 00

05 00 00 -> xx xx xx xx capabilites

06 00 -> xx xx xx xx capabilites
06 yy -> [max=01,min=81] [valH] [valL] [limitH] [limitL]
example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
06 01 -> xx xx xx xx xx ncms
06 02 -> xx xx xx xx xx ncms
06 09 -> 01 xx xx xx xx -> 81 xx xx xx xx ncms

07 -> 00 00 00 00 00 00 cms

08 00 00 00 00 00 00 -> xx xx xx xx capabilites SMART: none

09 00 -> 01 30 00 00 00 capabilites 5 bytes???

10 Start Diagnostic Session
11 ECU Reset
12 Read Freeze Frame Data
13 Read Diagnostic Trouble Codes
14 Clear Diagnostic Information
17 Read Status Of Diagnostic Trouble Codes
18 Read Diagnostic Trouble Codes By Status
1A Read Ecu Id
20 Stop Diagnostic Session
21 Read Data By Local Id
22 Read Data By Common Id
23 Read Memory By Address
25 Stop Repeated Data Transmission
26 Set Data Rates
27 Security Access
2C Dynamically Define Local Id
2E Write Data By Common Id
2F Input Output Control By Common Id
30 Input Output Control By Local Id
31 Start Routine By Local ID
32 Stop Routine By Local ID
33 Request Routine Results By Local Id
34 Request Download
35 Request Upload
36 Transfer data
37 Request transfer exit
38 Start Routine By Address
39 Stop Routine By Address
3A Request Routine Results By Address
3B Write Data By Local Id
3D Write Memory By Address
3E Tester Present
81 -> xx xx Start Communication
82 Stop Communication
83 Access Timing Parameters
85 Start Programming Mode

===Response Failure Codes===

10 General Reject
11 Service Not Supported
12 Sub Function Not Supported - Invalid Format
21 Busy - repeat Request
22 Conditions Not Correct Or Request Sequence Error
23 Routine Not Complete Or Service In Progress
31 Request Out Of Range
33 Security Access Denied - security Access Requested
35 Invalid Key
36 Exceed Number Of Attempts
37 Required Time Delay Not Expired
40 Download Not Accepted
41 Improper Download Type
42 Can Not Download To Specified Address
43 Can Not Download Number Of Bytes Requested
50 Upload Not Accepted
51 Improper Upload Type
52 Can Not Upload From Specified Address
53 Can Not Upload Number Of Bytes Requested
71 Transfer Suspended
72 Transfer Aborted
74 Illegal Address In Block Transfer
75 Illegal Byte Count In Block Transfer
76 Illegal Block Trasnfer Type
77 Block Transfer Data Checksum Error
78 Request Correcty Rcvd - Rsp Pending
79 Incorrect Byte Count During Block Transfer
80 Service Not Supported In Active Diagnostic Mode
C1 Start Comms +ve response
C2 Stop Comms +ve response
C3 Access Timing Params +ve response
81-8F Reserved
90-F9 Vehicle manufacturer specific
FA-FE System supplier specific
FF Reserved by document

==Sample scan obtained of a SMART FOR TWO car==

--wakeup
81 -> e9 8f
--get capabilities
01 00 -> b2 3f f8 11 capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
01 20 -> 80 00 00 00 capabilities service 1: 21
02 00 00 -> 7e 38 00 00 capabilities service 2: 2 3 4 5 6 7 b c d
05 00 00 -> 7f 05 11 capabilities service 5: none
06 00 -> ff c0 80 00 capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
08 00 00 00 00 00 00 -> 7f 08 11 capabilities service 8: none
09 00 -> 01 30 00 00 00 ???? expected 4 byte response...
--get status
01 01 -> 01 07 69 00 MIL light off, 1 dtc, ready, no 02monotoring
--get dtc's
03 -> 07 02 00 00 00 00 dtc P0702
--scan sensors
01 03
01 04
01 05 -> 3a engine coolant temp = 18C (3a=58 dec - 40 dec)
01 06
01 07
01 0b
01 0c
01 0d
01 0e
01 0f
01 10
01 11
01 12
01 13 -> 03 2 sensors
01 14
01 15
01 1c
01 20 -> 80 00 00 00 (always same: capabilities 21-40)
01 21 -> 00 37

OBD-II Protocol

2010-11-06T19:06:55Z

EdwardMarshall: /* Timing (in ms) */

(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from
various public internet sources. I have been successful building an ODB interface with this information,
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

; 0-20 : Inter byte timing in ECU response
; 25-50 : Time between end of tester request and start of ECU response or between ECU responses
; 25-5000 : Extended mode for "rspPending"
; 55-5000 : Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
; 5-20 : Inter byte time in tester request

==Initialization==

===Fastinit===

_________ _____ ____ ____
\_____/ \/\/\/\/ \/\/\/\/
300ms 25ms 25ms packet response

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

_________ S ___ 2 3 ___ 6 7 ___ ____ ____
\_/0 1\___/4 5\___/P \/\/\/\/ \/\/\/\/
300ms 200 400 400 400 400 250 packet response

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit: 200ms low
#:; databit 0, 1: 400ms high
#:; databit 2, 3: 400ms low
#:; databit 4, 5: 400ms high
#:; databit 6, 7: 400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below]
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

cmd0 cmd1 ... -> result0 result1 ... comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

yy 00 -> xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

01 00 -> xx xx xx xx capabilites
01 01 -> [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
01 03 -> xx xx Fuel System Status bitmap b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
01 04 -> xx Calculated Load Value % x*100.0/255
01 05 -> xx Engine Coolant Temperature C x-40
01 06 -> xx Short term fuel trim Bank 1 % x*(100.0/128)-100
01 07 -> xx Long term fuel trim Bank 1 % x*(100.0/128)-100
01 08 -> Short term fuel trim Bank 2 % x*(100.0/128)-100
01 09 -> Long term fuel trim Bank 2 % x*(100.0/128)-100
01 0a -> Fuel Pressure kPaG x*3
01 0b -> xx Intake Manifold Pressure kPaA x
01 0c -> xx xx Engine RPM RPM x*0.25
01 0d -> xx Vehicle Speed km/h x
01 0e -> xx Ignition timing advance Cyl #1 deg X*0.5-64
01 0f -> xx Intake Air Temperature C X-40
01 10 -> xx xx Air Flow Rate gm/s X*0.01
01 11 -> xx Absolute Throttle Position % X*(100.0/255)
01 12 -> xx Commanded secondary air status
01 13 -> xx Oxygen sensor locations bitmap b0=sensor1, b1=sensor2, ..., b7=sensor8
01 14 -> xx yy Bank 1 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 15 -> xx yy Bank 1 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 16 -> Bank 1 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 17 -> Bank 1 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 18 -> Bank 2 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 19 -> Bank 2 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1a -> Bank 2 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1b -> Bank 2 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1c -> xx Auxiliary Input Status bitmap b0:PTO Active
01 20 -> xx xx xx xx capabilities
01 21 -> xx xx

02 00 00 -> xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
02 02 00 -> [dtc1h] [dtc1l] DTC that caused freezeframe

03 -> [dtc1h] [dtc1l] 00 00 00 00

05 00 00 -> xx xx xx xx capabilites

06 00 -> xx xx xx xx capabilites
06 yy -> [max=01,min=81] [valH] [valL] [limitH] [limitL]
example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
06 01 -> xx xx xx xx xx ncms
06 02 -> xx xx xx xx xx ncms
06 09 -> 01 xx xx xx xx -> 81 xx xx xx xx ncms

07 -> 00 00 00 00 00 00 cms

08 00 00 00 00 00 00 -> xx xx xx xx capabilites SMART: none

09 00 -> 01 30 00 00 00 capabilites 5 bytes???

10 Start Diagnostic Session
11 ECU Reset
12 Read Freeze Frame Data
13 Read Diagnostic Trouble Codes
14 Clear Diagnostic Information
17 Read Status Of Diagnostic Trouble Codes
18 Read Diagnostic Trouble Codes By Status
1A Read Ecu Id
20 Stop Diagnostic Session
21 Read Data By Local Id
22 Read Data By Common Id
23 Read Memory By Address
25 Stop Repeated Data Transmission
26 Set Data Rates
27 Security Access
2C Dynamically Define Local Id
2E Write Data By Common Id
2F Input Output Control By Common Id
30 Input Output Control By Local Id
31 Start Routine By Local ID
32 Stop Routine By Local ID
33 Request Routine Results By Local Id
34 Request Download
35 Request Upload
36 Transfer data
37 Request transfer exit
38 Start Routine By Address
39 Stop Routine By Address
3A Request Routine Results By Address
3B Write Data By Local Id
3D Write Memory By Address
3E Tester Present
81 -> xx xx Start Communication
82 Stop Communication
83 Access Timing Parameters
85 Start Programming Mode

===Response Failure Codes===

10 General Reject
11 Service Not Supported
12 Sub Function Not Supported - Invalid Format
21 Busy - repeat Request
22 Conditions Not Correct Or Request Sequence Error
23 Routine Not Complete Or Service In Progress
31 Request Out Of Range
33 Security Access Denied - security Access Requested
35 Invalid Key
36 Exceed Number Of Attempts
37 Required Time Delay Not Expired
40 Download Not Accepted
41 Improper Download Type
42 Can Not Download To Specified Address
43 Can Not Download Number Of Bytes Requested
50 Upload Not Accepted
51 Improper Upload Type
52 Can Not Upload From Specified Address
53 Can Not Upload Number Of Bytes Requested
71 Transfer Suspended
72 Transfer Aborted
74 Illegal Address In Block Transfer
75 Illegal Byte Count In Block Transfer
76 Illegal Block Trasnfer Type
77 Block Transfer Data Checksum Error
78 Request Correcty Rcvd - Rsp Pending
79 Incorrect Byte Count During Block Transfer
80 Service Not Supported In Active Diagnostic Mode
C1 Start Comms +ve response
C2 Stop Comms +ve response
C3 Access Timing Params +ve response
81-8F Reserved
90-F9 Vehicle manufacturer specific
FA-FE System supplier specific
FF Reserved by document

==Sample scan obtained of a SMART FOR TWO car==

--wakeup
81 -> e9 8f
--get capabilities
01 00 -> b2 3f f8 11 capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
01 20 -> 80 00 00 00 capabilities service 1: 21
02 00 00 -> 7e 38 00 00 capabilities service 2: 2 3 4 5 6 7 b c d
05 00 00 -> 7f 05 11 capabilities service 5: none
06 00 -> ff c0 80 00 capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
08 00 00 00 00 00 00 -> 7f 08 11 capabilities service 8: none
09 00 -> 01 30 00 00 00 ???? expected 4 byte response...
--get status
01 01 -> 01 07 69 00 MIL light off, 1 dtc, ready, no 02monotoring
--get dtc's
03 -> 07 02 00 00 00 00 dtc P0702
--scan sensors
01 03
01 04
01 05 -> 3a engine coolant temp = 18C (3a=58 dec - 40 dec)
01 06
01 07
01 0b
01 0c
01 0d
01 0e
01 0f
01 10
01 11
01 12
01 13 -> 03 2 sensors
01 14
01 15
01 1c
01 20 -> 80 00 00 00 (always same: capabilities 21-40)
01 21 -> 00 37

OBD-II Protocol

2010-11-06T19:05:31Z

EdwardMarshall: /* Timing (in ms) */

(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from
various public internet sources. I have been successful building an ODB interface with this information,
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

0-20 Inter byte timing in ECU response
25-50 Time between end of tester request and start of ECU response or between ECU responses
25-5000 Extended mode for "rspPending"
55-5000 Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
5-20 Inter byte time in tester request

==Initialization==

===Fastinit===

_________ _____ ____ ____
\_____/ \/\/\/\/ \/\/\/\/
300ms 25ms 25ms packet response

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

_________ S ___ 2 3 ___ 6 7 ___ ____ ____
\_/0 1\___/4 5\___/P \/\/\/\/ \/\/\/\/
300ms 200 400 400 400 400 250 packet response

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit: 200ms low
#:; databit 0, 1: 400ms high
#:; databit 2, 3: 400ms low
#:; databit 4, 5: 400ms high
#:; databit 6, 7: 400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below]
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

cmd0 cmd1 ... -> result0 result1 ... comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

yy 00 -> xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

01 00 -> xx xx xx xx capabilites
01 01 -> [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
01 03 -> xx xx Fuel System Status bitmap b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
01 04 -> xx Calculated Load Value % x*100.0/255
01 05 -> xx Engine Coolant Temperature C x-40
01 06 -> xx Short term fuel trim Bank 1 % x*(100.0/128)-100
01 07 -> xx Long term fuel trim Bank 1 % x*(100.0/128)-100
01 08 -> Short term fuel trim Bank 2 % x*(100.0/128)-100
01 09 -> Long term fuel trim Bank 2 % x*(100.0/128)-100
01 0a -> Fuel Pressure kPaG x*3
01 0b -> xx Intake Manifold Pressure kPaA x
01 0c -> xx xx Engine RPM RPM x*0.25
01 0d -> xx Vehicle Speed km/h x
01 0e -> xx Ignition timing advance Cyl #1 deg X*0.5-64
01 0f -> xx Intake Air Temperature C X-40
01 10 -> xx xx Air Flow Rate gm/s X*0.01
01 11 -> xx Absolute Throttle Position % X*(100.0/255)
01 12 -> xx Commanded secondary air status
01 13 -> xx Oxygen sensor locations bitmap b0=sensor1, b1=sensor2, ..., b7=sensor8
01 14 -> xx yy Bank 1 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 15 -> xx yy Bank 1 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 16 -> Bank 1 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 17 -> Bank 1 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 18 -> Bank 2 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 19 -> Bank 2 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1a -> Bank 2 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1b -> Bank 2 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1c -> xx Auxiliary Input Status bitmap b0:PTO Active
01 20 -> xx xx xx xx capabilities
01 21 -> xx xx

02 00 00 -> xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
02 02 00 -> [dtc1h] [dtc1l] DTC that caused freezeframe

03 -> [dtc1h] [dtc1l] 00 00 00 00

05 00 00 -> xx xx xx xx capabilites

06 00 -> xx xx xx xx capabilites
06 yy -> [max=01,min=81] [valH] [valL] [limitH] [limitL]
example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
06 01 -> xx xx xx xx xx ncms
06 02 -> xx xx xx xx xx ncms
06 09 -> 01 xx xx xx xx -> 81 xx xx xx xx ncms

07 -> 00 00 00 00 00 00 cms

08 00 00 00 00 00 00 -> xx xx xx xx capabilites SMART: none

09 00 -> 01 30 00 00 00 capabilites 5 bytes???

10 Start Diagnostic Session
11 ECU Reset
12 Read Freeze Frame Data
13 Read Diagnostic Trouble Codes
14 Clear Diagnostic Information
17 Read Status Of Diagnostic Trouble Codes
18 Read Diagnostic Trouble Codes By Status
1A Read Ecu Id
20 Stop Diagnostic Session
21 Read Data By Local Id
22 Read Data By Common Id
23 Read Memory By Address
25 Stop Repeated Data Transmission
26 Set Data Rates
27 Security Access
2C Dynamically Define Local Id
2E Write Data By Common Id
2F Input Output Control By Common Id
30 Input Output Control By Local Id
31 Start Routine By Local ID
32 Stop Routine By Local ID
33 Request Routine Results By Local Id
34 Request Download
35 Request Upload
36 Transfer data
37 Request transfer exit
38 Start Routine By Address
39 Stop Routine By Address
3A Request Routine Results By Address
3B Write Data By Local Id
3D Write Memory By Address
3E Tester Present
81 -> xx xx Start Communication
82 Stop Communication
83 Access Timing Parameters
85 Start Programming Mode

===Response Failure Codes===

10 General Reject
11 Service Not Supported
12 Sub Function Not Supported - Invalid Format
21 Busy - repeat Request
22 Conditions Not Correct Or Request Sequence Error
23 Routine Not Complete Or Service In Progress
31 Request Out Of Range
33 Security Access Denied - security Access Requested
35 Invalid Key
36 Exceed Number Of Attempts
37 Required Time Delay Not Expired
40 Download Not Accepted
41 Improper Download Type
42 Can Not Download To Specified Address
43 Can Not Download Number Of Bytes Requested
50 Upload Not Accepted
51 Improper Upload Type
52 Can Not Upload From Specified Address
53 Can Not Upload Number Of Bytes Requested
71 Transfer Suspended
72 Transfer Aborted
74 Illegal Address In Block Transfer
75 Illegal Byte Count In Block Transfer
76 Illegal Block Trasnfer Type
77 Block Transfer Data Checksum Error
78 Request Correcty Rcvd - Rsp Pending
79 Incorrect Byte Count During Block Transfer
80 Service Not Supported In Active Diagnostic Mode
C1 Start Comms +ve response
C2 Stop Comms +ve response
C3 Access Timing Params +ve response
81-8F Reserved
90-F9 Vehicle manufacturer specific
FA-FE System supplier specific
FF Reserved by document

==Sample scan obtained of a SMART FOR TWO car==

--wakeup
81 -> e9 8f
--get capabilities
01 00 -> b2 3f f8 11 capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
01 20 -> 80 00 00 00 capabilities service 1: 21
02 00 00 -> 7e 38 00 00 capabilities service 2: 2 3 4 5 6 7 b c d
05 00 00 -> 7f 05 11 capabilities service 5: none
06 00 -> ff c0 80 00 capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
08 00 00 00 00 00 00 -> 7f 08 11 capabilities service 8: none
09 00 -> 01 30 00 00 00 ???? expected 4 byte response...
--get status
01 01 -> 01 07 69 00 MIL light off, 1 dtc, ready, no 02monotoring
--get dtc's
03 -> 07 02 00 00 00 00 dtc P0702
--scan sensors
01 03
01 04
01 05 -> 3a engine coolant temp = 18C (3a=58 dec - 40 dec)
01 06
01 07
01 0b
01 0c
01 0d
01 0e
01 0f
01 10
01 11
01 12
01 13 -> 03 2 sensors
01 14
01 15
01 1c
01 20 -> 80 00 00 00 (always same: capabilities 21-40)
01 21 -> 00 37

ECU Development

2010-11-02T21:57:39Z

EdwardMarshall: /* Getting Started */ Add link to table-locating guide.

== Getting Started ==

* [[Development Tips]]
* [[Locating Tables]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]
* [[MUT Protocol]]
* [[OBD-II Protocol]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)

Locating Tables

2010-11-02T21:57:19Z

EdwardMarshall: Added; copied from my post on EvoM.

This guide is adapted from [http://forums.evolutionm.net/ecuflash/448378-dev-disassembly-beginners-guide-evo-ecu-table-lookups.html the original thread on EvoM]:

==The beginners' guide to Evo ECU table lookups==

EcuFlash provides an XML file for each ROM, which defines a bunch of tables (1D, 2D, and 3D) that can be edited by the user. Every 2D or 3D table is indexed by one or two "axis" values; it's how you look up values in the table. By way of example, the High Octane Fuel Map has both RPM and Load axes; to look up a value in the table, you first look up the current engine speed (RPM) and calculated load, and the AFR target value you're looking for is where the two intersect on the table. (2D works the same way, but there's only one dimension to worry about.)

The XML tells you where in the ROM the table and axis table data is located. Back to our example, the High Octane Fuel Map table in 96530006 is listed as being at address "33bd", with the "Engine Load" axis as being at address "68b0" and the RPM axis at address "6888". If you pull those up in IDA Pro, you'll see the data listed there, just as EcuFlash promised, but that's not the whole story; if you've ever done this, you'll notice that IDA doesn't have any code or data references listed for those ROM addresses. Every table, and every "axis table", has a header attached to it, just before the data an end-user of EcuFlash normally edits. That header data is used by a set of standard routines that every Evo ROM provides to assist in performing lookups, and the address of that header is what IDA ends up generating code and data references to.

By understanding how the ECU performs lookups in tables, it can help you to both understand when you're looking at code that performs table lookups (thus helping you locate new tables), and help you understand why you get back the values you do when the ECU performs a table lookup.

To get to the value in a table, you have to first look up the axis positions. The axis table header, just prior to the data itself, defines an address to store lookup results in, followed by the address of "current value" of that axis. For example, if the table axis is "RPM", second address is where the current vehicle RPM is stored in memory. The next word defines the number of elements in the axis, and then the axis data follows.

So, axis tables look like this:
* A long word for the result address.
* A long word for the value to look up.
* A word for the length of the axis.
* A series of words, as long as the length, containing the axis data.

Axis lookup is done by calling the routine at <tt>sub_CC6</tt>. You tell <tt>sub_CC6</tt> where the axis header is by assigning its address to <tt>r4</tt>.

For 2D tables, you perform one axis lookup; for 3D tables, you perform two. The result of each call to <tt>sub_CC6</tt> is a value stored in that axis' "result address"; it's the position in the axis that most closely (rounding down) matches the current value of the axis (ie. the position on an RPM axis that most closely matches the current engine speed).

Once you have the axis positions back from <tt>sub_CC6</tt>, you need to look up the actual table value. For byte-width tables, you call <tt>sub_C28</tt>; for word-width tables, <tt>sub_E02</tt>.

The table header has some similarities to the axis header. The first byte (or word, for <tt>sub_E02</tt>) determines whether the table has two dimensions (0x2) or three (0x3). The second byte (or word) is a global "adder" that is added to any value returned from the table. Next, a long word describes where the position on the X-axis is stored in memory (returned from <tt>sub_CC6</tt>); in a 3D table, an additional long word is included, as well as a one-byte value denoting the length of a row. After that, the table data follows, either in word (for <tt>sub_E02</tt>) or byte (<tt>sub_C28</tt>) form.

So, tables look like this:
* A byte (or word, for word-sized tables) for the number of dimensions: 2 = 2D, 3 = 3D.
* A byte (or word, for word-sized tables) for a value "added" to all values returned from the table.
* A long word for the position on the X-axis.
* Optionally, a long word for the position on the Y-axis in a 3D table.
* Optionally, a byte (or word, for word-sized tables) for the length of each row in a 3D table.
* A series of words or bytes containing the table data.

Note that the X and Y position addresses must either match the result addresses from the axis tables, or match a pair of addresses that you have manually copied the axis lookup results into.

Just like with axis lookups, you set <tt>r4</tt> to the address of the table you want to perform the look-up in. When control is returned, <tt>r0</tt> contains an interpolated value based on how "close" the axis values were to a labelled position on the axis.

So, if you see calls to <tt>sub_CC6</tt> when reading through your disassembly of a ROM, it's an indication that an axis lookup is being performed, and if you see calls to <tt>sub_C28</tt> or <tt>sub_E02</tt>, there's a table lookup happening. Looking at the lines of code leading up to that for any assignments to register <tt>r4</tt> will tell you where the axis or table headers are located. Normally, the code right after a call to <tt>sub_C28</tt> or <tt>sub_E02</tt> will assign <tt>r0</tt> to some memory address (or eventually get there, by bouncing it around from register to register), which you can log via the MUT table if you want to keep an eye on the value, and can give you an idea of what other code that uses that value is doing (for example, code that deals with the result from a High Octane Fuel Map lookup is probably involved in fueling).

Hopefully, this can help some newer folks get started with understanding one of the most common activities ECU code participates in.

OBD-II Protocol

2010-10-25T22:04:22Z

EdwardMarshall: Created page with "(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.) =OBD-II ISO 14230-2 Protocol Specification= This document describes the OBD-II ISO 142..."

(Borrowed from [http://prj.perquin.com/obdii/ Perquin] until it can be cleaned up a bit.)

=OBD-II ISO 14230-2 Protocol Specification=

This document describes the OBD-II ISO 14230-2 serial interface protocol. It has been compiled from
various public internet sources. I have been successful building an ODB interface with this information,
but no guarantee can be given that this information is correct. Use at your own risk.

==Timing (in ms)==

0-20 Inter byte timing in ECU response
25-50 Time between end of tester request and start of ECU response or between ECU responses
25-5000 Extended mode for "rspPending"
55-5000 Time between end of ECU response and start of new tester request, or time between end of tester request and start of new request if ECU doesn't respond
5-20 Inter byte time in tester request

==Initialization==

===Fastinit===

_________ _____ ____ ____
\_____/ \/\/\/\/ \/\/\/\/
300ms 25ms 25ms packet response

# Wait for 300ms with K line high.
# Pull K line low for 25 +/- 1 ms
# Let K line rise high and wait 25ms
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

===Slowinit===

_________ S ___ 2 3 ___ 6 7 ___ ____ ____
\_/0 1\___/4 5\___/P \/\/\/\/ \/\/\/\/
300ms 200 400 400 400 400 250 packet response

# Wait for 300ms with K line high.
# send a byte 33 hex at 5 baud. 200ms per bit
#:; startbit: 200ms low
#:; databit 0, 1: 400ms high
#:; databit 2, 3: 400ms low
#:; databit 4, 5: 400ms high
#:; databit 6, 7: 400ms low
#:; stopbit + pause: 250ms high
# init serial connection to 10400 baud, 8N1, 1=0Volt 0=12Volt, least significant bit first
# send package c1 33 f1 81 66 33=dest, f1=our tester id, 81=start comms
# wait for response 83 f1 01 c1 e9 8f ae 01=physical address, c1=response ok (7f=fail), e9=kb1, 8f=kb2

==Packets==

Send command packet:
:header: [c0+cmdlen] [destination=33] [source=f1]
:data: [cmd0] [cmd1] ... [cmd(cmdlen-1)]
:checksum: [sum(header)+sum(data)]

::cmd0 = service ID, cmd1 = PID

Received response packet on success:
:header: [80+datalen] [destination=f1] [source=01]
:data: [40+cmd0] [cmd1] ... [cmd(cmdlen-1)] [result0] [result1] ... [result(datalen-cmdlen-1)]
:checksum: [sum(header)+sum(data)]

Received response packet on failure:
:header: [80+datalen] [destination=f1] [source=01]
:data: [errorcode=7f] [cmd0] [Response Failure Code, see below]
:checksum: [sum(header)+sum(data)]

Multibyte data is sent high byte first.

==Tester Commands==

===Request and response packet diagram format===

cmd0 cmd1 ... -> result0 result1 ... comment

''Note:'' only the data of the request and only the result of the response are shown.

====Example====

yy 00 -> xx xx xx xx

Bitmask of capabilities for mode yy, bit7 represents pid 1, bit6 pid 2, etc, if data4:bit0 is set then pid 20 contains capabilities for pid 21-40

===00-0F: SAE J1979 Diagnostic Test Modes===

01 00 -> xx xx xx xx capabilites
01 01 -> [b7: MIL light, b0-6: dtc count] [b4-7: readiness] [b5: o2monitoring] [b0-7: readiness]
01 03 -> xx xx Fuel System Status bitmap b0:Open, b1:Closed, b2:Open-Driving, b3:Open-Fault, b4:Closed-Fault
01 04 -> xx Calculated Load Value % x*100.0/255
01 05 -> xx Engine Coolant Temperature C x-40
01 06 -> xx Short term fuel trim Bank 1 % x*(100.0/128)-100
01 07 -> xx Long term fuel trim Bank 1 % x*(100.0/128)-100
01 08 -> Short term fuel trim Bank 2 % x*(100.0/128)-100
01 09 -> Long term fuel trim Bank 2 % x*(100.0/128)-100
01 0a -> Fuel Pressure kPaG x*3
01 0b -> xx Intake Manifold Pressure kPaA x
01 0c -> xx xx Engine RPM RPM x*0.25
01 0d -> xx Vehicle Speed km/h x
01 0e -> xx Ignition timing advance Cyl #1 deg X*0.5-64
01 0f -> xx Intake Air Temperature C X-40
01 10 -> xx xx Air Flow Rate gm/s X*0.01
01 11 -> xx Absolute Throttle Position % X*(100.0/255)
01 12 -> xx Commanded secondary air status
01 13 -> xx Oxygen sensor locations bitmap b0=sensor1, b1=sensor2, ..., b7=sensor8
01 14 -> xx yy Bank 1 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 15 -> xx yy Bank 1 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 16 -> Bank 1 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 17 -> Bank 1 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 18 -> Bank 2 Sensor 1 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 19 -> Bank 2 Sensor 2 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1a -> Bank 2 Sensor 3 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1b -> Bank 2 Sensor 4 Voltage/Trim V, % x*0.005, if y!=ff then y*(100.0/128)-100)
01 1c -> xx Auxiliary Input Status bitmap b0:PTO Active
01 20 -> xx xx xx xx capabilities
01 21 -> xx xx

02 00 00 -> xx xx xx xx capabilites SMART: 2 3 4 5 6 7 b c d
02 02 00 -> [dtc1h] [dtc1l] DTC that caused freezeframe

03 -> [dtc1h] [dtc1l] 00 00 00 00

05 00 00 -> xx xx xx xx capabilites

06 00 -> xx xx xx xx capabilites
06 yy -> [max=01,min=81] [valH] [valL] [limitH] [limitL]
example 01 00 23 01 2c is value 23 (=35 dec) with limit maximum 12c (=300 dec)
06 01 -> xx xx xx xx xx ncms
06 02 -> xx xx xx xx xx ncms
06 09 -> 01 xx xx xx xx -> 81 xx xx xx xx ncms

07 -> 00 00 00 00 00 00 cms

08 00 00 00 00 00 00 -> xx xx xx xx capabilites SMART: none

09 00 -> 01 30 00 00 00 capabilites 5 bytes???

10 Start Diagnostic Session
11 ECU Reset
12 Read Freeze Frame Data
13 Read Diagnostic Trouble Codes
14 Clear Diagnostic Information
17 Read Status Of Diagnostic Trouble Codes
18 Read Diagnostic Trouble Codes By Status
1A Read Ecu Id
20 Stop Diagnostic Session
21 Read Data By Local Id
22 Read Data By Common Id
23 Read Memory By Address
25 Stop Repeated Data Transmission
26 Set Data Rates
27 Security Access
2C Dynamically Define Local Id
2E Write Data By Common Id
2F Input Output Control By Common Id
30 Input Output Control By Local Id
31 Start Routine By Local ID
32 Stop Routine By Local ID
33 Request Routine Results By Local Id
34 Request Download
35 Request Upload
36 Transfer data
37 Request transfer exit
38 Start Routine By Address
39 Stop Routine By Address
3A Request Routine Results By Address
3B Write Data By Local Id
3D Write Memory By Address
3E Tester Present
81 -> xx xx Start Communication
82 Stop Communication
83 Access Timing Parameters
85 Start Programming Mode

===Response Failure Codes===

10 General Reject
11 Service Not Supported
12 Sub Function Not Supported - Invalid Format
21 Busy - repeat Request
22 Conditions Not Correct Or Request Sequence Error
23 Routine Not Complete Or Service In Progress
31 Request Out Of Range
33 Security Access Denied - security Access Requested
35 Invalid Key
36 Exceed Number Of Attempts
37 Required Time Delay Not Expired
40 Download Not Accepted
41 Improper Download Type
42 Can Not Download To Specified Address
43 Can Not Download Number Of Bytes Requested
50 Upload Not Accepted
51 Improper Upload Type
52 Can Not Upload From Specified Address
53 Can Not Upload Number Of Bytes Requested
71 Transfer Suspended
72 Transfer Aborted
74 Illegal Address In Block Transfer
75 Illegal Byte Count In Block Transfer
76 Illegal Block Trasnfer Type
77 Block Transfer Data Checksum Error
78 Request Correcty Rcvd - Rsp Pending
79 Incorrect Byte Count During Block Transfer
80 Service Not Supported In Active Diagnostic Mode
C1 Start Comms +ve response
C2 Stop Comms +ve response
C3 Access Timing Params +ve response
81-8F Reserved
90-F9 Vehicle manufacturer specific
FA-FE System supplier specific
FF Reserved by document

==Sample scan obtained of a SMART FOR TWO car==

--wakeup
81 -> e9 8f
--get capabilities
01 00 -> b2 3f f8 11 capabilities service 1: 1 3 4 5 6 7 b v d e f 10 11 12 13 14 15 1c 20
01 20 -> 80 00 00 00 capabilities service 1: 21
02 00 00 -> 7e 38 00 00 capabilities service 2: 2 3 4 5 6 7 b c d
05 00 00 -> 7f 05 11 capabilities service 5: none
06 00 -> ff c0 80 00 capabilities service 6: 1 2 3 4 5 6 7 8 9 a 11
08 00 00 00 00 00 00 -> 7f 08 11 capabilities service 8: none
09 00 -> 01 30 00 00 00 ???? expected 4 byte response...
--get status
01 01 -> 01 07 69 00 MIL light off, 1 dtc, ready, no 02monotoring
--get dtc's
03 -> 07 02 00 00 00 00 dtc P0702
--scan sensors
01 03
01 04
01 05 -> 3a engine coolant temp = 18C (3a=58 dec - 40 dec)
01 06
01 07
01 0b
01 0c
01 0d
01 0e
01 0f
01 10
01 11
01 12
01 13 -> 03 2 sensors
01 14
01 15
01 1c
01 20 -> 80 00 00 00 (always same: capabilities 21-40)
01 21 -> 00 37

ECU Development

2010-10-25T21:31:24Z

EdwardMarshall: /* Communications */

== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]
* [[MUT Protocol]]
* [[OBD-II Protocol]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)

MUT Protocol

2010-10-25T15:52:11Z

EdwardMarshall: More initial information, needs cleanup.

==MUT==

Quoted from http://www.myrollingroad.com/showthread.php?t=60 CLaNZeR@MyRollingRoad]:

:Okay the Mut Protocol Init is alot like the ISO9141-2 Init.

:We will be using 1 of the Pins from the OBD-II Connector for communicating.

:Pin7 K line

:If you take a Pin HIGH this means you are applying 12Volts to it.
:If you take the Pin LOW you are applying 0V

:The first thing that you need to do is to initialise the ECU so it knows you want to communicate.

:This is done with the following routine:

::'Slow Init
::Take K Line High
::Pause 300ms

::'Send 0x01 (00000001) at rate of 5 baud (LSB) with a Start Bit and a Stop bit

::'Send Startbit
::Set K line low (0)
::Pause 200ms

::'Now to send out 0x01
::'Send out bit0
::Set K line high (1)
::pause 200ms
::'Send out bit1
::Set K line low (0)
::pause 200ms
::'Send out bit2
::Set K line low (0)
::pause 200ms
::'Send out bit3
::Set K line low (0)
::pause 200ms
::'Send out bit4
::Set K line low (0)
::pause 200ms
::'Send out bit5
::Set K line low (0)
::pause 200ms
::'Send out bit6
::Set K line low (0)
::pause 200ms
::'Send out bit7
::Set K line low (0)
::pause 200ms

::'Send Stopbit
::Set K line high (1)
::Pause 200ms

::Switch to 15625 baud

::Receive C0 55 EF 85
::send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second byte of ECU ID
::Send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second Byte of ECU ID
::Send FD
::Receive 20
::Send FD
::Receive 20
::Send FD
::Receive 20

:The ECU is now initialised and you can start sending requests depending on the info you want back.

:For example if you wanted to know the RPM of the engine.

:Send 21 and it will reply with a answer, then simply do a calculation on that result to get the true answer.

:The calculation for RPM is 31.25*x

:Will sort out a list of know Request ID's and their calculations next.

Followup post:

:I have now been informed that after you do the 5 baud Init and then change Baud rate to Receive C0 55 EF 85, you can start sending request bytes straight away.

==MUT over OBD-II (Hybrid)==

See [http://forums.evolutionm.net/7422846-post11.html acamus' post] about using ELM-style loggers (in his case, a bluetooth logger:

:Here is little how to
:1. Open COM port of BT key, e.g. COM6 via HyperTerminal or write simple application
:2. Set baudrate to 19200
:3. Send ATSP0<CR><LF>
:4. Wait for reply OK - (Bus Init..... OK)
:5. Send A0<MUT ID><CR><LF> e.g. A032
:6. Parse reply E0 <value> e.g. E0 80, so value is 0x80
:7. Use formula to get the scaled value

MUT Protocol

2010-10-25T02:39:11Z

EdwardMarshall: Quick cut-and-paste; will clean up as a proper protocol spec later.

Quoted from http://www.myrollingroad.com/showthread.php?t=60 CLaNZeR@MyRollingRoad]:

:Okay the Mut Protocol Init is alot like the ISO9141-2 Init.

:We will be using 1 of the Pins from the OBD-II Connector for communicating.

:Pin7 K line

:If you take a Pin HIGH this means you are applying 12Volts to it.
:If you take the Pin LOW you are applying 0V

:The first thing that you need to do is to initialise the ECU so it knows you want to communicate.

:This is done with the following routine:

::'Slow Init
::Take K Line High
::Pause 300ms

::'Send 0x01 (00000001) at rate of 5 baud (LSB) with a Start Bit and a Stop bit

::'Send Startbit
::Set K line low (0)
::Pause 200ms

::'Now to send out 0x01
::'Send out bit0
::Set K line high (1)
::pause 200ms
::'Send out bit1
::Set K line low (0)
::pause 200ms
::'Send out bit2
::Set K line low (0)
::pause 200ms
::'Send out bit3
::Set K line low (0)
::pause 200ms
::'Send out bit4
::Set K line low (0)
::pause 200ms
::'Send out bit5
::Set K line low (0)
::pause 200ms
::'Send out bit6
::Set K line low (0)
::pause 200ms
::'Send out bit7
::Set K line low (0)
::pause 200ms

::'Send Stopbit
::Set K line high (1)
::Pause 200ms

::Switch to 15625 baud

::Receive C0 55 EF 85
::send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second byte of ECU ID
::Send FE
::Receive E4 ' First Byte of ECU ID
::Send FF
::Receive B3 ' Second Byte of ECU ID
::Send FD
::Receive 20
::Send FD
::Receive 20
::Send FD
::Receive 20

:The ECU is now initialised and you can start sending requests depending on the info you want back.

:For example if you wanted to know the RPM of the engine.

:Send 21 and it will reply with a answer, then simply do a calculation on that result to get the true answer.

:The calculation for RPM is 31.25*x

:Will sort out a list of know Request ID's and their calculations next.

Followup post:

:I have now been informed that after you do the 5 baud Init and then change Baud rate to Receive C0 55 EF 85, you can start sending request bytes straight away.

ECU Development

2010-10-25T02:26:25Z

EdwardMarshall: /* Communications */

== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]
* [[MUT Protocol]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)

EcuFlash

2010-10-20T20:20:21Z

EdwardMarshall:

[[openecu:EcuFlash|EcuFlash]] is a general-purpose ECU reflashing and editing tool that supports an [[openecu:EcuFlash:VehicleSupport|ever-growing list]] of vehicles. EcuFlash uses the [[openecu:OpenPort|OpenPort]] vehicle interface to reflash vehicles via the [[wikipedia:On_Board_Diagnostics|OBDII]] port. EcuFlash also allows you to edit ECU data (known as 'maps' or 'tables') in a human-readable format using a [[wikipedia:XML|XML-based]] definition system to translate the data. With properly setup definitions, the ROM from any vehicle can be edited.

Release history (from [http://forums.evolutionm.net/ecuflash/472456-collecting-old-versions-ecuflash.html EvoM]):

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_090.zip 0.90], 2005-07-06
** First official release
** Command line supports read / flash / compare
** Supports 2001-2005 WRXs
** [http://evoecu.logic.net/mirror/ecuflash/source_code/sourcepreview.zip Source for this version] was released, as well as for the [http://evoecu.logic.net/mirror/ecuflash/source_code/hc16subaru.rar 0.93 HC16 kernel].

* 0.91, 2005-10-25
** This version has been created to support the new OpenPort 1.2. The OpenPort 1.2 has a 12V reflashing voltage that is controlled by RTS line of the virtual serial port which is off by default. EcuFlash now switches this voltage on at the appropriate times.
** This is intended to be the last command line version of EcuFlash. Future versions under development use a GUI and are supported under Windows / OS-X / linux.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_101.rar 1.01], 2005-11-14
** First GUI version of EcuFlash using the [http://trolltech.com/ Qt Toolkit]
** (We only have the executable, and it might not be the official one at that.)

* 1.21, 2006-04-15
** Add support for drive by wire Subarus (STi,Forrester XT,Legacy GT,Baja,2006+ WRX)
** Switch to 'Mac' styled UI
** Add table view / editing with infinite undo
** Add user definable color maps
** Make 68HC916Y5 (WRX) kernel deal with bad serial data better

* 1.22, 2006-04-16
** Add flipx/flipy to axes widgets
** Change default color map

* 1.23, 2006-04-29
** Fix bug in SH7055 kernel that caused incorrect FMCLR register to be chosen
** Table checkboxes now single click and only hot within checkbox

* 1.24, 2006-04-30
** Fix bug causing crash when ROM images are closed out of order

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup125.exe 1.25], 2006-05-01
** Add user level option to hide obscure tables

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup126.exe 1.26], 2006-05-10
** This is the first version to officially support Mitsubishi vehicles (Evo 7/8,Eclipse,Lancer). Some ROM definitions are included, more will be added later
** Added driver installer to EcuFlash installation
** Installer backs up your current metadata to 'backupXXX'
** Removed option to delete maps until it works
** Added a needed checksum module for DBW Subarus
** Added support for float and double data types in scalings
** Added idle category
** Improved help in scalings editor
** Adaptive cell sizing in tables
** Map windows have ROM file in the title
** Added procedure steps for connecting to Mitsubishis
** Added directory browsing to options

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup127.exe 1.27], 2006-05-15
** Some new maps added to Evos
** Improved programming voltage messages for Subaru
** Fixed bug in tracking open map views when metadata view changed
** Expanded table cell sizing a bit to prevent ellipses

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup128.exe 1.28], 2006-06-20
** Evo 9 reflash support added
** Eclipse AT reflash support added
** Evo 9 map support improved
** Update all Mitsubishi XML definitions to use new reflash tool names
** Improved cell sizing further
** Fix problem of options changing when browsing options menus and canceling
** Add support for hex data entry when editing
** Switch to Qt 4.1.3
** Remove need for C runtime DLLs
** Fix update logic when editing map definitions
** Reset reference ROM data when reading a ROM
** Fix crash on edit of table with no parent

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129.exe 1.29], 2006-09-29
** Added many new Subaru ROM definitions thanks to merchgod of enginuity.org
** Added some Mitsubishi ROM definitions
** Added auto-selection of OpenPort cables
** Added descriptive icons to tables in metadata view
** Fixed bug with tables having 2 generations of parents
** Fixed bug with incorrect XMLID in new ROM wizard
** Added ability to load a ROM file from the command line
** Improved color scaling handling
** Changed table to show only units for main data
** Improved table layout
** Added help text to tables
** Fix metadata ordering to match XML file order
** Add support for bloblist data type which enables DTCs

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup129a.exe 1.29a], 2006-10-03
** fixed bug in install preventing driver installer from running

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_setup130.exe 1.30], 2007-03-09
** added OpenPort drivers for Amd64 processors
** simplified kernels to support both register-based and flash-routine versions of the SH7055
** moved to Qt 4.2.2
** prepare code for linux / OSX versions
** some new XML definitions / fixes
** (First release with an obscured executable. [http://forums.nasioc.com/forums/showthread.php?p=14207760#post14207760 Change of heart] from [http://forums.nasioc.com/forums/showthread.php?p=14204135#post14204135 a few months prior], yet "About" text still asks for donations. Nice.)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_131_win.exe 1.31], 2007-08-24
** added Mac OSX (intel) support! - still some minor Qt issues on the mac...
** moved to Q 4.3.0
** 2D and 3D graphing features working
** task pane is hideable and has resizing splitter
** significant improvements to the Subaru ECU defintions thanks to merchgod
** add better visibility options for invalid or higher user level tables
** faster on-demand XML parsing
** add relative directory support in the options
** read only support for H8/539 based mitsubishis - flashing disabled due to lockout problem
** switch to true kwp2000 protocol stack for Subarus
** fix endian reversal in metadata parser - old metadata files are no longer compatible!
** add shbootmode for SH705x processor recovery
** fix asymmetry error in substeps for undo and redo. undo now does steps in exact reverse order, in case two or more substeps operate on the same data (as happens in a 2D interpolation)
** fix crash on editing of static values
** automatically detect and warn if Subarus are not in the test mode when flashing

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_132_win.exe 1.32]2007-09-06
** removed test mode detection for 2005+ DBW Subarus because some models do not have a test mode connector

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_133_win.exe 1.33], 2007-10-01
** Subaru metatdata updated to version 0.79b
** removed test mode detection altogether as it causes problems on many ECUs
** fix to HC16 kernel to allow bootloader communications to complete before starting kernel
** fix bug causing extra data to be sent when loading some kernels
** improve KWP2000 resynchronization

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_134_win.exe 1.34], 2007-11-05
** fixed crash which occurred when using older OpenPort 1.2 cables
** added automatic notification when new version is released

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_135_win.exe 1.35], 2007-05-15
** this is a minor update to support some recent cable changes - a major release is coming soon!
** FTDI drivers updated to CDM 2.02.06
** Qt updated to 4.4.0
** Qwt updated to 5.1.0
** bitfields now supported in bloblists ("blobbits", ie. for periphery bit editing)
** Subaru definitions update to merchgod's 0.8 release

* 1.36

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_137_win.exe 1.37], 2008-09-05
** the main features of this release is support for Subaru CAN vehicles and the J2534 OpenPort 2.0 cable
** this release has no Subaru CAN definitions in it yet - those will be supplied in a few weeks once we collect all of the new ROMS.
** some mitsubishi definitions have been updated (thanks mychailo!)
** J2534 OpenPort 2.0 applications supported with new op20pt32.dll
** op20pt32.dll automatically updates OpenPort 2.0 firmware when needed
** test mode connection no longer needed with newer Subaru ISO and CAN vehicles when using OpenPort 2.0
** fix bug with unknown ROMs not carrying memory model through wizard
** fix bug with loading inherited XML when the rommetadata path is a relative one
** make shbootmode less picky about receiving ACK responses

* 1.38: [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_win.exe Windows] [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_138_osx.dmg MacOS]

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1392152_win.exe 1.39.2152]

* 1.40.2173, 2007-10-21 (??)

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1402178_win.exe 1.40.2178], 2007-10-??
** this release fixes a bug in op20pt32.dll which can allow older firmware to be used if the firmware update fails. using older firmware can lead to flashing failures

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1412483_win.exe 1.41.2483], 2009-01-29
** EcuFlash Related Changes
*** add support for EVO X CAN reflash
*** add DTC clear option for Evo X
*** add flash recovery mode option and flash recovery mode for Evo X
*** H8 support for 1.3 cables removed.

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1422595_win.exe 1.42.2595], 2009-06-27
** EcuFlash Related Changes
*** support for flashing H8/539FA processor (e.g. Evo 6.5) via new H8539FA memory model
*** add many generic memory models to allow support for arbitrary ROMs from ECUs that EcuFlash has no flashing support for. these are named Generic1K, Generic2K, ... up to Generic2048K, including all powers of 2, plus many other common sizes.
*** fix programming voltage warning errors in Subaru HC16 kernels
*** actively pull up OBD pin 9 when communicating with HC16 Subarus to avoid reflash mode initialization problems on some EDM models
*** add some retries to kernel reads, instead of failing
*** allow unique ID data in Subaru CAN ROM protected area to be different without requiring this area to be reflashed (which is not allowed). this allows ROMs of the same version to be shared amongst users without refusal-to-flash errors.
*** fixed error that limited data type to 4 bytes in size (doubles and bloblists can be bigger)
*** fixed bug in Subaru K-line reflashing that did not initialize the parity mode of the vehicle interface, causing errors if the interface had previously been used with odd or even parity
** J2534 DLL Related Changes
*** (no changes other than new firmware payload)
** Firmware Related Changes
*** fix bug which can cause CAN receive buffer overruns during large ISO15765 transfers
*** fix bug where resting voltage of adjustable power supply can be low enough to trigger undervoltage protection of voltage multiplexer IC
*** increase maximum allowable ISO9141 baud rate to be 125000 baud

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1432990_win_beta.exe 1.43.2990] (beta), 2010-03-26

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433000_win_beta.exe 1.43.3000] (beta), 2010-03-31

* [http://evoecu.logic.net/mirror/ecuflash/releases/ecuflash_1433150_win_beta.exe 1.43.3150] (beta), 2010-09-03

EcuFlash

2010-10-20T19:59:27Z

EdwardMarshall:

EcuFlash

2010-10-20T19:27:50Z

EdwardMarshall:

EcuFlash

2010-10-20T19:22:24Z

EdwardMarshall:

EcuFlash

2010-09-16T16:14:24Z

EdwardMarshall:

Help:Contents

2010-08-23T02:13:25Z

EdwardMarshall: Reverted edits by Jsmith (talk) to last revision by EdwardMarshall

{{PD Help Page}}
==Reading==
* [[Help:Navigation|Navigation]]
* [[Help:Searching|Searching]]
* [[Help:Tracking changes|Tracking changes]]
* [[Help:Watchlist|Watchlist]]

==Editing==
* [[Help:Editing pages|Editing pages]]
* [[Help:Starting a new page|Starting a new page]]
* [[Help:Formatting|Formatting]]
* [[Help:Links|Links]]
* [[Help:User page|User pages]]
* [[Help:Talk pages|Talk pages]]

===Advanced editing===
* [[Help:Images|Images]]
* [[Help:Tables|Tables]]
* [[Help:Categories|Categories]]
* [[Help:Subpages|Subpages]]
* [[Help:Managing files|Managing files]]
* [[Help:Moving a page|Moving a page]]
* [[Help:Redirects|Redirects]]
* [[Help:Deleting a page|Deleting a page]]
* [[Help:Protected pages|Protected pages]]

* [[Help:Templates|Templates]]
* [[Help:Variables|Variables]]
* [[Help:Namespaces|Namespaces]]

* [[Help:Special pages|Special pages]]
* [[Help:External searches|External searches]]

===Personal customization===
* [[Help:Preferences|Preferences]]
* [[Help:Skins|Skins]]

==Wiki administration==

* [[Help:Sysops and permissions|Sysops and permissions]]

The following features require extra permissions that are not normally granted to all wiki users.

* [[Help:Protecting and unprotecting pages|Protecting and unprotecting pages]]
* [[Help:Sysop deleting and undeleting|Sysop deleting and undeleting]]
* [[Help:Patrolled edits|Patrolled edits]]
* [[Help:Blocking users|Blocking users]]
* [[Help:Range blocks|Range IP blocks]]
* [[Help:Assigning permissions|Assigning permissions]]

{{Languages|Help:Contents}}
[[Category:Help| ]]
__NOTOC__

MediaWiki:Common.css

2010-06-28T17:45:21Z

EdwardMarshall: Created page with '/* Pad Google AdSense box in portlet in sidebar */ #p-googleadsense .pBody { padding-top: 5px; text-align: center; }'

/* Pad Google AdSense box in portlet in sidebar */
#p-googleadsense .pBody {
padding-top: 5px;
text-align: center;
}

Main Page

2010-05-04T02:50:39Z

EdwardMarshall:

EvoScan

2010-05-04T02:45:37Z

EdwardMarshall: Cleaned out marketing stuff. Seriously?

<br>[http://www.evoscan.com/ EvoScan] is a program created by [http://forums.evolutionm.net/member.php?find=lastposter&t=361521 Evo4Mad (Hamish)]. The program connects to the ECU via an OpenPort 1.3U or OpenPort 2.0 USB Cable [[Logging Cable]]. EvoScan allows you to log ECU data and also has the ability to connect to and log from a [[Wide Band Air Fuel Meter]].

=== Problems with the Map Tracer Feature ===

''' Logged Items '''

Unfortunately EvoScan bases this chart off of ECULoad (or LoadCalc, in some cases) and standard RPM. If you are using the 1 byte load mod or 2 byte RPM you can run into issues.

''' Incorrect XML Definitions '''

You can also run into issues if your XMLs are incorrectly defined in the Evoscan XML directory. It is often easiest to simply remove all unnecessary tables from the EvoScan definition files to ensure that you will not run into any snags. You can also add Alt-map tables (which are not included by default) and/or Big-Map tables for newer versions of the [[TephraMod]].

''' How to: For problematic map tracers or BigMap tracing '''

EvoM user [http://forums.evolutionm.net/members/55720-fostytou.html Fostytou] details this method in a thread [http://forums.evolutionm.net/7078367-post16.html here] and [http://forums.evolutionm.net/7078461-post18.html here] and further down.

Essentially [http://forums.evolutionm.net/7447843-post15.html all you are going to do] is make sure everything is properly defined for your rom, and as minimalistically as possible.

:* 1) Get loadCalc values in your log. The first time I did this I copied the load1byte column to to a column with "LoadCalc" in the header in the EvoScan XML (be sure to delete the old "LoadCalc" column.) (You can also just make a copy of the log and rename the load1byte or do as others have suggested and rename it in evoscan). This is silly because it allows you to then select which column you want to use for load. I assume if you log loadcalc or forced evoscan to populate it with 0 in each entry you would then be able to just select the correct load column.
:** More progress... Unfortunately you can't just have evoscan write a first and last entry of 0 with calc/priority 100. No matter what is selected in the drop down tracer is looking for loadcalc. You have 2 options:
:** 1) Rename the logged item for load1byte to "loadcalc" (less data, but could be confusing in the future)
:** 2) Replace your loadcalc and 1ByteLoad evoscan entry with these 2. Log the DEAD version. This should not really have an impact on performance, just create a very slightly larger log.
{|border="1" cellspacing="0"
|<nowiki><DataListItem DataLog="N" Color="" Display="Load Calculated REAL" LogReference="LoadCalcXXX" RequestID="29" Eval="5*[InjectorScaling]*((0.256*x)-(-0.1026*[Battery]+1.8741))/(14.7*128/[AFRMAP])" Unit="Load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="This is just an extended calculation to forumulate the real Load value beyond that shown in ECULoad. A more accurate method is to reflash your ecu with a ROM mod that allows you to log 2Byte Load.

Dont forget to update the InjectorScaling on the Main Form, with your injector scaling value used for your rom.

5*InjScaling*([InjPulseWidth]-(-0.1026*[Battery]+1.8741))/[AFRMAP]" Priority="1" Visible="False" /></nowiki>
|-
|<nowiki> <DataListItem DataLog="N" Color="" Display="Load Calculated DEAD" LogReference="LoadCalc" RequestID="CALC" Eval="[Load1B]" Unit="Load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" Notes="Fake Load to get map tracer to work." Priority="1" Visible="False" /></nowiki>
|}
<br>
:* 2) Modify an XML to have no includes, just all of the scalings from the base file and the fuel and timing tables. EG:
{|border="1" cellspacing="0"
|<nowiki> <table name="High Octane Fuel Map - ALT" category="Fuel" address="49b4d" type="3D" swapxy="true" scaling="AFR"></nowiki>
|-
|<nowiki> <table name="Engine Load" address="6ec8" type="X Axis" elements="20" scaling="Load"/></nowiki>
|-
|<nowiki> <table name="RPM" address="6ea0" type="Y Axis" elements="15" scaling="RPM"/></nowiki>
|-
|<nowiki> </table></nowiki>
|-
|<nowiki> <table name="High Octane Ignition Map 1 - ALT" category="Timing" address="49c8d" type="3D" swapxy="true" scaling="Timing"></nowiki>
|-
|<nowiki> <table name="Engine Load" address="6f2c" type="X Axis" elements="21" scaling="Load"/></nowiki>
|-
|<nowiki> <table name="RPM" address="6efa" type="Y Axis" elements="20" scaling="RPM"/></nowiki>
|-
|<nowiki> </table></nowiki>
|-
|<nowiki> <table name="High Octane Fuel Map" category="Fuel" address="2dbd" type="3D" swapxy="true" scaling="AFR"></nowiki>
|-
|<nowiki> <table name="Engine Load" address="6ec8" type="X Axis" elements="20" scaling="Load"/></nowiki>
|-
|<nowiki> <table name="RPM" address="6ea0" type="Y Axis" elements="15" scaling="RPM"/></nowiki>
|-
|<nowiki> </table></nowiki>
|-
|<nowiki> <table name="High Octane Ignition Map 1" category="Timing" address="33e9" type="3D" swapxy="true" scaling="Timing"></nowiki>
|-
|<nowiki> <table name="Engine Load" address="6f2c" type="X Axis" scaling="Load" elements="21"/></nowiki>
|-
|<nowiki> <table name="RPM" address="6efa" type="Y Axis" scaling="RPM" elements="20"/></nowiki>
|-
|<nowiki> </table></nowiki>
|}
:** An 88590715 example file is [[File:EVOSCAN_TephraMOD-88590715_ALT.zip]] . These files go in your C:\Program Files\EvoScan\EvoScan v2.6\ROMS directory
<br>
:* 3) Open EvoScan MAP Tracer and pick your log file.
:* 4) Right-click on the bottom and click "Load HEX and XML files."
:** The first file you load is the ROM XML file you copied from ECUFlash. This would be the 88590715.xml file that you just made, and if it works properly it should load automatically from now on when you select your ROM.
:** The second file is your actual .hex/.bin ECUFlash flash file (your current tune or the one you were using when the log file was created). If you don't have one, you will have to use ECUFlash to connect to your ECU and download whatever tune you currently have.
:* 5) Now everything should be loaded and you can click on the parameters on the left to view them.

Logging Cable

2010-05-04T02:43:11Z

EdwardMarshall:

There are a few cables that can be used to log and reflash data on Mitsubish ECUs:

* OpenPort 1.0 (no longer available)

* OpenPort 1.2 (no longer available)

* OpenPort 1.3M (no longer available)

* OpenPort 1.3D (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables]
** Datalogging only; no flashing support at all (needed physical wiring is not present). Low-cost logging option.

* OpenPort 1.3R (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables]
** Physically identical to OpenPort 1.3U, but without a license for use with EcuFlash; only Evo 7/8 vehicles can be flashed with this cable, using EvoScan. Lower-cost than 1.3U.

* OpenPort 1.3U (only available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables])
** Full-featured flashing/datalogging cable. Works with most loggers, as well as EcuFlash.

* OpenPort 2.0 (available from [http://www.limitless.co.nz/cables www.limitless.co.nz/cables] or [http://www.tactrix.com tactrix.com])
** Newest version of full-featured cable; is now a device which supports CAN-bus vehicles such as the Evo X. Requires newer version of EcuFlash, and some loggers have not added support for it yet (EvoScan works).

There have been quite a few additional cables produced over the years that EvoScan supports, but typically only Tactrix-licensed cables will operate with EcuFlash.

See [[ECU Development]] for schematics for the OpenPort 1.0, 1.2, and 1.3U cables, as well as pinouts for the Evo ECUs, OBD-II, and diag plugs, and other useful electronics information.

How to Tune an Evo TB Alternate

2010-05-04T02:32:44Z

EdwardMarshall: /* What you need to modify */

Original Thread by Touring Bubble:  [forum now closed - original posting date04-30-2007]<br>http://www.evolutionse.com/forums/showthread.php?t=3014<br><br>Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&hl=en&ct=clnk&cd=9&gl=us&client=firefox-a Here]
<br>
Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[[EcuFlash]]- Yes, let's assume you need the tuning software to tune your ECU. This software is a free download.

===Logging Software===
[[EvoScan]]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.

''(As of 8/15/08, LogWorks 3 does not include the OpenPort plugin needed to support the OpenPort cable used for logging an Evo. You must install a version of LogWorks 2 that includes this plugin.)''

Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[[Logging Cable]] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors. This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they only give accurate feedback at [http://en.wikipedia.org/wiki/Air-fuel_ratio stoich] (1 Lambda (λ), or 14.7:1 AFR for gasoline). This is because the ECU only uses data from these sensors in "closed loop" mode.

'''Closed loop''' means that the ECU references a signal from a sensor and compares it to a target value in the ROM, and can then make adjustments to values on-the-fly to reach that target. The stock ECU uses closed loop fueling at low load levels (idle, cruise) and the AFR target is 14.7:1, or 0.5v on the front O2 sensor. Stock boost control is also closed loop ... the ECU targets a specific load level for a given RPM and can adjust the duty cycle of the boost control solenoid for correction. More on that later.

There are crossover points defined (based on RPM, load and TPS voltage) that tell the ECU when to stop using closed loop fueling and switch to "open loop." '''Open loop''' occurs when the vehicle stops relying on sensors to give feedback and simply "trusts" the defined maps to be correct. In the case of AFR, the ECU used the data in the fuel maps and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing an extra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher voltage range of the sensor and it's linear response allows for more accurate readings.

Here are some choices for a [[Wide Band Air Fuel Meter]]

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately record boost levels with your logs. This should give the same readings as your mechanical boost gauge, but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get some info in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning! [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most up-to-date Evo IX ROM. For info on the most up-to-date, supported ROMs, check the [[Downloads|downloads page]].

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit, and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store misc. tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 reference values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustration below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the fuel value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not.

===ECU-Based Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route as you can use the stock boost control solenoid.

With this method you retain the ECU's closed loop control of the turbo system which allows for some options you can't get from most manual/electronic boost controllers. Mrfred has really gotten dirty with this functionality in the ROM and has found different ways of controlling the boost level with the stock ECU. Read about those discoveries here and here (EvoM currently down).

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

This method works with the modified stock boost control solenoid or other aftermarket 3-port boost control solenoids.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. The "Boost Limit" and "Boost Delay Timer" tables still function with a manual or electronic boost controller, so you'll need to adjust them as noted below.

===Controlling boost with the ECU===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&postcount=7 this post] if you want to learn more.

If you plan to use the stock BCS, read [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control]. You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

If you are using an aftermarket 3-port BCS you will remove the stock lines and the stock restrictor pills during the install. They are not needed for a 3-port solenoid setup.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu.

{{warning|Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.}}

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

====Boost Delay Timer====
[[Image:boostDelayTimerMap.gif]]
This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the ECU will cut fuel to protect the engine.

====Boost Control Load Offset====
[[Image:boostOffsetMap.gif]]
This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM. If using Mrfred's PSI-based boost control, this table is not used. You will add another table with scaling in PSI. The new table will function the same as this one.

====Turbo Boost Error Correction====
[[Image:boostErrorMap.gif]]
This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -> desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load. Again, when using PSI-based boost control you will create another error correction table with PSI scaling.

====BoostDesired Engine Load====
[[Image:boostDesiredMap.gif]]
The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control. For PSI-based boost control, you will create another set of these tables with PSI scaling.

====Max Wastegate Duty====
[[Image:maxWGDCMap.gif]]
This map, also referred to as "Baseline Wastegate Duty," determines the initial duty cycle values of the BCS. If the actual load/PSI is not equal to the desired values in the desired boost table, the error correction values kick in and make adjustments based on the values here.

====Boost Limit====
[[Image:boostLimitMap.gif]]
This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill/3-port solenoid installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

{{warning|Do not drive the car with the modified boost pill/3-port solenoid before flashing the ECU with your new boost settings!}}

====Boost Delay Timer====
This map can stay where it is,but you can increase it if you feel the need.

====Boost Control Load Offset====
Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

====Turbo Boost Error Correction====
You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

====Boost Desired Engine Load====
There are 3 of these maps, and sadly, I have no idea why. So, the easiest way to proceed is to modify all 3 of the maps. This will ensure that you have the desired boost settings in any sutuation.

Set the BDEL in all 3 maps to "140" with a taper down to "100" from 5500 RPM to 7000 RPM. This value added to the load offset value of "100" gives you a desired load of "240" through most of the rev band, which is equal to about 22 psi in most cases. We're tapering down the top end to reduce heat and the chance of knock.

====Max Wastegate Duty====
Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.

Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

====Boost Limit====
Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

====Min Temp for Full Boost Control====
This table is incorrectly defined, so leave it alone. Stock value is "85."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable if it isn't consistent. Knock counts higher than 3 (actually, 1 on a IX) begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location or by increasing the octane of your fuel. If the knock occurs in additional logs in the same RPM/load area even with higher octane fuel, then it is real knock and you need to adjust your maps to compensate. Phantom knock is very rare on lightly modified vehicles and should not be assumed without proper validation.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels which (for the most part) are parallel to your boost levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3 and boost is conservative, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at -2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for low load, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, the less stable it is under pressure and therefore more likely to burn in an unstable manner causing detonation or pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

'''The values in the fuel map are not actual AFR values.''' They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This affects your tuning by throwing off the values even in the fuel map even more and causing shifts in AFR between gears. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should show an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12s up to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and '''make small, gradual changes'''. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways, such as more boost, a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute timing advance number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the burning fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://en.wikipedia.org/wiki/Dynamometer dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of flat road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car and close the gap by .004 every 50 hp. This means increased boost, an open filter and exhaust on an average Evo could call for a colder plug.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&AAIA=1432585 here is a list of plugs that will work].

The Evo IX comes with a colder plug than the VIII so basic mods on the IX don't require a plug change. The standard, colder replacement plugs for the VIII are the BR7ES (1/2 step colder) and BPR8ES (1 step colder).

For more info on plugs, [http://sevo.motionforum.net/engine-turbo-f10/spark-plugs-t116.htm check here].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===

How to Tune an Evo TB Alternate

2010-05-04T02:32:26Z

EdwardMarshall: /* Boost control tables */

Original Thread by Touring Bubble:  [forum now closed - original posting date04-30-2007]<br>http://www.evolutionse.com/forums/showthread.php?t=3014<br><br>Google Cache Version: [http://64.233.167.104/search?q=cache:ekGVXrROeoAJ:www.evolutionse.com/forums/showthread.php%3Ft%3D3014+%22boost+desired+engine+load%22&hl=en&ct=clnk&cd=9&gl=us&client=firefox-a Here]
<br>
Note: Sections are broken up by original post-style

== TB's guide to tuning with ECUFlash ==
From start to finish. [[Image:smilie_thumbsup.gif]]

===Introduction===
The goal of this guide is simple: To provide you with the knowledge and techniques needed to tune your Evo using ECUFlash. I'm going to go through the entire process of tuning the ECU, and hopefully give you the knowledge to make your fast car go faster.

===Disclaimer===
I researched, tested, and compared tons of data before making adjustments to my car for the same reason that you should ... so you don't blow up your $30,000+ investment. You can trust that the data provided in this guide will be pretty darn accurate, but you should understand the risk you assume by modifying the values in your ECU. If you break anything because of this guide, '''it is not my fault'''... though I will feel kinda bad.

With that said, let's get started ...

===First things first===
Since you obviously want to know more about tuning your car, you should go ahead and read through [http://forums.evolutionm.net/showthread.php?t=201146 this brief tutorial] on EvoM written by EFIxMR. It quickly touches on some of the subjects that will be covered here.

If you read that article and are still awake, then you will probably be able to follow the rest of the tutorial here. I might get pretty technical at times, but if you have any questions, just post them here and I'll do what I can to get them answered.

== What you'll need ==
Before you get started, you'll need a few basics. Some of these necessities are going to lighten your pocket a little, but you drive an Evo ... you can afford it, right?

===Tuning Software===
[[EcuFlash]]- Yes, let's assume you need the tuning software to tune your ECU. This software is a free download.

===Logging Software===
[[EvoScan]]- This application is available for download for $25 and is the software I'll be using to log in this tutorial. For your hard earned$25, you'll get the logging software and free updates. EvoScan is simple and easy to use. It also works with most of the wideband O2sensors you'll find.

[http://www.aktivematrix.com/forum/portal.php MitsuLogger]- Mitsulogger is a free logging software developed (mostly) by MalibuJack, who you might know from EvoM. He knows his stuff, and his logger reflects that. It's powerful and constantly being updated. If you have questions about this logger, I probably can't help you ...but, I'm sure MJ would be happy to help you out. You can find him on his own site, [http://www.aktivematrix.com/forum/portal.php The Aktive Matrix], or on EvoM in the [http://forums.evolutionm.net/forumdisplay.php?f=179 ECUFlash tuning forum].

[http://www.innovatemotorsports.com/support.php LogWorks]- LogWorks is a super powerful logging application developed by Innovate Motorsports and is packaged with many of their products. I have this software, but I honestly haven't used it much. I hear that it's a smart, fast logger that can do anything you want and more after you learn how to use it. Lots of tuners love this software and wouldn't trade it for the world.

''(As of 8/15/08, LogWorks 3 does not include the OpenPort plugin needed to support the OpenPort cable used for logging an Evo. You must install a version of LogWorks 2 that includes this plugin.)''

Of course, these aren't the only choices for logging data from your ECU. Find a logger you like and learn your way around it. You can use the information here with any logger you end up with.

And now, the hardware ...

===OBDII Interface Cable===
[[Logging Cable]] -This is the interface that connects your computer to your car. This cable is used when data is being sent to or being pulled from the ECU.

===Boost Gauge===
You need to monitor the boost carefully when tuning your car. A boost gauge is the absolute minimum you need. A better solution is to log boost with an added MAP sensor which will be discussed a little later.That said, I'm currently tuning using only the stock boost gauge that Mitsubishi left in the car for me.

Boost gauges are everywhere and range for super cheap to insanely expensive. Pick one and install it. If you want my opinion, I've had VDO and Stewart Warner gauges and never had trouble with either.

===Wideband (5v) O2 Sensor and Interface===
I'll give a little explanation here. You have 2 O2 (oxygen) sensors on your car from the factory. One is in the turbo outlet pipe, and the other is just past the catalytic converter. The first one tells the ECU information about the fuel mixture, and the second is used in comparison to the first to determine if the converter is doing its job.

Both of these stock sensors are what we call "narrow band" sensors. This means that they send signals from 0.00v to 1.00v. This technically isn't a problem and narrow band O2 sensors can be used to monitor air/fuel mixtures when tuning, but the stock sensors are calibrated in such a way that they only give accurate feedback at [http://en.wikipedia.org/wiki/Air-fuel_ratio stoich] (1 Lambda (λ), or 14.7:1 AFR for gasoline). This is because the ECU only uses data from these sensors in "closed loop" mode.

'''Closed loop''' means that the ECU references a signal from a sensor and compares it to a target value in the ROM, and can then make adjustments to values on-the-fly to reach that target. The stock ECU uses closed loop fueling at low load levels (idle, cruise) and the AFR target is 14.7:1, or 0.5v on the front O2 sensor. Stock boost control is also closed loop ... the ECU targets a specific load level for a given RPM and can adjust the duty cycle of the boost control solenoid for correction. More on that later.

There are crossover points defined (based on RPM, load and TPS voltage) that tell the ECU when to stop using closed loop fueling and switch to "open loop." '''Open loop''' occurs when the vehicle stops relying on sensors to give feedback and simply "trusts" the defined maps to be correct. In the case of AFR, the ECU used the data in the fuel maps and just kind of assumes that that mixture is correct based on the things it DOES know, such as the MAF reading.

So, in order to achieve the ideal fuel mixture, we need to know the specifics of the fuel mixture when in open loop mode, especially since open loop occurs during acceleration. We get this data by installing an extra O2 sensor that can interface with a gauge or computer. This is usually a "wideband" sensor that sends signals from 0.00v to 5.00v. The higher voltage range of the sensor and it's linear response allows for more accurate readings.

Here are some choices for a [[Wide Band Air Fuel Meter]]

===Optional Hardware===
Items listed here aren't required to properly tune your car, but a little extra info never hurt anyone.

MAP Sensor and Interface - Adding a MAP (Manifold Absolute Pressure)sensor will allow you to accurately record boost levels with your logs. This should give the same readings as your mechanical boost gauge, but logging the values allows you to compare your boost levels with the rest of your log and could possibly allow you to catch subtle pressure nuances that you might not spot on the gauge.

On the Evo, there is a nifty way to log boost with a part from Japan and some minor modification to your ECU. Read about that [http://forums.evolutionm.net/showthread.php?t=259595 here]. There are also many aftermarket kits that allow you to log boost.

EGT Gauge - I've personally never dealt with one of these doo-dads, but monitoring your EGT (Exhaust Gas Temperature) can keep you from making some big mistakes while tuning. If you want to go this route, you'll need to do a little research because I can't help much. If you get some info in it, post here and I'll add it. [[Image:beer.gif]]

So, you've got all of the necessities. Let's start tuning! [[Image:headbang2.gif]]

== AAAHHHH! Lots of colors and numbers! ==
Alrighty, so you now have everything you need to get started. Let's get you familiarized with the software you'll be working with.

===ECUFlash===
ECUFlash is the application that you will use to write to and from your ECU. It comes packaged with everything you need to get started, minus a ROM image from your car.

If you have your OBDII cable nearby, you can run out to your car and pull the image from it to use for this section. If you don't have a cable yet, just right-click and save [http://www.frameleft.com/ecuflashTutorial/IX_STOCK_ROM.hex this file] and skip down past this part.

You know how to connect the OBDII cable to your car right? RIGHT? What do you mean you didn't read the article I sent you to above? Okay, fine! [http://forums.evolutionm.net/showthread.php?t=201146 Here is is again].

So, you're plugged in a ready to go, right? Good. Open up ECUFlash. you'll be greeted with this screen ...

[[Image:screen01.gif]]

Now, take a second to get familiar with the buttons at the top of thescreen ...

[[Image:ecuFlashButtons.gif]]

;Open ROM
:This will open a saved ROM image for editing or flashing.
;Save ROM As
:This saves the edits you've made to the ROM.
;Read From ECU
:This connects to the car's ECU and opens the currentimage from the ECU in ECUFlash.
;Write to ECU
:This writes the selected ROM file in ECUFlash to the ECU.
;Test Write to ECU
:The goes through the same processes as the "Write to ECU" function, but no data is actually written to the ECU.
;Compare to ECU
:This reads the image from the ECU and compares it to the selected ROM image in ECUFlash. This process runs every time you write to the ECU, and only the modified ROM data is written to the ECU.

If you're connected to the ECU properly, the "Read from ECU" icon will be lit. Go ahead and click the "Read from ECU" icon. You'll get this prompt ...

[[Image:screen02.gif]]

Select the vehicle that you are connected to and click "Read" to begin transferring your current ROM image to your computer. When the process has finished, your screen should look similar to this ...

[[Image:screen03.gif]]

On the left side, you'll see "read image*" in the top box (BTW, that'*' means that the file has not been saved) and "ROM info" and "Parameters" in the lower box. This would also be a good time to save this ROM somewhere safe before you go poking around and changing stuff. Just click the "Save ROM As" button at the top and select a location.

(Those of you who used the ROM I linked to from above can tune back in now)

Before you start tuning, it's best that you know a little about the information contained in your ROM image, so I'll start there ...

The '''ROM Info''' section contains, well, info about the ROM you're looking at. If you expand that section by clicking the little [+] to the left, you should see info that reflects the vehicle it was pulled from ...

[[Image:screen04.gif]]

Most of the info here is self explanatory, but note the value of "Internal ID." This internal ID is often referred to as the "definition file." In the ROM pictured above, the definition is "88590015" and happens to be the most up-to-date Evo IX ROM. For info on the most up-to-date, supported ROMs, check the [[Downloads|downloads page]].

Now, below the ROM Info section is the good stuff ... the '''Parameters'''. These Parameters hold the data that controls the variables you will harness to fine tune the performance of your Evo. The categories within are pretty cut and dry. They include:

;Fuel
:The fuel category includes the ever important fuel maps,as well as more advanced info such as the MAF and injector scaling tables.
;Timing
:The timing category hold your ignition and MIVEC maps.
;Limits
:Within the limits category you'll find the rev limit, stationary rev limit, and speed limit tables.
;Turbo
:The turbo category holds a ton of important info. The tables here control the desired boost, wastegate duty, and overboost protection. This is probably the most confusing section of them all.
;Misc
:The most important data here is the immobilizer table. You'll need to set your user level to "Developer" to see this though. This category is also commonly used to store misc. tables you add to the ROM definition (we'll cover this later).
;Idle
:These isn't much here, but the tables within control your desired idle settings.

With that out of the way, we can start looking at maps. Yay!

There are 3 levels of maps in ECUFlash ...

;1D
:A 1D map contains one address and a value for that address.
;2D
:A 2D map contains a reference column of addresses and values for each address in a second column.
;3D
:A 3D map cross references 2 address and assigns a value based on their relation.

Here are some examples of the different types of maps ...

1D: [[Image:revLimitMap.gif]]

2D: [[Image:boostErrorMap.gif]]

3D: [[Image:fuelMap.gif]]

3D maps can also be viewed as 3D graphs, like this one ...

[[Image:3dMap.gif]]

Reading the 1D and 2D maps is pretty straight forward, but the 3D map is a little more difficult. Basically, the ECU compares the 2 reference values on the X and Y axis then assigns the corresponding Z axis value. Take a look at the illustration below for more clarity ...

[[Image:3dTableExplained.jpg]]

In the fuel map illustration above, the ECU is reading an engine load value of "180" and an RPM value of "5500." The cell where the 180 load column and 5500 RPM row intersect decides the fuel value, which is"10.1."

Now that you know how to read the maps, you need to know how to modify them. It is actually pretty straight forward and simple ...

"=" pops up a dialog box and allows you to directly input a value in to the selected cell(s).

"+" incrementally increases the selected value(s).

"-" incrementally decreases the selected value(s).

You can also copy and paste values to and from the maps using the standard Windows CTRL+C to copy and CTRL+V to paste. If you want to know more, check out the "Edit" menu in an open map window.

Okay, well that about sums it up for the basics of using ECU flash. Now it's time to find out what values we need to change and why ...

== Pressure predicament ==
When I first started the tune for my car, I chose to begin with setting the boost. The reason for this was to hopefully reduce the amount of tuning needed later in the process.

By first setting the amount of air being shoved on to the cylinders, I could finish the first half of the AFR tuning without even touching the fuel maps. More importantly, the boost tables are directly related to the load values that the ECU uses as a basis reading values from most all of the tables that you will be editing while building your tune. By setting the boost first, you dial in the load values that you will be editing in the steps afterward.

===Ways to tune boost pressure===
There are basically two ways to set the boost levels on your Evo. You can install a boost controller, or modify the factory boost control system. Both have their pros and cons ...

===Aftermarket BoostController===
The main benefit of the boost controller option is ease of use. This option gives you direct, mechanical (or electronic) control of the boost level. Some options allow you to adjust the boost on-the-fly from the driver's seat, and that type of control is insanely convenient.

The downside of this option is mainly the amount of control you have over the boost levels. Some of the more expensive electronic controllers allow you to customize the boost curve based on RPM, but your basic manual controller does not.

===ECU-Based Boost Control System===
With this option, you have tons of control over the boost dynamics. You can dial out spikes and reduce taper. The method also retains the ECU's ability to reduce boost pressure in situations that might harm your engine. There is also a cost savings with this route as you can use the stock boost control solenoid.

With this method you retain the ECU's closed loop control of the turbo system which allows for some options you can't get from most manual/electronic boost controllers. Mrfred has really gotten dirty with this functionality in the ROM and has found different ways of controlling the boost level with the stock ECU. Read about those discoveries here and here (EvoM currently down).

Modifying the stock boost control system is also a little tedious and time consuming. There are many tables that interact with each other to make it all work, and when you start tinkering with the hardware that these values control, they can begin to act a little strangely. Also,to modify your boost setting with this option, you must re-flash the ECU which requires some time and a computer.

This method works with the modified stock boost control solenoid or other aftermarket 3-port boost control solenoids.

===Controlling boost with an aftermarket boost controller===
This is by far the easiest and fastest method to set the boost on your Evo. You simply remove the stock boost control system and replace it with an easy-to-adjust valve. Sung has already written [http://www.evolutionse.com/forums/showthread.php?t=2413 a great tutorial on installing a boost controller], so I'll just send you there in stead of wasting time reiterating it all.

Once you have your boost controller installed, be sure to adjust it all the way down to avoid initial overboosting. Make some runs, preferably in 4th gear, and monitor the boost levels. Turn the boost up in small increments until you reach your desired boost level. Read the logging section further down for more info.

A stock Evo IX can easily handle 22 psi after the needle settles. A spike of 24 or 25 psi can be expected in the peak torque area. The boost is likely to taper down toward redline, but it should still be an improvement over stock.

If you have chosen to install a manual boost controller, you've basically rendered the ECU's boost control features useless, but there are a few tables you might want to change anyway. The "Boost Limit" and "Boost Delay Timer" tables still function with a manual or electronic boost controller, so you'll need to adjust them as noted below.

===Controlling boost with the ECU===
Grab a seat, because things are about to get interesting ...

For starters, controlling boost using the factory boost control system isn't 100% dependent on settings in the ECU. This is due to Mitsu installing handy restrictor pills in the OE boost control solenoid (BCS) lines. There is one pill just before the BCS on the pressure side and one in the short line just before the turbo. Modifying either of these pills will change the boost characteristics. Wrcwannabe gives some great info about the 2 pills in [http://forums.evolutionm.net/showpost.php?p=4171934&postcount=7 this post] if you want to learn more.

If you plan to use the stock BCS, read [http://forums.evolutionm.net/showthread.php?t=227006 Evo Kid's write up on stock boost control]. You will need to follow the steps listed in his tutorial to modify the stock boost control pill for any information I give you to be applicable. Go ahead and read through that thread and head back over here after you have an understanding of the mechanical side of modifying for ECU boost control.

If you are using an aftermarket 3-port BCS you will remove the stock lines and the stock restrictor pills during the install. They are not needed for a 3-port solenoid setup.

===Boost control tables===
Before we get too far in to this stuff, you might want to set your user level in ECUFlash to "Developer". To do this, select "Options" from the menu up top. You'll see a user level section on the left. Open that up and select "Developer" from the pull down menu.

{{warning|Changing the user level opens up many other tables that we may or may not be using in this tutorial. If you don't know what a table is, don't mess with it. Setting values in ECUFlash incorrectly could possibly cause irreversible damage to your Evo.}}

On the Evo, there are no less than six tables that control boost. These tables are (in order of appearance):

====Boost Delay Timer====
[[Image:boostDelayTimerMap.gif]]
This map works with the "Boost Limit" map to protect the system from overboost. This map is a timer (in milliseconds) that comes in to play when your actual boost at a given RPM exceeds the value set in the "Boost Limit" table. If boost exceeds the limit for a time greater than the timer's value, the ECU will cut fuel to protect the engine.

====Boost Control Load Offset====
[[Image:boostOffsetMap.gif]]
This table is an offset value that is added to the values set in the "Boost Desired Engine Load" table. The sum of the values in these two tables is your desired engine load for a given RPM. If using Mrfred's PSI-based boost control, this table is not used. You will add another table with scaling in PSI. The new table will function the same as this one.

====Turbo Boost Error Correction====
[[Image:boostErrorMap.gif]]
This table is referenced when the desired engine load differs from the actual load value. The difference in load (actual -> desired) is in the left column, and the amount of correction is a variable value in the right column. The percentage of correction is applied to the wastegate duty cycle (WGDC) to raise/lower the actual load to align with desired load. Again, when using PSI-based boost control you will create another error correction table with PSI scaling.

====BoostDesired Engine Load====
[[Image:boostDesiredMap.gif]]
The values in this table are added to the value set in the "Boost Control Load Offset" table to determine the desired load value for a given RPM. This table is as close as you will get to RPM based boost control. For PSI-based boost control, you will create another set of these tables with PSI scaling.

====Max Wastegate Duty====
[[Image:maxWGDCMap.gif]]
This map, also referred to as "Baseline Wastegate Duty," determines the initial duty cycle values of the BCS. If the actual load/PSI is not equal to the desired values in the desired boost table, the error correction values kick in and make adjustments based on the values here.

====Boost Limit====
[[Image:boostLimitMap.gif]]
This table determines the max load value considered to be safe and acceptable at a given RPM. If actual load exceeds a value in this table for a duration greater than the "Boost Delay Timer" value, the wastegate will open to reduce boost pressure.

===What you need to modify===

'''Note: Before continuing this tutorial, be sure you've saved your stock ROM in a safe place.'''

Okay. You've got you modified boost pill/3-port solenoid installed and you want to dial in your boost settings. Lets go down the list of initial changes you will need to make.

'''''WARNING:''''' Do not drive the car with the modified boost pill/3-port solenoid before flashing the ECU with your new boost settings!

====Boost Delay Timer====
This map can stay where it is,but you can increase it if you feel the need.

====Boost Control Load Offset====
Increase this value to "100." Increasing this value will add some headroom to your "Boost Desired Engine Load" (BDEL) maps and allow for easier fine tuning later.

====Turbo Boost Error Correction====
You'll want to set the top half of this map (negative Boost Error %) to "0" and change the values on the lower half (positive Boost Error %) to make a gentle ramp of correction with a maximum of about "-5%." See the image below ...

[[Image:boostErrorAdjusted.gif]]

These settings will protect you from overboost but not skew your logged Wastegate Duty Cycle (WGDC) values while dialing in boost.

====Boost Desired Engine Load====
There are 3 of these maps, and sadly, I have no idea why. So, the easiest way to proceed is to modify all 3 of the maps. This will ensure that you have the desired boost settings in any sutuation.

Set the BDEL in all 3 maps to "140" with a taper down to "100" from 5500 RPM to 7000 RPM. This value added to the load offset value of "100" gives you a desired load of "240" through most of the rev band, which is equal to about 22 psi in most cases. We're tapering down the top end to reduce heat and the chance of knock.

====Max Wastegate Duty====
Again, there are 3 maps. The same thing stands ... I honestly don't know which is which. Edit all 3.

Reduce the values in the Max WGDC tables to about "30." A setting this low is likely to not offer any boost control at all and you will likely see only wastegate spring pressure. Don't worry, we'll be adjusting this map a bit.

====Boost Limit====
Raise the values in this table to "270." If you're a little worried about overboost you can taper these values toward redline for safety. Just don't drop the values below about desired load+ 15 or you're likely to hit the cut a few times while adjusting your boost. You can also adjust these values to more tolerable levels after you've dialed in your boost.

====Min Temp for Full Boost Control====
This table is incorrectly defined, so leave it alone. Stock value is "85."

===Time to log===
Well, we haven't spoken much about logging. When you log, it's best to log the full RPM range from about 2000 to 7000, much like a dyno pull. This should be done in at least 3rd gear, but 4th is preferred if you have a safe location. You log in higher gears for several reasons:

* In higher gears boost levels are less erratic.
* RPM's climb slower, allowing you to log more data.
* The engine is under higher physical load (not directly related to logged load %) and more likely to knock, allowing for a safer tune.

When you first start logging, it's probably best to log anything and everything you can since you will not know exactly what information you're looking for. As you learn more, you'll narrow down and re-arrange the information logged to suit you're tuning needs. However,you should always log these values:

* TPS
* RPM
* Load % (I suggest performing the [http://forums.evolutionm.net/showthread.php?t=261465 2-byte load mod] for more accuracy)
* AFR from a wideband O2
* Boost (if possible)
* Timing Advance
* WGDC ([http://forums.evolutionm.net/showthread.php?t=259494 Here's how])
* and, most importantly, '''KNOCK COUNT'''

Any time you log a run you will need to monitor knock count. Knock is a record of what may be detonation or pre-ignition, which is ''very bad'' for your motor. Ideally, you always want to aim for 0 knock count over your entire log. Sometimes a random knock count of less than 3 is acceptable if it isn't consistent. Knock counts higher than 3 (actually, 1 on a IX) begin to pull timing for safety, so you definitely want to stay below that number.

There is something called "phantom knock" than can be caused by shock or vibration. Phantom knock can be diagnosed by logging an additional pull in a slightly different location or by increasing the octane of your fuel. If the knock occurs in additional logs in the same RPM/load area even with higher octane fuel, then it is real knock and you need to adjust your maps to compensate. Phantom knock is very rare on lightly modified vehicles and should not be assumed without proper validation.

Knock is generally caused by factors you can control such as AFR, boost and timing advance. If you experience knock, look at the values in that RPM range and you're likely to see something out of wack. You AFR might be too lean or too rich, you might have too much timing advance or a dramatic jump in timing, or there may be a boost or load spike in the area. The more you tune, the easier it will be to find the issue and correct it.

===Setting your final boost levels===
To dial in your boost you'll have to log several runs. If you don't have a way to log boost levels, it might be a good idea to have a passenger watch your boost gauge and keep you informed in case something were to go awry. If none of these options are available to you, you'll just have to rely on your load levels which (for the most part) are parallel to your boost levels.

Remember, your ECU is aiming to hit 240% load but is currently being limited by the decreased WGDC. As you log, you'll notice that you're not hitting the load levels requested. After you log a run,increase the Max WGDC values in all 3 tables until you reach your desired load levels while '''constantly monitoring for knock'''.

If you experience knock, check your AFR and timing advance. You want an AFR below 11.3:1 or so. If your AFR is leaner (above 11.3:1), lower the AFR to correct for knock ... if AFR is between 10.5 and 11.3 and boost is conservative, lower timing advance. You will be fine tuning these values later.

After several runs you should have your WGDC dialed in to where it needs to be. When you are getting close to where you want to be, be sure to compare your WGDC logs to the Max WGDC table in ECUFlash. You may find that the numbers you are logging are slightly lower than what the maps define. This is caused by the error correction table making adjustments for overboost. Look through your log and locate the overboost area and adjust accordingly.

Your Max WGDC values should be lower in the 3000 RPM to 4500 RPM range and ramp upward after 6000 RPM to achieve a stable boost curve. Remember, we're looking for 22 psi tapering down slightly toward redline.

Once you have your boost almost exactly where you want it, add back a little error correction to the top half of the table. A correction of3% at -20 boost error should be fine. Taper down to 0 correction at -2.5 boost error. This will help flatten your load curve by keeping you within +/- 2.5% of your requested load. After adding back the correction for low load, you might see an overall increase of about 3 in your WGDC curve. It's nothing to worry about. It's because you're not at your desired load during spool up and the BCS is now trying to correct for it. It all balances out ... that's what this table is for.

Congratulations, you've set the boost levels on your Evo. You can work a little more on fine tuning these tables if you feel confident about it. One change I've made is to increase the BDEL values in the peak torque area to allow for slight overboost. This reduces the effects of the error correction table which can sometimes over-correct and cause a dip in your boost curve just after the boost peaks. You could also fine tune the boost limit values and the error correction to better suit your needs. Play around and have fun with it. [[Image:smilie_thumbsup.gif]]

== For richer or leaner ==
Woo Hoo! You've made your first logs, set your boost levels, and determined the load areas you'll be working with from now on. Good job. Now it's time move on to the fuel.

As (I hope) you know, internal combustion engines burn more than just gasoline. They burn a fuel mixture of gasoline and oxygen. The ratio of this mixture is very important to the performance of your Evo. The science behind this mixture in relation to horsepower is somewhat advanced, so I'll leave the explanation to the experts at Innovate Motorsports. Head over to their [http://www.innovatemotorsports.com/resources/tuning-videos.php video page] and watch the video named "LM-101 'Tuning Basics'" for a detailed look at why we tune for specific fuel ratios.

*snore*

... Aaahhh! Oh, your done with the video. Cool. So, now you have a basic understanding of the stoichiometric ratio and why turbocharged engines run richer than naturally aspirated engines.

Okay, are you ready for the let down? As the video stated, we're aiming for an air to fuel ratio of 10% to 15% richer than stoich ... that would put our goal right around 12.6:1 (since we're tuning a boosted engine). Well, the thing is that number is completely unreasonable for a normal street car. Why? Because our fuel sucks. Plain and simple.

Here in the Southeast, we have 93 octane fuel, which I guess is better than those poor saps elsewhere in the country who have to deal with 91. But, even with our superior 93 octane fuel, that ideal 12.6:1 mix is overly optimistic. You see, the lower the octane rating of a fuel, the less stable it is under pressure and therefore more likely to burn in an unstable manner causing detonation or pre-ignition. As I explained earlier, this is bad.

So, we must lower the bar, accept defeat, and cry ourselves to sleep as we aim toward a more realistic mixture of around 11.0:1 to 11.5:1 while under boost.

===Some things to consider===
The fuel map isn't as straight forward as it might seem. There are a couple of small nuances that you should know about ...

'''The values in the fuel map are not actual AFR values.''' They do represent AFR and look like AFR values, but they are not a reference to the actual mix. Just remember that raising the value takes away fuel and lowering the value adds fuel.

Mitsubishi decided to do some funny thing with the fuel map that leans the actual mix within a certain range in comparison the the mapped value. This is commonly referred to as "lean spool." You might notice that there is a significant value shift on the fuel map between 2000 RPM and 2500 RPM ... that's where the lean spool effect begins. This affects your tuning by throwing off the values even in the fuel map even more and causing shifts in AFR between gears. Lean spool can be disabled, and there is a [http://forums.evolutionm.net/showthread.php?t=261465 tutorial on EvoM] that will show you how.

Here is a comparison of 2 fuel maps. The top map still has lean spool enabled and the lower one has no lean spool.

[[Image:leanSpoolCompare.gif]]

Also, there are 2 fuel maps. One labeled "High Octane" and one "Low Octane." The high octane map is the first map referenced and will be the map used if you are experiencing no knock. The low octane map is referenced if the motor sustains knock over a period of time. Your logging software should show an octane value that you are able to log. This value will let you know if you are using the high or low octane map. The octane value will drop when you hit more than 6 counts of knock. When this value drops, the ECU begins interpolating between the high and low octane maps for fuel and timing. How much interpolation actually occurs is speculation, but just know that it happens. So, if you see this value drop, your log will not be accurate. Locate the source of the knock, repair it and try again.

===Setting a nice fuel curve===
So, now we know what we are aiming for and we can begin tuning. You can start your fuel tuning based on your final boost log. Here is what you want to do:

From 3500 RPM to about 6000 RPM you want to aim for an AFR of about 11.2:1. This is a safe value for pump gas. With higher octane fuel you can go leaner.

Here is a trick for you ... remember that magical 12.6:1 AFR I mentioned earlier? There is a way we can make use of that optimum burn.At low RPM, while the turbo is still trying to spool, it is much less likely to knock. This is because without boost, our engines are just low compression 4-bangers. I've found that running this 12.6 (or so)AFR during spool up will actually help the turbo spool faster than the basic ramp down to 11.2:1. I've successfully run an AFR in the mid 12s up to 13 psi on the stock turbo with 0 knock. This helped the turbo reach full boost about 250 RPM sooner.

At the high end of the revs, it's a good idea to gradually richen the mix since knock is often seen at higher RPM. An AFR of 10.9:1 is a safe value at 7000+ RPM. Ramp down to this value starting around 6000 RPM.

Remember, while tuning, always monitor for knock and '''make small, gradual changes'''. If you see knock while tuning your AFR, pull timing or reduce boost if there is a spike.

You're looking for something similar to this ...

[[Image:fuelCurve.gif]]

See, the process is getting a little easier now, huh?

== Excuse me, do you have the timing? ==
You're half way there ... let's move on to setting the timing. Now, the "timing" I'm talking about here it the adjustment of the moment when the spark plug fires to ignite the fuel.

There are 3 high octane timing maps, and 3 low octane timing maps on your Evo IX. These high and low octane maps work the same as the fuel maps ... if knock is encountered for an extended period of time, some interpolation will occur. You want to focus on the high octane maps right now.

If you compare the 3 high octane maps, you'll notice that they are not the same. Map #2 is a little more aggressive with more advance across most of the map. As mentioned earlier, it's speculated that the #2 map is the main map used during normal operating conditions. I've personally found that interpolation occurs across (mainly) the #2 and #3 maps even when no knock is present.

So, the tactic I've found most useful is setting all of the high octane maps with the same values. This produces dependable results and makes your life a lot simpler. Don't worry ... if something goes wrong, you'll still have the low octane maps to keep the car safe.

===Let's talk theory===
There is a theory that many tuners use as a guide for tuning timing. It's referred to as "Minimum Timing for Best Torque" (MTBT).

Looking at tuning from the most basic sense, timing advance makes power. This is what some tuners will set the timing unusually high and let the ECU's built in safety features correct for it ... more on that later. However, it is believed that there is a point where advancing the timing does not produce extra power ... it simple makes the engine more prone to knock. So, according to the MTBT theory, the best way to set timing advance is to advance it until you don't gain any more power. Tuning this way gives you more room to make power other ways, such as more boost, a leaner fuel mix or cam advance.

The MTBT theory is based on an absolute fact that an engine will produce the most power when peak cylinder pressure occurs at 15* past top dead center (TDC). This is the point in the ignition stroke where the rod has the most leverage to turn the crank. Now, you might think that 15* is an absolute timing advance number that we are aiming for, but it's not. We can control when the spark fires, but that doesn't mean at that exact moment the cylinder pressure is at it's greatest ... it's an involved process. We must consider the gap and temperature of the plug, the time it takes for the burning fuel to reach its maximum potential and the speed at which the engine is spinning.

To use this method of tuning, you'll need some way to measure the power output of the motor. The obvious and most effective way is on a [http://en.wikipedia.org/wiki/Dynamometer dynamometer]. But, dyno time is expensive and tuning takes time. Some of us don't really have much of either. There are other solutions though ... you can use some pretty complex equations and create your own road dyno. This will allow you to measure your cars performance based only on the values you can log from your ECU. You do need to know some vital info though .. such as vehicle weight, drag coefficient, gear ratios, frontal area of the vehicle, ambient temps, etc. Many self tuners use [[Data Log Lab]] for this analysis. EvoScan also has a power/torque calculation feature built in to the graph viewer, but I've found it do be only marginally useful.

'''Note:''' When using a road dyno your results will not be as accurate as an actual dynamometer. Since the calculations are based mainly on RPM gain over time, the actual road surface you choose can skew the numbers produced. It is highly recommended that you only compare data recorded on the same stretch of flat road if you want reliable results.

===Time to make some actual changes===
Timing can be advanced (+) or retarded (-) in regard to TDC (0). Advanced timing means that the spark fires before TDC and retarded means ignition occurs after TDC. I know it seems backward, but trust me.

We are aiming for peak pressure at the magical 15* ATDC. Now, lets look at the individual components that affect this peak pressure and when it occurs:

====RPM====
The speed the engine is spinning. This one is simple. The faster the engine is spinning, the earlier the spark has to fire for the burn to keep up.

====Fuel====
The A:F mix affects the length of the fuel burn in the cylinder. A leaner mix will burn faster, and will therefore require less advance to hit the 15* mark. The opposite is true for a richer mix. The added fuel will take longer to burn and will require more advance.

Also, the fuel octane should be considered here as well. The octane level doesn't really affect the timing needed, but more so the timing range available while avoiding knock. 87 octane fuel will burn exactly like 93, but you are less likely to reach your desired ignition point on 87 before you encounter pre-ignition.

====Spark====
The spark is probably the most crucial component in this array of variables. The heat range and gap of the plug play a very important role in the process. A "colder" (lower heat range) plug will slow the burn of the fuel and reduce the chance of knock by keeping cylinder temps and the temperature of the plug tip itself lower. This is important for us because cylinder pressures are generally higher in forced induction engines ... this increased pressure combined with excess heat is usually the cause of knock.

'''Note:''' The basic rule is that you need to go 1 heat range colder after adding 100hp to the car and close the gap by .004 every 50 hp. This means increased boost, an open filter and exhaust on an average Evo could call for a colder plug.

The material of which the spark plug's electrode is made should also be considered. Our cars come equipped with iridium plugs. Iridium is used as an electrode material because it does not corrode or melt in the cylinder like plugs of the past. This property creates a reliable spark over an extended period of time. Some people choose to run copper plugs for their increased conductivity. This is an advantage and is likely to give a slight increase in power. However, copper electrodes wear extremely fast in our cars and need to be changed every 5000 miles or earlier.

Basically, if you have some power mods on your Evo you want to run a colder plug (Stock IX = ILFR7H ... NGK only makes a colder plug in it's racing series, which is R7437-8). The plug gap should be on the high end of factory spec for best performance. Gap for the IX should be between .020 and .024. This kind of sucks because replacement plugs come at .044 or .032, which will likely cause misfire issues. Maybe the dealer sells the ILFR7H @ a .22 gap, but I've only seen them at .044. Either way, [http://www.sparkplugs.com/results_app.asp?productTypeID=1&AAIA=1432585 here is a list of plugs that will work].

The Evo IX comes with a colder plug than the VIII so basic mods on the IX don't require a plug change. The standard, colder replacement plugs for the VIII are the BR7ES (1/2 step colder) and BPR8ES (1 step colder).

For more info on plugs, [http://sevo.motionforum.net/engine-turbo-f10/spark-plugs-t116.htm check here].

(still adding ...)

== [Missing Sections] ==
===VVT ... no, it's nottransmitted sexually.===
===So... what now?===
===Summary?===

Template:Warning

2010-05-04T02:31:46Z

EdwardMarshall:

<br /><div style="border:1px solid red;background-color:#f9e9e9;padding:10px;">
[[Image:Warning.gif|left]] '''WARNING!''' {{{1}}} <br style="clear: both" />
</div> <br />

Template:Warning

2010-05-04T02:31:31Z

EdwardMarshall:

<br /><div style="border:1px solid red;background-color:#f9e9e9;padding:10px;">
[[Image:Warning.gif|middle]] '''WARNING!''' {{{1}}} <br style="clear: both" />
</div> <br />

Main Page

2010-05-04T02:30:59Z

EdwardMarshall:

'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

''Note to editors:'' if you're planning on adding a new page to the wiki, thank you for the help! But please, make sure you check to see if it doesn't already exist first. For example, we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. If the page you were going to add is already covered by an existing page, please help us improve by augmenting and cleaning up the existing articles. Thanks!

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''. If you are not careful you can destroy your ECU or worse, your engine. If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health. Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you. Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM. Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.

Template:Warning

2010-05-04T02:30:42Z

EdwardMarshall:

<br /><div style="border:1px solid red;background-color:#f9e9e9;padding:10px;">
[[Image:Warning.gif|left]] '''WARNING!''' {{{1}}} <br style="clear: both" />
</div> <br />

Template:Note

2010-05-04T02:29:49Z

EdwardMarshall:

<br /><div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;">
[[Image:Notepad.gif|left]] '''NOTE:''' {{{1}}} <br style="clear: both" />
</div> <br />

Template:Note

2010-05-04T02:25:10Z

EdwardMarshall:

<br /><div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;">
[[Image:Notepad.gif|middle]] '''NOTE:''' {{{1}}}
</div><br />

Template:Note

2010-05-04T02:22:12Z

EdwardMarshall:

<br /><div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;">
[[Image:Notepad.gif]] '''NOTE:''' <br /> <br /> {{{1}}}
</div><br />

Immobilizer Disabling

2010-05-04T02:21:49Z

EdwardMarshall:

Occasionally, there is a need to disable the immobilizer in the ECU. Situations where this can occur are:

* When switching from the USDM [[96940011]] ROM to the AUS/EU [[96530006]] ROM; the immobilizer code in 96530006 operates differently, and needs to be disabled when used on a USDM vehicle. (Update: this is no longer necessary for simply switching ROMs; see the first part of the [[96530006]] description for more details.)
* When the original immobilizer code has been lost due to user error, such as overwriting the original ROM on the vehicle with one found online without making a backup first.
* Your keyfob has been damaged, and the RFID tag can no longer be read properly by the ECU.

{{note|'''This information is provided solely to help you restore the operation of ''your own'' vehicle; this website's operators and authors do not endorse the use of this information for mischief or illegal purposes'''.}}

First, please read the page [[Periphery Configuration]]; you'll need to add the configuration information shown there to be able to do this. (This should no longer be necessary with newer versions of EcuFlash, although the periphery values are unlabeled.)

Once you've added that information, open EcuFlash and load your ROM. Scroll down to the "ECUPeriphery" section, and open the "ECU Periphery 0 (FAA) Bits" table. You should see a table of choices, one of which is "Immobilizer Enabled?", with a "1" in the column next to it. Select the field with "1" in it, and press the "[" key to change it to a "0" instead. You should see the entire bottom half of the column show an indication that it was changed; this is normal, because you're actually changing that whole byte of information, not just the bit you just edited.

After saving your work, simply upload your changes to the ECU as you normally would, and your immobilizer should now be disabled. To test, simply leave your car parked in a bad neighborhood overnight.

{{warning|Be aware that this disables an important security feature of your vehicle, and should not be done without understanding the full impact of the change.}}

Template:Note

2010-05-04T02:20:31Z

EdwardMarshall:

<div style="border:1px solid blue;background-color:#f9f9e9;padding:3px;">
[[Image:Notepad.gif]] '''NOTE:''' <br /> <br /> {{{1}}}
</div>

USDM ACD Pinout

2010-05-03T21:47:57Z

EdwardMarshall: Created page with '{{warning|This document is still being put together. Don't trust anything you read in here for now; check the [http://forums.evolutionm.net/ecuflash/473547-break-thru-reading-acd…'

{{warning|This document is still being put together. Don't trust anything you read in here for now; check the [http://forums.evolutionm.net/ecuflash/473547-break-thru-reading-acd-ecu-ecuflash.html EvoM thread] or [http://evoscan.com/technical-vehicle-manuals/62-acd-ayc-sayc-at EvoScan website] for more details.}}

The USDM Evo VIII ACD ECU uses a two-plug harness, with two rows of pins for each plug. See the [[Plugs, Pins, and Connectors]] page for part numbers and further details.

= Complete harness =

Pins 1, 2, 3, 12, 13, 14, 15, 16, 31, 37, 38, 39, 51, and 52 (16 total) are "large" (ie. power); the remaining (32) pins are "small" (signal). Large pins have been marked in the diagrams below with a yellow background color.

{| border=0 cellspacing=0 cellpadding=5
!C-121!!C-115
|-
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|1||style="background-color: yellow"|2||style="background-color: yellow"|3||4||5||6||7||8||9||10||11||style="background-color: yellow"|12||style="background-color: yellow"|13
|-
|style="background-color: yellow"|14||style="background-color: yellow"|15||style="background-color: yellow"|16||17||18||19||20||21||22||23||24||style="background-color: yellow"|25||style="background-color: yellow"|26
|}
|
{| border=1 cellspacing=0 style="text-align: center"
|style="background-color: yellow"|31||32||33||34||35||36||37||38||39||style="background-color: yellow"|40||style="background-color: yellow"|41
|-
|style="background-color: yellow"|42||43||44||45||46||47||48||49||50||style="background-color: yellow"|51||style="background-color: yellow"|52
|}
|}

Template:Warning

2010-05-03T21:47:37Z

EdwardMarshall:

<div style="border:1px solid red;background-color:#f9e9e9;padding:10px;">
[[Image:Warning.gif]] '''WARNING!''' <br /> <br /> {{{1}}}
</div>

ECU Development

2010-05-03T21:36:11Z

EdwardMarshall: /* Hardware */

== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[USDM ACD Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)

Plugs, Pins, and Connectors

2010-05-03T21:35:53Z

EdwardMarshall: /* ACD ECU */ Add pin size information.

= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-1&RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-2&RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172771-2&RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-1&RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-2&RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-1&RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-2&RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

The 22-pin plug requires six large (power) pins, and the 26-pin plug has 10.

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]. No, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors.

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

Plugs, Pins, and Connectors

2010-05-03T21:27:39Z

EdwardMarshall: Add ACD information.

= 1g DSM ECU =

This ECU appears to use AMP/Tyco Pulse Lock connectors. ''THIS HAS NOT BEEN VERIFIED YET.'' I'm keeping notes here as I confirm information about these plugs.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''6'''
:: gray
: X-'''7'''
:: yellow

''Plugs:''
: 10-pin plug, '''172315'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=1

: 18-pin plug, '''172316'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=2

: 24-pin plug, '''172317'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=247&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44495,44389,44395,44392,44378,44498,44500&N=4

: ECU-side connector, '''172319'''
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=11280&M=PPROP&P=&BML=10576,17560,17536,17534&LG=1&PG=1&IDS=44547,44546,58465,44263,44270,44483,44495,44389,44395,44392,89825,44378,44542,44498,44500,44399,44473,44534,72076,44276&N=1

: 20-22 AWG plug pin, '''170352-1'''/'''170352-2''' (strip), '''172771-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-1&RQPN=170352-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170352-2&RQPN=170352-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172771-2&RQPN=172771-2

: 16-20 AWG plug pin, '''170353-1'''/'''170353-2''' (strip), '''172772-1'''/'''172772-2''' (loose)
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-1&RQPN=170353-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=170353-2&RQPN=170353-2
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-1&RQPN=172772-1
:: http://www.tycoelectronics.com/catalog/bin/TE.Connect?C=1&M=BYPN&TCPN=172772-2&RQPN=172772-2

= Evo VIII and 2g DSM ECU =

This ECU uses [http://www.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Specification+Or+Standard%7F114-8005%7FA%7Fpdf%7FEnglish%7FENG_SS_114-8005_A.pdf Multilock 040/070-Series Hybrid Connectors] from [http://www.tycoelectronics.com/automotive/products.asp AMP (Tyco)].

[http://www.digikey.com/ Digikey] doesn't seem to stock these, but [http://www.newark.com/ Newark] has all of the pins in stock, and [http://www.mouser.com/ Mouser] has the large pins.

There are multiple colors available for each plug part number; where "X" is the base part number, the pattern to use when ordering is:
: X-'''1'''
:: white
: X-'''2'''
:: black (non-RoHS)
: X-'''5'''
:: blue
: X-'''6'''
:: gray
: '''6'''-X-'''6'''
:: light gray
: X-'''7'''
:: yellow

The 22-pin plug has 6 large pins (four on the left, two on the right), and the 26-pin plug has 10 large plugs (four on the left, six on the right), for a total of 16 large pins for a complete harness. All other pins (12, 16, 16, and 16, for each plug respectively, or 60 total) are of the small variety. Note that not all pins are actually used; see the [[USDM VIII ECU Pinout]] for details.

''Plugs:''
: 12 pin male, '''917978''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917978%7FC1%7Fpdf%7FJapanese%7FJPN_CD_917978_C1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917978-1-ND

: 16 pin male, '''917981''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917981%7FA%7Fpdf%7FEnglish%7FENG_CD_917981_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917981-1-ND

: 22 pin male, '''917989''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917989%7FA1%7Fpdf%7FJapanese%7FJPN_CD_917989_A1.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917989-1-ND

: 26 pin male, '''917992''' ([http://ecommas.tycoelectronics.com/commerce/DocumentDelivery/DDEController?Action=showdoc&DocId=Customer+Drawing%7F917992%7FA%7Fpdf%7FEnglish%7FENG_CD_917992_A.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=917992-1-ND

''Pins:''
: Large pins, '''175265-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175265-1-ND

: Small pins, '''175269-1'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=175269-1-ND

= Evo IX ECU =

This ECU uses [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX7 JAE MX7-series connectors]. Digikey seems to maintain stock of these plugs and pins; Jamie (Jack_of_Trades) also [http://www.dsm-ezine.com/evo9pins.html makes pins available].

Each plug has a block of 6 large pins (so, a total of 18), with the remainder (75) being the small type. Note that not all pins are actually used; see the [[USDM IX ECU Pinout]] for details.

''Plugs:''
: 28 pin retainer clip, '''MX7-A-28S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2312-ND

: 28 pin plug, '''MX7-A-28SC''' ([http://jae-connector.com/en/pdf/SJ028728.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2313-ND

: 30 pin retainer clip, '''MX7-A-30S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2314-ND

: 30 pin plug, '''MX7-A-30SC''' ([http://jae-connector.com/en/pdf/SJ028727.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2315-ND

: 35 pin retainer clip, '''MX7-A-35S-RT'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2316-ND

: 35 pin plug, '''MX7-A-35SC''' ([http://jae-connector.com/en/pdf/SJ028726.pdf datasheet])
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2317-ND

''Pins:''
: Large pins, '''MX7-PWC2-1E-4500'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2319-ND

: Small pins (tin), '''MX7-SGC3-7000'''
:: http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&name=670-2320-ND

= ACD ECU =

These are JAE [http://jae-connector.com/en/general_en.cfm?l_code=EN&series_code=MX5-E MX5-E] 3mm-pitch connectors. DigiKey doesn't carry them, although JAE still lists them as active items (as of last check, only the pins were available via the sample program).

''Plugs:''
:22-pin plug, '''MX5-E-22S-C-N''' ([http://jae-connector.com/en/pdf/SJ030493.pdf datasheet])

:26-pin plug, '''MX5-E-26S-C-N''' ([http://jae-connector.com/en/pdf/SJ030492.pdf datasheet])

''Pins:''
: Small pins, '''MX5-SG-C1-5000''' ([http://jae-connector.com/en/pdf/SJ028805.pdf datasheet])

: Large pins, '''MX5-PW-C0-4000''' ([http://jae-connector.com/en/pdf/SJ030048.pdf datasheet])

= OBD-II Connector =

Tyco/AMP produces the in-car (female) side of the plug as part numbers 179631 or 348822, and both use the same pins, either P/N 776001 or 1827012. Molex has a similar offering; the pins are P/N 50420, and the housings are 51115 (with a 51117 retainer) and 51116 (with a 51118 retainer). Delphi/Packard's part numbers are 11210250 for the housing and 12129373, 12129484, 13525297, and 15317769 for the pins (female Metri-Pack 150).

The client-side connection is pretty ubiquitous. The Molex P/Ns are 57964 for the pins, and 68503 for the housing. Delphi shows 12110252 as the P/N for the housing, and 12040993, 12047581, 12059894, 12092165, 12110502, 12160811, 15305307, or 15326725 for the pins (male Metri-Pack 150), depending on the size you need.

= Diagnostic Connector =

The Evo "diag" male connector (ie. the one under the dash) is a Sumitomo MT-series M(6244-1121) 12-way connector ([http://forums.openecu.org/viewtopic.php?p=4552 citation]), which was apparently a special-purpose run specifically for Mitsubishi. The US Evo service manual refers to this plug as MU801855. [http://www.seaps.com.sg/pdf/a_mt_e.pdf An old PDF] from SWS seem to indicate this connector may have actually been M(6520-0178) instead, however.

The female plug (for a cable) is a Sumitomo MT-series F(6244-5121) 12-way connector; it appears that [http://www.sws.co.jp/ SWS] in Japan can source these. ([http://forums.evolutionm.net/3935684-post42.html citation]). The pins are:

: F(8240-4849)
:: gold-plated, 0.2-0.5mm cable size)
: F(8240-4412)
:: tin-plated, 0.2-0.5mm cable size
: F(8240-4422)
:: tin-plated, 0.5-1.25mm cable size)
: F(8240-4652)
:: tin-plated, 2.0mm cable size, and cables are to be AVSS

Earlier 1g DSMs, late (97+) 2g DSMs, and earlier Evos also used this physical connector (for the MUT scantool on 1gs and Evos I-III, and as a flashing interface on later 2gs and Evos), but with a [http://www.dsmlink.com/wiki/diagport-12pin different pinout].

([http://swsct.sws.co.jp/components/series/pdf/mt.pdf PDF of MT-series connectors], [http://swsct.sws.co.jp/components/en/housing.asp?number_s=62445121mt link to item in SWS catalog])

One confirmed commercial source for these is [http://www.easternbeaver.com/ Eastern Beaver]. No, that's not a porn site, it's a Canadian guy who lives in Japan and sells motorcyle parts and carries a fairly extensive lineup of Sumitomo connectors.

(The actual part that appears in Evo and DSM vehicles seems to be a product of [http://www.mcausa.com/ Mitsubishi Cable America]; specifically, a [http://www.mcausa.com/unsealed/pdf/cs.pdf CS-style] connector. MCA does not sell directly to end-customers, although has shown some willingness via email and phone to source samples in small quantities for those having difficulty sourcing them elsewhere.)

= Boost Control Solenoid / EGR =

These are also Sumitomo parts: TS-series F(6188-0624) for the female plug, and TS-series M(6189-0264) for male. Again, it appears that [http://www.sws.co.jp/ SWS] can source these, and Ballenger Motorsports carries (as a special order item) the female plug in either an [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1683 assembly] package, as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1681 kit], or as a [http://www.bmotorsports.com/shop/product_info.php/cPath/109_110/products_id/1682 complete pigtail], along with the necessary [http://www.bmotorsports.com/shop/product_info.php/products_id/1567 pins] and [http://www.bmotorsports.com/shop/product_info.php/products_id/940 seals]. ([http://swsct.sws.co.jp/components/series/pdf/tss.pdf PDF for TS-series connectors]) Fully-assembled adapters for GM solenoids, as well as individual connectors, can also be ordered from [http://www.szabaga.com/store/diy.html spoolinup.com].

As a fun bit of useless trivia, the WRX BCS connector appears to be the opposite connectors: M(6188-0266) and F(6189-0249); the difference being the position (left side vs. right) of the key on the bottom of the male connector.

ECU Development

2010-05-03T15:26:06Z

EdwardMarshall: /* Hardware */

== Getting Started ==

* [[Development Tips]]

== Hardware ==

* OpenPort cable schematics (PDF): [[media:Openport.pdf|1.0]], [[media:Openport12.pdf|1.2]], [[media:Openport13.pdf|1.3U]] (sources: [http://forums.openecu.org/viewtopic.php?p=3220 original/1.2], [http://forums.openecu.org/viewtopic.php?t=542 1.3])
* [[media:Monamona-cablle-schematic.pdf|Monamona cable schematic]] (PDF) (sources: [http://minkara.carview.co.jp/userid/220698/blog/10838561/ blog], [http://sourceforge.jp/projects/ecuexplorer/document/monamona-cablle-schematic/ja/2/monamona-cablle-schematic.pdf schematic], [http://sourceforge.jp/projects/ecuexplorer/ SourceForge.jp project])
* [[1G DSM Datalogging Cable]]
* [[USDM VIII ECU Pinout]]
* [[USDM IX ECU Pinout]]
* [[OBD Pinout]]
* [[Diag Pinout]]
* [[Useful Tools]]
* [[Plugs, Pins, and Connectors]]
* [[Map switching harness]]

== Communications ==

* [[MUT Requests]]
* [[MUT Commands]]

== Development ==

* [https://rallyevo.com:8443/svn/evom/ Subversion repository] ([http://forums.evolutionm.net/ecuflash/454139-svn-repository-online-all-xml-roms-tools-spreadsheets-go-here.html EvoM thread], which includes authentication information)

File:Monamona-cablle-schematic.pdf

2010-05-03T15:22:41Z

EdwardMarshall:

Main Page

2010-05-02T00:54:42Z

EdwardMarshall: Add note about the mirror directory.

'''Welcome to the Evo ECU Wiki!'''

The [[wikipedia:Mitsubishi Lancer Evolution|Evo]] has a powerful stock [[Wikipedia:Engine control unit| Engine control unit]] (ECU) which can be reprogrammed to accommodate the needs of each individual car based on their modifications and desired outcomes.

This wiki has the goal of detailing, with community contributions, how to tune, patch, and log your stock ECU, but it isn't the only resource available to you; please see our [[Helpful_Links|helpful links]] page for other sites that provide useful information.

'''But wait, there's more!''' We also have mirrors set up for a variety of software packages, documentation, and other bits and pieces that folks find useful in our [http://evoecu.logic.net/mirror/ mirror section]. If you're looking for an obscure ROM version, an old version of EcuFlash, or some other odd bit of software, there's a good chance we might have a copy of it here.

''Note to editors:'' if you're planning on adding a new page to the wiki, thank you for the help! But please, make sure you check to see if it doesn't already exist first. For example, we already have pages on [[EvoScan]], [[EcuFlash]], [[Logging Cable]], [[Wide Band Air Fuel Meter]], and a [[Glossary]]. If the page you were going to add is already covered by an existing page, please help us improve by augmenting and cleaning up the existing articles. Thanks!

{{Warning|Tuning or patching the ECU can be '''VERY DANGEROUS'''. If you are not careful you can destroy your ECU or worse, your engine. If you enter a value incorrectly or tune the engine improperly you seriously risk your engine's health. Proceed with caution and '''ALWAYS DOUBLE CHECK''' any changes you make.}}

== Glossary ==
Throughout the pages of this wiki many acronyms are used, if you have an confusion over any terms please visit the [[Glossary]].

There are also many tables that are specifically referred to in ECUFlash that may not necessarily make sense to you. Please visit the [[ECUFlash_Specific_Glossary|ECUFlash Specific Glossary]] for an explanation of what these tables do.

==Tuning==
[[Tuning]] is the name for the process whereby you alter the fuel, ignition, boost, and other variables to influence how the ECU controls the car.

==Patching==
[[Patching]] is the new name given to modifying the code of the ROM. Through ROM modification various features of the stock ECU can either be improved or entirely new features can be created.

==Logging==
The term [[Logging]] refers to obtaining and recording data from the ECU to be used for tuning purposes.

==Downloads==
All files can be found in the [[Downloads]] section

==Development==
If you're interested in ECU communications, disassembly, patching, etc., please see our [[ECU Development]] page.