PDA

View Full Version : Engine Cutting Out



srgould41
10-17-2021, 09:51 PM
Hi all,

Trying to troubleshoot an issue before shot gunning parts. The question isn't the TBI, per say, but related. I'm happy to repost in a different forum if needed.

I have a 1990 Police 5.7 in an FJ40 trail vehicle. This year it has only been out of the garage twice. A year ago I posted about the engine stalling. I had thought it was an injector issue, but after lots of hunting I determined it was a wiring issue. The 4 wire plug that plugs into the distributor ICM was missing insulation and the bare wires were corroded. The high resistance led to lots of voltage drop and the return sense wire was not making a connection at all triggering a fault code. I replaced the wire harness and it drove great afterward with no more fault code for the sense signal. I have only driven it maybe four or fine days since.

Yesterday I went on a four wheeling trip. The whole trip the check engine light kept coming on and going off without performance degradation. I connected Tuner Pro today and the fault code is for a low coolant temp. I don't believe this is related to my current problem, but does need to be solved. While monitoring with Tuner Pro today the temp seemed fine so I am guessing it's intermittent, either a failing sensor or bad wire.

Now to the larger problem, while driving home the engine lost power several times for a few seconds and puffs of black smoke came out the exhaust. The worst one was for several seconds, but the engine came back on as I was drifting onto the shoulder. It happened a total of 6 times in the two hour drive before I got home.

First question just to make sure, a low coolant temp error would not cause the engine to cut out, right? Seems ignition related to me.

My thought on the engine cutting out issue is related to my previous distributor wiring issue. I suspect the low voltage/high resistance may have degraded the ICM.

What are your thoughts and suggestions?

Thanks

tayto
10-18-2021, 01:13 AM
Was it a code 15? do you have a known good coolant temp gauge to confirm the engine was up to operating temp? sounds like the CTS is bad or there is some wiring fault on that circuit. datalogging should tell you if that sensor is doing its job or not. i have seen sensors fail and cause the vehicle to run very rich, because it thinks the coolant temp is cold.

srgould41
10-18-2021, 02:18 PM
Yes, code 15. I do have a temp gauge and it was reading normal. I am going to test the wires, end to end, before replacing the CTS. I ordered a replacement ICM, just to be safe. My spare is pretty old and I would not trust it for more than getting off a trail.

NomakeWan
10-18-2021, 04:29 PM
The temp gauge is driven by a different sensor than the one the ECM/PCM uses, so the dash gauge working doesn't mean the ECM is getting the proper temp. In fact, the Code 15 blatantly states that it is not receiving any signal whatsoever from the CTS, and has gone into a fallback mode. I'm not certain about the L98, but if it's anything like the later LT1, the fallback mode for complete CTS failure is...sadly, nothing other than throwing the code and, on an automatic, applying the TCC early. You should find the FSM for your '90 5.7 (L98?) and check the diagnostic page for DTC 15 to be sure. I only have the 1994-1995 5.7 (LT1) FSM, so that's all I can go by. But if in 1994-1995 the only thing that happens is throwing a code and applying TCC early, I would assume 1990 would be exactly the same. Doesn't make sense for GM to do something more advanced on a far more primitive computer system.

However, you are correct that a failed-low-temp CTS should not cause the engine to not run at all. It will cause it to run pig rich, and will cause it to never enter closed loop operation, but it should still run. If it does not run, something else is going on.

I agree that a total cutout sounds like ignition. Check all connections between distributor, coil, ICM, and ECM thoroughly. Again, the FSM can actually help you with the kinds of readings you can get with your multimeter to check each of these components. Or you could just throw parts at it, like replacing the ICM. But 100% start with the wiring since you already know that was a problem before. And if that CTS is any indication, it sounds like your wiring in general is suspect. Perhaps a rodent decided to have a snack. Best of luck.

srgould41
10-18-2021, 04:59 PM
Thanks for the reply. True that I have two temp sensors, one for the ECM and one that runs the gauge and electric cooling fan. Part of the problems I have been solving come from using a donor harness. It was in fairly good shape overall, but did have some issues such as the bare wires on the ICM plug. I plan to spend some time this week checking wires and voltages again and doing some data logging to see if I can see the intermittent temp failure. Glad to know the CTS would not cause the stalls. Didn't think so, but it's nice for validation.

JimCT_9C1
10-18-2021, 06:43 PM
Sharing my experience with bad coolant temp sensor (CTS) on my 95 LT1 -
My CTS failed low (constant, not intermittent), but not failed to the point that a code was set.
Flooded out the engine - wouldn't run when warm. Could start it with flood clearing mode (throttle to floor, no fuel) but would flood out after running a few seconds. Pulled the CTS connector to cause a hard failure. Started and ran well enough with code set and no CTS to get me home.

Testing without the sensor in play (and thus wiring as well) may help narrow things down.
Note my experience was with LT1, so others can chime in on any differences to your application.

Hope this helps -
Jim

NomakeWan
10-18-2021, 11:00 PM
To add to the above, Code 15 is triggered (at least on the 94~95 LT1) when the ECM detects CTS at -40F or lower for 2 seconds. On this application, that means CTS circuit at 100700 ohms or more (open circuit) for 2 seconds.

So if you're triggering Code 15, that means your CTS is intermittently reading essentially disconnected for 2 seconds or more. However, as Jim pointed out, it would be good to know what "temperature" is being reported for those times when Code 15 is not triggered as well. My bet is that it will read normal until Code 15 events happen, because the culprit is poor wiring causing a complete signal dropout.

srgould41
10-18-2021, 11:33 PM
Thanks for the info Jim. I had black smoke coming out the exhaust when the engine lost power. The black smoke could be the ignition cutting out or a super rich condition. I would not think that the intermittent CTS would cause what I was experiencing, but thinking of your failure experience I am not so sure now. However, I was getting the intermittent check engine light all day without runability issues, so... Hmmm.

I recorded the CTS plug positions at the ECU so I can run a continuity test while wiggling the wires today after work. I have a new plug I could wire in if the wires at the plug are faulty. If the wires seem good a new CTS is cheap.


Sharing my experience with bad coolant temp sensor (CTS) on my 95 LT1 -
My CTS failed low (constant, not intermittent), but not failed to the point that a code was set.
Flooded out the engine - wouldn't run when warm. Could start it with flood clearing mode (throttle to floor, no fuel) but would flood out after running a few seconds. Pulled the CTS connector to cause a hard failure. Started and ran well enough with code set and no CTS to get me home.

Testing without the sensor in play (and thus wiring as well) may help narrow things down.
Note my experience was with LT1, so others can chime in on any differences to your application.

Hope this helps -
Jim

tayto
10-19-2021, 01:26 AM
sounds like you don't have equipment to data log? if not try to jumper the terminals of the CTS together. start engine, within ~30 seconds you should get a code 14. If you do, the wiring to ecu should be ok and the sensor is most likely at fault.

TBI codes explained with troubleshooting flow charts:
http://www.gearhead-efi.com/gearhead-efi/doc/TBIcodes.pdf

srgould41
10-19-2021, 01:51 AM
Hmmm. I like that idea as an extra troubleshooting step. I do have data logging capability as well as chip burning. I will try the idea you suggested though. Seems worth a shot just to prove I am getting what I expect. I'll probably try both open and closed to trigger each error.

On a positive note, I guess, I just finished testing the wires. I could not detect any issues in either the CTS or ICM wires. Wiggled like crazy everywhere I could and no change in continuity. Ordered a new CTS. ICM should be here Thursday. Ordered both the D1943A and the Police version D1984A. The D1943A will go in my onboard spares bin.


sounds like you don't have equipment to data log? if not try to jumper the terminals of the CTS together. start engine, within ~30 seconds you should get a code 14. If you do, the wiring to ecu should be ok and the sensor is most likely at fault.

TBI codes explained with troubleshooting flow charts:
http://www.gearhead-efi.com/gearhead-efi/doc/TBIcodes.pdf

tayto
10-19-2021, 06:55 AM
D1984A is the "369" module
D1945A is the "048" module

369 is the one to get. apparently gm discontinued the 048, so i've always wonder if both Delco numbers are the same module but never had the time to check with a timing light.

if you datalog just follow the troubleshooting flow chart in the pdf. my method is if you only have a paper clip in your tool box...

EDIT: aside from regular tune up items, I usually consider the CTS part of a "tune up" item for TBI. usually for my own vehicle or if someone brings me something that has been neglected or not running right. Also consider the same for the O2 sensor, I usually upgrade to a heated O2 at this time.

srgould41
10-19-2021, 02:06 PM
Thank you for the info.


D1984A is the "395" module
D1945A is the "048" module

395 is the one to get. apparently gm discontinued the 048, so i've always wonder if both Delco numbers are the same module but never had the time to check with a timing light.

if you datalog just follow the troubleshooting flow chart in the pdf. my method is if you only have a paper clip in your tool box...

EDIT: aside from regular tune up items, I usually consider the CTS part of a "tune up" item for TBI. usually for my own vehicle or if someone brings me something that has been neglected or not running right. Also consider the same for the O2 sensor, I usually upgrade to a heated O2 at this time.

brian617
10-20-2021, 12:30 AM
The CTS is a common failure for a TBI engine. The cutting out you are experiencing is the huge amount off fuel being adding intermittently as the PCM sees an engine temp of -40* when the sensor fails. It is enough added fuel to stall the engine and cause the issues you are having. Ignition cut out issues are usually followed by exhaust backfire.

srgould41
10-20-2021, 01:07 AM
I have experienced the engine backfire as the ICM failed. Didn't know what it was at the time.

Ran the experiment today, unplugged the CTS and the engine stalled and would not restart. Jumpering it seemed to run fine. Both cases threw the correct error code. Since I already ordered the ICM and CTS I'll swap both parts.


The CTS is a common failure for a TBI engine. The cutting out you are experiencing is the huge amount off fuel being adding intermittently as the PCM sees an engine temp of -40* when the sensor fails. It is enough added fuel to stall the engine and cause the issues you are having. Ignition cut out issues are usually followed by exhaust backfire.

tayto
10-20-2021, 06:03 PM
jumpering the connector and the vehicle running better is a good sign. I haven't seen this problem personally in over 10 years. as i stated before it is part of my TBI tuneup "recipe".

i made a mistake it's a 369 not 395. check what module you have currently. 048 will pull 6* of timing by 5000 rpm. 369 will add 2* by 3600. on a stock motor you should notice an improvement going to a 369 module. if you tune the timing tables it shouldn't matter what module you use.

srgould41
10-20-2021, 06:40 PM
I can only buy what's currently being sold. Not sure what the 369 module converts to these days. The D1984 is advertised as the "police" module. I assume that means it has a better performance profile, but who knows... I do have an older module that is marked as a 369 module. I'm keeping it as a spare.


jumpering the connector and the vehicle running better is a good sign. I haven't seen this problem personally in over 10 years. as i stated before it is part of my TBI tuneup "recipe".

i made a mistake it's a 369 not 395. check what module you have currently. 048 will pull 6* of timing by 5000 rpm. 369 will add 2* by 3600. on a stock motor you should notice an improvement going to a 369 module. if you tune the timing tables it shouldn't matter what module you use.

brian617
10-21-2021, 04:21 PM
One thing that just occurred to me also check the connector at the CTS, have had to replace one or two of those over the years as well.