1996 XJR - obd-ii compliant?
#1
#2
Join Date: Mar 2008
Location: Pacific Northwest USA
Posts: 24,850
Received 10,906 Likes
on
7,166 Posts
#3
#4
Join Date: Mar 2008
Location: Pacific Northwest USA
Posts: 24,850
Received 10,906 Likes
on
7,166 Posts
#5
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.
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.
#6
Thanks for educating a noob
"programming" was a bit of a misnomer i guess.
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?
"programming" was a bit of a misnomer i guess.
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?
#7
Trending Topics
#8
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.
#9
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 think Doug's frustration was with the X-300s lack of sensitivity to misfires and that many of them seem to grossly misreport LTFT.
#11
#12
Join Date: Mar 2008
Location: Pacific Northwest USA
Posts: 24,850
Received 10,906 Likes
on
7,166 Posts
#13
Join Date: Mar 2008
Location: Pacific Northwest USA
Posts: 24,850
Received 10,906 Likes
on
7,166 Posts
#14
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?
Most likely the unit is defective, but any suggestions before I toss it?
#15
The following users liked this post:
sparkenzap (12-18-2015)
#16
#17
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 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).
#18
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.
The following users liked this post:
smgdata (12-19-2015)
#19
#20