| Support Center Items |
 Troubleshooting v3 Interfaces |
If you can not communicate with your v3 interface please use the Interface User Guides listed in the User Guides and Installation Manuals section of the Woolich Racing website.You will need to login with your WR Account to view these guides.
If you require further assistance with your v3 interface please find the links to for your specific interface below.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| I have a Firmware Update Error for a USB v3 or a Log Box v3 |
The Woolich Racing Tuned software (WRT) runs on a computer which communicates with the ECU using an electronic interface. There are two types of Woolich Racing communication interfaces currently available for sale, a USB v3 interface and a Log Box v3 interface. This article applies to all of the USB v3 and Log Box D v3 interfaces. These devices have a software program (firmware) on them which allows them to talk to the WRT software and the ECU. When the communication is connected to the computer and the WRT software is started, the software will check the firmware on the interface to make sure it is the latest version. Sometimes a firmware update can fail due to internet connectivity, a damaged USB cable or other reason. If you find yourself in this situation please do not panic as the Woolich Racing technical support team have seen these problems before. Please open a support ticket so that we can provide you with further information to get you up and running again.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| I have a COM Port Error - How to Rollback USB Drivers |
The Woolich Racing Tuned software runs on a computer which communicates with the ECU using an electronic interface. There are two types of Woolich Racing communication interfaces currently available for sale, a USB v3 interface and a Log Box v3 interface. This article applies to all of the USB v3 interfaces as well as the Log Box D v3. These connect to the computer (or laptop) using a USB cable, the computer then detects these device as a COM Port which enables the WRT software to use serial communication to talk to the interface. Sometimes after a Windows update the devices are no longer detected correctly by the computer or the Woolich Racing Tuned software. If you find yourself in this situation please do not panic as the Woolich Racing technical support team have seen these problems before. Please open a support ticket so that we can provide you with further information to get you up and running again.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing "Failed to read address 0x...." Errors |
Most of the time ECU flashing works without a problem but there is always the small chance that something could go wrong. ECUs from different manufacturers all have their unique characteristics as well as potential problems too.
The Woolich Racing Tuned software is used to read/write information to/from an ECU and uses different communication protocols based on the specific ECU. Sometimes there are problems with the communication and an error like "Failed to read address 0x..." is shown in the software. This error typically indicates some basic communication issue which is sometimes seen on Keihin ECUs and is typically caused by a problem with the harness, power supply or computer.
These error messages could be something like this: - Failed to read address 0x0
- Failed to read address 0x599F8
- Failed to read address 0x7C740
- Failed to read address 0x3FFD8
- etc
The "Failed to read address 0x..." error means that the Woolich Racing Tuned software has attempted to read some information from a specific memory location of the ECU. The memory location (eg. 0x0, 0x599F8 etc) is a hexidecimal number that refers to the address where the information is be stored in the ECU.
Regardless of the actual address in the error message, these "Failed to read address 0x..." messages indicate that there is probably a fundamental problem with communication rather than an issue with the software, bin file, etc. The causes tend to be related to the harness pinout or installation which accounts for more than 90% of the cases that we support. There are a few other possibilities which are detailed here, this is a pretty easy checklist to run through so please take a few a minutes to review this information before creating a Support Ticket.
1. Harness issues - Check that you are using the correct harness for the specific ECU
- Verify that all of your wires are fully inserted into their connectors by gently pulling on them and checking whether they move or not. If they are able to move from the connector housing then they are a likely cause of the problem. You will need to unlock and locking tabs on the connector, re-insert the pin, and then lock the locking tab on the connector again.
- Look at the front of the connectors to ensure the wires/pins are fully inserted, are not bent and that they look like other OEM pins/connectors if applicable.
- This should be checked for ALL of the wires connecting to the ECU (bike or bench harness) as well as the wires going to your communication interface (Log Box or USB).
- Perform a wire continuity check using a multimeter on all the wires and verify that you have continuity end to end on each individual wire.
- Verify pinout and compare your installation with the photos in the installation guide, you can also send us photos so that we can verify the installation is correct and the harness itself is correctly assembled.
2. PC-related issues - Shut down your PC, let it sit for a few minutes and then restart it. It's important to do a full shutdown, sit for some time and then restart as opposed to a simple restart via the software. This approach clears all contents of RAM which may include configuration or temporary data that may be conflicting with the Woolich Racing Tuned software.
- It is also worth trying the following:
- Try a different USB cable
- Try a different USB cable in a different PC
- Try a different PC altogether
3. Interface-related issues: 4. Power Supply Issues - If bike flashing, turn the key on and kill switch on but do not start the bike. Measure the voltage directly at the battery and confirm you have 12.9 VDC or more. If 12.8VDC or less - put on a tender and let it charge for a while then retry later with the tender still on.
- If bench flashing, check your power supply with no load attached and ensure you have 13-14 VDC. Please check your power supply (if able to be completed safely) and verify your current is between 1-2A.
If you have checked the points listed above and are still experiencing "Failed to read address 0x...." errors please open a new Support Ticket
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing "The ECU VIN could not be read" |
Most of the time ECU flashing works without a problem but there is always the small chance that something could go wrong. ECUs from different manufacturers all have their unique characteristics as well as potential problems too.
This article is about issues encountered when writing to ECUs where the VIN is used by the Woolich Racing Tuned software to identify the specific ECU and associated bin file key. The term 'VIN' stands for Vehicle Identification Number which is a unique manufacturer for every vehicle worldwide. Some newer ECUs have a VIN written into them which allows us to recognise the vehicle as well as the specific ECU. Upon writing to these ECUs for the first time with the WRT software, the VIN is first read out and associated with the bin file key for that specific ECU. This has the advantage that the bin file key cannot be lost as it can always be recovered by simply reading the VIN from the ECU.
If the VIN cannot be read from these ECUs for some reason then the WRT software cannot identify the bin file key and will have issues when trying to write to these ECUs. In such cases you might see an error message like this:
If you encouter an error like this the first step is to try and read the VIN from your ECU to check that it can be read successfully. This can be done in the Woolich Racing Tuned software for supported models using Tools > Read VIN or Tools > Read Part Number and Serial Number.
The results are then shown as in the examples below:
These issues have been experienced for some ECUs from different manufacturers and the resolution depends on the specific bike details.
If this error occurs on BMW models (eg. S1000R, S1000RR, S1000XR) it is usually possible to restore the EEPROM (the place where the VIN is stored), in this case please see this support article:
If your VIN-related error is for a different bike please raise a Support Ticket: Open a new Ticket
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing "Failed to unlock protocol" |
Most of the time ECU flashing works without a problem but there is always the
small chance that something could go wrong. ECUs from different
manufacturers all have their unique characteristics as well as potential
problems too. The
Woolich Racing Tuned software is used to read/write information from an ECU and
uses different communication protocols based on the specific ECU.
Sometimes there are problems with the communication and an error like
"Failed to unlock protocol" is shown in the software. This
error can occur on ECUs from different manufacturers.
If you see this error when working on a Harley Davidson ECU, please see this article: Diagnosing Harley Davidson "Failed to unlock protocol" If
you see this error on a bike/ECU which is not a Harley Davidson, please Open a new Support
Ticket so that we can assist you further.
These Support Center articles may also be of
interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing "Failed to Initialize..." Errors |
Most of the time ECU flashing works without a problem but there is always the small chance that something could go wrong. ECUs from different manufacturers all have their unique characteristics as well as potential problems too.
The Woolich Racing Tuned software is used to read/write information to/from an ECU and uses different communication protocols based on the specific ECU. Sometimes there are problems with the communication and an error like "Failed to initialise..." is shown in the software.
The ECU is a kind of computer that on a bike controls all the functions of the engine while the bike is running, in this mode the ECU is reading signals from the bike sensors and sending commands in real time to tell the bike's hardware what to do next. In order to read or write to the ECU it is necessary to stop this normal mode of operation and get the ECU ready to send/receive data to/from the WRT software.
This means that the ECU must stop trying to communicate with the bike and get ready to communicate with the WRT software. The first step in this process is known as initialisation and although it is different for various ECUs, the common factor is that we need to tell the ECU to stop what it is doing so that we can control it directly. If this is not successful then we may see an error like 'Failed to initialise...' and this may or may not contain further information about the error. This error will typically occur before any reading or writing has happened and there can be a number of causes.
This article is about issues encountered when attempting to communicate with an ECU (eg. read or write) however the operation does not complete successfully. In most of these cases the WRT software will provide further information about the error, this article provides information and tips on how to resolve these sorts of issues.
These error messages can come in a number of different forms, please see below for suggested resolutions: - Failed to Initialize Communications with ECU - No Initial Response.
- This means that the ECU is not answering requests from WRT which could be due to it not being turned on (ie. power issue), connected correctly (ie. harness issue), or maybe the wrong bike model is selected to the ECU doesn't understand the commands that we are sending.
- In this case please confirm the following:
- You are using the correct Woolich Racing harness for the bike and it is installed according to our Installation Instructions
- The USB Device is connected and installed correctly
- The Mode Switch on the v3 device is in the right-hand side position (Green LED on)
- The Ignition is switched on
- The Bike is in neutral
- The Kill Switch is in the Run position
- Failed to Initialize Communications with ECU. Read ECU is only available after the ECU has been written using Woolich Racing Tuned software.
- This error indicates that the ECU is unable to be read out and must first be written to using the WRT software. Only after writing to the ECU for the first time with the WRT software is it possible to read the bin file out.
- This issue has nothing to do with power, harness connections etc and is a well known issue which is common for many eg. Denso ECUs where reading the ECU is not natively supported
- It is also possible that the ECU may have been previously written to and locked by another software package. This effectively prevents the WRT software from being able to communicate with the ECU.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing Harley Davidson "Failed to unlock protocol" |
Most of the time ECU flashing works without a problem but there is always the small chance that something could go wrong. ECUs from different manufacturers all have their unique characteristics as well as potential problems too.
The Woolich Racing Tuned software is used to read/write information from an ECU and uses different communication protocols based on the specific ECU. Sometimes there are problems with the communication and an error like "Failed to unlock protocol" is shown in the software.
This error can occur on ECUs from different manufacturers however this article specifically applies to Harley Davidson ECUs. If you see this error when working on a Harley Davidson ECU this error could indicate that the ECU has been locked by another software. In this case please try to read the ECU Part Number and Read the VIN to check whether basic communication is still working.
If you are able to read the Harley Davidson ECU part number, serial number and VIN the please try and read the ECU:
If you are unable to read the Harley Davidson ECU and you see an error message like 'Failed to unlock ECU Protocol' then please Open a Support Ticket so that we can assist you further.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| How to Update the Firmware on your v3 Interface (USB or Log Box) |
Woolich racing Interfaces are used by the Woolich Racing Tuned software (WRT) to read and write to ECUs. The firmware of these interfaces is updated periodically as new capabilities are added, bugs fixed and support added for new motorcycles and ECUs. It is then important to ensure that your Interface always has the latest firmware version installed, this is covered in detail in this article.
The firmware can be updated either automatically or manually using the WRT software as described below: - Automatic firmware update
- Updating Firmware on Woolich Racing v3 Interfaces - Video Tutorial
- Connect the USB v3 or Log Box v3 to the computer using the USB cable provided
- Start the Woolich Racing Tuned software on the computer
- The WRT software will automatically check for the latest firmware version for your specific Interface. If you do not have the latest version then you will receive a prompt like shown below asking whether you would like to update to the latest version.
- Click on 'Yes' and follow the on-screen prompts to update the firmware
- Manual firmware update
- Disconnect the USB cable and any harnesses from the v3 Interface
- Move the switch to the left-hand side
- Start the Woolich Racing Tuned software on the computer
- Connect the Interface to the computer with the USB cable provided
- The firmware update should start automatically and you will see the screen shown below:
- Once the update has finished you will be returned to the main window of the Woolich Racing Tuned software.
- If you want to check the current firmware version of the interface select Tools > Device Configuration from the menu. This will show the firmware version of your device as well as the latest firmware version as shown below.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| What is the difference between the USB Interface and the Log Box Interface? |
The Woolich Racing Tuned software which runs on a computer communicates with the ECU using an electronic interface. There are two types of Woolich Racing interfaces currently available for sale; a USB v3 interface, and a Log Box v3 interface.
USB v3 interface
Log Box v3 interface
A USB interface allows you to read and write to an ECU, access diagnostics (for bin files which have it available) and view some live engine data. The USB interfaces are not compatible with some of the newer models. Please check the products page for a model to determine which interfaces are supported. A Log Box interface can do everything that a USB can, and also allow you to record engine data while running the bike and log AFR (Air-fuel ratio) data when used together with the Zeitronix ZT-3/ZT-4 wideband sensor kit (model dependent). These additional features on the Log Box also allow you to use our Woolich Racing AutoTune feature in the WRT software. The letter on the interface denotes what ECU type it is capable of flashing. - B: Bosch ECU's
- D: Denso ECU's
- D-CAN: Denso ECU's using CAN Bus protocols
- K: Keihin ECU's
- M: Mitsubishi ECU's
- M-Duc: Mitsubishi-Ducati ECU's
- H: Harley Davidson ECU's (only for approved tuning shops)
Note: Engine Data is not available for all models.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Do you support non Woolich Racing Interfaces or Harnesses? |
We only offer support to customers who have purchased the Interface, Harness and Bin File Definitions from Woolich Racing, a tuning shop who uses our products, or one of our official distributors or re-sellers.
We are not able to offer support to products purchased from other vendors or do-it-yourself interfaces and harnesses. If your ECU has been flashed using another product, you may be able to overwrite the flashing using a Woolich Racing kit. Please open a Support Ticket if you are unsure if this is possible on your motorcycle.
Please note, using our Interfaces with non Woolich Racing Harnesses, or tampering with our Interfaces or Harnesses will void your Warranty.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Log Box v3 LED Lights Information |
When the Log Box v3/USB v3 is connected to the PC with the USB Cable. The Green LED stays solid when idle and connected to the PC. The Red LED indicates ECU Read/Write is happening..
When the Log Box v3/USB v3 is connected to the PC with the USB Cable and you are viewing Live Engine Data. The Green and Orange LED's indicate engine data is being requested, and received. The Red LED indicates that Engine Data is being sent to the PC.
When the Log Box v3 is connected to the bike only. The Log Box v3 will start data logging. (depending on the Device Configuration: Log Start Configuration settings) The Green and Orange LED's indicate engine data is being requested, and received. The Red LED indicates data is being saved to the SD Card. The USB v3 will do nothing.
Log Box/USB faults. If all 3 LED's are flashing together at the same time, this means the device is in Firmware Mode. Either the switch is in the Left position, or the software has put it into Firmware Mode. (The software can put the device in firmware mode automatically when it sees a new update is available for it, normally no user interaction is required for the auto-updates)
There is normally no reason to move the switch unless you are performing a manual firmware update/reinstallation.
If all 3 LED's are flashing in sequence, one after the other, this means the device can not detect the SD Card. The SD Card must be fitted, for normal use of the device. Try formatting the Card (format as FAT32/default settings)
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Updating Firmware on Woolich Racing v3 Interfaces - Video Tutorial |
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| How to Fix a Firmware Update Error on v3 Interfaces |
Woolich Racing uses communication interfaces like Log Box or USB to allow the Woolich Racing Tuned software to communicate with the ECU. The interface firmware is sometimes updated to support new models, or correct issues so it is important to update the Interface firmware version from time to time.
The v3 interfaces are recognized by Windows as 2 different devices depending on what position the device switch is placed.
The switch should be moved to the left position to update the Firmware only, otherwise the switch should be in the right position for all other operations including ECU communications, Reading, Writing, Engine Data, Diagnostics, etc.
If you have started a firmware update/reinstallation, and the software gives an error after starting the update, such as one of the following: - "This operation could not be completed"
- "COM Port could not be opened"
- "Cannot access a disposed object"
- "Object reference not set to an instance of an object."
This usually means there is a USB issue. Please first try reformatting the micro SD card or replacing the micro SD card. If that does not work then please try resetting the USB Drivers using these steps below:
- Open Windows Device Manger (right click Windows Start button)
- Click View > Devices by Container (Important!)
 - With the LogBox unplugged, put the switch in the right-hand side position, and connect it to your PC using the supplied USB cable.
- The interface (Log Box or USB) should appear in a Container called Woolich Racing or similar, as shown below:
 - Wait for it to appear in the list, and click the small dropdown arrow next to it.
- Starting at the bottom of that list, right click on each entry, and select Uninstall Device, (tick remove driver software if available in the next window)
 - Repeat this process to remove all drivers for the Woolich device until it completely disappears from the list.
- Unplug the interface from the USB cable, and move the switch to the left-hand side, and connect it back to your PC
- Wait for it to appear in the list again, and click the small dropdown arrow next to it.
- Starting at the bottom of that list, right click each entry, and select Uninstall Device, (tick remove driver software if available in the next window).
- Remove all drivers for the Woolich device until it disappears from the list.
- Unplug the interface from the USB cable and plug it back in, wait 20 seconds, and unplug it, and move the switch back to the Right, and reconnect, wait 20 seconds (for drivers to load)
- Once complete, start WRT again, and connect the interface with the switch in the right-hand side position.
You should then be able to complete any firmware updates, or connect to the ECU correctly.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Resetting Device Firmware on v3 Interfaces |
If there is a problem with the Device Firmware Update or you need to reset the Device Firmware, follow the procedure detailed below. This procedure is for v3 Interfaces ONLY (ie. Log Box v3 or USB v3) and forces the device into 'Bootloader Mode' allowing Firmware Installation. Please ensure that you have a strong and stable internet connection during the update process.
1. Unplug the Device from the USB cable. 2. Put the Interface into Bootloader mode by moving the mode switch to the Left Hand Side Position.  3. Plug the USB cable back into the Interface and computer. 4. When the Device is in Bootloader mode all LED's will flash. NOTE: For some devices with software will then automatically update the firmware and show the following screen: 
5. Open the "Tools" > "Device Configuration" screen in the WRT software.
6. You will be prompted that it is not the latest firmware. It will always display this as the Device is now in Bootloader mode. 7. Click Update Firmware and follow the on screen prompts. 8. You will be prompted to set the Device into Bootloader mode. Follow the on screen prompts by simply removing the USB cable and ensure the switch is on the Left Hand Side Position, connect the USB cable, wait for the Device to be recognised in Windows, then click Continue.
9. You will be prompted to Reset the Device. Follow the on screen prompts by simply removing the USB cable and move the switch to the Right Hand Side Position, connect the USB cable, wait for the Device to be recognised in Windows, then click Continue.
10. Once completed check the Device for correct operation.
Note: If you still have issue's updating the firmware on v3 Log Boxes remove and reinsert the Micro SD Card and start the process again. You may need to reformat the Micro SD Card (as FAT32) in an external card reader if it is not visible in windows explorer. A faulty Micro SD may cause the firmware not to update, or the Log Box may appear non-responsive.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| How to replace the Log Box v3 battery |
Log Box batteries can deplete after a few years and the timestamps in the data log will show a date and time of 12:00AM on the 1st of January, 2000. This video guides you through how to replace the battery in the Log Box.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Testing the Denso USB D / Log Box D v3 Interfaces |
Woolich Racing provides hardware and software solutions for writing tune files to the ECU, thereby modifying the vehicle performance. This all relies on our Woolich Racing Tuned software being able to communicate with the ECU via a Woolich Racing communication interface like the Log Box or USB. If there are problems with communication it is important to be able to quickly test the interface and its basic functions. This guide explains how to test the USB D v3 and Log Box D v3 interfaces for Denso ECUs.
***Please note that in the steps described in the video for testing Pin 1 and Pin 4 voltages you are asked to select any bin file that uses the specific interface (Log Box D v3 or USB D v3). We have found however that not all bin files will give the same result when testing the Pin 1 and Pin 4 voltages.
Please select a bin file for a 2008-2020 GSX1300R Hayabusa for these tests, these will provide reliable results for these interfaces for the Pin 1/Pin 4 voltage tests.
On the "Tools" menu in the Woolich Racing Tuned software there is an item for "Test Interface", this allows the basic interface communications to be tested as described below. Note: The following only applies to the USB D v3 and Log Box D v3 interfaces for Denso ECUs as shown below.
To Test Flashing Mode 1. Ensure the interface is NOT plugged into an ECU. 2. Put a jumper wire from pin 3 to pin 7 on the interface. 
The plug pin out above is the 8-pin Molex socket on the interface. 
3. Connect the USB cable from the interface to the computer. 4. Move the mode switch on the interface to the right hand side position to the Read / Write mode. Note: The v3 interface may not show the red LED until 'Test Interface' has been started. 5. Open the Woolich Racing Tuned software, go to "Tools" and then click on "Test Interface". 
Voltage Tests on Denso v3 interfaces ONLY Use a multimeter in a DC voltage setting to perform the following tests. 1. Connect the USB cable from the Interface to the computer. 2. Move the mode switch on the interface to the right hand side position to the Read / Write mode. 3. Open the Woolich Racing Tuned software . 4. Select and open a Bin file that uses a Denso Interface (eg. . 5. Click Read or Write ECU and measure the voltage between pin 4 and pin 8 on the interface, this should be 4.5-5V when in flashing mode (Red LED on) 6. Click Read or Write ECU and Measure the voltage between pin 1 and pin 8 on the interface, this should be 4.5-5V when in flashing mode (Red LED on).
The plug pin out above is the 8-pin Molex socket on the interface.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Testing the Log Box D-CAN v3 Interface |
Woolich Racing provides hardware and software solutions for writing tune files to the ECU, thereby modifying the vehicle performance. This all relies on our Woolich Racing Tuned software being able to communicate with the ECU via a Woolich Racing communication interface like the Log Box or USB. If there are problems with communication it is important to be able to quickly test the interface and its basic functions.
This guide explains how to test the Log Box D-CAN v3 interface. On the "Tools" menu in the Woolich Racing Tuned software there is an item for "Test Interface", this allows the basic interface communications to be tested as described below. Note: The following guide only applies to the Log Box D-CAN v3 interface. 
To Test Flashing Mode 1. Ensure the interface is NOT plugged into an ECU. 2. Put a jumper wire from pin 3 to pin 7 on the interface.
The plug pin out above is the 8-pin Molex socket on the interface. 
3. Connect the USB cable from the Interface to the computer. 4. Move the mode switch on the interface to the right hand side position to the Read/Write mode. Note: The v3 interface may not show the red LED until 'Test Interface' has been started. 5. Turn on the power supply. 6. Open the Woolich Racing Tuned software, go to "Tools" and then click on "Test Interface".
Voltage Tests on Log Box D-CAN v3 interface ONLY Use a multimeter in a DC voltage setting to perform the following tests. 1. Connect the USB cable from the Interface to the computer. 2. Move the mode switch on the interface to the right hand side position to the Read / Write mode. 3. Open the Woolich Racing Tuned software. 4. Select and open a Bin file that uses the Log Box D-CAN v3 interface. 5. Click Read or Write ECU and measure the voltage between pin 4 and pin 8 on the interface, this should be 4.5-5V when in flashing mode (Red LED on) 6. Click Read or Write ECU and Measure the voltage between pin 1 and pin 8 on the interface, this should be 4.5-5V when in flashing mode (Red LED on).
The plug pin out above is the 8-pin Molex plug on the interface.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Testing the Keihin USB K v3 and Log Box K v3 Interfaces |
Woolich Racing provides hardware and software solutions for writing tune files to the ECU, thereby modifying the vehicle performance. This all relies on our Woolich Racing Tuned software being able to communicate with the ECU via a Woolich Racing communication interface like the Log Box or USB. If there are problems with communication it is important to be able to quickly test the interface and its basic functions.
This guide explains how to test the USB K v3 and Log Box K v3 interfaces for Keihin ECUs. On the "Tools" menu in the Woolich Racing Tuned software there is an item for "Test Interface", this allows the basic interface communications to be tested as described below. Note: The following only applies to the USB K v3 and Log Box K v3 interfaces for Keihin ECUs as shown below. 
To Test Flashing Mode 1. Ensure the interface is NOT plugged into an ECU. 2. Ensure you have the interface powered with 12V DC connected to pin 5 and Ground connected to pin 8 of the Molex connector. If you have a bench harness to suit the Keihin interface you can connect the 8-pin Molex connector and power supply. 
If you only have a power supply you can connect to the interface as below.
The plug pin out above is the 8-pin Molex plug on the Interface. 
3. Connect the USB cable from the interface to the computer. 4. Move the mode switch on the interface to the right hand side position to the Read / Write mode. Note: The v3 interface may not show the red LED until 'Test Interface' has been started. 5. Turn on the Power Supply. 6. Open the Woolich Racing Tuned software, go to "Tools" and then click on "Test Interface".
Voltage Tests on Keihin v3 Interfaces ONLY Use a multimeter in a DC voltage setting to perform the following tests. 1. Connect the USB cable from the Interface to the computer. 2. Move the mode switch on the interface to the right hand side position to the Read / Write mode. 3. Connect the interface with a 12V DC power supply either by the bike ignition with an on bike harnesses or with the 12V DC power supply using a bench harnesses connected to the 8-pin Molex connector. Ensure the interface is NOT plugged into an ECU.
4. Turn on Power Supply. 5. Open the Woolich Racing Tuned software. 6. Select and open a Bin file that uses a Keihin Interface (eg. USB K v3 or Log Box K v3). 7. Click Read or Write ECU and measure the voltage between pin 3 and pin 8 on the interface, this should be 11.5V-13.5V when in flashing mode (Red LED on).
The plug pin out above is the 8-pin Molex plug on the Interface
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Testing the Mitsubishi USB M v3 and Log Box M v3 Interfaces |
Woolich Racing provides hardware and software solutions for writing tune files to the ECU, thereby modifying the vehicle performance. This all relies on our Woolich Racing Tuned software being able to communicate with the ECU via a Woolich Racing communication interface like the Log Box or USB. If there are problems with communication it is important to be able to quickly test the interface and its basic functions. This guide explains how to test the USB M v3 and Log Box M v3 interfaces for Mitsubishi ECUs.
On the "Tools" menu in the Woolich Racing Tuned software there is an item for "Test Interface", this allows the basic interface communications to be tested as described below. Note: The following only applies to the USB M v3 and Log Box M v3 interfaces for Mitsubishi ECUs as shown below. 
To Test Flashing Mode 1. Ensure the interface is NOT plugged into an ECU. 2. Ensure you have powered the interface with 12V DC connected to pin 5 and Ground connected to pin 8 of the Molex connector. If you have a bench harness to suit the Mitsubishi interface you can connect the 8-pin Molex connector and power supply as shown below. 
If you only have a power supply you can connect to the interface as shown below.
The plug pin out above is the 8-pin Molex socket on the interface. 
3. Connect the USB cable from the interface to the computer. 4. Move the mode switch on the interface to the right hand side position to the Read/Write mode. Note: The v3 interface may not show the red LED until 'Test Interface' has been started. 5. Turn on the power supply. 6. Open the Woolich Racing Tuned software, go to "Tools" and then click on "Test Interface".
Voltage Tests on Mitsubishi v3 interfaces ONLY Use a multimeter in a DC voltage setting to perform the following tests. 1. Connect the USB cable from the Interface to the computer. 2. Move the mode switch on the interface to the right hand side position to the Read/Write mode. 3. Connect the interface with a 12V DC power supply either using the bike ignition with an on bike harnesses or with the 12V DC power supply using a bench harness connected to the 8-pin Molex connector. Ensure the interface is NOT plugged into an ECU.
4. Turn on the power supply. 5. Open the Woolich Racing Tuned software. 6. Select and open a bin file that uses a Mitsubishi interface (eg. USB M v3 or Log Box M v3). 7. Click Read or Write ECU and measure the voltage between pin 3 and pin 8 on the interface, this should be 11.5V-13.5V when in flashing mode (Red LED on).
8. Click Read or Write ECU and measure the voltage between pin 4 and pin 8 on the interface, this should be 14.0V - 16.0V when in flashing mode (Red LED on).
The plug pin out above is the 8-pin Molex socket on the interface.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Testing the USB M-Duc v3 and Log Box M-Duc v3 Interfaces |
Woolich Racing provides hardware and software solutions for writing tune files to the ECU, thereby modifying the vehicle performance. This all relies on our Woolich Racing Tuned software being able to communicate with the ECU via a Woolich Racing communication interface like the Log Box or USB. If there are problems with communication it is important to be able to quickly test the interface and its basic functions. This guide explains how to test the USB M-Duc v3 and Log Box M-Duc v3 interfaces for Ducati Mitsubishi ECUs.
On the "Tools" menu in the Woolich Racing Tuned software there is an item for "Test Interface", this allows the basic interface communications to be tested as described below. Note: The following only applies to the USB M-Duc v3 and Log Box M-Duc v3 interfaces for Ducati Mitsubishi ECUs as shown below.
To Test Flashing Mode 1. Ensure the interface is NOT plugged into an ECU. 2. Ensure you have the interface powered with 12V DC connected to pin 5 and Ground connected to pin 8 of the Molex connector. If you have a bench harness to suit the Mitsubishi interface you can connect the 8-pin Molex connector and power supply. 
If you only have a power supply you can connect to the interface as below. 
3. Connect the USB cable from the interface to the computer. 4. Move the mode switch on the interface to the right hand side position to the Read / Write mode. Note: The v3 interface may not show the red LED until 'Test Interface' has been started. 5. Turn on the Power Supply. 6. Open the Woolich Racing Tuned software, go to "Tools" and then click on "Test Interface".
Voltage Tests on M-Duc v3 interfaces ONLY Use a multimeter in a DC voltage setting to perform the following tests. 1. Connect the USB cable from the Interface to the computer. 2. Move the mode switch on the interface to the right hand side position to the Read / Write mode. 3. Connect the Interface with a 12V DC power supply either by the bike ignition with an on bike harnesses or with the 12V DC power supply using a bench harness connected to the 8-pin Molex connector. Ensure the interface is NOT plugged into an ECU.
4. Turn on the power supply.
5. Open the Woolich Racing Tuned software. 6. Select and open a Bin file that uses a M-Duc v3 Interface. 7. Click Read or Write ECU and measure the voltage between pin 3 and pin 8 on the interface, this should be 11.5V-13.5V when in flashing mode (Red LED on).
7. Click Read or Write ECU and measure the voltage between pin 4 and pin 8 on the interface, this should be 14.0V - 16.0V when in flashing mode (Red LED on).
The plug pin out above is the 8-pin Molex socket on the interface.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Format Micro SD card - v3 Log Box |
If you are having difficulty with viewing and updating your Log Box, saving or viewing WRL log files it may be due to a problem with the Micro SD card, and formatting the Micro SD card may correct the problem.
If you are able to see the Log Box in Windows File Explorer as a USB drive (as shown below), you should be able to format directly while the Micro SD card in inserted into the Log Box.
If you are unable see the Log Box in Windows File Explorer you will need to use an external card reader to format the Micro SD card. In this case you will need to remove the micro SD card and format it using a USB card reader and your desktop computer. - Remove the Micro SD card from the Log Box v3
- Insert the Micro SD card into an external card reader connected to your PC
- The Micro SD card should appear in Windows as an external hard disk (see image above)
Regardless of whether you are formatting the card in the Log Box or an external card reader, the steps are the same as follows:
- Right click on the micro SD drive in windows and choose 'Format'
- Under 'File system' select FAT32
- Leave all other default settings unchanged
- Click Format
- Once formatting has completed you can remove the Micro SD card from your PC or card reader, and re-install it into the Log Box.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Unable to format micro SD card in Log Box or Log Box Pro? |
The Woolich Racing Log Box interfaces use a Micro SD memory card to save data during logging of engine data, etc. The log files written to the Micro SD card should be accessible to you using Windows File Explorer, if the Micro SD card is not visible in Windows it may be necessary to reformat the SD card.
If the Micro SD card in the Log Box is not visible in Windows Device Manager, Windows File Explorer, etc then it will not be possible to format the Micro SD card while it is inserted into the Log Box, in this case you will need an external Micro SD card reader to format the Micro SD card as follows: - Remove the Micro SD card from the Log Box/Log Box Pro
- Place Micro SD card into the external card reader connected to your PC
- The Micro SD card should appear in Windows as an external hard drive
- Right click on the Micro SD card in Windows and choose Format
- Select FAT32 under 'File System', and accept the other the default settings
- Click Format.
- Once formatting has completed you can remove the Micro SD card from your PC, and re-install it into the Log Box.
- The Micro SD card should now be visible in Windows File Explorer as an external drive and you should be able to view any log files saved on the card.
Was this helpful? YesNo
open in new page |
| My Interface says it's registered to another user |
Woolich Racing communication interfaces are used to allow the software running on the PC to 'talk' to the ECU. All communication interfaces (eg. USB, Log Box) are registered to only be used by the account that initially purchased them. If you try to use an interface that belongs to another account, or you have purchased a second hand interface, you will get an error saying "This device is registered to another user". You will not be able to use it until the device has been transferred to your own account, thereby making you the 'owner'.
To transfer the device, we must have permission from the current registered owner.
If you are in contact with the previous owner, please ask them to Open a Support Ticket, to let us know they have sold the hardware to you.
If you are not in contact with the previous owner or don't know who they are, we will need to contact them to seek permission to complete the transfer. We may ask you to connect the device to your PC, so we can find the owner.
We do not approve any transfer where we do not have permission from the registered owner.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing "Failed to Sync Baud Rate" |
The Woolich Racing Tuned software is used to read/write information from an ECU and uses different communication protocols based on the specific ECU. Sometimes there are problems with the communication and an error like "Failed to Sync Baud Rate" is shown in the software. The error "Failed to Sync Baud Rate" is typically caused by harness issue either with the pinout or installation, this accounts for about 90% of the cases that we support. There are a few other possibilities which are detailed here, this is a pretty easy checklist to run through so please take a few a minutes to review this information before creating a Support Ticket.
1) Harness issues
- Verify that all of your wires are fully inserted into their connectors by gently pulling on them and checking whether they move or not. If they are able to move from the connector housing then they are a likely cause of the problem. You will need to unlock and locking tabs on the connector, re-insert the pin, and then lock the locking tab on the connector again. - Look at the front of the connectors to ensure the wires/pins are fully inserted, are not bent and that they look like other OEM pins/connectors if applicable - This should be checked for ALL of the wires connecting to the ECU (bike or bench harness) as well as the wires going to your communication interface (Log Box or USB). - Perform a wire continuity check using a multimeter on all the wires and verify that you have continuity end to end on each individual colored wire. - Verify pinout and compare your installation with the photos in the installation guide, you can also send us photos so that we can verify the installation is correct and the harness itself is correctly assembled.
2) PC related issues
- Shut down your PC, let it sit for a few minutes and then restart it. It's important to do a full shutdown, sit for some time and then restart as opposed to a simple restart via the software. This approach clears all contents of RAM which may include configuration or temporary data that may be conflicting with the Woolich Racing Tuned software..
It is also worth trying the following:
- Try a different USB cable - Try a different USB cable in a different PC - Try a different PC altogether
3) Interface related issues:
4) Power Supply Issues - If bike flashing, turn the key on and kill switch on but do not start the bike. Measure the voltage directly at the battery and confirm you have 12.9 VDC or more. If 12.8VDC or less - put on a tender and let it charge for a while then retry later with the tender still on. - If bench flashing, check your power supply with no load attached and ensure you have 12-14 VDC. Please check your power supply (if able to be completed safely) and verify your current is between 1-2A.
If you get to this point and none of those have helped, then it is very possible this ECU has been reflashed elsewhere and locked by that software that last flashed it.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Diagnosing "Write ECU" and Harness Installation Errors |
If you are experiencing issues with reading or writing to your ECU, please watch this troubleshooting video and refer to the detailed information below.
The most common reasons the write process is interrupted are: - Harness Connection/Installation issue:
- Check the Installation Guide and double check each step of the install.
- Check you have fitted any extension harness correctly to the ECU plug.
- Check all the wires are firmly locked into the ECU plug, and are not loose.
- Check your diagnostic plug is clean, and making good contact (if used)
- Low or Loss of Power to the ECU:
- Battery power should be 12.8v or more.
- Run/Stop switch must be in the RUN position.
- Check for a loose connection between the Interface and the ECU
- Do not move the interface/harness during flashing (aka loose connection)
- Connect a battery charger at the same time, (So the battery does not drain while flashing)
- Check you are switching the Ignition key on/off at the right time. (follow software prompts)
- Computer interrupted the write process:
- PC should be checked that all updates are installed, and has been restarted.
- Check the PC is not busy doing background tasks
- Check your PC is powerful enough to keep up with the ECU write speed (Minimum Dual Core 2.4Ghz, 4 Gig Ram. Recommended i5 with 8 Gig Ram)
- Check your USB port is not worn out (try another USB port)
- Use the supplied USB cable. Do not use a long cable.
- Check your PC Battery is fully charged if using a Laptop.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Engine Data logging settings |
The Woolich Racing Log Box products allow data to be written (logged) to an micro-SD card while the bike is being run on the street, track or dyno. The Log Box will typically start logging data whenever the ignition is started AND the device is NOT connected to the computer.
The exact settings about how the data logging works can be modified by the user in the Woolich Racing Tuned software on the computer. These settings can be viewed by connecting the Log Box to your PC and setting your Log Start Configuration which can be found under Tools > Device Configuration Page as shown below.
The Log Start Configuration is shown as in the screenshot below:
The Default "Log Start Configuration" settings are:
Time Delay (secs) = 0 - The number of seconds to delay before starting to log data after the device is powered on. This setting is useful if you would like to delay data logging to prevent log files from being created when starting the bike for short amounts of time.
Engine Running = not ticked - When this option is checked the engine must be running before data will be logged. This setting is useful to prevent logging data when the key is turned on but the engine is not running.
RPM = 0 - The RPM that the engine must go above before data logging will begin. This setting is useful to delay the start of data logging until the engine has been taken above the selected RPM.
Log data to micro-SD in Engine data Mode = not ticked. - This setting creates data logs on the Interface when in normal operation mode. It is useful if you are using the Interface on the dyno to monitor engine data and you would also like to log data to be used with the Woolich Racing AutoTune.
OBD2 Engine data = not ticked - This option is required for models that use OBD2 engine data protocol. You can see it your model requires OBD2 data by checking the Engine Data Type' in the Bin File Details. If your model shows the Engine Data type: "OBD2 - CAN", then you will need to tick this option, and save to the Log Box.
|