Firstly, you would of chosen to run either Alpha-N (Throttle based load, i.e. if using throttle bodies) or Speed-Density fuelling (using Manifold pressure as a load reading) via the System>Engine Driver.


If you are using throttle position to detect load (only used on naturally aspirated engines, where a manifold pressure reading is not easily possible, such as throttle bodies) then your Algorithm Cfg should be set as below in the System>Engine Driver:

This will (if you have successfully calibrated your throttle sensor) make the Primary Load DRO read 0-100% as you move the throttle from closed to open.


If however your are using manifold pressure to measure load, such as on a turbocharged engine, or an engine with a large post throttle plenum, then the algorithm config should be set as follows (again, in the Engine Driver):

Now the primary load will be a direct copy of the manifold pressure reading, in kPa, so it will go from around 20 to perhaps 200 if you run 1 bar (100kPa) of boost.


As a result of these different possible ranges depending on algorithm/load reading, you will need to calibrate the left hand axis (load) axis of various tables to make the best use of the entire table's size. The tables to focus on are the Injection>Base VE Table 1, Ignition>Ignition Table (Pri 1), and the Lambda>Target AFR Table.


The following table is the Target AFR table, and you can see how the left hand column (Primary Load) is set to go from 20 to 205 - obviously intended for a manifold pressure (Speed Density) based primary load, running up to around 1 Bar of boost (200kPa absolute pressure).

 


If we were to use this on a throttle based map, (which as we said, would use 0-100 as primary load, i.e throttle percentage) then we can see that we would have no difference on target AFR below 20% of throttle, and almost half the table (rows with load reading over 100) would never be used. Hence the following would be a much better use of the tables memory - also note we have more ‘resolution’ at very small throttle openings, allowing better control of fuel at these minor changes - 90% to WOT (100%) throttle needs less refinement as the ECUs interpolation is usually accurate enough.

Tip: Change the axis numbers by double clicking them.

The RPM (top row) should be obvious, and evenly spaced from your idle speed to the maximum RPM of your engine.


It makes it easier to tune your engine if the tables axis all match across things like Ignition, Fuel, Boost etc, so as a setup process, it is a good idea to do this first.