DEVELOPMENT : MS41.0 to MS41.2 Conversion

mrf582 · **Posted:** Mon Aug 08, 2016 8:40 pm

How to Convert from MS41.0 to MS41.2 using "MS41.2 Conversion.zip" and MS41 Quickflash v2.6+
Step 0. Extract files.
Step 1. Flash 256KB file "MS41.2 1406464 ID12 - M3.bin"
Step 2. Flash either of the following depending on if you have a 2.3L or 2.8L engine
Step 2a. MS41.0 with 2.8L Engine - Flash 24KB file "328i-MS41.0_MS41.2.bin"
Step 2b. MS41.0 with 2.3L Engine - Flash 24KB file "323i-MS41.0_MS41.2.bin"

Read these posts carefully as the files are sourced from them.
MS41.2 Conversion (2.8L) - http://www.romraider.com/forum/viewtopi ... 95#p133695
MS41.2 Conversion (2.8L, AC Fixed) - http://www.romraider.com/forum/viewtopi ... 70#p136670
MS41.2 Conversion (2.3L) - viewtopic.php?p=165006#p165006

ba114 · **Joined:** Wed Oct 21, 2015 2:36 am **Posts:** 980

mrf582 wrote:

This thread will be used to initiate a proper peer reviewed process to create a basemap that can be flashed to an MS41.0 ECU which will result in a conversion to MS41.2 software yet still run the engine as properly as stock if not better.

Can upload the fully converted ms41.0 - ms41.2 basemap i made when i get home if that's of any help. Can't confirm full functionality as far as running goes as i'm yet to finish my engine build and drop it in.

mrf582 · **Posted:** Mon Aug 08, 2016 8:52 pm

Great, let's start with that. Please post that and I can do an initial review.

ba114 · **Joined:** Wed Oct 21, 2015 2:36 am **Posts:** 980

deleted

See post
http://www.romraider.com/forum/viewtopic.php?p=133695#p133695

ba114 · **Joined:** Wed Oct 21, 2015 2:36 am **Posts:** 980

deleted

See post
viewtopic.php?p=133695#p133695

M52Drifter · **Joined:** Sun Sep 06, 2015 2:16 pm **Posts:** 144

I did convert to 41.2 a few weeks ago copying maps I had on my 41.0 tune (COP, catalyst heating, fuel maps, timing, knock ...) and AFR wasn't good, I was too lean at high RPM so I decided to copy acceleration tables because increasing TPS isn't the same than 41.0, and after I was too rich, so I suggest to people who want to convert to have a wideband and log AFR and see what happens.
I think that there are maybe other tables not edited yet which are different between each versions ?

ijd8wn2k19 · **Joined:** Thu Mar 10, 2016 7:08 am **Posts:** 108

mrf582 wrote:

v0.43
- added support to extend MAF Limit on MS41.2 ID12 and MS41.1 ID60
- added 16x16 table to edit MAF in 2048kg/hr mode. MAF Scaling generally only needs to be edited in conjunction with increasing the software limit
- added Engine Speed Limiter (Hysteresis A & B) for MS41.2
- reordered VANOS maps to make it easier to edit RPM axis
- added OBD2 Readiness monitors for MS41.1 ID60 256KB
- removed undefined maps
- fixed Knock window map address order for MS41.2, MS41.1 ID60, MS41.0 ID41.
- added ability to disabled Misfire Detection (MS41.2 only)
- added some rear O2 sensor voltage thresholds that hadn't been integrated yet. thanks ba114.

Big update after a long time. I know there are probably still things that I didn't integrate yet that are posted on the forums but I at least wanted to get this out there so people could start using it.

So when converting ms41.0 to ms41.2 do we just copy knock maps over in the same cylinder order now?

busterhax · **Joined:** Wed Jan 22, 2014 6:54 pm **Posts:** 1773

ba114 · **Joined:** Wed Oct 21, 2015 2:36 am **Posts:** 980

Posting what i put in the MS41.1 conversion thread too:

I've attached a spreadsheet that details the difference in pinouts between MS41.0 and MS41.1/2 ECUs. What's interesting is there are some pins that are inputs on MS41.0, but listed as outputs on MS41.1/2. There are also variations between signal inputs/grounds. This compiled directly from ETMs.

The main differences that i know of between MS41.0 and 41.1/2 are:
- MS41.0 is not OBDII compliant. If you convert to 41.1/2 and want OBD, you'll need to wire in a port (i did direct to DME) and also modify your diagnostic port cap in order for it to function.
- All engines that ran MS41.0 have front mounted CPS sensors just like the M50 based engines. US based cars ran the rear mounted CPS with the trigger wheel inside the crank case. This can result is misfires being incorrectly registered.
- MS41.0 came in various O2 configurations, just like MS41.1/2. My MS41.0 equipped donor car had 2 pre-cat O2s and no post-cat O2s.
- All MS41.1/2 came with SAP, fuel tank pressure sensors, and others that will not be present in the dme wiring for your MS41.0.

Attached are the ECU pinout differences between MS41.0 and MS41.2

zladzejus · **Joined:** Tue May 06, 2014 2:34 pm **Posts:** 63

It is quite a lot of differences in pin's. For one - MAF connection pins are inversed + and -, so that shouldn't be functioning correctly and it would explain why M52Drifter cannot get the engine to work properly.

Has anyone finished converting their 41.0 and has a trouble free ecu?

Having such differences in pin-outs, is possible at all to convert from one to another, without modifying wiring harness?

ba114 · **Joined:** Wed Oct 21, 2015 2:36 am **Posts:** 980

zladzejus wrote:

It is quite a lot of differences in pin's. For one - MAF connection pins are inversed + and -, so that shouldn't be functioning correctly and it would explain why M52Drifter cannot get the engine to work properly.

Has anyone finished converting their 41.0 and has a trouble free ecu?

Having such differences in pin-outs, is possible at all to convert from one to another, without modifying wiring harness?

The problem with the ETMs unfortunately is there appears to be no consistency. One version for '97 models has different pinout allocations to a '98 for the exact same software version.

Further the Bentley manual also lists inputs/outputs differently too.

One thing was consistent in the ETMs though, the MAF + & - was always switched, However we are still able to log the correct MAF readings in OBD scanning and romraider logging. I don't believe this is the issue in M52Drifters case.

Enabled · **Posted:** Sun Sep 18, 2016 11:43 pm

So for my curiosity, and hopefully not too off topic... If I were to flash an MS41.1 DME with MS41.0 ID 41 (for converting a us S50B30 engine with front crank sensor to a flashable DME) would I run into wiring harness problems? The ID41 is well enough defined to use for such a conversion, and still keep misfire detection active.

M52Drifter · **Joined:** Sun Sep 06, 2015 2:16 pm **Posts:** 144

I won't be able to say what was wrong with it because I haven't made logs running on 41.2 but my AFR in full load went from 0.88 lambda to 0.98..

zladzejus · **Joined:** Tue May 06, 2014 2:34 pm **Posts:** 63

ba114 wrote:

The problem with the ETMs unfortunately is there appears to be no consistency. One version for '97 models has different pinout allocations to a '98 for the exact same software version.

Further the Bentley manual also lists inputs/outputs differently too.

One thing was consistent in the ETMs though, the MAF + & - was always switched, However we are still able to log the correct MAF readings in OBD scanning and romraider logging. I don't believe this is the issue in M52Drifters case.

Interesting. If different ecus with different pinouts can have the exact same software version (and all together a perfect software match) then we could assume that the ecu hardware part is tied to its wiring harness. That would mean, that swapping ecus may sometimes be problematic. Aswell, if this assumption could be verified, it would be good news for the .0/.1/.2 conversion topic, as the ecus could not be swapped, but changing the software version would not cause problems with pinouts.

Any further ideas on how to test and verify this?

ba114 · **Joined:** Wed Oct 21, 2015 2:36 am **Posts:** 980

zladzejus wrote:

ba114 wrote:

The problem with the ETMs unfortunately is there appears to be no consistency. One version for '97 models has different pinout allocations to a '98 for the exact same software version.

Further the Bentley manual also lists inputs/outputs differently too.

One thing was consistent in the ETMs though, the MAF + & - was always switched, However we are still able to log the correct MAF readings in OBD scanning and romraider logging. I don't believe this is the issue in M52Drifters case.

Interesting. If different ecus with different pinouts can have the exact same software version (and all together a perfect software match) then we could assume that the ecu hardware part is tied to its wiring harness. That would mean, that swapping ecus may sometimes be problematic. Aswell, if this assumption could be verified, it would be good news for the .0/.1/.2 conversion topic, as the ecus could not be swapped, but changing the software version would not cause problems with pinouts.

Any further ideas on how to test and verify this?

I have an ms41.1 and ms41.0 ecu. My harness is from a '96 euro 328i with ms41.0. I'll test them both back to back with the same ms41.2 tune flashed once I get the engine in the car

RomRaider

Forum rules

DEVELOPMENT : MS41.0 to MS41.2 Conversion

Who is online