KTM 2020 Superduke Gear Sensor Learning with OBDSTAR

I just cleaned my 2020 KTM 1290 Superduke motorcycycle throttle carbon and some stains, but I have encountered some problems after cleaning it. Now I've solved them and I'm sharing the experience here.

 
I cleaned the throttle after removing the parts like air filter, intake pipe etc. After cleaning, I found that the motorcycle's idle speed was unstable, and I remembered that I had forgotten to initialize and learn about the throttle. So I looked for a friend from the repair store to borrow a scanner to initialize the bike, because there is no dedicated scanner for the KTM, so I used a scanner called OBDSTAR Motormaster (or use iScan for KTM).... As far as I know, normally the motorcycle should be back to normal after doing the throttle initialization function, but after I did this function the motorcycle's gear and startup seemed to have some abnormalities.

I asked my friend for a service manual for a 2020 Superduke to see if there was anything in there about the throttle, and I finally found information about it in section 27.3 of the manual, and you can see the photos below for the specific information, which probably means that you need to do a function like a gear sensor reset at the end. I was a bit puzzled as to why I would need to do this, but went ahead to did what it said......

After doing the gear reset, the dashboard gear was reset, but the car has been restored to normal on the startup side, and finally you just need to learn the gear again to be able to drive normally, as for the method of learning the gear is not that difficult, there is a function called “Shift Shaft Reference Value Learning” in the OBDSTAR scanner, and you can just follow the instructions in it to operate it in a easy way.

Program VW MQB 5A All Keys Lost with OBDSTAR G3 and RH850 Kit

 We have introduced how to calculate sync data for VAG MQB 5A all keys lost using OBDSTAR X300 Classic G3 in the previous post. Today we’ll walk through the step-by-step process for proximity key programming on a 2018 VW Tiguan MQB48 5A model, covering data extraction, decryption, synchronization, and key generation. OBDSTAR now only supports MQB 5A add key and all keys lost. It cannot do 5C immo yet.

 

Tools Required

Before starting, ensure you have the following:

• OBDSTAR X300 Classic G3 programmer

• OBDSTAR RH850/V850 kit

• MP001 programmer (for EEPROM/Flash reading)

• ECM-001 & TCM dedicated cables (for ECU and transmission module access)

• OBDSTAR MQB collector

Step 1: Vehicle Identification & Preparation

1. Connect OBDSTAR G3 to the vehicle via OBD.

2. Select VW > MQB Meter- MQB48-5A/MQB49-5C detection.

3. Power on the ignition to confirm the platform type (5A in this case).

Step 2: Reading IMMO Data from Modules

Select All Keys Lost- Read IMMO Module Data.

It’s a keyless module. So we need to read data from 4 modules: Dashboard, ECU, TCU and ELV.

Ensure an internet connection for server-based calculations.

A: Read Dashboard (Instrument Cluster) IMMO Data

• MCU Model: R7F70147 (RH850-based).

• Method:

  • Disassemble the dashboard and locate the MCU.

  • Solder wires to the C4-06 decryption board (black) using the provided wiring diagram.

  • Connect the MP001 programmer and read PFlash + DFLASH data.

• • Parse immo data. Load Pflash data and Dflash data to calculate immo data. Calculate immo data successfully. Save dash immo data.

B. Read Engine Control Module (ECM) IMMO Data 

• ECM Model: MED17.5.25 (bench mode).

• Method:

  • Use the ECM001 dedicated cable (or jumper wires) to connect. ECM-001 makes it easier.

  • Hit Read IMMO data. Read INT flash + INT eeprom data respectively.

  • Select IMMO Data Decryption function. Upload flash and eeprom data to and get CS code. Save the decrypted immo data.

C. Read Transmission Control Module (TCM) Data 

• TCM Model: DQ380 (0DE).

• Method:

  • Connect TCU via OBDSTAR TCU adapter via P004 adapter or jumper wires (through wiring diagram).

  • Read flash and eeprom data of the DQ380.
    Then select IMMO Data Decryption function.
    Decode CS code.
    Save TCU immo data.

D. Collect ELV (Electronic Steering Lock) Data 

• Method 1: Use the ELV data collector via OBD or bench if remove the ELV module from vehicle (no soldering).

• Method 2: Manual extraction via RH850 adapter (soldering required). OBDSTAR will show you connection instruction.

• In this case, the OBD method was used, and authentication data was calculated via the server.

Connect the MQB collector to the ELV module according to the diagram.

Read and save ELV immo data.

Note:
If the dashboard, ECM, TCM or ELV is not original, such as a replaced module which has not been programmed online at the dealer service or IMMO OFF directly, it will not be able to calculate the ELV IMMO data.

 

 

Step 3: Calculating Synchronization Code

1. Load all extracted data:

   • Dashboard data

   • ECM data

   • TCM data

   • ELV data

2. The OBDSTAR G3 calculates the sync code (starting with the VIN).

3. Verify and confirm the data before proceeding.

Step 4: Making a Dealer Key

1. Load the dashboard immo data and sync code data.

2. Place a blank proximity key on the induction coil.

3. The system writes the immobilizer data, making it a dealer-recognized key.

Step 5: Programming the New Key

1. Reconnect all modules and plug the OBDSTAR G3 into the OBD port.

2. Select “Program Keys” and Load the dashboard IMMO data

3. Place the key near the ignition coil and press the ignition button.

4. The dashboard updates from “0 keys” to “1 key”, confirming success.

Verification & Testing

• Test the remote functions (lock/unlock).

• Confirm the engine starts with the new key.

 

Done.

http://blog.obdii365.com/2025/04/27/obdstar-g3-program-vag-mqb-5a-all-keys-lost-with-rh850-kit/

OBDSTAR OdoMaster Alfa Romeo Stelvio 2018 Mileage Correction Problem Solution

After calibration the mileage of Alfa Romeo Stelvio 2018 year. This error appears (attach a photo). The mileage changes to the desired but flashes constantly and does not show average consumption and instantaneous consumption on the dashboard. I used OBDSTAR OdoMaster Cluster pro. How can I solve the problem? There are no errors on the dashboard.

Solution:

Try to do proxy alignment with tester.

Feedback:

Test proxy alignment with MultiscanEcu.

Everything went good.