Evo8 ECU in a 1G DSM in the works!
#556
Evolved Member
iTrader: (2)
The primary fan output is most certainly a PWM output and I would t recommend running it directly to a relay. You'll either burn out the output circuit on the ECU over time or start killing relays. Even with the A/C off, the condenser fan will turn on if the coolant temps exceed a specified coolant temp to help combat dangerously high coolant temps. If you want to directly control your primary fan from the ECU the correct way, you need to use the PWM module.
-Jamie
-Jamie
#557
Evolving Member
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Likes: 0
Received 0 Likes
on
0 Posts
Made a pinout for the 02-04 Lancer A/T ecu to 1G DSM, and I can confirm it works. Had my car running on it today. The 256kb Evo8 file needs to have another 256kb worth of 00 bytes added to the end in order for it to work in the A/T ecu.
http://www3.sympatico.ca/tchaad/Lanc...M%20pinout.xls
Incidentally, the ecu from a 2001-2004 2.4 A/T Hyundai Sonata works with this patch harness too. It reads and flashes exactly the same way as the Lancer A/T. This ecu ran my car exactly the same way as the Lancer A/T one .
http://www3.sympatico.ca/tchaad/Lanc...M%20pinout.xls
Incidentally, the ecu from a 2001-2004 2.4 A/T Hyundai Sonata works with this patch harness too. It reads and flashes exactly the same way as the Lancer A/T. This ecu ran my car exactly the same way as the Lancer A/T one .
Last edited by Broke4speed; Apr 13, 2013 at 04:56 PM.
#558
Evolved Member
iTrader: (2)
Made a pinout for the 02-04 Lancer A/T ecu to 1G DSM, and I can confirm it works. Had my car running on it today. The 256kb Evo8 file needs to have another 256kb worth of 00 bytes added to the end in order for it to work in the A/T ecu.
http://www3.sympatico.ca/tchaad/Lanc...M%20pinout.xls
Incidentally, the ecu from a 2001-2004 2.4 A/T Hyundai Sonata works with this patch harness too. It reads and flashes exactly the same way as the Lancer A/T. This ecu ran my car exactly the same way as the Lancer A/T one .
http://www3.sympatico.ca/tchaad/Lanc...M%20pinout.xls
Incidentally, the ecu from a 2001-2004 2.4 A/T Hyundai Sonata works with this patch harness too. It reads and flashes exactly the same way as the Lancer A/T. This ecu ran my car exactly the same way as the Lancer A/T one .
#561
Evolving Member
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Likes: 0
Received 0 Likes
on
0 Posts
That is something that has crossed my mind .
I've just compared the pinouts for the 4spd Lancer A/T to the Sonata SportTronic box, and they're almost identical. The only differences visible on the schematics are the wires for the sport shifter/selector and the dash lights.
I'm fairly certain that the sporttronic boxes could be run on the base Lancer A/T code, which opens up the possibility of using those RoadSpike bigmap A/T roms with all the Tephra Mods in them .
I also checked the reluctor cup on the exh cam the other day, and it's identical to the EDM Evos and 2G DSMs too .
I've just compared the pinouts for the 4spd Lancer A/T to the Sonata SportTronic box, and they're almost identical. The only differences visible on the schematics are the wires for the sport shifter/selector and the dash lights.
I'm fairly certain that the sporttronic boxes could be run on the base Lancer A/T code, which opens up the possibility of using those RoadSpike bigmap A/T roms with all the Tephra Mods in them .
I also checked the reluctor cup on the exh cam the other day, and it's identical to the EDM Evos and 2G DSMs too .
Last edited by Broke4speed; Apr 16, 2013 at 10:40 AM.
#562
Evolving Member
I apologize in advance as I'm sure the information is somewhere in this thread, however, I for the life of me, cannot find it here, or anywhere else.
Does anyone have the 1g MAF scaling? I have my conversion all ready to go, however, I'd like to work out any and all bugs using my factory MAF before swapping to my SD setup. I have 3 1g's and help troubleshoot many buddies 1g's, so being able to swap my ecu into a different 1g running the 1g maf still would make diagnosing much easier than trying to swap to either a 2g/evo maf just to troubleshoot.
Does anyone have the 1g MAF scaling? I have my conversion all ready to go, however, I'd like to work out any and all bugs using my factory MAF before swapping to my SD setup. I have 3 1g's and help troubleshoot many buddies 1g's, so being able to swap my ecu into a different 1g running the 1g maf still would make diagnosing much easier than trying to swap to either a 2g/evo maf just to troubleshoot.
Last edited by black_out; Jun 29, 2013 at 04:12 PM.
#563
Evolving Member
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Likes: 0
Received 0 Likes
on
0 Posts
MAF adder: 100 (you may have to add this to your xdf, it's at 1513h in the 9653 roms)
MAF size: 221.54
MAF comp:
91.00
91.00
89.00
89.00
96.00
101.00
108.00
110.00
110.00
111.00
115.00
118.00
122.00
129.00
130.00
132.00
135.00
133.00
127.00
122.00
127.00
Airflow/Hz/Baro and IAT comp table:
1.33 1.33 1.36 1.38
1.41 1.38 1.38 1.40
1.37 1.37 1.37 1.37
1.37 1.37 1.37 1.37
1.37 1.37 1.40 1.40
1.40 1.39 1.37 1.33
1.36 1.36 1.37 1.42
1.42 1.42 1.40 1.37
1.33 1.32 1.36 1.37
There is also the Closed Loop LT fuel trim switching table, but that's going to be based on the DSM code, so it's not really a direct swap over. The above tables are hardware-based, so they're the ones you need. There is no identified MAF smoothing table in the 1G hex, so run with the stock evo 8 one IMO. Can't hurt to see how it goes.
MAF size: 221.54
MAF comp:
91.00
91.00
89.00
89.00
96.00
101.00
108.00
110.00
110.00
111.00
115.00
118.00
122.00
129.00
130.00
132.00
135.00
133.00
127.00
122.00
127.00
Airflow/Hz/Baro and IAT comp table:
1.33 1.33 1.36 1.38
1.41 1.38 1.38 1.40
1.37 1.37 1.37 1.37
1.37 1.37 1.37 1.37
1.37 1.37 1.40 1.40
1.40 1.39 1.37 1.33
1.36 1.36 1.37 1.42
1.42 1.42 1.40 1.37
1.33 1.32 1.36 1.37
There is also the Closed Loop LT fuel trim switching table, but that's going to be based on the DSM code, so it's not really a direct swap over. The above tables are hardware-based, so they're the ones you need. There is no identified MAF smoothing table in the 1G hex, so run with the stock evo 8 one IMO. Can't hurt to see how it goes.
#564
Evolving Member
MAF adder: 100 (you may have to add this to your xdf, it's at 1513h in the 9653 roms)
MAF size: 221.54
MAF comp:
91.00
91.00
89.00
89.00
96.00
101.00
108.00
110.00
110.00
111.00
115.00
118.00
122.00
129.00
130.00
132.00
135.00
133.00
127.00
122.00
127.00
Airflow/Hz/Baro and IAT comp table:
1.33 1.33 1.36 1.38
1.41 1.38 1.38 1.40
1.37 1.37 1.37 1.37
1.37 1.37 1.37 1.37
1.37 1.37 1.40 1.40
1.40 1.39 1.37 1.33
1.36 1.36 1.37 1.42
1.42 1.42 1.40 1.37
1.33 1.32 1.36 1.37
There is also the Closed Loop LT fuel trim switching table, but that's going to be based on the DSM code, so it's not really a direct swap over. The above tables are hardware-based, so they're the ones you need. There is no identified MAF smoothing table in the 1G hex, so run with the stock evo 8 one IMO. Can't hurt to see how it goes.
MAF size: 221.54
MAF comp:
91.00
91.00
89.00
89.00
96.00
101.00
108.00
110.00
110.00
111.00
115.00
118.00
122.00
129.00
130.00
132.00
135.00
133.00
127.00
122.00
127.00
Airflow/Hz/Baro and IAT comp table:
1.33 1.33 1.36 1.38
1.41 1.38 1.38 1.40
1.37 1.37 1.37 1.37
1.37 1.37 1.37 1.37
1.37 1.37 1.40 1.40
1.40 1.39 1.37 1.33
1.36 1.36 1.37 1.42
1.42 1.42 1.40 1.37
1.33 1.32 1.36 1.37
There is also the Closed Loop LT fuel trim switching table, but that's going to be based on the DSM code, so it's not really a direct swap over. The above tables are hardware-based, so they're the ones you need. There is no identified MAF smoothing table in the 1G hex, so run with the stock evo 8 one IMO. Can't hurt to see how it goes.
Unfortunately I don't have a wideband right now (no funds), so until I am able to pick on up I'll be doing this old school. We'll see how it goes though! Thanks a ton
#565
Evolving Member
Join Date: Sep 2012
Location: Ottawa, Ontario, Canada
Posts: 181
Likes: 0
Received 0 Likes
on
0 Posts
Basically, you find the XML for the rom you're using (in this swap's case, it should be a 9653 variant), which will be in the 'rommetadata' folder in ECUFlash's directory. Then you insert this:
This will add a new map to the XML, called "MAF adder". Change that to 100 for a 1G MAF .
Code:
<table name="MAF Adder" category="Global Fuel Settings" address="1513" type="1D" scaling="uint8"/>
#567
I'm looking to do this with my 1g eclipse because I don't want to deal with dsm link and want an electronic boost controller, but I want to use an 9 ecu in stead for mivec (Kiggly has made a mivec head for a 1g, he is just waiting on releasing the exact procedures). I know the 9 uses a different model of ecu, would it be much more difficult to get it to run in my 1g?
Just want a quick sanity check before I throw 250 bucks at an ECU that might be too difficult to interface and/or tune.
Just want a quick sanity check before I throw 250 bucks at an ECU that might be too difficult to interface and/or tune.
#568
Evolving Member
I'm looking to do this with my 1g eclipse because I don't want to deal with dsm link and want an electronic boost controller, but I want to use an 9 ecu in stead for mivec (Kiggly has made a mivec head for a 1g, he is just waiting on releasing the exact procedures). I know the 9 uses a different model of ecu, would it be much more difficult to get it to run in my 1g?
Just want a quick sanity check before I throw 250 bucks at an ECU that might be too difficult to interface and/or tune.
Just want a quick sanity check before I throw 250 bucks at an ECU that might be too difficult to interface and/or tune.
Anyway, to make an Evo 9 ecu fit in a 1g, its the same procedure as doing an 8 ecu swap. Just a matter of making a different jumper harness.
#569
http://www.dsmtuners.com/forums/cyli...der-4g63s.html
The process works, Kiggly uses it on his own car and one other has the modification as well. It actually doesn't look like too bad of a modification, certainly less than adapting an evo 9 head to fit on a dsm block.
After looking through the thread it seems like just about all the sensors work for the 8 ecu save the knock sensor, just wanted to make sure mitsu didn't change too much between that and the 9.
The process works, Kiggly uses it on his own car and one other has the modification as well. It actually doesn't look like too bad of a modification, certainly less than adapting an evo 9 head to fit on a dsm block.
After looking through the thread it seems like just about all the sensors work for the 8 ecu save the knock sensor, just wanted to make sure mitsu didn't change too much between that and the 9.
Last edited by Nardokor; Jul 30, 2013 at 01:34 AM.
#570
Evolving Member
Can someone go over my ROM and make sure I didn't miss anything/mess anything up? I cannot get the car to start, verified there's no spark, haven't verified fuel yet, however, it seems as though no fuel either. My immobilizer SHOULD be deleted, however, I may be overlooking something since I've been ripping my hair out trying to figure it out. Maybe I missed something someone else will catch. This is in a bone stock GVR4, MAF should be scaled to 1g tables, injectors should be scaled to 450's.
I also cannot get it to log via evoscan AT ALL. I can read/write using ecuflash, but it will NOT connect to evoscan. I'm getting the wonderful j2534 code with my 2.0, and my 1.3u won't connect either. V2.7,2.8, and 2.9 all do the same thing, however, I can log perfectly fine on my 2g, but not on my galant. Pin 16 of my OBDII plug has 12v, 4/5 have ground, pin 7 is wired to pin 62 and the connection is good, but I can't verify communication through pin 7, my multimeter is in my toolbox at work.
Any help would be great. Wiring all appears to be good and ready, I've checked it over 20 times now. I have a feeling this ecu I bought is trash (it was pretty cheap for an evo ecu), but I don't understand why I'd still be able to read/write if it was.
I also cannot get it to log via evoscan AT ALL. I can read/write using ecuflash, but it will NOT connect to evoscan. I'm getting the wonderful j2534 code with my 2.0, and my 1.3u won't connect either. V2.7,2.8, and 2.9 all do the same thing, however, I can log perfectly fine on my 2g, but not on my galant. Pin 16 of my OBDII plug has 12v, 4/5 have ground, pin 7 is wired to pin 62 and the connection is good, but I can't verify communication through pin 7, my multimeter is in my toolbox at work.
Any help would be great. Wiring all appears to be good and ready, I've checked it over 20 times now. I have a feeling this ecu I bought is trash (it was pretty cheap for an evo ecu), but I don't understand why I'd still be able to read/write if it was.