When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I have been using Torque Pro for many years on an el-cheapo Bluetooth $0.99 ELM/OBDII I bought from Hong Kong - no issues on Jaguars and many cars - but I have had issues on some Fords and some GM vehicles making a connection.
My temp reads fine on both my 2000 and 2001 XJ8's, I also used it on my old '96 XJ6 to diagnose - using a trend chart graph - a failing coolant Temperature Switch that was failing to no signal at about 120F causing a full stall on acceleration. $10 later and 5 minutes to R/R from Advance Autoparts and it was fixed.
My question is, has anyone thought about developing some custom Torque Pro templates/Plugins and PID's for our Jaguars to access more diagnostic real time data?
It seems to me the command information is available in the JITS if anyone is so inclined - gifted with some time to add some functionality.
The latest Torque Pro version I just updated has a Manage PID - OBD2 PID editor for building custom commands.
First thing: please update your signature profile to let us know what MY X308 you own.
I run a MY1997 XK8, and Jaguar does not fit a coolant temperature sensor to the 4.0 litre V8. Therefore you will not be able to read the coolant temp from your OBD II, period. The temperature gauge fitted to the XK8 followed by the MY1998 XJ8 is a "rigged" gauge: it will always be centered as long as the temperature is within the tolerance limits; it does not show the actual temperature.
I have no idea from which MY after MY1998 did Jaguar started to fit real temp gauges to the AJ-V8 engines, as some posts state that they do read the temp, but again I have no way to determine their X308 MY as they sadly also do not show it in their signature...
Originally Posted by Z07Brandon
And the ELM Bluetooth adapter. Am I the only one who can't read coolant temp? It always shows"no data". Also, my 02 XJ Sport started running rough/misfiring randomly at stop lights. So I was checking to see if any codes were set. There is a p1111, but I researched that and it nothing to be worried about.
Brandon
Last edited by Pristine97XK8Convertible; 11-29-2017 at 12:35 PM.
... and Jaguar does not fit a coolant temperature sensor to the 4.0 litre V8. Therefore you will not be able to read the coolant temp from your OBD II, period...
I don't know where you get that from, but it is nonsence.
A XJ8 has the temperature sensor in the cross over pipe in front of the thermostat tower.
I do agree that the gauge in the dash is pretty much useless to diagnose, but that does not mean the sensor is.
OBD2 is perfectly able to read the exact temperature in one degree steps (minus before mentioned bug on the 2002 then ..)
Ohh, and my signature perfectly stated car and year, as some of the other posters do as well.
First thing: please update your signature profile to let us know what MY X308 you own.
I run a MY1997 XK8, and Jaguar does not fit a coolant temperature sensor to the 4.0 litre V8.
Hi Pristine97XK8Convertible,
I'm not sure why, but I notice that signatures are not always showing up today. May just be a glitch in the forum software, or maybe some users really do need to add their vehicle info to their signatures.
Regarding the engine coolant temperature sensor, that has been a primary engine management system component since the advent of electronic fuel injection, so most cars built since the 1980s have them, including Jaguars. As Eric stated, on the AJ26 and AJ27, the ECTS is in the coolant crossover pipe. Here's the description from the Engine Management System manual:
We all agree that the temperature gauge in the instrument cluster does not provide an accurate temperature reading, but the ECTS certainly does, because the Engine Control Module depends on it as a primary input for determining fueling.
My x308 is a 2002 Sport. I will start downloading some other obd2 apps, and see how it goes. If they don't work with my ELM, I'll just buy a different one.
My torque pro yesterday showed me code p1338 and interpreted it as bad cam position sensor bank 1 but a repair shop told me it means bad fuel pump. Looking on here, I see that p1338 does indeed refer to a fuel pump issue, not a cam position sensor so this is a warning to not take the data provided by TP as gospel. It does know what my car is and has no trouble pairing with it via WiFi on a foseal dongle. My car is keeping P1000 no matter what cycle I complete but it is not lighting the CEL.
On the list of gauges torque pro will let you add, does it show coolant temp in light green or grayed out? If greyed out, you can add the gauge to your screen but it won't give you any readings.
My torque pro yesterday showed me code p1338 and interpreted it as bad cam position sensor bank 1 but a repair shop told me it means bad fuel pump. Looking on here, I see that p1338 does indeed refer to a fuel pump issue, not a cam position sensor so this is a warning to not take the data provided by TP as gospel. It does know what my car is and has no trouble pairing with it via WiFi on a foseal dongle. My car is keeping P1000 no matter what cycle I complete but it is not lighting the CEL.
On the list of gauges torque pro will let you add, does it show coolant temp in light green or grayed out? If greyed out, you can add the gauge to your screen but it won't give you any readings.
Hmm, I'll have to check later today if it is green or gray. It read it(coolant) on my dad's Merc no problem. Yeah, on the codes, I'll search "p1202 x308" before I believe torque pro's general description. Not that I have that code, or is a real code, I was just using it as an example.
All P1 codes are non-generic. They can be specific to any/all of the maker, the model, the year, the VIN range or even the one car (which Jaguar don't seem to do).
So, any car with a P1xxx code - look the code up for the exact car.
TP would need huge tables and it hasn't got them. Telling you the wrong meaning does strike me as worse than useless, though - but it does that.
My torque pro yesterday showed me code p1338 and interpreted it as bad cam position sensor bank 1 but a repair shop told me it means bad fuel pump. Looking on here, I see that p1338 does indeed refer to a fuel pump issue, not a cam position sensor so this is a warning to not take the data provided by TP as gospel. It does know what my car is and has no trouble pairing with it via WiFi on a foseal dongle. My car is keeping P1000 no matter what cycle I complete but it is not lighting the CEL.
For your 2004, you can consult the official Jaguar diagnostic trouble code definitions and possible causes in the X350 DTC Summaries guide, which you can download here:
Also, Torque Pro offers the ability to read some of the Mode $06 data which may show you which system or systems are not completing their System Readiness Tests (SRT). If I recall correctly, the Mode $06 data is found under the "Test Results" option.
Mode $06 data appears in a format like this: "Test ID $04 Comp ID $00." The numbers following the dollar signs will vary depending on the system involved. To interpret the data, see the only Jaguar-specific definitions of Mode $06 data that I have been able to find, on pages 12 and 13 of the document at this link:
Curious what the issue might be for a 2002 not being able to display data for Coolant.
I was under the impression 1998-2003 were all basically the same ECU, next changes came at 2004- 2008.
I know different OBDII adapters are claimed to have intermittent issues with which sensors they can actually read - which really does not make sense to me.
he OBDII Adapter is only a communication protocol interface (CAN bus) between the Scanner Software and ECU, the adapter is not the device interrogating the various diagnostic codes from the computer.
It is the Scanner Software that sends the codes to the ECU via the CAN bus interface using OBDII protocols to receive a values and display them on your screen.
For example this Mode $06 Code Sequence requests the parameters for the Lean-to Rich Sensor Threshold Voltage - and the ECU returns the values:
------------------
TID:$02 CID:$11
- Lean to Rich sensor threshold voltage(constant)
Min: 0
Test result value: 65,535
PASS
I will have to do more research into that issue as it must be something in the chipsets - whether they are genuine CAN Bus ELM/OBD2 communication protocol devices or not.
This standard dashboard shot was after a new update of TorquePro to version 4.5 but I have had Coolant temps (bottom right gauge) all along with all previous versions.
After this shot I did change readouts to US units.
Anyway, both my 2000 and 2001 show as follows"
TorquePro with Coolant Temp
Last edited by StagByTriumph; 12-03-2017 at 03:32 PM.
The hardware device is a complete uC (micro controller with interfaces and firmware). Then there's the stuff inside the app (TPro, DashCommand, etc). As DashCommand can read ECT but TPro fails that pins down the culprit.
11-28-2017, 02:04 PM
Torque Pro Jaguar Plugin / Custom PID
