Best X350 Scanner?? (for C codes, etc)
#22
Yep, there are still some high quality laptop scanners out there that will get you close to everything you need, but as the article basically says, you get what you pay for. You might not get a serious drill down, but with vehicles this age, there is enough information on this forum and collective experience to solve virtually any problem.
The hand helds can be touchy and even adversely affect systems, (regardless of vehicle) as there are too many modules on our cars to read them all accurately (again you get what you pay for.)
You've clearly spent significant time just researching your scanner options, so I'm sure you'll find the right fit.
If you want to re-flash stuff (well your just asking for trouble) but you need to go OEM.
Let us know what you end up deciding.
The hand helds can be touchy and even adversely affect systems, (regardless of vehicle) as there are too many modules on our cars to read them all accurately (again you get what you pay for.)
You've clearly spent significant time just researching your scanner options, so I'm sure you'll find the right fit.
If you want to re-flash stuff (well your just asking for trouble) but you need to go OEM.
Let us know what you end up deciding.
#23
I learned I know nothing about scanners
Yep, there are still some high quality laptop scanners out there that will get you close to everything you need, but as the article basically says, you get what you pay for. You might not get a serious drill down, but with vehicles this age, there is enough information on this forum and collective experience to solve virtually any problem.
The hand helds can be touchy and even adversely affect systems, (regardless of vehicle) as there are too many modules on our cars to read them all accurately (again you get what you pay for.)
You've clearly spent significant time just researching your scanner options, so I'm sure you'll find the right fit.
If you want to re-flash stuff (well your just asking for trouble) but you need to go OEM.
Let us know what you end up deciding.
The hand helds can be touchy and even adversely affect systems, (regardless of vehicle) as there are too many modules on our cars to read them all accurately (again you get what you pay for.)
You've clearly spent significant time just researching your scanner options, so I'm sure you'll find the right fit.
If you want to re-flash stuff (well your just asking for trouble) but you need to go OEM.
Let us know what you end up deciding.
#24
If you use JLR IDS V118 there is no software updates, no hacking to make it work, but yes you need a laptop, and a VCM (a proper one not a Chinese clone).
IDS V118 is the same software used by JLR dealers in 2009, does everything on an X350.
No it's not cheap, but in my eyes it's a "good diagnostic tool solution" because it works and it's fully functional. Yes you need to take your time to set it up properly on a good, clean, laptop, get a decent battery charger, etc...
Anything else is going to be a compromise of some sort.
Fast, Cheap, Good, you can't have all three!
The following users liked this post:
hisport (08-15-2016)
#25
Well I purchased this unit: VXDIAG VCX NANO SSD V141 for Land Rover and Jaguar 2 in 1. On Ebay for $86 including shipping from Canada.
I suppose it will fail at some point however I have it up and running and have found a failure in my front parking sensors which I was only vaguely aware of. There are other DTCs that I have to explore which maybe connected to problems I had with the supercharger swapping in and out.
I had to convert my laptop to Windows 7 from WXP. Had the disk so no sweat there.
Instructions are very "sparse" . Took some figuring out how to load and what to load from 5 CDs. That took many hours.
At least I could walk away and come back later and only once did I get a niggling query icon that needed an answer to continue.
So I already notice significant improvement over the older JLR SDD kit that I had.
By improvement I mean that I see many more options and detail on DTCs detected.
It is early days yet with a lot to learn.
I suppose it will fail at some point however I have it up and running and have found a failure in my front parking sensors which I was only vaguely aware of. There are other DTCs that I have to explore which maybe connected to problems I had with the supercharger swapping in and out.
I had to convert my laptop to Windows 7 from WXP. Had the disk so no sweat there.
Instructions are very "sparse" . Took some figuring out how to load and what to load from 5 CDs. That took many hours.
At least I could walk away and come back later and only once did I get a niggling query icon that needed an answer to continue.
So I already notice significant improvement over the older JLR SDD kit that I had.
By improvement I mean that I see many more options and detail on DTCs detected.
It is early days yet with a lot to learn.
Last edited by jackra_1; 08-14-2016 at 06:25 PM.
The following users liked this post:
hisport (08-15-2016)
#27
#28
It is "limited" functionality because I am using it off-line since I do not want to pay a subscription. Also a time limit on using it this way.
We will see if I can overcome that time limit easily or not.
If I remember correctly the JLR SDD had a similar time limit.
When I first hooked it up I had to enter my VIN manually, unlike the JLR SDD.
Once I did it when thru a reconfiguration. Something to do with models pre 2010.
The following users liked this post:
hisport (08-15-2016)
#29
Folks:
Just FYI, I ordered an NT 510 Foxwell handheld scanner from Amazon Prime (so I can return it if required). $180. Yes, its a compromise.
Tried it yesterday; it does seem to read all (16 or so) Jag (07 XJR) modules. Found that I have (mostly historic) DTC's in most of them
The "drain the swamp" objective behind all this was to properly diagnose why the rear of my XJR is in "low rider" mode (yet front is OK)
In a nutshell, the associated chassis DTC (non plausible height sensor) doesn't say much beyond the obvious, yet looking through the related "live data" quickly allowed me to see that the air compressor is working properly, and the reservoir pressure builds to correct level, etc, yet bleeds down slowly once the engine is turned off. So, I can now proceed with the workshop manual troubleshooting sequence in a reasonable way
I will now see if the NT 510 will allow me to follow bidirectional workshop manual stuff (eg, place in transportation mode; reset ride height for each corner) as I further troubleshoot
If there's interest in the NT510, I'll update here once I get a little further forward
Thanks for all your help along the way...
Just FYI, I ordered an NT 510 Foxwell handheld scanner from Amazon Prime (so I can return it if required). $180. Yes, its a compromise.
Tried it yesterday; it does seem to read all (16 or so) Jag (07 XJR) modules. Found that I have (mostly historic) DTC's in most of them
The "drain the swamp" objective behind all this was to properly diagnose why the rear of my XJR is in "low rider" mode (yet front is OK)
In a nutshell, the associated chassis DTC (non plausible height sensor) doesn't say much beyond the obvious, yet looking through the related "live data" quickly allowed me to see that the air compressor is working properly, and the reservoir pressure builds to correct level, etc, yet bleeds down slowly once the engine is turned off. So, I can now proceed with the workshop manual troubleshooting sequence in a reasonable way
I will now see if the NT 510 will allow me to follow bidirectional workshop manual stuff (eg, place in transportation mode; reset ride height for each corner) as I further troubleshoot
If there's interest in the NT510, I'll update here once I get a little further forward
Thanks for all your help along the way...
The following 2 users liked this post by hisport:
joeldietzjr (01-22-2017),
Sean W (08-15-2016)
#32
Big problem with the VXDIAG.
I cannot get by the time limit of just a few days built in to the "evaluation" period for this software.
Looks like you have to have a dealer level ID that can be validated for this product to work.
Now I did not load all of the files on all of the disks. I will complete all of that and see what happens. I somehow doubt that will solve the problem.
If that turns out to be true then the only way to use this product for the DIY person is to reinstall everything on the day you want to use it. Would give you 2 days of use unless of course some register in the operating system is used by this software.
Will find out over the next few days.
Found a 2016 Youtube video on how to install. It shows Windows XP which would not work with my install??
I cannot get by the time limit of just a few days built in to the "evaluation" period for this software.
Looks like you have to have a dealer level ID that can be validated for this product to work.
Now I did not load all of the files on all of the disks. I will complete all of that and see what happens. I somehow doubt that will solve the problem.
If that turns out to be true then the only way to use this product for the DIY person is to reinstall everything on the day you want to use it. Would give you 2 days of use unless of course some register in the operating system is used by this software.
Will find out over the next few days.
Found a 2016 Youtube video on how to install. It shows Windows XP which would not work with my install??
Last edited by jackra_1; 08-16-2016 at 11:21 AM.
#34
The software is the reason I keep harping on about using a VCM and IDS V118.
It just works. There's no hacks, no fixes, no time-outs, no expiration.
There are probably ways around the issues you raise Jackra but ultimately you are still working with a clone of a clone from the hardware side of things so even if you get the software sorted out and stable, the device itself can always crap out.
Regarding the operating systems.
You must use a 32-bit OS for any version of IDS or SDD.
It does not have to be WinXP Pro, can also be Win7 Pro.
Actually Win7 Pro 32-bit is what I use for everything, and it's fine. IDS/SDD versions 118, 125, 134 and the latest ones 144 onward. Even the old Land Rover T4 software is running fine in Win7 Pro 32-bit.
It just works. There's no hacks, no fixes, no time-outs, no expiration.
There are probably ways around the issues you raise Jackra but ultimately you are still working with a clone of a clone from the hardware side of things so even if you get the software sorted out and stable, the device itself can always crap out.
Regarding the operating systems.
You must use a 32-bit OS for any version of IDS or SDD.
It does not have to be WinXP Pro, can also be Win7 Pro.
Actually Win7 Pro 32-bit is what I use for everything, and it's fine. IDS/SDD versions 118, 125, 134 and the latest ones 144 onward. Even the old Land Rover T4 software is running fine in Win7 Pro 32-bit.
#35
I have a PLX Kiwi (drive green model I believe) that I bought years ago. It has been able to read and clear the codes that I have gotten so far on my Jaguar. It doesn't give in depth info, but at least gives the code, so you know where to start looking. I think it was $300 back when I bought it, probably a heck of a lot cheaper now.
#36
The software is the reason I keep harping on about using a VCM and IDS V118.
It just works. There's no hacks, no fixes, no time-outs, no expiration.
There are probably ways around the issues you raise Jackra but ultimately you are still working with a clone of a clone from the hardware side of things so even if you get the software sorted out and stable, the device itself can always crap out.
Regarding the operating systems.
You must use a 32-bit OS for any version of IDS or SDD.
It does not have to be WinXP Pro, can also be Win7 Pro.
Actually Win7 Pro 32-bit is what I use for everything, and it's fine. IDS/SDD versions 118, 125, 134 and the latest ones 144 onward. Even the old Land Rover T4 software is running fine in Win7 Pro 32-bit.
It just works. There's no hacks, no fixes, no time-outs, no expiration.
There are probably ways around the issues you raise Jackra but ultimately you are still working with a clone of a clone from the hardware side of things so even if you get the software sorted out and stable, the device itself can always crap out.
Regarding the operating systems.
You must use a 32-bit OS for any version of IDS or SDD.
It does not have to be WinXP Pro, can also be Win7 Pro.
Actually Win7 Pro 32-bit is what I use for everything, and it's fine. IDS/SDD versions 118, 125, 134 and the latest ones 144 onward. Even the old Land Rover T4 software is running fine in Win7 Pro 32-bit.
How much is a VCM and where is the best place to buy one?
#38
Dave,
Are you saying that the PLX Kiwi will read the proprietary Jaguar C (Chassis), B (Body) and U (Undefined, mostly network-related) codes? Or will it only read the standard P (Powertrain) codes that most OBDII scanners can read?
Cheers,
Don
The following users liked this post:
AD2014 (08-26-2016)
#39
Sorry Don, I guess I should have clarified. I have only had 2 engine codes and a suspension fault since I got this car, and it could read all of them. I cannot say for sure if it can read other codes beyond that. The other cars that I have used it on for code reading (Ford, GM, Dodge, etc) have always been engine faults.
Sorry, hope I didn't cause any confusion.
Sorry, hope I didn't cause any confusion.
#40
Thanks for the clarification, Dave!
FYI, you can download the full DTC Summaries manual at the link below, which will show you nearly all of the diagnostic fault codes your Jag can store. By law, most of the Powertrain codes must be readable by a generic OBDII scanner, but the C, B, U and possibly some of the P codes are proprietary to Jaguar and require a scanner capable of reading them. The scanner's electrical connector also must have the two additional pins used by Jaguar but missing from the connectors of most OBDII scanners.
Here's the link to the DTC Summaries manual:
https://www.google.com/url?sa=t&rct=...03388427,d.cWw
Cheers,
Don
FYI, you can download the full DTC Summaries manual at the link below, which will show you nearly all of the diagnostic fault codes your Jag can store. By law, most of the Powertrain codes must be readable by a generic OBDII scanner, but the C, B, U and possibly some of the P codes are proprietary to Jaguar and require a scanner capable of reading them. The scanner's electrical connector also must have the two additional pins used by Jaguar but missing from the connectors of most OBDII scanners.
Here's the link to the DTC Summaries manual:
https://www.google.com/url?sa=t&rct=...03388427,d.cWw
Cheers,
Don