can0
interface (always can0
if you only have one device connected) at a bit rate of 500 kbps, which is standard.-c
colorizes the changing bytes and can0
is the interface to sniff. It takes a few seconds to remove the constant packets.C9
. There are probably multiple potential packets that vary with RPM, this is just the first one.07
don’t seem to correlate to varying RPM. The last byte 1B
does.00
. This would indicate that it represents the throttle position and not the RPM.21 C0
that do seem to correspond to a change in RPM. More so, it varies as a 16 byte integer i.e. when the second byte C0
overflows, the first byte 21
gets increased by one. Also it seems that 21
corresponds to roughly 2000 RPM. This is good to note when you will replay the message.<arb_id>#
{data} and must be substituted with your own CAN message.0C9
with CAN message you identified and it’s arbitration id respectively. You can experiment with both approaches to see which one works better.