This is an un-implemented feature in the software, per the reply below from Mathworks, Don Mathworks reply: Unfortunately this is a limitation in our software. Although the CAN pack block is able to generate the necessary data to mark the given CAN message as Remote Frame, the same information is not used by the C2000 CAN Tx block. The C2000 CAN Tx block treats the CAN message from CAN pack block as another Tx frame and not as Remote frame. The reason being the CAN Tx block does not have the intelligence builtin to parse the Remote bit. 56 GIIMD_CANOpenNMTTestR0_B.CANPack.ID = 1794U; 57 GIIMD_CANOpenNMTTestR0_B.CANPack.Length = 1U; 58 GIIMD_CANOpenNMTTestR0_B.CANPack.Extended = 0U; 59 GIIMD_CANOpenNMTTestR0_B.CANPack.Remote = 1; 60 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[0] = 0; 61 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[1] = 0; 62 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[2] = 0; 63 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[3] = 0; 64 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[4] = 0; 65 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[5] = 0; 66 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[6] = 0; 67 GIIMD_CANOpenNMTTestR0_B.CANPack.Data[7] = 0; Line 59 from CAN pack block sets the Remote bit. But the CAN Tx block is not looking out for this bit as shown below. 95 /* S-Function (c280xcanxmt): ' /eCAN Transmit' */ 96 { 97 tCANMsgObject sTXCANMessage; 98 sTXCANMessage.ui32MsgLen = GIIMD_CANOpenNMTTestR0_B.CANPack.Length;// size of message 99 sTXCANMessage.pucMsgData = (unsigned char*) 100 GIIMD_CANOpenNMTTestR0_B.CANPack.Data; 101 sTXCANMessage.ui32MsgID = GIIMD_CANOpenNMTTestR0_B.CANPack.ID;// CAN message ID - use 1 102 sTXCANMessage.ui32MsgIDMask = 0; // no mask needed for TX 103 sTXCANMessage.ui32Flags = MSG_OBJ_NO_FLAGS; 104 CANMessageSet(CANA_BASE, 18, &sTXCANMessage, MSG_OBJ_TYPE_TX); 105 } Line 104 then configures the message object as Tx rather than Tx_Remote. I have conveyed this information to the development team and they may consider this as an enhancement in a future release.
↧