Click image for an unscaled view

To log runtime data in an open loop area, the map or the part of the map, which is to be adjusted, will be processed at a fixed TPS. To do so, each load, that is present in the map (y axis values) will be indicated by a mark at the throttle grip. During the test ride the throttle will be positioned on each mark, starting with a low speed and the highest possible gear, and held until the speed stops increasing. Overrun conditions should be avoided as the mixture will change. With the throttle held steadily each line in the map will be run through from left (low rpm) to right (high rpm) and all runtime and lambda data for this specific load condition will be recorded. Repeat each run at least three times.
Open loop adjustments require a wideband O2 sensor, because a narrowband O2 sensor will not provide mixture data. Connect the wideband sensor(s) to the laptop and record lambda data simultaneously with ECM runtime data. Log file analysis will then calculate the average lambda maps and fill in the average lambda maps. The fuel maps are adjusted according to this average lamda values manually.

Click image for an unscaled view

Adjusting the Closed Loop area, located in the center of the fuel maps, follows a different approach. In this case the test ride should span the closed loop area as much as possible. The more cells of the map are used, the more meaningfull will be the averages calculated from the log data. Vary load and engine speed, but ride calmly and avoid hard acceleration or overrun conditions. A test ride should last at least 30 minutes (time is more significant than distance) to collect a sufficient number of data records. It takes some time to establish an EGO correction for each operating point (load-rpm combination). An easy way to cover the map is to ride at a steady speed in a high gear for 15-20 seconds, then gear down keeping the speed until rpm reach the closed loop rpm threshold (about 5000 rpm for XB engines).

All logged EGO correction data will be averaged and filled into the appropriate map, when the log file is analysed with EcmSpy. For a significant result, each cell should show more than 100 hits (number of records collected). To check a cell's hits, click the cell in the "Average Correction" map and look for the number in the cell's status bar:

Click image for an unscaled view

Cell entries with a hit value below 100 should be used with care only. The calibration and closed loop areas have to be adjusted before the open loop areas, because the AFV is calculated from EGO correction and controls the open loop mixture. A well adjusted calibration area will result in a stable AFV, which is a good foundation for open loop adjustments using a wideband O2 sensor.

Click image for an unscaled view

1.) The first and most important task is to backup and savely store the stock EEPROM data. This copy will allow you to come back to a known working setup for the bike in case something goes wrong.

2.) Check the static timing according to the service manual. Static timing will commonly not change unless the Camshaft Position Sensor has been moved. Crankshaft Position Sensors, as found in 2008 and later engines, can't be adjusted at all.

3.) Perform a TPS reset for DDFI and DDFI-2 ECM types:

• Connect EcmSpy to the ECM and push the "Execute" button to display runtime data in the "Overview" tab.
• Back off the idle adjustment screw until TPS voltage stops decreasing, then continue to back it out two more turns. Close the throttle butterfly carefully, so that it is slightly sticking in the throttle body.
• Toggle the "Execute" button, open the "Diagnostics" tab, then the "TPS Reset" tab and hit the "Reset" button.
• Go back to the "Overview"; tab and push the "Execute" button, then turn the idle adjustment screw clockwise until TPS degrees read about 5.5 degrees.
• Warm up engine (to at least 160 °C) and set idle to 1050-1150 rpm.

4.) Do a calibration ride to update the AFV. Write down the actual AFV (it must no necessarily have changed) and multiply the front and rear fuel maps by it. Clear the AFV (push the "Clear" button at the "Calibration Mode" tab), but do not block it, as it is important to know if the AFV changes later.

5.) Optional: create a new adjustment run in your "My Maps" area, describing the engine setup (airbox changes, exhaust, ...) in the comment area. Add the initial map version to this adjustment run.

Click image for an unscaled view

With the help of the decision tree, shown in the picture at the left, you can find the tuning process that fits your configuration and instrumentation. Six different processes will be shown below, each one having a different requirement, for examples, a front exhaust gas O2 sensor allows to adjust the front cylinder as well as the rear. All ECM of type DDFI-3 support to monitor and log two (narrowband) O2 sensors and the resulting EGO correction individually, once configured to do so. This reduces the number of test rides compared to using a single O2 sensor only.
If you own a wideband O2 sensor, which is supported by the EcmSpy software (currently only Innovate LC-1 and PLX's wideband sensor are recognized by EcmSpy) the lambda values could be recorded additionally. DDFI-3 ECM also provide two pins for reading the analog output from any wideband sensor, which needs to be configured to the ECM's needs (0-5 Volt = 10-20 AFR). Using an additional wideband O2 sensor in a slave boss further reduces the number of test rides required to adjust the fuel maps.
The core of each tuning process is always a test ride as described above to collect closed loop or open loop data.

Click image for an unscaled view

After installing the wideband O2 sensor into the rear headers O2 sensor's boss, a test ride A has to be done to log runtime and lambda data. After the test ride, the log file need to be analysed. The fuel maps will then concurrently adjusted according to the average lambda (Average Lambda 1) cell values. Recommended target values for lambda and detailed informations can be found in section 6.2 of the Tuning Guide Version 2.

To speed up fuel map adjustment, only the rear fuel map will be adjusted, but the front fuel map will be locked to changes of the rear by choosing "lock percentaged" from the map lock selector. This way the front map will receive the same percentual changes as applied to the rear map.

Repeat this adjustment cycle until the desired result is achieved.

Click image for an unscaled view

Collect and store runtime data by performing a test ride A. After the ride, analyse the log file. The fuel maps will then adjusted concurrently according to the average EGO correction map's (Average Correction 1) cell values. The target is to get an average EGO correction near 1.0 (= 100%) all over the closed loop area and the idle area, if desired.

To speed up fuel map adjustment, only the rear fuel map will be adjusted, but the front fuel map will be locked to changes of the rear by choosing "lock percentaged" from the map lock selector. This way the front map will receive the same percentual changes as applied to the rear map.

Repeat this adjustment cycle until the desired result is achieved.

Click image for an unscaled view

1.) Fuel map adjustments start with a test ride B to collect and store runtime data. After the ride the logfile is analysed and the fuel maps get adjusted concurrently according to the average EGO correction map's (Average Correction 2) cell values. The target is to get an average EGO correction near 1.0 (= 100%) all over the closed loop areas.

These adjustments are continued, until the desired precision is achieved.

Please make sure that AFV is stable when riding in different areas of the closed loop area before proceeding to step 2. If the AFV is still fluctuating (without changing altitude or without heavy climatic air pressure changes), repeat the first step until the problem is solved.

2.) Once closed loop is adjusted, the narrowband O2 sensor in the rear header will be replaced by the wideband O2 sensor. Additionally all EGO correction is switched off by unchecking the "Enable Closed Loop" box in the "Closed Loop" tab.

The next step requires to mark the throttle grip for all load rows above the closed loop area, usually the topmost 4 rows in the fuel maps. Then a test ride A is performed to collect and store runtime as well as wideband lambda data.

After the ride the logfile is analysed and the fuel maps get adjusted concurrently according to the average lambda map's (Average Lambda 1) cell values. Recommended target values for lambda and detailed informations can be found in section 6.2 of the Tuning Guide Version 2.

To speed up fuel map adjustment, only the rear fuel map will be adjusted, but the front fuel map will be locked to changes of the rear by choosing "lock percentaged" from the map lock selector. This way the front map will receive the same percentual changes as applied to the rear map.

Repeat this adjustment cycle until the desired results are achieved.

Click image for an unscaled view

1.) With a narrowband O2 sensor installed in the rear hader, fuel map adjustments start with a test ride B to collect and store runtime data. After the ride the logfile is analysed and the fuel map for the rear cylinder is adjusted individually according to the average EGO correction map's (Average Correction 1) cell values. The target is to get an average EGO correction near 1.0 (= 100%) all over the closed loop areas. To avoid changing the front cylinder's fuel map also, "unlocked" has to be selected from the map lock selector.

ECM of type DDFI-3 can monitor a second narrowband O2 sensor and will calculate EGO correction individually for each cylinder if the "Enable Independent Front CL" checkbox is marked on the "Closed Loop" tab and a narrowband O2 sensor is connected to the ECM at pin 31 of the grey plug. This saves a lot of time because only half the number of test rides is required now and step 2 can be skipped. The average EGO correction for the front cylinder will then be shown in the second EGO correction map (Average Correction 2).

Repeat this adjustment cycle until the desired precision is achieved.

2.) When all adjustments are done for the rear cylinder, the ECM is connected to the narrowband O2 sensor installed in the front header. To avoid unwanted side effects it is also recommended, to set all rows of the "Front Cylinder Correction" table to 100% fuel.

With a narrowband O2 sensor installed in the front hader, fuel map adjustments start with a test ride B to collect and store runtime data. After the ride the logfile is analysed and the fuel map for the front cylinder is adjusted individually according to the average EGO correction map's (Average Correction 2) cell values. The target is to get an average EGO correction near 1.0 (= 100%) all over the closed loop areas. To avoid changing the rear cylinder's fuel map also, "unlocked" has to be selected from the map lock selector.

Repeat this adjustment cycle until the desired precision is achieved.

Click image for an unscaled view

1.) The first step requires to adjust the closed loop area for both cylinders, as described in process 4. Please follow the instructions given there to individually adjust the front and rear cylinder.

Please make sure that AFV is stable when riding in different areas of the closed loop area before proceeding to step 2. If the AFV is still fluctuating (without changing altitude or without heavy climatic air pressure changes), repeat the first step until the problem is solved.

2.) After the closed loop area is adjusted, the rear narrowband O2 sensor is reconnected to the ECM and the front narrowband sensor is replaced by a wideband sensor, which is then connected to the PC or netbook. To avoid unwanted side effects it is also recommended to set all rows of the "Front Cylinder Correction" table to 100% fuel. All load values above the closed loop area, usually the topmost 4 rows in the fuel maps, must be marked at the throttle grip. EGO correction needs to be disabled by unchecking the "Enable Closed Loop" box in the "Closed Loop" tab.

The next steps depend on the availability of one or two wideband O2 sensors.

A) 1 wideband O2 sensor available:

A.1.) Perform a test ride A to collect and store runtime data from the ECM and lambda data from the wideband O2 sensor. After the ride the logfile is analysed and the fuel map for the front cylinder is adjusted individually according to the average lambda value map's (Average Lambda 1) cell values. Recommended target values for lambda and detailed informations can be found in section 6.2 of the Tuning Guide Version 2.

To avoid changing the rear cylinder's fuel map also, "unlocked" has to be selected from the map lock selector.

Repeat this adjustment cycle until the desired results are achieved.

When all adjustments are done for the front cylinder, the wideband O2 sensor is installed in the rear header. The sensor bung in the front header can be closed with a plug now as it is not needed any further.

A.2.) Again perform a test ride A as describe in step 2.1 above. Collect data, analyse the logfile and adjust the rear fuel map's open loop areas now according to the average lambda value map's (Average Lambda 1) cell values. Recommended target values for lambda and detailed informations can be found in section 6.2 of the Tuning Guide Version 2.

To avoid changing the front cylinder's fuel map also, "unlocked" has to be selected from the map lock selector.

Repeat this adjustment cycle until the desired results are achieved.

B) 2 wideband O2 sensors available:

A wideband O2 sensor will be installed in each header. If not done already, EGO correction needs to be disabled by unchecking the "Enable Closed Loop" box in the "Closed Loop" tab.

B.1.) Perform a test ride A to collect and store runtime data from the ECM and lambda data from the wideband O2 sensors. After the ride the logfile is analysed and the fuel maps for the front and the rear cylinder are adjusted individually according to the average lambda value map's cell values. If the wideband sensor was connected to the PC as described in the instructions below the sensor type selector, the front O2 sensor data is shown in the "Average Lambda 1" map, rear O2 sensor data in the "Average Lambda 2" map. Recommended target values for lambda and detailed informations can be found in section 6.2 of the Tuning Guide Version 2.

To avoid changing the other cylinder's fuel map also, "unlocked" has to be selected from the map lock selector.

Repeat this adjustment cycle until the desired results are achieved.

Click image for an unscaled view

1.) The first step requires to adjust the closed loop area for both cylinders, as described in process 4. Please follow the instructions given there to individually adjust the front and rear cylinder.

Please make sure that AFV is stable when riding in different areas of the closed loop area before proceeding to step 2. If the AFV is still fluctuating (without changing altitude or without heavy climatic air pressure changes), repeat the first step until the problem is solved.

2.) After the closed loop area is adjusted, the rear narrowband O2 sensor is reconnected to the ECM and both narrowband sensors are replaced by wideband sensors, which are then connected to the PC or netbook. To avoid unwanted side effects it is also recommended to set all rows of the "Front Cylinder Correction" table to 100% fuel. All load values above the closed loop area, usually the topmost 4 rows in the fuel maps, must be marked at the throttle grip. EGO correction needs to be disabled by unchecking the "Enable Closed Loop" box in the "Closed Loop" tab.

Perform a test ride A to collect and store runtime data from the ECM and lambda data from the wideband O2 sensor. After the ride the logfile is analysed and the fuel map for each cylinder is adjusted individually according to the average lambda value map's (Average Lambda 1 for the front, Average Lambda 2 for the rear cylinder) cell values. Recommended target values for lambda and detailed informations can be found in section 6.2 of the Tuning Guide Version 2.

To avoid changing the other cylinder's fuel map also, "unlocked" has to be selected from the map lock selector.

Repeat this adjustment cycle until the desired results are achieved.