topscoder
Newbie
Karma: +0/-0
 Offline
Posts: 10
|
 |
« Reply #15 on: October 01, 2020, 12:12:50 PM »
|
|
|
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. |
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #16 on: August 29, 2022, 12:48:16 PM »
|
|
|
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 |
|
|
|
|
Logged
|
|
|
|
justinvw2646
Full Member
Karma: +17/-3
Offline
Posts: 192
|
|
« Reply #17 on: August 29, 2022, 05:07:19 PM »
|
|
|
Deleted, workaround was for P0606, should have looked it up first to be sure.
|
|
|
|
« Last Edit: August 30, 2022, 05:39:37 PM by justinvw2646 »
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #18 on: August 30, 2022, 10:22:39 AM »
|
|
|
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
|
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #19 on: August 30, 2022, 11:58:01 AM »
|
|
|
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 |
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #20 on: April 14, 2023, 06:06:55 AM »
|
|
|
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?
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. |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #21 on: April 14, 2023, 03:01:35 PM »
|
|
|
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.
|
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #22 on: April 16, 2023, 03:57:32 PM »
|
|
|
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 !!!!! |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #23 on: April 16, 2023, 05:45:28 PM »
|
|
|
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". |
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #24 on: April 17, 2023, 06:48:51 AM »
|
|
|
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) |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #25 on: April 17, 2023, 07:42:16 AM »
|
|
|
The problem is not the checksum, that's all I am gonna say.
You guys wanna fuck with this, figure it out.
|
|
|
|
|
Logged
|
|
|
|
|
matchew
|
|
« Reply #26 on: April 17, 2023, 05:24:45 PM »
|
|
|
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.
|
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #27 on: April 27, 2023, 11:38:31 AM »
|
|
|
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? |
|
|
|
|
Logged
|
|
|
|
Tezotto01
Full Member
Karma: +3/-12
Offline
Posts: 97
|
|
« Reply #28 on: April 27, 2023, 11:40:00 AM »
|
|
|
I am looking for a full backup of another ECU and to do the online encoding with ODIS
|
|
|
|
|
Logged
|
|
|
|
|
