Strange VAG EDC17cp14 problem

[z786]

Hi, i have been fighting with this car for months

i have wrote files in with 2 different tools via bootloader

once ecu is plugged back in car, ignition is turned on, i read via obd the maps have randomly changed, DPF switch is also turned back on

i have put in tprot off file, but when i try writing via obd fgtech says ecu not programmable, x17 also flags up error

in the obd reads, both tools fail to read checksum

is there anyway to fix this ecu to read write via obd or stop it changing the maps?

thanks

[z786]

nobody can help???

[wiseman]

Bump......

[J_amb_o]

Write ori back IROM only using full, not data, on X17. Then write ori back over OBD.

[z786]

if i write ori IROM back the tprot will be in affect, how will i write via obd?

[J_amb_o]

You can write ori back over OBD as it is a signed file so will pass TP.

[z786]

so once i write original over obd then how do i get dpf off?

[jnoroeste]

Hi M8,

Unlock and read on bench then should be able to write&read by Eobd.
Seems you are using the read before unlock.

Regards.

[z786]

my friend, i have done maybe 20 edc17 in last few months

this is only 1 that is strange

even when machine tries to read via obd ecu doesnt let it read full checksum, therefore it can not identify the maps

galletto gives the message "ECU not programmable"

willing to pay for solution

[filecloud]

What are the ecu numbers?

[z786]

i havent got car here but i got a screenshot of x17 maybe that will help?

thanks

[filecloud]

Hello
Wrong protocol for this ecu! This is CANA edc17cp14 with external rom. Cannot be done over OBD at all. In Bootmode you tune external rom which contains only maps, over OBD you touch only internal rom which contains program area and some inactive data.
greetings,
filecloud

[z786]

so how isit when i read over obd i can read xrom?
even i fgtech menu it identifies cd016 spansion

here is obd read and what i wrote in bootloader

even when i try writing in a file with dpf off, the switch is on when i read obd

iv used x17 and fgtech and both act same way

[Babos]

try this one maybe this working for you.
pass in PM

[filecloud]

so how isit when i read over obd i can read xrom?
even i fgtech menu it identifies cd016 spansion

here is obd read and what i wrote in bootloader

even when i try writing in a file with dpf off, the switch is on when i read obd

iv used x17 and fgtech and both act same way

But it does not write it!
Read irom in bootmode and see what i mean.
:-)

[z786]

Can u pm me ur Skype /email plz

[filecloud]

Can u pm me ur Skype /email plz

Let's discuss it here so everyone can learn. Read irom in bootmode please and post it.
greetings,
filecloud

[J_amb_o]

So you've been writing it back over OBD?

[z786]

ok maybe i typing it wrong

lets start from beginning

audi a6 came in for dpf removal

i wrote dpf off file

1 switch in irom and a few switches in xrom

after i put ecu back in car, car was still in limp mode

i reset ash counter in VAS and car was normal

after every 200 miles dpf light on, limpmode

reset on VAS, normal again

now when i read file via obd it reads alot of stuff different, it also shows the switch for dpf is on again

i have never managed to write this ecu via obd, even tho i have wrote TPOT off in irom

all i need is to keep that dpf switch off

could it be software in ecu makin switch back on?

as said before willing to pay for solution

[filecloud]

ok maybe i typing it wrong

lets start from beginning

audi a6 came in for dpf removal

i wrote dpf off file

1 switch in irom and a few switches in xrom

after i put ecu back in car, car was still in limp mode

i reset ash counter in VAS and car was normal

after every 200 miles dpf light on, limpmode

reset on VAS, normal again

now when i read file via obd it reads alot of stuff different, it also shows the switch for dpf is on again

i have never managed to write this ecu via obd, even tho i have wrote TPOT off in irom

all i need is to keep that dpf switch off

could it be software in ecu makin switch back on?

as said before willing to pay for solution

Once again.
Post your full bootloader IROM read original and we are able to explain how memory adressing works in this ecu and what you actually read over OBD.
greetings,
filecloud

[z786]

irom file attached thanks

[filecloud]

Perfect.
The explanation is the memory overlap function of external rom and ram. This symptom will happen on similar ecus like CCWA or CDYA also. Nothing to worry about. All tuning tools will read false data here.
Since this ecu has TP7 active anyways it is not possible to tune it over OBD. Use your bootloader to write external rom for tuning. You can read it out to verify the content in bootloder mode.
greetings,
filecloud

[z786]

any reason as to why the ash counter counts up and throws car into limp mode after dpf removal?

[Stanton]

Because soot loading model is still active.

[z786]

any chance u wud point me in right direction plz

[Stanton]

I can't help with address but you probably need to find location for application mode for soot loading, enable by setting to 1 then set the override value to 0.
See if you can get an A2L and strategy guide for this or similar software.

[z786]

not enuff time :(

[guille_masco]

What is the solution to this? read and write via bootloader always?

[z786]

any1 here willing to give solution for ash loader and dpf off???