Pages: 1 [2] 3 4
Author Topic: M3.8.X Stage 1 maps & procedure  (Read 8423 times)
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #15 on: June 01, 2023, 01:45:11 PM »

Nobody knows about this? Further research I've done has demonstrated it's definetly related to N75 duty cycles, KFLDTV map.

Does somebody have any insight on how to read the info in the log properly and tune accordingly?

Kind regards,
Logged
doktor
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 36


« Reply #16 on: November 11, 2024, 02:15:56 PM »

Hi marantzvieta,
thank you very much for your excellent effort. You inspired me to try a first step and convert a 150hp AGU engine (m3.8.3) to 180hp AJL maps. However I have a slight problem with the KFZW map, which is 16x12 in AJL and 16x16 in AGU. Did you do a simple resample? If the axes in the map packs are correct, they seem to have slightly different values and limits, which would mean a proper inter/extrapolation would be required from perfectionists point of view.

Thanks
Logged
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #17 on: November 11, 2024, 03:38:36 PM »

Hi doktor,

Yes, you are correct I performed a simple interpolation and also used a bit of common sense. I used the perfectionist point of view you mention, even helping myself with excel charts to do calculations and observe different values that may work, and it proved to be a good investment in time. My car runs awesome.

Last load lines in AJL map are 8,25 and 9,25 (from memory). When I converted to M3.8.3 ecu, I used 9,25 load line values for 9 and 10 load lines in M3.8.3. I used them in load 10 line too because as 9,25 is it's last line, it uses those values for anything from 9,25 and above, so I considered it safe to be done this way.

Also used 8,25 values for load 8 line as I considered a difference of 0,25 in load to be almost insignificant, and it did actually prove good results in my case.

Always double check the changes you make, do logs and use common sense. Better be safe than sorry.

I am happy to hear my work has been useful to you. Please let me know if you need further help.

Best regards.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6034


« Reply #18 on: November 11, 2024, 03:57:58 PM »

If anyone is interested I can dump the M3.8.x stuff I have also on my site.

I do have a file with specific injectors (Bosch green EV6) + MAF that is re-calibrated and all problems are fixed (cold start, acceleration enrichment, load cap, excessive fuel dump on WOT etc), and uses HFM5, so the MAF is not NLA.
It can take you to ~360-370hp.

I think anything more is better to switch to ME7 or standalone. There is no good datalogger for this old ECU and it just becomes a pain with the load limit and injection time limit. I spent a crazy amount of time 10+ years ago calibrating that stuff.
« Last Edit: November 11, 2024, 03:59:46 PM by prj » Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #19 on: November 11, 2024, 04:26:24 PM »

If anyone is interested I can dump the M3.8.x stuff I have also on my site.

I do have a file with specific injectors (Bosch green EV6) + MAF that is re-calibrated and all problems are fixed (cold start, acceleration enrichment, load cap, excessive fuel dump on WOT etc), and uses HFM5, so the MAF is not NLA.
It can take you to ~360-370hp.

I think anything more is better to switch to ME7 or standalone. There is no good datalogger for this old ECU and it just becomes a pain with the load limit and injection time limit. I spent a crazy amount of time 10+ years ago calibrating that stuff.

I would be very, very interested, I am sure your work can be super useful. I am still working on these ecu's and recently have been working on the VR6 maf conversion (you can see it in the helpers and how to's subforum). I know it has it's limitations but still haven't found them myself, and the power figures you talk about are even above my expectations/needs. I have complemented this ecu with a wideband and boost sensor logged with arduino, and narrowband output to keep the ecu happy and functional.

I will also update my guide as there has been quite a bit of development since then. My car is running up to 167-169g/s on the stock turbo very steadily, with a good power delivery, and with reliability in mind. I would love to keep improving my work and I belive your contribution will be very helpful.

Thank you for turning up in this topic and offering to help.

Best regards.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6034


« Reply #20 on: November 11, 2024, 05:05:47 PM »

I did a car with a GT28RS over 10 years ago on this ECU. It made 350hp on the dyno.
I won't dump the file for free... but probably fairly low priced.
So don't really thank me for anything besides the info.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #21 on: November 11, 2024, 05:17:23 PM »

I did a car with a GT28RS over 10 years ago on this ECU. It made 350hp on the dyno.
I won't dump the file for free... but probably fairly low priced.
So don't really thank me for anything besides the info.

Knowledge is power, I understand your point. PM me with a price so I know what you are considering. Maybe I won't go for it right now but surely the time will come in the following months.

I appreciate you offering to provide your work.

Best regards
Logged
doktor
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 36


« Reply #22 on: November 13, 2024, 04:59:51 AM »

I have been reading a bit on the functioning of the m3.8 system and something is still not clear.

KFTLWS is starting point (?) for fuel injection based on TPS position. I found that "Fuelling calculated by (KFTLWS x KFLFLAV) x KFLF". The values resulting from the calculation are lower than those practically logged. How does boost come into play here? KFLDS is desired boost, based on target fuel (as this ecu does not have MAP). How does KFLDS interfere with KFTLWS? Or is KFTLWS a "starting point" for injection, while the turbo spools up and then targets (is regulated to) the values in KFLDS?

My point is that, for a simple Stage 1 tune, is there any issue with raising values only in KFLDS and corresponding load cap in LDSMXN (and possibly maximum MAF in KFMLDMX, but there seems to be a considerable margin)? Of course all this considering that 100% injector duty cycle is not reached. For medium rpm this should not be an issue and nice torque gains might be possible...

Thanks
Logged
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #23 on: November 13, 2024, 05:44:56 AM »

I have been reading a bit on the functioning of the m3.8 system and something is still not clear.

KFTLWS is starting point (?) for fuel injection based on TPS position. I found that "Fuelling calculated by (KFTLWS x KFLFLAV) x KFLF". The values resulting from the calculation are lower than those practically logged. How does boost come into play here? KFLDS is desired boost, based on target fuel (as this ecu does not have MAP). How does KFLDS interfere with KFTLWS? Or is KFTLWS a "starting point" for injection, while the turbo spools up and then targets (is regulated to) the values in KFLDS?

My point is that, for a simple Stage 1 tune, is there any issue with raising values only in KFLDS and corresponding load cap in LDSMXN (and possibly maximum MAF in KFMLDMX, but there seems to be a considerable margin)? Of course all this considering that 100% injector duty cycle is not reached. For medium rpm this should not be an issue and nice torque gains might be possible...

Thanks

See in the excel file guide, KFTLWS is a base map for prediction and used when maf is defective. Can't confirm how much is used in standard driving but i haven't touched them myself for stages 1 or 1+ kind of tunes.


Key point is to massage KFLDS, KFZW, KFLDTV and other maps like limiters and others in the list in the excel (I made a specific list of maps for stage 1), to acheive the goals you want. Most torque and midrage rpm driveability come from ignition maps.

Understand and forget from now on to not talk about boost with this ecu. It does have absolutely no notion of boost, only load, load request, and cycles n75 accordingly to obtain the needed air reading to reach the desired load. There is an "eureka" moment with this ecu when the load stuff makes sense in your brain haha.

Also there is a ton of people, not to say almost everybody I've known, that throws the keyboard to the wall to make a stage 1. I've seen tunes from professional shops with values as high as 11,70 on KFLDS that only made 1 bar of boost. I myself have acheived 1,1bar of boost with only 9,60 of load in KFLDS, so learn to optimise the values too. The study you made of converting from 150 to 180hp is a very good path.

Best regards
Logged
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #24 on: November 13, 2024, 05:46:14 AM »

I did a car with a GT28RS over 10 years ago on this ECU. It made 350hp on the dyno.
I won't dump the file for free... but probably fairly low priced.
So don't really thank me for anything besides the info.

Any updates on this information? I am very interested in having a look at it.

Best regards.
Logged
doktor
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 36


« Reply #25 on: November 13, 2024, 07:42:57 AM »

Marantz, thanks a lot for the discussion.

See in the excel file guide, KFTLWS is a base map for prediction and used when maf is defective. Can't confirm how much is used in standard driving but i haven't touched them myself for stages 1 or 1+ kind of tunes.
"overspeed" in this thread wrote that "KFTLWS is not "only used when MAF is defective", it´s the predective load value". Not sure, how it would interfere with KFLDS then...

Key point is to massage KFLDS, KFZW, KFLDTV and other maps like limiters and others in the list in the excel (I made a specific list of maps for stage 1), to acheive the goals you want. Most torque and midrage rpm driveability come from ignition maps.
Sure timing can make quite a difference, but looking at the maps of the AGU and AJL, the timing looks somewhat similar globally. There are areas with slightly more advance in AJL, but also in AGU. I do not see a substantial difference. Also I do not trust the axes data, sometimes I see a weird anomally in them (like as skipped value), so I am not keen for interpolating the timing maps - as these are "high risk".

I was comparing the maps for about an hour or two, but it is not a simple "bigger numbers in AJL" thing. It seems they used a somewhat different approach, some maps in certain areas are considerably lower in AJL, while others are higher, they might still work together to produce a similar result - like KFLF with KFTLWS. This is why I started to dig one level deeper, to understand which things are only cosmetic corrections (which might be the case of KFLF and KFTLWS so these might not need any alterations), and which are the real thing. Also, there are quite large differences in KFLDTV, both positive and negative, this might even look they are for different turbos (but they both should be k03), weird. As I understand it, this map might not need a lot of tuning for stage 1 as there is feedback n75 duty regulation anyway, but could produce a larger turbo lag due to lower-than-optimal initial n75 duty.


Understand and forget from now on to not talk about boost with this ecu. It does have absolutely no notion of boost, only load, load request, and cycles n75 accordingly to obtain the needed air reading to reach the desired load. There is an "eureka" moment with this ecu when the load stuff makes sense in your brain haha.
I know, thats why I wrote "desired boost, based on target fuel", but I understand thats a quite unsuitable formulation.

So, for a not quite optimal but safe first tune, altering only KFLDS (with LDSMXN and possibly other applicable limiting maps) should work okay? Timing and other maps are usually factory-calculated up to 10ms "load", which is still sufficient for a stage 1.

Thanks again.
Logged
overspeed
Sr. Member
****

Karma: +21/-5
Offline Offline

Posts: 387



« Reply #26 on: November 13, 2024, 05:04:01 PM »



KFTLWS is part of "BGTLW: A 41. 20  Berechnungsgröße tLw - Lastsignal" wich is the load expected for each TPS position wich is your EXPECTED LOAD


With MAF, RPM, KHFM etc you´ll get  ACTUAL LOAD

There are a bunch of filters


KFLDS is you DESIRED LOAD, based again in TPS x RPM, 


KFLDTV is the N75% output to make ACTUAL LOAD = DESIRED LOAD,  If  ACTUAL LOAD < EXPECTED LOAD  you are in a underboost condition and  special KFTVLDRE is used to cap N75 output, and DTC will be set






Logged
doktor
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 36


« Reply #27 on: November 14, 2024, 01:06:51 AM »

Thanks a lot. Makes sense.
Logged
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #28 on: November 14, 2024, 11:01:41 AM »


KFTLWS is part of "BGTLW: A 41. 20  Berechnungsgröße tLw - Lastsignal" wich is the load expected for each TPS position wich is your EXPECTED LOAD


With MAF, RPM, KHFM etc you´ll get  ACTUAL LOAD

There are a bunch of filters


KFLDS is you DESIRED LOAD, based again in TPS x RPM, 


KFLDTV is the N75% output to make ACTUAL LOAD = DESIRED LOAD,  If  ACTUAL LOAD < EXPECTED LOAD  you are in a underboost condition and  special KFTVLDRE is used to cap N75 output, and DTC will be set


Thanks mate, your explanation is brilliant, I will include it in the excel file. Smiley
Logged
marantzvieta
Full Member
***

Karma: +2/-1
Offline Offline

Posts: 70


« Reply #29 on: November 14, 2024, 11:13:07 AM »

Marantz, thanks a lot for the discussion.
"overspeed" in this thread wrote that "KFTLWS is not "only used when MAF is defective", it´s the predective load value". Not sure, how it would interfere with KFLDS then...
Sure timing can make quite a difference, but looking at the maps of the AGU and AJL, the timing looks somewhat similar globally. There are areas with slightly more advance in AJL, but also in AGU. I do not see a substantial difference. Also I do not trust the axes data, sometimes I see a weird anomally in them (like as skipped value), so I am not keen for interpolating the timing maps - as these are "high risk".

I was comparing the maps for about an hour or two, but it is not a simple "bigger numbers in AJL" thing. It seems they used a somewhat different approach, some maps in certain areas are considerably lower in AJL, while others are higher, they might still work together to produce a similar result - like KFLF with KFTLWS. This is why I started to dig one level deeper, to understand which things are only cosmetic corrections (which might be the case of KFLF and KFTLWS so these might not need any alterations), and which are the real thing. Also, there are quite large differences in KFLDTV, both positive and negative, this might even look they are for different turbos (but they both should be k03), weird. As I understand it, this map might not need a lot of tuning for stage 1 as there is feedback n75 duty regulation anyway, but could produce a larger turbo lag due to lower-than-optimal initial n75 duty.

I know, thats why I wrote "desired boost, based on target fuel", but I understand thats a quite unsuitable formulation.

So, for a not quite optimal but safe first tune, altering only KFLDS (with LDSMXN and possibly other applicable limiting maps) should work okay? Timing and other maps are usually factory-calculated up to 10ms "load", which is still sufficient for a stage 1.

Thanks again.

Actually, timing makes most of the power change in this case: yes 150 to 180hp is a noticeable change, but 210nm to 235 isn't. The change is basically in air flow, but in Stage 1 style of tunes, these cars can go easily to 290 to 300nm while still being safe. And this is done mostly with timing. Be sure these 1.8t's have room to work with. I you want to touch KFZW I recommend to search and look for tunes all over the internet (they are) which have been run, and develop your own ignition map (most changes are made on the higher load rows). Make small changes and log for ignition retardation, you'll see. Remember to make changes with common sense and in little increments, and then log, log and log to check your work.

Please everybody, if I am mistaken in something or think different, let us know. This is how I did it and got great results on the road, butt dyno, and logs, but I'm sure there is more experience out there than mine.

Best regards
« Last Edit: November 14, 2024, 11:20:07 AM by marantzvieta » Logged
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

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