Quote:
Originally Posted by geeteezee
Interesting and more than a bit concerning. I'll post my log info for some feedback I guess.
So, 8 revisions including the base which opens the ECU to allow logging and to my knowledge doesn't change anything else.
Rev1 - 184mb - 11 logs
Rev2 - 32mb - 3 logs
Rev3 - 265mb - 36 logs
Rev4 - 216mb - 26 logs
Rev5 - 162mb - 26 logs
Rev6 - 184mb - 29 logs
Rev7 - 121mb - 21 logs
Rev8 - 588mb - 68 logs
Rev9 - 644mb - 57 logs
This spans April 13 - Nov 14 '22.
Mods are Berk cats, Z1 intakes, Invidia Gemini C/B.
|
It doesn't matter if I tune the car on a dyno or if I tune it remotely. I ALWAYS require lots of data collected over a long period of time to track trends with the fuel system , the knock correction system, and other variables. Here's how it works:
each driving scenario results in a different engine speed & engine load. So you have tables in within the ecu and most of them are indexed as such
X: engine load
Y: engine speed
As you drive, the ecu does a lookup in various tables to control fueling, vvel, cam timing, etc etc. Here is an example of a timing map:
So as you can see there are many cells. If you are only tuning full throttle at sea level, then generally your load will stay around 100% as your rpm increases, this is a very small portion of the "tune".
There are some scenarios where you will have a very hard time reaching them on the dyno and other scenarios that are difficult to reproduce on the dyno, so real world driving is required.
In addition, and this is probably the most important part, you can't just go off of a small sample. You need to drive the car as conditions change and repeatedly log the vehicle to determine the ideal values for each cell. One day your car might pull timing, the next day it might be fine, so the best value will lie somewhere in between. It's common to see knock sensors desensitized or turned off completely to avoid having to do this extra work. Analysis of why a car pulls timing can be complicated and made more difficult by lack of tooling, especially in a remote tuning situation.
Seeing as how the values may change somewhat significantly, some smoothing of the tables will be needed and this will again require additional adjustments until there is a convergence..
This process can take a while to complete depending on the vehicle, there is no other way.
Each tune I do comes with unlimited revisions and data processing/review, until no more practical changes need to be made. You can keep collecting data for the entire duration of the tune support. The more data you collect, the more accurate the results of the tune will be. It's only in your favor to collect as much data as you can over a longer period of time to get the best results.