Creating extended message with non-defined DLC
Posted: Thu 23. Feb 2023, 07:29
Hi,
I need to generate a CAN Extended frame in the CAN Router Pro-FD which has a DLC = 40 bytes and with an extended message ID. The message is currently setup with the following values TxMsg values:
TxMsg.id = 0x18FEE300;
TxMsg.dlc = CAN_LEN48_DLC;
TxMsg.msgtype = CAN_MSGTYPE_EXTENDED;
TxMsg.bufftype = CAN_BUFFER_TX_MSG;
When observing the message in CANalyzer I see DLC = 14, but only 8 bytes of data in the trace.
Is there some limitations to non-standard extended CAN messages which can be created? If it matters the message is in J1939 format with a cyclical transmission rate.
I need to generate a CAN Extended frame in the CAN Router Pro-FD which has a DLC = 40 bytes and with an extended message ID. The message is currently setup with the following values TxMsg values:
TxMsg.id = 0x18FEE300;
TxMsg.dlc = CAN_LEN48_DLC;
TxMsg.msgtype = CAN_MSGTYPE_EXTENDED;
TxMsg.bufftype = CAN_BUFFER_TX_MSG;
When observing the message in CANalyzer I see DLC = 14, but only 8 bytes of data in the trace.
Is there some limitations to non-standard extended CAN messages which can be created? If it matters the message is in J1939 format with a cyclical transmission rate.