Graculus said:
Well it's there in V163 - albeit for a different model...
View attachment 313859
Click to expand...
I'm going to try a different version. I presume the engine needs to be running when the air path calibration is done?

Just for absolute clarification can I confirm the ignition positions:

0 = key out of the slot
1 = key in the slot
2 = key in the slot, Start button pressed to illuminate dash lights etc
3 = engine running
 
Those key positions are correct from memory, the routine will instruct you when to start the engine.
I had various problems with V164 (which I used as a 'quick' way of getting rid of the restricted functionality warning) so I've gone back to V163, which is fine for my needs.
 
Graculus said:
Those key positions are correct from memory, the routine will instruct you when to start the engine.
I had various problems with V164 (which I used as a 'quick' way of getting rid of the restricted functionality warning) so I've gone back to V163, which is fine for my needs.
Click to expand...
I'm working my way through the thread looking for a link to v163 though in the early posts @Nodge68 said that v130 had more functionality that later versions I believe.
 
OK, I finally found air path calibration. I tried using v163 but it didn't show up in the recommendations and I think I know why. Because the car is in Reduced Engine Performance (limp mode) it won't allow air path calibration to be run because it needs the engine to rev through the range etc. I cleared the codes and limp mode went away but as soon as I fired up the engine again and gave it a bit of boot, limp mode was back again.

For reference, if anyone doesn't get air path calibration in Service Functions > Recommendations it can be found in the Diagnosis session. Go to Powertrain > Engine and click on something like "reduced engine power" symptom. Go through to the DTC screen and select a relevant DTC. When you move on to the next screen you should see it listed as a recommendation.

APC.jpg
 
Hello Guys 👋

Does anyone have an updated link for the tools @PRO mentioned. I have a VM of sdd already but cannot get it read data from the car although it says Mongoose is connected ok.

I was going to give the other VM a go to see if I got any better luck, but the link says it's no longer available.

Many thanks
 

Attachments

  • 20240401_145706.jpg
    20240401_145706.jpg
    251.6 KB · Views: 96
Post the log file, it'll be more helpful than a photo - although it does show the VCI is at least recognised, is there a reason you have the date set to 2012? Also, what vehicle are you trying to connect to ?
 
Ok will do, will get log file and post here. Just wondered if the VM i have is misconfigured somehow. I tried with the date set to 2012 because I remembered reading somewhere you needed to do this to make it work, but it made no difference. With both current date or 2012. The vehicle I'm trying to connect to is a 2014 L405 TDV8
 
Then it should connect fine, have you looked at the port settings in the VM? It could be the data rate is doing something. The text of the error message suggests a connection to the vehicle is being made. Can you connect to the vehicle with a standalone generic reader?

I wonder if the date being changed has activated the update timeout - on the 'system' tab, how many days is it showing since the last update?
 
Hello, Sorry about the delay in reply, been hectic with work.

So if the date is current then it displays a warning in the diag screen about functionality being disabled due to missing updates,

But if the date is set back to 2012 then DIAG screen appears to work but it still wont connect to the car.

I also have an Autel scanner that connects to the car fine and can read all modules without issue, so it definitely seems to be SDD related issue.

Interestingly this VM seems to have been stopped from connecting to the internet, it was one that I got with the cable, a year or so back when I had an XKR with the intention of using it for that, but I have never needed to use it until now, so I am wondering if the VM never worked in the first place.

Which is why my train of thought led to getting a known working VM as a good starting point

Many Thanks
 

Attachments

  • SDD.png
    SDD.png
    63.6 KB · Views: 91
delboy1234 said:
Have you double checked in Device Manager to make sure the mongoose cable is recognised? And does it say the cable is connected in SSD?
Click to expand...
Hi, thanks for the reply. SDD says the mongoose is connected and device manager has the Mongoosepro on the list. Any other pointers to get it working?
 

Attachments

  • manager.jpg
    manager.jpg
    151.3 KB · Views: 95
  • SDD.jpg
    SDD.jpg
    131.3 KB · Views: 79
Hibbo15 said:
Hi, thanks for the reply. SDD says the mongoose is connected and device manager has the Mongoosepro on the list. Any other pointers to get it working?
Click to expand...

There is a question mark next to the Mongoose Pro in Device Manager. Check in properties to see what it says.
Also have you fully removed pin 13? That's what caused me all sorts of issues when I first connected my RRS.
 
delboy1234 said:
There is a question mark next to the Mongoose Pro in Device Manager. Check in properties to see what it says.
Also have you fully removed pin 13? That's what caused me all sorts of issues when I first connected my RRS.
Click to expand...
Did open up the properties last night and it says the device is working properly. I used some long nose pliers to snap the pin off, I think it snapped off at the base, I'll double check when I get home.

The pin is snapped off flush with the plastic.
 
Last edited:
Hi,
I did a Powertrain update on a Freelander 2 (not being logged with a key, by mistake) and I get:

P02E0-13, Diesel intake air flow control- open circuit.

The car is in Restricted performance now, having no error prior. I tried rerun it with a key, it finds the right patch, it finds the serial for the hardware but doesn't let me run it for I have to contact the hot line support.

Hoe can I revert on get a suitable update for the module to work?

Thanks!
 

Attachments

  • WhatsApp Image 2024-04-08 at 21.14.47_f7fa6c24.jpg
    WhatsApp Image 2024-04-08 at 21.14.47_f7fa6c24.jpg
    294.1 KB · Views: 66
  • WhatsApp Image 2024-04-08 at 21.15.09_5d5cf247.jpg
    WhatsApp Image 2024-04-08 at 21.15.09_5d5cf247.jpg
    223.6 KB · Views: 69
What do you mean by 'not being logged with a key'? you shouldn't need Engineering mode access to update existing software, only change it from the intended software.
Try creating a new shortcut on your SDD desktop with this as the target C:\Program Files\JLR\IDS\Runtime\SoftwareDownload.htm then open the shortcut, click on the Land Rover badge, enter the required information and try to force the correct software - make sure you have some sort of battery support unit connected to keep the system voltage above 12.5VDC
 
Graculus said:
What do you mean by 'not being logged with a key'? you shouldn't need Engineering mode access to update existing software, only change it from the intended software.
Try creating a new shortcut on your SDD desktop with this as the target C:\Program Files\JLR\IDS\Runtime\SoftwareDownload.htm then open the shortcut, click on the Land Rover badge, enter the required information and try to force the correct software - make sure you have some sort of battery support unit connected to keep the system voltage above 12.5VDC
Click to expand...
Thanks for your reply, I thought that for every existing software update you need to be logged with an engineering access code.
I tried to do that by settings and ask for patch, I get the same error.
Will try your way and let you know.

Thanks
 
Graculus said:
What do you mean by 'not being logged with a key'? you shouldn't need Engineering mode access to update existing software, only change it from the intended software.
Try creating a new shortcut on your SDD desktop with this as the target C:\Program Files\JLR\IDS\Runtime\SoftwareDownload.htm then open the shortcut, click on the Land Rover badge, enter the required information and try to force the correct software - make sure you have some sort of battery support unit connected to keep the system voltage above 12.5VDC
Click to expand...

Managed to try your way but I get this:

🥺
 

Attachments

  • IMG_4055.jpeg
    IMG_4055.jpeg
    300.2 KB · Views: 91
  • IMG_4054.jpeg
    IMG_4054.jpeg
    539.8 KB · Views: 92
What were you trying to do? - as in, why did you want / need to update, have there been any hardware changes, what faults were present before... I've a feeling you might need to either drive (slowly) to a dealer or find an independent with Autologic or similar that can re-load your software.
Edit: Did you initially try to configure existing module or configure new module? and did you have a BSU connected? it could be the module is stuck in bootloader mode, try a battery disconnect for a few minutes then use the method above to try again. I assume you have all the files already downloaded for your model series?
 
Last edited:
Graculus said:
What were you trying to do? - as in, why did you want / need to update, have there been any hardware changes, what faults were present before... I've a feeling you might need to either drive (slowly) to a dealer or find an independent with Autologic or similar that can re-load your software.
Edit: Did you initially try to configure existing module or configure new module? and did you have a BSU connected? it could be the module is stuck in bootloader mode, try a battery disconnect for a few minutes then use the method above to try again. I assume you have all the files already downloaded for your model series?
Click to expand...

I modified some confort settings, like headlights and one step locking etc and I got recommended to Configure existing module (Powertrain module). I did it.
 
You don't have to go through all the 'recommended' actions, SDD just brings them into focus in case they're required.
Have you tried a battery disconnect/reconnect? Given the error message, I'd also consider reloading the original CCF to 'as built', another battery disconnect/reconnect then trying again with the Powertrain module.
 
Graculus said:
You don't have to go through all the 'recommended' actions, SDD just brings them into focus in case they're required.
Have you tried a battery disconnect/reconnect? Given the error message, I'd also consider reloading the original CCF to 'as built', another battery disconnect/reconnect then trying again with the Powertrain module.
Click to expand...
Learnt it the hard way 🤦🏻‍♂️
I tried battery disconnect/reconnect to no avail. I did a reset (I’m not sure it’s the same thing as reloading original as built ccf).
I have as built files downloaded on to PC.
 
Last edited:
You must log in or register to reply here.

Similar threads

M
the JLR DoiP VCI SDD Pathfinder Interface
Replies
1
Views
339
Anaconda
A
E
SDD V150 PATCH
Replies
2
Views
929
Ejaikbros
E
E
New Member
Replies
2
Views
714
brianp38dse
brianp38dse
aleksey-ms
Jaguar Land Rover JLR SDD (new version) + Calibration files
Replies
1
Views
3K
Marksman702
M
S
L322 SC Electrical Issues. Terrain control, Handbrake
Replies
0
Views
354
spitfire
S