Pages: [1]
Author Topic: 4B0 906 018 P and 021 906 018 M - Looking for KFMLDMN  (Read 669 times)
rzyao
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 45


« on: December 03, 2024, 09:35:05 AM »

Swapped my 1.8t to a 3 inch MAF, runs but still getting a CEL. Need to find KFMLDMN in these files and swap them over to stop my CEL from turning on.

So far I have 0x1B592 for KFMLDMN in the 4b0906018P file and 0x1A8AC in the 01906018M file, does this look correct? Axes appear correct but it's entirely guesswork based on proximity to KFMLDMX and similarity to an M box file that's already defined, but the values for the 4B0 file seem to be really low.
« Last Edit: December 03, 2024, 10:45:19 AM by rzyao » Logged
fknbrkn
Hero Member
*****

Karma: +186/-24
Offline Offline

Posts: 1469


mk4 1.8T AUM


« Reply #1 on: December 03, 2024, 10:46:18 AM »

The airmass stays the same so why you want to change this?
Logged
gremlin
Hero Member
*****

Karma: +201/-9
Offline Offline

Posts: 679


« Reply #2 on: December 03, 2024, 12:22:37 PM »

Swapped my 1.8t to a 3 inch MAF, runs but still getting a CEL.


Before you invent a problem for yourself, fix a stupid mistake first.
New MAF calibration is incorrectly placed in the 1.8T firmware you posted above.
As a result, you have damaged the MAF offset value and minimum value limit.
« Last Edit: December 03, 2024, 12:51:57 PM by gremlin » Logged
rzyao
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 45


« Reply #3 on: December 03, 2024, 12:35:16 PM »

The airmass stays the same so why you want to change this?

I was looking at it and noticed it was in kg/s instead of voltage, but other posts said it was a good idea to move KFLDMN over (might have been Hitachi -> Bosch)


Before you invent a problem for yourself, fix a stupid mistake first.
New MAF calibration is incorrectly placed in the 1.8T firmware you posted above.

Which map is placed wrong? All I tried to change was MLHFM but I'm not sure exactly what I need to change and I've just been blindly trusting the XDFs I have
Logged
gremlin
Hero Member
*****

Karma: +201/-9
Offline Offline

Posts: 679


« Reply #4 on: December 03, 2024, 01:09:57 PM »

Which map is placed wrong? All I tried to change was MLHFM but I'm not sure exactly what I need to change and I've just been blindly trusting the XDFs I have

Who says that your XDF is correct?

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.
Logged
fknbrkn
Hero Member
*****

Karma: +186/-24
Offline Offline

Posts: 1469


mk4 1.8T AUM


« Reply #5 on: December 03, 2024, 01:56:21 PM »

I've just been blindly trusting the XDFs I have

Who says that your XDF is correct?

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.


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   Shocked
Logged
rzyao
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 45


« Reply #6 on: December 03, 2024, 03:09:28 PM »


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   Shocked

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
« Last Edit: December 03, 2024, 07:30:37 PM by rzyao » Logged
gremlin
Hero Member
*****

Karma: +201/-9
Offline Offline

Posts: 679


« Reply #7 on: December 04, 2024, 02:45:52 PM »

Here is locations of MAF calibrations data  in 018P_0006 firmware
Logged
rzyao
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 45


« Reply #8 on: December 05, 2024, 12:09:07 AM »

Yeah, that looks like it confirms what I had guessed. For some reason every single map for this ECU I found puts MLHFM in the wrong spot
Logged
prj
Hero Member
*****

Karma: +1075/-501
Online Online

Posts: 6073


« Reply #9 on: December 05, 2024, 03:32:42 AM »

Yeah, that looks like it confirms what I had guessed. For some reason every single map for this ECU I found puts MLHFM in the wrong spot

Because software NUMBER and VERSION are BOTH important.
You can't take a random non-matching xdf and expect it to match.

If something is done for 0002 version, it won't work for your 0006 version and vice versa.
Even better, look at the EPK (search for /1/) if the EPK's don't match the defs also don't match.

That's why not writing the version and only writing the software number is dumb, and that's what you have done here as well.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.022 seconds with 18 queries. (Pretty URLs adds 0s, 0q)