JLR SDD V160 and MongoosePro Issues
#22
![Default](/forum/images/icons/icon1.gif)
Sean, Yep will do!
My Plan:
1. I am thinking there could be a problem with the 64bit pass through device drivers I am using, I am going to see if I can roll these back to something more aligned to the heritage of the SDD SW. Researching whether installing them as though they thing they are running under Windows 7 or XP may be better if that is possible, also seeing whether I can install them as 32bit versions that came with the device itself - although I am not sure you can do this with a 64 bit operating system.
2. I have started to see if I can find a better pass through device and whether a VCI would work better - thought - DA dongle but seems to me most are based on earlier versions of Windows - although some are 64bit, but I am guessing everything would be a lot more stable in the drivers were made for the specific operating system rather than trying to run them via a Windows compatible emulation.
3. If this fails, I am going to dust down my old Sony Laptop with Windows 7 and check which version it has 32 or 64 bit and then install an earlier version of SDD, so help on finding a location for the right one would be nice; is this V131?
Love to have projects through our cold bleak English winter months and after all we are locked down at the moment so the wife can't complain when I spend all my time with the my favourite toy!
Thanks again for all you amazing help and support, I am always taken aback by the power of the internet to connect people across the world to share their experiences. Very Very much appreciated
My Plan:
1. I am thinking there could be a problem with the 64bit pass through device drivers I am using, I am going to see if I can roll these back to something more aligned to the heritage of the SDD SW. Researching whether installing them as though they thing they are running under Windows 7 or XP may be better if that is possible, also seeing whether I can install them as 32bit versions that came with the device itself - although I am not sure you can do this with a 64 bit operating system.
2. I have started to see if I can find a better pass through device and whether a VCI would work better - thought - DA dongle but seems to me most are based on earlier versions of Windows - although some are 64bit, but I am guessing everything would be a lot more stable in the drivers were made for the specific operating system rather than trying to run them via a Windows compatible emulation.
3. If this fails, I am going to dust down my old Sony Laptop with Windows 7 and check which version it has 32 or 64 bit and then install an earlier version of SDD, so help on finding a location for the right one would be nice; is this V131?
Love to have projects through our cold bleak English winter months and after all we are locked down at the moment so the wife can't complain when I spend all my time with the my favourite toy!
Thanks again for all you amazing help and support, I am always taken aback by the power of the internet to connect people across the world to share their experiences. Very Very much appreciated
Last edited by CozyDave; 11-13-2020 at 12:29 PM.
#24
![Default](/forum/images/icons/icon1.gif)
Hi guys, thought I would give you an up-date on progress. Thanks to V7 Sport for the link to the Jaguar Forum, I read through all the posts ref:108460 - very useful, lots of hidden gems. So a big thankyou for pointing me toward this one.
1. Took a close look at the MongoosePro probe, found that 2 pins were about 1.5mm longer than the rest, so took it apart and re-soldered them in the correct position. Also checked that there was no damage to the Jag connector - all seems fine here. Thought this was a eureka moment, but alas - no change when connected the laptop and car. Seriously thinking about ordering another one from a different supplier now!
2. Did a lot of reading about windows drivers, in the end I am pretty sure it goes, you either have the right ones for the OS or you don't - so cannot do anything if the drivers do match or haven't been written for the OS - however, it would appear that the MongoosePro 64 bit ones should work with Window 10 - others seem to have had some success. So it seems the best way forward is to host the correct version of windows on your host machine as a virtual machine operating system - see (3) below.
3. So I downloaded a retro version of SDD (V130) and loaded this onto an old laptop using the virtual machine method as defined in the post 108460. Got everything working including the SDD s/w and the MongoosePro device (FYI worked as per the V160 version I previously loaded on my Windows 10 Laptop) . Connected to the car, auto read the VIN and manually typed in the VIN, in both cases SDD interrogated the car and returned the exact same results of I got with the SDD V160 set up! i.e. CAN_HS read, CAN-MS and others present but showing a red 'X."
So have submitted a post to the 108460 thread to see if anyone can shed some more light on the issues I am having. I am now working on the assumption that the MongoosePro has some kind of problem, but not knowing how the comms work with it and the HS and MS CAN buses it is hard to trace. Questions in my mind are are the CANs read from the same pin or not so if you can read the HS should it also read the other? Could it be a latency problem i.e. bus is not responding fast enough through the Mongoose? More research over the next couple of days.
1. Took a close look at the MongoosePro probe, found that 2 pins were about 1.5mm longer than the rest, so took it apart and re-soldered them in the correct position. Also checked that there was no damage to the Jag connector - all seems fine here. Thought this was a eureka moment, but alas - no change when connected the laptop and car. Seriously thinking about ordering another one from a different supplier now!
2. Did a lot of reading about windows drivers, in the end I am pretty sure it goes, you either have the right ones for the OS or you don't - so cannot do anything if the drivers do match or haven't been written for the OS - however, it would appear that the MongoosePro 64 bit ones should work with Window 10 - others seem to have had some success. So it seems the best way forward is to host the correct version of windows on your host machine as a virtual machine operating system - see (3) below.
3. So I downloaded a retro version of SDD (V130) and loaded this onto an old laptop using the virtual machine method as defined in the post 108460. Got everything working including the SDD s/w and the MongoosePro device (FYI worked as per the V160 version I previously loaded on my Windows 10 Laptop) . Connected to the car, auto read the VIN and manually typed in the VIN, in both cases SDD interrogated the car and returned the exact same results of I got with the SDD V160 set up! i.e. CAN_HS read, CAN-MS and others present but showing a red 'X."
So have submitted a post to the 108460 thread to see if anyone can shed some more light on the issues I am having. I am now working on the assumption that the MongoosePro has some kind of problem, but not knowing how the comms work with it and the HS and MS CAN buses it is hard to trace. Questions in my mind are are the CANs read from the same pin or not so if you can read the HS should it also read the other? Could it be a latency problem i.e. bus is not responding fast enough through the Mongoose? More research over the next couple of days.
#25
![Default](/forum/images/icons/icon1.gif)
Dang, man, suck-o-rooney.
It's sort of retrospect now, but maybe try a DA Dongle next? Mongoose cables are twice the price of Dongle, which is the reason I went DA.
Anyway, maybe someone near you has access to either another Mongoose or possibly a DA Dongle that you could try?
Since the only consistent item with your specific problem is the interface, I also believe that item is the cause.
Good luck with it.
It's sort of retrospect now, but maybe try a DA Dongle next? Mongoose cables are twice the price of Dongle, which is the reason I went DA.
Anyway, maybe someone near you has access to either another Mongoose or possibly a DA Dongle that you could try?
Since the only consistent item with your specific problem is the interface, I also believe that item is the cause.
Good luck with it.
#26
#27
![Default](/forum/images/icons/icon1.gif)
@CozyDave were you able to fix this issue? I'm struggling with this for MONTHS now. I've got LR Freelander 2, not Jag, but symptoms are exactly the same - no matter what I do, SDD can connect to high speed can ONLY. Currently I've a car connected to external power supply with 13.8V and 60A of power, Windows 7 x86 with SDD v163 and Windows XP x86 with SDD v130 (tried multiple different Windows+SDD version combinations) and even tried other laptop and other passthough cables (Mongoose, Tactrix OpenPort2), checked ALL fuses in the car... Nothing. Just can't get this thing to work. I'm totally lost now, staring to pull my hair out
[img]data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7[/img] Although SDD can't connect to these modules, everything in car works 100% fine and there is no single DTC logged...
Anyone?
![Frown](https://www.jaguarforums.com/forum/images/smilies/frown.gif)
Anyone?
#28
![Default](/forum/images/icons/icon1.gif)
Hi, was asked if I managed to solve the Mongoose Probe issue not recognising the High Speed CAM BUS. Well yes I did, but not until I had learnt the lessons below:
1. Reverted back to an earlier version of the SDD S/w thinking this was the cause, thus needed an XP environment. Solved this by running an XP virtual machine on a Windows 7 OS - there is a thread on how to do this already in this forum which includes the virtual machine code to down load and instructions in how to configure it, I found it workes fine. But still not with the Mongoose Probe I had same problem.
2. I also found that I had inadvertantly tried to up-date the Mongoose probe believibg it was not a Chinese copy, turns out it was and when connected to the Mongoose Web site to up-date it, I eventually discovered that the Probe had in deed been updated with a new name, thus stopping it from being recognised by the SDD S/W. Luckily this can be fixed by down loading an EPROM programming app, one that reads the high level characteristics of the Probe. You can then reset them to the original names that the SDD S/W is looking for. This can be done with the USB cable that connects to your computer. However, whilst this made the Probe work again it still did not read the HS CAM BUS. I did read in some of the threads that the Chinese copy had some issues in providing data for all modules and this seems to be the case certain with the one I bought.
3. I then managed to find a Divna probe which I ordered and bought as some others had suggested, this was the break through, once this was connected to the XP virtual.machine running the early SDD S/W it did a full analysis of the car and just like magic, recognised all the modules on the bus. I was then able to recalibrate the seat after what must have been 70 days of research.
So the bottom.line, if.your Mongoose.probe is a Chinise copy, then it is probably the problem. I don't actually know whether the DIVA probe I bought is also a copy, but if it is, it seems to be a lot more stable and more importantly works. However, it was hard to find one on the net from a trusted site. My first order for one turned out to be a pair of Sun Glasses ~ so check the seller very carefully if you go this way.
Trust this helps
1. Reverted back to an earlier version of the SDD S/w thinking this was the cause, thus needed an XP environment. Solved this by running an XP virtual machine on a Windows 7 OS - there is a thread on how to do this already in this forum which includes the virtual machine code to down load and instructions in how to configure it, I found it workes fine. But still not with the Mongoose Probe I had same problem.
2. I also found that I had inadvertantly tried to up-date the Mongoose probe believibg it was not a Chinese copy, turns out it was and when connected to the Mongoose Web site to up-date it, I eventually discovered that the Probe had in deed been updated with a new name, thus stopping it from being recognised by the SDD S/W. Luckily this can be fixed by down loading an EPROM programming app, one that reads the high level characteristics of the Probe. You can then reset them to the original names that the SDD S/W is looking for. This can be done with the USB cable that connects to your computer. However, whilst this made the Probe work again it still did not read the HS CAM BUS. I did read in some of the threads that the Chinese copy had some issues in providing data for all modules and this seems to be the case certain with the one I bought.
3. I then managed to find a Divna probe which I ordered and bought as some others had suggested, this was the break through, once this was connected to the XP virtual.machine running the early SDD S/W it did a full analysis of the car and just like magic, recognised all the modules on the bus. I was then able to recalibrate the seat after what must have been 70 days of research.
So the bottom.line, if.your Mongoose.probe is a Chinise copy, then it is probably the problem. I don't actually know whether the DIVA probe I bought is also a copy, but if it is, it seems to be a lot more stable and more importantly works. However, it was hard to find one on the net from a trusted site. My first order for one turned out to be a pair of Sun Glasses ~ so check the seller very carefully if you go this way.
Trust this helps
The following users liked this post:
Burag (09-30-2022)
#29
![Default](/forum/images/icons/icon1.gif)
@CozyDave Thanks for the reply!
This is indeed my case... Both my J2534 cables are Chinese knock-offs from Aliexpress :/
This DA-dongle interface is this one? https://www.diagnostic-associates.co...thru-interface
So the bottom.line, if.your Mongoose.probe is a Chinise copy, then it is probably the problem. I don't actually know whether the DIVA probe I bought is also a copy, but if it is, it seems to be a lot more stable and more importantly works. However, it was hard to find one on the net from a trusted site. My first order for one turned out to be a pair of Sun Glasses ~ so check the seller very carefully if you go this way.
This DA-dongle interface is this one? https://www.diagnostic-associates.co...thru-interface
#30
![Default](/forum/images/icons/icon1.gif)
@CozyDave Thanks for the reply!
This is indeed my case... Both my J2534 cables are Chinese knock-offs from Aliexpress :/
This DA-dongle interface is this one? https://www.diagnostic-associates.co...thru-interface
This is indeed my case... Both my J2534 cables are Chinese knock-offs from Aliexpress :/
This DA-dongle interface is this one? https://www.diagnostic-associates.co...thru-interface
#31
![Default](/forum/images/icons/icon1.gif)
Hi, I am not sure if the one you highlight will work to be honest, I guess you will need to check its full functionality and compatibility with the SDD S/W version you are planning to use coupled with the Computing / Windows version to be sure. The one I used is the DA-VINA 2534 - which is more like this one: http://j2534.co.uk/downloads/DA-VINA...34%20Sales.pdf. - but I cannot find one like this anymore. Having said that the data sheet appears to be very similar to the probe you highlight - but be careful as may Chinse sites simply copy the data from the original site and are not always fully accurate.
I am guessing the main issue with the newer replacement probe you reference has drivers that are compatible with your computing environment, the Windows version e.g. 32 / 64 bit drivers etc.... you plan to use and the SDD S/W version - For example I know in my case the SDD S/W and probe drivers are for XP 64bit. So I cannot recognise the probe with Window 7 or later. But having said that, I did manage to get a later version of the SDD S/W working on a 128 bit machine so if there are newer drivers for a newer probe then maybe you could get it to work with a later version of SDD.
A generic note, it is good practice to keep the computer and operating system at the same standard - NO UP-DATES - hence I have a dedicated old laptop for this purpose. Why? Well, OS up-dates could make SDD unstable - so best to lock this down so once it works - you are sure nothing will change.
I would try messaging the seller and try asking which OS and SDD versions it is compatible with and what the Computer needs to be. If this is not possible it may be a case of try it out and see - or keep a look out for a second hand genuine DA-VINA probe. Also, sometimes the seller has the S/W for the probe on a generic website so you download it rather than getting a disk with the device. So you could try to find the link and then inspect which drivers are available - their filenames and / description (right click file properties) usually gives this info.
Good Luck!
I am guessing the main issue with the newer replacement probe you reference has drivers that are compatible with your computing environment, the Windows version e.g. 32 / 64 bit drivers etc.... you plan to use and the SDD S/W version - For example I know in my case the SDD S/W and probe drivers are for XP 64bit. So I cannot recognise the probe with Window 7 or later. But having said that, I did manage to get a later version of the SDD S/W working on a 128 bit machine so if there are newer drivers for a newer probe then maybe you could get it to work with a later version of SDD.
A generic note, it is good practice to keep the computer and operating system at the same standard - NO UP-DATES - hence I have a dedicated old laptop for this purpose. Why? Well, OS up-dates could make SDD unstable - so best to lock this down so once it works - you are sure nothing will change.
I would try messaging the seller and try asking which OS and SDD versions it is compatible with and what the Computer needs to be. If this is not possible it may be a case of try it out and see - or keep a look out for a second hand genuine DA-VINA probe. Also, sometimes the seller has the S/W for the probe on a generic website so you download it rather than getting a disk with the device. So you could try to find the link and then inspect which drivers are available - their filenames and / description (right click file properties) usually gives this info.
Good Luck!
#32
![Default](/forum/images/icons/icon1.gif)
I'm also considering getting the VXDIAG as it's half the price of DA-Dongle: https://www.aliexpress.com/item/33020957937.html
The offer is direct from HW vendor, which BTW is a confirmed and trustworthy company - I've used their products previously with other cars.
On the computer note: I've got a dedicated laptop (Thinkpad X230) for car diagnostics and dedicated Windows 7 x86 (32 bit) install just for SDD. I'm aware of these things being really fragile...
The offer is direct from HW vendor, which BTW is a confirmed and trustworthy company - I've used their products previously with other cars.
On the computer note: I've got a dedicated laptop (Thinkpad X230) for car diagnostics and dedicated Windows 7 x86 (32 bit) install just for SDD. I'm aware of these things being really fragile...
#33
![Default](/forum/images/icons/icon1.gif)
just buy the legit jbox this thing is dirt cheap. it literally has a picture of a jumping cat on it.
https://www.diagnostic-associates.co...thru-interface
https://www.diagnostic-associates.co...thru-interface
Last edited by xalty; 09-30-2022 at 01:11 PM.
Thread
Thread Starter
Forum
Replies
Last Post
Aarcuda
S-Type / S type R Supercharged V8 ( X200 )
6
04-03-2020 02:59 PM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)