Have you considered just riding the bike?Below is a tiny example of some raw CAN data.
-----CAN Data example------
The 'Time' field is simply seconds since the start of that particular extract and as you can see there are hundreds of messages per second (approx 300 in this example).
The fields we are interested in are the ARBID and the B0 to B7 columns. The length (len) always seems to be 8 and the Extended indicator (Ext) always seems to be 0 so ignore them.
The data in the columns B0-B7 is in HEX (which excel can easily converts to decimal). HEX is base 16 as opposed to decimals base 10.
Now for a specific example. Engine Temperature appears to be on ARBID 100 column B3, e.g the value 2A at 0.026 seconds. 2A is HEX and converts to 42 in Decimal. It peaked at 142 (dec). I know It was 2 degrees when I started and had reached 84 degrees when it stopped so you can easily work out that you just need to subtract 40 to get to actual temp in degrees c. ARBID 100 seems to transmit about 7 times per second resulting in a the log below for the engine warming up on idle for a few minutes.
-----Engine temp example------
All i've been doing is changing one variable at a time and then searching for it in the data, e.g. indicator flashes starting 5 seconds into the log and lasting for say 5 flashes. If I know what I am looking for it is not too hard to find a corresponding change in the data.
It gets a bit more difficult when multiple things change at the same time. For example, rev the engine and there may be 5 or more columns of data that all change in some way (may be more) at about the right time in the right way.
In the case of revving the engine there are various sensors that you'd expect to respond, e.g. twist grip position, throttle position sensor, engine revs themselves, possible a lambda signal etc. The multi doubles up on most of the 'ride by wire' sensors (I assume for safety reasons), e.g. APS, TPS etc and I think I can see the pair in the data.
To complicate things further a single variable might be split across two columns (or parts of columns). Rear wheel speed is a good example of something that appears to be split across colmuns, ARBID 18, B5, and the 2nd value from B4 (combined as HEX value and then converted to decimal) seems to be rear wheel speed. You then multiple the decimal result by 0.15 to convert to (true) MPH (indicated is +8% according to the manual).
The 1st value from B4 appears to be the gear position indicator so I'm 99% sure I've got this right.
Logic would suggest that you can start to predict what variables are going to be split across columns as the max resolution of 1 column is 16 x 16 = 256. Any sensor needing an output that will have more than 256 incriments must be split across multiple columns.
I can only assume Wheel speed needs it for the ABS and DTC as it clearly doesn't need it for the dash display. Engine revs are split but use all 4 values from a pair of colums.
--------------- SPEED AND GEAR INDICATOR ---------------------
The data sets get very big (in terms of rows as opposed to MB) very quickly, but the newer versions of excel (2007 onwards) are quite good at working with big data sets. Simply filter the data to a single ARBID value, plot as an XY Scatter chart and look for what you are expecting, e.g. the rise and fall of revs or the on/off flash of an indicator.
I got started as much through curiosity as anything but do seem to have become somewhat obsessed with decoding all of the 'normal' CAN traffic. No idea what I'll do with it other than write a program to log the bit I understand in 'english' instead of raw CAN data.