What I think is confusing you is the bit number 0-64 within a message. Some folks do it the way Aim shows it (bit 0 within the byte is the lowest bitnumber for that word), and most do it the way MoTeC shows it. I don't know which is right (need to scope the bits on the bus)...
What I do know is that the least significant bits of a two character hex values are the lowest order bits -- and that's what I've shown. if you created this template yourself, you probably have the bit numbering within a byte incorrect, so most of your sub-byte values will need to be swapped. If you got it from Aim, then I guess it doesn't work as well as I thought it did (pretty sure I've gotten gear from the M1 CAN stream on Aim dashes).