Hi all,

recently I bought the AutoEnginuity Pc tool. My problem is it doesn't connect to the car. I'm not talking about the extra jag package. What I'm trying to do is use standard ODB-II.

my car is XJR from year 2000. Anyone who managed to make it work with this car?
BTW: AutoEnginuity support let me down :-(

Thanks.

 

I have the AE for my 03, and it does take awhile to connect to the car, sometimes 30 seconds. You also need to first select the correct protocol (ISO 9141-2 pretty sure), otherwise it will take forever, or maybe even time out before making the connection. If you were in the states I could talk you through it the first time. I have some luck canceling the initial connection, then re-connecting and it often connects much quicker, like within 10 seconds. post back with your step by step process...and if you succeed.

 

My experience is exactly the same, plus a few reboots in the process.

 

Just a thought.

If you have the usb version, and you are prone to using it while on battery power, the usb power management functions might be getting in your way.

Go into advanced properties of both device manager and power settings, and turn of power management of your usb ports.

 

I have the USB version. I was told by AE that the standard obdII functions will not work on my car (01VDP) at this time. I believe there is some sort of pin out issue. As you can imagine I'm not to happy, if there are enough of us with problem maybee we can pressure them to make a fix.

 

That's strange. They offer the software upgrade/addon and then say the base odbII won't work on their hardware?

 

You know reading about the lack of support has put me right off using A.E. - I'm now on the hunt for the correct dongle to plug into an old laptop to run the IDS. Problem is, it's the same as Ford use and very popular, so the prices start at $2000. For me, it's the only way now - I've toyed with the idea of A.E. Oh well, time to start saving....

 

It's funny I found their phone support to be quite good with the exception of not fixing the obdII issue... which is a big deal., but the reason I bought it was to read the JAG specific codes which it does... U can read obdII with any autozone reader.

 

Hi all,

I bought the Jaguar extension and upgraded both, the ScanTool and the firmware (I have the proline usb connector).

Then I finally managed to connect to my 2001 My Jaguar XKR this way:
1) connect the connector to the car
2) connect via USB cable to the computer
3) turn on the ignition
4) start the ScanTool program
5) go to the connection configuration (pressing F4)
6) select protocol ISO 9141-2 and select non OBD-II vehicle
7) connect to the vehicle (pressing F2) then when asked for the vehicle details filled the correct ones ;-)
Done.

This way I was able to read and clean error codes, I didn't have tome to see if sensor data can be read and loged.

 

I do not know what really happened in dneidr's experience with AE customer support. As I said earlier, my software is slow to connect, occaisonally requiring several "boot bounces", but it has always connected and worked on my '96 XJ6, '98 XJR, '99XJR, and my '02 XJ8. So, something ain't adding up.

And while I wish the software connected better, and I wish it had module programming support and could trigger the resequence functions needed in the XJ6, an examination of several current threads right here points out it's value. AE (with extensions) will read transmission switch positions, ABS codes and sensor values, sensor feedback data fior seats, mirrors and control switches. It will even indicate current variable cam offset, and allow commanding vvt positin to test operation and feedback.
I own and have used ProScan, EASE, and all the ELM freeware, and am working on setting up my WDS. I believe the AutoEnginuity is the best deal for the serious DIY Jaguar mechanic due to its relative ease of use and pretty good functionality.

I am in no way connected with them or any other scanner software company.

 

The so called plug and play would be a wildcard. Different behaviour on every system, especially when power save features are factored in. Possibly different hardware assignment on every startup. If the vendor is not at least allowing for the changes of resource assignment, then life is going to be very difficult.

Lots of developers don't like doing hardware detection because .... well it's hard. Instead, they make assumptions.

Then you have dll hell. The developer has every piece of software known to man on his machine. When something goes wrong, his answer is "well it works on my machine". That's when a smart product manager throws the machine out the window.

 

SHl1980 -> Are you able to read the standard ODBII codes or only the systems from the expansion pack?

 

I have the pre-ProLine USB AE, with the jag enhancements.

It connects to the PCM over ISO or for extra features over CAN. It connects to various modules over ISO, SCP (PWM) or CAN, as needed. Some 100s of sensors etc.

It doesn't quite support ALL sensors and supports few actuators, but it's quite a feature set.

I found a bug in the early days of owning it, contacted support and they sent me a revised version to try, which worked fine. The later versions included the changes and "just worked". Yes, it can be slowish to connect but using the Get VIN feature it correctly works out the modules and protocols.

I've only had to reboot occasionally, frankly like so many other Windows apps - the common item being Windows. Cmon, it's junk and MS are never gonna fix it so I live with it when I have to (Linux all the rest of the time).

 

to dneider: I was able to read out so codes (P0420, U1260, B2290) so I guess it is capable of reaing thew OBDII codes. But I'm no expert, what I said is based on the fact that I was able to read and clear few codes.