RomRaider

I have most of my fueling dialed in so my method seemed like the easiest way of keeping it "correct"

I think Bosch vs Siemens is about as close to an "apples to oranges" comparison as they get.
Sure they both run a similar engine, but how they do it is apparently as different as different gets.

I'm just saying that trying to make comparisons between the two is a good way to get confused.

In anyway we just continued tuning my friends car. There were quite much problems caused poor wiring, old sensors and the car even was missing vss wire because it was originally with m50b20tu using ms40.1.

But now when all is mostly sorted out, I did some tuning and all seems to work fine. Highest load I could see with 0,55 bar boost was 750mg/stroke. Now when I use 1k resistor maf scaling with 2,2k resistor. So plenty of headroom for rising boost level. Shame we couldn't do it this time because the turbosmart eboost is pain in the ass to use. And of course I had to test the car because we were at the track: https://www.instagram.com/p/BVK5YFSgR9Y/

It now only needs ignition advance fine tuning in dyno. But before that I need to sort out why the injector pw goes up after the vanos returns normal position in high rpm. The AFR goes from 12,5 to 10 when that happens. I have zeroed out the vanos correction map, but still that happens.

Yep, you're on the right track. I have posted about this here and outlined it years ago for a Subaru application.
https://forums.nasioc.com/forums/showth ... ?t=1363692

Basically, yes, we want to identify and multiply by 0.5 (or 0.25) all values in the code that are either MAF (kg/h) or Load (mg/stroke). Most of the relevant tables are already defined but I have yet to add the MAF related Accel Enrichment tables. Throttle related Accel Enrichment is already defined. There may also be some other tables not yet defined that require multiplying by 0.5 (0.25). And of course the corresponding Logger Definitions change to show 'real' values.

This basically requires systematically searching for all instances in the code that use MAF (kg/h) or Load (mg/stroke), defining them so you all can modify it. This is a lot of work, and is certainly on my 'to-do' list. And this method is exactly what I meant when I mentioned a more 'comprehensive' fix earlier.

I have some thoughts on doing this via a custom ECU ID that can be recognized by RomRaider so it will know the base code has been modified as such and display all tables and logged values correctly. If someone who has the ability to chip-level flash (I think Abel does?) wants to run a couple of tests for me (incase something goes wrong), we can move forward with this approach. The benefit of using a custom code approach is I'll also be able to rewrite what logged values are being reported using the main DS2 command so we can get all relevant tuning variables returned in 1 group reply instead of having to log several different groups which slows logging down considerably. I think we can get a 10Hz logger for all critical parameters this way (including Knock, and MAF, etc) as opposed to the 3-4Hz that it ends up being now.

This sounds like a really good idea! i have a couple of spare ECUs that i can test with, but dont have the ability to flash chips directly.

I have a socketed ms41.

Would it be simpler to change the calculation of load in a similar fashion to the calculation change of kg/hr for 2048kg/hr and just apply the new formula via definitions to all data that share that load calculation? Or give the main fuel/timing tables their own specific calculation that allows for higher load limit and leave everything else alone?

I have an MS41 with a burned camshaft position sensor driver (doesn't recognize any camshaft position sensor), which I can use for experimenting as well. Would love to socket it as well for easier flashing if needed.
Let me know.

OK, cool. Abel, we'll start with you since you have the most expendable ECU. Send me your current ROM so I can edit it and I'll send it back modified (just for custom ECU ID test) and with a special set of ECU definitions to test. Not sure exactly how to address the Logger ID part yet but worst case we do an add-on Logger definition.

I'll convert it to MS41.2 and get you a fullflash.

Just checking in here to report I have also halved my maf table, and all data points referencing load. So far so good, tuned up to 5 psi wastegate spring. Max load so far is around 450mg/stk. Setup still in progress:





5psi graph above^

I do have some strange issue in 1st gear when boost comes in, the car falls flat on it's face. 2nd gear and higher no issue. Will have to dig into it more. I will attach a log of this if anyone is curious to look. Unfortunately there doesn't seem to be enough logging speed to see what is going on.

EDIT: Looks like my incorrect setup of rev limiters after converting to ms41.2 is to blame Car is happy now

Mine is also running pretty much exactly how i want it to as well. peak loads at just over 22psi have been around the 1000mg/stk area.

Have got open loop dialed in fairly well at around 11.7:1. my biggest issue these days is keeping traction long enough to get clean logs.

Theoretically you can induce some turbo lag by retarding* the timing at the lower rpm, no?

I have the same problem ,at 3500-4000 rpm in 2nd and 3rd gear hard jolt and power is cut, how did you solve that problem?


Отправлено с моего Redmi Pro через Tapatalk

wheres your MAF located?

Left side? Do you see before throttle body?