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.
Hopefully Jaguar improved the OBDII on the'96 cars. On my '95 XJR the OBDII wasn't all that hot....and I'm being gracious here. I found it more of a torment than a benefit, actually
plums:
IDS and WDS both work fine (well as fine as they work!). I don't know about Mongoose. The X-300 modules are not programmable, for the most part- they use factory flashed PROMS. There are some setups you configure, though. Diagnostics in AutoEnginuity are pretty good for non powertrain modules, but it cannot do the setups like O2 Orientation and TPS calibration. And it is a whole lot more intuitive and easy to use.
What I really meant was diagnostics/servicing/configuration.
Maybe the X300 is not quite so reliant on computer diagnostics
as later models.
The basic question is whether someone owning a IDS/Mongoose will be
able to service a 1996 XJR most of the time. Anyone using that combination
on a 1996 X300?
Hopefully Jaguar improved the OBDII on the'96 cars. On my '95 XJR the OBDII wasn't all that hot....and I'm being gracious here. I found it more of a torment than a benefit, actually
Cheers
DD
What did it support? I'm trying to figure out whether it'd be worth getting a device for my 1995 X300. I want a bluetooth unit that will talk to a smartphone.
The MY 95 OBD is apparently legally not an OBDII compliant implementation, bu tI found little difference between the MY 95 and MY 96 connections. The ELM 327 Chinese knockoffs work fine and will report OBD faults just fine on an X-300.
I think Doug's frustration was with the X-300s lack of sensitivity to misfires and that many of them seem to grossly misreport LTFT.
I assume someone else will reply. I do not remember and I don't have an X-300 on the road anymore, but I BELIEVE the answer is yes, The speed is an OBD parameter as I recall.
I bought a ELM327 "Chinese knockoff", but not having much luck with the X300s. I can't get anything out of the 1996 car (LED on device is glowing, but can't find it on bluetooth), and on the 1995 car it's visible and seems to pair with the phone OK, but the software can't use it. I tried Torque and Dash and they both hang on "connecting" indefinitely.
Most likely the unit is defective, but any suggestions before I toss it?
I think bluetooth is a separate problem from connecting a obd-ii device.
While it might be unusable on a X300, you could try it on a more recent
vintage car of another make. Perhaps it functions as expected on other
vehicles. In that case, it still has its uses.
I agree with Plums - bluetooth connectivity is a separate issue.So it sounds to me like the device is faulty.
I have a cheapo ELM327 and Torque on my phone and works well with my Oct 94 registered X300. As an example, here's an O2 Sensor voltage graph I did a while back (seems Torque or the device can't interpret higher than 1.2 volts which is wrong for the X300 which is why there is a flat peak - but you can see the swing which is the important bit).
I have the mongoose adapter with the jlr v139.
it sees it and noticed that it's a legacy but when I try to open up the legacy IDS it doesn't work.
That is a function of tabman.exe starting up.
All of IDS/SDS is cobbled together by outsourced "programmers"
who seem to know little about system architecture and have
made some very rash ***umptions about the underlying
setup of the windows environment. They make it worse by
not documenting those assumptions.
Could you do me a big favour and see if your torque will let you add more O2 sensors. I have only two fitted but it will let me set up meters for sensors 3 & 4 which is puzzling.
Mike, Do you get data from 3 & 4?
My recollection is you can display a host of things in Torque as meters, dials, graphs, or digits, but they won't populate with data if they are not present or not supported by the OBDII implementation.
1996 XJR - obd-ii compliant?
