Rs6
Newbie
Karma: +0/-0
 Offline
Posts: 21
|
 |
« on: August 13, 2016, 09:15:19 AM »
|
|
|
Hello guys!
I hope someone can help my a little on this.
I have a Audi RS6 C5 with Me 7.1.1 ecu. Wanted to decode the rear lambda's so started reading a lot on here. After lots of reading i was not brave enough to do it my self so i decided to let someone with more experience do it.
So i sent the ECU to a guy how does lots of decoding and other stuff and asked to remove the fault-codes for rear lambda's. Received the ecu and mounted it back in the car again. Car started fine so i took it for a drive. Car drove fine and no check engine light! So i came home i turned the engine off. After about one hour i wanted to start the car but the engine didn't start. No faults ware stored and the start RPM was fine.
So i asked the guy who did the software and he said it its not the software but a coincidence. Okay fine, everything can happen with the car so i check everything but all traced back to the ecu.
So i sent the ECU back to the guy how did the software and he flashed the original software back on the ECU. Received the ecu but still nothing. Car wont start.
After that i arranged a used ecu. Put it back in the car and the engine stared fine. Off course it died again do to the immobilizer.
So sent the ECU to the guy again and he removed the immo and decoded the rear lambda's. Installed the ECU back in the car and it started fine so i took it for i drive. Drove fine so turned the engine off. After 1 hour i try to start it again but nothing. Exactly the same as last time. No fault codes and good start RPM.
The guy ho did the software still says it has nothing to do with the software. I believe him because he has lots of experience.
So is there something that would course a not start after a flash and 1 heat-cycle on the ME7.1.1 RS6 ecu? No fault codes present.
|
|
|
|
|
Logged
|
|
|
|
|
nubcake
|
|
« Reply #1 on: August 13, 2016, 12:47:12 PM »
|
|
|
The guy ho did the software still says it has nothing to do with the software. I believe him because he has lots of experience. Or he actually doesn't. Wrong checksum, causes death code. Is stored in the eeprom, so re-uploading the flash does nothing. Has to be cleared manually. |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #2 on: August 13, 2016, 12:50:16 PM »
|
|
|
Or he actually doesn't. Wrong checksum, causes death code. Is stored in the eeprom, so re-uploading the flash does nothing. Has to be cleared manually. 7.1.1 should be able to just be reflashed with correct chksum file and all is well. even later 7.5 is this way as well. |
|
|
|
|
Logged
|
|
|
|
|
nubcake
|
|
« Reply #3 on: August 13, 2016, 01:09:05 PM »
|
|
|
7.1.1 should be able to just be reflashed with correct chksum file and all is well. even later 7.5 is this way as well.
Well, it definitely doesn't work this way with RS6. EDIT: or it actually might work with some flashing tools, can't be 100% certain about that. |
|
|
|
« Last Edit: August 13, 2016, 01:10:59 PM by nubcake »
|
Logged
|
|
|
|
|
prj
|
|
« Reply #4 on: August 13, 2016, 03:00:39 PM »
|
|
|
You need to find someone who has a clue of what they are doing.
All this is solvable in software.
The car does this because the checksum is wrong.
The death code can be cleared in the flash in the same place as it is set. It is enough to flash the ECU with a correctly modified software and it will self-clear it.
Also, if protocol is used to flash the ECU and the flash session completed correctly, I am pretty sure it will clear as well.
|
|
|
|
|
Logged
|
|
|
|
|
nubcake
|
|
« Reply #5 on: August 13, 2016, 03:09:07 PM »
|
|
|
The death code can be cleared in the flash in the same place as it is set. It is enough to flash the ECU with a correctly modified software and it will self-clear it. Needs modifying the asm code, and I don't think that the person who made such a mistake is capable of that. Generally speaking, pretty much anything can be achieved with software modifications, but it all comes down to "who's able to do this" and "if it makes sense to do it". Also, if protocol is used to flash the ECU and the flash session completed correctly, I am pretty sure it will clear as well. Hence the edit. Tried MPPS clone v12 in my case, didn't work. Probably also tried the nefmoto flasher, but I'm not 100% certain about that. Happened a few years ago. |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #6 on: August 13, 2016, 03:59:14 PM »
|
|
|
i have bad flashed 518ak files (forgot ecufix) and reflashed via nefmoto with vcds cable and ecu is ok, no codes.
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #7 on: August 13, 2016, 06:23:17 PM »
|
|
|
MPPS does not use proper protocol to flash.
Hence why MPPS can not update the software version in the ECU and bricks the ECU for example.
Using a tool that uses proper protocol will also clear the death code.
As for the ASM modifications - I can do them, so others can too. All it takes is reversing the EEPROM access routines and finding where it is set.
|
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #8 on: August 13, 2016, 08:51:34 PM »
|
|
|
MPPS does not use proper protocol to flash.
Hence why MPPS can not update the software version in the ECU and bricks the ECU for example.
Genuine? |
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
Rs6
Newbie
Karma: +0/-0
Offline
Posts: 21
|
|
« Reply #9 on: August 14, 2016, 08:26:14 AM »
|
|
|
Thanks guys, really appreciate it! I already read about the P1640 death code. But if i understand it right it sets the P1640 in the fault memory of the ecu? I don't have any faults stored in the ECU when i check with Vag-com. Is it still possible to have a P1640 death code due to a bad checksum without a fault saved? I also did check the bin file with ME7Check and fount 1 fault on the file witch is already on my ECU  |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #10 on: August 14, 2016, 10:14:30 AM »
|
|
|
Genuine?
Yes, MPPS has never used protocol to flash these. Take a genuine fully updated tool, try to update the software version, it will will brick the ecu. It is a tradeoff - it flashes faster than other tools due to this. |
|
|
|
|
Logged
|
|
|
|
Rs6
Newbie
Karma: +0/-0
Offline
Posts: 21
|
|
« Reply #11 on: August 14, 2016, 11:03:54 AM »
|
|
|
What you guys say about i just try to flash the original bin file back on the ecu with the Nefmoto flasher and see if this clears the bad checksum i have now on my ECU? I also did a ME7check on the original bin file and its fine.
|
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #12 on: August 14, 2016, 11:10:07 AM »
|
|
|
What you guys say about i just try to flash the original bin file back on the ecu with the Nefmoto flasher and see if this clears the bad checksum i have now on my ECU? I also did a ME7check on the original bin file and its fine. you should be fine to flash original with nefmoto. |
|
|
|
|
Logged
|
|
|
|
Rs6
Newbie
Karma: +0/-0
Offline
Posts: 21
|
|
« Reply #13 on: August 15, 2016, 12:01:46 PM »
|
|
|
Just flashed the original file back with the nefmoto flasher and the car started right up!!!!  I now have a spare ecu to play with so i flashed the modified bin file i have from the tuner and took the car for a drive again. Shut the car down and tried to start it after 10 minutes and the car just started fine? Anyone has a idea how that is possible? Has the nefmoto software cleared the checksum error? To be sure i took the car for a longer drive (about 30 min) i will try to start it tomorrow again. Did i already said i love this nefmoto stuff  |
|
|
|
|
Logged
|
|
|
|
|
nubcake
|
|
« Reply #14 on: August 15, 2016, 02:50:32 PM »
|
|
|
10 mins probably were not enough to re-check all the checksums.
You can fix the binary with me7sum and flash it afterwards, should be fine.
|
|
|
|
|
Logged
|
|
|
|
|
