PDA

View Full Version : EDC17CP44 Read



Jerak
29th November, 2019, 01:28 AM
I have:
2014 Volkwagen, Tourareg II (7P)
3.0 TDI 240HP generation II
ecu EDC17CP44-Tricore (TC1797)
CNRB 7P0907401K H21 0011 (2018) SW 564344

Kess Boot Pin gives:
BOSCH EDC17 VAG TPROT8/10 (282) > BOSCH EDC17 CP44 VAG (P268) > TOOL > ECU DATA
Protocol not correct. Use protocol 226.

BOSCH EDC17 VAG (226) > BOSCH EDC17 CP44 VAG (P203) > TOOL > BACKUP READ
MICRO unprotection failed.

Kess OBD gives:
Volkswagon > Touareg II (7P) > CNRB, 2012 OBDII (453) > ID
has the software reporting that my ecu is unknown


I have the "updated" China Kess:
Firmware: v5.017
Software: KSuite 2.47
with:
WF = Infineon, BCR112 NPN Digital Transistor
27E = ON Semiconductor NUP2105LT1G
6DW = NXP BC817,215 NPN Bipolar Transistor
A6c = MMUN2113LT1G / MMUN2113LT3G
K5B = BC807-25-7-F PNP Bipolar Transistor
imported Japanese muRata filter NFE61PT472C1H9L

This vehicle had the North American update. Has anyone been able to read this ecu after the 0011 (2018) update?
Thank you.

figani
29th November, 2019, 07:05 AM
Better not read it with your clone...
It will not end good...

Make a research on forum/Internet...
Up to 2009 it's possible with clone...

Your are member here since 2011, you have never read about this problem...?

Jerak
29th November, 2019, 04:40 PM
Thank you.

I am not too worried about taking a read with this clone because I have had the ECU on the bench a few times.
I have updated the Kess microSD card protocols and re-tried boot loading with a few versions of K-Suite.
So far no damage has been caused to the ecu.

I just wonder if anyone has read this updated ecu with Kess original, Kess re-chipped or clone.
And what protocol worked.

Lambda1
29th November, 2019, 04:59 PM
kess 453, ktag 268.
OBD did VR Read.

Jerak
29th November, 2019, 05:39 PM
Did you use original or Russian Kess 5.028?
I can't get a VRead on the China 5.017.

Lambda1
29th November, 2019, 05:44 PM
Original tools. Clons never did virtual reads from server... because they had no connection to server...
russian guy use his own.

Jerak
29th November, 2019, 05:59 PM
Alright, thank you.
I knew that VR is not possible so I do have the .frf (and extracted .bin) for my car so I don't really need the read.
My worry is (from the first post), that "the software reporting that my ecu is unknown".

I just don't want to be the first person to try to write via OBD with a clone on this vehicle without a spare ECU.
Original Kess is way out of my price range.

Jerak
1st December, 2019, 04:21 AM
I see that KSuite 3.37 has included my ecu (maybe) in its \Update folder.
From FL0301.csv:
VOLKSWAGEN;TOUAREG (7P5);3.0L V6 24V TDI 176kW/236HP EDC17CP44;FLASH_0376 VAG BOSCH EDC17CP44;FLASH_0376;5495;;;7P0907401 0011;0x00000008

Okay, mine is 7P0907401K not 7P0907401, but it is 0011.
Some hope.

There is talk of a KSuite3.37 version that works for some China 5.017s but so far it seems to be a miss.

Jerak
11th December, 2019, 10:16 PM
For the next guy:
I have found out that the original 2.47 (not China) also had this update, a little different though:
VOLKSWAGEN;TOUAREG (7P5);3.0L V6 24V TDI 176kW/236HP EDC17;FLASH_0376 VAG BOSCH EDC17CP44;FLASH_0376;5495;;;7P0907401 0011

I copied the Update files to my China software and my Kess seemed to update with them.
No EEFFACE trouble.
But, trying to do an ID on the car, it still says that the ecu is unknown.