Distributed Real-Time Systems (TI-DRTS) Track 3

Similar documents
Introduction to TTP and FlexRay real-time protocols

FlexRay A Communications Network for Automotive Control Systems

Comparison of FlexRay and CAN-bus for Real-Time Communication

Simple and error-free startup of the communication cluster. as well as high system stability over long service life are

Introduction to RACE FUELS Hans-Christian von der Wense Munich, Germany

In-Vehicular Communication Networking Protocol

Standardized software components will help in mastering the. software should be developed for FlexRay were presented at

Local Interconnect Network Training. Local Interconnect Network Training. Overview

Distributed Real-Time Systems (TI-DRTS) Track 2. CAN-BUS Introduction. Version Ref. VECTOR application note & Motorola note

LIN (Local Interconnect Network):

FOUNDATION Fieldbus High Speed Ethernet Control System

Introduction to. LIN (Local Interconnect Network)

In-Vehicle Networking

Comparison of CAN, TTP and Flexray Communication Protocols

EBERSPÄCHER ELECTRONICS automotive bus systems. solutions for network analysis

In networking ECUs in heavy-duty vehicles, it is the J1939 protocol that. plays a key role. J1939 networks are based on the CAN bus (high-speed

AutoSAR Overview. FESA Workshop at KTH Prof. Jakob Axelsson Volvo Cars and Mälardalen University

Mixed-Criticality Systems Based on Time- Triggered Ethernet with Multiple Ring Topologies. University of Siegen Mohammed Abuteir, Roman Obermaisser

byteflight - A New Protocol for Safety Critical Applications

Introduction to LIN. Webinar

The Temporal Firewall--A Standardized Interface in the Time-Triggered Architecture

The Problem: Automotive safety recalls, Control Systems Diagnostics, Stability Control, Traction Control, Anti-lock Braking, Adaptive Cruise Control

Lecture 4 Profibus. Urban Bilstrup Urban.Bilstrup@ide.hh.se

Embedded OS. Product Information

Linear Motion and Assembly Technologies Pneumatics Service. Industrial Ethernet: The key advantages of SERCOS III

LOCAL INTERCONNECT NETWORK (LIN)

Automotive Software Engineering

Model-based Testing of Automotive Systems

Introduction to Ethernet and IP in automotive vehicles

ECU State Manager Module Development and Design for Automotive Platform Software Based on AUTOSAR 4.0

Wireless Microcontrollers for Environment Management, Asset Tracking and Consumer. October 2009

SIMULATION-BASED APPLICATION SOFTWARE DEVELOPMENT IN TIME-TRIGGERED COMMUNICATION SYSTEMS

How to design and implement firmware for embedded systems

Automotive Communication Network Trends

Integration of FlexRay-based control units in existing test benches

Laboratory Course Industrial Automation. Experiment Nr. 6. Introduction to the FlexRay bus system. Brief User Guide IAS Demonstrator Go-Cart

Embedded Networking. CarRing II: A Real-Time Computer Network as Successor of Flexray?

Open Source Software

Vorlesung Kommunikationsnetze Fieldbus Systems

A Real-time Ethernet Prototype Platform for Automotive Applications

Contributions to the Engineering of Safety Critical Automotive Systems

Welcome to the Introduction to Controller Area Network web seminar My name is William Stuart, and I am a Applications Engineer for the Automotive

Application of Software Watchdog as a Dependability Software Service for Automotive Safety Relevant Systems

Software Development for Multiple OEMs Using Tool Configured Middleware for CAN Communication

An Automated Model Based Design Flow for the Design of Robust FlexRay Networks

Software Stacks for Mixed-critical Applications: Consolidating IEEE AVB and Time-triggered Ethernet in Next-generation Automotive Electronics

Making model-based development a reality: The development of NEC Electronics' automotive system development environment in conjunction with MATLAB

Industrial Networks & Databases

SUSPENSION AND STEERING OVERVIEW

ISO11783 a Standardized Tractor Implement Interface

EB Automotive Driver Assistance EB Assist Solutions. Damian Barnett Director Automotive Software June 5, 2015

The I2C Bus. NXP Semiconductors: UM10204 I2C-bus specification and user manual HAW - Arduino 1

Safety compliance. Energy management. System architecture advisory services. Diagnostics. Network topologies. Physical and functional partitioning

GE Power Controls FIELDBUS APPENDIX PROFIBUS DP. Doc. No.: ASTAT Plus PB_Appendix-v0

EB TechPaper. Test drive with the tablet. automotive.elektrobit.com

Vehicular On-board Security: EVITA Project

SAN Conceptual and Design Basics

From Signal Routing to complete AUTOSAR compliant CAN design with PREEvision (II)

Customer Experience. Silicon. Support & Professional Eng. Services. Freescale Provided SW & Solutions

Elettronica dei Sistemi Digitali Costantino Giaconia SERIAL I/O COMMON PROTOCOLS

Low-Overhead Hard Real-time Aware Interconnect Network Router

Serial Bus Systems in the Automobile

Real-Time (Paradigms) (51)

Safety and Security Features in AUTOSAR

Automotive electronics CAN and LIN buses. Copyright 2006 Matrix Multimedia Limited

Introduction CHAPTER 1

PROFINET the Industrial Ethernet standard. Siemens AG Alle Rechte vorbehalten.

Technical Article. NFiC: a new, economical way to make a device NFC-compliant. Prashant Dekate

Industrial Requirements for a Converged Network

Customer Specific Wireless Network Solutions Based on Standard IEEE

Highly Available Mobile Services Infrastructure Using Oracle Berkeley DB

How to Hack Your Mini Cooper: Reverse Engineering CAN Messages on Passenger Automobiles

EBERSPÄCHER ELECTRONICS automotive bus systems

Safety and security related features in AUTOSAR

Java-based Functionality and Data Management in the Automobile. Prototyping at BMW Car IT GmbH. by Alexandre Saad, BMW Car IT GmbH, Munich/Germany

SPI I2C LIN Ethernet. u Today: Wired embedded networks. u Next lecture: CAN bus u Then: wireless embedded network

Towards Verified Automotive Software

Overview and Applications of PROFINET. Andy Verwer Verwer Training & Consultancy Ltd

Ring Local Area Network. Ring LANs

An Automated Data Structure Migration Concept - From CAN to Ethernet/IP in Automotive Embedded Systems (CANoverIP)

Ingegneria del Software II academic year: Course Web-site: [

Fiber-Optic Real-Time Networks for Distributed Computing Systems. Magnus Jonsson. Node 2. Magnus Jonsson, Halmstad University, Sweden.

Switch Fabric Implementation Using Shared Memory

Development of AUTOSAR Software Components within Model-Based Design

Vehicle data acquisition using CAN By Henning Olsson, OptimumG

Real-time Ethernet with TwinCAT network variables

Created by: Austin Davis Neel Iyer Darcie Jones Sascha Schwarz

Adaptive Cruise Control System Overview

A Transport Protocol for Multimedia Wireless Sensor Networks

M.S Ramaiah School of Advanced Studies - Bangalore. On completion of this session, the delegate will understand and be able to appriciate:

Bus Data Acquisition and Remote Monitoring System Using Gsm & Can

Generic term for using the Ethernet standard in automation / industrial applications

The OSI Model and the TCP/IP Protocol Suite PROTOCOL LAYERS. Hierarchy. Services THE OSI MODEL

LIN. Specification Package. Revision 2.0. This specification is provided on an "AS IS" basis only and cannot be the basis for any claims.

Design and Verification of Nine port Network Router

CSMA/CA. Information Networks p. 1

Network protocols used in the automotive industry

PEMS Conference. Acquiring Data from In-Vehicle Networks. Rick Walter, P.E. HEM Data Corporation

Bluetooth Audio Data Transfer between Bluetooth chipset (PMB6752&PMB6625) and TriCore Host TC1920

Mixed-Criticality: Integration of Different Models of Computation. University of Siegen, Roman Obermaisser

Transcription:

Distributed Real-Time Systems (TI-DRTS) Track 3 The Communication Systems for advanced automotive control applications www.flexray.com Version: 17.11.2008

Abstract The FlexRay protocol provides flexibility and determinism by combining a scalable static and dynamic message transmission, incorporating the advantages of familiar synchronous and asynchronous protocols Sources: FlexRay Requirements Specification, Version 2.1, 19-dec-2005 (115 pages). FlexRay Protocol Specification, Version 2.1.Rev.A, 15-dec-2005 (243 pages). Slide 2

Context Demand for a bus system with high data rate for automotive applications Deterministic and fault-tolerant bus system for advanced automotive control applications Support from the bus system for distributed control systems Limited number of different communication systems within vehicles Slide 3

FlexRay Consortium Goals Develop an advanced communication technology for high-speed control applications in vehicles Make the technology available in the market place for everyone Drive the technology as a defacto standard Slide 4

FlexRay Architecture Example CAN Slide 5

FlexRay Core Partners The seven FlexRay Consortium Core Partners: BMW Daimler Volkswagen General Motors Bosch Freescale (Motorola) NXP (Philips) Semiconductors have agreed on continuation agreements for the time frame from January 1, 2009, until December 31, 2009. Slide 6

FlexRay History Source: www.flexray.com Slide 7

Freescale s FlexRay Roadmap Slide 8

Slide 9

FlexRay News BMW X5 Slide 10

BMW X5 first FlexRay Car AdaptiveDrive an optional chassis package: AdaptiveDrive, uses sensors that constantly monitor and calculate data on the road speed of the vehicle, its steering angle, straight-line and lateral acceleration, body and wheel acceleration, as well as height levels. Then, based on this information, the system controls both the swivel motors on the anti-roll bars and the electromagnetic shock absorber valves, controlling body roll and dampening as required at all times. Simply by pressing a button, the driver can choose either a sporting or a more comfortable basic setting of AdaptiveDrive. BMW X5 is based on Freescale's 32-bit FlexRay MCUs. Freescale is currently the only semiconductor supplier that has FlexRay microcontrollers (MCUs) in a production-ready automobile. The new BMW X5 will be launched in North America at the end of November 2006. It will be available in other markets worldwide in spring 2007. Slide 11

FlexRay News (2006) Slide 12

General FlexRay Requirements One or two channel solutions must be supported An electrical and optical physical layer must be supported Redundant physical links is optional. A mix of non-redundant and redundant physical links must be supported Wake-up of nodes and stars via the communication system A baud-rate from 500 Kbit/s up to 10 Mbit/s Slide 13

Basic Features Synchronous and asynchronous data transmission High net data rate of up to 10 Mbit/sec Deterministic data transmission, guaranteed message latency and message jitter Support of redundant transmission channels Fault tolerant and time triggered services implemented in hardware Fast error detection and signaling Support of a fault tolerant synchronized global time base Error containment on the physical layer through an independent "Bus Guardian" Support of optical and electrical physical layer Support for bus, star and multiple star topologies Slide 14

Use Cases for the FlexRay Communication System Source: FlexRay Req. spec. Slide 15

FlexRay Node Architecture (1) ECU= Electronic Control Unit Slide 16

FlexRay Node Architecture (2) Bus Driver Slide 17

Host Processor Inteface Slide 18

FlexRay Communication Controller http://www.semiconductors.bosch.de/pdf/bosch_product_info_e-ray_ip_v11.pdf Slide 19

E-Ray FlexRay Controller Block Diagram PRT A: Protocol Communication Controller (Protocol Finit State Machine) TBF A: Transient Buffer RAM IBF: Input Buffer OBF: Output Buffer Source: www.bosch.de Slide 20

State Model of a Communication Module Source: FlexRay Req. spec. Slide 21

Topologies - Bus & Star Bus passive medium no active components within the channel most automotive experience automotive costs Star best suited technology for high speed networks different degrees of intelligence possible with/without protocol knowledge can protect against concurrent media access limits the error domain of not correctly working sub networks Slide 22

Passive Bus Topology Slide 23

Active Star Toplogy Slide 24

Active Star Component A branch has to be deactivated if a faulty signal is detected A deactivated branch shall be fail-silent and should be reactivated if the fail condition is no longer available Slide 25

Hybrid Topology Slide 26

Static and Dynamic Segments Static message segment state message semantic deterministic communication behavior periodic statically scheduled message transfer is a benefit for automotive applications, especially distributed control loops with replication required support for distributed control and closedloop control functions Dynamic message segment spontaneous (event) message transfer e.g. for burst transmissions for diagnostic information for ad hoc messages in general Slide 27

FlexRay Configurations Slide 28

Frame Transfer Cycles consisting of two segment Static: Divided in timeslots (TDMA) The slot length is defined off-line and therefore fixed during runtime Dynamic: Has a start delimiter: Start of cycle SOC Dynamic frame length Media is accessed via timers and priorities Slide 29

FlexRay Communication Cycle Slide 30

Communication Scheme Slide 31

Topology Example A node can either be connected to both channels or only to one of the channels Slide 32

Frame Transfer (1) Communication cycle with both static and dynamic segments A,D,C,E A,B,C,E Slide 33

Frame Transfer (2) Communication cycle in a pure dynamic system Start of Cycle Slide 34

Timing Hierarchy Within one communication cycle FlexRay offers the choice of two media access schemes. These are a static time division multiple access (TDMA) scheme, and a dynamic mini-slotting based scheme. Slide 35

Static Part Characteristics (1) Slide 36

Static Part Characteristics (2) Slide 37

Dynamic Part Minislotting (1) Slide 38

Dynamic Part Minislotting (2) Slide 39

Dynamic Characteristics (1) Slide 40

Dynamic Characteristics (2) Slide 41

FlexRay Frame Format (1) 254 bytes payload Payload length Frame ID (11 bits): The frame ID defines the slot in which the frame should be transmitted. A frame ID is used no more than once on each channel in a communication cycle. Slide 42

FlexRay Frame Format (2) Network Management Vector The message ID is an application determinable number that identifies the contents of the data segment Slide 43

AUTOSAR TTAutomotive Joins AUTOSAR, Vienna, Austria November 29, 2005 AUTOSAR is the acronym for AUTomotive Open System ARchitecture. TTAutomotive, TTTech s subsidiary for FlexRayTM solutions, has joined the AUTOSAR development partnership as a premium member. TTAutomotive will focus on FlexRay software modules that comply with AUTOSAR specifications to advance FlexRay-based Time-Triggered Architecture (TTA) in the automotive industry. The development partnership s mission is to establish an industrial standard for off-the-shelf software components, in order to provide costoptimized, best-in-class solutions to the automotive industry. The architecture is characterized by standardized, non-proprietary, and clearly defined interfaces. Slide 44

AUTOSAR FlexRay Communication Stack Task: - Provide a uniform interface to the FlexRay network - Hide protocol and message properties from the application Slide 45

Summary FlexRay is the de facto standard for high performance bus systems for the automotive market FlexRay supports both static and dynamic communication Future for car makers: the AUTOSAR initiative (supporting CAN, LIN, FlexRay) Slide 46

[FlexRay2005] References FlexRay Requirements Specification, Version 2.1, 19-dec.-2005 [FlexRay2005] FlexRay Communications System, Protocol Specification Version 2.1. Rev.A, 15-dec.-2005 [FlexRay] FlexRay Consortium home page: www.flexray.com [FlexRay-tools] [Autosar] http://www.ttautomotive.com/ http://www.autosar.org Slide 47