CpStruct_CAN Struct Reference
CAN message structure. More...
Public Attributes | |
| _U32 | v_MsgId |
| _U32 | v_MsgFlags |
| _U08 | v_MsgData [8] |
Detailed Description
CAN message structure.
For transmission and reception of CAN messages a structure which holds all necessary informations is used. The structure has the following data fields:
Definition at line 46 of file cpstruct.h.
Member Data Documentation
| _U08 v_MsgData[8] |
The data fields contain up to eight bytes for a CAN message. If the data length code is less than 8, the value of the unused data bytes will be undefined.
Definition at line 84 of file cpstruct.h.
Referenced by CANMessage::operator=().
| _U32 v_MsgFlags |
The message flags field contains the data length code (DLC) of the CAN message and the buffer number when using a FullCAN controller.
The data length code (Bit 0 - Bit 3) contains the number of data bytes which are transmitted by a message. The possible value range for the data length code is from 0 to 8 (bytes).
A FullCAN controller (e.g. AN82527) has more than only one transmit and one receive buffer and offers more sophisticated message filtering. The field message buffer (Bit 4 - Bit 7) specifies the buffer for message transmission or reception.
The high word (Bit 16 - Bit 31) is reserved for user defined data.
Definition at line 78 of file cpstruct.h.
Referenced by CANMessage::operator=().
| _U32 v_MsgId |
The identifier field may have 11 bits for standard frames (CAN specification 2.0A) or 29 bits for extended frames (CAN specification 2.0B). The three most significant bits are reserved for special functionality (the LSB is Bit 0, the MSB is Bit 31 ).
- Bit 31: Bit value 1 marks the identifier as an extended frame. Bit value 0 marks the identifier as a standard frame.
- Bit 30: Bit value 1 marks the identifier as an remote transmission (RTR).
- Bit 29: Reserved for future use
Definition at line 61 of file cpstruct.h.
Referenced by CANMessage::operator=().
The documentation for this struct was generated from the following file:
