As far as I know, there is only one local member with a cable, I was thinking about messaging him and doing exactly as you suggest. Worth a shot!

 

Let us know how it goes

Cheers
34by151

 

First off, big thanks to rickpwilson for letting me try his mongoose and meeting a fellow Jag fan.

Now, guess what, his cable works fine. Connects to car, reads the VIN and no error, confirming my cable is duff. Unfortunately, both our SDD programs were acting up (probably needs another install) so we couldn't diagnose my ACC issue, but did come to the decision that the problem isn't the cruise module itself but likely a sensor or switch somewhere (but that's another story).
The other interesting thing I noticed was that when I plugged in his cable, my computer said new hardware installed and found the drivers again. Also, I noticed that while my cable is a normal mongoose, it doesn't use the normal drivers, only the Pro ones. Maybe that has something to do with it. And I noticed on other threads with bad cables, the serial number on them was 000442, the same as mine. I guess don't buy a normal one, only a Pro is the lesson here! I think I'm going to just ask for a refund on mine and order a Pro instead since they seem to work.

 

Hi!
Just want to fill in some info. My Mongoose has serial 000442 and I am using driver version 1.2.12.0 It works on both XP and W7. Firmware revision is reported as 01.10 The full name is reported as Mongoose JLR SAE J2534 USB OBD-II Interface
So at least some of them works...

 

I have both sets of drivers PM me you details and I send both versions to you

All the clones have the serial number 000442

Cheers
34by151

 

I'm not an expert, but IIRC in the long thread on the Clone Mongoose, it was advised not to update the drivers with the Pro version.
I understand that it may fry your device.
Could that be a reason for your Mongoose not to work?

 

34by151 PM sent!

Well its good to hear that some of the 000442 clones work! lol
I am actually using the drivers that they told me to use and that come with the cable, and upon digging they appear to be the Pro ones. I'll have to try the other drivers and see what happens. Also, when the cable is plugged in the computer says mongoose pro detected, even though it isn't.

I believe that the problem wasn't using the pro drivers, but trying to update the firmware of the cable to Pro, which I haven't done. And that totally fried the cable, as in no lights or anything when plugged into the computer, mine still lights up and everything.

I'll give a fresh install with the proper drivers a try and see what happens. But this is the last attempt, if this still doesn't do it, its back to China!

 

I do not use the driver that came with the cable any more. I used it the first time. The installation prog was in Chinese, but we know about where the "Install" and "cancel" buttens are located so that's ok. The real problem started when the laptop refused to boot. After some investigation I discovered that the chinese mongo driver deleted the ntldr file on disk. It happend suddenly after a few minutes when the laptop was idle. When I uninstalled the driver package all was well again. I found another driver somwhere and after that things have been stable. (WinXP Pro SP3)

The cost of the Mongoose is down to 40$ now and from my country that is about the cost for returning it! I asked the chinese pusher some time ago what is the difference between the different models. (not pro) The answer was "Not much different, but they come from different factories")

 

Alright, with the help of 34by151, I got the good drivers, installed them and still no go. In fact, now it says wrong device connected when I load up SDD. So that's that. Back it goes. Because of how long it would take to send back and wait for a replacement, I'm considering just going through PayPal to get my money back and ordering a new one! Anyway, at least there is no doubt that the cable is bad.

 

I got a defective flasher from these guys some time back: obd2express.co.uk but they gave me full refund without problems. (Well exept for the shipment cost for the defective unit.)

 

Well, I just got the cost to send the cable back to China with tracking. It costs the same that I paid for it! So, I just sent of a email to uobd2 and I'll see what they say. It would cost the same to just buy another cable. I'm hoping they will find a way to work something out or I might have to go to PayPal in the end. I figured I'll buy a Pro this time since more of them seem to work!
At this rate, I may never sort out my ACC issue.