[matias54]

Hi guys! I'm new in here. My name is Guilherme and I am a mechanical engineering student who lives in Brazil and love Bimmers.

The idea to create this topic is because I think togetter we can develop something similar to MSS54 topic and discover the full capabilities of E92 M3's!

As much of you know, the main problem is that we dont have public .a2l for this DME. I am starting just now on this project so I just searched some maps by comparing with MSS65 information on the net and some OEM Bins from .0da files.

I am posting 5 winols projects here: Two made by me, other two of the MSS65 (INJ and IGN) and the last one is for MSS60 but only contains IGN side. Comparing both dme's helps a lot to find some maps.

I dont know what most of the maps I found does, so feel free to tell if something is wrong or to add as much information as you can.

I think we can start with the same objectives as MSS54 topic: Cold start delete, Cat delete, Sap Delete, Injection Maps, Ignition Maps, Vanos, Rev Limit, Speed Limit....

I am using Kessv2 to read, write and do checksums. Both clone and genuine tools works fine.

Now, I ask for the gurus of dme tuning like pOlar, Jagwar and other on the MSS54 topic to help us!

Let's do some cool stuff with these cars.

Ps: The M3_E92_Partial is from a M3 E92 MT. Read with kess.

[matias54]

Guys, problems with files upload, will try again tomorrow.

[miguex]

Subscribed

[bigjae1976]

Cool.

My research so far tells me that the MSS60 is a lot more complex than the MSS54.

[Jonzny]

Great idea!

[Garage5]

Weird. Kess V2 didn't work for me. Any updates on this?

[dpaul]

Originally Posted by Garage5

Weird. Kess V2 didn't work for me. Any updates on this?

What exactly does "didn't work" mean? Some specifics might be helpful - what failed; ID, read or write? Kess clone or genuine tool? if so what revision? Year of vehicle and software revision of your DME?

I just used a KessV2 clone ver 5.017 with red PCB board and Ksuite 2.23 software to read my 2011 m3 (MSS60), 231E software. Kess ID'ed the DME correctly and full read produced a 5376Kb file. However, offsets in the file differ from the few "full" reads I've found on the internet (for example, the UIF was at 0x47dc0, rather than 0x7dc0).

I immediately performed a full write of that file back to the DME, as the minimal documentation available for the Kess tool suggests this is necessary to "unblock" the DME. I don't know what that means - perhaps patching the code to defeat RSA signature checks on future writes. That would be wonderful if so.

Then I made a few small changes in the UIF and performed another full write, to see if those changes would be correctly written. The tool reported success without any errors. However, the changes were not written to the DME. Possibly Kess is fooled by some shadow memory re-mapping that the DME performs. One hopeful note was that the vehicle still started and ran correctly.

Haven't tried partial read/writes - will as soon as the weather in Boston warms up a bit. Presumably, the "partial" read will recover calibration data that the tool is capable of writing back to the DME, with RSA and checksums taken into account.

[MartynT]

Full reads/writes work perfectly with my Kess V2.

I haven't tried a partial either though but the writing occurs much quicker than the read.

I just wish it was quicker!

[dpaul]

Originally Posted by MartynT

Full reads/writes work perfectly with my Kess V2.

I haven't tried a partial either though but the writing occurs much quicker than the read.

I just wish it was quicker!

MartynT

A couple of questions;

1) Do you know what parts of the full read actually get written back? I know my UIF doesn't but not sure what does. I also noted that the write took MUCH less time than the read.

2) Would you be willing to post or PM your full read - I'd like to see how it aligns with mine. I'm more than happy to reciprocate.

3) Do you know of A2L or any map information that is publically available for the mss60?

4) Are you thinking about putting together a binary mod tool for the mss60 like the one you did for the mss52/54? That would be awesome.

[MartynT]

Hi believe only the changed bytes get written, hence why the write takes much less time. I could be wrong though!

Shoot me a PM with your details and I'll send my reads.

I'm yet to find an A2L, it would have saved me loads of time.

Yes, i'm currently writting the MSS60 tool.