Pages: [1]
Author Topic: Does permanent solution exist for "Death Code" (DTC 16985)?  (Read 11758 times)
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176



Hi Guys,

As far as I understand from the below topics:
http://nefariousmotorsports.com/forum/index.php?topic=2973.0
and
http://nefariousmotorsports.com/forum/index.php?topic=915.0

Permanent solution for "Death Code" (DTC 16985) doesn't exist and this error can appear in any chipped ECU with immo-off at any time. So in order to avoid stop the car at some place with the death code owner should have spare ECU with same flash-file and EEPROM. According to above in order to avoid this error we shouldn't defeat immo (use immo always after chipping the ECU).

Is my understanding correct?

Thanks in advance!
Logged
CoupedUp
Full Member
***

Karma: +0/-0
Offline Offline

Posts: 59


« Reply #1 on: June 26, 2013, 05:44:37 AM »

There is a way to prevent this but it is not recommended and for that purpose I won't 'advertise' it in this thread. However, if you look hard enough you'll find your solution. Like I said though, it is not recommended so READ!
Logged
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176


« Reply #2 on: June 26, 2013, 08:40:39 AM »

There is a way to prevent this but it is not recommended and for that purpose I won't 'advertise' it in this thread. However, if you look hard enough you'll find your solution. Like I said though, it is not recommended so READ!
You can send me PM with the way Smiley

Or maybe only some ECUs affected?
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #3 on: June 26, 2013, 11:14:47 AM »

The only time this happens is if you have a corrupted file. You can put the ecu in test mode so that it ignores checksum errors, but just fix the file? The code will never randomly occur.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176


« Reply #4 on: June 26, 2013, 12:55:24 PM »

The only time this happens is if you have a corrupted file. You can put the ecu in test mode so that it ignores checksum errors, but just fix the file? The code will never randomly occur.
Hi Daz!

What do you mean under "corrupted file" eeprom or flash? So if I upload eeprom and flash-file with correct CS in that case I'll never have this error? How can I check properly CS?
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #5 on: June 26, 2013, 12:57:13 PM »

I assume he recalculates the csum by hand when he adjusts bytes in areas that are checksummed?

I suppose somebody could write a csum eeprom checker, but that would require somebody to document what is checksummed and what isn't.
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655


« Reply #6 on: June 26, 2013, 01:03:30 PM »

this thread has so much confusion in it.
Logged
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176


« Reply #7 on: June 26, 2013, 01:12:02 PM »

this thread has so much confusion in it.
Ok, let's clarify the topic.
We have "death code" error  how we can permanent solve this issue? Why reason of the issue? In order to solve this we should only upload eeprom and flash file with correct CS?
Logged
ddillenger
Moderator
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #8 on: June 26, 2013, 01:15:03 PM »

The deathcode is set when the engine fails to start due to a flash checksum error. The error is recorded in the eeprom and must be manually cleared. I flashed 100x to try to clear it, but in the end I had to manually remove it from the eeprom, and then write it back to the ecu. It will come back after a few start cycles IF you don't fix the problem itself, which is a bad checksum in the flash.

Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
tbm
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 176


« Reply #9 on: June 27, 2013, 06:36:14 AM »

Thanks a lot guys! It's clear for me.
Logged
mods4cars
Newbie
*

Karma: +1/-1
Offline Offline

Posts: 5


« Reply #10 on: August 14, 2013, 03:25:39 PM »

The deathcode is set when the engine fails to start due to a flash checksum error. The error is recorded in the eeprom and must be manually cleared. I flashed 100x to try to clear it, but in the end I had to manually remove it from the eeprom, and then write it back to the ecu. It will come back after a few start cycles IF you don't fix the problem itself, which is a bad checksum in the flash.



100% correct  , it normally happens when you modify  a tuned  me7 file into ols which messes up CHK  .  lines 1 and 2  near the end 003  in the 95040  Smiley
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.02 seconds with 17 queries. (Pretty URLs adds 0s, 0q)