Evo 8 ECU In 2g Works!!

[the_mork]

That was the first thing i checked when i noticed the ac problem. Now if only i can figure out how to fix my initial startup problem with the 9653 rom, on cold startups its kind of a rough idle for a few seconds. It always idles kind of crappy at first to the point i have to give it some gas to get it going.

I had exactly the same problem. I do not have this problem with 9055 but my car feels much slower using this rom than the 9653, I'm not sure if it is just that I have been using stock maps and the 9055 is less aggressive or if there is something going on that I haven't found yet. I know that evo guys that switch to 9653 claim that they usually have some idle issues that are fixed by adjusting the BISS up a bit. I'm not sure if this will help for you but my car idles too high already with the BISS all the way in.

 

[mike96]

[/PHP][/HTML]well i have good news and bad news, the bad news is the car still idles to low with the AC on... so adjusting the idle didn't fix the problem. the good news is after applying the rear O2 heater patch and driving for two days i still have no CEL for the O2 heater, and i do not have the resistor mod done. so that works like a champ.

<table name="Rear O2 Heater Patch" category="Front/Rear_O2" address="2c61e" type="3D" level="1" scaling="Hex16">
    <table name="Code" type="Static X Axis" elements="1" scaling="Hex16">
        <data>Hex16</data>
    </table>
    <table name="Address" type="Static Y Axis" elements="8">
        <data>2c61e</data>
        <data>2c620</data>
        <data>2c622</data>
        <data>2c624</data>
        <data>2c626</data>
        <data>2c628</data>
        <data>2c62a</data>
        <data>2c62c</data>
    </table>
</table>

change all values to 0009.

 

[the_mork]

Edit your post and use the < html> tag.

<code></code>


Also have you considered that your ISC might just happen to be going out at the same time? My car idles fine with the AC on.

 

[mike96]

Edit your post and use the < html> tag.

<code></code>


Also have you considered that your ISC might just happen to be going out at the same time? My car idles fine with the AC on.

thanks mork... i hate html....i really do.

considering i just replaced it with a brand new one about 6 months ago, i really hope not.

but i did do some digging though the evo FSM and found there is a wire that the evo uses that the eclipse does not. pin 24 on the ECU, the wiring picture on page one shows it as AC Switch #2. there is an extra wire that runs from the AC ECU pin 5 to this pin on the engine ECU. according to the FSM the checks at the AC ECU are

pin 4 = Output to the ECM (A/C1)
A/C stopped 0 V,
A/C switch: ON, blower switch:ON vBattery positive voltage

pin 5 = Output to the ECM (A/C2)
When the A/C is under low load Battery positive voltage
When the A/C is under high load 0 V

so i think it is safe to say that i can apply 12v to pin 24 at the ECU to simulate a low load. i think i am going to add this in as a test to see while i am under the center console adding the inter-cooler wiring and lights and such this weekend. i also need to add in my alt map switch.

 

[johnnyboy55]

** did u try adjusting all the idles by the way?? there is like three maps i think try to adjust all of them and see.. Im sure it wont make a difference but i always adjust all of them..

 

[the_mork]

Mike96, another subject but did you have to do anything special to get your car running with the evo ecu? You should have the same inverted CAS as the 95s and I'm still trying to track down what is wrong with Roni-Wan's car. I thought I could help him and that it was a simple matter of moving around wires but his thread was pretty complete and it comes down to CAS inversion being the problem Perhaps an evo8 ecu would help him.

 

[mike96]

Mike96, another subject but did you have to do anything special to get your car running with the evo ecu? You should have the same inverted CAS as the 95s and I'm still trying to track down what is wrong with Roni-Wan's car. I thought I could help him and that it was a simple matter of moving around wires but his thread was pretty complete and it comes down to CAS inversion being the problem Perhaps an evo8 ecu would help him.

aside from inverting the firing order and injectors i didn't have to do anything special.

 

[mike96]

something that might help with us having issues with knock at 2500 - 3000 rpm

Knock between 2800 and 3000 - evolutionm.net

 

[_Madman_]

something that might help with us having issues with knock at 2500 - 3000 rpm

Knock between 2800 and 3000 - evolutionm.net

DON'T DO THAT! There is a good reason why the ECU sees knock. Injectors are firing all at the wrong times with the old CAS. And there is a physical vibration at this range at noticeable load.

[noob hat on]I even think that if there's a situation when injectors are firing while the exhaust valves are open, you can run extra lean, extra quick. But I might be completely wrong here.[/noob hat off]

Also, during some testing I managed to get the car running with no knock during one of the logs in troubled range, but the excessive vibration was still there. So tweaking the knock maps is not something I would recommend.

The linked thread that might or might not come of interest: http://www.dsmtuners.com/forums/tun...g-order-random-excessive-knock-vibration.html

 

[_Madman_]

Ok, I posted, then I decided to read the whole thread, I did it and...

Wholy moly batman, you guys do like to play with loaded guns, and with guns I mean .50 cal Desert Eagles baby!!!

1) Don't EVER copy something from one ROM definition to another!!! EVER!!!
I followed the discussion and only on page 15 I found something about periphery bits being at the same address on all Evo 8 ROMs.
CEL patches and stuff, I highly doubt, by highly I mean 99%.
Why I think so? Because I have an experimental definition for H8 ROMs on my hands, with 4 AFR maps and some timing maps, but they differ between ROMs. And what's more important, code entry point (the address at the very beginning of the ROMs) differ between versions as well. And if CEL removal is code patch (I guess all those more advanced patches like blinking CELs on knock and Valet modes are), then you are randomly replacing code with something which can cause ECU to reboot, divide amount of fuel by 17, kick the ABS ECU, stop the injector 1 or whatever.
Basically, there are chances that pistons will be sent flying... Through hood of course.
Before applying the patch, verify that it's compatible with the ROM you have! Don't ever copy parts of definitions from one ROM to another without research.
The guys at Evo forums have been using dis assemblers to check if stuff works and there is a good reason why there are incomplete definitions.
2) Problems with ROMs number xxx
Have you guys verified what are the ECU part numbers and if USDM/EDM/JDM EVO ECUs are the same? It would be nice to have problem description + ROM number + ECU part number.
If the ECUs differ the symptoms might be completely random. Also, (remember the 1st bullet point) randomly patched ROMs can do anything. Best way to go is to load ROM that was on your car and then patch the tables via definitions that are verified for that ECU.
If you resort to chemistry there is whole new can of worms that you are about to open.
3) How to use HEX editor to patch something
Download XVI32 ( Freeware Hex Editor XVI32 ) and you'll find it rather easy, but remember the 1st point, don't change random numbers, and more importantly don't say that it works, it might work for you and then go BOOM on some other car where load/RPM/air ratios differ.
4) Problem with car not shutting down / fuel pump switch
Have you verified that ECU clicks when you turn the power off. DSM ECUs do that, maybe the EVO ones do that as well?
5) GSXDNA post about H8 being flashable
This seems to be true, but you need the OpenPort 2.0 cable, and it has not been verified yet.
But there is also a bright side for you Evo ECU guys. Evo ECU has:
18x15 AFR maps vs 14x14 on H8 ECUs
20x19 Ignition maps vs 18x16 on H8 ECUs
The Evo load axis seems to end at 260 vs 180 on H8 ECUs
6) Flashing on Evo ECUs
Has anyone verified what is the flash limit on Evo ECUs? H8 is supposed to be limited to 100 flashes, can you flash Evo ECUs unlimited number of times?
7) Sticking the wire into the flash pin (79)
I would also warn you against that. H8 ECUs are toast if flash goes wrong, the same can happen with Evo ECUs I guess. If the wire gets loose during flashing, the Ecu might get bricked.
8) Evo 8/9 harnesses
I would guess Evo 9 ROM should work too, Power FC ECUs seem to be same for them, aren't they?
9) ECU renaming
If the ECU sends CPU or motherboard number then no go, if it sends ROM number, I guess you could just change it inside ROM. I don't know if it's legal, but it should be doable. ROM ID numbers should be well known, and, (should be proved with disassembly I guess) shouldn't be used throughout the code much.
10) The CAS and injector firing order
As I already said, I wouldn't recommend to run the car if there is that supposedly "phantom knock". There is something wrong with older CASes. And on my car it caused more problems if I swapped injectors the same way I swapped the plug wires. Maybe I messed something up, but it run worse than without swap. Remember that our cars fire both plugs on the same coil at the same time.
I haven't solved this problem with my car, I'll be back to investigation as soon as I get some free time.

That's all I wanted to comment, awesome job everyone!

But please, don't do random modifications to ROMs that are unproven!

 

[the_mork]

I appreciate your effort but on a number of these points you have missed some valuable information since this discussion in parts is actually also happening on the evolutionm ecuflash forum.

Ok, I posted, then I decided to read the whole thread, I did it and...

Wholy moly batman, you guys do like to play with loaded guns, and with guns I mean .50 cal Desert Eagles baby!!!

1) Don't EVER copy something from one ROM definition to another!!! EVER!!!
I followed the discussion and only on page 15 I found something about periphery bits being at the same address on all Evo 8 ROMs.
CEL patches and stuff, I highly doubt, by highly I mean 99%.
Why I think so? Because I have an experimental definition for H8 ROMs on my hands, with 4 AFR maps and some timing maps, but they differ between ROMs. And what's more important, code entry point (the address at the very beginning of the ROMs) differ between versions as well. And if CEL removal is code patch (I guess all those more advanced patches like blinking CELs on knock and Valet modes are), then you are randomly replacing code with something which can cause ECU to reboot, divide amount of fuel by 17, kick the ABS ECU, stop the injector 1 or whatever.
Basically, there are chances that pistons will be sent flying... Through hood of course.
Before applying the patch, verify that it's compatible with the ROM you have! Don't ever copy parts of definitions from one ROM to another without research.
The guys at Evo forums have been using dis assemblers to check if stuff works and there is a good reason why there are incomplete definitions.
Periphery bits are applicable across all evo7/8/9 roms. The NLTS, knock CEL, valet, etc are very different but we actually start with pre-patched roms that the cod is specific for. For instance if you want a Tephra-patched rom you must download the whole rom and the definitions for it and then move your maps onto it. We aren't doing this blindly.
2) Problems with ROMs number xxx
Have you guys verified what are the ECU part numbers and if USDM/EDM/JDM EVO ECUs are the same? It would be nice to have problem description + ROM number + ECU part number.
We are all AFAIK using a USDM computer and for the most part ECUs that came from 03s. All of these ECUs started with 9417xxxx ROMs on them. Some people might be running oddballs but so far problems and solutions have been universal.
If the ECUs differ the symptoms might be completely random. Also, (remember the 1st bullet point) randomly patched ROMs can do anything. Best way to go is to load ROM that was on your car and then patch the tables via definitions that are verified for that ECU.
If you resort to chemistry there is whole new can of worms that you are about to open.
This isn't an issue, switching roms is verified to work well and there is a movement to move the whole tuning populace to only a few universal roms to make it easier for developers.
3) How to use HEX editor to patch something
Download XVI32 ( Freeware Hex Editor XVI32 ) and you'll find it rather easy, but remember the 1st point, don't change random numbers, and more importantly don't say that it works, it might work for you and then go BOOM on some other car where load/RPM/air ratios differ.
If the definitions are wrong then the tables will look bonkers. It isn't foolproof but it works and we verify the addresses of of working definitions anyway.
4) Problem with car not shutting down / fuel pump switch
Have you verified that ECU clicks when you turn the power off. DSM ECUs do that, maybe the EVO ones do that as well?
This is just one persons problem. He messed with his wiring and I have no idea if it is fixed now. I'm sure he would appreciate your help if you have ideas but it isn't a universal evo ecu problem.
5) GSXDNA post about H8 being flashable
This seems to be true, but you need the OpenPort 2.0 cable, and it has not been verified yet.
But there is also a bright side for you Evo ECU guys. Evo ECU has:
18x15 AFR maps vs 14x14 on H8 ECUs
20x19 Ignition maps vs 18x16 on H8 ECUs
The Evo load axis seems to end at 260 vs 180 on H8 ECUs
I hope it is true and I don't know why no one has tried it yet. There must be someone who has access to an openport2.0 cable. As far as the load you can always rescale it for higher load.
6) Flashing on Evo ECUs
Has anyone verified what is the flash limit on Evo ECUs? H8 is supposed to be limited to 100 flashes, can you flash Evo ECUs unlimited number of times?
AFAIK this has never been a problem. I doubt that it is a problem on H8 computers either, more of a factory recommendation that they didn't want to test more than 100 writes. Who would have thought that anyone would flash the computer that much.
7) Sticking the wire into the flash pin (79)
I would also warn you against that. H8 ECUs are toast if flash goes wrong, the same can happen with Evo ECUs I guess. If the wire gets loose during flashing, the Ecu might get bricked.
The evo8 ECU is hard to brick. You just about have to be trying. My flash pin is connected with a pin but I just stuff it into the hole on the cable side. It doesn't even matter if it falls out, the ecu is already in the flash mode and works fine.
8) Evo 8/9 harnesses
I would guess Evo 9 ROM should work too, Power FC ECUs seem to be same for them, aren't they?
It might kind of work a little bit but the evo9 ecu has MIVEC which screws everything up and it is almost impossible to get pins for it except through Jack_of_Trades. It wouldn't be worth trying to tune it when we have a much closer match in the evo8 ECU. I forgot to add that the difference in pins is because of different connectors. I don't want to entirely replace the ends of my wiring harness because I WOULD mess something up and for what gain?
9) ECU renaming
If the ECU sends CPU or motherboard number then no go, if it sends ROM number, I guess you could just change it inside ROM. I don't know if it's legal, but it should be doable. ROM ID numbers should be well known, and, (should be proved with disassembly I guess) shouldn't be used throughout the code much.
10) The CAS and injector firing order
As I already said, I wouldn't recommend to run the car if there is that supposedly "phantom knock". There is something wrong with older CASes. And on my car it caused more problems if I swapped injectors the same way I swapped the plug wires. Maybe I messed something up, but it run worse than without swap. Remember that our cars fire both plugs on the same coil at the same time.
The 2gb CASs are similar to evo CASs. I also have no vibration. I'll be filling up with race gas when my tank gets near low to verify my phantom knock, otherwise I've been gently pushing through it. If I roll into a pull I don't get the knock. One thing that I've been considering is if it is a problem with our knock sensors. DSMs use an analog signal right up to the ADC at the ECU whereas Evo ECUs switch to digital right after the amplifier. I wonder how much of a difference there is between the systems that might cause us problems.
I haven't solved this problem with my car, I'll be back to investigation as soon as I get some free time.

That's all I wanted to comment, awesome job everyone!

But please, don't do random modifications to ROMs that are unproven!

Don't stop contributing just because you were missing some information. You have some very valuable insight into computer systems that I think can be very helpful and I think we are all pleased with more discussion, it is just that in this case we've already discussed some of those answers.

 

[delta448]

Agreed. Any input from someone with experience manipulating ECUs is greatly appreciated by everyone attempting this swap.

I was unaware of the differences in the knock sensors, mork. I havn't had much time to work on my knock issues lately, with starting a new job and all. If the knock doesn't disappear when you switch to race gas, a complete Evo knock sensor swap might be something for us to consider.

 

[_Madman_]

I appreciate your effort but on a number of these points you have missed some valuable information since this discussion in parts is actually also happening on the evolutionm ecuflash forum.

Oh, I see I guess I just read thought the thread too quickly, I will look up the EvolutionM thread as well, you have some very valuable information here, and since H8 ROMs are very similar to Evo ROMs it's good to know.

1) Don't EVER copy something from one ROM definition to another!!! EVER!!!
...
Periphery bits are applicable across all evo7/8/9 roms. The NLTS, knock CEL, valet, etc are very different but we actually start with pre-patched roms that the cod is specific for. For instance if you want a Tephra-patched rom you must download the whole rom and the definitions for it and then move your maps onto it. We aren't doing this blindly.
It's good then! All ROMs are available at EvolutionM forums, right?
2) Problems with ROMs number xxx
...
We are all AFAIK using a USDM computer and for the most part ECUs that came from 03s. All of these ECUs started with 9417xxxx ROMs on them. Some people might be running oddballs but so far problems and solutions have been universal.
So I would be better off with USDM ROM for experiments? Do you know the MDxxxxxx part number I should be best looking for?
...
This isn't an issue, switching roms is verified to work well and there is a movement to move the whole tuning populace to only a few universal roms to make it easier for developers.
But what about different CELs? They do differ if you flash to different ROMs as far as I understood, right?
5) GSXDNA post about H8 being flashable
...
I hope it is true and I don't know why no one has tried it yet. There must be someone who has access to an openport2.0 cable. As far as the load you can always rescale it for higher load.
As soon as I will finish my study stuff, I'll try to check that, as I know where I could borrow an OpenPort 2.0, but with studies and CAS issues, I had to forget about that for now.
Concerning rescaling, I think it might be pretty hard. Internally ECU uses some bit manipulation tricks that might just break if you'd modify the axis structures. And there is a huge amount of tables in those ROMs, all of them have to be verified in code for such modifications, and that is hard. You guys are luckier
8) Evo 8/9 harnesses
...
It might kind of work a little bit but the evo9 ecu has MIVEC which screws everything up and it is almost impossible to get pins for it except through Jack_of_Trades. It wouldn't be worth trying to tune it when we have a much closer match in the evo8 ECU. I forgot to add that the difference in pins is because of different connectors. I don't want to entirely replace the ends of my wiring harness because I WOULD mess something up and for what gain?
AFAIK, there are MIVEC tables in those ROMs, and the discussion seems to indicate that it should work in theory ( evolutionm.net - View Single Post - converting my 9 to an 8 (remove mivec) ). Of course, so far it's better to concentrate on single ECU, but if EVO8 ECUs will become rare, that's an option. Or maybe someone will make a MIVEC DSM cams
10) The CAS and injector firing order
...
The 2gb CASs are similar to evo CASs. I also have no vibration. I'll be filling up with race gas when my tank gets near low to verify my phantom knock, otherwise I've been gently pushing through it. If I roll into a pull I don't get the knock. One thing that I've been considering is if it is a problem with our knock sensors. DSMs use an analog signal right up to the ADC at the ECU whereas Evo ECUs switch to digital right after the amplifier. I wonder how much of a difference there is between the systems that might cause us problems.
Well, switch to a race gas is only curing the symptoms, there is some incompatibility. Moving ADC closer to knock sensor (microphone) can decrease the interference and extra noise picked out, but it could be that Evo engines just sound different.
Another idea is that maybe we could use H8 knock filter maps with Evo ECUs, we just have to figure out which ones are which.

EDIT: Also, someone mentioned something about messed fan pins. You can use EvoScan actuators to check if things work. That should be easier, and that way you can check everything right after the ECU is swapped while still standing in your garage. There is also a FP, wastegate and some other actuators there.

 

[the_mork]

This is a good discussion. I'm pleased to try and get all of this information out into the open and clearly stated.





Oh, I see I guess I just read thought the thread too quickly, I will look up the EvolutionM thread as well, you have some very valuable information here, and since H8 ROMs are very similar to Evo ROMs it's good to know.
There isn't one single evolutionm thread, there are bits of information scattered everywhere, unfortunately we don't have a clean repository for all the information but hopefully this discussion will help.

1) Don't EVER copy something from one ROM definition to another!!! EVER!!!
...
Periphery bits are applicable across all evo7/8/9 roms. The NLTS, knock CEL, valet, etc are very different but we actually start with pre-patched roms that the cod is specific for. For instance if you want a Tephra-patched rom you must download the whole rom and the definitions for it and then move your maps onto it. We aren't doing this blindly.
It's good then! All ROMs are available at EvolutionM forums, right?More or less, stock roms seem to be harder to find but they are definitely out there. The patched roms from Tephra are available at evolutionm in the threads labeled as Tephra mod X.xx or something like that. 5.10 is the current stable version but version 7 should be out any time now and is considered to be stable.
2) Problems with ROMs number xxx
...
We are all AFAIK using a USDM computer and for the most part ECUs that came from 03s. All of these ECUs started with 9417xxxx ROMs on them. Some people might be running oddballs but so far problems and solutions have been universal.
So I would be better off with USDM ROM for experiments? Do you know the MDxxxxxx part number I should be best looking for?
That is what we are using mostly but I actually expect that the ECUs are very similar internally. The problem with the different CELs is that the cars are actually physically different from one market to another. AFAIK it really is just a matter of having the right rom for your setup because each computer can handle input/output from each pin according to its type and the input types are the same across the EDM/USDM/AUDM computers. One of the most common ROMs we use is 96530006 which IIRC is an EDM rom.
...
This isn't an issue, switching roms is verified to work well and there is a movement to move the whole tuning populace to only a few universal roms to make it easier for developers.
But what about different CELs? They do differ if you flash to different ROMs as far as I understood, right?
AFAIK everyone has had the same experience with every rom. I would be curious with your unique CAS issue if you could run a USDM rom that we have trouble with because of CAS and crank sensor issues.
5) GSXDNA post about H8 being flashable
...
I hope it is true and I don't know why no one has tried it yet. There must be someone who has access to an openport2.0 cable. As far as the load you can always rescale it for higher load.
As soon as I will finish my study stuff, I'll try to check that, as I know where I could borrow an OpenPort 2.0, but with studies and CAS issues, I had to forget about that for now.
Concerning rescaling, I think it might be pretty hard. Internally ECU uses some bit manipulation tricks that might just break if you'd modify the axis structures. And there is a huge amount of tables in those ROMs, all of them have to be verified in code for such modifications, and that is hard. You guys are luckier
Someone burning chips has to have come up with a way to handle this, porting might not be cake but it is hopefully easier than starting from scratch. Also you can always enforce your own rationality on the ECU, big turbo and stroker evos that move to SD just change the behavior of the ECU in determining load and mess with the injector scaling and fuel maps to make it come out right. You don't necessarily need to make load become a bigger number to handle more flow.
8) Evo 8/9 harnesses
...
It might kind of work a little bit but the evo9 ecu has MIVEC which screws everything up and it is almost impossible to get pins for it except through Jack_of_Trades. It wouldn't be worth trying to tune it when we have a much closer match in the evo8 ECU. I forgot to add that the difference in pins is because of different connectors. I don't want to entirely replace the ends of my wiring harness because I WOULD mess something up and for what gain?
AFAIK, there are MIVEC tables in those ROMs, and the discussion seems to indicate that it should work in theory ( evolutionm.net - View Single Post - converting my 9 to an 8 (remove mivec) ). Of course, so far it's better to concentrate on single ECU, but if EVO8 ECUs will become rare, that's an option. Or maybe someone will make a MIVEC DSM cams
Interesting, but I'm not sure it is worth pursuing at this time, as I said before the connectors are different.
10) The CAS and injector firing order
...
The 2gb CASs are similar to evo CASs. I also have no vibration. I'll be filling up with race gas when my tank gets near low to verify my phantom knock, otherwise I've been gently pushing through it. If I roll into a pull I don't get the knock. One thing that I've been considering is if it is a problem with our knock sensors. DSMs use an analog signal right up to the ADC at the ECU whereas Evo ECUs switch to digital right after the amplifier. I wonder how much of a difference there is between the systems that might cause us problems.
Well, switch to a race gas is only curing the symptoms, there is some incompatibility. Moving ADC closer to knock sensor (microphone) can decrease the interference and extra noise picked out, but it could be that Evo engines just sound different.
Another idea is that maybe we could use H8 knock filter maps with Evo ECUs, we just have to figure out which ones are which.
I'm not curing the symptoms, I'm verifying that it really is phantom knock. At that point I can edit the knock control tables to bring the knock floor up just a touch. Real knock should still show while phantom knock will be ignored. It is delicate work but done right shouldn't compromise safety. IMO it is much safer than putting a soft washer on the knock sensor. If that doesn't work well then we may have to try some more drastic hardware fixes.

EDIT: Also, someone mentioned something about messed fan pins. You can use EvoScan actuators to check if things work. That should be easier, and that way you can check everything right after the ECU is swapped while still standing in your garage. There is also a FP, wastegate and some other actuators there.

 

[Gamble97]

Can evoflash/evoscan support a gm maf and a 3.3bar sensor?

 

[the_mork]

It can support nearly any MAP sensor. I am personally using a GM MAP sensor and it is working beautifully through the stock MDP harness. With the right scaling and sizing I imagine you could make a GM MAF work if you hacked up the wiring but why would you want to? The evo ecu supports SD and you already have a MAP sensor, all you would need is a IAT sensor and a couple hours to dial the setup in.

 

[mike96]

Can evoflash/evoscan support a gm maf and a 3.3bar sensor?

with the GM MAP like mork said ... yes with some re scaling.

with the GM MAF .... i will say No, not yet anyway. i don't believe anyone is working on figuring that out. not with speed density on the horizon. reason being is that if you get on full throttle's net work and look into the GM translator, the GM sensor works a little different in how it works and the computer doesn't need to compensate for air temperature and baro, the sensor does that in how it works, thats why the MAFT has a pair of wires that you hook up to supply a fixed voltage to the stock ECU to simulate those sensors. i have messed around with a rom a little just to see what i can do with MAF Hz settings and i have figured out how to change the scaling (it isn't easy). and the factory ecu tops out about 3066 Hz where the GM sensor puts out that value almost at idle the frequency range of the GM sensor is almost 100X that of the Mistu sensor.

 

[the_mork]

with the GM MAP like mork said ... yes with some re scaling.

Just to expound on this a bit, with a non-usdm rom such as 90550001 or 96530006 all that you need to do is alter the entry in evoscan just a touch and check the box. With a USDM rom you need to apply a patch from MRFred which is simple enough then alter the entry in evoscan and check the box.

 

[Gamble97]

Will this work with all 95-99 2g cars?

 

[bling5tatus]

^^and you're a wiseman...

If you can plug it into the harness it will work. That's the point, the harnesses are the same. I could use a honda ecu on my gst if I wanted with a custom harness.

 

[_Madman_]

^^and you're a wiseman...

If you can plug it into the harness it will work. That's the point, the harnesses are the same. I could use a honda ecu on my gst if I wanted with a custom harness.

No, he has a point, CAS issues are still troubling for 95/96 cars. So you can only say it will definitely work on 97-99 cars now.

 

[the_mork]

Mike96 is running one on a 96.

 

[GSXDNA]

i had the same problem... try this.

evolutionm.net - View Single Post - 96530006 can't logg trims

change it to 7deg C

So I changed it from 70 to 7, and I'm still throwing the same "excessive time to enter closed loop" code. Any other ideas?

Additionally, if my car has been sitting for 6-8 hours, and I go to start it, it starts fine. However, if it has been sitting for more than 10-12 hours, I have to turn it over 8-10 times before it will start.

 

[Gamble97]

^^and you're a wiseman...

If you can plug it into the harness it will work. That's the point, the harnesses are the same. I could use a honda ecu on my gst if I wanted with a custom harness.

Yes because these is soooo much information on this

No, he has a point, CAS issues are still troubling for 95/96 cars. So you can only say it will definitely work on 97-99 cars now.

This is exactly what I was trying to figure out. So maybe if we turn the cas 180* on the 95/96? But I think that may still mess with the injectors. On dsmlink selecting inverting the case does that AND I believe it also switches the firing between cylinder 3 and 4.

 

[mike96]

:

So I changed it from 70 to 7, and I'm still throwing the same "excessive time to enter closed loop" code. Any other ideas?

Additionally, if my car has been sitting for 6-8 hours, and I go to start it, it starts fine. However, if it has been sitting for more than 10-12 hours, I have to turn it over 8-10 times before it will start.

may be try changing it to 0 or 1, only problem is that you will go into closed loop almost instentantly... not that you aren't going into closed loop fast enough already... could be a CTS going bad or a pour connection at the CTS. have you ever gotten a CEL for CTS p0115 i think?

Yes because these is soooo much information on this



This is exactly what I was trying to figure out. So maybe if we turn the cas 180* on the 95/96? But I think that may still mess with the injectors. On dsmlink selecting inverting the case does that AND I believe it also switches the firing between cylinder 3 and 4.

actually with the right amount of work you probably could use a Honda ECU in an eclipse the connectors are the same but i don't think i would want to deal with the nightmare of having to change all the pins around at the ecu, not to mention the different Cam/Crank sensors.... may be only if i were going to put a gt in a honda....... think out side the box right?

as far as the CAS is conserned... not exactly. i am running an evo8 ecu in a 96 so yes it will work, you just need to switch the pins at the ecu for the injectors and coils, not a big deal. i am working on something to try to get the CAS correct on the eclipse... right now it looks like the CAS pickup wheel is a bit different on the evo. i have seen two different pictures of an EVO cas and both were different (may be a difference dependent on year???) but i am working on it i just don't have the time right now to press forward with it, that and my car is down for the count right now. i did some wire harness re routing/shortening and apparently i cant solder for s#!t....5 bad solder joints can cause a lot of issues.