[Walbor]

I’ve got a couple of keys on order so may still give it a try, also just found my old elm327 cable so should hopefully be ok.

 

[orsom weels]

I can't speak for IDS/SDD. I use Forscan.

I use a X202/4's with the 4 button flip key for my X200 system without any problem. All S types use a Texas Crypto 4D / 4D60 / JMA: TPX2, TP06 / SILCA: GTI transponder chip and this chip is also used in other Honda's, Ford's and jaguars till 2008.

Maybe it works for you because you have a Ford/Jaguar hybrid?

I actually have a third key cut and ready to program to my 2004 X202 3.0l, so thought if I can just add it with ForScan, great, I'll give it a go. ForScan won't even connect to the Jag? I just get an 'Unable to connect to vehicle' message. Have tried with the HS/MS CAN switch both ways (it asked for it to be set to MS, but tried the other way as well just in case), but this is all I get,

I also watched the You Tube clip you linked earlier in the thread, and as his new key didn't work, he ended up having to call a lock smith, as it deleted his original key and he couldn't start his car, which kinda reinforces the theory that you can't add a key without deleting keys already coded?

 

[46421]

I also watched the You Tube clip you linked earlier in the thread, and as his new key didn't work, he ended up having to call a lock smith, as it deleted his original key and he couldn't start his car, which kinda reinforces the theory that you can't add a key without deleting keys already coded?

As from 3.00 into the vid you could hear him tell he had a wrong or faulty key and because of that Forscan keept stuck in the programming mode. If you look closely you can see he can not turn the new key in the II position. The lock smit cut a second key and then he could program it.

I'll give it a go. ForScan won't even connect to the Jag? I just get an 'Unable to connect to vehicle' message. Have tried with the HS/MS CAN switch both ways (it asked for it to be set to MS, but tried the other way as well just in case), but this is all I get,

You get the message:
Make sure the ignition key is on and try again.

By the looks of it Forscan is connected to the adaptor. I hope this will help you.

Support Request

Error "Unable to connect to vehicle. Please make sure the ignition key is ON and try again"

The error means that FORScan has successfully connected to the adapter, but for some reason hasn't received any response from the vehicle PCM. This is normal situation if the ignition is OFF or in ACC position instead of ON/Run, so FORScan advises to check the ignition. If the ignition is ON, possible reasons are:

• Only for CAN vehicles: if you use an adapter with mechanical HS/MS switch, the switch may be in the wrong MS position. PCM is always on HS-CAN, so the switch must be in HS position at the moment of connect. Attention: it is not recommended to use adapters with HS/MS switch for new cars. Recommended adapters switch between buses in automated way and don't require any user's attention.

• Bad contact of the adapter in the OBDII port. This problem is very popular for cheap low quality adapters. Sometimes it is enough to gently move the adapter in the port to restore the contact. Also, please check the OBDII pins on both adapter and vehicle sides: some pins may be bent or damaged.

• Adapter's malfunctioning.

• Damaged car's OBDII port, connection or wiring. 3rd party equipment is connected to CAN bus quite often and this work is not always done correctly or neatly. Please check the OBDII port and connectors and wires near it for any interference.

Helpful links:

• How to access MS CAN bus using FORScanV2 and modified ELM327

 

[orsom weels]

As from 3.00 into the vid you could hear him tell he had a wrong or faulty key and because of that Forscan keept stuck in the programming mode. If you look closely you can see he can not turn the new key in the II position. The lock smit cut a second key and then he could program it.

Yes, I realise his new key was either the wrong chip or faulty, but the point I was trying to make was we clearly saw him select the option to not delete any keys, just add a new one, but it still deleted the original key, and as he then only had the one 'good' key, he couldn't complete the programming process so ended up with no key programmed. If it hadn't deleted the original key, it should have still worked after disconnecting Forscan.
I 'added' a key to my daughters Fiesta with Forscan, and assumed that it hadn't effected the original, but as the new key was good, and programmed ok, I don't really know for sure that it hadn't deleted and then reprogrammed the original, as well as the new.
I'm not sure what you mean by "If you look closely you can see he can not turn the new key in the II position"? Both keys appear to turn all the way from off, through accessories and ignition on, to the start position, but as neither are now recognised, they won't start the car.

You get the message:
Make sure the ignition key is on and try again.

By the looks of it Forscan is connected to the adaptor. I hope this will help you.

Support Request

Error "Unable to connect to vehicle. Please make sure the ignition key is ON and try again"

The error means that FORScan has successfully connected to the adapter, but for some reason hasn't received any response from the vehicle PCM. This is normal situation if the ignition is OFF or in ACC position instead of ON/Run, so FORScan advises to check the ignition. If the ignition is ON, possible reasons are:

• Only for CAN vehicles: if you use an adapter with mechanical HS/MS switch, the switch may be in the wrong MS position. PCM is always on HS-CAN, so the switch must be in HS position at the moment of connect. Attention: it is not recommended to use adapters with HS/MS switch for new cars. Recommended adapters switch between buses in automated way and don't require any user's attention.

• Bad contact of the adapter in the OBDII port. This problem is very popular for cheap low quality adapters. Sometimes it is enough to gently move the adapter in the port to restore the contact. Also, please check the OBDII pins on both adapter and vehicle sides: some pins may be bent or damaged.

• Adapter's malfunctioning.

• Damaged car's OBDII port, connection or wiring. 3rd party equipment is connected to CAN bus quite often and this work is not always done correctly or neatly. Please check the OBDII port and connectors and wires near it for any interference.

Helpful links:

• How to access MS CAN bus using FORScanV2 and modified ELM327

We can rule quite a bit of that list out,

Yes, ELM adapter connected to laptop/Forscan.

Ignition was definitely on.

Tried CAN switch both ways, made on difference. But interesting that it says above that it needs to be in the HS position, but the pop up banner in Forscan, when plugged in to the S type, asked for it to be set to MS?

ELM adapter is not a cheap low quality item, it came from a reputable supplier and has worked perfectly on several vehicles, including as mentioned key programming.

The cars OBD port is also good, it connects to IDS and other OBD readers etc with no issues at all.

Looking at the Forscan support pages, it seems that it will not connect to 2003 on S types.

"That Jag you have is a different beast and the network structure all though similar to all manufactuters.
It's like a language, Ford speaks Ford and Jag speaks Jag.
No different than the UK tyre (which is correct) and the US tire (which is incorrect)'

" FORScan was never designed to work on that model, the communications protocols are not the same."

Unable to Connect to Vehicle using OBDLink EX - FORScan forum

 

[46421]

Several user have used Forscan to connect to the later S type so i can't tell you were it goes wrong for you.

I had the same problem with the early S type. A mail to the support gave me the answer i needed to get it working.

I do see you are using a older version. I would advice to use the latest version.

Yes, I realise his new key was either the wrong chip or faulty, but the point I was trying to make was we clearly saw him select the option to not delete any keys, just add a new one, but it still deleted the original key, and as he then only had the one 'good' key, he couldn't complete the programming process so ended up with no key programmed.

If you don't abort the Forscan if adding key function fails (or any other kind of programming) the ECU it self gets stuck in the programming mode and won't work anymore. Its bricked. You either need to finish the programming or abort it.

Edit: Sadly as in some YouTube vids they don't show or tell you everything or twist the truth a bid for a nicer video to get higher ratings. In this case it would be a good thing if the author showed what the lock smith has done to save the situation. At the moment we only know that the locksmith cut new key and then finished the programming part.

 

[orsom weels]

Several user have used Forscan to connect to the later S type so i can't tell you were it goes wrong for you.

There is only one report there, but it's a bit contradictory, as that post was made by Ecmbuster, and assuming it's the same Ecmbuster that posts in the Forscan support forum, it's he who states clearly when referring to coding keys to a 2005 S type 3.0l.

I use SDD or JLR with the VCM 1 or J2534-2 Devices
Everytime the VCM 1 changes hands from a Ford to a Jag, the firmware is overwtiten and it's the same with a Mazda.
Back to a Ford, firmware is again written.

FORScan was never designed to work on that model, the communications protocols are not the same.

To program keys, SDD is required if it's not a hacked version.
A legitimate version that has an operator with the NASTF SDRM Credentials.
An illigitimate version needs to be hacked and outside calculations need to be performed to have the access code.

in the post I linked in my previous post.

Whatever, given in Forscan you apparently have the option of not deleting existing keys, you would have thought that even if the new key was incorrect or faulty, the process shouldn't have effected any coded keys. The worst that should happen is it fails to code the new key.
Adding a key worked for you, and for me, but neither of us had a faulty key, so all went according to plan. I wonder if that would have been the case if one of us had a dodgy new key?

I think if anything is to be learned from all this, it's that if you only have the one coded key, you must be sure any replacements you want to add have the correct chip and that it's working, and that you know what you're doing, or there's a risk you could end up deleting the one working key you have, even if you select the option that says 'Keys already known to the PATS system will not be erased'