RomRaider

Hi ,

I have successfully tuned a custom engine M50B30 turbo , and is running very well on MS41.3.

I have one problem which i do not understand.

If i remove the Maf Sensor plug, the engine dies , so it does not switch to Alpha-N maps. I have tuned the Alpha-N maps alot and still the same thing happens.

My question is , how is supposed to work the engine if there is an error with the maf sensor ( ex maf sensor just dies suddenly while driving) ?

On mS41.2 that i had before , this didnt happen.

Am I missing something?

Cheers

I am having the same problem.

If I follow this: https://sites.google.com/site/openms41/ ... authuser=0

I get extremely different values for the tables as show in the datalog and megalogviewer. But realistically the stock values should run the car out of boost.

But how in the stock table can 0 mg/stroke in the TPS table run the engine? I asked in Discord but didn't get much response. I am baffled. Glad to see I am not alone.

I _DID_ get it to run once but on the next flash it didn't work again.

When I unplug (while running and datalogging) the load goes to 0 and the injector pulsewidth gets very small, about 25% of where it should be. IACV still looks good. Can anyone say if load has a value when in Alpha N mode and running on MS41.2?

The 25% IPW is very interesting. The load in MS41.3 is 4x. I wonder if one of the tables isn't rescaled properly in the MS41.3 code. I will try 4x the load in the Alpha N TPS table and see what happens. Probably will not work as the load in the log is 0, not too low, but 0. I would think Alpha N would log guessed load.

Yeah it's interesting. If I use "Alpha N" mode in Romraider under fuel it does start and run, but in the data log it immediately goes to 1389 load and 21ms IPW. And of course my garage reeks of fuel now. So it behaves differently if Alpha N mode is selected or not.

If I had to guess I think the biggest issue is the broken MAF detection is not working. And in MS41.2 there are tables for how this is detected that are not present in MS41.3 at all.

Someone very knowledgeable on discord confirmed. I'll attempt to follow the code to see if I can figure out where the bug is as I get time. It might be a while though.

Hi ,

Good thing is that you have found that it might be a problem on maps or some map is missing . I do not know how to work with the code , so if you find any solution , please share so we bring the ms41.3 code further.

Thank you for replying @piku