After Read (F2), you need to determine what software version you have.
The easiest way is just open it with Windows Wordpad.
Here is the first line of my 808:
X Ò@  Ž 1037380808P53363K0
¼ˆ§ˆ@


The 10373808 number is shown.

X Ò@  Ž 1037375603P_399423

Hi all - I am a new owner of a 2005 CRD. I read through the guide on ECU flash, bought the reader and checked my ECU. I have 811 version, so I downloaded and tried the 811 EGR, FCV delete (Nick's) and noticed in Titanium when I checked for differences, there weren't any?

So maybe someone had already done that I was thinking, so I checked the Stock 811 file and Titanium see's no difference between my original ECU code, the 811 stock code, and Nick's 811 EGR, FCV delete ECU code. Am I doing something wrong here?

Jacktar
Tampa, FL

Can anyone tell me if ECM Titanium is 64 bit compatible?

We are called it 808, which set of 808 determines that it is 808?

Which I think means I have version 603, is this correct?

... editing with a hex editor...

Second order of business, I installed 5V glow plugs. I don't see definitive talk about what needs to be flashed to change the 5V setting. I have a DRBIII and could possibly load the 5V flash via rs232 and a flash card, but I would need to get a flash card first.

Yes.
But the 603 has the older 1/2meg binary. I should probably make a point of this in the first page.
The number isn't shown on the first line in Wordpad.

32bit Titanium works in 64bit Windows 7.

This:
1037380808P53363K0

Yes.
But the 603 has the older 1/2meg binary. I should probably make a point of this in the first page.
The number isn't shown on the first line in Wordpad.

Good for comparing the differences in binary files but editing should be done with an app that can set the CheckSum.

The MPPS software doesn't access the glow plug information which may be contained in the second bank of flash memory.

The file size of my bin file is 1mb. What number isn't shown in the first line in wordpad/notepad?

My first line is:

Tunes are ecu specific. Most ecu bin file's addressed here so far are of 1mb size. The version number in these are in the first line of "text".
The 603 is from an older vehicle which has a 1/2mb size and the version number is near the end of the file. I needed to add this information to the first page of the thread so that I am not confusing those who have 1/2mb files.


My omission. I didn't want to make your question seem impertinent because of me changing the information in the first post, so I mentioned it here.

You definitely have a tune version different than what I have seen to date.

Your 2005 603 is different from the early 603. Now I have to change my numbering scheme!

(For 1mb files) the only reliable version number that works with matching tune to ecu is the one in the first line of text that you see in Wordpad. Yours is 603.

I don't have time now to check the difference between yours and the 811.
Interesting, why is yours different?

I know as soon as Yeti reads this he will be checking though. He is currently looking for the elusive glow plug difference.

...and if I understand where the GP's managment is ...
for what I have understand
526
811
808
812
813
and other have the latest GP's calibration , but I must verify with some test

809
810
600
617
518
516
513
do not have ..........but remember I'm not sure

So you believe that the glow plug values are stored in the map?
Maybe the person who gave you the 5v map exactly the same as the 7v was wrong about the glow plug update?

I posted this in another thread a couple of weeks ago but removed it temporarily until we did some more tests. So far everything seems to work as it should, so I assume it is safe to repost it again here ...

Based on some sparse info about EDC16 error handling I have examined CRD ECU map file and located the necessary locations for disabling various error codes. There are still a few unknowns here but I gathered enough info to make it work for what I wanted to achieve.

To understand ECU error handling the following terms have to be explained:

(1) Error Class Block

Error classes determine the actions upon various error conditions, for example - does a particular DTC activate CEL, is the error code stored in the permanent memory so it can be read with an OBDII scanner, etc. I know the approx. location of Error Class Block but didn't deciphered the structure yet. For DTC disabling error classes aren't needed anyway and you don't modify anything here.

(2) Error Code Block

This memory area contains all DTC codes known by the ECU. Codes are arranged into groups of four and each group forms one Error Path so all codes from the same group have the same Error Class ID. Most likely it was easier for ECU programmers to organize the processing of similar error codes this way and/or the position of code in the list provides some additional info about the error condition. You don't modify anything in this area - Error Code Block is used only to find the appropriate Error Path for each DTC.

(3) Error Path Block

This memory area contains Error Class IDs for each Error Path and this is where things get very interesting. To disable a particular DTC all you have to do is to write a zero to the appropriate location inside this block. I have located memory addresses for both Error Code and Error Path blocks for all software versions I have access to. The necessary tables are here:

http://www.hrastprogrammer.com/jeep/513_DTC.txt
http://www.hrastprogrammer.com/jeep/516_DTC.txt
http://www.hrastprogrammer.com/jeep/526_DTC.txt
http://www.hrastprogrammer.com/jeep/808_DTC.txt
http://www.hrastprogrammer.com/jeep/809_DTC.txt
http://www.hrastprogrammer.com/jeep/811_DTC.txt
http://www.hrastprogrammer.com/jeep/812_DTC.txt

For versions 513, 516, 526, 808 and 812 Error Code Block starts at $E3FDA and Error Path Block starts at $E4872.

For versions 809 and 811 Error Code Block starts at $E39F2 and Error Path Block starts at $E426C.

As I said before, there are still a lot of unknowns here. For example, according to the error code table 222 ($DE) error paths are possible. But error code block contains more than 222*4 codes and they don't have the associated error path. This could be just unused area reserved for future expansion but I am not 100% sure about it. And on 809/811 it doesn't even start where it is supposed to start so I left this area out in those files.

Practical example ... Disable P0102 DTC so you don't have CEL while using ORM (Off-Road Modification - disconnecting MAF sensor to turn EGR off):

Open the appropriate DTC file for your ECU version. My ECU is 513 so I'll open 513_DTC.txt and locate P0102 code inside the table:

[008] P0103 P0102 ----- -----: E4879=16

From the above data you can see that error path for P0102 is 008 and the Error Class ID (16) for this error path is at location $E4879. To disable P0102 all you have to do is to put zero at this location:

Map[$E4879]:=0;

This will also disable P0103 because it is in the same group and has the same error path.

Save the modified map, write it to the ECU and that's it

I was driving with MAF disconnected and CEL turned off for a few weeks without any problem.

Disclaimer: This is all "gray area" and without source code we cannot possibly know how exactly does ECU/ECM work and what could be the additional consequences of this hack! So, if you decide to use it for whatever reason ... I am not responsible for anything - if you destroy your ECU or your car etc. Use at your own risk!

Note #1: EGR can be turned off using different method described in this thread but this is a very nice practical example of DTC disabling technique.

Note #2: I am using $ symbol for hexadecimal notation.

Note #3: I am not claiming that everything I wrote is 100% correct - all this is based on my own examinations, speculations and assumptions. If anyone has more info about EDC16 unit and EDC16 error handling I will be very happy if this knowledge can be shared here so we can all learn from it ...