Scribd Logo
Upload

Welcome to Scribd!

  • 31 views

    GSXR Scluster

    Uploaded by

    Anthony August Archer
    The document provides instructions for building and using a decoder to access diagnostic data from a GSX-R motorcycle's ECU. The decoder connects to the ECU and a laptop to display real-time data like coolant temperature and trouble codes. It uses an Arduino microcontroller and requires uploading firmware before establishing a serial connection to view the datastream in a terminal program like Putty. Precautions are outlined to avoid damaging the ECU during the process.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    GSXR Scluster

    Uploaded by

    Anthony August Archer
    31 views6 pages
    The document provides instructions for building and using a decoder to access diagnostic data from a GSX-R motorcycle's ECU. The decoder connects to the ECU and a laptop to display real-time data like coolant temperature and trouble codes. It uses an Arduino microcontroller and requires uploading firmware before establishing a serial connection to view the datastream in a terminal program like Putty. Precautions are outlined to avoid damaging the ECU during the process.

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides instructions for building and using a decoder to access diagnostic data from a GSX-R motorcycle's ECU. The decoder connects to the ECU and a laptop to display real-time data like coolant temperature and trouble codes. It uses an Arduino microcontroller and requires uploading firmware before establishing a serial connection to view the datastream in a terminal program like Putty. Precautions are outlined to avoid damaging the ECU during the process.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    31 views6 pages

    GSXR Scluster

    Uploaded by

    Anthony August Archer
    The document provides instructions for building and using a decoder to access diagnostic data from a GSX-R motorcycle's ECU. The decoder connects to the ECU and a laptop to display real-time data like coolant temperature and trouble codes. It uses an Arduino microcontroller and requires uploading firmware before establishing a serial connection to view the datastream in a terminal program like Putty. Precautions are outlined to avoid damaging the ECU during the process.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 6

    GSX-R Scluster decoder v1.0 by mr_hollywood@cogeco.

    ca (Apr 2019)

    These instructions detail how to build, connect and use the GSXR Scluster decoder.

    The decoder is used to calibrate the TPS sensor (in Dealer Mode) and read ECU Trouble Codes, when the original
    instrument cluster is not installed. The data can be viewed by connecting a laptop to the Scluster via a USB port.

    An ANSI compatible terminal program (such as Putty) can then connect over a COM port to display the data. Here’s an
    example of data (in Dealer Mode with 3 trouble Codes):

    Display details:

    Rcvd :This is a hex byte counter that increments as data is received from the ECU. This gives a visual indicator
    that data is being received.

    Coolant Temp : This is raw data (hex byte) that is inversely proportional to the actual temperature.

    Dealer Mode : Displays whether Dealer Mode is active (Y,N). Dealer Mode must be active to calibrate the TPS sensor.

    TPS adjust : Displays adjustment data (H, -, L) when Dealer Mode is active. This is used to calibrate the TPS sensor.

    Critical Codes : Displays all critical error codes. The engine will not start when critical codes are present.
    (If only one ignition or one injector code is present, the engine will still start).

    Error Codes : Displays all non-critical error codes. The engine can be started if these codes are present.

    Note: All Error Codes are cleared when the ECU is powered off.
    Hardware:

    The decoder uses a 5v 16mhz Arduino Nano v3 (Atmel 328P/CH340G) to decode data from the ECU. These are
    commonly available for less than $10 and must have an Arduino compatible bootloader installed.

    Connection to the ECU:

    Only 3 wires are required to connect the decoder to the ECU as illustrated below:

    The R (pin48) and B/Br (pin54) wires are already present at the harness “YAFMS” (Yoshbox) connector. If you’re not
    using a Yoshbox to adjust fuel trim (and don’t have a cluster installed), this connector can be modified to accommodate
    the decoder by adding a connection from ECU pins 56. This version of the decoder is designed to be connected to the
    ECU during diagnostic sessions only. There is no CPU supervision enabled (i.e. watchdog timer) to prevent CPU lock-up.

    NOTE: Shorting any of the above wires to frame ground or battery voltages will destroy the
    ECU. As such, the Nano board must also be suitably insulated/protected to avoid shorts.
    Connecting to the laptop:

    The Scluster decoder connects to the laptop with a USB cable. Windows should automatically install the CH340 driver
    when it is connected, and you can confirm this (and the COM port being used) in the Windows Device Manager.

    Note: Windows automatically assigns the COM port and this will change if a different USB port is used.

    Uploading the Scluster firmware:

    The Arduino Nano v3 comes from the factory without any programming, but (should) contain a bootloader that allows you
    to upload your firmware (program). The Scluster decoder firmware is written in AVR 328p assembler and can be uploaded
    as follows:

    1) Unzip the “Scluster v1.0.zip” file to a new folder on your computer.


    2) Connect the Scluster Decoder to your laptop and run the Device Manager to confirm the COM port assigned.
    3) Double-click on the “- Firmware 56k.bat” file in your new folder, to begin the upload process…
    - You will be prompted to enter the COM port number (digits only, then press ‘enter’)
    - If this fails (as below), retry using the “- Firmware 115k.bat” file instead. The correct baud rate for the upload
    depends on the bootloader version installed in the Nano(which is unknown).

    - You should also check the error message confirm the correct COM value was used (circled in yellow above).
    - The above picture shows the tail end of the message from a successful flash. You should check the message
    to confirm the flash was successfully verified (circled in yellow).

    4) Once the upload is successful, run the Putty program and connect to the Scluster Decoder (see next page) to confirm it
    is displaying properly.

    Note: The “Rcvd” count will remain at “00” until data is received from the ECU, and will increment each time
    new data is received (about twice per second).
    Installing the ANSI terminal (Putty) software:

    You can download the (free) Putty terminal program here:


    http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

     After installing the program, run the ‘Putty.exe’ program and adjust the following settings:

    o Category: Session
    Serial line: COMx (x is the port you're using)
    Speed: 115,200

    Select the ‘Serial’ radio button

    o Category: Keyboard
    Function Keys: ESC[n~

    o Category: Serial
    Serial line: COMx (x is the port you're using)
    Speed: 115,200
    Bits: 8
    Stop: 1
    Parity: None
    Flow: None

    o Return to the Session screen and save the settings with a new ‘Saved Sessions” name (i.e. Scluster)

     To start a session, connect the Scluster decoder to the laptop the click on your saved session in Putty.

    Note that changing the laptop USB port you’re using will change the COM port.

    Warnings:

     ESD precautions should be taken at all times to ensure the ECU and Scluster Decoder are not damaged by static
    electricity discharge.

     Incorrect connections (misaligned pins, reverse connection) may result in permanent damage to the ECU and the
    Scluster decoder, so double-check your connections carefully before applying power.

     Reasonable efforts have been made to ensure that the information presented here is correct and accurate.
    Nevertheless, you are solely responsible for the outcome, no matter the cause. Proceed at your own risk.

    In closing:

    The Scluster Decoder project would not have been possible without the amazing work done by JoE on the TLPlanet.com
    forum. His research on the protocol used by the GSXR insturmentation cluster was the starting point for this whole
    project….

    Hat’s off to you JoE and many thanks!!!

    [email protected]
    - Appendix -

    Here’s a list of all Error Codes available with the Scluster Decoder:

    You might also like