This is a continuation of another forum post, from here.
Hooovah, the capability I need is very similar to how the "ID CRC" feature currently works, I just need a little bit more flexibility in how the ID is added to the payload bytes, prior to CRC calculation. As you described it, the 4-byte CAN ID is concatenated to the front of the CAN payload, and by your example, it is being added in "big endian" fashion. What I require for my application, is to add that same 4-byte CAN ID to CAN payload, but I need it added in "little endian" format, such that:
if CAN ID = 0x1FFF313
and CAN payload = 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x[CRC]
then the CRC is calculated on:
0x13 0xF3 0xFF 0x01 0x01 0x02 0x03 0x04 0x05 0x06 0x07