“On the (non-intrusive) observability of the CAN FD protocol”
From Navigators
(Difference between revisions)
(Created page with "{{Publication |type=inproceedings |title=On the (non-intrusive) observability of the CAN FD protocol |author=João de Sousa Alves, José Rufino |Project=Project:COST Action IC140...") |
|||
| (5 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
{{Publication | {{Publication | ||
|type=inproceedings | |type=inproceedings | ||
| + | |document=Document for Publication-Alves-2017-CANFD-ESI-INForum17.pdf | ||
|title=On the (non-intrusive) observability of the CAN FD protocol | |title=On the (non-intrusive) observability of the CAN FD protocol | ||
|author=João de Sousa Alves, José Rufino | |author=João de Sousa Alves, José Rufino | ||
| - | |Project=Project:COST Action IC1402, Project:NORTH, | + | |Project=Project:COST Action IC1402, Project:NORTH, |
|ResearchLine=Timeliness and Adaptation in Dependable Systems (TADS) | |ResearchLine=Timeliness and Adaptation in Dependable Systems (TADS) | ||
|month=oct | |month=oct | ||
| Line 11: | Line 12: | ||
The definition of the CAN with Flexible Data rate (CAN FD) specification, currently under normalisation, enhances the original CAN protocol in two ways: it extends from 8 to 64 bytes the maximum payload size of a data frame; it enhances the bus signalling rate, while maintaining the determinism of node network access arbitration. | The definition of the CAN with Flexible Data rate (CAN FD) specification, currently under normalisation, enhances the original CAN protocol in two ways: it extends from 8 to 64 bytes the maximum payload size of a data frame; it enhances the bus signalling rate, while maintaining the determinism of node network access arbitration. | ||
| - | The CAN FD data frame includes in its header an | + | The CAN FD data frame includes in its header an Error State Indicator (ESI) flag. Thus, one fundamental question is whether or not the ESI flag will be useful for building highly reliable distributed real-time embedded systems based on the CAN FD protocol? |
This communication formulates the problem in terms of provisioning node failure detection and membership services for CAN FD systems. | This communication formulates the problem in terms of provisioning node failure detection and membership services for CAN FD systems. | ||
| - | + | |booktitle=Proceedings of the 9th Simpósio de Informática (INForum 2017), Aveiro, Portugal | |
| - | |booktitle= | + | |
}} | }} | ||
Latest revision as of 11:21, 7 November 2017
João de Sousa Alves, José Rufino
in Proceedings of the 9th Simpósio de Informática (INForum 2017), Aveiro, Portugal, Oct. 2017.
Abstract: The Controller Area Network (CAN) protocol has been extensively used in many application domains, including industrial control, appliances, medical, and transportation. The last sector includes manned and unmanned vehicles in land, maritime and aerospace. The definition of the CAN with Flexible Data rate (CAN FD) specification, currently under normalisation, enhances the original CAN protocol in two ways: it extends from 8 to 64 bytes the maximum payload size of a data frame; it enhances the bus signalling rate, while maintaining the determinism of node network access arbitration. The CAN FD data frame includes in its header an Error State Indicator (ESI) flag. Thus, one fundamental question is whether or not the ESI flag will be useful for building highly reliable distributed real-time embedded systems based on the CAN FD protocol? This communication formulates the problem in terms of provisioning node failure detection and membership services for CAN FD systems.
Download paper
Download On the (non-intrusive) observability of the CAN FD protocol
Export citation
Project(s): Project:COST Action IC1402, Project:NORTH
Research line(s): Timeliness and Adaptation in Dependable Systems (TADS)
