Renault Twingo 2 Phase II + ELM327 : problème de scan d'ECU

[raphaelyancey]

Bonjour,

Tout d'abord merci aux contributeurs pour le travail que vous faites.

Mon objectif : retrofitter une autoradio pas d'origine sur une Renault Twingo 2 Phase II

Connectique identique à celle qui marchait (qui était elle aussi pas d'origine). Ce n'est pas exactement le même modèle en revanche.

Elle s'allume mais au démarrage indique "Connect Diag Tool"

Après quelques recherches j'ai conclu qu'ils fallait indiquer le VIN/CRC du véhicule dans l'ECU de la radio pour qu'elle soit reconue.

J'ai donc acheté un clone ELM327 Wifi avec une puce PIC18F25K80 (j'ai ouvert et vérifié, c'est bien le cas) puis installé ddt4all avec une base de 4000+ ECUs.

Mes problèmes :

• Lors du scan des ECUs en CAN : aucun résultat
• Lors du scan des ECUs en KWP : 1 résultat

DAE_X44_E33_V1.9_20100323T115323.json DIAGVERSION [9]SUPPLIER [373] SOFT [3241] VERSION [3045] {1885}

C'est la direction assistée donc ça ne m'intéresse pas malheureusement. En revanche pour tester, j'arrive bien à lire les données en direct avec cette ECU (par exemple les rpm moteur). Je n'ai pas tenté d'écriture car je ne veux rien altérer.

---

J'ai quand même essayé de sélectionner à la main les ECUs de mon modèle dans la liste, la plupart me renvoient NO DATA mais certains renvoient les bonnes valeurs (notamment l'odomètre, mais je ne sais plus dans quelle ECU)

Comment ça se fait que je n'arrive à lister qu'une ECU ? Est-ce que je m'y prend mal ?

Est-ce un problème de matériel ?

Merci d'avance !

Benchmark de mon ELM327

v1.0 ATZ [OK] v1.0 ATE1 [OK] v1.0 ATL0 [OK] v1.0 ATI [OK] v1.0 AT@1 [OK] v1.0 ATAL [OK] v1.0 ATBD [OK] v1.0 ATBI [OK] v1.0 ATCAF0 [OK] v1.0 ATCFC1 [OK] v1.0 ATCP 01 [OK] v1.0 ATCS [OK] v1.0 ATCV 1250 [OK] v1.0 ATD [OK] v1.0 ATDP [OK] v1.0 ATDPN [OK] v1.0 ATH0 [OK] v1.0 ATI [OK] v1.0 ATIB 10 [OK] v1.0 ATIB 96 [OK] v1.0 ATL1 [OK] v1.0 ATM0 [OK] v1.0 ATMA [OK/TIMEOUT] v1.0 ATMR 01 [OK/TIMEOUT] v1.0 ATMT 01 [OK/TIMEOUT] v1.0 ATNL [OK/TIMEOUT] v1.0 ATPC [OK] v1.0 ATR1 [OK] v1.0 ATRV [OK] v1.0 ATSH 001122 [OK] v1.0 ATSH 012 [OK] v1.0 ATSP A6 [OK] v1.0 ATSP 6 [OK] v1.0 ATCM 123 [OK] v1.0 ATCM 12345678 [OK] v1.0 ATCF 123 [OK] v1.0 ATCF 12345678 [OK] v1.0 ATST FF [OK] v1.0 ATSW 96 [OK] v1.0 ATSW 34 [OK] v1.0 ATTP A6 [OK] v1.0 ATTP 6 [OK] v1.0 ATWM 817AF13E [OK] v1.0 ATWS [OK] v1.1 ATFC SD 300000 [OK] v1.1 ATFC SH 012 [OK] v1.1 ATFC SH 00112233 [OK] v1.1 ATFC SM 1 [OK] v1.1 ATPP FF OFF [OK] v1.1 ATPP FF ON [OK] v1.1 ATPPS [OK] v1.2 ATAR [OK] v1.2 ATAT1 [OK] v1.2 ATDM1 [OK/TIMEOUT] v1.2 ATIFR H [OK/TIMEOUT] v1.2 ATIFR0 [OK] v1.2 ATIIA 01 [OK] v1.2 ATKW0 [OK] v1.2 ATMP 0123 [OK/TIMEOUT] v1.2 ATMP 0123 4 [OK/TIMEOUT] v1.2 ATMP 012345 [OK/TIMEOUT] v1.2 ATMP 012345 6 [OK/TIMEOUT] v1.2 ATSR 01 [OK] v1.3 ATCRA 012 [OK] v1.3 ATCRA 01234567 [OK] v1.3 ATD0 [OK] v1.3 ATFE [OK] v1.3 ATJE [OK] v1.3 ATJS [OK] v1.3 ATKW [OK] v1.3 ATRA 01 [OK] v1.3 ATS1 [OK] v1.3 ATSP 00 [OK] v1.3 ATV0 [OK] v1.4 ATCEA [OK] v1.4 ATCEA 01 [OK] v1.4 ATCV 0000 [OK] v1.4 ATIB 48 [OK] v1.4 ATIGN [OK] v1.4 ATPB 01 23 [OK] v1.4 ATRD [OK] v1.4 ATSD 01 [OK] v1.4 ATSI [OK] v1.4 ATFI [OK] v1.4 ATSS [OK] v1.4 ATTA 12 [OK] v1.4 ATCSM1 [FAIL] v1.4 ATJHF1 [FAIL] v1.4 ATJTM1 [FAIL] v1.4 ATJTM5 [FAIL] v1.4b ATCRA [FAIL] v2.0 ATAMC [FAIL] v2.0 ATAMT 20 [FAIL] v2.1 ATCTM1 [FAIL] v2.1 ATCTM5 [FAIL] Result: 86 succeeded from 95 ELM Max version:v1.4

[busheyko]

Perhaps the xml version for the block does not match the block itself. Select an earlier version of the block, less than v 1.9.

[AndyIreland]

Good morning,

First of all, thank you to the contributors for the work you do.

My goal: to retrofit a non-original car radio on a Renault Twingo 2 Phase II

Identical connectors to the one that worked (which was also not original). It is not exactly the same model, however.

It turns on but on startup it says "Connect Diag Tool"

After some research I concluded that you need to enter the vehicle's VIN/CRC into the radio's ECU for it to be recognized.

So I bought an ELM327 Wifi clone with a PIC18F25K80 chip (I opened it and checked, it is the case) then installed ddt4all with a base of 4000+ ECUs.

My problems:

• When scanning ECUs in CAN: no results
• When scanning ECUs in KWP: 1 result

DAE_X44_E33_V1.9_20100323T115323.json DIAGVERSION [9]SUPPLIER [373] SOFT [3241] VERSION [3045] {1885}

It's the power steering so I'm not interested in it unfortunately. However, for testing purposes, I can read live data with this ECU (for example, engine rpm). I haven't tried writing it because I don't want to alter anything.

I still tried to manually select the ECUs of my model from the list, most of them return me NO DATAbut some return the correct values ​​(notably the odometer, but I no longer know in which ECU)

How come I can only list one ECU? Am I doing this wrong?

Is this a hardware issue?

Thanks in advance !

Benchmark of my ELM327

Have you wired up cable specially so you can read the CAN2 through the OBD2 socket?

if its an rlink 1 unit you got choose mfd5.4

[raphaelyancey]

By "it doesn't read back" I meant it isn't saved: the write command succeed but I can't read the data I wrote afterwards. Unlike other fields where it works fine.

[AndyIreland]

By "it doesn't read back" I meant it isn't saved: the write command succeed but I can't read the data I wrote afterwards. Unlike other fields where it works fine.

ah right - your car hasn't got a security gateway on it , blocking changes being written no? - I am not familiar with your twingo 2 PH2

[raphaelyancey]

I don't think so...

The only parameters I didn't managed to write were acoustic parameters. I think the radio is expecting it so I copied it from the previous radio and tried to write it on the new.

Only Phone acoustics works. I succeeded by starting pyren in --cfc mode - then doing a Configuration Reset of the ECU to clear any previous memory fault with my previous tries - then start a Classic Diagnostic session (and not Extended Diagnostic) then write the field. Not sure if everything was needed in that order though.

One particularity is that the Phone acoustics fields is the shortest of the three acoustic parameters - only 622 chars

0x00fa0d01fffa012c1101fffb01f40901fffd03200901000003e81d01000004b01d010000060e1301fff806401301fffb0960090100000c1c050100000c80050100000fa00901000000fa0701000602761701fffc03201901000403e80901000005780901000006400f01fffb07080901000407d00901fffd0960090100030af0090100000bb8090100000e740901000000fa095a280017700117700003753000060000000001388000fa140000000014000900000000000000000000010003d70a01fff1ffceffe70004fca4fd08fd6cfdbcfe07fe48fe7ffeb1fee3fefcff06ff10ff1aff24ff2eff38ff42ff4cff56ff60ff6aff74ff7eff88ff92ff9cffa6ffb0ffbaffc4ffceffd84a00000102030000000000000000000000000000000000000000000000000000000000000000000000000000

Doing the same processus but writing to Whole Car (1836 chars) results in pyren returning Wrong response

0x0d055d00000100000100001e00001e0000010000017fffff0d102f07ff07ff07ff07ff0d1034047f032f047f047f0d10560bfe0c6e0ebc0ebc000000000d107a07ff0d107f07ff07ff07ff07ff07ff07ff0d112103d3000707a70c0e05b307ef0ee50673004004e60c81037906ba0f2005e900f503d30deb03740de60f3f02a500ae054a0d5c02a800750f440d113d03d3000707a70c0e05b307ef0ee50673004004e60c81037906ba0f2005e900f503d30deb03740de60f3f02a500ae054a0d5c02a800750f440d115905b2000303660c07011e07f80ef30371000a06e40c1403c707ea0f3f017b001002f70c20044707dd0ef3068d0033051b0c670105076c0f010d117505b2000303660c07011e07f80ef30371000a06e40c1403c707ea0f3f017b001002f70c20044707dd0ef3068d0033051b0c670105076c0f010d119306e803f10772084303c603d8008e07bc05520c35028c03ff063d080207b203fd01c307fd05c10c02037d03ff076f080205e403fd009107fd069f0c020d11b106e803f10772084303c603d8008e07bc05520c35028c03ff063d080207b203fd01c307fd05c10c02037d03ff076f080205e403fd009107fd069f0c020d11cf03d303f1052e089e075503c102d2076104d70c4c02b5030c077302b1043e01f9008d0d4e010b0efa00c503f70377083b01bc03e0048807c4057d0c280d11ed03d303f1052e089e075503c102d2076104d70c4c02b5030c077302b1043e01f9008d0d4e010b0efa00c503f70377083b01bc03e0048807c4057d0c280d120b00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000d123301ad03e8062208180000040001dd07e706530c1701b903e80268081a00000400059807e506460c170d1247028303ff02010803046a03fd05ff07fc01120c030d125101c103e802ae081b00000400055207e4063e0c1701d603e8077f081d00000400008107e206290c170d126500000000000000000000000000000000000000000d126f002a02d207aa0a5b002a02d205f907f701c20c080d12a106ed000205da0c05052007f90f4400bf0003017f0c06050107f90ee5002f000300600c06050907f90f0100360c6e076b0ee200370c6f07400f030d12c004c7000b01900c17048907e60eea03c0001007810c2005e207da0f0101100e2105690f1b00b30d6704660ef2d3d5

Is it a buffer problem? I'm using a PIC18F25K80 WiFi ELM clone.

[AndyIreland]

yes , I have read that before where the ELM buffer may not be sufficient - i think the suggested one is a v-linker .... but i could be wrong on that . A search on here should throw up something about the buffer issue on the acoustics

[raphaelyancey]

Sooo I somehow managed to write the largest parameter (Whole Car) with ddt4all... but I don't know how. I think I switched the session to AfterSales just before, the CAN timeout was 600ms, and I didn't use flow control. I just witnessed that in the specific moment it was being written, the rate of the CAN commands in the terminal monitor was A LOT faster than previous tries, like it was 10s by second instead of 2/3 usually.

That's wizardry I think 🤷

One parameter left tho, couldn't write it even if it's smaller than this one

[raphaelyancey]

I finally managed to fill all the configuration of the radio, but I'm still getting the Connect Diag Tool message and I'm not prompted for entering the code.

I plugged back the old radio and checked again, everything is the same.

I do have 2 DTC errors though, but I already had it on the old radio:

DTC #0
DTCDeviceIdentifier : [930d] Front Right Loudspeaker
DTCFailureType : [11] circuit short to ground
DTCStatusAvailabilityMask : 57 [0x39]
StatusOfDTC : [10] Default not yet checked by the ECU
DTCDeviceAndFailureTypeOBD : 37645 [0x930d]
DTCFailureType.Category : [01] General Electrical Failures
DTCFailureType.ManufacturerOrSupplier : 1 [0x1]
DTCStatus.warningIndicatorRequested : 0 [0x0]
DTCStatus.testNotCompletedThisMonitoringCycle : 0 [0x0]
DTCStatus.testFailedSinceLastClear : [00] No
DTCStatus.testNotCompletedSinceLastClear : [01] Yes
DTCStatus.confirmedDTC : [00] No
DTCStatus.pendingDTC : 0 [0x0]
DTCStatus.testFailedThisMonitoringCycle : 0 [0x0]
DTCStatus.testFailed : [00] No

DTC #1
DTCDeviceIdentifier : [930d] Front Right Loudspeaker
DTCFailureType : [12] circuit short to battery
DTCStatusAvailabilityMask : 16 [0x10]
StatusOfDTC : [10] Default not yet checked by the ECU
DTCDeviceAndFailureTypeOBD : 37645 [0x930d]
DTCFailureType.Category : [01] General Electrical Failures
DTCFailureType.ManufacturerOrSupplier : 1 [0x1]
DTCStatus.warningIndicatorRequested : 0 [0x0]
DTCStatus.testNotCompletedThisMonitoringCycle : 0 [0x0]
DTCStatus.testFailedSinceLastClear : [00] No
DTCStatus.testNotCompletedSinceLastClear : [01] Yes
DTCStatus.confirmedDTC : [00] No
DTCStatus.pendingDTC : 0 [0x0]
DTCStatus.testFailedThisMonitoringCycle : 0 [0x0]
DTCStatus.testFailed : [00] No

I found nothing in the UCH regarding the radio. I guess I'll check again if I'm not missing something.

Anyway, let's say I had the proper CLIP hardware, is there something ddt4all can't display but CLIP can? If a mechanic do connect the diag tool, what are they supposed to look for that I can't see?