I've read some posts on the topic of CAN Bus and Daytona 675 ... haven't really found any thread that would get to any sensible results, so I started from the scratch myself. The goal is to build a data logger for track day (or road) use, and eventually build a replacement instrument panel. I have already built and used a custom GPS / Accelerometer / Gyro / Compass for my Daytona 675 and I'm process of writing software tools around it to analyze and use the collected data.
Daytona 675 2011
- OBD connector under the seat has only K-Line, no CAN bus :-/ I could possibly make an active sniffer that sends K-line OBD requests all the time, but I'd rather avoid that. Also, I don't think we'll see much of K-line on bikes in the future. So I'm investigating the connection between the instrument panel and the ECU, which seems to be using CAN. Got connectors that I could plug between the ECU and the instrument panels (avoiding splicing cables) and sniff the traffic. Just didn't have try this last step out yet.
Daytona 675 2015
- OBD connector under the seat has CAN Bus, but seem to be ignoring OBD commands (at least with engine turned off). There is a bit off traffic on the bus that can be passively read out. Just collected the data today, have to do the analysis.
Is there anyone here who is further than I am on this topic and could possibly advise me on any pitfalls that I might be missing?
And by any chance, does anyone know the addresses & message formats of the CAN bus for any of the Daytonas? I'll ask Triumph otherwise, but I expect an NDA, which would be a little counter productive for making this thing public / open source ...
I'm trying to keep track of the progress at http://onkickstand.com/daytona-hacking/
, there is also a bit more detail on what I've done so far in case you are looking for some basic information on CAN / K-Line.