So today my Autoenginuity basic + enhanced Jaguar package
arrived.
Installing the software was easy enough. But getting it to
connect to my 2003XJR was not succesfull.
I have mailed the autoenginuity support, but I’m not
expecting an answer untill Monday. I wanted to do some work
on the Jag this weekend.
It detects the Proline connector but then it fails to
connect to the car as it can’t detect the cars protocol.
I’ve tried it on auto detect or manually on ISO 9141-2
(which is recommended setting for my Jaguar).
I’ve tried, just to be sure a different USB cable. Reset
everything multiple times, but to no avail.
It’s very frustrating, because I have a generic USD55,–
handheld OBDII scannar that connects automatically
everytime!
In reply to a message from JeroenD sent Fri 25 Mar 2011:
Joreon:
Sorry you are having trouble. I don’t have experience with the
Proline interface, but with the other one, I have found that a few
re-boots are sometimes needed. since you say it sees the ProLine
interface, I would say the driver is loaded right and the USB port
is open. Another piece of advice- Sometimes it can take up to 3
minutes or so th actually connect. Also, try reconnecting the car
side plug several times.
Good luck.–
Ross - 89 XJS, 98 XJR, 99 XJR, 02 XJ8
–Posted using Jag-lovers JagFORUM [forums.jag-lovers.org]–
–Support Jag-lovers - Donate at http://www.jag-lovers.org/donate04.php –
In reply to a message from sparkenzap sent Fri 25 Mar 2011:
I’ve just made some progress. I’ve been searching several
Jaguar forums. Came across a posting of somebody who had
similar postings and mentioned that by setting the device to
non-OBDII it would connect. And so it would!
So I’m connected know and trying to figure out how it all
works.
I saw the P1571 code which was related to the brake switch
(Failsafe Engine Mode) I reported earlier. Managed to clear
that one. Now I have U1135, U1260 and U1261 left. My JTIS is
useless, or I don’t know (yet) how to find these codes.
In reply to a message from JeroenD sent Fri 25 Mar 2011:
You are right - Neither JTIS or Alldata gives the meaning of more
than a few U codes, and do not include yours. Do you have the Jag
enhanced option? I assume it gives no explanation, either?–
Ross - 89 XJS, 98 XJR, 99 XJR, 02 XJ8
–Posted using Jag-lovers JagFORUM [forums.jag-lovers.org]–
–Support Jag-lovers - Donate at http://www.jag-lovers.org/donate04.php –
In reply to a message from sparkenzap sent Fri 25 Mar 2011:
If it’s like my Elmscan, you have to go into the Hardware
monitor on the laptap and determine which COM Port it is
connected to, you then have to select that one in the
setup/programme options and also select a suitable Baud Rate
(38400 in my case), there may be other parameters to set,
there are usually help files etc. on the disc and Googling
questions like: ‘‘How do I get my Proline interface to
connect to my car’’ generally brings up a wealth of information.–
The original message included these comments:
Sorry you are having trouble. I don’t have experience with the
Proline interface, but with the other one, I have found that a few
connect to the car as it can’t detect the cars protocol.
I’ve tried it on auto detect or manually on ISO 9141-2
(which is recommended setting for my Jaguar).
In reply to a message from Neil Maldon sent Sat 26 Mar 2011:
Thanks for all the help and suggestions.
As I discoverd, and now also confirmed by AutoEnginuity, in
order for it to connect (I use the USB version) you need to
set it to ISO and Non-OBDII compliant.
works fine. It’s an impressive suit of different sensors it
sees.
Last Sunday I hooked it up to a '95 XJR of a friend of mine.
Car had been running rough for a while, no engine check
lights. When I hooked my laptop on, there where no codes
visible, but when we started checking the various
parameters, O2 sensors were way out of whack and then we saw
the Mass Air Meter was not giving any signal at all. So we
took it out cleaned it, put it back in and presto, car runs
fine.
Not sure why there were no codes or no engine check light to
start with. Once we had cleaned the Mass Air Meter and put
it back in, we disconnected it with the engine running. Then
it did produce an engine check light and code, which I could
reset.
Still, this tool allowed us to very quickly isolate the
fault and fix it. I’m very pleased with it!
In reply to a message from JeroenD sent Tue 29 Mar 2011:
Jeroen, glad to hear it’s sorted and that you’ve fixed the
problem. These I/F’s are great when you finally get them to
work, but the instructions are often non existent or at best
sparse, The Elmscan clone I got for �15 was a real pain to
get going but does do most of what it says on the tin, so
not bad for the price.–
The original message included these comments:
As I discoverd, and now also confirmed by AutoEnginuity, in
set it to ISO and Non-OBDII compliant.
works fine. It’s an impressive suit of different sensors it
sees.
Still, this tool allowed us to very quickly isolate the
fault and fix it. I’m very pleased with it!