BASICS

This toolset consists of three main components:

The emulator board: replaces the EEPROM chip in your ECU, emulates it, and enables data feedback.

The EMUBT Windows application: allows you to upload new files for emulation and configure the board.

Tuning and data logging tools: TunerPro or ALDLdroid.

EMUBT

DOWNLOAD LINK
The EMUBT Windows application lets you upload new files for emulation, select emulation banks, and configure each bank. Each part of the application includes interactive help: hover over buttons, windows, or panels to display tooltips.

EMUBT FIRMWARE UPDATE
The emulator board and Windows application are continuously improved. Firmware updates can be applied using the REFLASH button. Ensure you use a compatible version of EMUBT.exe with the firmware. The latest versions can be found in the Download section.
Important: Reflashing uses a *.hex file for firmware updates, while the UPLOAD button is for EEPROM images (*.bin files). The application prevents incorrect file usage but be cautious when using the REFLASH button. If interrupted, the emulator will not function until the correct firmware is flashed. Complete the reflashing process to see the message: "You can close Reflasher window."

TunerPro and ALDLdroid

TunerPro

DOWNLOAD LINK
TunerPro is a powerful tool for decoding, displaying, and modifying ECU programs. These programs contain maps (fuel, ignition, etc.), flags, and procedures for engine control. To decode maps in an ECU program (e.g., DigifantBinaryExample.bin), you need an XDF definition file. Note that different Digifant1 binaries may require specific XDF files.

With a binary file running on the EMUBT board and the appropriate XDF file, you can modify maps or other ECU settings.

Another key feature of TunerPro is data logging and "hit data tracing," which tracks ECU feedback in real-time or during log playback. For fuel or ignition maps, it tracks RPM and MAP readings (RPM vs. Engine Load). Watch the video below for more details.

To enable logging, you need an "Acquisition Definition File" (ADX) for the EMUBT board. Download it here.

Try It!

Follow these steps to explore data logging in TunerPro with the EMUBT board:

Install TunerPro.

Load the XDF file in TunerPro: XDF -> Select XDF.

Load the ADX file: Acquisition -> Load Definition File.

Open the BIN file: File -> Open Bin.

Load a collected LOG file: Acquisition -> Load Log File.

Click Play in the logging section and explore the available views and values.

Hit Play in logging section visible in above picture

Try playing with buttons highlighed in red to see different views and all values possible to trace

To see all values in tunerPro:
Acquisition->Edit Definition File->Values

ALDLdroid

ALDLdroid is an Android application similar to TunerPro. It allows map editing, data logging, and controlling the EMUBT board (e.g., switching emulation banks). The app is available on the Google Play Store for a one-time purchase. To enable logging, pair the EMUBT device via Bluetooth and provide the ALDLdroid ADX file.

This application is not free and is available in Google Play store and it is installed per account so you pay once and you can use it on any Android device you are logged in. To enable data logging in ALDLdroid you need to pair EMUBT bluetooth device and provide ALDLdroid adx file in ALDLdroid application.

EMUBT Emulator Board

The EMUBT board replaces the EEPROM chip in your ECU and can operate in standalone mode without a PC. It stores up to three programs for emulation, which can be switched using the EMUBT app or ALDLdroid. The board also provides data feedback, enabling you to monitor and tune your car's performance. Feedback includes sensor readings (e.g., lambda, temperature, knock) and processed ECU data, which can be analyzed using TunerPro or ALDLdroid.

Another feature of this board is data feedback, as described in the sections above on TunerPro and ALDLdroid. The Digifant1 ECU does not natively provide data feedback. However, through deep analysis of the Digifant1 ECU and its program, this feature has been enabled. The board provides readings from all analog sensors, such as the lambda sensor, intake manifold temperature, engine coolant temperature, and knock sensor readings, among others. Additionally, it is possible to retrieve processed ECU data, such as knock detection and additional ignition advance related to knock readings. This allows you to tune your car and diagnose all sensors effectively.

Using TunerPro, you can modify your ECU program and upload it to the EMUBT board to improve your car's performance. All communication with the board, including reading data and uploading new files for emulation, is done via Bluetooth.

Adding Wideband O2 Sensor Readings

It is possible to add WBO2 readings to data feedback if you have a WBO2 sensor and controller that provides an analog output. The analog output should be in the 0–5V range and preferably linear.

I am using this unit: WBO2 2Y1, which provides multiple outputs including analog linear output (click for details).
The main challenge is synchronizing WBO2 readings with current engine operating conditions (MAP vs RPM). This can be achieved by connecting the WBO2 analog output to one of the analog inputs of the Digifant 1 ECU.

From my experience, the COPOT (CO potentiometer used to adjust carbon monoxide levels) wears out over time and becomes inaccurate. With the EMUBT board, it is possible to adjust fuel mixtures directly in TunerPro using fuel maps instead.

This makes it possible to replace the inaccurate potentiometer with TunerPro and EMUBT, while also freeing up an analog input. The COPOT input is also linear.
Note that the COPOT unit integrates the Intake Air Temperature sensor, which shares a ground pin with the CO potentiometer. The idea is to disconnect the potentiometer signal wire and connect the WBO2 analog output instead.
To do this, carefully identify PIN 1 in the COPOT connector and cut that wire. It is recommended to do this in a reversible way, so the original potentiometer can be reconnected if needed. Using a pair of male and female connectors is a good approach.
It is important to ensure a common ground for the WBO2 controller, sensor, and COPOT. Ideally, the WBO2 controller should be grounded close to the ECU grounding point. Due to chassis resistance, a small offset in readings may occur, but this can be corrected in TunerPro.

If you decide to cut the wire, a modification in the Digifant code is required so that the ECU uses a fixed value instead of reading the CO potentiometer resistance.

You should do the following

• Measure the current resistance of the COPOT (measurement between pins 1 and 3)
• In EMUBT applicatation
• Select the EEPROM image you want to update
• Click the COPOT patch button
• Enter the resistance measured in the first step and click OK
• Upload the EEPROM image to the emulator

Most WBO2 controllers also provide a digital output, typically available via a dedicated application. This can be used to compare analog and digital readings and calibrate the ADX file in TunerPro accordingly.
To do this, open: Acquisition → Edit Definition in TunerPro.

If the WBO2 output is purely analog, you can adjust the final constant (e.g. value "9" in the equation shown above) to correct the reading.