EVO/3G ECU in a 6th Gen Galant

ok so ive been doing some research on GalantVr4 and on the DSM forums and im thinking of running either a 3g Manual or an Evo ECU in my Galant, it's already been successfully swapped into a 1g and a 6GVR4 and running great, and i wanna take advantage of the tuning abilities as well as being able to run a 8g/3g MAF in place of the 6g MAF so i can run a CAI...

I have both pinouts of my 6g ECU as well as 3g/evo pinouts and 1G DSM pinouts

I plan on boosting in the future but i am aware than NT guys have run the evo ecu in their 8g's...so i dont think it would be much different in my 6g....those who did it in 1g's and Gvr4's both said the response from the swap is unbeleivable..

Parts to get:

ECU - Either 3g or Evo (Both are relatively the same)
ECU Pigtails - Either 3g or Evo
3g MAF
3g Injectors

Parts to Make:
3g/evo to 1g/6g Harness
OBDI-OBDII Cross Harness

http://i41.tinypic.com/168cztg.jpg
(harness made by keydiver on Galantvr4.org)

Everything should be plug and play with the 3g injectors and MAF


ECU Pinouts:

http://i143.photobucket.com/albums/r...981/viewer.png
http://i143.photobucket.com/albums/r...81/viewer1.png
http://i143.photobucket.com/albums/r...81/viewer2.png
(credit to eyebromski on EvoM)

The changes to get it working in the 91+ are as follows.

Evo 19- DSM 6 - 90 to 91 changed the wire for the MAF Reset from 14 to 6
Evo 43-DSM 104 - This is the clutch switch. Wired up it allows use of Modded Tephra maps which have NLS, etc.
Evo 18-DSM 67 - ISC Coils are reversed but the jury is still out on if this matters.
Evo 5-DSM 68 - See above.

In addition, you'll notice one wire (Evo 62) goes to the OBDII plug, pin 7. Look here click for the OBDII pin out. The one to use is "ISO and KWP Protocol Pins". Pin 15 does not need to be hooked up. You can get power for the OBDII plug from pin 12(DSM)/102(Evo) and ground from 13(DSM)/101(Evo).

You also need to wire pin 79(Evo) to OBDI Pin 12
(credit Broxma on Galantvr4.org)


Gonna start making my harness soon....

Thanks to Spd_Frk and Isaurio for helping me out with this last night

ROM INFO 2006 EVO VIII 96530006

link: 9653006.HEX

link: 96530006.XML

link: evo7base_20081101

Oh shit, gonna be awesome!!


Sent from my iPhone using Tapatalk fam!

I would personally run a 1g EPROM and link. Probably the easiest overall as well. Speed density> the rest

some of the people who run speed density also upgraded, said it was a world of difference, think about it, faster processor will make faster response

plus this swap will cost me alot less since its more DIY...

at Max it'll only cost me $150-200 to get this done

got all the pieces to the puzzle now, grand total spent: $0.00 lol

Good work bro. True about the faster processor. Also more memory.

awesome, cant wait to see what this is going to look like since i got you most of the parts for free..

i still have to get the 3g MAF and knock sensor, i should have grabbed it out of that 3g but I forgot

^^^duah

making sure i did this right, with the help of ivory8g i was able to get the rom and xml for my ecu

added to the xml
table name="ECU Periphery00 Hex" category="Periphery" address="f9a" type="1D" level="2" scaling="Hex16"/
table name="ECU Periphery0 Hex" category="Periphery" address="faa" type="1D" level="2" scaling="Hex16"/
table name="ECU Periphery1 Hex" category="Periphery" address="fba" type="1D" level="2" scaling="Hex16"/
table name="ECU Periphery2 Hex" category="Periphery" address="fca" type="1D" level="2" scaling="Hex16"/
table name="ECU Periphery3 Hex" category="Periphery" address="fda" type="1D" level="2" scaling="Hex16"/
table name="ECU Periphery4 Hex" category="Periphery" address="fea" type="1D" level="2" scaling="Hex16"/

then changed Periphery0 - 56D0 -No rear O2 no Immobilizer
Periphery2 to 6FDF
Periphery3 to C0C0
Periphery4 to FE00

just wondering if i did that right

here's a copy of my xml and rom
https://docs.google.com/open?id=0ByM...2xVenpOWlUtWTA

I told you about the rear o2. "dont disable it". Even if the 6g dont have one. U using a rom that was written with a rear o2. If you disable u wont get your fuel trims. No fuel trims no tune. Since you the computer wont calculate your AFRs.

well i didnt flash it yet, i just worked on it with Evoscan, so i can always change it, i just wanted to make sure i did it right

Yes. Thats part of it. Not 100%. I was working on your xml. Im so busy that i dont have much time to work on it.

Would this application be made to work in a six bolt swapped 7G and congratulations on continuing to push the envelope on Mitsubishi factory part upgrading

they've made it run in a 2g, so i assume it would work with a 6bolt swapped 7g

added to my xml

Code:

---

<scaling name="blobbits" storagetype="bloblist" storagebits="1">
                <data name="0" value="00"/>
                <data name="1" value="01"/>
        </scaling>

        <table name="ECU Periphery00 (F9A) Bits" category="ECUPeriphery" address="f9a" type="2D" level="2" scaling="blobbits">
                <table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
                        <data>bit.15</data>
                        <data>bit.14</data>
                        <data>bit.13</data>
                        <data>bit.12</data>
                        <data>bit.11</data>
                        <data>bit.10</data>
                        <data>bit.9</data>
                        <data>bit.8</data>
                        <data>bit.7</data>
                        <data>bit.6</data>
                        <data>bit.5</data>
                        <data>bit.4</data>
                        <data>bit.3</data>
                        <data>bit.2</data>
                        <data>bit.1</data>
                        <data>bit.0</data>
                </table>
        </table>

        <table name="ECU Periphery0 (FAA) Bits" category="ECUPeriphery" address="faa" type="2D" level="2" scaling="blobbits">
                <table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
                        <data>bit.15</data>
                        <data>front o2 sensor heater circuit </data>
                        <data>bit.13</data>
                        <data>bit.12</data>
                        <data>Disable EGR / Enabled Ign Adv (set bit=1)</data>
                        <data>timing knockdown on light acceleration and less than 3000rpm</data>
                        <data>Enable Warmup Ign Retard</data>
                        <data>bit.8</data>
                        <data>Enable High Oct Ign Map Lookup (and many other subroutines)</data>
                        <data>"WG solenoid? Enable Speed Limit Test"</data>
                        <data>bit.5</data>
                        <data>for full time open loop set to 0</data>
                        <data>Immobilizer (1=enable 0=disable)</data>
                        <data>bit.2</data>
                        <data>rear o2</data>
                        <data>bit.0</data>
                </table>
        </table>

        <table name="ECU Periphery1 (FBA) Bits" category="ECUPeriphery" address="fba" type="2D" level="2" scaling="blobbits">
                <table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
                        <data>bit.15</data>
                        <data>bit.14</data>
                        <data>bit.13</data>
                        <data>bit.12</data>
                        <data>bit.11</data>
                        <data>bit.10</data>
                        <data>bit.9</data>
                        <data>bit.8</data>
                        <data>bit.7</data>
                        <data>bit.6</data>
                        <data>2nd thermo fan table</data>
                        <data>bit.4</data>
                        <data>bit.3</data>
                        <data>bit.2</data>
                        <data>bit.1</data>
                        <data>Lean Spool</data>
                </table>
        </table>

        <table name="ECU Periphery2 (FCA) Bits" category="ECUPeriphery" address="fca" type="2D" level="2" scaling="blobbits">
                <table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
                        <data>P0443, P0446, P0403, P0243, P0090, P2263</data>
                        <data>P0450, P0451, P0452, P0453 Evap</data>
                        <data>P0441, P0442 Evap</data>
                        <data>bit.12</data>
                        <data>P0031, P0032, P0037, P0038</data>
                        <data>P1400 MAP Sensor</data>
                        <data>P0401 EGR Test</data>
                        <data>P0506, P0507 Idle Test</data>
                        <data>P0170 (P0171, P0172)</data>
                        <data>P0134 Front O2</data>
                        <data>P0300; set bit.4 and bit.5 to 0 to disable</data>
                        <data>P0300; set bit.4 and bit.5 to 0 to disable</data>
                        <data>P0132, P0136 O2</data>
                        <data>P0133, P0159</data>
                        <data>P0421 not in FSM</data>
                        <data>bit.0</data>
                </table>
        </table>

        <table name="ECU Periphery3 (FDA) Bits" category="ECUPeriphery" address="fda" type="2D" level="2" scaling="blobbits">
                <table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
                        <data>P0128 CT Below Reg</data>
                        <data>P1603 Battery Backup</data>
                        <data>bit.13</data>
                        <data>bit.12</data>
                        <data>P0180 - P0183, P0461, P2066 Fuel Sensors</data>
                        <data>bit.10</data>
                        <data>bit.9</data>
                        <data>bit.8</data>
                        <data>P0551 PS Pressure</data>
                        <data>P0500 Speed Sens</data>
                        <data>bit.5</data>
                        <data>bit.4</data>
                        <data>bit.3</data>
                        <data>P0234, P0243, P2263</data>
                        <data>P0510 not in FSM</data>
                        <data>P1715, P1750, etc</data>
                </table>
        </table>

        <table name="ECU Periphery4 (FEA) Bits" category="ECUPeriphery" address="fea" type="2D" level="2" scaling="blobbits">
                <table name="Periphery Bit Number" type="Static Y Axis" flipy="true" elements="16">
                        <data>P0140 Rear O2 No Act</data>
                        <data>P0069 MAP vs Baro</data>
                        <data>P0111 IAT Circuit</data>
                        <data>P0554 PS Press Sens</data>
                        <data>P1530 A/C1 Switch</data>
                        <data>bit.10</data>
                        <data>bit.9</data>
                        <data>P0830 Clutch Pedal Circuit</data>
                        <data>P0090 Fuel Pressure Circuit</data>
                        <data>bit.6</data>
                        <data>bit.5</data>
                        <data>bit.4</data>
                        <data>bit.3</data>
                        <data>bit.2</data>
                        <data>bit.1</data>
                        <data>bit.0</data>
                </table>
        </table>

---

MAF PINOUT CONVERSION

Turbo 1G/GVR4 MAF pinout
Pin 1 = Reset
Pin 2 = Airflow Hz
Pin 3 = +12 Volt from MPI
Pin 4 = +5 Volt Sensor Power
Pin 5 Not Connected
Pin 6 = Sensor Ground
Pin 7 = Barometer
Pin 8 = Intake Air Temp

2G/3G/EVO MAF pinout
Pin 1 = +5 Volt Sensor Power
Pin 2 = Barometer
Pin 3 = Airflow Hz
Pin 4 = +12 Volt from MPI
Pin 5 = Sensor Ground
Pin 6 = Intake Air Temp
Pin 7 = Reset
Pin 8 Not Connected

So, the correct crossover wiring to our MAS plug is:
3G/EVO Pin 1 to 1G MAS Pin 4
3G/EVO Pin 2 to 1G MAS Pin 7
3G/EVO Pin 3 to 1G MAS Pin 2
3G/EVO Pin 4 to 1G MAS Pin 3
3G/EVO Pin 5 to 1G MAS Pin 6
3G/EVO Pin 6 to 1G MAS Pin 8
3G/EVO Pin 7 to 1G MAS Pin 1

Quote:

---

Originally Posted by Isaurio

I told you about the rear o2. "dont disable it". Even if the 6g dont have one. U using a rom that was written with a rear o2. If you disable u wont get your fuel trims. No fuel trims no tune. Since you the computer wont calculate your AFRs.

---

Why would disabling the rear o2 effect the fuel trims? The fuel trims are calculated with the front o2. The only job of the rear o2 is to check for effectiveness of the cat on a stock car.

If your using a evo8 ecu why not just run speed density of the bat and save your self the trouble of buying a maf.As for injectors you can run any injector you want. You just need to get the global and deadtime.

Interesting......

No rebuttal? I actually want a good convo someone?

I'm using a 3g ecu. Not an evo one..and its cheaper for me to get a maf than to get speed density to get the car started

Sent from my PC36100 using Tapatalk 2

Quote:

---

Originally Posted by imback

No rebuttal? I actually want a good convo someone?

---

Can't wait for Isaurio to Skool you bro don't worry I'll let him know your looking for a challenge make sure u got your big boy pants on!

Quote:

---

Originally Posted by imback

Why would disabling the rear o2 effect the fuel trims? The fuel trims are calculated with the front o2. The only job of the rear o2 is to check for effectiveness of the cat on a stock car.

If your using a evo8 ecu why not just run speed density of the bat and save your self the trouble of buying a maf.As for injectors you can run any injector you want. You just need to get the global and deadtime.

---

I believe mitsu did a check balance. Both o2 sensor check each other for a accurate reading to give you a fuel trim. The math of the fuel trims includes the second o2 for calculation period!!. Programers had wrote a extra code to simulate a virtual second o2 so you could delete without affecting the trims calculations. Without that is no other way around it. U could try but you will fail.

Going SD takes a lot of tuning to get running 100% since the computer could not re-adjust itself with any air to fuel changes due to the maf missing. The tune needs to be from the bottom up since he using a different hardware "engine parts" than the evos. Maf would be more flexible with this big changes. All this things are easy said than done. But the ecu or pcm thinks different.

Maf is the way to go for a start up built specially with a totally different ecu. Is not just fuel, timing and injectors needs to be change to get a engine running. Is the little sensors that does most of the job that also needs to be readjusted within the rom.

world first when this is all said and done? I think it is!

Uum I don't think he's the first but defiantly one of a hand full at best. In any case major props to Denver this is a conversion u just don't see period.

Quote:

---

Originally Posted by deeznutz

Can't wait for Isaurio to Skool you bro don't worry I'll let him know your looking for a challenge make sure u got your big boy pants on!

---

Um ok lol


The only purpose of the rear o2 is for checking of the cat efficiency. This is for emissions only. If the rear o2 see's that the reading is low it will throw a CEL and that's it. There a few things that will throw the ecu into open loop but a clogged cat is not one of them. You are right about SD taking time to set up but i'm sure there is a map out there or a map that's close enough to get it running.Hell you can find a stock dsm map and just modify it buy adjusting the the cells in the higher load region. I never got into flashing so i can't say much about that but only thing needed for getting a car running on SD would be a map sensor. A maf would be easier though in the long run since you still have to work out some of the bugs.

^ u are missing the ecu comands. Every one knows 2 o2 it check the cat for any efficiency of the AFR but thats one of the job. But like i said is a check and balance, both o2 check for the AFR mixture to check and readjust your fuel mixture, it adjust your injectors to stay at 14.7 on closed loop "o2 monitoring". You cant depend in only one o2 sensor to make a big fuel mixture calculation and chances, the ecu uses 2 o2 to minimize any error to avoid knock and performance. If it gets to lean it will cause knock making the computer go to the low fuel and timing maps. The old 6g and older cars dont need the second o2 because the ecu did not have enough memory to write extra commands to it. Know ecu has more ROM memory and processing power to make fast and more complex calculations.

You cant just plug another map from a SD Rom to non SD rom. People call this base map to get you going and start. Here is the problem. The SD map are made just for that specific component on the engine, injectors, displacement, head, intake mani, map sensor and more. If you transfer the maps to a whole different setup. 1 it will run like shit. 2 you will knock like crazy due to the unbalance fuel mixture. 3 you could damage the engine if you run it for a long period of time since the ecu CANT readjust the fuel mixture. SD always run open loop.

Learning learning..... OK question

Y not just weld an o2 bung into your 6G exhaust its easy and whether your right or wrong the 3g ecu can soul with the information it was designed a to calculate

The ECU only relies on feedback from the front o2. The STFT (short term fuel trim) is what is used to get the desired a/f ratio of 14.7 assuming this is on regular gasoline. These older cars like the 6g's are based of the same technology that the 1g and 2g dsm use and i have a very good understand of how they work since i've worked on them for a long time.1 I never said putting in another map would make it run perfect but since your able to adjust hence the reason going through all this trouble it wouldn't be to hard as long as you have a basic understanding of how to adjust things. 2 You would have to be so rich in order to get rich knock cause you are most defiantly not getting real knock since the n/t 4g is pushing no were near as much airflow. 3 SD does not always run open loop unless you force it to run open loop. Your running a OEM computer that want's to see feedback from the front o2. If your fuel trims are so off then yes it will be stuck in open loop cause adjustment needed is more then the ecu can do it self and your front o2 will be stuck at .04 volts or .89 volts.

http://www.dsmlink.com/images/forums/1GECUPinout.pdf

if 3g pin out is the same as the evo 8
http://www.roadraceengineering.com/e...-ecuwiring.htm

does not seem too hard to put together, and remember most of the wires are ground switched

i know, im done with the harness, but my car isnt running so i cant complete it

Dude that was fast!

almost done

http://i143.photobucket.com/albums/r...-3gharness.jpg

still running the 6g MAF, but SUCCESS!! car starts and idles, havent done further testing cuz im waiting on my timing belt tensioner

OBDII port and flash plug...still figuring out where I'm going to put it
http://i143.photobucket.com/albums/r...1/IMAG0229.jpg

ECU plugged in for testing purposes
http://i143.photobucket.com/albums/r...1/IMAG0230.jpg

FLASH successful
http://i143.photobucket.com/albums/r...1/IMAG0231.jpg

quick video
http://i143.photobucket.com/albums/r..._VIDEO0005.jpg

Nice man! I did the same harness conversion, but im still to test it. Great work bro!

Congrats on getting this done!

Good job bro. The response is going to be 10x better.

got it to idle a little better, this is still with the 6g MAF

NO CEL
http://i143.photobucket.com/albums/r..._VIDEO0008.jpg

Sounds good! What did you do exactly?

flashed to an EVO rom, scaled the injectors, adjusted latency, etc etc etc etc lol