ECMlink Interesting ECMlink issue

[Deadspool]

TL;DR

Once in a while, frequently but randomly, the ecu will stop logging CombinedFT and stick the afr to 14.7.

However, the real afr goes so lean it pops a misfire cell, 18-20:1 kind of lean. Undriveable.

If i turn the car off, and start it again, the problem goes away. Sometimes for a few days, sometimes just a few mins.

During "normal" operation, the ecu runs lean, no matter what i do. Fuel sliders, VE, dead time, nothing. Drives smooth, just pretty lean. 15-16:1

Fuel pressure is dandy, no boost leaks.

Thoughts?

 

[gofer]

First rule when posting in the log file advice forum, attach a log.

...then we can help.

 

[Deadspool]

I have not been lucky enough to be logging or have the laptop on me when the problem arises. I do not daily this car right now.

Even if the opinions are hypothetical, Good enough for me.[DOUBLEPOST=1413225643][/DOUBLEPOST]And for the record, I went through this thread already: http://www.dsmtuners.com/threads/please-read-before-you-ask-for-ecmlink-dsmlink-log-advice.443297/


And verified everything.

It -seems- like either a grounding issue, or the ECU is hurt.

 

[jim95redgsx]

TL;DR

Once in a while, frequently but randomly, the ecu will stop logging CombinedFT and stick the afr to 14.7.

However, the real afr goes so lean it pops a misfire cell, 18-20:1 kind of lean. Undriveable.

If i turn the car off, and start it again, the problem goes away. Sometimes for a few days, sometimes just a few mins.

During "normal" operation, the ecu runs lean, no matter what i do. Fuel sliders, VE, dead time, nothing. Drives smooth, just pretty lean. 15-16:1

Fuel pressure is dandy, no boost leaks.

Thoughts?

It sounds like your problem is being caused by the misfire CEL, not the other way around. When the ECU detects misfire, it will disable an injector, making the car undriveable. Turning the car off will reset the ECU until it completes another 300 second, closed loop, highway cruise drive cycle. Disabling the injector will cause a very lean reading on a wideband. Are you using a 1G CAS? Try unchecking "cylinder misfire" on the DTCs tab.

http://www.dsmtuners.com/threads/po300-code-like-clockwork.481913/#post-153445000

Jim

 

[Deadspool]

Interesting. I am indeed using a 1g CAS.

I will disable the code and report back later on.

Thank you Jim.

 

[gofer]

TL;DR

Once in a while, frequently but randomly, the ecu will stop logging CombinedFT and stick the afr to 14.7.

However, the real afr goes so lean it pops a misfire cell, 18-20:1 kind of lean. Undriveable.

I have not been lucky enough to be logging or have the laptop on me when the problem arises. I do not daily this car right now.

Your first post mentions the CombinedFT will stop logging, inferring that you were logging or at least had a laptop connected when the problem occurred.

 

[bmxfelon420]

My personal suggestion based on my experience with this problem is to just undo the crank sensor portion of your wiring and hook the crank sensor back up, if you have a 7 bolt and the capability to do so. It will work with misfire detection disabled but I still feel like my car runs better with the crank sensor hooked up rather than using the cam sensor for that. At least with a 2g ECU.

 

[Deadspool]

Your first post mentions the CombinedFT will stop logging, inferring that you were logging or at least had a laptop connected when the problem occurred.

I said, either having the laptop on me, or running a log.

And i mentioned when this happens, it goes away after restarting. The happens when im in traffic with no exits nearly every time forcing me to cycle the ignition just to get off the road. The last time it happened my GF had the laptop on her, and was watching live data feed without logging.

Again, happened in heavy traffic, instructing her on how to start a log while decellerating due to misfires and a ton of road ragers was the last thing on my brain.

I dont have any logs or i would have posted them.

Can you do me a favor and pin off the condencending attitude in your first reply, followed by a third degree. It looks bad coming from a site moderator.

This is a technical forum, not a talk show.[DOUBLEPOST=1413255211][/DOUBLEPOST]

My personal suggestion based on my experience with this problem is to just undo the crank sensor portion of your wiring and hook the crank sensor back up, if you have a 7 bolt and the capability to do so. It will work with misfire detection disabled but I still feel like my car runs better with the crank sensor hooked up rather than using the cam sensor for that. At least with a 2g ECU.

Unfortunately ill have to get by with turning off the dtc code. It is 6 bolt swapped.

Thanks though!

 

[gofer]

No problem. Since this is the log file advice forum I'll just move it to the appropriate forum since you've got no log, sorry for asking for a log file so I (we) could help.

 

[Deadspool]

I can appreciate that i made a mistake posting in the wrong sub section. Thank you for trying.

Jim probably nailed it anyway.

 

[gofer]

Jim's correct. Usually a random misfire DTC can be attributed to a 1g/2gb CAS on a '95 ECU and the easy fix is disabling thing misfire detection DTC. I checked his post as the "best answer" for the thread that way it pushes to the top.

If it doesn't fix the problem try capturing a log of it and attaching it.

 

[Deadspool]

Thanks!

Yeah. Next time I go for a run in it, im just going to set capture everywhere i go.

Tomorrow I may disable the dtc and take it to work. That's a 40 min highway trip.