BMW 404 & 484 M60B40 E34, E32 & E38 tunes

[Mykk]

Hey guys,

I just recently picked up a Burn 2 and was able to read a couple OE chips. One from an E34 540i Auto, the other an E32 740i Auto. Both with chip numbers 1 267 358 720, 1 744 050. They are subtly different from each other and drastically different then the 357689 404 tune on the TunerPro site.

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

Hope it can help anyone else out there. Cheers -Mykk

[Mykk]

Also, here is the XDF I've made for the 404. It's far from complete, but I made it by pulling apart the hexcode and using the readily known axis identifiers. It also has automatic checksum correction, just remember to save your bin before loading it to your emulator or burning a chip for the checksum correction to take effect.

Again, it's not perfect and it's not yet finished. The temperature factor & offset have sent me through a loop so for now temp axis are improperly labelled. But it's far better then the 404 XDF available for download on the site.

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

[Mykk]

Here is another E34 540i Auto 404DME that came in. Production 6/1994. Chip # 1 744 050, 1 267 358 720.

It is slightly different then the previously posted E34 540i and E32 740i tunes.

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

[Mykk]

Here's a 12/1995 E38 740il, 484DME chip numbers, 1 744 605, 1 265 358 772. This is an EWS file. It will not work with the existing XDF, I believe this this to be a DME for the non-vanos M62B44. I'll spend some time with it in order to make an XDF.

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

EDIT: Midas' XDFcreator has recognized several maps in the 484 .bin. I'll spend some time with it and see what I can recognize and what not. I already see Idle, PT, WOT Fueling and also Idle, PT, WOT ignition. From what I can tell, despite the data side of the .bin being drastically different and all the MAP addresses are moved around the tables themselves are very similar to the 404 tunes.

[Mykk]

Here's a quick 484 .xdf with the maps identified by pulling apart the hex code. The axis are unlabelled since that is the most time consuming part of the process. Checksum correction is in this xdf. If someone can find it useful and build upon it, that would be cool.

If and when I find out how to disable EWS in the tune I'll update it to the .xdf

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

[Laimis]

Hi, could you please check XDF link ? It's the same link for .bin file as in previous post. Thanks

[Mykk]

Today I was able to get my hands on the rare and elusive E34 540i/6 404DME original chip. You have no idea how hard it was to find one of these as a 404DME. Every take out DME I could find was auto trans, I'm happy to present the manual tune. There are more changes between the two in the coding then you would think. Here you go:

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

Here is an updated and cleaned up version of my 404 XDF, still with many unknown tables.

https://drive.google.com/file/d/0B3ENo4 ... sp=sharing

[Hairyscreech]

I was just going to take a look at these BINs after your comments in the other thread, I just had a thought though, these files should have the same ID at the end as the 413/506 files.
There should be a small table down in the 0xFF00 range that lists the start of each of the data sections, it also points out the table of tables making map ID easy from there.
It should be easy to find as it is surrounded by areas of blank data (0xFF) so easy to spot.

You should be able to quickly find all of the required maps in each of these files.

If your not sure what I mean then take a look at the spread sheet, it has this area highlighted.

[Mykk]

I can verify on both 404 DME and 413 Red DME, at address FE14 there are five hex code addresses (that I can recognize).

404:
C0 00 - Start of table code
C1 1A - DTC's on/off
C2 A6 - MAF table w/ header
D0 3E - Table of Tables
D1 4A - End of table code

413 Red:

D002 - Start of table code
D106 - DTC's on/off
D28E - MAF table w/ header
E67E - Table of Tables
E7B2 - End of table code

Do you know how to read the rest of the data in these end section of the code?

[Hairyscreech]

Yep, the 413 BIN on the excell sheet has as much as I know of that area right now.

It contains the ECU number, the ECU chip number and the BMW part number. The hex needs to be converted into ASCII and then read backwards. :rol: (cause that's convenient).

Would love to work out what the rest of it means, I think it may be more important that we yet know. I think there may be a few more clues in there that could open up a bit more stuff.

I took a look at your 404 bin the other day and added it to the sheet, while it is not quite the same as the 413 (M3.3 vs M3.3.1) it is very similar. Like a pre-evolution of the 413 almost.

The human readable hex addresses are pointing to the self references that start each of the sections.
You will find your Table of tables at 0xD03E where the self reference points to.

[olafu]

413 Red:

413 red with 623 bin:

D002 - Start of table code - Also it seems to tell checksum starting point, with -2 offset? I did some tests, and it seems to act like this.
D106 - DTC's on/off
D28E - MAF table w/ header
E67E - Table of Tables
E7B2 - End of table code - Also tells checksum location and end of checksum calculation area. I did tests and succesfully moved checksum location.

There is also own checksum for fault codes, because there is own checksum error fault code (DTC 202) for fault code area checksum I didn't found that fault code area checksum yet.

[Mykk]

I should update this thread with most current xdf for the 404:

https://drive.google.com/file/d/1WZMXGT ... sp=sharing

[theownit]

have you got new XDF for 404 or 484 ecu ?

[bomj911]

Mykk would you still have xdf file for 484 ews ecu by any chance old link wont work no more, and i think ews delete on 484 ews is at 0FE80 change 00 to FF.

[Sinbad98]

Thats a really helpful Information. I am also Building two 484 XDFs. I tried today starting a 530 bin with 0FE80 changed to FF. it worked.
At the next step i tested a 540 binary with modified Maps (Part throttle, WOT) and 0FE80 changed to FF. This did Not work.

Tomorrow I test it without changes, an original 540 bin only with „EWS Off“. I do Not know if my own XDF has a failure.

[bomj911]

I tested all the stock files 740i, 530i 540i AT and 6sped, they all work on the simulator . https://youtu.be/9fa8akZq_R8?si=SlDZ8M16ZMG4bGiU

[bomj911]

Thats a really helpful Information. I am also Building two 484 XDFs. I tried today starting a 530 bin with 0FE80 changed to FF. it worked.
At the next step i tested a 540 binary with modified Maps (Part throttle, WOT) and 0FE80 changed to FF. This did Not work.

Tomorrow I test it without changes, an original 540 bin only with „EWS Off“. I do Not know if my own XDF has a failure.

Are you able to test this file on a car its a 540 6speed.

[Sinbad98]

Hey hey,

This week I was working with your Information. It is working. The EWS Position is correct. But you Need to know: There a two types of 484s. One has a Brown Label, the other has a white/silver Label. It is Not possible to interchange the binarys. U Need to use the right binary. (Just use for correction the original binary)

The EWS Location on Both is the same (0FE80).

[bomj911]

Hey hey,

This week I was working with your Information. It is working. The EWS Position is correct. But you Need to know: There a two types of 484s. One has a Brown Label, the other has a white/silver Label. It is Not possible to interchange the binarys. U Need to use the right binary. (Just use for correction the original binary)

The EWS Location on Both is the same (0FE80).

The brown label 484 had no ews far as i know, there is no ISN so that's why it dose not have ews.