Ducati SuperSport 950 S MY2022 – M4C – Bike not recognized / wrong live data / DTC not read

[Kubajz09]

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!

[Kubajz09]

Here are screenshots

[Kubajz09]

I have also found the existing thread regarding a 2021 SuperSport 950 S with very similar symptoms. My MY2022 bike appears to behave very similarly in MelcoDiag, so the two cases may be related.

[Kubajz09]

Melcodiag debug file:

"File generated On 14. 8. 2026 17:46:36"
"Software version 2.0.5.2"
"ELM version : ELM327 v1.5"

"Auto Detect Bike = Recent Ducati ?"
"User Bike = 2022"

"CAN Bike = "
"Ecu = N/A"
"Hardw = DU CAX20"
"Softw = DN2LT000173"
"OilService = NO"
"DesmoService = NO"

"
14 PIDS active founds

023_000000547FC702DB
024_0000000000000C96
150_0002207E00004DDB
020_0040951000004DFF
018_0002A0008200485C
019_960960000000083B
080_2192BCC025200C3F
100_C812019FFF001B21
174_18800051448701A6
178_00800000458101DB
17C_FE7F0100789D017E
188_7FFF7C4F804B4349
022_000000000003F386
18C_800B7FFF00000475
"
"Vin = ZDM3V35*********"
"DTC = "
"E4436880"
"Bike = 8"
"lic found
? outp='ZDM3V35*********'
PaniVIN: ZDM3V35*********
lic is valid
? outp='DU CAX20'
? outp='DN2LT000173'
"
"registered"

[jpl250rs]

you can try the version 2.0.5.3 for recognizition and DTC

[Kubajz09]

Thanks for fast response, I tried the version 2.0.5.3 and motorcycle model is great but data looks very strange, and I still have unknown ECU, is it somehow possible to solve it?

[jpl250rs]

for the live data , it need me to access your computer via a remote session with rustdek

[Kubajz09]

Ahh ok. So anyway it works? It reads the data from ecu like errors etc even if theres written unknown (N/A) ecu?

[jpl250rs]

all functions are separated , the vin is only the entry point