So I am running around in circles right now with having my Autoenginuity with Jag enhancement unable to communicate (not even retrieve DTC) with my 2000 Jag XK8. I also have a Aeroforce gauge with protocol that does not work. In both cases the suppliers are helping but are currently stumped. The OBDCOM unit I have works great with all sensors reporting correctly (STFT, LTFT, O2 sensors, MAF, IAT, RPM, ign advance, and more) and all DTC showing correctly. The OBDCOM determines the protocol automatically, and unfortunately there is no way to see what protocol it is using. Here is what I have been told by smart folks who obviously can't all be right. Only posts I could find were from a guy with a 2000 XJ8 that could never get the Autoenginuity to work and gave up.

Quotes:
-The 1999-2001 XK8 use a different protocol and have ECM configurations that are unique to those years.
-There is an OBDII terminal used by Jag only for those years that is powered and will confuse many interfaces. It also causes conflict with those interfaces designed to be compatible with Mercedes. Eliminating that pin on the interface plug might enable proper communication.
-The protocol is ISO 1430-2 PWM
-The protocol is CAN
-The protocol is ISO 9141-2
-The protocol is J1850-PWM (Aeroforce configured to this and does not work)
-The protocol is most likely JWP 2000 (as stated by OBDCOM engineer and their unit works 100%) but what ISO is equivalent to JWP 2000 ?


Thanks for any help

 

The protocol is ISO 9141-2.

The newer Autoenginuity pods need an adapter for pre-2003 XK8/Rs. Call Autoenginity for it, or if you can solder, open the pod up and connect pins 7 and 15 at the OBDII connector. It then should start working and auto-determine the protocol.

 

They left out pin 7? Astonishing.

(Pin 15 is a bit surprising, too.)

 

Most cars do not use the wake-up signal on pin 15, since it is redundant on the pin 7 signal, but the older Jags require it.

It is astonishing that they continue to sell the Jag kit, but only send the adapter that should have been included when someone calls to complain after hours of aggravation trying to get it to work.

 

My autoenginuity works on my 01 XKR without any adapter. Mine autoengineuity is about 1 year old. I am using Proline VCI hardware and Giotto software version 13.0.0.

 

Interesting. My Giotto software is version 14.0.0. with a build date of 11/15/2015. Also Proline VCI interface hardware. Works fine with my GM Cars for all the basic OBDII codes and sensors (but only have enhanced for Jag).

 

I am running version 10 with the Proline and it would not work on my 2001 XKR without jumping pins 7 to 15.

 

Well, finally got this resolved and in the process now understand to some degree why there are apparently conflicting answers.


The 2000 Jaguar and I would guess any using the LNF1410XX ECU uses CAN Protocol for the enhanced parameters available with the AutoEnginuity software and hardware interface. Jaguar was evidently early to implement CAN.

It also outputs GENERIC OBDII data via ISO 9141-2 protocol.


If you have ALLDATADIY access and also perhaps in the Jag service manual, there is a Communications Network diagram that clearly shows both the CAN Data Bus and The ISO 9141/2 Data Bus both communicating with the Diagnostic Connector and both buses communicating with the ECU.


This explains in part why the Diagnostic connector has all pins wired up.


The pin 7 and pin 15 issue was evidently an earlier issue, but the latest Proline VCI cable provided by AutoEnginuity works fine with any known application now.


When using the Enhanced Jaguar Interface, it is important that the Vehicle Communication Interface type is set to CAN and the Initialization Type is set to Non-OBD-II Only.

 

That's essentially the same as my STR. Actually the enhanced are also available via ISO (but it's a much slower interface).

 

Correct, that is the way it was explained to me too by the Jag expert at Autoenginuity.


I have a new Aeroforce gauge on order that will be set up for the ISO protocol and limited to the Generic data. Out of curiosity I tried a Aeroforce setup for CAN that I use in a GM car and it did not function.

 

So now that I have played with this a bit, I am pretty impressed with the Autoenginuity software and interface. A wealth of information so to speak.


Apparently the latest hardware and software no longer has any problem related to the pin 7 and pin 15, and are also now tolerant of the Jag power on pin 12 which is a problem for early units and other readers.