The Central Hub for DSM Community and Information

For 1990-1999 Mitsubishi Eclipse, Eagle Talon, Plymouth Laser, and Galant VR-4 Owners. This is where the DSM platform history is documented and archived. Log in to help us in our mission, and to remove most ads from the browsing experience.

2g flashed ecu problem

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.

BelleauTsi

10+ Year Contributor
34
0
Feb 20, 2011
Val d'Or, QC, Canada
Hi,
I just begin to tune my car with ceddymod and h8 ecu flash. I scaled my injector put in the latency. Now when i start my car wideband is reading 10.0 extra rich so i made multiple flash playing with injector to try to bring my afr and trim back to normal. Nothing work car alway idle to 10-11 afr. I log o2 sensor and it never swing between 0.1-0.9 its stay near 0.1-0.3. I have verified wiring from ecu to front o2 sensor everything ok. Is it my o2 reading always lean that make ecu to run my engine rich? by the way 02 sensor feedback trim is at 25% all the time.
Thanks!
 
Post a log, are you still on the Evo 560s? What scaling and latencies are you using?
 
I should update my mod because i am now running 550 precision turbo injector
the log end up with me unhooking the o2 sensor
by the way precision turbo said that latency is 1.130 for that injector it look very high compare to other make
during this log wide band read 10.9 all the time
 
You're rich because you're in open loop, let your car get into closed loop and take another log.
the log end up with me unhooking the o2 sensor
What does this mean?

I'm having a very hard time finding any information for PTE 550s.
 
haha :) it mean that i unplug the o2 sensor to see the reaction, the last minute of log o2v read 0.039 it when i unplug
oh really? so what data should i look to see if its in closed loop?
sorry for my frenchy english ;)

you finish by find them where? what is yout latency?
 
Leave the O2 sensor plugged in. Let the car warm up until coolant temp is > 180* at that point your O2 sensor should start to cycle and your wideband should read 14.7:1-ish. You said you put latency at 1.130, for what voltage?
HOW TO: Adjust Injector Latency & Scaling for Larger Injectors - EvoXForums.com - Mitsubishi Lancer Evolution X Forums
I know that's not for a DSM, but the basic principles are the same. You still didn't say what scaling you're using, either.

Go ahead and post your scaling and all of your latencies, or your entire ROM.
 
Woah nice information nice!

1.130 is the spec that appear on the precision turbo website, they done give any voltage i assume it was 14v
Precision Turbo & Engine - Turbocharger, Intercooler, Fuel Injector, Performance Parts & more!
mine is 043-0540
someone tell me that 1.130 was total value. Is it possible that i have to add 1.130 to all stock value? some voltage setting come max out?
I have my injector scaling to 535 with all latency increase by 1.130ms and it run extra rich. So i reflash scaling to 510 to see if change anything, no change.
I dont have my rom on that computer i will post them tomorow. Other make of injector seem to got .300 or so of deadtime.
I will take a another log tomorow and tryget it in closed loop.
Thanks!
 
IF you lower your injector scaling you'll actually run even richer because the ECU thinks the injectors are smaller than they are, so it'll run up IDC/IPWs. Follow that guide for tuning, remembering you MUST be in closed loop operation to get fuel trims.

According to that listing the open/close time is the same as their 680s, and THOSE I can find information for:
3.312
2.184
1.416
0.960
0.696
0.480
0.360

Start with that and tune from there.
 
I should try those number directly? I dont add them to the stock one?
Oh yes i increase to 580 sorry :)
So if i understand right engine fully hot, o2 will start cycle and then im in closed loop, it is when low trim gonna start moving on?

Thanks for your nice info!
 
No, it's when your STFTs will start moving. Your LTFTs won't start cycling for a while, but STFT should be enough if it's stable. If you're actually running rich your O2 sensor won't cycle and your STFTs will drop to -12.5% attempting to lean it up a bit so you can't JUST watch the O2 sensor, but generally speaking once you're >180* coolant temp and you're idling/cruising you'll be in closed loop.

And use those values directly, I searched for you (you're welcome) and stole them from an Evo driver's thread. They are for the 680s, but should be close enough to get you started.
 
Last edited by a moderator:
Ah really :thumb:
I give it a try tomorrow morning for sure :hellyeah:
I will post back a new log tomorow
Thanks again Absit

I reflash with those number you found for me. :rolleyes:
It idle a lot better now reach 13.5 after warm up so sound like my latency were way too high. I try to make a closed loop log with o2 hooked but my o2 sensor keep display 0v even after engine fully warmed up. :aha: I resistance check all wiring, everything ok. I finally check terminal from connector for tightness. Signal terminal is loose :notgood:
I will be replacing them all tomorrow as i cant find those on Sunday and making new log if that works.
Another question, is it normal that evoscan display 5v for o2 sensor at startup?
Thanks taking your time to help me

log from this morning if someone can take a look?

Maybe it is normal those reading?
 
Last edited:
I went to my car to make some test and went it ran extra rich it smoke blue as hell. Rich condition is washing oil from my cylinder and burn?
 
I looked at your recent log but since we know your O2 sensor wasn't working it's pretty hard to test anything.

Most recent post did you get the O2 sensor working? What was your wideband saying?
 
No it wasnt working, i now think that o2 i dead i will replace terminal from connector today and make a order on that sensor. Blue smoke appear when wideband is 10.1-12.1
 
You may want to check your shaft play and compression while you're in there. Your fuel trims won't work and as such you can't tune your injectors/MAF until your O2 sensor is working.
 
I check and recheck all my wiring, heater circuit ok, replace 4 terminal, o2 still dont wanna show up voltage. So i ordered a new one
Yes good idea im gonna make a compression test and check turbo to be sure
Im gonna come back when my o2 is fix and log thanks
 
While you're waiting you may want to check continuity from the end of the O2 sensor wires to the ECU.
 
Yes that's what i did last night all wire perfect contuinity and have replaced terminal a that time. So this sensor is really wrong. I just got evoscan and cable so i never been logging, so it must be the root cause of my really poor gaz milage, this sensor was dying. Nice :thumb:
 
New sensor received and installed. Now it looks must more better 02 voltage is cycling and now i got the control of the afr. Idles after warm up is little bit lean 16 of afr it making idle rough. Did i need to adjust scaling or latency at idle for now cause if a follow ceddy how to, i should begin with WOT tuning by adjusting scaling. I take the car for a ride but there is no way to make WOT, afr is too much rich. I should make my WOT afr fit my wideband first?
Thanks! here a log with o2 cycling
 

Attachments

You must be registered for see attachments list
You should adjust for idle/cruise before you go WOT, doing it the other way around is a good way to break your car.

Like the EvoX forums state:
3. If trims are roughly the same, but positive, then you need to increase your global fueling, or in terms of ECUFlash, you need to lower your injector scaling number.
4. If both trims are roughly the same, but negative, then you need to descrease your global fueling, or in terms of ECUFlash, you need to raise your injector scaling number.
5. If idle trim is more positive than cruise trim, then you need to increase the dead time, or in terms of ECUFlash, you need to increase the latency value.
6. If the idle trim is less positive than the cruise trim, you need to decrease the deadtime, or in terms of ECUFlash, you need to decrease the latency value.

And log coolant temp, not coolant temp scaled. In fact, go through everything you're logging, you've got some weird and redundant stuff in there.
 
I don't have coolant temp in my list of input on evoscan. Do i need to add it?
I copy the xml from ceddy in the evoscan datasetting folder, like i should.
 
Ok thanks, that,s what i make. I just like to log more things that i need, does this slow down the logging process?

Wow make more tuning and now car pull as hard as never.
I put injector scaling at 535 and use latency that Absit found for me and remove 0.050 to all V. Now need some fine tuning but look very nice!
After little bit of searching i have been able to wire the 0-5v output of my Dynojet Wideband to signal wire of the rear oxygen sensor. With a formula that i found on evom. That is really awesome, its work perfectly. Now can log wideband :thumb:
So i decide to buy Ceddymod complet to encourage his really nice work!
And now finish messing with stupid af controller that make car run weird.
Thanks ceddy your change my life :hellyeah:
 
You should have used the xml file that Ceddy provided in the zip.

It's listed as "Coolant Temp Scaled."

My mistake, I'm not using the same XML, someone using his XML should probably give input then. Thing is, his temp showed 91* but his STFT was changing, that's why I thought it was wrong.
 
Add Value - Be Respectful - No Trolling - No Misinformation - Participate Often!
Support Vendors who Support the DSM Community

Build Thread Updates

Latest Classifieds

Back
Top