Professional Documents
Culture Documents
413 Part1
413 Part1
Page 1 of 4
User
ECU Hackers Forum > BMW Technical > Motronic 3.3.1 DME User Name b Remember Me?
c
d
e
f
g
Name
The 413 Definitive Bin File! Password Log in
Page 1 of 2 1 2 >
10-25-2006, 10:41 AM #1
This is the 413 bin that should be used by people so that discoveries and map locations are correct for one and all
(though its easy to find the same map in another file...just a bit more work! )
Attached Files
stock413v1.bin (64.0 KB, 36 views)
11-29-2006, 08:20 PM #2
Hello Andy.
Its seems that the checksum for the maps section is wrong...
Richard
11-29-2006, 08:29 PM #3
1. The revlimit is at E033h (2 Bytes). Stock chips always have 9065h in that location, which is equivalent 6500 RPM
or 6700 RPM, don't know. Also, I haven't found the algorythm to calculate it. I do know that the crystal frequency
along with other parameters are used to calculate it.
In this chip, that code is repeated at 'F7D8h' also. I haven't seen that in the other chips.
2. The vehicle speed limit is at E0EBh (1 Byte) - C9h-, which is 201 Km/Hr (125 MPH).
Thanks,
Richard
http://www.greystonesagainst3g.co.uk/showthread.php?t=42 06/04/07
ECU Hackers Forum - The 413 Definitive Bin File! Page 2 of 4
11-29-2006, 10:11 PM #4
2 Bytes = Word
So that it's interpreted as 6590 HEX = 26,000 DEC divided by 4 = 6,500
If someone want to test just put in that location 803E and if the formula is right you should rev to 4000 RPM.
11-30-2006, 10:05 PM #5
I would upload the xdf, but the site won't let me.
Attached Files
1094m50mstk.BIN (64.0 KB, 11 views)
12-01-2006, 01:24 AM #6
don't know why you can't upload the xdf. maybe an extension problem? you can probably change the extension of
the xdf to something else.
12-01-2006, 02:46 AM #7
In the checksum xdf, I've added a few more maps and andrew also added a few.
I tried to add an automatic checksum correction via the menu xdf>header info>...checksum (tab) (Ctr + f2)
You must identify the checksum address and the start/stop of the data area. I failed probably failed to identify
the data area.
Attached Files
1094m50m.zip (1.5 KB, 14 views)
1094m50m(CkSum).zip (2.4 KB, 14 views)
12-01-2006, 09:15 PM #8
http://www.greystonesagainst3g.co.uk/showthread.php?t=42 06/04/07
ECU Hackers Forum - The 413 Definitive Bin File! Page 3 of 4
Hello.
Peluca, first of all, hello. I think you are from my home land PR.
About the limiter, maybe you are right. The only thing is that you swapped bytes in the word you proposed for
testing. It should be 3E80h (16000d) and not 803E (32830h). If someone can do the test, it would be great.
About the checksum, yes, the checksum is identified in the begining of the data block as told by Jim Conforti in
some other forum. In this chip, the data block start like this at FDF4h:
F7 A8 F8 B0 E7 E2 92 FB 08 FC 3A...
Always the fifth word (2 bytes) in that line, in this case with value "FC 3A", is the address right after the checksum
that protects the area of the maps. So the area of the maps begins at E000h (in other chips at D000h, but it is
easily identifiable) and ends at "FC3A", including the checksum.
You just go two bytes back that area to find the written checksum (CCFB in this chip) that covers from E000h to
right before the checksum (FC37h).
That is why I said before that the checksum seems to be wrong, because if you do a cumulative checksum from
E000h to FC37h in this chip, the result is CD40 instead CCFB. If you look in other similar 413 chips, the checksum
fit exactly as explained above no problem. Just the begining of the block changes from D000h to E000h.
325icintn; If you would be able to do those two tests it will be nice: Changing the revlimit to something lower for a
safe test and "correcting" the checksum to "CD40" to see if it works fine too.
Regards,
Richard
12-01-2006, 09:36 PM #9
This weekend, I'm installing a replacement stock catback (cheap, used), wideband/logger, diff/trans oil, plus I had
to change a tire on the interstate in 15 F (-9 C) wind chill this morning in rush hour. So I have a tire repair too. I'll
try to burn a couple of new chips, though, and test this theory.
Quote:
F7 A8 F8 B0 E7 E2 92 FB 08 FC 3A...
Always the fifth word (2 bytes) in that line, in this case with value "FC 3A", is the address right after the
checksum that protects the area of the maps. So the area of the maps begins at E000h (in other chips at
D000h, but it is easily identifiable) and ends at "FC3A", including the checksum.
Page 1 of 2 1 2 >
http://www.greystonesagainst3g.co.uk/showthread.php?t=42 06/04/07
ECU Hackers Forum - The 413 Definitive Bin File! Page 4 of 4
Posting Rules
vB code is On
Smilies are On
[IMG] code is On Forum Jump
HTML code is Off Motronic 3.3.1 DME Go
http://www.greystonesagainst3g.co.uk/showthread.php?t=42 06/04/07