My SDD (134.04) indicates that I have an "Invalid VIN"? Have attempted several searches on the Forum to no avail. I am loosing my patience on this *#*# software.
Note: It will not let me enter the VIN manually and when I click on "Continue", it goes back to the "VIN search window" and repeats.

 

Did you install the vehicle database ?

Do other VINs work ?

 

I am under the impression that you can't use any version after v131 without a Topix suscription.

 

A gent in the UK informed me that my version will only work on 2005-2011 vehicles.

 

I dont believe that.
When I bought mongoose, they also claimed 2005+. But it works perfect with my 2003 X350.

 

Is this the cloned & cracked software? Kinda points to a foul up but not perhaps the software's fault!

 

I have version v134.04 running with a Mongoose clone and am not planning a TOPIx sub unless I win the lottery.

Graham

 

Yes it is, from UOBD2....

 

I'm having this same issue with not only my v134 that I am trying to get to work with my 2011, but after I uninstalled it and went back to v130, I still can't get either of my vehicles to identify the VIN, whether it was read or typed manually.

My v134 did let me download 40 files of as-built & calibration files...which was something my v130 NEVER allowed me to do. However, it only let me do this download one time using the Software Management utility. Every other time, it tried 3 times and gave me an error.

Reyes, did you ever find a fix?

 

Have you tried the vin scan with the ignition on position II?

I can confirm V125 up to and including V141 works on the 2004 X350

Versions released after 2010 will identify the VIN, then reconfigure for "Legacy Pre 2010" vehicles then continue on

The Best version by far is 125 as you have access to IDS and SDD in the one system

Cheers
34by151

 

Hi reyesl,

I am running V134 successfully on our '04 XJR, even though the vendor, UOBD2, told me it would only work on 2005 and later cars.

I find that the program only works properly if I turn of all Internet connections and set the date of the computer master clock to sometime in August 2012. I once let the clock advance to November 2012 and the software functionality was disabled and gave me an error message along the lines of: "It has been too long since the software was updated."

Another possibility is low battery voltage. If resetting the master clock date doesn't work, you might check your batt voltage. For any long SDD sessions, I connect our portable battery booster (the Jag Workshop Manual says to use a very high-end battery charging system that costs hundreds of dollars, but our $100 Schumacher booster seems to work fine).

Cheers,

Don

 

I had the same issue today where the SDD could not read VIN because it said there was no connection.
I moved the cable to a different USB port and it worked fine and read the VIN.

 

After little sleep last night, and much determination...I was able to get my v134 to read and identify both of my cars this morning. I uninstalled everything, then re-installed...making sure my date was August 8, 2012, applied the license file shared over at the jaguarforum.uk (also connected to that same date, I presume), and presto!!... all is good. It seems to run a bit faster than v130 too. Less time in between program functions. No internet needed as once suspected, either.

I was able to clear my tranny adaptations and the 'service required' light on my 2011.

PS, I'm going to put all of the files and some instructions needed on my FTP server if anyone wants to give it a try themselves.

 

My v131.03 worked like a breeze on my X350 of 2004 since I succeeded installing it on a dedicated laptop with XP-SP2, no internet connexion and a clock blocked on a date of August 2012.
Blocking the clock is easy to do and provides peace of mind.

 

It's Java issue.
Uninstall all installed JRE and install JRE v. 1.6.0_26 (it is the only version supported by SDD)

 

I've had it several times that a version initially works good but after a while it refuses to read the VIN as well as decode the manually entered VIN while the clone Mongoose is connected. Disconnecting the Mongoose before manually entering the VIN works and usually it starts working again after a fresh install of SDD.

My clone died on me so I have to get another clone, the real version or maybe a VCM. It would be nice to have a proper interface so one can rule that out as part of any problems.

Guus

 

nebelfuerst:

What do you mean by "Did you install the vehicle database ?" How do you do that step?

Thanks

 

Wondering myself, think they are changing the programing on the computer.

 

I purchased another clone copy (V131.00 v.113) and installed it on a Panasonic CF-29 Toughbook. Several hours later, and after connecting my battery tender, everything is working fine. I used it to troubleshoot the transmission and brake problems my VDP had for several weeks.