• Notice for iPhone users: DO NOT use the image size reduction option when uploading photos to the forum. This causes portrait images to post as landscape. We have added a warning to the image insert pop-up as well.

4.0L OBDII engine swap - Check engine light solution

bigwalton

Alaskan Postal nutjob
FORUM MANAGER
SOA Member
City
Dexter
State
MI
Since CJOffroad seems permanently dead (so incredibly sad how much awesome swap info died with it :banghead:) does anyone out there know about resources/info related to getting the check engine light/MIL working on an OBDII swap?

EVERYTHING I looked at was on that site and as I wasn't concerned with getting it working in my swap immediately due to not having emissions here, I didn't save off anything relative to it. I've come up empty in searching, everything ends up pointing back over to CJO.com

I do believe that I never saw a thread where anyone actually had a working solution, lots of dead end "how do I..." threads or people saying "the way you'd figure it out is..." though. But I wasn't looking hard either, as mentioned.

I'm asking because I have connected with an automotive design engineer that I am working with to develop an all-in-one, easy-to-install digital solution to this for all 4.0L engines from 96-02 that will work without the cluster. We have a prototype and I've been searching to find anything about alternative/competing solutions.

Any info/resources/links would be very appreciated.

Also, if you did the swap or were thinking about the swap and would be interested, let me know.
 
The Hesco/Mopar MPI kit I put on my red Scrambler came with instructions on how to hook up the MIL light. It was fairly simple. But, my harness came from Hesco, but I would imagine the wiring/wire colors would be the same as a 95 YJ harness. I can look/post up what I find, if that helps:shrug:
 
That's an OBDI setup, it is very simple, just wiring a light to the wires off the PCM. The issue is with newer motors after '96 that use OBDII. These motors use a digital signal fed to the gauge cluster to run a number of the readouts/lights that decodes the signal and lights the MIL.

Trick is that it's getting harder to find decent reasonable-mile OBDI motors and will only continue to do so.

On the other hand, there's a TON of later motors out there already with lower miles and will only be more for some time to come that would be great swap candidates, but only work for people in non-emissions locations or that don't care about not having a check engine light.
 
just put power on lead of the LED and the ECM provides the ground to turn it on when you have a malfunction. That is the way it works on a chevy obdii...i am pretty sure its the same..if not i am sure i will be soon corrected.
 
No. There is no ground coming from the PCM. The MIL is hard wired in the cluster from the microprocessor that decodes the CCD/PCI signal, the PCM doesn't have any connection to the MIL electrically, it feeds a control signal to the cluster that then activates the MIL. This is why the only things I saw that worked were people who installed the donor cluster.


Edited because I misread Scott's comment, thought he said power was coming from the PCM.
 
Last edited:
For reference, the basics of how the Chrysler OBDII system (96-02) triggers the MIL is that there's a digital signal between the PCM and the dash that gets read by a microprocessor in the cluster that does whatever is needed on the respective gauge/light. Most of the functions in the cluster are controlled by this signal/microprocesor from the water temp, to tach to MIL, etc. There are a few things that do not involve this signal, but unfortunately, the MIL is not one of those and you have to figure out a way to get the information from the CCD signal.

For this reason, I'm not aware of a solution other than using the donor dash, but I could easily be missing something, which is why I started this thread. I can say with confidence that there's no setup that can work like the earlier OBDI systems where you simply wire a light between two wires/terminals, I think it's got to be something like we're doing with a microprocessor circuit to read the CCD signal or somehow pulling the respective circuitry out of the gauge cluster.
 
eeeeek..then it is over my head...when i did mine, put a stand alone LED in the dash. The harness i had provided a lead for it to go to the ECM. I just put potential on one lead and the ECM provided the ground when a Malfunction was indicated. That is my only experience. sorry i was no help.
 
eeeeek..then it is over my head...when i did mine, put a stand alone LED in the dash. The harness i had provided a lead for it to go to the ECM. I just put potential on one lead and the ECM provided the ground when a Malfunction was indicated. That is my only experience. sorry i was no help.

LOL. Exactly, that's how we all wish it was! That's how the pre-96 systems worked. Durn engimaneers went and screwed it all up for us!

Trying to fix that though :D
 
You mean pre-97 on an XJ. Obviously no 96 Wranglers and I can't speak for the 96 Grands, but a 96 XJ works like OBD1 for MIL.

I didn't dig it out my FSM, but my spreadsheet from doing the wiring shows C165 CAV17 runs right to the light. No computer in the gauge cluster, just a printed circuit similar to OBD1 Cherokees.
 
That's an OBDI setup, it is very simple, just wiring a light to the wires off the PCM. The issue is with newer motors after '96 that use OBDII. These motors use a digital signal fed to the gauge cluster to run a number of the readouts/lights that decodes the signal and lights the MIL.

Trick is that it's getting harder to find decent reasonable-mile OBDI motors and will only continue to do so.

On the other hand, there's a TON of later motors out there already with lower miles and will only be more for some time to come that would be great swap candidates, but only work for people in non-emissions locations or that don't care about not having a check engine light.

Yep, I breezed right over the whole OBD II issue, sorry:o

Besides the easier availability of the OBD II stuff now, is there any other benefit:shrug:

The diagnostic information that I can pull off my OBD I port is unreal. Besides the codes, I can pull all sensor voltages, engine operating parameters (RPM, temp, IAC % open, etc, etc) and any other info that I might want. But, if the OBD I stuff is getting hard to find, it is a moot point:shrug:

I never hooked up the MIL light in mine, still need to do it, I guess. I just check mine with the scan tool every once in a while. But, the light would be better:thumbsup:

It seems the Jeep OBD II MIL light issue is going to be a tough nut to crack. My 05 TJ has this set up, kind of crappy how the computer just tells the oil pressure gauge to go past normal as long as there is over like 5 psi of oil pressure, not too useful to me:confused: Someone must have figured this out by now:fingerscrossed:

I did a little research, and every time something useful would come up, it would be a link to the CJOffroad site, which is dead:confused:

Good luck, post up any news on this:thumbsup:
 
You mean pre-97 on an XJ. Obviously no 96 Wranglers and I can't speak for the 96 Grands, but a 96 XJ works like OBD1 for MIL.

I didn't dig it out my FSM, but my spreadsheet from doing the wiring shows C165 CAV17 runs right to the light. No computer in the gauge cluster, just a printed circuit similar to OBD1 Cherokees.

Ah, my bad on the years, regardless, it's the OBDII versions for each.
 
Yep, I breezed right over the whole OBD II issue, sorry:o

Besides the easier availability of the OBD II stuff now, is there any other benefit:shrug:

The diagnostic information that I can pull off my OBD I port is unreal. Besides the codes, I can pull all sensor voltages, engine operating parameters (RPM, temp, IAC % open, etc, etc) and any other info that I might want. But, if the OBD I stuff is getting hard to find, it is a moot point:shrug:

I never hooked up the MIL light in mine, still need to do it, I guess. I just check mine with the scan tool every once in a while. But, the light would be better:thumbsup:

It seems the Jeep OBD II MIL light issue is going to be a tough nut to crack. My 05 TJ has this set up, kind of crappy how the computer just tells the oil pressure gauge to go past normal as long as there is over like 5 psi of oil pressure, not too useful to me:confused: Someone must have figured this out by now:fingerscrossed:

I did a little research, and every time something useful would come up, it would be a link to the CJOffroad site, which is dead:confused:

Good luck, post up any news on this:thumbsup:

This isn't for anything that's wrong with the OBDI setup, there's plenty of good info you can get from it.

This is purely from the fact that you're already seeing people (like me!) having to/wanting to go with a newer motor because it's so much easier to find with decent miles (something that will only be more apparent as time passes). But, if you need to smog with it somewhere that requires a MIL, you're out of luck and you'd better keep looking for an older motor or resign yourself to installing the donor cluster :eek: (or try to convert an OBDII to OBDI, which works, but is not going to be cheap). To my knowledge, the ONLY thing that would prevent a proper OBDII swap from smogging in one of those locations is the lack of a working MIL, so there would seem to be all kind of need for something like we're developing.

The fact that CJOffroad died only makes it that much worse. I have not come across a definitive solution anywhere. Lots of swaps of course, but not that has a true, working MIL

As for the tough nut to crack, sort of in that it's not something you or I can easily do (again, as far as I've ever see) due to the limitations I mentioned on it being buried in the CCD signal but it would take someone who knew enough to be able to build the circuitry that can locate and act on the MIL signal buried in the CCD feed.

That's exactly who I am working with and we already have a rough proof-of-concept prototype (has some extra circuitry for testing/troubleshooting that wouldn't be a part of the production units) that's getting it's first testing and should be in my hands soon. After that, we'd be hand-assembling a few test boards with the same functionality as the production unit would have to test even further.

Anyone out there with an OBDII swapped 4.0 that kept the diagnostic port, let me know on here or via PM and maybe you can beta test one of the functional units. :D
 
Might be worth talking to that company, Hot Wires, I think it is that is making a harness for the OBDII stuff. I kept looking at them to get a modified harness for the OBDI system but looks like they are into the newer stuff. There is a link on magazines like JP to that company.

I am not sure how they do it. But they must e decoding it somehow.



Carl
 
Great idea Carl, I just did that.

They know of one solution, an "undocumented location" in the computer connector that can be accessed by disassembling the computer itself, drilling out a sealed off pin location and soldering a pin/wire to the board at that location to drive a light. He was very sure to caution me about it "if I was really going to try it myself" as it's not easy to do without destroying the connector or the computer.

He didn't have any directions/procedure to send me, but he said he'd "talk me through it" on the phone. He was very helpful and willing to give me the verbal instructions it for no fee, but it was easy to hear the hesitation in his voice about trying it. I didn't make him go through the process.

I specifically asked him if he knew of any other solution and his answer was a definitive "no". He actually offered that the only other possibility was to try to find someone to build something that worked off of the CCD signal ;) Ok, I will :D
 
Not sure what year computer you have... but I found this.

http://www.jeepforum.com/forum/f12/pin-obdii-trouble-light-lead-1130773/

I am still in the process of installing the 4.0 head and just got it fired up tonight for the first time. Yay me!

However, I DID find a 'check engine' light lead from the ECM on the OBDII systems. I thought there had to be one because I had done the on-off-on-off-on to the Cherokee key switch before I stripped it down and had retrieved the flashing codes from it.

My pin-out for the OBDII showed the gray plug/pin #17 as blank and not used. I had a black/pink wire coming out of it and that was the color of the CEL on the OBDI systems, so I hooked up a LED to it and cycled the ignition and, sure enough, it started flashing codes to me! The wire is, of course, a ground to a light that is now installed in my dash bezel.
__________________
Boycott shampoo! Demand the REAL poo!
White Jeep Club #119
☼lllllll☼
 
Not sure what year computer you have... but I found this.

http://www.jeepforum.com/forum/f12/pin-obdii-trouble-light-lead-1130773/

I am still in the process of installing the 4.0 head and just got it fired up tonight for the first time. Yay me!

However, I DID find a 'check engine' light lead from the ECM on the OBDII systems. I thought there had to be one because I had done the on-off-on-off-on to the Cherokee key switch before I stripped it down and had retrieved the flashing codes from it.

My pin-out for the OBDII showed the gray plug/pin #17 as blank and not used. I had a black/pink wire coming out of it and that was the color of the CEL on the OBDI systems, so I hooked up a LED to it and cycled the ignition and, sure enough, it started flashing codes to me! The wire is, of course, a ground to a light that is now installed in my dash bezel.

Yeah, thanks, that seems to have been proven out in that thread to be an oddball '96 - only setup that guy had. That was the transition to OBDII. I'm guessing that's probably the wire/pin that the HotWire guy mentioned adding into the computer.
 
Back
Top