Legacy (IDS) not opening
#1
![Default](/forum/images/icons/icon1.gif)
Hello All!
I have searched this topic and have yet to find the answer. It has been discussed, but not resolved...that I could find.
First off, I have a 1995 XJ12, which is an X305. I have placed this topic in X300 hoping to get more exposure. I have an HP G62 32 bit laptop running Windows XP Pro and Internet Explorer 8. After a clean install of Windows I loaded SDD version 138. The interface module is a DA-VINA 2534. I selected the DA-VINA because it is one of the few that will work back to 1995.
When everything is plugged in, the software indicates that the DA-VINA is plugged in. As this vehicle is older, the software cannot detect the VIN; this is expected. I key in the VIN, the software correctly states that SDD will not work and to click on the link to go to IDS. When I click the link, the IDS splash screen opens for an instant and goes away...and that's it. I can't get past this point. I have tried running tabman.exe directly from Windows Explorer, but the same thing happens.
I am at a loss! Has anyone solved this problem yet?
Thank you for any help you can offer!
I have searched this topic and have yet to find the answer. It has been discussed, but not resolved...that I could find.
First off, I have a 1995 XJ12, which is an X305. I have placed this topic in X300 hoping to get more exposure. I have an HP G62 32 bit laptop running Windows XP Pro and Internet Explorer 8. After a clean install of Windows I loaded SDD version 138. The interface module is a DA-VINA 2534. I selected the DA-VINA because it is one of the few that will work back to 1995.
When everything is plugged in, the software indicates that the DA-VINA is plugged in. As this vehicle is older, the software cannot detect the VIN; this is expected. I key in the VIN, the software correctly states that SDD will not work and to click on the link to go to IDS. When I click the link, the IDS splash screen opens for an instant and goes away...and that's it. I can't get past this point. I have tried running tabman.exe directly from Windows Explorer, but the same thing happens.
I am at a loss! Has anyone solved this problem yet?
Thank you for any help you can offer!
#2
#3
![Default](/forum/images/icons/icon1.gif)
When you say IDS, did you buy the old IDS software or a complete IDS system?
#4
![Default](/forum/images/icons/icon1.gif)
Hello Engineer,
I have a years-old generic OBDII scanner that reads and clears the P codes just fine on the XJ12. Were you attempting to dig deeper into the ECU or other areas, or are you troubleshooting a problem?
The software of these old cars is about as capable as a Windows PC in 1995. Not very!
I have a years-old generic OBDII scanner that reads and clears the P codes just fine on the XJ12. Were you attempting to dig deeper into the ECU or other areas, or are you troubleshooting a problem?
The software of these old cars is about as capable as a Windows PC in 1995. Not very!
#5
#6
![Default](/forum/images/icons/icon1.gif)
Hello Engineer,
I have a years-old generic OBDII scanner that reads and clears the P codes just fine on the XJ12. Were you attempting to dig deeper into the ECU or other areas, or are you troubleshooting a problem?
The software of these old cars is about as capable as a Windows PC in 1995. Not very!
I have a years-old generic OBDII scanner that reads and clears the P codes just fine on the XJ12. Were you attempting to dig deeper into the ECU or other areas, or are you troubleshooting a problem?
The software of these old cars is about as capable as a Windows PC in 1995. Not very!
I want to dig deeper into the various controllers. I am assuming I can see the potentiometers for the seats and steering column.
#7
Trending Topics
#8
![Default](/forum/images/icons/icon1.gif)
I personally don't think any of the SDD versions will read a 1995MY Jaguar but I don't know. The original IDS with VCM probably will.
I can communicate with 1995 XJ6 with my WDS but I have not worked on an XJ12 in YEARS!!!!!!!!
bob
#9
#10
#11
![Default](/forum/images/icons/icon1.gif)
It sounds like you have solved this issue by using WDS. Can WDS software be loaded on a generic laptop?
#12
![Default](/forum/images/icons/icon1.gif)
To make sure I understand, you have the software but no hardware to interface between the car and the laptop? Is the disk you purchased a genuine Jaguar disk?
#13
![Default](/forum/images/icons/icon1.gif)
IDS will load onto any laptop running Windows XP PRO Service Pack 2.
Back in 2006 I had a Pentium III 900mhz Toshiba XP PRO with DVD43, DVD101, DVD102 and DVD103 (upgraded in succession). I used the Jag shop VCM with my Toshiba instead of the Panasonic TOUGHBOOK. It worked FINE as long as the Toshiba and ToughBook used the same version of DVD IDS. (The VCM did not care what laptop was used)
WDS will load onto a laptop (maybe) but the Vehicle Communication Module is BUILT-INTO the Genrad GDS 3500 PTU of WDS. They are a unit, the front is a Pentium I 233mhz computer and the back half is a VCM.
Legacy IDS on SDD138 will probably NOT recognize a VIN from an X300.
SDD 118.5 will NEED a VCM and a laptop with USB port. A Mongoose will not support software older than a certain version (128 I THINK??)
Engineer1, Your SDD is likely TOO late of a version for the X300.
smgdata, You need a VCM between your laptop and the vehicle.
Both of you could use a WDS for all Jaguars 1995/96 up to about 2007MY.
You could also use a PDU (if you can find a working unit) for 1990 to 2001MY Jaguars.
bob
Back in 2006 I had a Pentium III 900mhz Toshiba XP PRO with DVD43, DVD101, DVD102 and DVD103 (upgraded in succession). I used the Jag shop VCM with my Toshiba instead of the Panasonic TOUGHBOOK. It worked FINE as long as the Toshiba and ToughBook used the same version of DVD IDS. (The VCM did not care what laptop was used)
WDS will load onto a laptop (maybe) but the Vehicle Communication Module is BUILT-INTO the Genrad GDS 3500 PTU of WDS. They are a unit, the front is a Pentium I 233mhz computer and the back half is a VCM.
Legacy IDS on SDD138 will probably NOT recognize a VIN from an X300.
SDD 118.5 will NEED a VCM and a laptop with USB port. A Mongoose will not support software older than a certain version (128 I THINK??)
Engineer1, Your SDD is likely TOO late of a version for the X300.
smgdata, You need a VCM between your laptop and the vehicle.
Both of you could use a WDS for all Jaguars 1995/96 up to about 2007MY.
You could also use a PDU (if you can find a working unit) for 1990 to 2001MY Jaguars.
bob
The following users liked this post:
Engineer1 (03-15-2016)
#14
![Default](/forum/images/icons/icon1.gif)
If you have a J2534 device (i.e. MongoosePro, DA-VINA) then the oldest version of IDS/SDD you can use is V125, and the most commonly used from that period is V125.03 since that was the last version that you could run IDS independently of SDD (just copy the Tabman.exe link to the desktop and you have IDS).
BUT
IDS V125.03 with a J2534 interface still has some issues, namely a bug in reading DTC's, often IDS will crash when you try to read the codes. The way around this is to start SDD (so the front page is open) and then start IDS.
But there are some other traps too. For example you MUST use an older version of Java (not the latest, it's incompatible), you need to disable the SDD updates or it will lock out, and so on...
Don't waste your time with cheap Chinese clone of Mongoose or DA-VINA, they are junk, and if they fail at the wrong time (and they will fail) you could be left with a very large paperweight of a vehicle.
For working on an X300 (or X305) you really want to use a VCM, and the last version of IDS as a standalone, which is V118.5.
Or use a WDS. Or a PDU...
Yes they are not cheap, yes they are hard to find, but they are the only reliable options for vehicles of that era. Forget what you read about the latest versions and interfaces being compatible, they're not. The JLR Diagnostic Team does not care about these old cars. For JLR Diagnostics a "heritage vehicle" is pre-2010, post 2005. Yep, really...
Anything prior to 2005 they don't care about anymore. So you need to use old software/equipment on old cars if you want something to work reliably.
BUT
IDS V125.03 with a J2534 interface still has some issues, namely a bug in reading DTC's, often IDS will crash when you try to read the codes. The way around this is to start SDD (so the front page is open) and then start IDS.
But there are some other traps too. For example you MUST use an older version of Java (not the latest, it's incompatible), you need to disable the SDD updates or it will lock out, and so on...
Don't waste your time with cheap Chinese clone of Mongoose or DA-VINA, they are junk, and if they fail at the wrong time (and they will fail) you could be left with a very large paperweight of a vehicle.
For working on an X300 (or X305) you really want to use a VCM, and the last version of IDS as a standalone, which is V118.5.
Or use a WDS. Or a PDU...
Yes they are not cheap, yes they are hard to find, but they are the only reliable options for vehicles of that era. Forget what you read about the latest versions and interfaces being compatible, they're not. The JLR Diagnostic Team does not care about these old cars. For JLR Diagnostics a "heritage vehicle" is pre-2010, post 2005. Yep, really...
Anything prior to 2005 they don't care about anymore. So you need to use old software/equipment on old cars if you want something to work reliably.
The following 4 users liked this post by Cambo:
#15
![Default](/forum/images/icons/icon1.gif)
Cambo is correct.
We used to keep one of our SDD units back to just before SDD2 came out, but in later versions the VCM would have to reload the code every time you switched.
We can use the latest SDD version with a 1995 XJS (just did it last week), but a VCM is needed. Mongoose is best used on vehicles with PanPAG and later ECUs.
If you have the software, just reload the whole thing. It's not that difficult. It will take you longer to figure out why it doesn't load, than just starting fresh.
IDS/SDD gets slogged down after a while, and can become unpredictable.
I reload all our SDDs completely once every few years; sometimes earlier if there's unpredictable behavior.
We used to keep one of our SDD units back to just before SDD2 came out, but in later versions the VCM would have to reload the code every time you switched.
We can use the latest SDD version with a 1995 XJS (just did it last week), but a VCM is needed. Mongoose is best used on vehicles with PanPAG and later ECUs.
If you have the software, just reload the whole thing. It's not that difficult. It will take you longer to figure out why it doesn't load, than just starting fresh.
IDS/SDD gets slogged down after a while, and can become unpredictable.
I reload all our SDDs completely once every few years; sometimes earlier if there's unpredictable behavior.
The following users liked this post:
Engineer1 (03-15-2016)
#16
![Default](/forum/images/icons/icon1.gif)
If you have a J2534 device (i.e. MongoosePro, DA-VINA) then the oldest version of IDS/SDD you can use is V125, and the most commonly used from that period is V125.03 since that was the last version that you could run IDS independently of SDD (just copy the Tabman.exe link to the desktop and you have IDS).
BUT
IDS V125.03 with a J2534 interface still has some issues, namely a bug in reading DTC's, often IDS will crash when you try to read the codes. The way around this is to start SDD (so the front page is open) and then start IDS.
But there are some other traps too. For example you MUST use an older version of Java (not the latest, it's incompatible), you need to disable the SDD updates or it will lock out, and so on...
Don't waste your time with cheap Chinese clone of Mongoose or DA-VINA, they are junk, and if they fail at the wrong time (and they will fail) you could be left with a very large paperweight of a vehicle.
For working on an X300 (or X305) you really want to use a VCM, and the last version of IDS as a standalone, which is V118.5.
Or use a WDS. Or a PDU...
Yes they are not cheap, yes they are hard to find, but they are the only reliable options for vehicles of that era. Forget what you read about the latest versions and interfaces being compatible, they're not. The JLR Diagnostic Team does not care about these old cars. For JLR Diagnostics a "heritage vehicle" is pre-2010, post 2005. Yep, really...
Anything prior to 2005 they don't care about anymore. So you need to use old software/equipment on old cars if you want something to work reliably.
BUT
IDS V125.03 with a J2534 interface still has some issues, namely a bug in reading DTC's, often IDS will crash when you try to read the codes. The way around this is to start SDD (so the front page is open) and then start IDS.
But there are some other traps too. For example you MUST use an older version of Java (not the latest, it's incompatible), you need to disable the SDD updates or it will lock out, and so on...
Don't waste your time with cheap Chinese clone of Mongoose or DA-VINA, they are junk, and if they fail at the wrong time (and they will fail) you could be left with a very large paperweight of a vehicle.
For working on an X300 (or X305) you really want to use a VCM, and the last version of IDS as a standalone, which is V118.5.
Or use a WDS. Or a PDU...
Yes they are not cheap, yes they are hard to find, but they are the only reliable options for vehicles of that era. Forget what you read about the latest versions and interfaces being compatible, they're not. The JLR Diagnostic Team does not care about these old cars. For JLR Diagnostics a "heritage vehicle" is pre-2010, post 2005. Yep, really...
Anything prior to 2005 they don't care about anymore. So you need to use old software/equipment on old cars if you want something to work reliably.
Your comment regarding V125 being the last version that the Legacy IDS version works just blows me away! I don't understand why the software carries the IDS section, but it doesn't work! I can attest to the fact that 138, 139, and 141 running on Windows XP Pro would not work. I tried everything and I couldn't get IDS to work, but SDD was fine! I just recently got 118 and it runs on the laptop. I will soon be trying it with the DA-VINA and the VCM.
I didn't know that 125 is the newest version of SDD that works with DA-VINA and Mongoose. I thought I had seen Mongoose shipping 143.
I didn't follow your comment regarding IDS in 125 versus in 118. Is the last version that IDS runs standalone 125 or 118?
You suggested to use a VCM with my X300. Shouldn't a DA-VINA also work? I know it was recommended by JLR back in the day.
And I agree with you that any of the OEMs couldn't care less about vehicles that are older than the warranty is long!
Thank you for your help!
The following users liked this post:
smgdata (03-16-2016)
#17
![Default](/forum/images/icons/icon1.gif)
Cambo is correct.
We used to keep one of our SDD units back to just before SDD2 came out, but in later versions the VCM would have to reload the code every time you switched.
We can use the latest SDD version with a 1995 XJS (just did it last week), but a VCM is needed. Mongoose is best used on vehicles with PanPAG and later ECUs.
If you have the software, just reload the whole thing. It's not that difficult. It will take you longer to figure out why it doesn't load, than just starting fresh.
IDS/SDD gets slogged down after a while, and can become unpredictable.
I reload all our SDDs completely once every few years; sometimes earlier if there's unpredictable behavior.
We used to keep one of our SDD units back to just before SDD2 came out, but in later versions the VCM would have to reload the code every time you switched.
We can use the latest SDD version with a 1995 XJS (just did it last week), but a VCM is needed. Mongoose is best used on vehicles with PanPAG and later ECUs.
If you have the software, just reload the whole thing. It's not that difficult. It will take you longer to figure out why it doesn't load, than just starting fresh.
IDS/SDD gets slogged down after a while, and can become unpredictable.
I reload all our SDDs completely once every few years; sometimes earlier if there's unpredictable behavior.
To make sure I understand, you are saying that you are running the latest version of SDD (143?) and it is able to launch IDS through a VCM? What version of Windows are you running?
I have reloaded 138, 139, and 141 multiple times, including reformatting the hard drive twice. No dice! I am wondering if the later versions of SDD require a later version of Windows.
Thank you for your help!
#18
![Default](/forum/images/icons/icon1.gif)
Genuine MongoosePro will "work" with an X300, but there are some limitations to what it can do. And this also depends if you are talking about a 6-cylinder X300, or a V12 X305. The engine management systems are different in those cars.
See the next answer:
VCM is fully functional with an X300 (as functional as is possible) but DA-VINA, MongoosePro, JLR VCI, Bosch iView, all have some limitations.
Of course i am referring to GENUINE devices, if you use clones then who knows what they can or can't do...
The following 3 users liked this post by Cambo:
#19
#20
![Default](/forum/images/icons/icon1.gif)
The latest version of SDD is 145. It works fine with VCM.
All factory SDDs are currently Win 7.
The older CF-18s were XP.
I have my own personal SDD with Win XP and the last version of SDD1 (131.03) loaded. I have loaded later versions on XP, and it works as well.
I would recommend at minimum Windows 7.
All factory SDDs are currently Win 7.
The older CF-18s were XP.
I have my own personal SDD with Win XP and the last version of SDD1 (131.03) loaded. I have loaded later versions on XP, and it works as well.
I would recommend at minimum Windows 7.
The following users liked this post:
Engineer1 (03-20-2016)