View Full Version : Boot tricore edc17c46 ktag no read
TuningInside83
29th December, 2018, 02:04 AM
Whi ktag no read edc17c46 vag.?
Protocol used 199.
Ktag master 7.020
KILL_THE_IMMO
29th December, 2018, 07:30 AM
I had the same problem
And when i used p199 all is ok
TuningInside83
29th December, 2018, 07:36 AM
Yes I tryed but dont work. Solution?
chli1976
29th December, 2018, 07:59 AM
Had problem with "Microprotection removal failed". Tried it with serval protocolls and also with byteshooter and does not work. But my ECU was tuned from an other guy. My theorie is, other guy has changed anthing for noread.
Solution was new flash with ODIS. After them i could read it
KILL_THE_IMMO
29th December, 2018, 08:12 AM
I choose edc17c14 and after p199
TuningInside83
29th December, 2018, 08:25 AM
My ecu is edc17c46.
should I first remove the protection via obd and then read with ktag?
TuningInside83
29th December, 2018, 10:33 AM
Solutions???
KILL_THE_IMMO
29th December, 2018, 10:45 AM
u cant read it using obd for me i had edc17c46
when i read it i choose edc17c14 and after p199 and it work for me with the same pinout like c46
TuningInside83
29th December, 2018, 11:32 AM
the pinout for edc17cp14 is different than c46.
How is it possible? did you read the file correctly? both micro and eeprom?
KILL_THE_IMMO
29th December, 2018, 12:04 PM
yes i read correctly
carmageddon
29th December, 2018, 02:09 PM
Whi ktag no read edc17c46 vag.?
Protocol used 199.
Ktag master 7.020
edc17c46 have 2 protocols, 199 and 269, same connections but 199 is for ecu with low TP (below TP8) and 269 is for ecu with minimum TP8
sdtsedat
29th December, 2018, 04:41 PM
Post id, and we give ori vr file. then you can flash over obd
TuningInside83
29th December, 2018, 05:40 PM
It did not work in protocol 199 in Protocol 269. I solved by reading and writing with Fgtech. Thanks to all.
TuningInside83
31st December, 2018, 03:31 PM
Probably the reading error is due to the power supply
I did not have +12
I'll try with 12v 5A power supply next time.
If someone has had the same problem, check this too.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.