How to read an LED Error Report


Some Torpedo products are equipped with a display, which is used to control the device, and to display a report when an error is detected in the firmware. Some other products don't have a display, so they report errors another way: through a blinking LED. This article describes how to read this error report.


An error report consists of two numbers, each one from 0 to 255. These numbers are displayed through the red LED on the device. Here is how one number is displayed on the LED:

  • Each digit X is indicated by the LED flashing X times (from 1 to 9). Zero (0) is indicated by a fast double flash.
  • Then, there is a pause between digits.
  • And after all digits have been flashed, there is a longer pause, then the whole thing starts again.


A few examples:

  • The number "5" is indicated by five flashes.
  • The number "30" is indicated by three flashes, a pause, and two fast flashes.
  • The number "128" is indicated by one flash, a pause, two flashes, a pause, eight flashes.

In all these cases, the indicated pattern is displayed, then there is a longer pause, and the pattern is flashed again, and so on.


When an error occurs, the first number of the error report is displayed. Pressing the pushbutton* on the unit once will display the second number of the report. Then, pressing it a second time will either erase the error indicator or reboot the unit, depending on the error. If for any reason pressing the pushbutton doesn't work, simply reboot the unit (turn it off and on again).


Several errors can be triggered simultaneously, in which case several pushes of the button or several reboot of the unit may be required.


* The pushbutton may be hidden, placed at the rear or bottom of the unit. If the pushbutton is accessible through a hole, use a pen or other small object to press it.

  • On the Torpedo Captor X, the pushbutton is accessible through a small hole between the Out Level and Voicing potentiometers.
  • On the Revv D20 and G20, the pushbutton is accessible through a small hole next to the USB connector.


Here is a list of errors that can be flashed by a Torpedo unit. If you encounter an error that is not listed here, please contact us.

This article is a work in progress and being updated regularly.


  • 501, 532, 533: these errors indicate that the product is not fully programmed. Usually, this is because of an update that did not finish properly. The Torpedo products are designed to be ultra-safe when it comes to updates, so don't worry: this can be easily fixed. Usually, connecting the unit with a USB cable to the Remote software on a computer will be enough: Remote will detect that the firmware is missing, and will automatically repair it. Please note this does not work with Wireless Remote at the time.


  • UPDATE V2.xx (actual number may vary): If "No User Firmware" is also displayed on the display, this is the same issue as above. But if the display only shows "Update V2.xx" and nothing more, then the EDIT button may be stuck (On the Torpedo Live and Torpedo CAB). Check if the EDIT button moves freely. If the EDIT button is not stuck, then this may be due to a loose flat cable inside the unit.


  • 206 to 211 (if the unit has no display): these are usually the same as above, but could also be something else. Try the solution described above first.


  • BOOT ERROR 9.0: an update file transfer failed. This may lead to the same issue as above. In any case, simply retry the update.


  • 516: the Bluetooth subsystem did not reboot properly. This error is known to only happens during updates, and has no problematic implication. Simply reboot the unit manually. If rebooting the unit doesn't solve the issue, then it could be a Bluetooth subsystem malfunction, which could require servicing of the unit. Contact Two notes for more details.


  • 564: the Bluetooth subsystem is malfunctionning. This could be a programming issue, you can first try to reinstall the firmware (use Torpedo Remote for this). If reinstalling the firmware doesn't work or doesn't solve the issue, this probably indicates a hardware issue. Contact your retailer for a return, or contact Two notes for help.


  • 25: the DSP is not booting properly. This can indicate either a hardware issue or a firmware bug. Contact Two notes for help on your particular situation.


  • 82: this indicates an error reported by the DSP. The second number of the report indicates which error is reported by the DSP : "82.15" for instance means the DSP is reporting an error 15. Here is the list of these DSP errors (also a work in progress) :
    • 35: a 3rd party IR is longer than supported. This probably means there is a bug either in the Torpedo firmware or Remote software.


  • 87: the DSP is not responding properly to a preset change. This error could be triggered by another error, in which case consider the other error first. Try to check if the error happens when loading one (or several) particular presets, in which case this could indicate an issue with this (or these) particular preset. If this error happens on all presets, this could indicate a hardware issue. In any case, don't hesitate to contact Two notes for help on your particular situation. 


  • 101 : this error indicates a timeout during a file transfer, either during an update or while transfering cabinet files or IRs. Usually, this simply indicates a local, temporary communication issue, like an interference. This error could trigger other errors, or be triggered by other errors. In any case, the usual solution is to simply retry the update or file transfer.


  • 113 : the firmware detected an unknown version of data in the internal memory. This usually means that an update was started, but failed, and then an older version of the firmware was reinstalled. The solution to this issue is to retry and finish the update, using the latest version of Remote available.


  • 125 (Torpedo Live and CAB only): same as error 113.


  • 182: this error is triggered by the "watchdog", a supervisor system that insures the firmware is always running as it should. It usually indicates that the firmware stalled unexpectedly. To solve this issue, please contact Two notes with details about this error.


  • 197: this error indicates a low level issue in the communication between the processors in the unit. This error is rare and still under investigation, but it has been found that it could be linked to the USB connection, and more specifically its quality. If your unit works fine when powered up, and then this error happens when you connect the USB cable and/or launch the Remote software, you can try using another USB cable, removing any hub in the USB connection, using another USB port, or even another computer. If the error seems to not be linked to the USB connection, please contact Two notes for more information.


  • 205: this error happens when trying to renew the BLE pin code while or after being connected to Remote on a computer through USB cable. It is caused by a conflict between BLE and USB connection. To avoid this error, disconnect the USB cable, reboot the unit, and then renew the BLE pin code. This error will be corrected in a future update.


  • 213: the firmware failed to "mount" the memory card (ie, to read its filesystem). This usuallu means the card is not formatted, or formatted with a filesystem that the firmware doesn't support. Try formatting the card, through the "Global" -> "Memory Card Browser" menu.