2012
DOI: 10.1007/978-1-4614-0314-2
|View full text |Cite
|
Sign up to set email alerts
|

Understanding and Using the Controller Area Network Communication Protocol

Abstract: except for brief excerpts in connection with reviews or scholarly analysis. Use in connection with any form of information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed is forbidden. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
76
0
6

Year Published

2012
2012
2021
2021

Publication Types

Select...
4
2
2

Relationship

1
7

Authors

Journals

citations
Cited by 121 publications
(82 citation statements)
references
References 0 publications
0
76
0
6
Order By: Relevance
“…As noted by Di Natale (2008), there are a number of potential issues that can lead to behaviour that does not match that required by the scheduling model given by Davis et al (2007). For example, if a CAN node has fewer transmit message buffers than the number of messages that it transmits, then the following properties of the CAN controller hardware can prove problematic: (i) internal message arbitration based on transmit buffer number rather than message ID (Fujitsu MB90385/90387, Fujitsu 90390, Intel 87C196 (82527), Infineon XC161CJ/167 (82C900)); (ii) non-abortable message transmission: Philips 82C200, (Di Natale, 2006);(iii) less than 3 transmit buffers: Philips 8xC592 (SJA1000), Philips 82C200, (Meschi et al, 1996).…”
Section: Motivationmentioning
confidence: 76%
See 1 more Smart Citation
“…As noted by Di Natale (2008), there are a number of potential issues that can lead to behaviour that does not match that required by the scheduling model given by Davis et al (2007). For example, if a CAN node has fewer transmit message buffers than the number of messages that it transmits, then the following properties of the CAN controller hardware can prove problematic: (i) internal message arbitration based on transmit buffer number rather than message ID (Fujitsu MB90385/90387, Fujitsu 90390, Intel 87C196 (82527), Infineon XC161CJ/167 (82C900)); (ii) non-abortable message transmission: Philips 82C200, (Di Natale, 2006);(iii) less than 3 transmit buffers: Philips 8xC592 (SJA1000), Philips 82C200, (Meschi et al, 1996).…”
Section: Motivationmentioning
confidence: 76%
“…Di Natale (2008) noted that using FIFO queues in CAN device drivers / software protocol layers can seem an attractive solution, "because of its simplicity and the illusion that faster queue management improves the performance of the system". This is unfortunate, because FIFO message queues undermine the priority-based bus arbitration used by CAN.…”
Section: Motivationmentioning
confidence: 99%
“…Non-preemptive means that a message being transmitted can not be preempted by higher priority messages that are made available after the transmission has In addition, we observe that sensor data are periodically sampled in control systems . Hence, in most implementations of CAN, there is a software task in the middleware layer, called TxTask, which is periodically activated and responsible for packing messages from signal data and queuing them for transmission [11]. This is supported by the automotive AU-TOSAR/OSEK standard and implemented by the commercial tools from Vector [3].…”
Section: Chapter 4 Online Delay Prediction On Canmentioning
confidence: 99%
“…However, the current current approaches have significant drawbacks. They either perform joint offline design on timing and control, hence inapplicable for online employment [7,11]; or rely on precise knowledge on the timing information of software tasks in the remote sender node, which is ill-suited for CAN where nodes are unsynchronized [19].…”
Section: Introductionmentioning
confidence: 99%
“…Controller Area Network (CAN) is a multi-master serial data bus [3] with real-time capabilities [10,11]. CAN is a broadcast bus, thus each message that is transmitted on the network can be received by every node connected to it.…”
Section: Introductionmentioning
confidence: 99%