Bus Access Optimisation for FlexRay-based Distributed Embedded Systems

Abstract

FlexRay will very likely become the de-

Task Migration for Fault-Tolerant FlexRay Networks

“…They present several heuristics to determine proper configurations and parameterizations for the FlexRay bus based on the static [11] [7][10] and the dynamic segment [14] [13]. In general, their optimizations and the resulting configurations assume that the executed tasks are statically linked to the nodes of the FlexRay network.…”

Categorizing and Analysis of Activated Faults in the FlexRay Communication Controller Registers

“…Examples of event-triggered protocols are Byteflight, CAN, LonWorks, and Profibus. The main drawback of event-triggered protocols is their lack of predictability [3]. Examples of time-triggered protocols are SAFEbus, SPIDER, and TTP/C.…”

“…To resolve the drawbacks of both event-triggered and time-triggered protocols, other protocols such as TTCAN, FTT-CAN, and FlexRay [4] are introduced. Among the latter protocols, the FlexRay protocol is advancing as the predominant protocol and is expecting to become the de-facto industry standard for X-by-wire applications [5], [2], [3], [6]. As an example, the next edition of the BMW X5 will use the FlexRay protocol in its electronically controlled dampers [5].…”

“…Examples of time-triggered protocols are SAFEbus, SPIDER, and TTP/C. The main drawback of time-triggered protocols is their lack of flexibility [3]. To resolve the drawbacks of both event-triggered and time-triggered protocols, other protocols such as TTCAN, FTT-CAN, and FlexRay [4] are introduced.…”

Investigation and Reduction of Fault Sensitivity in the FlexRay Communication Controller Registers

“…Examples of event-triggered protocols are Byteflight [1], CAN [2], LonWorks [3], and Profibus [4]. The main drawback of event-triggered protocols is their lack of predictability [5]. Examples of time-triggered protocols are SAFEbus [6], SPIDER [7], and TTP/C [8].…”