| Support Center Items |
 How to Send a Bin File to Woolich Racing for Analysis |
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 describes how to read the bin file from your ECU and send it to the Woolich Racing technical support team so that they can resolve potential problems that you are having. This will typically be requested by the Woolich Racing team in a Support Ticket. Many technical support issues require that you read out the bin file from your ECU and send it to Woolich Racing so that it can be analysed in order to resolve problems and provide technical advice. If you have been asked to send your bin file to Woolich Racing, please follow the steps below. If you have a partial write failure and the ECU is non-responsive, the bike doesn't start or the fuel pump does not prime, you can go ahead and follow these instructions and create a ticket in advance, to save on Support time. **PLEASE ENSURE YOU READ THROUGH EACH STEP BELOW** NOTE: PLEASE DO NOT WRITE OVER THE ECU UNTIL THE STEPS BELOW HAVE BEEN COMPLETED! - Ensure that the computer running the Woolich Racing Tuned software is connected to the internet.
- Connect the harness to the ECU
- On-bike harness needs to be installed as per the User Guides
- Bench harness needs to be connected to ECU and powered using a 12V power supply
- Connect the communication interface (eg. Log Box or USB) to the ECU using the appropriate harness
- Connect the communication interface to the computer using the provided USB cable
- Turn on the 12V power to the ECU
- Switch on the ignition if using an on-bike harness
- Turn on 12V power supply if using a bench harness
- Start the Woolich Racing Tuned software and click on the 'New' button
- Select the Manufacturer (1), Model (2), Year (3) and ECU Part Number (4) for the ECU you wish to read as per the screenshot below. Click on 'New' (5) to open the bin file
Read the ECU as per normal by clicking on the 'Read ECU' button and following the prompts as shown below. If this does not work please attach a screen shot of any errors you receive in the software attempting to READ the ECU. Please position the error window so that the make/model/part number is visible on the main WRT window.
- Once read out, DO NOT SAVE THE FILE! If the file is saved then this transfer request will be invalid and this process must be repeated from Step 1 above.
You can always read the ECU again, and save the file after it has been sent.
- Click on the 'Tools' drop-down menu in the software and select, 'Send Bin File to Woolich Racing' as shown below.
Enter the reason for sending as 'Support Issue' as shown below.
Enter the Support Ticket Number if this is part of a current Support Ticket. If this was requested by the Woolich Racing team in a Support Ticket, please go into the Support Ticket and let us know that you have sent in the bin file. If this is part of a new support request, please Open a new Ticket and let us know. When we receive the support ticket reply, we will review the File and reply back to you with the outcome.
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 |
| Zero Write - How Can I fix this and get my Bin File Key back? |
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 a 'zero-write' which can occur when trying to write to an ECU for the first time with the Woolich Racing Tuned software (WRT) but it does not complete successfully. The WRT software is associated with a user account, this is the account of the user who signed in previously. If tell the WRT software to write a bin file to an ECU it will first check and see if the account has any keys (ie. license) available to perform the write action.
The 'Model Selector' window of the WRT software shows a summary of the Bin File Definition Keys for the user account currently logged in as shown below:
Example of 'zero-write' record
This summary typically shows the total number of keys available for the model selected as well as details about when a Bin File Key was allocated and the number of times that it has been written. Every time that a bin file is written to the ECU, the number of Writes normally increases by one.
If the very first write attempt with an ECU fails then the number of writes will show '0' (zero). In this situation even though the write failed, a Bin File Key was allocated. If the write was unsuccessful it is possible that the Bin File Key was not written to the ECU, which means that you have effectively lost the Bin File Key due to the 'zero write'.
If this has happened within the first hour or two of the first 'zero-write' attempt, you should still be able to try another write attempt and WRT should let you write to the ECU. However if you try to write the ECU again and the software says you do not have any keys, 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 |
| My 2015-2016 BMW S1000RR BMSX ECU has No VIN - What Can I do? |
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 2015 and 2016 BMW S1000RR models with BMSX ECUs. These issues typically occur after a failed or partial write to the ECU, as the VIN is stored on the ECU for these models. If a write operation is interrupted before the VIN is written, you might see an error message like "VIN could not be found" as the VIN has not been written to the ECU correctly. 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 |
| My Denso ECU is Unresponsive - What Can I do? |
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 a Denso ECU with the Woolich Racing Tuned software. This could occur if there was previously a problem with communication during a write operation (e.g. USB cable damaged), if Windows shut down during the write operation (e.g. restart after system update) or any number of other possible reasons.
In some cases the Denso ECU could become non-responsive, meaning that it was working fine initially but suddenly it is no longer possible to communicate with the ECU. You can check if the ECU is unresponsive by trying to perform a simple task like read the Part Number and Serial Number from the Woolich Racing Tuned software as shown below:
If you can read the Part Number and Serial Number then the communication is working well and you can ignore this article. If you do not get a response from the ECU or see multiple error messages when you try and communicate with your Denso ECU, it might have become unresponsive.
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 |
| My Honda Keihin ECU is Unresponsive - What Can I do? |
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 a Honda/Keihin ECU with the Woolich Racing Tuned software. This could occur if there was previously a problem with communication during a write operation (e.g. USB cable damaged), if Windows shut down during the write operation (e.g. restart after system update) or any number of other possible reasons.
In some cases the Honda/Keihin ECU could become non-responsive, meaning that it was working fine initially but suddenly it is no longer possible to communicate with the ECU. You can check if the ECU is unresponsive by trying to perform a simple task like read the Part Number and Serial Number from the Woolich Racing Tuned software as shown below:
If you can read the Part Number and Serial Number then the communication is working well and you can ignore this article. If you do not get a response from the ECU or see multiple error messages when you try and communicate with your Honda/Keihin ECU, it might have become unresponsive.
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 |
| My ECU has Error Code 50 - What Can I Do? |
Most of the time ECU flashing works without a problem but there is always the small chance that something could go wrong. ECUs typically have their own error-logging system internally and when the ECU detects that it has found an error, it will produce an error code (diagnostic trouble code or DTC) which is normally represented as a number. These error codes can sometimes be seen on the dash directly, or in the Diagnostics window of the Woolich Racing Tuned software. Other times the error code requires a special tool like an OBD2-reader to read the error code and find the meaning.
One such example is ECU Diagnostic Code 50 which can be translated as "Faulty ECU Memory".
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 |
| Error - You do not have any Bin File Definition Keys |
This article address the error message in the Woolich Racing Tuned software which informs you that "You do not have any Bin File Definition Keys to write to this ECU". If you have successfully written to this ECU before in the same session (i.e. you haven't closed the software and/or rebooted your computer) AND then you see this message when trying to write to the same ECU again, it is possible that you have had a failed
write which could have resulted in the bin file key not being written to the ECU
correctly. The bin file key is the license that Woolich Racing
uses to allow users to write to an ECU. The bin file key is written onto
the ECU by the Woolich Racing Tuned software so that it can be recognized to
allow read/write access in the future. If an error has occurred during writing to the ECU then
the bin file key not have been written successfully and is effectively 'lost'
at that point.
If this happens you may see a message telling you
that "You do not have any Bin File Definition Keys to write to
this ECU" as shown below:
Here are the steps that we ask you to take in order
for us to confirm that you lost a valid bin file key and hopefully replace it
for you: - Do NOT overwrite your ECU with a
new key - doing this will delete the old key forever.
- READ your ECU out and submit the
bin file to Woolich Racing for us to review the file
- Open
a ticket and inform us that you
have had a failed write, you have sent us the bin file and would like to
request a replacement key
- Send us screenshots of ALL errors or messages you see on the computer while completing the above steps
- Wait until you hear from our
support team before writing to this ECU again.
We will then review the incoming bin file and check
for your key, and return the lost key to your account so you can attempt to
flash your ECU again. If you do not wait for us to respond and simply use another key to write to the ECU again, we can not guarantee that we will replace the key.
If you have followed the steps above and provided Woolich Racing with the information required to show that your ECU
previously had a valid bin file key written to it then we will typically be able to
replace it for you. Woolich Racing does this to avoid you being out of
pocket for the cost of a new bin file key.
Here are the most common reasons for a failed write process:
- Low power or a loss of 12V power to the ECU, possibly caused by one
of the following:
- Battery power is less than 12.8v
- A loose wire connection between the Interface and the ECU
- Moving the interface/harness during flashing (also caused by a
loose connection)
- Allowing battery to drain while flashing, we recommend always
using a battery charger at the same time
- Ignition key switched off at wrong time
- Computer interrupted the write process, possibly caused by one of
the following:
- PC is installing updates
- PC is busy doing background tasks
- PC is not powerful enough to keep up with the ECU write speed
- Worn or damaged USB port
- USB cable is too long
- Battery is not charged fully
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 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 "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 |
| Diagnosing "Failed to unlock Mitsubishi Protocol" 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 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 Mitsubishi Protocol" is shown in the software.
This error is typically only seen when working with newer Mitsubishi ECUs such as 2021+ ZX-10R, ZH2, etc. If you encounter this error when working with a Mitsubishi ECU please try the following steps to resolve the issue:
- Restart your PC
- Reconnect the interface (USB or Log Box) to the computer using the provided USB cable and to the ECU using either an on-bike or bench harness
- Check that your power supply (battery or bench power supply) has a voltage of at least 13.5V. If using the battery connect a charger/tender.
- In the Woolich Racing Tuned software select Tools > Recover ECU as shown below
- Once the process has completed switch the ECU off for 10 seconds and then switch it back on again.
- Check that communication with the ECU is now possible by selecting Tools > Read Part Number and Serial Number
If you are unable to recover the Mitsubishi ECU and you still see an error message like 'Failed to unlock Mitsubishi 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 |
| Can I use a VPN with Woolich Racing? |
A VPN or Virtual Private Network is a tool which is used to encrypt your internet traffic. VPNs can be used to hide your IP-address, change your apparent location or make it appear that your are located in a different country.
We do discourage the use of VPNs when using the Woolich Racing websites and the WRT software for the following reasons:
- Orders could be shipped to the wrong country which usually incurs long delays and increased shipping costs
- New accounts cannot be automatically verified if the account address does not match your detected location
- Existing Woolich accounts may be locked if the detected geolocation does not match the physical address on your account. This can cause delays to your tuning workflow as you will not be able to access the WRT software or buy products on the Woolich Racing website until you have opened a support ticket and we have reviewed the situation.
If your account is locked outside of the Woolich Racing support hours you may experience significant delays before we can restore access.
If you are using a VPN and receive a notification that your account has been locked, please Open a new Support Ticket and let us know what has happened so that our support team can review and help resolve your issue.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Overview of the WRT Software - Video Tutorial *RECOMMENDED VIEWING* |
This video provides an overview of the Woolich Racing Tuned software which can be used to tune your bike and get the best performance out of it. It shows in simple steps how it can be used to to edit various maps and settings including Fuel maps, Ignition maps, Limiters, Race Tools and Advanced Settings among others before finally writing the new settings to your ECU.
This video is also available in other languages as shown below:
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| WRT Software - Minimum Computer Specifications |
WRT Recommended Windows Operating Systems:
Windows 10 32-bit Windows 10 64-bit Windows 11 32-bit Windows 11 64-bit
Windows 7 and Windows 8/8.1 are no longer supported by Microsoft and they do not support some security functions used by the Woolich Racing Tuned software to protect your account information.
If you are still using a Windows 7/8 PC then we recommend that you consider updating to a newer model that runs on Windows 10 or Windows 11. Using an older computer with newer ECU's can result in unexpected software errors and ECU writing faults.
WRT Recommended System Requirements (especially for newer 2019+ ECUs) - Windows 10 64 Bit
- Minimum 8 GB RAM
- Intel i5 or i7 4-Core Processor (or comparable AMD CPU), minimum 2.0 GHz
- 1 x USB 3.0 Port
- 1 GB free disk space
WRT Minimum System Requirements (for older pre-2019 ECUs)
- Minimum 4 GB RAM
- Dual/Multi Core CPU, minimum 2.0 GHz
- 200 MB free disk space
- 1024 * 768 display
- USB 2.0 Port
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Why can’t I login to the Woolich Racing Tuned software? |
If your Woolich Racing account is locked and you are unable to login to the Woolich Racing Tuned software, it may be due to one of the following reasons. - Maximum number of computers exceeded
- The Woolich Racing Tuned software may be installed and used on up to three (3) computers at the same time
- Exceeding this limit (ie. installing it on a 4th computer and trying to login), will result in your account being locked. If this happens you will need to Open a Support Ticket.
- Account closed due to inactivity
- If you have not logged into and used your account for more than 12 months, your account will automatically be locked to protect your account from misuse. In this case please Open a Support Ticket.
- No Woolich Racing products purchased/owned
- The Woolich Racing Tuned software is free of charge for customers who have purchased or own a Woolich Racing package
- You need to have purchased a Woolich Racing ECU Flashing Package to gain access to an account, and the software.
- It can take up to 48 hours for your account to be verified. If you have received your package, but your account is not yet verified, please Open a Support Ticket.
Please Open a Support Ticket if you have any further questions about your account. These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| I have made a purchase but I can't login |
After you have created a Woolich Racing account and made a purchase on our website, your account will be automatically verified assuming that the same email address is used for both the account as well as the purchases.
This is done when your Order is process and packed, your account will be checked and verified.
This means you will get access to the software, and you can watch the video guides before your Package arrives. This is also the perfect time to complete the Woolich Foundations Training Course (free) which will guide you in the basics of how to lookup ECU part numbers, check harnesses, how to find answers to common questions and general guidelines for using the Woolich Racing equipment and software.
If you have ordered over the weekend, then your order will be processed and shipped on Monday.
If your account has failed automatic verification, it is usually because some details on your Woolich Racing account, or PayPal address, or your geolocation details, do not match up, and your account will require manual verification. If this has happened, or if your account has not been verified by the time you have received your package, then please Open a Support Ticket.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Troubleshooting Checklist |
Having difficulty reading and/or writing to the ECU? Here’s our 'Troubleshooting Checklist'.
Problems related to reading and writing an ECU are generally not software related. They are generally caused by one of the following issues: - 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.
- We also have a range of interface Troubleshooting Videos if you believe that your USB or Log Box interface has a fault.
Other things to note: - If the ECU has been flashed by either a send-in service or any other flashing service before, it has more than likely been locked by that service. Please run the unlock function if available. Sometimes the ECU may have to be sent back to the original source to get returned to stock.
- Please check you are using a high speed USB 3.0 compatible USB Port on your computer.
- Your computer meets our recommended PC Specifications.
- If you are performing multiple flashes on a legacy v1 or v2 interfaces , remember to move the interface mode switch into the center position, then back to flashing mode (red led on), before attempting another write/read operation.
If you are still having issues troubleshooting and have completed all of these checks, please open a Support Ticket.
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 |
| 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 "Failed to Unlock ECU" |
Woolich Racing provides hardware and software to allow users to write tune files to their ECUs, thereby modifying the vehicle performance. This requires that we can communicate with the ECU using our Woolich Racing Tuned software. This works very well for all stock ECUs of all supported part numbers (see the Products page for details on supported part numbers) however sometimes ECUs have been modified already from the original factory settings so are no longer 'stock' ECUs. This can result in an error when trying to write to the ECU with the message "Failed to Unlock ECU".
It is possible that ECUs that have been written to by another third-party software (ie. non-Woolich Racing software) and that these ECUs can be locked to other software. This is common with many Denso models, and means that the WRT software is unable to write to the ECU.
This happens when the other software product changes the 'key' used to unlock the ECU, so that it can be read or written to. If it has been locked, the Woolich Racing Tuned software will give an error message saying 'Failed to Unlock ECU'.
Unfortunately in most cases there is no way around this, and usually the ECU will need to go back to the previous tuner, to have that software/code removed from the ECU, and returned to 100% factory stock, before it can be written to using Woolich Racing Tuned. For a few select models we do have an 'Unlock ECU' feature that if available, you may try using to unlock the key in the ECU, but this may take some time to complete.
In some cases the other software will not be able to return it to stock, because it does not support that option, and they can only rewrite to it with a new bin file. This will not remove the lock, and a replacement ECU may be required to flash it with Woolich Racing Tuned.
The Woolich Racing Tuned software supports going back to 100% stock, but it can not remove another software's lock.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Failing to complete the pre-write checks |
Each time you write to an ECU, the WRT software asks you to confirm that you have completed the displayed checklist (as shown below), before attempting to write to the ECU. These items are very important, and failing to make sure you have checked each one can result in a failed flash.
If you have not checked all of those items, to make sure you will have problem free flashing, then you are responsible for the failure, and any associated losses such as the Bin File Key.
We include these checks to prevent issues, and every customer must agree that they have done these checks before clicking OK.
If you just click OK, and do not do these checks, Woolich Racing will not accept responsibility for your own actions, or the loss of your Bin File Key. You will need to repurchase a new Bin File Key to continue.
While we do understand that there will be a learning curve when you first start using the software, we will offer assistance and leniency for some mistakes. But, we can only offer to correct a limited number of 'accidents', and once you have some experience with the software, you are fully responsible for any losses caused by your own actions, or inactions. Basically, new customers will have a short grace period, and after that, full responsibility to do these checks, rests with the customer.
Please make sure you have completed ALL of those required checks before proceeding to write any ECU.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| I wrote the Wrong Part Number to my ECU, and have errors |
You must use the correct matching ECU Part number always.
There are many points to catch this error before the ECU write will start. - You can check the physical ECU casing.
- You can connect to the ECU and use Tools > Read ECU Part Number. (best option as you can't get it wrong)
- You can search in the software for that part number to confirm what definition (model) it belongs to.
- When clicking write ECU, you are also presented with a checklist that you must confirm that you have actually done those checks before continuing.
If you ignore all those things, and just auto-agree to the checks without doing them, and write the wrong part number to an ECU, we are unable replace the Key if you already agreed that you had done these checks (when you obviously have not)
It is a simple matter to check before flashing and it is fortunate that in most cases it will not be a catastrophic loss, but it can be. ECU's can be very temperamental, and do not like being flashed with the wrong part number, and it is very possible to brick the ECU, which then requires further costs to fix, or replace it.
The end result is that the tuner AND Woolich Racing both get blamed for the bricked ECU.
We will not return Keys that have been incorrectly flashed to an ECU. This is to encourage better responsibility and due diligence, and to avoid damage to both our business' reputations.
Please be very careful, as simple mistakes can cost both the tuner and Woolich Racing, much more than the cost of a key.
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 |
| Failed to check for updates |
If you receive the "Failed to check for updates" error message in the Woolich Racing Tuned software you should manually update the software. Please read the instructions below to Manually Update.
Locate the Woolich Racing Tuned software folder on your computer, this will be in either of the following locations on your hard disk.
c:\Program Files\Woolich Racing Tuned\ or c:\Program Files (x86)\Woolich Racing Tuned\
Double click on the file name "wyUpdate.exe" and follow the prompts to update the software.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| How many computers can I use my WRT account on? |
You are able to use your WRT account on a maximum of 3 computers at the same time.
Your computer count will increase if you install the WRT software onto another PC. If you upgrade your PC to a newer version of Windows, such as Win10 or Win11, this may also count as a 'new' computer by the software.
The account will be auto-locked if you attempt to use the software on more than 3 computers.
If you are no longer using the WRT Software on one of your PC's, it is recommended that you uninstall the software, to avoid your computer count increasing again, and your account being auto-locked.
Please contact us with your account details if this happens as we are able to remove computers from your account.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| I have sent in a Bin File through the software |
When submitting a Bin File readout through the WRT software, you will need to open a Support Ticket (or reply back to your existing ticket/email) to let us know it has been submitted.
Please be aware that we do not monitor these file submissions by email, and if you have been asked to read your ECU and submit the file, you must open a new ticket, or reply back to the relevant ticket/email where we asked you to submit it. If you do not let us know you have submitted a file for review, it will not be reviewed which will cause delays in resolving your issues.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Does your software work on Apple Mac computers? |
Woolich Racing Tuned software is a native Windows application and we can only offer support when installed on a native Windows PC. However we do have customers using Boot Camp or Parallels on Apple Mac computers and while some customers are able to run our software successfully on a Mac, we can not offer support due to the nature of changing Mac hardware and MacOS updates.
If you are experiencing software issues when installing onto a Mac, we can only recommend that you try installing the WRT software onto a native Windows PC.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| Adding WRT Woolich Racing Tuned to Anti Virus / Security Software White List |
Some Anti Virus / Security software falsely detects the WRT Woolich Racing Tuned software as a Trojan or Virus. We have contacted the major Security Companies and reported this issue.
Please read this document and follow the instructions to resolve the issue on your computer.
These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |
| My antivirus software is saying that the Woolich Racing Tuned software is a virus. Should I be concerned? |
Some customers have reported that the Woolich Racing Tuned software has been falsely detected as a virus by their antivirus software. Please follow the documentation for your particular antivirus software to add the Woolich Racing Tuned software as a safe or trusted application/software location on your computer. Please also take the time to submit the software to the antivirus company as a false positive.
The Woolich Racing Tuned software will generally be installed to one of the following locations: - C:\Program Files\Woolich Racing Tuned
- C:\Program Files (x86)\Woolich Racing Tuned
We have put together a document to guide you in adding the WRT software to the Whitelist in your Anti Virus software. If you are still having this issue after following the steps above, please Open a Support Ticket. These Support Center articles may also be of interest to you:
Was this helpful? YesNo
open in new page |