I have tried all suggestions an still the nanocom will not read the security code even tried a different ecu
I dont understand what you mean with the bolded part... no need to read the security code it's about making the ECU to learn it, there's no way to read that code cos it's not readable with nanocom.(i hope you dont confuse the security code with the EKA code). If two engine ECUs refused to learn the security code then IMO the problem is with the BCU(which can be the cause of flashing M+S too) or with the connection between it and the ECU on the code link(providing it's not some operator error)...for that link you should make a continuiity test on that wire across ECU black plug C0658 -34 and BCU C0661-10(see RAVE - Electrical ibrary - connector views) though it would be easyer to rule out the BCU first
if the eka code is not correct or if the key fobs are flat could that cause problems
As long as nanocom can comunicate with the BCU and modify settings the EKA code is no factor cos it means it's not immobilised and the fobs have nothing to do with the learn security code function which is in the engine ECU section.
Discovery Td5 (2000), manual, tuned
Bookmarks