|
Load references
SloS14… thanks for the post.
Think of a map like a spreadsheet. If a map is airflow based, one axis references airflow (the MAF for the FT86) and the other axis references engine speed. Where the Unichip goes in the map is a combination of airflow… somewhere between 0% and 100%... and engine speed…somewhere between idle and redline. We can set both the 100% and redline as desired.
Consider, for example, a “brand x” intake set up. With that intake, you’d expect the best airflow for the engine would happen with the intake, a good set of headers, and a good exhaust. We do testing and determine where to set the 100% to ensure we’re making the correct changes at the most airflow that configuration will breath.
Now consider the car with the intake but not the headers or exhaust modifications… by definition, it shouldn’t breathe as well. As a consequence, the load input (MAF) to the Unichip won’t go all the way to the 100% row… it might only get to row 9 instead of row 10 because the airflow is only 90% as much without the headers and exhaust.
Since the corrections are partially airflow based, at that 90% value the corrections are “correct” for either configuration…the difference is without the headers and exhaust modifications, that’s all the higher in the map the engine goes. With the headers and exhaust, the engine can process more air and the Unichip can make additional adjustments. Same map, same data, but the engine gets to different places depending on what it does.
That’s a bit of a simplification, but it’s an important concept because each vehicle, each intake, each headers, etc…are all slightly different so as a result on any particular car where the map actually goes will be slightly different. The Unichip correspondingly goes to a slightly different spot in the map.
Cheers
|