Renault Forums :: Independent Renault forum - View Single Post - Renault - Clio - Replacement key w/central locking button

View Single Post
post #13 of (permalink) Old 7th March 2007
Junior Member
Join Date: Feb 2007
Posts: 11
Nominated 0 Times in 0 Posts
TOTW/F/M Award(s): 0
Thanks: 0
Thanked 2 Times in 1 Post
Hello guys, i'm new to this forum and been reading carefully all your posts on this subject. There seems to be quite a bit of confusion here. I have the original service/technical manual cd´s from Renault and it cover´s all cars till 2004. The manual states that the procedures above and found wildly on the net is for re-sinchronising the remotes only! Is when the frequency is alredy programed in the car and the remote goes out off sync with it. It is NOT for peogramming a new remote frequency in to the car. The ONLY way to do it is with the diagnostic computer at Renault or a dealer that has one. You can onle program 2 remotes at once. As for programing the car to acept a new key (transponder chip) it can ONLY be done on the diagnostic computer too, and you can program up to 4 keys, witch is kind of dumb IMHO as if you shoud be alowed to program 4 remotes as well. So that saied you can buy a key on e-bay (will save you about £90) but you still have to spend some to get the car programmed to the key.
Resuming all of this, it is the CAR that´s programed to acept a new key (transponder signal), so the car doesn´t care if the key is new or used. What the dealer does is conect the immobilyser to the diagnostic computer and put the immob. in lerning mode to clear all the codes programed into it and then it is told to acept the new code from the key. If you have another key you have to bring it too as the immo.'s "memory" is cleared and then programed to acept the codes again.

Note: this is for RF fobs, i dont know if it´s the same for IR ones
Currently in jorgemncardoso's garage:
2005 Renault Clio Extreme

Last edited by jorgemncardoso; 7th March 2007 at 01:46 PM.
jorgemncardoso is offline  
For the best viewing experience please update your browser to Google Chrome