BlocMonsieur
12th October, 2021, 09:37 PM
Hello All, I'm new here, and hoping you may be able to help me with some of your collective brain power :top:
TL;DR - is it possible to extract the ISK from a Clio III UCH using an ELM327 cable and DDT4ALL (without any de-soldering of EEPROM chips), or do I need to purchase (at a minimum) a RenoLink cable/software something mroe sophisticated? (I'm trying to avoid buying a CAN CLIP, as it seems like an older tool, and I will rapidly be approaching the cost of having a Renault dealer programme a key, which rather defeats the purpose of my efforts, and just isn't worth it for a car worth so little). I would be very grateful for any help anyone is able to give on this! I must admit that I am a novice in this area despite many hours of reading forum posts on this topic...
My aim is to read the ISK for the car in order to generate the APV (PIN) code to programme a virgin key I have.
I am using DDT4ALL (v2.0 Novembre 2020) on Windows 10. The car is a mk3 Renault Clio from 2009. I am using a cheap generic ELM327 cable - having run the benchmark in DDT4ALL and received feedback on the github page for DDT4ALL, I believe that the cable is working properly and should support the functions necessary to communicate with the UCH over CANBus. I can read other information about keys (number in memory, ID's), VIN etc.
All seems to work as it should in DDT4ALL until I get to the point of sending the manual request (21D8) for the ISK code, at which point the interface returns 'SubFunction Not Supported'. I have even tried modifying an xml file 'UCH_transv_7_0 ' to use some of the functions listed within it, but no luck there either. I suspect that this Hex request is not correct for the UCH in this car.
The link below is to a ticket I opened on DDT4ALL Github page, showing some more details (screenshots etc.).
https://github.com/cedricp/ddt4all/issues/600
(Apologies that the inital post is in French, I thought I might be more likely to get a response that way)
In case it might help someone else, the Hex frame requests I have found through trawling many forum posts on this topic are as follows:Megane 2 Scenic 2 - 21AB
Clio 2 - 21D8
Kangoo, Master, Trafic ( UCH X83,X76, X70, X24) - session 10A0 and 21FF
UCBIC Siemens UCH used on X06, L35, X41, X65 ph2 export, X75, X90, H79 - session 10A0 and 21D8
(The above does not apply to UCBIC BFR BMT Sagem, or other models of UCBIC.)
Laguna 2, Espace 4 - 21DC
Clio 2 (X65) - dump EEPROM via OBD:
230200000020 dump bytes 0 - 31
230200002020 dump bytes 32 - 63 ( contains ISK code)
230200004020 dump bytes 64 - 95
230200006020 dump bytes 96 - 127
230200008020 dump bytes 128 - 159
23020000A020 dump bytes 160 - 191
23020000C020 dump bytes 192 - 223
23020000E01F dump bytes 224 - 255
Bytes from 256-511 are the same with 0 - 255
If you got his far, thanks for reading!
TL;DR - is it possible to extract the ISK from a Clio III UCH using an ELM327 cable and DDT4ALL (without any de-soldering of EEPROM chips), or do I need to purchase (at a minimum) a RenoLink cable/software something mroe sophisticated? (I'm trying to avoid buying a CAN CLIP, as it seems like an older tool, and I will rapidly be approaching the cost of having a Renault dealer programme a key, which rather defeats the purpose of my efforts, and just isn't worth it for a car worth so little). I would be very grateful for any help anyone is able to give on this! I must admit that I am a novice in this area despite many hours of reading forum posts on this topic...
My aim is to read the ISK for the car in order to generate the APV (PIN) code to programme a virgin key I have.
I am using DDT4ALL (v2.0 Novembre 2020) on Windows 10. The car is a mk3 Renault Clio from 2009. I am using a cheap generic ELM327 cable - having run the benchmark in DDT4ALL and received feedback on the github page for DDT4ALL, I believe that the cable is working properly and should support the functions necessary to communicate with the UCH over CANBus. I can read other information about keys (number in memory, ID's), VIN etc.
All seems to work as it should in DDT4ALL until I get to the point of sending the manual request (21D8) for the ISK code, at which point the interface returns 'SubFunction Not Supported'. I have even tried modifying an xml file 'UCH_transv_7_0 ' to use some of the functions listed within it, but no luck there either. I suspect that this Hex request is not correct for the UCH in this car.
The link below is to a ticket I opened on DDT4ALL Github page, showing some more details (screenshots etc.).
https://github.com/cedricp/ddt4all/issues/600
(Apologies that the inital post is in French, I thought I might be more likely to get a response that way)
In case it might help someone else, the Hex frame requests I have found through trawling many forum posts on this topic are as follows:Megane 2 Scenic 2 - 21AB
Clio 2 - 21D8
Kangoo, Master, Trafic ( UCH X83,X76, X70, X24) - session 10A0 and 21FF
UCBIC Siemens UCH used on X06, L35, X41, X65 ph2 export, X75, X90, H79 - session 10A0 and 21D8
(The above does not apply to UCBIC BFR BMT Sagem, or other models of UCBIC.)
Laguna 2, Espace 4 - 21DC
Clio 2 (X65) - dump EEPROM via OBD:
230200000020 dump bytes 0 - 31
230200002020 dump bytes 32 - 63 ( contains ISK code)
230200004020 dump bytes 64 - 95
230200006020 dump bytes 96 - 127
230200008020 dump bytes 128 - 159
23020000A020 dump bytes 160 - 191
23020000C020 dump bytes 192 - 223
23020000E01F dump bytes 224 - 255
Bytes from 256-511 are the same with 0 - 255
If you got his far, thanks for reading!