Moderator: Luke

Dave Deeda wrote:Hi, I know this topic comes up loads, and I have trawled pages and pages of really helpful stuff that has got me to this point, helped me understand loads, but I could really do with some last details if someone could spare a minute.
So..2004 duratorq 2.4...won't start, have sussed out the flash codes and it says code 13. From a chart I have found, this relates to keys not being read.
I have two keys with chips, have been fine for years. Now not working. Also keys not together, understand that bit.
Last week, went to start, turned over, but needed second turn, but dead.spent day checking things, then for no apparent reason, suddenly started. Fine for a day then won't start and same for days.
Have checked loads of connections, nothing obvious.
Q is...although it reads 13 as key, could this be an transponder issue ? I've checked it visually, but is there a way to check it with a voltmeter? If the transponder has gone, what's the best route forward ?
As another confusing clue, occasionally go to start, and immobiliser light goes out, but won't start, nothing, lights on dash go out and a click from Relay (?) under passenger dash.then oil light goes on for a few seconds, then goes out before immobilser flashes normally... but then usually does the whole flash code13 process again.
Many thanks
Dave...soon to go bald not from hair loss, but from pulling it out..


Altransit wrote:The fault could possibly be in the reader which wraps around the barrel to read the key chip.
It could just be out of place or have a damaged wire

[/quote]knobby1 wrote:
You might need to pull the "actual" fault codes using forscan or IDS, this will give a good idea of where to look...."From the chart I have found, relates to keys not being read" is a bit vague.
Lord Knobrot

Dave Deeda wrote:knobby1 wrote:
You might need to pull the "actual" fault codes using forscan or IDS, this will give a good idea of where to look...."From the chart I have found, relates to keys not being read" is a bit vague.
Lord Knobrot

knobby1 wrote:Dave Deeda wrote:knobby1 wrote:
You might need to pull the "actual" fault codes using forscan or IDS, this will give a good idea of where to look...."From the chart I have found, relates to keys not being read" is a bit vague.
Lord Knobrot
Only just found out how to use the quote button, so I'll post this bit again..

knobby1 wrote:Dave Deeda wrote:knobby1 wrote:
You might need to pull the "actual" fault codes using forscan or IDS, this will give a good idea of where to look...."From the chart I have found, relates to keys not being read" is a bit vague.
Lord Knobrot
Forscan will be quite specific rather than pointing in the general direction...
You can set yourself up with Forscan for less than 20quid.
Download Forscan onto a windows lappy from here:
https://forscan.org/download.html
Modified ELM-327 from here:
https://tunnelrat-electronics.fwscart.c ... tch-elm327
Lord Knobrot

Dave Deeda wrote:One more question..am I right in thinking that if I get a new transponder ring and attach it to the wiring, it should work properly ?
Ie, the transponder ring does not have to be coded to the immobilser and key, it just reads the key ?
Thanks
Dave
Altransit wrote:Straight forward swap, no coding required



Return to Technical Problems & Questions
Users browsing this forum: No registered users
This site contains affiliate links for which we may be compensated.