Custom ECU:
Here is where things get interesting. I have mapped out each pin on the factory ECU, and captured voltages/scope patterns to verify what it is actually doing. Some of the inputs require a pull-up resistor — like the CPS, CMS, VSS… Whereas the stock ECU processor was based on 5 volts, newer more powerful processors are 3.3 volt. The “brain” for the replacement controller is a Microchip dsPIC33CK256MP506; 64-pins, surface mount, 3.3 volt VREF (as opposed to the original 5 volt), lots of memory, lots of timers, other cool features, and FAST!!
I wanted to use an original style header connector so the factory harness would plug right in. They seem to be obsolete — to the point where I cannot even find a part number let alone order one (or more). I considered sacrificing a stock ECU to pirate the header. Instead, I plan on putting the circuit board into a Cinch LE-60 enclosure with a 60-Pin header/connector arrangement. At least the number of pins matches the factory connector. It looks like a factory ECU (not like our Jeep’s, but still), is weather tight, durable, and functional (the Cinch has 2-30 pin connectors to get the 60 pins). I’ve used many Cinch enclosures for past projects and love them. However, it requires re-pinning each of the wires from the factory connector to the new connectors. Important wires can be spliced & split, where a factory connector is retained, but the signals and outputs are sent/received to
either the factory ECU
or replacement ECU (only connect one or the other). If I have to troubleshoot issues with my replacement, I can just plug in the factory ECU and I’m mobile.
Having a fancy controller only has value if you can data log and tune on-the-fly. I am creating a “dashboard” to interface the replacement controller via USB for tuning and data logging. I’m looking at ways to use Innovate Motorsports’ LogWorks3 for data logging, though there are still a few hurdles to conquer to get it to work for this project. Plan B is to create data logging software from scratch (not looking forward to that, as it will entail several hundreds of hours). Another feature I want to add is to use the J1962 OBD II diagnostic connector to monitor data. This means a crap load of software so I can use my Actron Scan Tool to monitor what is going on without having to pack a laptop along. It will generate OBD II compatible codes to indicate malfunctions/issues, monitor data stream information, facilitate the “clear codes” function, and perhaps other OBD II features. (This will easily consume over 250 additional hours to implement!!! But, I think it is worth it.)
Added Features:
In addition to what the stock ECU controls, there are a couple open pins not doing anything. I want to add electric fan control — not just on/off, but have at least 4 speed control selections using PWM; low at slightly above threshold, half speed at the next threshold, 75% speed at the next threshold, and full-on at the critical threshold. For my personal project I want EGR. I know most of you cannot possibly appreciate how valuable this can be for low-end torque and fuel economy, but look into what George Arlington Moore did with EGR back in the 1920’s. I believe newer vehicle engineers have taken Moore’s lead with how they use EGR. I want to assign other unused pins for generic digital I/O’s or analog inputs for added capabilities.
Here is why you should care:
I intend to make all of this open source. The schematics and PCB boards are being created with
free ExpressPCB software. You can download it at no cost. The PCB board is a 4-layer board you can order yourself from ExpressPCB (or we can do group buys to reduce costs). The software will be regular Microchip XC16 C code using MPLABX IDE that are both free to download from Microchip. All parts (BoM) will be made available so you can duplicate everything yourself. And lastly, I am trying to create this project so that it allows for not only the 4.0 ECU replacement, but also V-8 and even 4-Cylinder ECUs. If you own a Chrysler product 1995 or older, this could be YOUR next controller!
Here’s where I’m at:
The block is basically done (more or less). I left a few things unfinished until I’m ready to bolt the head on (like installing lifters). The head still needs a few finishing touches before I send it off to the machine shop for seats, milling, tanking, and guides. I have been simultaneously building the schematic, controller software, and the dashboard. I have yet to start the PCB board, as that requires everything else to be done first. In other words, I spend about 100 hours on ECU replacement engineering, but probably still have 200-350 hours left before I can even start ordering parts.
I encourage comments. Imagine I’m doing engineering for YOUR Jeep. What would you like to see? What might you do differently? Since I’m making it all open source, your comments now could ultimately become
YOUR reality later.
View attachment 4163426
Thanks so much for this post. I'm trying to talk to my original ECU, now on the bench since I bought a cloned unit with IMMO disabled. So I'm frustrated about not being able to find schematics, pinouts or much on this Motorola #56044 ECU. I looked inside and there is a Moto MCU with what appears to be a Chrysler house part #. I tried shooting a pic but there is just too much potting solution on it.
All I want to do is remove IMMO, Remote programming, basic fuel efficiency re-mapping.
What is the tool (s) of choice for WJ? I'm totally proficient in soldering/desoldering including SMD so whatever it takes to talk to this guy is fine with me.
Thanks, JP