Electronic Components Datasheet Search
  English  ▼
ALLDATASHEET.NET

X  

MCP2510-I Datasheet(PDF) 7 Page - Microchip Technology

Part # MCP2510-I
Description  Stand-Alone CAN Controller with SPIInterface
Download  80 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  MICROCHIP [Microchip Technology]
Direct Link  http://www.microchip.com
Logo MICROCHIP - Microchip Technology

MCP2510-I Datasheet(HTML) 7 Page - Microchip Technology

Back Button MCP2510-I Datasheet HTML 3Page - Microchip Technology MCP2510-I Datasheet HTML 4Page - Microchip Technology MCP2510-I Datasheet HTML 5Page - Microchip Technology MCP2510-I Datasheet HTML 6Page - Microchip Technology MCP2510-I Datasheet HTML 7Page - Microchip Technology MCP2510-I Datasheet HTML 8Page - Microchip Technology MCP2510-I Datasheet HTML 9Page - Microchip Technology MCP2510-I Datasheet HTML 10Page - Microchip Technology MCP2510-I Datasheet HTML 11Page - Microchip Technology Next Button
Zoom Inzoom in Zoom Outzoom out
 7 / 80 page
background image
© 2007 Microchip Technology Inc.
DS21291F-page 7
MCP2510
2.0
CAN MESSAGE FRAMES
The MCP2510 supports Standard Data Frames,
Extended Data Frames, and Remote Frames (Stan-
dard and Extended) as defined in the CAN 2.0B speci-
fication.
2.1
Standard Data Frame
The CAN Standard Data Frame is shown in Figure 2-1.
In common with all other frames, the frame begins with
a Start Of Frame (SOF) bit, which is of the dominant
state, which allows hard synchronization of all nodes.
The SOF is followed by the arbitration field, consisting
of 12 bits; the 11-bit ldentifier and the Remote Trans-
mission Request (RTR) bit. The RTR bit is used to dis-
tinguish a data frame (RTR bit dominant) from a remote
frame (RTR bit recessive).
Following the arbitration field is the control field, con-
sisting of six bits. The first bit of this field is the Identifier
Extension (IDE) bit which must be dominant to specify
a standard frame. The following bit, Reserved Bit Zero
(RB0), is reserved and is defined to be a dominant bit
by the can protocol. the remaining four bits of the con-
trol field are the Data Length Code (DLC) which speci-
fies the number of bytes of data contained in the
message.
After the control field is the data field, which contains
any data bytes that are being sent, and is of the length
defined by the DLC above (0-8 bytes).
The Cyclic Redundancy Check (CRC) Field follows the
data field and is used to detect transmission errors. The
CRC Field consists of a 15-bit CRC sequence, followed
by the recessive CRC Delimiter bit.
The final field is the two-bit acknowledge field. During
the ACK Slot bit, the transmitting node sends out a
recessive bit. Any node that has received an error free
frame acknowledges the correct reception of the frame
by sending back a dominant bit (regardless of whether
the node is configured to accept that specific message
or not). The recessive acknowledge delimiter com-
pletes the acknowledge field and may not be overwrit-
ten by a dominant bit.
2.2
Extended Data Frame
In the Extended CAN Data Frame, the SOF bit is fol-
lowed by the arbitration field which consists of 32 bits,
as shown in Figure 2-2. The first 11 bits are the most
significant bits (Base-lD) of the 29-bit identifier. These
11 bits are followed by the Substitute Remote Request
(SRR) bit which is defined to be recessive. The SRR bit
is followed by the lDE bit which is recessive to denote
an extended CAN frame.
It should be noted that if arbitration remains unresolved
after transmission of the first 11 bits of the identifier, and
one of the nodes involved in the arbitration is sending
a standard CAN frame (11-bit identifier), then the stan-
dard CAN frame will win arbitration due to the assertion
of a dominant lDE bit. Also, the SRR bit in an extended
CAN frame must be recessive to allow the assertion of
a dominant RTR bit by a node that is sending a stan-
dard CAN remote frame.
The SRR and lDE bits are followed by the remaining 18
bits of the identifier (Extended lD) and the remote trans-
mission request bit.
To enable standard and extended frames to be sent
across a shared network, it is necessary to split the 29-
bit extended message identifier into 11-bit (most signif-
icant) and 18-bit (least significant) sections. This split
ensures that the lDE bit can remain at the same bit
position in both standard and extended frames.
Following the arbitration field is the six-bit control field.
the first two bits of this field are reserved and must be
dominant. the remaining four bits of the control field are
the Data Length Code (DLC) which specifies the num-
ber of data bytes contained in the message.
The remaining portion of the frame (data field, CRC
field, acknowledge field, end of frame and lntermission)
is constructed in the same way as for a standard data
frame (see Section 2.1).
2.3
Remote Frame
Normally, data transmission is performed on an auton-
omous basis by the data source node (e.g. a sensor
sending out a data frame). It is possible, however, for a
destination node to request data from the source. To
accomplish this, the destination node sends a remote
frame with an identifier that matches the identifier of the
required data frame. The appropriate data source node
will then send a data frame in response to the remote
frame request.
There are two differences between a remote frame
(shown in Figure 2-3) and a data frame. First, the RTR
bit is at the recessive state, and second, there is no
data field. In the event of a data frame and a remote
frame with the same identifier being transmitted at the
same time, the data frame wins arbitration due to the
dominant RTR bit following the identifier. In this way,
the node that transmitted the remote frame receives
the desired data immediately.
2.4
Error Frame
An Error Frame is generated by any node that detects
a bus error. An error frame, shown in Figure 2-4, con-
sists of two fields, an error flag field followed by an error
delimiter field. There are two types of error flag fields.
Which type of error flag field is sent depends upon the
error status of the node that detects and generates the
error flag field.
If an error-active node detects a bus error then the
node interrupts transmission of the current message by
generating an active error flag. The active error flag is
composed of six consecutive dominant bits. This bit


Similar Part No. - MCP2510-I

ManufacturerPart #DatasheetDescription
logo
Microchip Technology
MCP2510-IP MICROCHIP-MCP2510-IP Datasheet
993Kb / 76P
   Stand-Alone CAN Controller with SPI Interface
2000 - 2001
MCP2510-ISO MICROCHIP-MCP2510-ISO Datasheet
993Kb / 76P
   Stand-Alone CAN Controller with SPI Interface
2000 - 2001
MCP2510-IST MICROCHIP-MCP2510-IST Datasheet
993Kb / 76P
   Stand-Alone CAN Controller with SPI Interface
2000 - 2001
More results

Similar Description - MCP2510-I

ManufacturerPart #DatasheetDescription
logo
NXP Semiconductors
SJA1000N NXP-SJA1000N Datasheet
226Kb / 68P
   Stand-alone CAN controller
2000 Jan 04
82C200 PHILIPS-82C200 Datasheet
1Mb / 36P
   Stand-alone CAN-controller
November 1992
SJA1000 PHILIPS-SJA1000 Datasheet
234Kb / 68P
   Stand-alone CAN controller
2000 Jan 04
PCA82C200 PHILIPS-PCA82C200 Datasheet
1Mb / 42P
   STAND-ALONE CAN-CONTROLLER
October 1990
logo
IK Semicon Co., Ltd
IN2515 IKSEMICON-IN2515 Datasheet
540Kb / 17P
   STAND-ALONE CAN CONTROLLER
logo
Microchip Technology
MCP2515T-ESTRB4 MICROCHIP-MCP2515T-ESTRB4 Datasheet
633Kb / 84P
   Stand-Alone CAN Controller With SPI Interface
10/05/07
MCP2510I-ST MICROCHIP-MCP2510I-ST Datasheet
1Mb / 80P
   Stand-Alone CAN Controller with SPI??Interface
12/08/06
MCP2515 MICROCHIP-MCP2515 Datasheet
1Mb / 84P
   Stand-Alone CAN Controller With SPI??Interface
2005
MCP2515 MICROCHIP-MCP2515_12 Datasheet
1Mb / 92P
   Stand-Alone CAN Controller with SPI Interface
2003-2012 11/29/11
MCP2515-I MICROCHIP-MCP2515-I Datasheet
1Mb / 92P
   Stand-Alone CAN Controller with SPI Interface
11/29/11
More results


Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80


Datasheet Download

Go To PDF Page


Link URL




Privacy Policy
ALLDATASHEET.NET
Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com