Ducati SuperSport 950 S MY2022 – M4C – Bike not recognized / wrong live data / DTC not read
Posted: Sat Aug 15, 2026 8:33 am
Hi jpl250rs,
I would like to ask for help with MelcoDiag and my Ducati SuperSport 950 S MY2022.
The connection to the bike works successfully using:
Ducati red Euro5 6-pin diagnostic connector → OBD adapter
USB ELM327 with PIC18F25K80 / CH340
HS-CAN
MelcoDiag 2.0.5.2
"Any bike" selected
MelcoDiag communicates with the ECU and successfully reads:
VIN: ZDM3V35**********
Hardware Version: DU CAX20
Software Version: DN2LT000173
Year: 2022
However, during identification I get:
Bike not recognized: 3V35
Estimated: Recent Ducati (bike=8)
The debug report also shows 14 active PIDs, so communication with the ECU seems to be working correctly.
The problem is that the decoded live data are clearly incorrect. For example, with the engine not running MelcoDiag displayed approximately:
RPM: 8206
AFR: 42
ECU voltage: 25.5 V
Ambient temperature: -40 °C
Mileage: 3423 km
DTC scanning also communicates with addresses 7E0, 7E1, 7E2 and 7E3, but finishes with:
No faults / 0 ECU(s) with 0 fault(s)
This is interesting because the motorcycle was recently connected to the official Ducati diagnostic system and the engine ECU had stored:
P0314 – High misfire with risk of catalyst damage (MEM)
Therefore it looks like the CAN/ELM communication itself is working, but this particular SuperSport 950 / M4C configuration may not yet be correctly identified/decoded by MelcoDiag.
Could you please check whether 3V35 / Ducati SuperSport 950 S MY2022 with Continental M4C can be added or correctly identified in MelcoDiag?
I have the complete MelcoDiag debug report and screenshots available and can provide any additional ECU data or tests you need.
Thank you very much for your work on MelcoDiag and for your help!
I would like to ask for help with MelcoDiag and my Ducati SuperSport 950 S MY2022.
The connection to the bike works successfully using:
Ducati red Euro5 6-pin diagnostic connector → OBD adapter
USB ELM327 with PIC18F25K80 / CH340
HS-CAN
MelcoDiag 2.0.5.2
"Any bike" selected
MelcoDiag communicates with the ECU and successfully reads:
VIN: ZDM3V35**********
Hardware Version: DU CAX20
Software Version: DN2LT000173
Year: 2022
However, during identification I get:
Bike not recognized: 3V35
Estimated: Recent Ducati (bike=8)
The debug report also shows 14 active PIDs, so communication with the ECU seems to be working correctly.
The problem is that the decoded live data are clearly incorrect. For example, with the engine not running MelcoDiag displayed approximately:
RPM: 8206
AFR: 42
ECU voltage: 25.5 V
Ambient temperature: -40 °C
Mileage: 3423 km
DTC scanning also communicates with addresses 7E0, 7E1, 7E2 and 7E3, but finishes with:
No faults / 0 ECU(s) with 0 fault(s)
This is interesting because the motorcycle was recently connected to the official Ducati diagnostic system and the engine ECU had stored:
P0314 – High misfire with risk of catalyst damage (MEM)
Therefore it looks like the CAN/ELM communication itself is working, but this particular SuperSport 950 / M4C configuration may not yet be correctly identified/decoded by MelcoDiag.
Could you please check whether 3V35 / Ducati SuperSport 950 S MY2022 with Continental M4C can be added or correctly identified in MelcoDiag?
I have the complete MelcoDiag debug report and screenshots available and can provide any additional ECU data or tests you need.
Thank you very much for your work on MelcoDiag and for your help!