Pages: [1]
Author Topic: 1.8T ME7.5 with 29F400BT flash (Ex: 06A 906 032 AF)  (Read 11285 times)
Ionut
Full Member
***

Karma: +4/-3
Offline Offline

Posts: 89


« on: May 02, 2013, 08:02:02 AM »

Hello,

I`ve opened this topic to be a guide/reference for those who have this ECU fitted on their cars.
Topics that I would like to cover in this topic are (not only me, anyone who have info can post it here):
1. Axis / factors.
2. Map types (8bit, 16bit LoHi, 16bit HiLo).
3. Map order (if it`s there an standard order like KRKTE after FKKVS).
4. Fueling maps.
5. Turbo maps.
6. Ignition maps.
7. Limiters.
8. Checksum regions (how much they are, how to calculate on modified file without any external tool).
9. What maps should be edited for a basic tune (without changing any engine component).

1. Axis / factors:
Any two dimensional map (actually 3D) ia represented by X, Y and Z dimensions.
X and Y are the Axis and Z is value at a specified X & Y value.
Some maps has axis just before map start, and looks like: 0006 0012 0011 0012 .... 0016 0001 0002 .... 0012
First is X axis, second is Y axis, then first 6 bits are X axis values without factor applyed, after this, we have 12 bits that represents Y axis values.
Each kind of axis (rpm, load, etc) has a predefined factor.
Ex:
   Lambda: 0.007813
   Rpm: 40.00000 (sometimes they have other values, like 0.75000 and 0.250000 as limiter)
   Boost limiter: 0.001563
   % Pedal: 0.001526
   Load: 0.023438
Generally, factor 40 on rpm is applyed when rpm is the Y axis.


2. Map types:
8 bit (1 byte) maps are maps that each byte represents 1 value. That number is from 0 to 255 (256 values), but it can be also -128 to 128.
16 bit maps (2 bytes) are 2 types of this kind of map:
Let`s say we have this 8 bit data:
89 AB CD EF
16 bits HiLo will be
AB89 EFCD
while 16 bits LoHi will be
89AB CDEF
16 bits maps are easy to recognize when searching from maps in 8 bit mode because most of them consit in a chain of low value high value
Decimal example:
12 250 18 143 52 99 120 255


3. To be...

4. Here`s a list of main fueling maps:
Code:
LAMFA - Lambda driver request
DLAMOB - Lambda with overboost
DLAMTANS - air temperature-dependent enrichment
KFLAFWL - Offset lambda target engine
KFLAMKR - weighting factor for enrichment with ignition retard
KFLAMKRL - enrichment at ignition retard
LAMFAS - barrier driver's Lambda
GANGFAW - transition threshold for disabling drivers in the amount desired
DLAMFAW - threshold driver command via activation of enrichment
KFLF - Lambda at part load map
KFLBTS - lambda components for protection
KFFDLBTS - Delta lambda factor for component protection
KFDLBTS - lambda for component protection
DLBTS - lambda for component protection
FBSTABGM - component protection factor dependent model. Exhaust gas temperature
FBSTMOT - offset component protection function of motor temperature
TABGBTS - exhaust gas temperature threshold - Component protection
DTBTS - temperature hysteresis protection for components
TKATBTS - Kat-temperature threshold for component protection
TIKATBTS - threshold temperature in the catalytic converter components for protection
TVLBTS - delay time protection components lambda
ZLBTS - time constant lambda - component protection
ZDLBTS - time constant delta lambda - component protection
TVUB - voltage correction
KRKTE - rk translation relative fuel mass in effective injection time
CWLAMFAW- Codeword LAMFAW
FKKVS - correction factor fuel supply system
KVB - constant for consumption display
FKVA - constant conversion factor for consumption display
Maybe they`re more.

5. Turbo maps:
Code:
KFMIOP - optimum engine torque map 
KFMIRL - map for calculating target charge
FRLMNHO - height correction factor RLmin about
KFLDRQ1 - LDR controller parameters Q1 (Integratorbeiwert)
LDRQ0S - controller parameters Q0 LDR PID controller in stationary mode
LDRQ1ST - Q1 PID controller parameters in stationary mode (integration factor)
KFLDRQ2 - map LDR controller parameters Q2
KFLDRQ0 - control parameters LDR Q0
LDRQ0DY - LDR controller parameters Q0
LDRQ1DY - Q1 PID controller parameters in dynamic mode (integration factor)
KFLDIAPL - adaptation correction value integral component
KFRBGOF - offset for I component limiting LDRPID
KFLDIMX - map LDR I, controller limitation
KFLDIWL - I LDR correction limit during warmup
LDIATA - I-limit correction LDR Rgler PID as a function of Tan
KFLDIOPU - correction of the TV values ??by height influence
NLDIAPU - speed threshold limit for adaptation I
LDDIMXN - safety distance LDR I, controller limitation
LDDIMNN - safety distance LDR I, controller limitation negative
TLDIAPN - debounce for tracking I-positive adaptation
KFLDRL - KF for linearizing boost = f (TV)
NDLDRAPU - speed threshold for LDRA error path error path LDO and healing
KFVPDKLD - Max permissible pressure ratio DK for diagnosis LDRA
LDRXNZK - maximum charge of LDR in continuous knocking
LDRXN - maximum charge of LDR
RLKRLDA - RI threshold for slow LDR intervention (adaptation)
TLKRLDAB - slow time constant for lowering LDR
TLKRLDAU - time constant for slow LDR control
TSKRLDAB - time constant for fast LDR reduction
TSKRLDAU - time constant for fast LDR control
KFFSLDE - LDR factor for rapid intervention (reduction)
KFFLLDE - factor for slow loading pressure engagement on rlmax by KR
KFFWLLDE - weighting factor for slow loading pressure engagement on rlmax by KR
KFFLDEO - factor to boost engagement on overboost value by KR
KFTARXB - underlying map maximum charge of Tans correction factor
KFTARXZK - map maximum charge of Tan's correction factor for continuous knocking
KFTARX - map Maximum level Tans correction factor
KFLDHBN - LDR altitude limitation (maximum compressor pressure ratio)
LDPBN - LDR p-limiting case of excessive engine temperature
LDORXN - maximum charge of LDR at E_ldo (overcharge error)
UMDYLDR - dynamic switching threshold LDR
CWLDIMX - code word for application processes KFLDIMX / KFLDIOPU
KFWPLGTA - map for weighting factor base boost pressure as f (tans)
KFLDDIMNN - safety distance LDR I, controller limitation negative
KFMI_UM - map of optimal engine torque monitoring function
LDRAPP - fixed value for LDR application without coordination Md
KFLDRAPP - map for LDR application without coordination Md
KFTVLDRE - map Tastverhältnisersatzwert for LDR
LDRPBU - P controller parameter LDR back up regulator
TVLDMN - lower duty cycle limitation for LDR
TVLDMX - the upper duty cycle limitation for LDR


In my opinion, a good tuning for a stock car can be done in few steps after reading current maps:
1. Calculate how much fuel can be inserted into cylinder at high revs.
2. Calculate air that is needed to completelly burn that fuel with best torque/power
3. Calculate if current turbocharger can actually give enaugh boost at high rev to have a fair AFR.
Those was "before".
4. Increase turbo boost (KFMIOP, KFMIRL, LDRXN, LDRXNZK, KFLDRL).
4.1 increase only first 3 maps until knocking appear (you can see that on VCDS for example, when advance is retarding).
5. Increase fueling (drivers wish) until knock dissapears at all revs and increase a little bit more then repeat step 4 few times until you get turbo pressure calculated at point #3.
5.1 If at specified boost you cannot provide enaugh fueling to mantain lambda, decrease boost a little bit.
6. Increase spark advance if needed (not so sure wich is the best way, but maybe increasing until knock and then retarding in 2 degrees steps should be just fine).

If you want to run lean at some points and rich to others, edit KFLF, LAMFA, LAMFAS before step 4.
If you encounter issues with fueling, try to optimise FKKVS map.



P.S. I`m a beginner in this branch and for me is just a passion, maybe a lot of my knowledge is wrong, but as is a discussion forums, anyone can contribute.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #1 on: May 02, 2013, 09:47:04 AM »

I am gonna get slagged off for this, but...

PLEASE put down the ECU and open a book about forced induction engines.
You have no idea what you are doing and why.
Logged

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

Karma: +4/-3
Offline Offline

Posts: 89


« Reply #2 on: May 02, 2013, 01:31:02 PM »

If you know more than me (and maybe you know), you should contribute to this thread an correct informations.

I hope your next post in this thread will be a constructive one, not like one above.


P.S. In 2005 someone told me on a Romanian forum that i should go in Spain to collect Raspberries because programming is not for me. Now, after 8 years i`m project manager for a company and normal employee for another.
I`ve read a lot about how fueling is calculated, how limiters acts, but all those informations are hard to understand for beginners.
Much simpler is to tell something like "There are your fueling maps. By increasing/decreasing values here you`ll change X parameter of engine".
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #3 on: May 02, 2013, 02:21:54 PM »

Honestly, the best thing is to get a bit of background anyway. Blindly following advice isn't going to get you anywhere...
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
catbed
Sr. Member
****

Karma: +8/-2
Offline Offline

Posts: 300


« Reply #4 on: May 02, 2013, 02:50:27 PM »

Isn't pretty much all of this info in the s4wiki Tuning section?
Logged
Ionut
Full Member
***

Karma: +4/-3
Offline Offline

Posts: 89


« Reply #5 on: May 02, 2013, 10:17:33 PM »

@nyet, yes, i agree. But if a beginner reads out the documentation of ME7 will be like  Huh
reading documentation is a must, i know, but some peoples learn quicker if they have examples.

@catbed, i think there is, because is about same type of ecus, even it was write by me, no copy/paste (map names was translated with google translate, as i don`t know german).

@nyet, could you advise on point 3? Someone on ecuconn... write everytime that KRKTE for example, is everytime in the right place, but never told what`s that right place Smiley

Thank you,
Ionut.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #6 on: May 10, 2013, 03:08:25 PM »

You don't need to read the documentation for ME7 ECU just yet, it will be a waste of time.

Get this and read it:
http://www.amazon.com/Induction-Performance-Practical-Supercharging-Turbocharging/dp/1859606911
Then get this:
http://www.amazon.com/Engine-Management-Advanced-Greg-Banish/dp/1932494421

You are never going to understand the ECU when you don't understand the FI engine.
When you start with a sport, you don't jump into the olympics right away, you go slow. Same like with car engines, first it is a good idea to get mechanical background and understand how the bits and pieces work. Only then do you have a chance at understanding how the ECU works.

You don't need to do any of those "calculations" you say - it's not a math game or programming. You need to log every parameter of the engine and give it what it needs, to give it what it needs you have to understand how to look at and interpret said data, and you can not do that unless you know how it works.
Logged

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

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #7 on: May 10, 2013, 03:43:47 PM »

I've put everything I consider critical reading here

http://amzn.com/w/45QQW7709BZO

Hope this helps anybody who is interested ...
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
jimmcgee5
Full Member
***

Karma: +7/-7
Offline Offline

Posts: 201


« Reply #8 on: May 11, 2013, 10:29:45 AM »

 Cheesy do you have any PDF links for any of them  Grin
Logged
Aurélien
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 60


« Reply #9 on: May 11, 2013, 12:41:19 PM »

I am gonna get slagged off for this, but...

PLEASE put down the ECU and open a book about forced induction engines.
You have no idea what you are doing and why.

I couldn't agree more.

What the hell is that idea of calculating how much fuel you can put in cylinder then how much air then boost then ........ Seriously.

An engine is an air pump.

Your turbocharger, is creating pressure in your intake manifold thus increasing you're Volumetric Efficiency. But at the same time it creates backpressure thus increase exhaust gas partial pressure and so reducing VE in a certain proportion.

You set up your boost, cam phasing, whatever affect air path, to maximise VE ( or another parameter if you need / know what you try to reach ) .

Then you just fucking setup ignition timing to get a proper 50% mixture burn arround 8 - 12 ° ATDC without knock, later if knock.

And get a proper A/F to get nice flamme speed, nice economy or low egt.

And that's pretty much everything about why the hell should I do 101.
Logged
Pages: [1]
  Print  
 
Jump to:  

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