Folks,

I've been looking into possible ways to swap the AJ34/6HP26 combos for others like the Coyote/4R70/4R75/4R100 or the LT4/8R90-E combos ...etc. This has been done for the older XK8s with AJ26/27 and ZF5HP combos to Chevy LS and GM4L80 combos ...etc, but nothing for the X350 and AJ34/6HP.

For this to work, an interface between to the gauges and a bunch of other original components needs to be created - I have the know-how in comms and software to do it, but need can info to decode the CAN/SCP messages on the Jag's busses.

Any pointers would be gratefully received; once achieved (and I hope it will be !), I'll publish the info to get the interface and detailed info on converting my own X350 to my dream Coyote/4R100 combo here in the forum.

Thanks,

Ahmed.

 

Hi, the probably best available source of first information for your project is imo the wiring diagram for the X350 MY 2005, which can be found at jagrepair.com.

This wiring diagramm contains at the end a message matrix separated by bus system, showing which controller expects which input signals from other controllers or sensors, actuators etc..
In addition, you will find information on the type and quality of the signals in the diagrams in the explanations of the connector/PIN assignment.

A very demanding task, I wish you good luck.

Fritz

 

Thanks for the response and wishes @flatsix

I have the wiring diagram and know of message matrix you're referring to, but I wish it was that simple. I need to somehow break apart the CAN messages themselves, to extract the PIDs - these are the node addresses. Once the PIDs are figured out, I can then reverse engineer the message chatter between the nodes, and therefore make whatever translation is necessary.

In particular, I want to start with the cluster, and figure out which messages control the various gauges and indicators. This information is available pretty much for all things German, and Japanese to a lesser extent; I could find nothing for the X350.

Thanks again.

 

Hi Ahmed, I was already clear that it is only an overview of the message babble, but that's where it starts i think.

If you like and for my understandig describe an example of what the interface does exactly. Let's take a physical information in form of a variable resistance value given fron an NTC temperature sensor for the coolant temperature, input signal for the ECU. Among other values, the ECU (which one, the original one or the one of the swap unit?) generates output signals in the form of voltage values (V) of different lengths for triggering the injectors.

So, according to my layman's understanding, the interface is about receiving and correctly pin distributing physical information (volts, ohms, amps, seconds, degrees), while the actual software processing happens as usual in the ECU?

Thanks, Fritz