ETHERNET JOURNEY AT JAGUAR LAND ROVER - CHALLENGES IN THE DEVELOPMENT OF AN ETHERNET BACKBONE - Vector
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
ETHERNET JOURNEY AT JAGUAR LAND ROVER CHALLENGES IN THE DEVELOPMENT OF AN ETHERNET BACKBONE Vector Automotive Ethernet Symposium 2017 Syreeta Bath - Technical Specialist – Vehicle Communication Networks Wednesday, May 3rd, 2017 Sachin Shinde - Senior Engineer – Vehicle Communication Networks
CONTENTS
• Our Business
• Ethernet Journey
• Backbone Enabled Architecture
− Challenges
• Next Generation Architecture
− Further Challenges
2
OUR BUSINESS
• 15 vehicle lines.
• 3 UK vehicle assembly plants, 1 engineering
and manufacturing centre and 2 UK design
and engineering sites.
• 40,000 people globally – headcount has
almost doubled over the last five years.
• Plants in China, India and Brazil.
• Employs over 10,000 engineers and
designers and actively recruiting
• Sales network in 137 countries.
• Jaguar Land Rover is the largest automotive
employer in the UK.
• 201 awards won in 2016
3
ETHERNET JOURNEY WHY ETHERNET • Next Generation Infotainment concept • Network to carry Control Data, Internet, Audio and Video • Unconstrained by the network • Decouple applications from the network • Embrace consumer technology • Emergence of BroadR-Reach • Joined Open Alliance as Promoter • Use cases for Ethernet across all vehicle domains
ETHERNET JOURNEY
2012 - 2015
• Start of Ethernet Pre development for
Infotainment
• Focus on 100 Base T1 Physical Layer
and Ethernet Protocols
2012 2015
• Master controller with Broadcom
Polar Switch
• AVB 802.1 AS running in Switch
• BroadR-Reach links front to rear
• Any media any screen
In 2015 InControl TouchPro Infotainment system • Multiple HW and SW suppliers
launched to high acclaim! collaborating
5
ETHERNET JOURNEY
2015
• New electrical architecture Pre
development
2015
• FlexRay
• AutoSAR 4.x
• UTP solution for Ethernet 100Base-T1
• DoIP for Diagnostics & Software
Download
Many new technologies deployed in parallel!
6
ETHERNET JOURNEY
2017 AND BEYOND
Ethernet Backbone
Capability
2017 20xx
Development of
Dynamic Network
7
BACKBONE ENABLED ARCHITECTURE
CHALLENGES
• Challenges faced when considering Ethernet Communication within the vehicle
− Protocols to use and how to configure
− Command and Control
− Audio & Video
− VLAN Implementation within a vehicle environment
− How to configure the switch for AVB and VLANs
− Bandwidth requirements and how to control
− Diagnostics
− DoIP between Ethernet nodes
− How to capture Ethernet traffic (Port Mirroring)
− Time synchronisation
8
BACKBONE ENABLED ARCHITECTURE
CHALLENGES
JLR worked on a project with Vector to demonstrate:
• Ethernet communication compatibility
between non Infotainment domain and
Infotainment domain
• Exchange information between classic
networks and Ethernet via a Gateway
• Prove out Ethernet functionality within
AutoSAR
• AutoSAR Ethernet Stack Configuration
and Toolchain capability
• Synchronisation of data between
networks
9
BACKBONE ENABLED ARCHITECTURE
CHALLENGES
• To utilise Ethernet capability when sending data between different network types
− Configuration of triggering of container PDU’s
− Rules for Ethernet to non Ethernet communication to ensure that trade off between
gateway loading and network bandwidth is considered
10BACKBONE ENABLED ARCHITECTURE
CHALLENGES
• Communication with existing non AutoSAR
SOME/IP nodes
− Limited set of SOME/IP message types
supported in AutoSAR
− SOME/IP Configuration within ARXML
• Ethernet Start-up Timing
− Slower start-up times than seen on traditional
networks
− Configuration of switches at start-up
− Negotiation time between the nodes started
late
− No wake on LAN capability at time of
development 11BACKBONE ENABLED ARCHITECTURE
CHALLENGES
• Time synchronisation over Ethernet
using IEEE 802.1 AS
− Meeting pDelay requirement for AS
Standard
• Switch vs Host Controller
Timestamping
− Accuracy & Predictability
• Time synchronisation over CAN &
FlexRay are different domains using
one global clock each with its own
synchronisation period
• Switchover of the GrandMaster
− Not supported in AutoSAR
12BACKBONE ENABLED ARCHITECTURE
CHALLENGES
• Additional knowledge gained for configuring the switch
− VLAN Configuration – Static and runtime
− Traffic shapers and scheduler for bandwidth control
− Data Mirroring – Port based
• Switch Operating Modes
− Managed mode allows analysis and modification of special Ethernet packets e.g. PTP
− Managed mode more difficult to get working needs additional driver code/switch firmware
13BACKBONE ENABLED ARCHITECTURE
CHALLENGES
• Configuration within AutoSAR
− Configuration of Time Sync for all classic buses
− Mixed AutoSAR versions - configuration and generation of ARXML files
− Diagnostics configuration (DoIP, DHCP/AutoIP)
− Analysis of generated ARXML/FIBEX contents
• Test Tools
− Tools with FIBEX with Ethernet support minimal
− Difficult to perform manual simulation for Ethernet as compared to traditional networks
− FIBEX with AutoSAR concepts e.g. container PDU/SOMEIP
14NEXT GENERATION ARCHITECTURE
THE ROAD AHEAD
• Distributed Computer Network Programmed
as a Car
• Automotive Plug and Play requires a Service
Based Architecture
15NEXT GENERATION ARCHITECTURE
Distributed Network Programmed as a Car
• Consumer electronic gadgets have given high expectations where consumers are happy to
receive new features by a software update
• High number of static network configurations currently used imposes limitations on how new
features can be updated
− A more dynamic methodology needs to be adopted
− Complexity of features and functions are growing at a higher rate
Service Based Architecture
• Resolve the increasing vehicle variants
• Hardware & Software Re-use
• Support bandwidth increase
16NEXT GENERATION ARCHITECTURE
CHALLENGES
Shift from Static to Dynamic Network
• Collection of single busses, partly • Structured network with different speed
connected via gateways forwarding grades, access to any service from any
specific messages sub-network/bus
• Mainly sender centric transmission of • Every function represented as a service
data, only a few services offered to apps/services (in the same
• Moving of functions and ECUs process, computing platform, network, or
requires manual update of static in the cloud)
network configuration • Moving of functions and devices with
• Detailed design and configuration of automatic update of network configuration
each network variant required • Only network topology planning, all the
(complex variant handling and details shall be done automatically
software logistics)
17NEXT GENERATION ARCHITECTURE
DEMONSTRATIONS
• ConherenSE Middleware
• Automotive Plug and Play
• Described last year at the IEEE Automotive Ethernet and IP Tech Day
• Currently being demonstrated and analysed
• TSN in an SOA environment
• Currently being demonstrated and analysed
• Ultra low guaranteed latency
• Redundancy
• Network security solutions for SOA
• Currently being demonstrated and analysed
18NEXT GENERATION ARCHITECTURE
FURTHER CHALLENGES
• Distributed Computer Network Programmed as a Car
− Vehicle as a Device
• Solutions for video transfer
• Security of access to I/O
• Proving Dependability
Lots of work still to do, will not be a single step to end game, physics and availability of
technology will help decide!
19THANK YOU Syreeta Bath Jaguar Land Rover
Technical Specialist – Vehicle W/1/26 Abbey Road, Whitley
Communication Networks Coventry CV3 4LF, UK
Electrical, Electronic & Software jaguarlandrover.com
Engineering
Sachin Shinde
Senior Engineer – Vehicle
Communication Networks
Electrical, Electronic & Software
Engineering
20You can also read
