In your file the values now
MLMIN = 1077 kg/h (should be -200 kg/h)
MLOFS = 1086 kg/h (should be 200 kg/h)
Your MAF now shows the weather in Paris, not the air flow...
KFKHFM is also slightly corrupted at one point.
none of the XDFs I've found online show those values, so I was just going based off of the table for MLHFM that seemed consistent across multiple XDFs. Could you send me the definition you're using to check those? I did also notice KFKHFM was corrupted but for some reason never actually fixed it, that one's on me
My location for MLHFM appears to be from 0x10D8A to 0x11188, 512 rows. Same for every single definition file I have (in both TunerPro and WinOLS), and there's one single data point (in every bin file I tried, including a completely stock file) that reads as 6353.6 at 4.95 volts/0x11180 immediately followed by random numbers between 0 and 1,000. So, now I'm just more confused as to what's going on
And can someone give me a sanity check that I do indeed need to copy MLHFM from the VR6 file into the 1.8t file when I swap to a VR6 MAF sensor + housing? From reading a bunch of posts that *looks* to be what needs to happen, and it appears that it's "portable" across ECUS but I would love to hear directly from someone that actually understands ME7
always wonder how the people take the map showing some random values like '0 2334 -23 9966' and is like .. nah thats seems fine, ill go with it
everything I touched seemed like it had the correct values and seemed to make the changes I wanted, the only thing I've messed with that seemed suspect was MLHFM having no axis values but for good luck I will probably start again from a completely stock file
EDIT: It looks like MLHFM had the wrong offset, the map continues smoothly starting from 0x10D80, which also cuts what I assume to be MLOFS (a cell with value of 200) out of the map as well as the other misplaced data. Will see how it runs with MLHFM copied down starting at that address
