TuneBoy WBO2Analyzer

Select the COM port the WBO2 unit is connected to and click Connect

The TPS range needs to be set so that the software can calculate the TPS as a percentage. Click Reset; with the ignition on but the engine off, hold the throttle at 100% for 2 or 3 seconds and release for 2 or 3 seconds. The range is stored between executions; however it should be reset everytime you connect to a different bike.

Select whether you are creating a new map or overlaying an existing map. Always create a new map when importing into TuneBoy Tune Editor and ensure you commit the trims to main tables between runs. Use the overlay option when using a Power Commander unit and select the map currently used in the PCIII. When creating a new map, click Settings to govern how the map is created.

Set the target AFR that is to be attained. If a TuneBoy map has been baselined as per above, this setting should match the value used in the map. Click Advanced for more options.
 

The live data screen shows the existing data being received from the WBO2 unit.

Each of the data displays shows the raw data being received in the bottom right and the calculated equivalent. The RPM calculation depends upon the number of spark events per revolution. This is set by clicking the up/down arrows in the upper right corner of the RPM screen. Cycle through until the RPM display matches the rev counter.

The analysis depends upon capturing data. Therefore, when you wish to start a run click Record and Stop when you have finished. If you click Record again, this simply appends to the previous recording. The logs are reset each time you run WBO2Analyzer.
 

After analysing the data, graphs are generated to show the data that has been captured. Select the TPS to display, the TPS values correspond to the grid points used in the PCIII map.

The upper graph shows the average (green) and median (blue) AFR values for each RPM grid point within the PCIII map. The horizontal line shows the target AFR.

The lower graph shows the number of readings at each grid point, with a horizontal line showing the minimum number of readings required. Readings in green are used in the corresponding map, readings in red are discarded as not enough readings are available for confidence in predicting the required trim.

Click Save to save the generated PCIII map to either import into TuneBoy Tune Editor or to use on a Power Commander.
 

The list on the left is the TPS values, on the right is the RPM values.

To enter a series, enter the start of the series in start/min, the end of the series in end/max and the required increment. For example, to create an RPM series starting at 500rpm through to 10,000rpm at 250rpm intervals; enter 500 in start, 10000 in end and 250 in increment. Click the > or < button to enter it into the required list.

To enter an individual setting, enter in manual and click the corresponding button. You may also press r or t to enter into RPM or TPS respectively.

Version is Dynojet's way of governing which model the map can be used with. Set version to equate to the value displayed in the Power Commander software for the bike model. This is not required if the map is being imported into TuneBoy Tune Editor.

When the resulting PCIII map is being imported into a TuneBoy map, ensure the TPS and RPM points match the fuel table of the TuneBoy map. This ensures the resulting import is accurate.
 

Maximum Trim: The maximum trim that will be applied by the generated PCIII map. If the required calculated trim exceeds this value, it will be capped to this value.

Sensor Lag: The AFR reading to a corresponding TPS/RPM combination occurs after the initial TPS/RPM reading to give enough time to allow the exhaust gasses to flow into the exhaust. The lag is the number of readings to wait between reading TPS/RPM and the AFR.

Moving Average Period: The analysis generates a number of moving averages, this setting governs how many readings are used in calculating these averages.

Minimum TPS Change: The minimum change in TPS, compared to its moving average, for inclusion in the analysis.

Maximum TPS Change: The maximum change in TPS, compared to its moving average, for inclusion in the analysis.

Minimum RPM Change: The minimum change in RPM, compared to its moving average, for inclusion in the analysis.

Maximum RPM Change: The maximum change in TPS, compared to its moving average, for inclusion in the analysis.
 

Grid Mapping: The tolerance used in ascertaining the grid reference a particular reading equates to. At 10%, an RPM reading of 1800-2200 is deemed to be part of the 2000rpm grid point. Where two grid points overlap, the nearest grid point is used.

Maximum TPS Difference: The maximum difference from a grid reference. This overrides the grid mapping if the maximum difference is less than the percentage difference.

Maximum RPM Difference: The maximum difference from a grid reference. As above, this overrides the grid mapping reading.

Percentile of Readings: The upper and lower extremities of readings are discarded to ensure data spikes do not affect the analysis. At 95%, the lower and upper 2.5% of readings are discarded.

Minumum Number of Readings: The minimum number of readings required at each grid point to calculate a trim.

Average/Median Difference: The maximum difference allowed between the average and median values. High differences between these calculations suggests the data is too volatile for usage.