CEL on can't pull codes. Solid CEL no flashes at all. ??

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

Tedward

95 LC
SILVER Star
Joined
Feb 2, 2015
Threads
45
Messages
1,254
Location
Cleveland OH
04/95 LC OBDI

A couple years ago I managed to pull ABS fault codes.
For some time now I haven't been able to pull any codes at all. Lost my touch I guess.

Just replaced the short block, main engine wire harness, had the head reworked and am getting a CEL. I've pulled the 15 amp EFI fuse and or the battery for 15 mins. ECU relearns after about 15-20 miles and 5-7 restarts and CEL returns. However, I can't pull any codes.

I can set the base timing, just as I could before the new parts, with E1 and TE1 jumped in the diagnostic port. Pull the jumper and ECU takes over and adjusts the timing. Confirmed with timing gun.
However, I can't pull any codes even though the CEL is lit while truck is running.

Here is what I do in an attempt to pull code/codes:
Engine off
Jump E1 TE1 in diagnostic port on firewall.
Pull the very small jumper in the diagnostic port. (tried not pulling that small jumper with same result)
Turn key to the "on" position.

Results in solid CEL light with no blinking.

Would you all fine people help me get this worked out please?

Thanks,
Ed
 
Have you tried going to Checker or AutoZone and have them read out codes with a scanner? Free and easy if you don’t have a Scan Gauge or Ultra Gauge or a Bluetooth scanner on yur Smartfone.
 
I did go to one Autozone and try the scanner.
First I put a 15 amp fuse in the OBD fuse slot in the in-cab fuse panel.

The scanner powers up and tries but does not read anything. It's got 3 indicator lights on it, scanning/a green check/a red x. Getting the red x which I take to mean it's not reading anything. I tried that once before when they had a different scanner at that location. Nada.

I do have a OBDI bluetooth reader coming to me in the mail. The one someone posted up as being available again about 3 days ago. TOYOCOM or something.

This 04/95 wagon may be what some call OBD 1.5.
It has in-line cats, not the pair system EGR but later style, a MAF, and a crank position sensor.

However the 2 or 3 times I've put a scanner on it comes up with nothing.

Thank You for asking, I'm grateful for your time and expertise!
 
Have worked on some 95 year models. They have all been full blown OBD II setups. I’m guessing you have some kind of wiring problems? Have you looked at the main harness up around the EGR pipe at the rear of the valve cover? It is a common place for heat damage.
 
The main engine wire harness is brand spanking new.
The original one with no damage I wrapped and zip tied up long ago.

I've only run the "new" motor for 3 hours tops and the EGR pipe is deleted.
Had this can't pull codes mess before the swap.

Yes, there is an OBD socket above the fuse panel on the left side of dash.
I've tried twice for sure to plug in an OBD scanner. Once with the original harness and once with the new harness.

The metal cross member behind the glove box that the ecu bolts to is not even back in yet.
There is no damage to the loom or wires there.

Thanks again
Ed
 
Last edited:
If the OBD2 connector doesn't work, it's not likely to have anything to do with the engine harness. IIRC it only has a few connections, data from the ECU, power from the OBD fuse and a couple of grounds. So one of those connections or the ECU (rare).
 
Tools your correct. There are 4 connections in the obd socket.
Data, power, and 2 grounds.
I'll get to the wagon and check the pins for voltage or ground respectively.

I may be mistaken about it being obdI and feel sorta dumb not knowing for sure.
I do know '95 was voluntary obdII compliance and 96 was mandatory in the U.S.A.

Perhaps this one is obdII but has an early, short lived type of obd communication.
I know next to nothing about this just puking up some info I've read about here and there.
I looked in my 95 FSM, 95 EWD and 97 fsm and the pinouts for the obd socket are the same.

I've read MANY threads over a few years with you, @Tools R Us, and @inkpot helping people get wagons sorted with all manner of problems. Thanks for your help!

I may have goofed something up once upon a time when I removed the security system. It was not the dealer installed one but some other aftermarket brand. I'll do some stretches and get under there with a meter.
 
I did go to one Autozone and try the scanner.
First I put a 15 amp fuse in the OBD fuse slot in the in-cab fuse panel.

The scanner powers up and tries but does not read anything. It's got 3 indicator lights on it, scanning/a green check/a red x. Getting the red x which I take to mean it's not reading anything. I tried that once before when they had a different scanner at that location. Nada.

I do have a OBDI bluetooth reader coming to me in the mail. The one someone posted up as being available again about 3 days ago. TOYOCOM or something.

This 04/95 wagon may be what some call OBD 1.5.
It has in-line cats, not the pair system EGR but later style, a MAF, and a crank position sensor.

However the 2 or 3 times I've put a scanner on it comes up with nothing.

Thank You for asking, I'm grateful for your time and expertise!
I have two 95's, January and July builds. Both are fully OBDII compliant, as per the SAE specifications for 95.

If your connector doesn't give you any information, either it, your diagnostic tool or both are at fault.
 
Started checking the connector last night.
Terminals 4 and 5 ate good grounds and 16 is battery voltage.
Didn't check number 2 yet for pulse wave generation.
I've always assumed it was OBDI despite the manual and sticker under the hood stating it's sae j1850 compliant.
I'll seek out a different scanner.
Thanks @Malleus


20180404_194703.webp
 
There is another obd port on the firewall passenger side. Try that one just Incase it’s a wiring issue under the dash?
 
Yup. The diagnostic port on the firewall.
That is where I assumed I'd pull a code.
It is also where I successfully jumpered e1 and te1 to set base timing.

I was thinking my reading and or comprehension is not up to the task.
Meaning I don't follow the directions to pull codes from the diagnostic port on the fire wall.

The way to that is (I think)

1. Engine off
2. Jump E1 TE1
3. Pull tiny jumper in the diagnostic port.
Not my "paperclip" but the one that lives there full time that comes with the harness.
I've tried leaving that little jumper in as well, no dice.
4. Turn ignition to the On position
5. Count the flashes/blinking of the CEL indicator light.
Don't start the engine or unless you want to clear the code.

Can one pull codes from an OBDII system the 'old' way in the diagnostic port as well as use a scanner? (not at the same time)
Is it one or the other only?
I'm gonna put a meter on the diagnostic port pins and see if they check good.

Didn't even check the pulse wave generation pin under the dash yet.

Thanks @cjmoon for your time as well!
 
So connector D3, the OBD socket above ds fuse panel, has
battery voltage at pin 16. Good
grounds at pins 4,5 Good
No idea how to measure the pulse generation at signal wire. pin 2 Oscilloscope maybe and I don't have one. ??

Connector D1, the diagnostic port on the firewall
ground is Good
battery voltage. Good
signal Forgot to check that while trying to pull codes.

The signal wire in D3, the obd socket, has continuity to the correct pin at ECU
The signal wire in D1, the firewall, has continuity to the correct pin at ECU

Went to the Zone again and tried the scanner agin. Nothing
Still can't pull code from the firewall.
Same results with the original ECU and another from a 97.
Will try a different scanner elsewhere.

Truck runs well, except the CEL is on. Fairly certain the cel is on because of the EGR temp sensor. All I did was jump the 2 wires after the EGR delete. Thought it's obdI so just need to jump wires. I will install a 4.7k ohm resistor when it arrives and clear the code/codes again.

Just for the record the CEL came back on yesterday time after only 9 miles. Personal best!

Hopefully it's just the crappy the Autozone scanner, but I imagine they would know if it was broken. People use that thing everyday.
 
Is that an exclusive araingment? I know, why would anyone care to go about counting flashes and be limited, but can one so thay on obdII?
Thanks for checking in again.
 
Is that an exclusive araingment? I know, why would anyone care to go about counting flashes and be limited, but can one so thay on obdII?
Thanks for checking in again.

Only way I know to read OBD II codes is with a digital code reader plugged into the dash socket. Have never heard of anyone having good results trying to read it like an OBD I system.
 
Only way I know to read OBD II codes is with a digital code reader plugged into the dash socket. Have never heard of anyone having good results trying to read it like an OBD I system.

They guy in the store may think it should be tested like other OBD I rigs since it is a 1995. Tell him it is a 1996 and test as OBD II.
 
My build date is 06/95 and both the crap scanner at O'Reilly's and the nice snapon scan tool read mine just fine since it's obd2. Idk you could even hook a scan tool up to obd1 vehicles. I've never seen obd1 with a plug for a scan tool. I could be thinking of obd0 also...
 
Are messing with me...
OBD0?
Come on man, I got enough trouble figurin tween 1 and 2. Now there is a 0.
 
Back
Top Bottom