Question about Multistrada CAN reverse engineering, dashboard/BBS, and old notes

[Jodameister]

Hi,

I came across your MTS1200-CANBUS repo while researching Ducati Multistrada diagnostics and CAN reverse engineering.

I am currently looking at a 2017 Ducati Multistrada 1200 DVT and trying to understand the deeper architecture behind service/reset functions, especially around:

• instrument cluster / dashboard
• BBS / body-side modules
• CAN-level communication
• possible KWP2000-on-CAN / UDS-like diagnostics
• read-only sniffing before attempting anything risky

I am not looking for a quick workshop shortcut. I am trying to understand which modules matter, how the traffic is structured, and where service logic may actually live.

Your repo is old, so I do not know if you are still active in this topic. But if you still remember any of it, I would love to ask:

1. Did you ever identify useful CAN IDs or module boundaries on the Multistrada beyond the basic bike-state data?
2. Did you ever look at dashboard / instrument-cluster related traffic specifically?
3. Did you ever find anything pointing toward service-reminder logic, odometer sync, or body-module interaction?
4. Do you still have any old notes, captures, logs, or unpublished experiments?
5. If you are no longer active, do you know anyone from the Ducati CAN / reverse-engineering scene who would be worth contacting?

One extra angle that may be new compared to older forum work: I suspect modern AI-assisted analysis could help cluster large CAN logs, correlate state changes, and speed up hypothesis testing on unknown bytes and IDs. So even partial raw captures or rough notes could still be surprisingly useful today.

If you are open to it, even a short pointer would help a lot.

Thanks.

[renatobo]

Thanks to @MrCanBus initial work, I put this together : DucatiPanigaleCanBus

If you go to credits, you'll find a community contributed spreadsheet and some additional info.