Difference between revisions of "The Famous Custom VS Generic Debate"

From PrecisionCodeWorks
Jump to navigation Jump to search
 
Line 3: Line 3:
 
'''Fact - In chip tuning there is no such thing or ever was..'''
 
'''Fact - In chip tuning there is no such thing or ever was..'''
  
*For any formally qualified automotive/calibration engineer the custom remap debate is amusing to say the least for a number of reasons;
+
For any formally qualified automotive/calibration engineer the custom remap debate is amusing to say the least for a number of reasons;
  
 
Firstly – After 2004 most engine management systems became a closed looped torque based model simply put, the engine management is adapting (optimizing) the tune of the engine in almost real time based on the hard code or what is known as the statistical dynamics element of the memory.
 
Firstly – After 2004 most engine management systems became a closed looped torque based model simply put, the engine management is adapting (optimizing) the tune of the engine in almost real time based on the hard code or what is known as the statistical dynamics element of the memory.
Line 11: Line 11:
 
'''"Even under these circumstances, only a small modification is required to a base calculation within the ECU to correct the internal equation."
 
'''"Even under these circumstances, only a small modification is required to a base calculation within the ECU to correct the internal equation."
  
*Think of an ECU in its simplest form, it's a calculator programmed to receive values in terms of voltages and frequencies at a rate of 1 to 200 HZ or in layman's terms 1 to 200 times a second dependent on the type of value it needs to sample.
+
Think of an ECU in its simplest form, it's a calculator programmed to receive values in terms of voltages and frequencies at a rate of 1 to 200 HZ or in layman's terms 1 to 200 times a second dependent on the type of value it needs to sample.
 
For example - sensor values such as coolant temperature, are a slow changing value, so a sample of 1-5 HZ is fine. Where fast changing variable's such as manifold pressure, it requires a faster sample rate of say 50 HZ or 50 times a second.
 
For example - sensor values such as coolant temperature, are a slow changing value, so a sample of 1-5 HZ is fine. Where fast changing variable's such as manifold pressure, it requires a faster sample rate of say 50 HZ or 50 times a second.
 
The processor then first of all references (for the sake of this explanation) three memory models within the ECU, one known as 'statistical elements' and the others as we know them as 'maps' and 'curves'
 
The processor then first of all references (for the sake of this explanation) three memory models within the ECU, one known as 'statistical elements' and the others as we know them as 'maps' and 'curves'
Line 19: Line 19:
 
[[File:Ideal_gas.png ]]
 
[[File:Ideal_gas.png ]]
  
*This is the core structure of the ECU function - It can be made up by a number of control algorithms such as 'Motronic' and elemental rules such as ideal gas law, this also includes configuration switches and curve/map address library for the controller to switch between based on the strategy or mode required.
+
This is the core structure of the ECU function - It can be made up by a number of control algorithms such as 'Motronic' and elemental rules such as ideal gas law, this also includes configuration switches and curve/map address library for the controller to switch between based on the strategy or mode required.
  
 
====Curve====
 
====Curve====
Line 25: Line 25:
 
[[File:MAF-EXP.png|250px ]]
 
[[File:MAF-EXP.png|250px ]]
  
*The curve structures in the ECU are a vital and are often mistaken as torque limiters by 'CUSTOM MAPPERS' or re-scaled in a effort to bypass a mechanical limit resulting in a loss of resolution and refinement.
+
The curve structures in the ECU are a vital and are often mistaken as torque limiters by 'CUSTOM MAPPERS' or re-scaled in a effort to bypass a mechanical limit resulting in a loss of resolution and refinement.
 
An ECU can only interpret what a engine is doing by its input signals via the relevant sensors.
 
An ECU can only interpret what a engine is doing by its input signals via the relevant sensors.
 
This is usually done by voltage or frequency - so the 'curve' is the real world signal conversion to a digital value the ECU can use in a calculation to out put to its PWM's
 
This is usually done by voltage or frequency - so the 'curve' is the real world signal conversion to a digital value the ECU can use in a calculation to out put to its PWM's
Line 34: Line 34:
  
  
*Basically a data matrix, a table of data values arbitrated to a output of the ecu drivers or PWM's referencing values such as requested torque, boost, lambda and air flow.
+
Basically a data matrix, a table of data values arbitrated to a output of the ecu drivers or PWM's referencing values such as requested torque, boost, lambda and air flow.
 
These are desired targets based on the data and control logic influenced by the 'curve' and 'statistical elements'.
 
These are desired targets based on the data and control logic influenced by the 'curve' and 'statistical elements'.
 
ALL employing PID control - understanding this will expose the ignorance of most chip tuners.
 
ALL employing PID control - understanding this will expose the ignorance of most chip tuners.
  
 
[[Advanced ECU Engineering Principles]]
 
[[Advanced ECU Engineering Principles]]

Latest revision as of 12:55, 4 December 2015

Custom Tuning Files

Fact - In chip tuning there is no such thing or ever was..

For any formally qualified automotive/calibration engineer the custom remap debate is amusing to say the least for a number of reasons;

Firstly – After 2004 most engine management systems became a closed looped torque based model simply put, the engine management is adapting (optimizing) the tune of the engine in almost real time based on the hard code or what is known as the statistical dynamics element of the memory. A quality remapping engineer understands and respects this and simply enters the correct desired targets in the correct places to the code and the system references the sensors accordant (closed loop or PID) thus using these settings to achieve the desired result. The one and only time a 'custom' strategy is required is when a vehicle is modified to a point where the dynamics employed by the factory ECU are no longer valid for example - a larger turbo is fitted requiring new PID loops to be employed.

"Even under these circumstances, only a small modification is required to a base calculation within the ECU to correct the internal equation."

Think of an ECU in its simplest form, it's a calculator programmed to receive values in terms of voltages and frequencies at a rate of 1 to 200 HZ or in layman's terms 1 to 200 times a second dependent on the type of value it needs to sample. For example - sensor values such as coolant temperature, are a slow changing value, so a sample of 1-5 HZ is fine. Where fast changing variable's such as manifold pressure, it requires a faster sample rate of say 50 HZ or 50 times a second. The processor then first of all references (for the sake of this explanation) three memory models within the ECU, one known as 'statistical elements' and the others as we know them as 'maps' and 'curves'

Statistical elements

Ideal gas.png

This is the core structure of the ECU function - It can be made up by a number of control algorithms such as 'Motronic' and elemental rules such as ideal gas law, this also includes configuration switches and curve/map address library for the controller to switch between based on the strategy or mode required.

Curve

MAF-EXP.png

The curve structures in the ECU are a vital and are often mistaken as torque limiters by 'CUSTOM MAPPERS' or re-scaled in a effort to bypass a mechanical limit resulting in a loss of resolution and refinement. An ECU can only interpret what a engine is doing by its input signals via the relevant sensors. This is usually done by voltage or frequency - so the 'curve' is the real world signal conversion to a digital value the ECU can use in a calculation to out put to its PWM's

Map

Injector-1.jpg


Basically a data matrix, a table of data values arbitrated to a output of the ecu drivers or PWM's referencing values such as requested torque, boost, lambda and air flow. These are desired targets based on the data and control logic influenced by the 'curve' and 'statistical elements'. ALL employing PID control - understanding this will expose the ignorance of most chip tuners.

Advanced ECU Engineering Principles