SLIDE 1 Keynote
The role of CAN in the age of Industrial Ethernet and IoT
16th International CAN Conference Nuremberg Christian Schlegel, Managing Director, HMS Technology Center Ravensburg
chsc@hms-networks.de
2017-03-07
SLIDE 2
Looking back into history … When CAN was born
SLIDE 3
Looking back into history … When CAN was born The 80‘s
A decade of fast evolving and spreading technolgy Personal Computer Wearables (Walkman) Mobile Phones
SLIDE 4
Looking back into history … When CAN was born The 80‘s
A decade of fast evolving and spreading technolgy Cars (Automotive) Automation
SLIDE 5 Looking back into history … When CAN was born
RS232 RS485
Serial interfaces Limited in
- bandwidth
- functionality
- no. of
devices
New fieldbus technology
principle
- considerably increased wire
speed
- more features (e.g. device
management)
- master/slave communication
principle
Automation
SLIDE 6
Looking back into history … When CAN was born
Cars (Automotive)
SLIDE 7 Looking back into history … When CAN was born
Situation inside cars
- More chaotic communication
structure
- Electric world is not as stable
and „clean“ as in the automation world
Automation communication technology not applicable in cars
Steering Wheel
Cruise control, wiper, turning light Optional: climate control, radio, telephone
Roof
rain sensor, light sensor, light control, sun roof
Seat
Seat positon motors,
control panel
Door
Mirror, central (ECU), mirror switch, window lift, seat control switch, door lock
Engine
Sensors, small motors
Climate
Small motors, control panel
Cars (Automotive)
SLIDE 8
Looking back into history … When CAN was born 1983
Bosch started the development of a new serial communication system
1986
„Controller Area Network“ was introduced at SAE congress
1987
First CAN controller chip 82526 (FullCAN) introduced by Intel, shortly after 82C200 (BasicCAN) from Philips Semiconductor
SLIDE 9 Ingenious features made CAN different
Bus access & arbitration principle CSMA/CA => Avoids collisions and prioritizes messages Error signaling and recovery mechanism => Ensures data consistency
Physical Layer - representation of 1s and 0s on bus line => Makes CAN rather immune to electromagnetic and common mode interferences
SLIDE 10
CAN and its way into industrial (non-automotive) applications
SLIDE 11
CAN and its way into industrial applications 1991
Mercedes S class first car with CAN
Late 80‘s and early 90‘s
The „classic“ fieldbus systems were introduced by the large automation companies for industrial automation applications
Late 80‘s and early 90‘s
Small companies started promoting CAN for industrial applications
I+ME
SLIDE 12
CAN and its way into industrial applications
Example of first non-automotive / industrial applications by STZP
SLIDE 13
CAN and its way into industrial applications
Need for CAN infrastructure components
PC/CAN interface board (ISA-bus) with 82527 & 82C200 developed by STZP First CAN repeater presented by STZP at INTERKAMA fair in Dusseldorf in 1992
SLIDE 14
CAN and its way into industrial applications 1992
Founding of CAN in Automation
1992
CAN Application Layer (CAL)
1994
CANopen CIA301
Today
CiA maintains and still develops most comprehensive set of standards for applications and device profiles
SLIDE 15
- Using
- Higher layer protocols
- Device profiles
- Application profiles
- Various higher layer protocols exist
- CANopen
- DeviceNet
- J1939
- NMEA2000
- ISOBUS
- …
- Manufacturer specific catalog
specifying for each data (called signal)
- Transmitting ECU
- Receiving ECUs
- Frequency
- Message (ID)
- Position in Message
- Additional common definitions came
later, e.g. in AUTOSAR for diagnostic purposes
Data modeling with CAN
Industrial / non-automotive Automotive / Cars
SLIDE 16
Ethernet – A thread for CAN ?
SLIDE 17 Ethernet – A threat for CAN ?
History of Industrial Ethernet
1999 2001 2003 2004 2006
Foundation
EtherNet/IP Powerlink V1 Profinet EtherCAT SERCOS III Powerlink V2
SLIDE 18
Ethernet – A threat for CAN ?
Why Ethernet for industrial data communication ?
Cheap components Large network extension Fast data transmission Large data frames High bandwidth Number of nodes unlimited
SLIDE 19 Ethernet – A threat for CAN ?
Why Ethernet for industrial data communication ?
Especially of interest
Interconnection
Factory Automation Cheap components Large network extension Fast data transmission Large data frames High bandwidth Number of nodes unlimited
SLIDE 20
Ethernet – A threat for CAN ?
Industrial Ethernet for all applications / markets?
Power and Energy
Trucks, utility vehicles & farming machines
Automotive & recreational vehicles Ships & Boats
“Small” Machines Oil & Gas (subsea)
Small Robots Medical & Laboratory Automation Building Automation Measurement Systems
SLIDE 21 Ethernet – A threat for CAN ?
Arguments for staying with CAN?
Robustness Real „bus“ system Short data packages Monitoring & Trouble shooting Power Consumption Price Disadvantage: maximum network extension
Conclusion: CAN still has his eligibility, especially when these requirements are important
- power consumption
- up-time (MTBF)
- diagnostic & maintenance
capabilities
SLIDE 22
CAN FD – The booster for CAN and its future
SLIDE 23 CAN FD – The booster for CAN
Obstacles for CAN
- Max 8 data bytes / message
- Bandwidth limitations - also
dependent on network extension Workarounds
- More CAN networks
- Other networks with similar
working principles (e.g. FlexRay) Improvements by CAN FD
- Up to 64 data bytes / message
- Increase of transmission speed
after arbitration phase up to 8 Mbit/s
- Longer network extension at
higher transmission speed
capabilities => reduced residual error propability
SLIDE 24 Future of CAN / CAN FD in automotive applications
Ethernet in cars
More bandwidth required for
- Driving assistance and security
- Camera systems – surround view
- Infotainment
=> Ethernet was introduced in last decade Special requirements need specific technical solutions
(=> BroadR-Reach)
- Synchronization & guaranteed
latency times (=> AVB, TSN in the future)
SLIDE 25 Future of CAN / CAN FD in automotive applications
New communication methods and protocols have been introduced
New mechanisms in AUTOSAR …
- Intelligent PDU multiplexing
(IPDU)
- Secure on-board communication
(SECOC)
- End-to-end protection profile
(E2E) … lead to new requirements
- More data to be transmitted
(larger messages)
- Authentication mechanisms for
securing safety-critical data
SLIDE 26 Future of CAN / CAN FD in automotive applications
Will Ethernet replace CAN in cars?
Definitely NOT (within next 10 yrs)
(cost for Ethernet Interface = 6x cost for CAN interface)
- Ethernet is only point-to-point
(restricts topology, requires switches where unused ports are unnecessary cost)
- Use of powerful CPUs with MII
interface for simple ECUs like in doors is not acceptable Outlook for CAN FD
- CAN FD will be the bridge
between “classic” CAN and Ethernet
- Most cost effective solution
- Well-known by everyone at the
car manufacturers
- CAN FD in next car generations
- f all German car manufacturers
(will not replace CAN completely)
SLIDE 27 Future of CAN / CAN FD in non-automotive applications
When is CAN the preferred network solution?
Benefits of CAN / CAN FD …
- Cost structure
- Flexibility
- Ease of use
- Low power consumption
… makes it the perfect solution for
- Smaller machines (applications
with limited network extension)
- Extension or sub-systems to
larger machines
- All mobile applications (especially
when battery powered)
SLIDE 28 Future of CAN / CAN FD in non-automotive applications
When is CAN the preferred network solution?
CAN FD even provides
- Higher bandwidth (four times and more)
- Shorter transmission times
- Longer network extensions at higher transmission speed
- Larger messages
However: still waiting for suitable CPUs with CAN FD => Makes CAN FD suitable for even more applications
SLIDE 29
CAN and the Internet of Things
SLIDE 30 CAN and the Internet of Things
What is the Internet of Things (IoT)?
IoT = Ethernet from IT down to the sensor level IoT = Integration of automation networks with IT networks & cloud services Main use-cases
- Improving diagnostics, maintenance and
management capabilities
- Optimizing production and making
production more flexible
- Communication between cars, cars and
infrastructure and cars and humans
SLIDE 31 CAN and the Internet of Things
What is the Internet of Things (IoT)?
IoT related data Automation & control data
- Detailed diagnostic data
- Larger data packages
- Transmitted less
frequently
- Short data
- Transmitted frequently
- Real-time (defined
latency)
SLIDE 32 CAN and the Internet of Things
IoT related technologies
TSN (Time Sensitive Networking) OPC UA
- Extends Standard Ethernet
(802.1) with real-time capabilities
microsecond
performance concerning the implementation
with semantics for each data point
mechanisms like authentication and encryption
SLIDE 33 CAN and the Internet of Things
IoT down to field level?
Field level properties
- Automation & control data
- Cost sensitive
- Reliability
- Maintainability
Ethernet not always suitable CAN as the preferred solution But
- Also extended diagnostic data
shall be gathered from field level CAN not suitable (8 byte limitation) CAN FD solves the problem
SLIDE 34 CAN and the Internet of Things
IoT architecture with CAN FD
Machine 1 Machine 2 Ethernet Ethernet
& TSN
CAN FD
inside a machine for IoT related applications
control data
- In parallel also IoT related
data
several Industrial Ethernet protocols => Overall cost-savings
SLIDE 35
Conclusion
SLIDE 36
Conclusion
Will Ethernet become the only communication system used for automation and control purposes ? CAN FD comes exactly at the right time to make CAN fit for the future CAN / CAN FD remains unbeatable when it comes to cost level, ease-of-use, reliability, flexibility CAN FD is a perfect sub-network inside machines for IoT related applications
SLIDE 37
Thanks for listening!
www.hms-networks.com