I have no idea, since I only have a Chinese knock-off... nothing to compare it to. I can only state that which I personally experienced.

 

And you definitely have one of these and not a red VCM?

 

And once you get it going, bad things can happen. I had a clone and could read VIN and other diagnostics. I went and updated some dealer settings on the security, and it failed to update the ECM VID block and bricked it. I eventually bought an original Drew cable and was able to complete the process. There are two communication channels to the car and it maybe that the Serial ecm bus is not supported by some clones.
Just my experience as a caution, maybe my clone supplier was more dodgy than others.

 

I removed JLR_IDS v125, set the date back to 11/30/2011 and installed all the JLR_SDD v130 files. I also removed and reinstalled the MongoosePro drivers. I ran SDD and entered the username and password that were listed in the offline authentication pdf, (JLR9A8172 and L538X760) and it said "Details for user identification JLR9A8172 have been successfully authenticated, press continue to begin session". the XP OS recognizes the MongoosePro and so does JLR_SDD; the interface icon is green and it knows it is a MongoosePro, the message at the bottom says "The Mongoose Pro JLR is connected", and the mongoose flashes green at one flash per second.

When I took it out to the SV8 and connected the mongoose to the OBDII and ran SDD, the interface icon was still green, the battery icon was yellow, but the upper right icon was red and still said "activation required" when I ran the cursor over it. It could not "READ" the VIN but took the entry manually and then asked for an "ignition on" test but returned a "Data Collection Error" with the ignition turned on to position II after clicking continue.

OK, So...I am one step further along, but still not communicating with the car except for the apparent reading of the battery voltage via the OBDII. Could the yellow battery icon be holding it back? Or is it the red X "activation required" icon? If it is the latter, is there some other entry needed to activate it off line?

I had just about figured out the menus for v125 but v130 is quite different, although I did find a screen for the interface and was able to capture the MongoosePro info in the picture below. I don't see a VCM recovery tool, but do see a MongooseProUpdater executable file and did a screen capture of its location. I haven't tried it because it seems that SDD is communicating with the Mongoose now, just not with the OBDII.

I am open to any suggestions. I'll try again tomorrow with a battery maintainer hooked up, but for some reason after several successfull VIN entries it is now telling me my VIN is invalid and I know I entered it correctly.

BTW, the pictures were captured inside away from the car so the battery icon is red in them. Oh, And what did you mean when you said "run the patch"? Would that be something within JLR_SDD 130?

 

Not sure if this may be contributing but check fuse #43 in passenger footwell


https://www.jaguarforums.com/forum/x...iences-148784/

 

a) unless you have done a complete reinstall of the OS, find the IDS removal tool on
the Ford site and run it to remove all traces of the first install. then consistently install
and run with an old date set in the clock.

b) you will never be able to get auto vin read for a X308. just won't happen.

 

Its for an X350 Plums.

The VCM recovery tool is in the start menu/all programs/JLR/IDS/Sub folder. See attached photo.

 

I haven't checked that fuse, but I do have battery voltage at the OBDII plug, as read by my UltraGage, and did have a yellow battery icon at the top of the SDD screen when the mongoose was connected to it.

Would I do a search for Ford IDS removal tool to find the right download site?

I used XP's add/remove programs to remove IDS v125 but had to delete the JLR folder from Program Files to remove the Additional Pinpoint Tests when it said it needed the IDS v125 to remove that program and I had already removed IDS 125 first; Got to remember to remove the additional pinpoint tests first in the future. I did set the date back to Nov 30, 2011 before installing SDD v130; it didn't fool XP Pro, though, which still said I had 21 days (more like 19 now) to activate it.

My car is an 06 X350 which I believe is in the v130 fully supported list; well, before it decided mine was an invalid VIN, that is.

I charged the SV8's battery yesterday, but haven't tried the SDD again yet. I've been busy repairing injector, headlight, and sensor wiring that a rat ate in our Dodge mini-van when it set up housekeeping in the under hood insulation. I had pulled a bunch of nesting material and half eaten nuts out of the lining and was removing the blanket itself when I came face to face with an 8 inch rat (that's body length not including the tail). It scuttled under the part of the blanket that was still up and I went and got a dip net and tried to catch it and almost did, but it wiggled out and ran under the van. They love to nest in the center of XK6 engines between the cam covers and eat spark plug wires too. I hate rats!

 

For those interested.

I just received the new MongoosePro (clone) I ordered after my original Mongoose (non Pro) died on me. I asked the question if this version, which the seller calls 1.42, would work with the older SDD 1.31 version. I prefer to keep that version because it doesn't need patches or anything. Didn't get an answer but I thought it would.

The clone comes with 1 DVD with version 1.39 of the software (including Mongoose driver and stuff for Mazda and Ford). Also with 3 DVD's with the 1.42 version (including Mongoose driver and serial).

I deleted the old Mongoose driver from my VirtualBox with SDD V1.31.3 and installed the one from the 1.39 DVD and the SDD works fine again with the new MongoosePro.

The version I bought is also named Version SP205 by the seller.

 

So the new MongoosePro clone works with your version 1.31 software And you used the driver from the JLR 1.39 DVD (DVD named SDD_DVD139)?

Is your software activated (beacon icon in the upper right is green)? And if so how did you do it? My V130 said it had been successfully authenticated when I entered the user and password, but the little beacon icon is red and says "activation required" when I cursor over it. I am assuming that is why my Mongoose Pro does not communicate with the OBDII beyond showing a yellow battery icon.

Did you run anything from the Patch folder on the 139 DVD? I was just looking at the files in that folder on the DVD and got a virus warning from Avira just now.

 

I bought my 1.31 on Ebay and it came with an userid and password. No patches required. The beacon is red and states it's activated but not confirmed. I don't remember for sure if it was the same on with the old Mangoose but I think it has always been red. It does work though. Mine came with the instruction that when I wanted to use the calibration files the computer date should be set to august 2012 before installing those.

I don't let the computer connect to internet while my VM with SDD is running (maybe that's the reason it isn't confirmed and I always set the date back to the original install date to avoid the software from deactivating certain functions. I didn't do that the first time I installed it and after a certain number of days certain functions in SDD stopped working.

This time I also didn't run any patches of the SDD_DVD139 either.

 

Thanks, I had set my date earlier than that when I installed V130 so maybe I need to use Aug 2012. I used the M-Pro driver I downloaded so perhaps I need to remove it and try running the one from the DVD; seems like they were the same size files, but perhaps not exactly the same. My old Sony does not have an internal wireless so it can't connect to the net without a card and I've removed the card.

Sure would like to get the mongoose to communicate to read the chassis codes; I get an air suspension fault message 50 to 60% of the time and when I counted the codes that can cause it there were 35 different ones.

 

From the instructions I got the impression the date is only relevant for the calibration files, not the SDD software itself. However I noticed on previous installs of the SDD software that it uses the date to check how old it gets and disables functions. Always setting the date back to the original install date solves that.

I would stick to the V1.30 version with the MPro driver from the V1.39 DVD you've got.

 

A convenient way not to have to set back the date is to block it within your windows OS.
I did that for my SDD dedicated PC (XP Pro SP2 fresh install, v 130 and calibration files bought separately on ebay, clone non-pro Mongoose) and never need to reset it.