jeff24680
10+ Year Contributor
- 223
- 6
- Jun 2, 2008
-
Allen Park,
Michigan
You're logging Injector pulsewidth, and have it listed before IDC right? With calculated items, anything it uses in the calculation MUST be before it (and enabled).
Correct.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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.
This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
You're logging Injector pulsewidth, and have it listed before IDC right? With calculated items, anything it uses in the calculation MUST be before it (and enabled).
What exactly should the Baro reading be doing? Depending on which scaling I used on my injectors I can get the reading to cycle, or hold rock steady. I'm assuming we want it to be cycling?
My Baro readings are in the 95-96 range most of the time.
One question GSXEclipsePSI I noticed your boost cut delay timer is set to 1000 where mine is 1638375, I was under the impression you need to set it to its max possible value?
Trims disabled if one true:
Throttle position too high (varies by RPM)
Airflow too low (units are tricky, but it's very low)
Coolant temp < 51F
Coolant temp > 228F
The O2 sensor did not switch around 0.5v for over 128 seconds while running in closed loop mode. In that case, the ECU locks itself in open loop mode.
You must be logged in to view this image or video.

I decided since I was wiring a bunch of stuff (Fuel Pump, Sub and Meth) I would fix my wideband wire to go under my carpet and to make the serial cable for the datalogger to see if that stops my trims from not updating.
I'm just waiting for the rest of the parts to finish, then I will up date if it have any luck. My rear o2 sensor is now completely unplugged from the ECU no WB input.
jeff24680 & Kiddsm95What is the revision of your ECU before you flashed it?
Does anyone know which way (pos+/neg-) to compensate the latency values in order to increase the O2Sensor values? Right now my O2Sensor has a very low output of 0.01952V, but sometimes it will peak at 0.56608V...This is even with using the latency values Ceddy provided for the Evo 5/6 above. Ceddy mentioned that the O2Sensor voltage should cycle from 0.1V to 0.9V every second, so I'm wondering if another way to get the fuel trims to read is to bias the latency values such that the O2Sensor operates in the 0.1V-0.9V range.
I'm not going to get a CEL light now am I its not connected. Now with the meth I'm hoping to get this 6152 pushing good boost 27-32psi. Will my maps be fine, or do you have to rescale them. I forget the LOAD max right now as I'm on my desktop but if you could send me one with a higher scaling cause I still don't understand how to move stuff over in ecuflash. I watched the ecuflash video's from recompile on the evo forums.
I know you can take out some rows in the under 100 load.
People having issues with the Fuel Trims not updating.
* People who had this issue please keep me posted of your results with new setting. Such as CELs, etc.
Does anyone know which way (pos+/neg-) to compensate the latency values in order to increase the O2Sensor values?


Interesting...The only difference between our periphery bits are as follows.
bit 04 & 05 (P0300): Mine were off, you have them on. Description says set them to zero.
bit 02 (P0133, P0159): Mine were on, you have them off.
bit 01 (P0421): Mine on, you have them off.
I've adjusted mine so that they match yours. Will report the outcome shortly.
Not sure if this is an issue but I still have my rear O2 plugged into my exhaust and my ECU. I have my WB welded just past the flex section on the DP.
Just an FYI

Here are my settings. I have a lot of things disconnected.