NefMoto > Technical > Flashing and Chipping > Help! AGU with V6 MAF Sensor. Rescaling 1.8T M3.8.3
Pages: [1]
« previous next »
Author Topic: Help! AGU with V6 MAF Sensor. Rescaling 1.8T M3.8.3  (Read 7055 times)
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« on: September 02, 2019, 09:23:52 AM »
Hi,
I need help to be able to use a Golf IV V6 MAF sensor on my 1.8T AGU. I cannot find the mistake in my tune, the car starts but runs unsteady and misfires.
Of course I changed the pin out for the 5 pin new MAF housing.

1. -
2. 12V
3. Sensor Ground ECU Pin 12
4. 5V
5. Sensor Signal ECU Pin 13

And I checked the funktion of the MAF sensor.

my approach at the tune:
I locate the MLHFM Maps and convert them into Airflow in kg/Hours.

AGU with M3.8.3: factor 0,125/ offset -200
V6 with ME7.X: factor 0,1/ offset -200

Now I scale the V6 map from 1x512 to 1x246 and change the negativ Values to 0.

Does anybody know where my mistake is ? Or can explain how to rescale the AGU KLHFM Map correctly for the newer generation of MAF sensors?
Thank you very much
Logged
BlackT
Hero Member
*****

Karma: +80/-42
Offline Offline

Posts: 1475
« Reply #1 on: September 02, 2019, 09:59:48 AM »
You use MAF sensor for M7.x ECU on M3.8
Why you do that?
Logged
eliotroyano
Hero Member
*****

Karma: +48/-12
Offline Offline

Posts: 833
« Reply #2 on: September 02, 2019, 10:12:15 AM »
Also sensor orientation inside MAF are different.
Logged
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #3 on: September 02, 2019, 11:15:02 PM »
Because I want a bigger MAF sensor, and the V6 MAF sensor is easy to instal on the original airbox.
Logged
BlackT
Hero Member
*****

Karma: +80/-42
Offline Offline

Posts: 1475
« Reply #4 on: September 02, 2019, 11:31:52 PM »
Post you boths, new and old map.
Or simly find a housing from VR6, or some ATMO BMW or MERC
Logged
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #5 on: September 03, 2019, 12:50:52 AM »
Yes, I will do it later. Do you want the complete map with all values or just a picture of the graph?

The V6 is easier to fit in my car and I already installed it. But must be possible because people also drive S3 MAF sensors on M3.8.3, and that's the same typ or not?
Logged
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #6 on: September 03, 2019, 03:19:03 AM »
These are all values of the AGU and the V6, without factor or offset.
Logged
BlackT
Hero Member
*****

Karma: +80/-42
Offline Offline

Posts: 1475
« Reply #7 on: September 03, 2019, 04:17:27 AM »
Can you post table
voltage and g/s
Logged
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #8 on: September 03, 2019, 05:44:35 AM »
Sure
Logged
eliotroyano
Hero Member
*****

Karma: +48/-12
Offline Offline

Posts: 833
« Reply #9 on: September 03, 2019, 06:38:42 AM »
Quote from: ni97 on September 02, 2019, 11:15:02 PM
Because I want a bigger MAF sensor, and the V6 MAF sensor is easy to instal on the original airbox.
you can use a VR6 12V MAF that is totally plug n´play. Other plus is you can use the MLHFM map directly for that sensor.
« Last Edit: September 03, 2019, 06:47:44 AM by eliotroyano » Logged
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #10 on: September 03, 2019, 07:09:12 AM »
Yes I know, but I have the V6 MAF Sensor and the airbox already  Roll Eyes  Aside from that I am interested how to use these newer MAF sensors like from the S3 on M3.8.3 becouse its seems to be possible. I thought maybe someone here knows how.
Logged
eliotroyano
Hero Member
*****

Karma: +48/-12
Offline Offline

Posts: 833
« Reply #11 on: September 03, 2019, 07:29:30 AM »
Quote from: ni97 on September 03, 2019, 07:09:12 AM
Yes I know, but I have the V6 MAF Sensor and the airbox already  Roll Eyes  Aside from that I am interested how to use these newer MAF sensors like from the S3 on M3.8.3 becouse its seems to be possible. I thought maybe someone here knows how.
Logged
ni97
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #12 on: September 03, 2019, 08:23:14 AM »
Are you sure about the pinout? i figured out that the AGU ECU don’t send 5V to the MAF sensor.
I think ECU Pin 12 is Signal Ground and ECU Pin 13 is the signal. I took the 5V from the throttle.
Logged
marantzvieta
Full Member
***

Karma: +3/-1
Online Online

Posts: 80
« Reply #13 on: Today at 02:30:13 AM »
Hi, sorry to revive this old thread but i am in the same boat, swapped in a VR5 MAF that uses a HFM5 MAF with a M3.8 ecu, so MLHFM is a good known one for M3.8.

But after copying MLHFM from the VR5 ecu, my car also runs unsteady and with misfires. I suspect I need to copy too KHFM but I am not sure if a different KHFM will affect other maps related to load... KHFM is 43XXX in 06A906018CG (M3.8.3) and 32XXX in the VR5 ECU (M3.8.3), curiously like the M3.8.2 ecu's.

Does anybody have any input about it before I try KHFM too?

Thank you so much.

Best regards,


Quote from: ni97 on September 02, 2019, 09:23:52 AM
Hi,
I need help to be able to use a Golf IV V6 MAF sensor on my 1.8T AGU. I cannot find the mistake in my tune, the car starts but runs unsteady and misfires.
Of course I changed the pin out for the 5 pin new MAF housing.

1. -
2. 12V
3. Sensor Ground ECU Pin 12
4. 5V
5. Sensor Signal ECU Pin 13

And I checked the funktion of the MAF sensor.

my approach at the tune:
I locate the MLHFM Maps and convert them into Airflow in kg/Hours.

AGU with M3.8.3: factor 0,125/ offset -200
V6 with ME7.X: factor 0,1/ offset -200

Now I scale the V6 map from 1x512 to 1x246 and change the negativ Values to 0.

Does anybody know where my mistake is ? Or can explain how to rescale the AGU KLHFM Map correctly for the newer generation of MAF sensors?
Thank you very much
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • June 08, 2025, 02:46:49 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.021 seconds with 15 queries. (Pretty URLs adds 0s, 0q)