Search Results

Communication between electronic control units (ECUs) and vehicle gateways can span LIN, CAN, FlexRay, and Ethernet. Designing an in-vehicle network supporting multiple car platform variants, with respect to selecting the appropriate technology to connect ECUs and gateway networks, and making timing based analysis and synthesis is extremely challenging. This paper discusses how to handle a variety of communication protocols on an individual network level and how multiple networks relate to the overall communication design of a vehicle platform ensuring consistent variants.

Increasingly, Ethernet is being used in automotive as a vehicle network backbone. It is ideal for service-oriented communications; streamed communications, such as Audio/Video Bridging (AVB) [1]; and Diagnostics over Internet Protocol (DoIP) [2] communications - areas in which high-bandwidth and reliable performance are essential. Designers are accustomed to network communication systems CAN, LIN, and FlexRay, but how will the timing performance be verified in an Ethernet network? This paper looks at network-wide timing analysis challenges where a mixture of CAN, FlexRay, and Ethernetbased busses co-exist. It is also worth noting that the AUTOSAR standard [3] supports timing definition for all elements in a mixed topology network, but again, accounting for the many different timing paths is a non-trivial process. Figure 1 The Ethernet backbone serving different domains.