I'm trying to program additional keys with SDD using a mongoose clone. In SDD - Service Functions I see the programming options and have tried "Security - Program new transponders" When I run this option it goes through the prompts until it asks to connect the diagnostic tester.



I'm sure other members have been successful using a mongoose cable to program keys but I've been unable to find away around or ignore the "connect the diagnostic tester" Can anyone help?

 

One of my fobs lost its programming, so I re-programmed it along with the one that was working (must do both of them). I didn't run into any problems following the prompts and didn't get a message to connect the diagnostic tester. I don't know what that's about.

 

Yeah you're doing something wrong...maybe because you're in a Diagnostic session...

Try going into a Service session.

 

Well this is frustrating. I thought cambo was onto something as I couldn't be sure I had selected a service session. But still no joy after selecting either a service function or a diagnostic function. I am using SD 138 so I thought lets get back to basics and loaded SDD 130 but again the same issue asking to connect the diagnostic tester in either type of session, service or diagnostic.

I'm not an SDD expert but cant think Ive got a setting wrong that rejects the mongoose cable already connected and prompts to use a diagnostic testing cable. Now I am suspecting something is wrong in the car but not sure where to look. I scanned DTC but nothing jumps out to me. I think the mongoose cable is good as it reads Vin, loads sessions works in SDD 138 and 130 etc

Any thoughts out there from SDD users or prior key programmers

 

Have you tried disconnecting and then reconnecting the 'mangoose' cable when it tells you to connect it ?

Edit:

Sudden thought; (X350 mantra [all together now] - "battery, battery, battery") What's the battery voltage while you are doing this ? If the battery voltage gets too low that may be upsetting the system.

I'm sure I've read somewhere that when using an SDD/Mongoose cable you ought to have a voltage maintainer connected to the battery.

 

Yes, you're supposed to connect such a thing (a decent charger will do) to keep the volts high.

 

Hope the vehicle's key programming issue is sorted out. If not, from the picture attached, i can see a drop in voltage retention(red battery indicator) when the issue crops up. Try to connect a running vehicle with a cables (parallel) for voltage retention or have a way to independently support the ignition system with seperate battery power while procedure is carried out again. Its an issue with the car's power retention system.

 

Avoid another car if it's running as you're asking for grief with alternators etc. Just use a charger or the like.

 

+1 for JagV8's comment.

I think we are specifically warned, somewhere (sorry, can't be *bothered to look for it at the mo'), against connecting jump leads to a running system.

* I was going to say 'can't be fagged to' (a good standard UK slang expression), but then I remembered that this is a US forum !

 

Thanks for support & ideas. FYI - I've been running SDD v138 with a voltage maintainer delivering 13.7V but get still get the red battery symbol. Dont know why. SDD reads the vin automatically & I can get the service fuction menu and get DTC's. So i'm thinking SDD and monoose are communicating correctly. As a check I reinstalled v138 in a new VM and I'm still having "connect the
diagnostic tester" This prompt is for several of the service functions e.g. transponder programming, seat calibration, configure restraints module etc. Is anyone else getting this prompt?

For my last trial I swaped the battery maintainer for a battery charger and at the end of the session battery was at 12.86V. Still getting "connect the diagnostic tester" prompt. I tried disconnecting and reconnecting the mongoose but this didn't allow me to advance in transponder programming and it ultimately crashed SDD

So I'm guessing I have one of three problems
1. not enough voltage to the car during the programming
2. Sdd installation or mongoose cable communication problem or
3. some vehicle/module problem interfering with SDD operation

Does anybody know what voltage values change the battery symbol color in SDD - what's red, yellow or green? I'm connecting my voltage maintainer directly across the battery. Anyone see any issues with that? SDD reads VIN, loads vehicle spec page, service function & recommendatons. So could SDD or the monmgoose cable be the problem?

The SDD vehicle spec page shows the various module status. I have a couple of modules not responding, red X, could anything on the diagnostics be preventing me from accessing the transponder programming?

 

Voltage maintainer is not enough. Connect a good charger, able to output at least 20-30Amps of current.
Since you are running SDD in a VM, this way no security functions will work and every bit of programming is a risk. Install it on a physical machines to avoid problems.

 

Just wanted to close this thead out and I have now got 3 programmed keys; so happy at last

Problem resolution explained in this thread https://www.jaguarforums.com/forum/x...iences-148784/

I could'nt get my standalone laptop (SDD v138) to list the program key options so went back to my modern laptop with vmware xp and SDD v138. Tried programming/calibration on a less critical feature (calibrated headlights) and it worked with no problem. So I jumped into programming keys which also worked without problems. So 1 month later I have peace of mind should a key get lost.

Thanks to all the forum members that helped me through all this. It's a great community