DEVELOPMENT : MS41.0 to MS41.2 Conversion

gadziuWLKP · **Posted:** Thu Apr 23, 2020 3:55 am

mrf582 wrote:

Your engine didn't start during Log # 2 because you selected this:

Ethanol - rear O2 bank1

: without connecting an actual Ethanol sensor. The Ethanol logic gets enabled as soon as you tell the ECU you have connected something as Ethanol input. I have put in a default Fuel Trim for Eth in there so people should be able to just install the hardware, flip one table in the tune and run the engine on Ethanol as a base tune.

By not connecting the proper sensor, the code still ran and generated a really high Fuel Trim to add to your cranking tables. This flooded the engine and 'cooled off' your existing O2 sensor.

No big deal though, just nice to know what/why/how something happened

Thanks for posting such detailed data on the topic of custom 0-5V inputs. If I understand you correctly:

Once you selected the correct inputs and set them to their correct scalings, you were able to log the correct values as expected?

Did you say you connected your external wideband to the front O2 sensor wiring and selected that as input in the Wideband setup tables?

And also tried to 'spoof' the MAP table into using the front O2 as input and with the 'correct' scalings, it also showed the correct value? Also, in 'psi or kpa' instead of AFR?

If so, that's good to know. I had only run these tests on my car using TPS voltage. That validated 90% of it especially the code that does the y=mx+b calculation. I actually use two different function types:

: one for MAP that uses full 2 byte precision (for future Speed Density use)
: the rest for AFR, Oil/Fuel Pressure, Ethanol use half 1 byte precision since there is enough resolution there. The MS41 Wiki on Custom Code has the actual resolution values posted.

Your additional testing proved out that the actual variable I've selected for repurposing is correct for Front O2 sensor. So that can now also be classified as confirmed.

At the beginning I would like to clarify the names of the O2 front and back.
Front 02 before catalisator means the input of the probe placed at the factory in the first manifold, i.e. Bank1, i.e. cylinder 1,2,3, counting from the timing, which corresponds to the original harness of the second O2 connector, counting from the timing, which is placed next to the fuel rail.
Rear O2 before catalisator means the input of the probe placed at the factory in the second manifold, i.e. the Bank2 or cylinder 4,5,6 from the timing, which corresponds to the original harness of the first connector 02 from the timing, which is located from the front of the car.

mrf582 wrote:

: without connecting an actual Ethanol sensor. The Ethanol logic gets enabled as soon as you tell the ECU you have connected something as Ethanol input. I have put in a default Fuel Trim for Eth in there so people should be able to just install the hardware, flip one table in the tune and run the engine on Ethanol as a base tune.

Now I understand.

mrf582 wrote:

Once you selected the correct inputs and set them to their correct scalings, you were able to log the correct values as expected?

After yesterday's physical connection of MAP and MAF, ecu displays the correct values, before displaying the values before connecting them, however, it did not show zero values as I expected.

mrf582 wrote:

Did you say you connected your external wideband to the front O2 sensor wiring and selected that as input in the Wideband setup tables?

Initially, during the first tests on 17.04.2020, I attached only one input - Rear 02 input - and it turned out that without connecting anything (the connector was empty), the ECU saw the voltage of 5V and showed the maximum value from the scaling table.

mrf582 wrote:

And also tried to 'spoof' the MAP table into using the front O2 as input and with the 'correct' scalings, it also showed the correct value? Also, in 'psi or kpa' instead of AFR?

For MAP reading, the value was also represented as the maximum, unit kpa.

If you still need any confirmatory tests, I can do them on the inputs available in the controller. Currently, I can disconnect everything quickly by unplugging the plug. I plan to migrate from MAF to MAP and see how the engine will behave. Many people use MAP as the main turbo engine load sensor successfully. I will present the results here on the forum.

Thank you for clarifying the topic.
Unfortunately, I don't have any hardware in the driver for the other inputs.
No O2 after the catalyst and Evap Presure and MIL. I will not use 80,81,82 entries due to being taken by ASC.
Regards!

mrf582 · **Posted:** Thu Apr 23, 2020 12:01 pm

gadziuWLKP wrote:

mrf582 wrote:

Once you selected the correct inputs and set them to their correct scalings, you were able to log the correct values as expected?

After yesterday's physical connection of MAP and MAF, ecu displays the correct values, before displaying the values before connecting them, however, it did not show zero values as I expected.

mrf582 wrote:

Did you say you connected your external wideband to the front O2 sensor wiring and selected that as input in the Wideband setup tables?

Initially, during the first tests on 17.04.2020, I attached only one input - Rear 02 input - and it turned out that without connecting anything (the connector was empty), the ECU saw the voltage of 5V and showed the maximum value from the scaling table.

mrf582 wrote:

And also tried to 'spoof' the MAP table into using the front O2 as input and with the 'correct' scalings, it also showed the correct value? Also, in 'psi or kpa' instead of AFR?

For MAP reading, the value was also represented as the maximum, unit kpa.

If you still need any confirmatory tests, I can do them on the inputs available in the controller. Currently, I can disconnect everything quickly by unplugging the plug. I plan to migrate from MAF to MAP and see how the engine will behave. Many people use MAP as the main turbo engine load sensor successfully. I will present the results here on the forum.

Thank you for clarifying the topic.
Unfortunately, I don't have any hardware in the driver for the other inputs.
No O2 after the catalyst and Evap Presure and MIL. I will not use 80,81,82 entries due to being taken by ASC.
Regards!

Thanks for clarifying where you put the probes and which inputs were selected.

Do NOT run MAP instead of MAF at this time. The stock code is not going to work. The stock code is hardcoded to divide airflow by rpm to get load. If you scale a MAP sensor which represents Load, the ECU will divide Load by RPM, and get something that's NOT load. Also, air temp compensation for SD Fueling is CRUCIAL!

Anyway, long story, don't bother, yet. MS41.3 Stage 2 has the correct provisions

Also, the pullup to 5V the ECU does is helpful in detecting opens or shorts as part of a DTC. If you use a high enough resistance pull-up just enough to bias the float, when an actual sensor is connected, you can detect an open or short depending on if you see 5v or 0V.

Krychol rc · **Posted:** Wed Sep 02, 2020 4:40 pm

Hello

Today I converted id41 to id12.
I have questions, can I move the shock tables along with the axis value ?
Whether to move all tables from the knock section 1:1 ?

dx4picco · **Posted:** Wed Sep 02, 2020 4:45 pm

edit- copy table (yours) - edit paste (in ms41.2)

Krychol rc · **Posted:** Wed Sep 02, 2020 4:54 pm

I know how to copy. I asked can I move all tables from ID41 to ID12 1 to 1?

dx4picco · **Posted:** Wed Sep 02, 2020 4:55 pm

yes you copy everything including the axis from your stock rom

Juli 323i e36 · **Joined:** Thu May 09, 2019 4:06 pm **Posts:** 6

hello

I was trying to do the conversion from ms41.0 (861)version to ms41.2 us m3 file (464) with MS41 Quickflash v2.0.1, at the end of fullflash of m41.2 file message (error finalizing flash! DO NOT turnoff the iginiton! Perform partial or fullflash with original file immediatly or else risk bricking ECU!) was shown, after this i tryed to fullflash the original version but the program cant erased MS41.2 flash. car starts but dont run normal. What i have done wrong and can i save the ecu from braking?

E36Perth · **Posted:** Mon Sep 21, 2020 7:28 am

Hello there.. First post after lurking for some time.

recently flashed from ms41.0 to ms41.2. I have a euro M52B25.
How are we calculating the table values as the axis scaling is different in certain tables? ignition timing, etc.

Fairly new to this kind of stuff, hoping someone may be able to point me in the right direction, Cheers.

tjwasiak · **Posted:** Mon Sep 21, 2020 12:26 pm

There are 2 possible ways around this:
- use your MS41.0 axis and copy values
- interpolate your MS41.0 values for new axis values - taking into consideration that engine with lower displacement will have lower load you are loosing accuracy using this method.

E36Perth · **Posted:** Tue Sep 22, 2020 9:32 am

Appreciate the reply.

i've had a go at interpolating my ms41.0 values, car runs okayy-ish.. now for fine tuning.

e39ns · **Joined:** Fri Dec 13, 2019 5:05 pm **Posts:** 4

just need a quick tip, plan on doing the 41.0 to 41.2 conversion on a e39 with a m52b25, just cant find any stock 41.2 file for a e39 6cyl , so what should I start with since I saw a few people had issues with using e36 maps on it

Lienke · **Joined:** Sun Sep 06, 2020 7:22 pm **Posts:** 9

Hello guys, I successfully converted my ecu from ms41 to ms41.2 but now I'm getting both o2 sensor error, has anyone had this problem before?
I used the US specs m3 fullread and 328i partial (posted by: ba114) while my is 328i euro, might that be a problem?

E36Perth · **Posted:** Tue Oct 06, 2020 2:30 am

Lienke wrote:

Hello guys, I successfully converted my ecu from ms41 to ms41.2 but now I'm getting both o2 sensor error, has anyone had this problem before?
I used the US specs m3 fullread and 328i partial (posted by: ba114) while my is 328i euro, might that be a problem?

Did you disable the O2 Dtc mentioned in ba114 post on page 12?

Lienke · **Joined:** Sun Sep 06, 2020 7:22 pm **Posts:** 9

E36Perth wrote:

Lienke wrote:

Hello guys, I successfully converted my ecu from ms41 to ms41.2 but now I'm getting both o2 sensor error, has anyone had this problem before?
I used the US specs m3 fullread and 328i partial (posted by: ba114) while my is 328i euro, might that be a problem?

Did you disable the O2 Dtc mentioned in ba114 post on page 12?

Yes I did, I'm getting these two errors and I can't delete them, they reappear instantly.
25 - Lambda Sensor Heater -Bank 1
55 - Lambda Sensor Heater -Bank 2

And after driving for a while I also got this error:
244 - Crankshaft Interval Timing
But I cleared it and it haven't reappeared yet.

Update: after driving for a while the 244 - Crankshaft Interval Timing error reappeared. The car is running fine, no lights on the dash, the power is as it should be

Does anyone know what this might mean?

m0ck · **Joined:** Wed Mar 15, 2017 11:44 am **Posts:** 8

Can someone help me sort out some issue?
Converted friend's 328 from ms41.0 to ms41.2, disabled unwanted DTCs (including misfire detection), copied all corresponding maps from the stock 41.0. I'm running into an issue when the engine -sometimes- unstable at idle and has weird rpm oscillation between 500rpm to 900rpm. In addition, sometimes the rpm drops to ~400 and almost stalls after sudden trottle release from full to zero.
Pressing the throttle, there is also slight delay like its choking or a vacuum leak, but there isn't, and everything was running just fine prior the conversion.

It did show 2 errors, TPS sensor and "(P1145) Solenoid Valve" (Vanos?). After clearing the errors out, the "Solenoid Valve" error returns. It doesn't seem the rpm drop and oscillation is Vanos related, or am I wrong?

RomRaider

Forum rules

DEVELOPMENT : MS41.0 to MS41.2 Conversion

Who is online