NefMoto

Hi all,

Have a mare with this car. Have tuned plenty TTRS and also older SW versions, but this is the first 0040.

Write file in via KTAG - all is good. Then, 1 week later, "Engine management, workshop!" on the dash with the dreaded P0601.

Fortunately I have a full backup so can write back to stock and reflash file, but then it comes back.

There seems to be mixed opinions on fixing whether it be checksum only (file was checksummed in OLS with latest OLS288 - yes, legit OLS) and also written with no checksum.

Ideas?

Ori files is OK.
Your tuning is a problem.

Yes I know. It's a tuning protection that Audi applied. After some time, it triggers this fault and reverts to stock performance.

I need to know how to get round it.

After killing some stuff you will also need to do the cksum properly...if your tool is not genuine it will not do the cksum correctly..

Cmd bdm has not problems on this...Also genuine ktag..if ktag fails support will fix it for you.

Hi there!

Myself and my company has also been suffering with this problem, and we don't know what to do about it.

A customer wanted his 2012 RS3 tuned. Some light mods and upgraded HPFP among other things. I used AutoTuner to read and write it, and that's when the trouble started. It got a checksum error code, and even if the original file that was read with AutoTuner was written again, it still has that same fault code.

I opened a ticket with AutoTuner, but they were unable to help my company with this sometime in the forseeable future. I can not tell if the tool made a mistake, or if the tuned file triggered a tuning protection. Either way it is a problem.

Since the file read with AutoTuner was not valid to write with KTAG, and this model can not be written with KESS (since that function is not allowed/implemented), I bought an original file for the ECU that should be flashed with KTAG. I tried that file, although the problem still persists.

We tried different methods of flashing, checksum correcting etc. etc. but the problem comes back. Tried writing the files separately (CPU, Flash, Immo), and as a K-tag "maps" file to no avail.

The software version is 8P0907404 0060 by the way.

After all of this happened, I heard that there were some issues with this particular car/ECU from other people in the business, but that doesn't help me now after the fact.

Can I get some tips or some help from you fine folks here at nefmoto?

P0601 is in the EEPROM. You'll need to either have it removed from that or flash in an entire different BDM backup and have the ECU adapted to the car.

Its the tuning protection that is active, its possible to fix.

it is fairly easy to have that fixed and you also need the right equipment to flash :)

can you please explain how to do this?

Use a tool to remove the DTC P0601 from the eeprom file and write it back using BDM. Or, try and find a FULL BDM read (MPC, Flash, EEPROM) of exactly the same car with SW. Write that into the ECU and adapt new software to the car (immo) using ODIS.

Just curious, bFlash? KTAG? or?

i am not a friend of "tool" i would like to learn and understand

when you write bflash it shows that you dont know what you are talking about because rs3 i way longer around than any bflash

power in my case does not decrease, i dont have a real ori eeprom because car was pretuned by mtm and some folks say you have to do it with bdm100 instead of ktag blabla

its just about the p0601 in my case

bFlash is a tool that writes to this ECU via OBD. Your comment makes no sense either - of course the car is round longer than the tool. How can you make a tool to work on a car before it exists???

my intention was to say that the "right equipment" was available bevore bflash and autotuner

check topscoders other posts... looks like autotuner is not the right equipment  :-X

I think there are 2 different "problems" in these ecu. First is the P0601 error which is maybe just because of not correct checksums. The second is that in newer ecu is a harcoded monitoring which does not even set any error, but you get message in cluster and power is gone. In generic OBD values you can see something is wrong. This happens after some driving time, i dont know when it´s set. Maybe after several transgression from boost, vmax, or whatever. Anyway it´s a hardcoded problem. In past i read sometimes that car was tuned fine and after one week it´s driving stock again. Not sure if that part from ecu can be written via OBD anyway...

My point of view: checksums are made over all parts. Including MPC. If e2p or other part is overwritten, but mpc not, The checksums are corrupt. ECU knows there is some “tune” existing and does a fallback to a shadow copy which contains stock data.

Result: permanent p0601 kicks in. Even ODIS S or E cannot fix this as the MPC is not written either by ODIS. I tried all that, including online Odis account.

It seems not a lot of tools (sorry for the word ;)) can write all parts over OBD. But bFlash should do it. CMDflash and Arbrites also afaik.

Also I believe P0601 is permanently erased (DTC Off) by tuners in order to workaround this issue.

This is what I think after my research until now. Will try to fix P0601 using KTAG next week in MED9.1.2 RS3.

Sorry to dig up the topic, I am running a 2012 year TTRS with software 8J0907404N 0030 that has been remapped by another preparer in the past. When I write the original file via OBD with Flex from MagicMotorsport the P0601 error appears.
Writing the read file (Modified) the error disappears, it seems to me that the error has been removed from the modified file.
One problem I am facing is the loss of power at full load, both with modified and original file, can someone help me?
Sorry for any language errors, English is not my native language.

https://log.tunezilla.com/s/pl0K9Ypt

Deleted, workaround was for P0606, should have looked it up first to be sure.

I will try to do this test, my question is if the boost loss issue has to do with the P0601 error or are they two problems that I will need to solve, today I am tuning the car with a bigger turbo, HPFP boost and LPFP upgrade

Here is one more torque data record, NOTE: MDNORM = 500 in file
I have the car tied up on the dynamometer, if anyone wants to look at any records just let me know



https://log.tunezilla.com/s/vkPMrGI6

Can you share this full backup?
I have a car reprogrammed by another tuning company and it is getting this checksum error when I go back to the original file.

I did the removal of the P0601 error through the file but am having strange behavior in the car so I would like to save an original backup and code the ECU in the car and start from scratch on the reprogramming.

VAG did pretty good on these.
Tunprot still fucking noobs up a decade later.

Tho the C5 RS6 where that first was introduced has an even longer track record.

What's the use, I'll humiliate him and tell him how big my dick is and live happily ever after !!!!!

It was done to reduce the amount of warranty claims, due to the modern mindset of "it ain't my fault, I didn't do nuffin".

All the posts I find about it say to merge the flash and eeprom files by correcting their checksum together, but my tool (Flex) already gives me both unified and corrects the checksum automatically.
Even when saving the ori file I have DTC P0601.

The problem is that this car has been tuned previously at another tuning company and the dtc was deleted in the tuning file.
I would like to run this car ori without the DTC P0601.



Translated with www.DeepL.com/Translator (free version)

The problem is not the checksum, that's all I am gonna say.
You guys wanna fuck with this, figure it out.

P0601 Literally means "Anti-tuning triggered". Be it detected by digital signature failure or other means. You'll not get around this with "DTC delete" or any other trivial method. The anti tuning strategy implemented in this ECU is interesting to say the least. Once it has been triggered by a file made my someone clueless to this method, the ECU will always have this code unless it is cleared (be it by code changes, or by manually clearing the flag). No amount of flashing a stock file will clear this code once it is lodged.

Any idea how I can solve this?

I am looking for a full backup of another ECU and to do the online encoding with ODIS