Hello to all,

2 years ago I had a LPG conversion done on my 2005 s type.
This came with a lot of fault codes and restrict performance.
So I bought a ELM327 cable to read and erase OBD2 codes.Luckily the LPG is working fine now.

Wanting to program a second key to my car I bought a Mongoose JLR clone.
After some trial and error I managed to install the SDD V130 and login successfully.

After reading the VIN and data collection I selected PROGRAM NEW TRANSPONDERS
Following the steps I erased the existing transponders.
After this I got an error connecting to the DRIVER DOOR MODULE and got stuck resulting in not being able to start the car.
Some screen shots :

Flickr: Mark Mongoose's Photostream

and a short clip capturing the problem :


Specifications :

Jaguar S type 2005 2.5i V6
Windows XP SP2 on a Oracle virtual machine
Java 6 up26
mongoose driver V1.02.12
firewall and antivirus turned off
no updates performed
followed the steps to install SDD as described here on the forum :

cheap mongoose

I guess the problems is that I can't get access to the DDM module cause I get the error just after SDD wants to communicate with DDM module.
After the data was collected in the beginning this module had a red X marked.
Tried a hard reset of the car without result.

Can somebody pinpoint why I have the red marker at the DDM module or what steps to take?
Can it be a problem with the mongoose and is there a way to check if the cable is working fine or to diagnose if the pins on the cable are fitted well in the OBD connector on the car?

Thanks for any advise.

 

Welcome to the forum Mark, quite an introduction!

Seems to be that for whatever reason, there is no communication with several modules in your car, it's not just the DDM that's "out of the loop" you can see the others with the red cross as well.

This could be a wiring problem, or could be that those modules need reflashing to re-establish communication.

Frankly i don't recall ever seeing that particular error message, usually it's a larger box with a statement like "Communications Failure, do you want to re-establish communications", with two buttons to retry or abort.

So this Testman error might be an indication of a completely dead module, or a wiring problem. It's as if the module isn't even there, which kind of makes sense given it's crossed out in the Network Overview screen.

If we specifically look at the key situation, there are 4 modules where the new information for the key transponders must be written:

Drivers Door Module (DDM)
Instrument Cluster (IC)
Engine Control Module (ECM)
General Electric Module (GEM)

If for whatever reason there is no communication with one or more of those modules, the programming of the keys will fail. Which appears to be the problem here.

So what to do? Firstly you can try to reprogram the DDM.

Go into a Diagnostic Session, and select symptoms that relate to this issue, it might take a little trial & error to find them, but in the end the Recommendations need to be "Program Existing Drivers Door Module" and "Program New Drivers Door Module", it might not be that exact wording, but something along those lines.

You won't find the option to reprogram the specific modules in a Service Session, you have to make a Diagnostic Session & select the symptoms.

When reprogramming the DDM, other modules in that list of 4 also need to be updated, if there are communication problems with any other modules that will also come up. And you will likely have to go after each module that comes up with "Commincations Failure"

I had to do something similar on an X350 once, from memory by reprogramming the GEM, the other 3 modules were reprogrammed at the same time, including the key transponders and the remotes.

But in your case, if the DDM is completely dead or disconnected by bad wiring, this could make the situation even worse.

Try to reprogram the DDM like I mentioned above. If that doesn't work then there are deeper issues to look at, maybe a replacment module & check the wiring.

If you attempt to repogram the GEM and for whatever reason it fails, then the car will be even more immobilised than it is now (yes it could get worse)

A couple of last points.

In my experience clone Mongoose cables either work, or they don't. If the lights are flashing & you can read the VIN when you connect, then I wouldn't be concerned about that.

More often than not the problems come from the SDD software itself, not installed properly, corrupted, or just being buggy/unstable. i.e. a software issue, not a hardware issue.

Good luck with it, let us know how you get on with reprogramming the DDM.

Take small steps!

 

Hello Cambo351,

Thanks for your reply.

I am doing a fresh install of SDD v130 to see if there is any difference in test results.
Next step will be reprogramming the modules.

SDD v130.03 will do for this job?

I thought I have :

If the DDM module or wiring is damaged/corrupted can it still function normally ?
The remote fob and windows are still working.

 

That's something I forgot to ask. Short answer is, maybe.

The funny thing is, sometimes you can't talk to a module via SDD, but it seems to be functioning correctly. For example with my XJR it's not possible to reflash the ecu with SDD, it brings up the "Communications Failure, do you want to re-establish communications" but the car runs fine.

The only direct experience I have with the DDM was with a mates X350 as mentioned above, in his case the original DDM had either died or lost it's programming, so the remote locking had stopped working. You pressed the button on the remote & the locks would cycle, but not lock. He put in a new module without reprogramming it & it was the same.

How this relates to your car is a little unclear. Could be that the module has corrupted "a little" and that prevents communication with SDD. Could be a wiring problem that prevents communication to the SDD, but doesn't affect the operation of the module.

It's hard to say for sure.

Looking at the wiring of the DDM, the other modules crossed out on your list are all connected via the SCP (CANbus) so maybe there is a wiring issue with the Bus.

Did you read the DTC's (related and unrelated events) and can you share the screenshots of what the DTC's were listed? I'm thinking now there might be a wiring problem on the Bus....

 

Er, a bit puzzled by "SCP (CANbus)". SCP is a network (running at 41.6k) and CAN is another thing (and here runs at 500k). Are they both suffering or just one?

On my car, but perhaps not in a 2005 car as modules started to migrate to CAN, DDM is on SCP. (ECM aka PCM is not on SCP even in my car so won't be in a 2005.)

If there might be a wiring problem, check some volts etc at the DLC (OBD socket).

 

Hi JagV8, I'll try that tomorrow. Thanks

Today I started with a fresh installed SDD v130 and connected to the car.
I have read all the DTC codes and posted them here :

Flickr: Mark Mongoose's Photostream

After this I started to reprogram/configure the DDM module in the EXTRAS menu.
At one point I was asked to select "automatic" or " manual" method.
see picture Programming SDD progress1
At this point I couldn't select one of these options, there was no link or button available.
I saw activity on both the mongoose device and virtual disk ( was indicated right lower corner of Oracle VM ) and left it as it was cause I had visitors.
After a couple hours there was no change and I decided to go one step back.
At this point it seems to have selected automatic and a progress bar was active.
So I let it run for about 50 min but suspected that again nothing was written.
Decided to start again tomorrow in daylight.

I didn't got a error that a connection to the DDM wasn't possible.
Maybe I didn't got that far?

How long does it take to successfully program a DDM module ?

Something else I tought about :

When I bought the car 2years ago there were 2 keys and fobs.
One was working correct, key, transmitter, transponder OK.
On the other one the transmitter and transponder didn't worked.
At that point I thought the battery on the fob was flat and replaced it.
Still didn't worked and somewhere on the web I read that this could be because the battery on the fob was flat for a long time and erased the code?

Now I think about this, the transponder has a fixed code no?
As the battery of the car was good how can the code be gone in the car?
Maybe the second key never worked in the first place and somebody else tried to add this key before unsuccessfully.
Maybe during this process corrupting the DDM?

Just guessing here and hope to connect/program the DDM tomorrow.

How long will it take to successfully program the DDM ?

 

I don't go for the already-corrupted DDM.

If other key had ever been programmed it would start the car. Fob might or might not have been programmed and anyway can lose it separately. Key would still work.

Can't read the DTCs, too small and the GUI is the worst I've ever met.

 

Can't post the shots from your Flickr here which makes it a little awkward, but the screenshot of the Related Events is very interesting:



Points to a break in the Bus wiring somewhere. Which would explain why so many modules are not able to be read.

 

Today I erased all the DTC codes successfully and performed a new Diagnose to see if the errors came back.
There were only 2-3 codes because of the incorrect key, the rest was empty.

Next step was to reprogram the DDM module since this is still marked with a red cross.
At the point where I have to select automatic or manual the SDD is stuck.
There are 2 arrows but no link or button to select.

Decided to install SDD v135 to see if this works.

Something that I didn't mentioned was that when I bought the car 2 years ago the seller insured that the car was never involved in an accident.
I asked because the car was off road for 2.5 years.
Now I have reason to believe it was involved in an accident because there are signs of a respray on the passenger side front and rear door.
( rear door the paint starts to show little cracks as result of bad? respray quality )
Maybe during the accident or during the repair something caused these DTC errors ?

So hopefully the DTC codes shown above will stay away.

 

Check the elec diagram to be certain which network your DDM is on, as diagnosing the fault is going to involve knowing that, especially if you'll be using a meter.

I can't see any reason to try v135 but it'll want to go online unless you use a cracked version which is itself a cause for worry.

 

1) having the system in a VM might be the problem

2) powersaving in XP and the usb port would be a problem

3) are you sure it is not the arrows that you are supposed to click?

4) IE settings might be a problem

5) programming mode should be used only when both vehicle and laptop are on external power

6) never leave the system unattendied in programming mode for hours on end, see #5

 

Hi plums,

I did all this even have battery charger on and laptopcharger on.

Today I installed SDD v135 and here it showed a blue bar ( only visible is you clicked beside manual or automatic ).
After selecting automatic it started to upload but coudn't connect to DDM

DDM failure | Flickr - Photo Sharing!

Nearly all of the previous DTC codes are still erased except these :

DTC after clearing | Flickr - Photo Sharing!

Is there a way to test the DDM module with a tester ?

Am asking this because everything seems to be working normal ( windows, door locks,interior light...)

 

After installing a replacement DDM module I still couldn't connect to the module.
Although the cables and connectors look fine I noticed 2 cables who were bent.
I straightened them and reconnected the original DDM module.
Finally this came back on line together with several other modules who had a red marker in SDD before.
I managed to add a second remote control, adding a second transponder failed.


Suspect that this transponder died before I bought the car since I never was able to start the car with this one.

Can you replace the transponder from the key or do I have to buy an uncut key with transponder?

 

Well this is a result. So you are back to having one working key and the car is driveable?

You will have to repair those wires, they will be broken inside the insulation, straightening them back out has re-made the connection, but it's not a good one.

As far as I know the transponder is just an RFID chip, which draws power via Electro-motive Force (i.e. through the air) when it's in close proximity to the transceiver have a look at this article here https://www.jaguarforums.com/forum/x...49/#post651375

It may be an old wives tale, but the bloke who sold me my old X-Type (a little independant garage) seemed to think that if one of these key's had not been used for a while, you needed to leave it in the ignition to "charge up" might be total BS, but given that the chip is basically RFID, I can imagine that there might be a tiny capacitor in there that needs recharging...

Failing that, you could just pull the chip out of another key & reprogram it...

 

Everything solved !

Couldn't start the car cause I only had 1 working key.
The SDD required 2 working keys to complete the programming successfully.
No idea why?
So I borrowed somebody else his key and held it against the ignition switch during programming so this code is installed.

Have my car back running with 2 remotes.
Ordered a transponder chip, so when this arrives I can program the second key.

Big thanks to Cambo351 and everybody else for their input.

 

Thanks for the update, did you have to programme this second key?

 

Yes, first I used my working key and then I used the borrowed working key.
So I can use my car again,once I have another transponder for my spare key I have to program this as well.

 

So, you will keep the key until you get the new transponder then pair it back to your friends car?

"Working" just means functioning, there is no need for the key to work with the car?

I assume you still need to fix the wiring fault?

Sorry if I'm a bit slow!

 

You need 2 keys which you can turn to position II in the ignition.
Also 2 functioning transponders which code gets stored in the car.

I had to use a 3th key, which I borrowed, since my spare key ( key No2 ) had a faulty/dead transponder.

Step 1 : Put in 1st key with functioning transponder ( key needs to be possible to turn to position II in ignition )

Step 2 : Put in 2nd key, my spare one ( 2nd key needs to be possible to turn to position II in ignition )

Step 3 : Since the 2nd had a dead transponder I held the borrowed key ( 3th key that you can't turn in the ignition but no need for anyway ) during the process against the ignition ring while key 2 was in the ignition therefore tricking the car that there is functioning key available.
The code of key 3 gets read.

So for key 2 I used the code of key 3.

At the moment I have 2 valid codes programmed ( key 1 and 3 ) and can start the car only with key 1.
Can't use key 3 but no need for that, as soon as I have a new transponder I reprogram the keys 1 and 2.

No need to pair it with my friends car cause this car is not involved, just borrowed the key for the code of the transponder.

( "working key" was a bad translation from Dutch to English, should be valid, functioning )

 

not sure if your still active on this but I wanted to say thank you for this post it's quite detailed and very informative and is right inline with my current situation although I fear mine might be alot worse but I won't know until I can at least cycle the start/stop button from pos 1 and pos 2