View Full Version : Evo IV problems (VII Ecu)
Ok Just got an Email and thought we could use it as test post/problem...
Email reads like this...
Hi Lee,
You've been pretty helpfull with stuff and are doing alot of mapping with ecuflash so I thought I'd ask you if you have a spare 5 mins to have a quick look at some logs for me.
A friend had a problem with said Evo IV. The CEL came on and the code was referring to fuel trim. He was cruising at the time in 5th at fast motorway speeds.
Anyway I offered to do some logs to see if anything showed up.
I have Attached the logs
The lambda voltage at idle seemed fine fluctuating from 0.2 to 0.9 volts.
The LTFT high was mostly sitting at 50 odd percent, I'm led to believe that it should be around 100. The AFR (wideband) at cruise sometimes would be OK (14.7afr) then other times would be sitting around 11 or 12 which is too rich for cruising. Also the car was very jerky when trying to cruise at more than 4500rpm.
When the afr's were reading 11 or 12's I noticed the lambda voltage was stuck at close to 0.9 volts whereas normally it would fluctuate about.
One thing I'm not sure of is when in closed loop at cruise where does the ECU get the fuel and timing targets from as I was led to believe the maps are not used in closed loop (idle and cruise). I may of course have got this totally wrong. I can email the rom if you like too.
Many thanks for your help in advance.
Cossie1
26-01-2009, 10:56 PM
Sounds like a problem with the lambda sensor being lazy and not switching fast enough.
Sounds like a problem with the lambda sensor being lazy and not switching fast enough.
That what i would have thought, just wanted to see what you said as you are the only one that is on at the min.
Lee
Cossie1
26-01-2009, 11:05 PM
I will take a look at the logs in a min, just replying to a couple of emails.
Cossie1
26-01-2009, 11:19 PM
Ok have looked at the logs.
I will stick with what I said, looks like a fubar lambda sensor to me.
Ok have looked at the logs.
I will stick with what I said, looks like a fubar lambda sensor to me.
Yep me to.
I thought it was a nice test post tho :D
Lee
Cossie1
26-01-2009, 11:33 PM
Yeh not bad, but a better one would have been:
"why haven't I fitted this evo 7 ecu into my 5 yet, as Russ was so kind and helpful in rushing to the post office to get it to me, so I could fit it the weekend before last" ;)
Yeh not bad, but a better one would have been:
"why haven't I fitted this evo 7 ecu into my 5 yet, as Russ was so kind and helpful in rushing to the post office to get it to me, so I could fit it the weekend before last" ;)
Errrrrrrrr, Been busy, is that any good ?????:o
Cossie1
26-01-2009, 11:51 PM
nope
YOU FAIL
nope
YOU FAIL
Ok Ok........
Tbh I had to remove all my old pipe work, refit the battery then find my maf that has the honeycomb missing from it, why its missing I don't have a clue:confused:
Then I needed to solder the maf wires up, fit a new induction pipe, clean the air filter, refit my SAS while everyone turns up at my gaff stopping me from working !!!!!!
Better???:lol:
Cossie1
27-01-2009, 12:03 AM
Nope, thats just excuss's.
Nope, thats just excuss's.
Phhhaaaaaaaa............
:eek:
Cossie1
27-01-2009, 12:25 AM
Phhhaaaaaaaa............
:eek:
Pikey
Cossie1
27-01-2009, 12:43 AM
:lol:
evonut270
27-01-2009, 08:22 PM
i think thats from GROVIT off the mlr.iv seen the lambda through out P0170 dtc before.he said he replaced the lambda back in october.
Grovit
27-01-2009, 08:37 PM
i think thats from GROVIT off the mlr.iv seen the lambda through out P0170 dtc before.he said he replaced the lambda back in october.
Yep - that's right.
Was doing some testing with the car over the weekend and was very much trying to keep up with the data being presented to me - got to be about the steepest learning curve I've gone through in a while and am still no where near comfortable with what I know so far. I have much to learn.
We're going to be fitting another lamda over the weekend to see what effect that has. As above, the new 4 wire lamda was only fitted in October '08 so am annoyed that it's lasted only this long, but hey ho.
Cheers for the help given chaps - as a first test post I feel quite chuffed to be the guniea pig :)
Ah, if I'd known it was going to be made public I wouldn't have been so complimentary Lee. ;) :D
Anyway, going to try a spare lambda I have at the weekend and will post results. :cool:
Ah, if I'd known it was going to be made public I wouldn't have been so complimentary Lee. ;) :D
Anyway, going to try a spare lambda I have at the weekend and will post results. :cool:
Hi Mate,
It was a test post just to make sure we could upload post etc, I didnt think it was going to stay up......lol
Hope you get it sorted :D
Lee
A related question:
His rom ID is 98640014, I think it's a JDM 7 ECU since it came from an imported RS.
Are there any tephra roms that will work with this. I have tried opening the rom with 90550001 in ecuflash but no tables are there to see.
Cheers,
Don
Cossie1
28-01-2009, 12:29 AM
A related question:
His rom ID is 98640014, I think it's a JDM 7 ECU since it came from an imported RS.
Are there any tephra roms that will work with this. I have tried opening the rom with 90550001 in ecuflash but no tables are there to see.
Cheers,
Don
90550001 is the only tephra modded E7 rom.
It is 100% compatable with a 98640014 car, as it's address's are all the same.
The reason nothing is showing is because you haven't added the tephra patch lines to your xml, they are included in the zip file I have posted.
90550001 is the only tephra modded E7 rom.
It is 100% compatable with a 98640014 car, as it's address's are all the same.
The reason nothing is showing is because you haven't added the tephra patch lines to your xml, they are included in the zip file I have posted.
Cool thanks for that I'll give it a bash. :D
Cossie1
28-01-2009, 12:33 AM
Cool thanks for that I'll give it a bash. :D
No probs mate
No probs mate
Just tried opening it with the 90550001 patched xml in Ecuflash V1.4 and no tables are present at all, just the rom info.
Did the same in version 1.29 and all the tables are there when using the 9055001 xml.
I can open the patched rom but just no tables in the rom from the car in version 1.4.
Wierd?!
Hi Don
I had a few gremlin with V1.4 and not showing maps etc so I use 1.38 and they all work fine in that.
I can email it over if you cant find it.
Lee
Cossie1
28-01-2009, 12:58 AM
Just tried opening it with the 90550001 patched xml in Ecuflash V1.4 and no tables are present at all, just the rom info.
Did the same in version 1.29 and all the tables are there when using the 9055001 xml.
I can open the patched rom but just no tables in the rom from the car in version 1.4.
Wierd?!
Try this 1
And make sure your status is set to developer in ecuflash options.
Hi Don
I had a few gremlin with V1.4 and not showing maps etc so I use 1.38 and they all work fine in that.
I can email it over if you cant find it.
Lee
Perfect, I don't have v1.38 as I went from 1.29 to 1.4. :rolleyes:
I like the graphs in 1.4 though. Does 1.38 have them?
email would be great.:D
Perfect, I don't have v1.38 as I went from 1.29 to 1.4. :rolleyes:
I like the graphs in 1.4 though. Does 1.38 have them?
email would be great.:D
Yep it has the graphs, I will email it now.....:cool:
Lee
Also the knock tables seem to be wrong, does this mean that they are in a different location in 98640014. Everything else seems perfect though.
Cossie1
28-01-2009, 01:05 AM
If your using my XML you need to use it in 1.30 or later.
It won't display the info correctly in pre 1.30
If your using my XML you need to use it in 1.30 or later.
It won't display the info correctly in pre 1.30
Bollocks I forgot about the endian. :lol:
Ok this is a bit starnge. It works now in V1.4 but I changed the endian from big to little when I thought it should have been the other way round as per text below.
And it works in V1.29 with the endian at big. :lol:
NOTES:
1) Change your ENDIAN just below, ECUFlash version 1.31 and higher = "big", 1.30 and lower = "little"
2) Remove/Rename your current "Boost Desired Engine Load" #2 and #3, only #1 matters anymore
3) Remove/Rename your current "Base Wastegate Duty" #2 and #3, only #1 matters anymore
4) Please test the features of this rom before driving off, if anything doesn't work as expected report back to Tephra.
Anyway it works so that is the main thing.
Only the knock multiplyer mid rpm that seems out now. it is "61" is this right?
Cossie1
28-01-2009, 01:28 AM
Bollocks I forgot about the endian. :lol:
Ok this is a bit starnge. It works now in V1.4 but I changed the endian from big to little when I thought it should have been the other way round as per text below.
And it works in V1.29 with the endian at big. :lol:
Anyway it works so that is the main thing.
Only the knock multiplyer mid rpm that seems out now. it is "61" is this right?
Have you left the old xml file you had, in the rommetadata folder somewhere ?
Or even renamed it as ecuflash looks into any file in there, and will mix and match multipul xml files if it feels like it.
As for the mid Knock muliplyer it should be 18
Have you left the old xml file you had, in the rommetadata folder somewhere ?
Or even renamed it as ecuflash looks into any file in there, and will mix and match multipul xml files if it feels like it.
As for the mid Knock muliplyer it should be 18
Nope just got the one 90550001 in both versions rommdata files. Not to worry it's working now. :D
I thought the mid multiplyer should be 18. Does that not mean that the location is wrong as I wouldn't have thought the multiplyer would be that high?
Cossie1
28-01-2009, 02:05 AM
Nope just got the one 90550001 in both versions rommdata files. Not to worry it's working now. :D
I thought the mid multiplyer should be 18. Does that not mean that the location is wrong as I wouldn't have thought the multiplyer would be that high?
It shouldn't be anywhere near that high.
Just double check that you haven't added the same table into your evo7base.xml incase it's seeing an incorrect address from there.
It should be looking at 24a8 and unit16
It shouldn't be anywhere near that high.
Just double check that you haven't added the same table into your evo7base.xml incase it's seeing an incorrect address from there.
It should be looking at 24a8 and unit16
It was referencing 24aa for some reason hence the incorrect figure. Changed it to 24a8 and it's now reading 18. :cool:
Cossie1
28-01-2009, 02:16 AM
It was referencing 24aa for some reason hence the incorrect figure. Changed it to 24a8 and it's now reading 18. :cool:
sorted :)
Grovit
28-01-2009, 08:40 PM
OMG - How much am I going to have to try and keep up this weekend:eek::D
Many thanks to D for helping with this and cheers to Cossie and Lee for helping D to help me. :D
Chris
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.