Mongoose Pro and IDS 125.03
#1
![Default](/forum/images/icons/icon1.gif)
I bought the genuine Mongoose Pro cable and JLR IDS 125.03 (Ebay). Installed the IDS on a computer with Windows 7 Professional and installed the driver for the Mongoose Pro provided together with the IDS by the Ebay seller.
I am unable to see anywhere in the IDS that it is communicating via Mongoose Pro or any option where I can select Mongoose. So, the status is now as follows:
1. The computer recognises connection (and disconnection) of the Mongoose
2. The IDS starts and runs fine, I can go to the VIN page and manually enter the VIN of my car (no automatic reading of the VIN)
3. When I connect Mongoose to the OBD port, the "V" (volt) icon at the bottom right corner of the IDS turns green
4. I then start the "read the diagnostic trouble codes" and see message at the bottom of the screen "please wait"
5. The "padlock" icon to the left of the green "V" icon is red and shows a locked padlock
6. I left it in the "please wait" code reading stage for half an hour but nothing happened
I then aborted the process. Should I have waited longer? How long does it normally take?
I suspected that there was actually no communication through the Mongoose. I then checked all menus in the IDS but could not find anywhere that Mongoose is shown as the communication link. Under the blue icon which looks like a communication symbol at the top left corner of the IDS page, and under "information", when I expand the "VCM" it shows "Not Connected".
I would appreciate advice on how to ensure communication of the IDS through MongoosePro. Is there anything I should perform under "JLR" and/or "Drew Technologies Inc" folders in the computer "Start" and "All Programs" menu after completion of installation of the IDS and the Mongoose driver? I can see "MongoosePro JLR Configuration" in the "Drew Technologies Inc" folder but I did not do anything with it.
I am unable to see anywhere in the IDS that it is communicating via Mongoose Pro or any option where I can select Mongoose. So, the status is now as follows:
1. The computer recognises connection (and disconnection) of the Mongoose
2. The IDS starts and runs fine, I can go to the VIN page and manually enter the VIN of my car (no automatic reading of the VIN)
3. When I connect Mongoose to the OBD port, the "V" (volt) icon at the bottom right corner of the IDS turns green
4. I then start the "read the diagnostic trouble codes" and see message at the bottom of the screen "please wait"
5. The "padlock" icon to the left of the green "V" icon is red and shows a locked padlock
6. I left it in the "please wait" code reading stage for half an hour but nothing happened
I then aborted the process. Should I have waited longer? How long does it normally take?
I suspected that there was actually no communication through the Mongoose. I then checked all menus in the IDS but could not find anywhere that Mongoose is shown as the communication link. Under the blue icon which looks like a communication symbol at the top left corner of the IDS page, and under "information", when I expand the "VCM" it shows "Not Connected".
I would appreciate advice on how to ensure communication of the IDS through MongoosePro. Is there anything I should perform under "JLR" and/or "Drew Technologies Inc" folders in the computer "Start" and "All Programs" menu after completion of installation of the IDS and the Mongoose driver? I can see "MongoosePro JLR Configuration" in the "Drew Technologies Inc" folder but I did not do anything with it.
#2
![Default](/forum/images/icons/icon1.gif)
I think IDS will only work with the Rotunda VCM dongle, not the mongoose pro. I did read on here that the mongoose cable released originally will read codes but not configure the car.
It states 2005 up? It will work with the X350.
Rotunda VCM was designed for Jaguar's IDS (information driven diagnostics) Also, try V131 or whatever the last version was?
Mongoose was designed for Jaguar's follow-on support software, SSD (symptom driven diagnostics) from 05-present.
I suggest asking Cambo via p.m. if he has any ideas as he has experience with the mongoose and software.
One tip I would suggest is reinstalling the mongoose driver, this is usually done once IDS is installed, not the other way round.
It states 2005 up? It will work with the X350.
Rotunda VCM was designed for Jaguar's IDS (information driven diagnostics) Also, try V131 or whatever the last version was?
Mongoose was designed for Jaguar's follow-on support software, SSD (symptom driven diagnostics) from 05-present.
I suggest asking Cambo via p.m. if he has any ideas as he has experience with the mongoose and software.
One tip I would suggest is reinstalling the mongoose driver, this is usually done once IDS is installed, not the other way round.
Last edited by Sean B; 05-14-2018 at 11:47 AM.
#3
#4
![Default](/forum/images/icons/icon1.gif)
Thanks Sean and Bob.
Sme mode info - the specs for the MongoosePro I bought are as follows:
- Supports full factory diagnostics and reprogramming with JLR Diagnostics Program
- New VCI for the JLR IDS system
- Emissions Reprogramming: 1999 to current
- Body Control Reprogramming: 1999 to current
- OEM Diagnostics: 1999 to current
The Ebay seller of the IDS ("software_deals_uk") confirmed that the version 125.03 I bought works with VCM (not with VCM2) and with MongoosePro cable, genuine or clone.
My laptop is a 32 bit machine, Windows 7 Pro, as advised by the IDS seller and it has a 300 Gb disc space.
I have read most of the posts on this forum on the subject. Some members said the combination IDS 125 - MongoosePro does not work and some said it does. I am reluctant to experiment further with trying the configurations in the IDS or the Mongoose driver without some advise from someone who has got it to work as the IDS software easily gets "frozen" if you do something wrong and then you have to reinstall it (another half a day).
Sme mode info - the specs for the MongoosePro I bought are as follows:
- Supports full factory diagnostics and reprogramming with JLR Diagnostics Program
- New VCI for the JLR IDS system
- Emissions Reprogramming: 1999 to current
- Body Control Reprogramming: 1999 to current
- OEM Diagnostics: 1999 to current
The Ebay seller of the IDS ("software_deals_uk") confirmed that the version 125.03 I bought works with VCM (not with VCM2) and with MongoosePro cable, genuine or clone.
My laptop is a 32 bit machine, Windows 7 Pro, as advised by the IDS seller and it has a 300 Gb disc space.
I have read most of the posts on this forum on the subject. Some members said the combination IDS 125 - MongoosePro does not work and some said it does. I am reluctant to experiment further with trying the configurations in the IDS or the Mongoose driver without some advise from someone who has got it to work as the IDS software easily gets "frozen" if you do something wrong and then you have to reinstall it (another half a day).
#5
![Default](/forum/images/icons/icon1.gif)
I am still unable to get the MongoosePro work with IDS 125.03. Both are installed correctly but do not seem to communicate (the IDS does not see the Mongoose as its VCM). Or, perhaps, MongoosePro does not work with 1999 supercharged Jaguar (AJ26).
I have asked Drew Technologies for assistance 5 days ago but, so far, no rely (re-sent my email today). They do not appear to be as helpful (after you have bough their cable) as they advertise.
I have asked Drew Technologies for assistance 5 days ago but, so far, no rely (re-sent my email today). They do not appear to be as helpful (after you have bough their cable) as they advertise.
#6
![Default](/forum/images/icons/icon1.gif)
With great help/assistance from Cambo, I have clarified the issue with my genuine MongoosePro - IDS 125.03 combination which I tried to use on my 1999 AJ26 supercharged Jaguar (Daimler). The conclusion is as follows:
MongoosePro works with the SDD part of the v.125.03 but not with its IDS part or with any IDS. In the case of my 1999 model, the software (upon entering the VIN in the SDD) directs the session to IDS and that's where MongoosePro stops communicating with the car and can't do anything.
After a few inquiries with Drew Technologies, I received from them a confirmation that MongoosePro does not work with IDS but only with SDD. So, the advertised coverage of the MongoosePro of Jaguars "1999 to present" means "provided that they are SDD compatible". 1999 supercharged (AJ26) obviously requires IDS so a VCM must be used; as for 1999 NA (AJ27), it might be SDD compatible.
Did the switch from IDS to SDD take place for the first time with AJ27 engines?
Otherwise, the Ebay seller from whom I bought the MongoosePro ("racingpowersports" - Racing Powersports, Texas) was very kind and immediately accepted my request for a return of the cable and will issue a refund.
MongoosePro works with the SDD part of the v.125.03 but not with its IDS part or with any IDS. In the case of my 1999 model, the software (upon entering the VIN in the SDD) directs the session to IDS and that's where MongoosePro stops communicating with the car and can't do anything.
After a few inquiries with Drew Technologies, I received from them a confirmation that MongoosePro does not work with IDS but only with SDD. So, the advertised coverage of the MongoosePro of Jaguars "1999 to present" means "provided that they are SDD compatible". 1999 supercharged (AJ26) obviously requires IDS so a VCM must be used; as for 1999 NA (AJ27), it might be SDD compatible.
Did the switch from IDS to SDD take place for the first time with AJ27 engines?
Otherwise, the Ebay seller from whom I bought the MongoosePro ("racingpowersports" - Racing Powersports, Texas) was very kind and immediately accepted my request for a return of the cable and will issue a refund.
#7
Thread
Thread Starter
Forum
Replies
Last Post
abonano
PRIVATE For Sale / Trade or Buy Classifieds
3
04-23-2016 12:52 PM
juha_teuvonnen
XJ XJ6 / XJR6 ( X300 )
4
12-01-2014 02:41 PM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)