canmsg_t.3

can4linux.3.4.6.gz,一个CAN的高级协议包装

.TH "canmsg_t" 3 "8 Feb 2007" "can4linux" \" -*- nroff -*-
.ad l
.nh
.SH NAME
canmsg_t \- The CAN message structure.  

.PP
.SH SYNOPSIS
.br
.PP
.SS "Data Fields"

.in +1c
.ti -1c
.RI "int \fBflags\fP"
.br
.RI "\fIflags, indicating or controlling special message properties \fP"
.ti -1c
.RI "int \fBcob\fP"
.br
.RI "\fICAN object number, used in Full CAN. \fP"
.ti -1c
.RI "unsigned long \fBid\fP"
.br
.RI "\fICAN message ID, 4 bytes. \fP"
.ti -1c
.RI "timeval \fBtimestamp\fP"
.br
.RI "\fItime stamp for received messages \fP"
.ti -1c
.RI "short int \fBlength\fP"
.br
.RI "\fInumber of bytes in the CAN message \fP"
.ti -1c
.RI "unsigned char \fBdata\fP [CAN_MSG_LENGTH]"
.br
.RI "\fIdata, 0. \fP"
.in -1c
.SH "Detailed Description"
.PP 
The CAN message structure. 

Used for all data transfers between the application and the driver using read() or write(). 
.PP
.SH "Field Documentation"
.PP 
.SS "unsigned char \fBcanmsg_t::data\fP[CAN_MSG_LENGTH]"
.PP
data, 0. 
.PP
..8 bytes 

.SH "Author"
.PP 
Generated automatically by Doxygen for can4linux from the source code.