DOCSLIB.ORG

Analysis of the SAE J1708 Protocol Raine Saastamoinen

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Analysis of the SAE J1708 Protocol Raine Saastamoinen Volvo Construction Equipment AB Component Division Analysis of the SAE J1708 protocol Raine Saastamoinen Bachelor thesis report May - Juli 2008 School of Innovation Design and Engineering Mälardalen University, Västerås, Sweden Supervisor and Examiner: Johan Stärner Supervisors at company: Nils-Erik Bånkestad and Jarmo Talvén “ Engineers does’nt buy solutions they create them” LeCroy comersial 2 Abstract Component Division at Volvo Construction Equipment, develops electronic control units (ECU) to be used in entrepreneur machines. In an operating vehicle there are several ECU’s communicating with each other to make everything work as a complete. There are two main network protocols in use to solve different communication needs. One of them is using the SAE J1708 physical layer protocol in transmitting of the actual bits when exchanging information. Manufacturing of the units are made by external suppliers.Up to date, there is a lack of good tools, to verify that delivered components conforms to the J1708 specifications. WaveRunner 104 MXi, is an advanced digital oscilloscope with scripting possibilities. It has been used in this thesis work to find out, whether suitable or not to solve this problem. This thesis shows that analysis is possible and most important of all, in future potential of being a great tool for verification. 3 Acknowledgements Thanks to my supervisors Nils-Erik Bånkestad and Jarmo Talvén at VCE Component Division for professional guidance. Pushing me in the right direction when stumbeling into difficulties (especially after that important meeting the very first week). My supervisor at Mälardalen University, Johan Stärner, a friendly professional for support and important advices. Despite having summer vacation, taking time to read and comment my report. Annika Nerén and Peter Sävström for aid and patience shown in the laboratory environment. Magnus Åkesson, always giving a helping hand when needed and for having many good ideás. Also special thanks to Mikael Back, making this opportunity possible, to finish my studies at this interesting and challenging company. Toni Riutta for being a god friend with the heart at right place, I wish you all the best. A special thought to my family and belowed ones. Being there, listening, supporting, encouraging and all to help me to the finishing line. And last but not the least to all the people at location, showing that, despite all serious work dealt with, there is always room for laughter. Surrounded by a great atmosphere it has been a delightful experince to work here. Thank you all! Raine Saastamoinen 4 Contents 1 Introduction …….….….…………………………………………………….……………..6 2 Background ...……………………………………………………………….……………..6 3 Problem formulation.……………………………………………………….…………..….7 4 Thesis outline……………………………………………………………….…………..….8 5 The SAE J1708 protocol………………………………………………….…………..……8 6 TheWaveRunner 104 MXi DSO ..……………………………………….…………..…….8 6.1 WaveScan, an advanced search and analysis tool……. .………….…………..……..11 6.2 LabNotebook ..………………………………………………………………..……..12 6.3 Custom DSO…. ……………………………………………………………….……13 7 Requirements on analysis…….……………………………………………………….…..13 7.1 Voltage levels on the bus..………….………………………………………………...14 7.1.1 Bus state levels..……....………………………………………………………….14 7.1.2 Bits and voltage differences ……………………………………………………..15 7.2 Single bits………………………………………………………………………….…15 7.2.1 Verify bit time….…………………………………………………………….…..15 7.2.2 Low-to-high delay…. ……………………………………………………….…..15 7.2.3 High-to-low delay .. ….. ………………………………………….....……….…..15 7.2.4 Higher frequecies………………………………………...……………………….15 7.3 Characters……………….……………………………………………… ……….…..16 7.3.1 Interpretation………………. …………………………………… ………….…..16 7.3.2 Character time duration………………………………………….………….……16 7.4 Messages………………………….…………………………………………….……16 7.4.1 Idle state…………………………………………………………………….……16 7.4.2 Inter byte delays…………………………………………………………….……16 7.4.3 Message lengths ………………. ………………………………………….…….17 7.5 Further analysis……………………. .……………………………………….………17 7.5.1 Unknown-zone…………………..……………………………………….………17 7.5.2 Traffic load on bus………………… ………………..….….….………….. ……17 7.5.3 Count collisions………………………………………………………………….17 7.5.4 Monitor communication………………….……………………….. ……………17 7.5.5 Decode messages……………………………………………….. ………………17 8 Method ………………………………………..………. .. ………….. …………………18 8.1 Workplace simulation equipment……….……………. ………….. ………………..18 8.2 Laboratory simulation equipment……….………………. …….. …………………..18 8.3 Measurement to be done for voltage levels. ………... ….. .. …….. ………………..18 8.4 Measurement to be done for single bits .…….…….….……..... ……………………19 8.5 Measurement to be done for characters .……….……..……. ………………………20 8.6 Measurement to be done for messages..…………..………….. ……………………..20 8.7 Measurement to be done for further analysis ………. .….….……………………….20 9 Results…………………………………………………….. .……………………………..20 9.1 Analysis of results …..……………………….. ……………………………………..22 10 Future work/recommendations.. …………….. ………………....………………....……34 11 Summary and conclusions ……..………..…...…..………………………………………36 References…………………………….….…….……………..…...………..……………37 Appendix A… …….…….…….…………………………………………………………38 Technical data……..…………………………………………………………………38 Sample code………………………….….….………………………………………..39 5 1. Introduction Volvo Construction Equipment (VCE) is one of the leading manufacturers of construction machines on the world market. Wheel-, and backhoe loaders, excavators and articulated haulers are some of the products (see fig.1). This big company is divided into several divisions responsible for specific areas. One of them, Component Division has the global responsibility for developing and manufacturing powertrains and electronic systems. This thesis work is made at a department, within Component Division in Eskilstuna. In here development take place in making new hardware and software solutions for the electronic control units (ECU), used by the machines. Software is developed on both platform and application level. The hardware is devoloped together with external suppliers, which by the end makes the actual manufacturing of the ECU’s. Figure 1. Wheel-, and backhoe loaders, excavators, articulated haulers, motor graders and road machinery are products developed by VCE. 2. Background First of all, a very brief explanation to what an ECU is doing. An ECU, electronic control unit, is a small embedded computer that has specific behaviour implemented in it to take care of certain parts of a vehicle. Engine, transmission, hydraulics, cabin, instrument and so on have their own ECU’s. A real-time operating system is in use to schedule and decide on which task (a small piece of program), may execute what and when. Different tasks read sensor values, others make decisions upon that and some make actuators to react accordingly. The beaty of this is having the possibility to tune in some small specific details or change of characteristics and behaviour of a vehicle with changes in software (of cource with limitations). The trend is with increasing count of modules per vehicle. In an operating vehicle there are several ECU’s communicating with each other to make everything work as a complete. Communication between these autonomous nodes that the ECU’s represent, make the use of network protocols a necessity. There are two main protocols in use to solve different communication needs. First there is the CAN (Controller Area Network) according to J1939 standard in use for most of the data communication [8],[9]. With CAN being the primary bus, it allows critical interchange at high speeds among the connected modules. The second alternative in use is a protocol following the SAE (Society of Automotive Engineers) J1587 standard [12],[14]. A rather old standard, yet offering the advantages of a proven by use, reliable but rather slow communication service, used mainly for secondary or less urgent data exchange in the form of… • loading new software to the platform • dataset loading • on-vehicle test • diagnosis / faultcodes 6 Figure 2: The electronic system J1587 describes the application level in a protocol suite according to the OSI Model1. It defines format of the messages and data to be sent that is of general value. It describes a standard to use for... “ electronic data interchange between microcomputer systems in heavy-duty vehicle applications” [12]. This application layer protocol is to be used together with the SAE J1708 standard [13][15]. In a protocol suite, this one defines the data link-, and physical layer. 3. Problem formulation How well does the ECU’s implement the recommended practice when data interchanged? The main objective of this thesis work is to make measurements and analysis of the SAE J1708 physical layer protocol in use. Up to date there has been a lack of good supporting tools to verify such things easily.VCE having a vision, invested in an advanced digital signal oscilloscope with scripting possibilities. LeCroy’s WaveRunner 104 MXi has been used in this thesis work to find out, whether suitable or not to solve the aforementioned problem. 1 The OSI Model describes a layered, abstract description for communications and computer network protocol design 7 4. Thesis outline To solve this thesis work, a logical work flow has been identified. 1. First of all getting deeper knowledge of the SAE J1708 protocol. 2. Studying the WaveRunner 104 MXi oscilloscope with focus on sorting out different alternatives for measurement and analysis. 3. Establish a specification of requirements on what to analyse. 4. Do the required measurement needed for analysis. 5. Make analysis
Load more

Recommended publications
  • Benefits of a Standardized Diagnostic Framework
    Benefits of a standardized diagnostic framework Hareesh Prakash Development Engineer The copying, distribution and utilization of this document as well as the communication of its contents to other without expressed authorization is prohibited. Offenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or ornamental design registration. Agenda DiagnosticsDiagnostics withwith standardsstandards –– Motivation Motivation ODXODX –– ODXplorer ODXplorer MCD-3MCD-3 ServerServer –– samMCD3 samMCD3 serverserver MVCI-D-PDU-APIMVCI-D-PDU-API –– HSX HSX samtecsamtec DiagnosticDiagnostic FrameworkFramework The copying, distribution and utilization of this document as well as the communication of its contents to other without expressed authorization is prohibited. ffenders will be held liable for the payment of damages. All rights reserved in the event of the grant of a patent, utility model or ornamental design registration. Diagnostics with Standards Motivation 2000 - 2009 New ACC Stop & Go ALC + Navigation Strategies, Heading Control Night Vision Process, AFS I + II X-AGS 1990 - 1999 Internet Tools, … Telematics Navigation system Online Services CD-Changer Bluetooth Bus system Car Office ACC Adaptive Cruise Control Complexity Local Hazard Warning Complexity 1980 - 1989 Airbags Integrated Safety Systems DSC Dynamic Stability Control Electronic Transmission control Break-By-Wire Adaptive Transmission Control Electronic air conditioning control Steer-By-Wire Anti-roll ASR i-Drive Xenon Lights ABS Fuel cells 1970 - 1979 BMW Assist Telephone LH RDS/TMC 2 Electronic Fuel Injection Seat heating Lane change ssistant Emergency calls Electronic Ignition … Personalization Servotronic Check Control Software Update … Idle speed regulator Force Feedback Pedal Central lock … Costs Source: [2] Hudi; [4] Reichert The copying, distribution and utilization of this document as well as the communication of its contents to other without expressed authorization is prohibited.
    [Show full text]
  • The Problems in Fibre Optic Communication in the Communication Systems of Vehicles
    TEKA Kom. Mot. i Energ. Roln. – OL PAN, 2011, 11, 363–372 THE PROBLEMS IN FIBRE OPTIC COMMUNICATION IN THE COMMUNICATION SYSTEMS OF VEHICLES Sumorek Andrzej, Buczaj Marcin Department of Computer and Electrical Engineering, Lublin University of Technology, Poland Summary. The diversifi cation of technical solutions occurred as a result of almost thirty years of evolution of the communication systems between the mechatronic systems in motor vehicles. The vehicles are equipped with the conventional cable connections between the switches and actuators as well as with advanced data exchange networks. These networks show more and more similarities to computer networks. They are the new solutions; even their classifi cation has been created a few years ago (class D). Therefore the personnel engaged in the scope of functional programming and vehicles servicing encounter the problems associated with networks operation. The purpose of the article is to present the principles of functioning of the basic networks with the medium in the form of an optical fi bre. Particular emphasis has been placed on the detection of failures consisting in the damage of communication node and optical fi bre. Key words: Media Oriented Systems Transport, Domestic Digital Bus. INTRODUCTION The systematics associated with networks classifi cation presented in the year 1994 contained 3 types of networks. Such systematics was also presented in 2007 in literature in 2007 [12]. This approach has been established as a result of the standardization introduced by SAE J1850 [5, 10]. Three classes of communication systems have been specifi ed in SAE J1850. The applications group associated with bus throughput is used as the criterion of subdivision.
    [Show full text]
  • SAE J1587 (2002 Standard).Pdf
    SURFACE REV. VEHICLE J1587 FEB2002 RECOMMENDED Issued 1988-01 400 Commonwealth Drive, Warrendale, PA 15096-0001 PRACTICE Revised 2002-02 Superseding J1587 JUL1998 Electronic Data Interchange Between Microcomputer Systems in Heavy-Duty Vehicle Applications 1. Scope—This SAE Recommended Practice defines a document for the format of messages and data that is of general value to modules on the data communications link. Included are field descriptions, size, scale, internal data representation, and position within a message. This document also describes guidelines for the frequency of and circumstances in which messages are transmitted. In order to promote compatibility among all aspects of electronic data used in heavy-duty applications, it is the intention of the SAE Truck and Bus Low Speed Communications Network Subcommittee (formerly Data Format Subcommittee) (in conjunction with other industry groups) to develop recommended message formats for: a. Vehicle and Component Information—This includes all information that pertains to the operation of the vehicle and its components (such as performance, maintenance, and diagnostic data). b. Routing and Scheduling Information—Information related to the planned or actual route of the vehicle. It includes current vehicle location (for example, geographical coordinates) and estimated time of arrival. c. Driver Information—Information related to driver activity. Includes driver identification, logs, (for example, DOT), driver expenses, performance, status, and payroll data. d. Freight Information—Provides data associated with cargo being shipped, picked up, or delivered. Includes freight status, overage, shortage and damage reporting, billing and invoice information as well as customer and consignee data. This document represents the recommended formats for basic vehicle and component identification and performance data.
    [Show full text]
  • Body Builder Connectors, Schematic
    BODY BUILDER INSTRUCTIONS Mack Trucks Electrical Wiring and Connections CHU, CXU, GU, TD, MRU, LR Section 3 Introduction This information provides design and function, specification and procedure details for Electrical Wiring and Connections for MACK vehicles. Note: For information on mDrive PTO installation and wiring see Section 9 PTO Installation, mDrive. Note: For information on PTO parameter programming see Section 9 PTO Parameter Programming. Unless stated otherwise, following a recommendation listed in this manual does not automatically guarantee compliance with applicable government regulations. Compliance with applicable government regulations is your responsibility as the party making the additions/modifications. Please be advised that the MACK Trucks, Inc. vehicle warranty does not apply to any MACK vehicle that has been modified in any way, which in MACK's judgment might affect the vehicles stability or reliability. Contents • “Abbreviations”, page 3 • “General Wiring Definitions”, page 4 • “Routing and Clipping Guidelines”, page 5 • “Body Builder Connectors, Schematic Examples”, page 17 • “Remote Start n Stop”, page 23 • “Remote Engine Stop”, page 24 • “Adding Auxiliary Accelerator Pedal”, page 25 • “BodyLink III”, page 26 • “Auxiliary Switch Locations (Cab)”, page 30 • “Power Connections”, page 31 • “Control Link II”, page 37 • “LR Workbrake”, page 50 Mack Body Builder Instructions CHU, CXU, GU, TD, MRU, LR USA139448393 Date 9.2017 Page 1 (94) All Rights Reserved • “Wiring J1939”, page 52 • “9-pin Diagnostic Connector”,
    [Show full text]
  • Study of an Error in Engine ECU Data Collected for In-Use Emissions Testing and Development and Evaluation of a Corrective Procedure
    Graduate Theses, Dissertations, and Problem Reports 2007 Study of an error in engine ECU data collected for in-use emissions testing and development and evaluation of a corrective procedure Petr Sindler West Virginia University Follow this and additional works at: https://researchrepository.wvu.edu/etd Recommended Citation Sindler, Petr, "Study of an error in engine ECU data collected for in-use emissions testing and development and evaluation of a corrective procedure" (2007). Graduate Theses, Dissertations, and Problem Reports. 1840. https://researchrepository.wvu.edu/etd/1840 This Thesis is protected by copyright and/or related rights. It has been brought to you by the The Research Repository @ WVU with permission from the rights-holder(s). You are free to use this Thesis in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you must obtain permission from the rights-holder(s) directly, unless additional rights are indicated by a Creative Commons license in the record and/ or on the work itself. This Thesis has been accepted for inclusion in WVU Graduate Theses, Dissertations, and Problem Reports collection by an authorized administrator of The Research Repository @ WVU. For more information, please contact [email protected]. Study of an Error in Engine ECU Data Collected for In-Use Emissions Testing and Development and Evaluation of a Corrective Procedure Petr Sindler Thesis submitted to the College of Engineering and Mineral Resources at West Virginia University in partial fulfillment of the requirements for the degree of Master of Science in Mechanical Engineering Mridul Gautam, Ph.D., Chair Gregory J.
    [Show full text]
  • SAE International® PROGRESS in TECHNOLOGY SERIES Downloaded from SAE International by Eric Anderson, Thursday, September 10, 2015
    Downloaded from SAE International by Eric Anderson, Thursday, September 10, 2015 Connectivity and the Mobility Industry Edited by Dr. Andrew Brown, Jr. SAE International® PROGRESS IN TECHNOLOGY SERIES Downloaded from SAE International by Eric Anderson, Thursday, September 10, 2015 Connectivity and the Mobility Industry Downloaded from SAE International by Eric Anderson, Thursday, September 10, 2015 Other SAE books of interest: Green Technologies and the Mobility Industry By Dr. Andrew Brown, Jr. (Product Code: PT-146) Active Safety and the Mobility Industry By Dr. Andrew Brown, Jr. (Product Code: PT-147) Automotive 2030 – North America By Bruce Morey (Product Code: T-127) Multiplexed Networks for Embedded Systems By Dominique Paret (Product Code: R-385) For more information or to order a book, contact SAE International at 400 Commonwealth Drive, Warrendale, PA 15096-0001, USA phone 877-606-7323 (U.S. and Canada) or 724-776-4970 (outside U.S. and Canada); fax 724-776-0790; e-mail [email protected]; website http://store.sae.org. Downloaded from SAE International by Eric Anderson, Thursday, September 10, 2015 Connectivity and the Mobility Industry By Dr. Andrew Brown, Jr. Warrendale, Pennsylvania, USA Copyright © 2011 SAE International. eISBN: 978-0-7680-7461-1 Downloaded from SAE International by Eric Anderson, Thursday, September 10, 2015 400 Commonwealth Drive Warrendale, PA 15096-0001 USA E-mail: [email protected] Phone: 877-606-7323 (inside USA and Canada) 724-776-4970 (outside USA) Fax: 724-776-0790 Copyright © 2011 SAE International. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, distributed, or transmitted, in any form or by any means without the prior written permission of SAE.
    [Show full text]
  • Efficiently Triggering, Debugging and Decoding Low-Speed Serial Buses
    Efficiently Triggering, Debugging and Decoding Low-Speed Serial Buses Hello, my name is Jerry Mark, I am a Product Marketing Engineer at Tektronix. The following presentation discusses aspects of embedded design techniques for “Efficiently Triggering, Debugging, and Decoding Low-Speed Serial Buses”. 1 Agenda Introduction – Parallel Interconnects – Transition from Parallel to Serial Buses – High-Speed versus Low-Speed Serial Data Buses Low-Speed Serial Data Buses – Challenges – Technology Reviews – Measurement Solutions Summary 2 In this presentation we will begin by taking a glance at the transition from parallel-to-serial data and the challenges this presents to engineers. Then we will briefly review some of the most widely used low-speed serial buses in industry today and some of their key characteristics. We will turn our attention to the key measurements on these buses. Subsequently, we will present by example how the low-speed serial solution from Tektronix addresses these challenges. 2 Parallel Interconnects Traditional way to connect digital devices used parallel buses Advantages – Simple point-to-point connections – All signals are transmitted in parallel, simultaneously – Easy to capture state of bus (if you have enough channels!) – Decoding the bus is relatively easy Disadvantages – Occupies a lot of circuit board space – All high-speed connections must be the same length – Many connections limit reliability – Connectors may be very large 3 Parallel buses present all of the bits in parallel, as shown in the logic analyzer display. A parallel connection between two ICs can be as simple as point-to-point circuit board traces for each of the data lines. If you can physically probe these lines, it is easy to display the bus state on a logic analyzer or mixed signal oscilloscope.
    [Show full text]
  • Fieldbus Communication: Industry Requirements and Future Projection
    MÄLARDALEN UNIVERSITY SCHOOL OF INNOVATION, DESIGN AND ENGINEERING VÄSTERÅS, SWEDEN Thesis for the Degree of Bachelor of Science in Engineering - Computer Network Engineering | 15.0 hp | DVA333 FIELDBUS COMMUNICATION: INDUSTRY REQUIREMENTS AND FUTURE PROJECTION Erik Viking Niklasson [email protected] Examiner: Mats Björkman Mälardalen University, Västerås, Sweden Supervisor: Elisabeth Uhlemann Mälardalen University, Västerås, Sweden 2019-09-04 Erik Viking Niklasson Fieldbus Communication: Industry Requirements and Future Projection Abstract Fieldbuses are defined as a family of communication media specified for industrial applications. They usually interconnect embedded systems. Embedded systems exist everywhere in the modern world, they are included in simple personal technology as well as the most advanced spaceships. They aid in producing a specific task, often with the purpose to generate a greater system functionality. These kinds of implementations put high demands on the communication media. For a medium to be applicable for use in embedded systems, it has to reach certain requirements. Systems in industry practice react on real-time events or depend on consistent timing. All kinds are time sensitive in their way. Failing to complete a task could lead to irritation in slow monitoring tasks, or catastrophic events in failing nuclear reactors. Fieldbuses are optimized for this usage. This thesis aims to research fieldbus theory and connect it to industry practice. Through interviews, requirements put on industry are explored and utilization of specific types of fieldbuses assessed. Based on the interviews, guidelines are put forward into what fieldbus techniques are relevant to study in preparation for future work in the field. A discussion is held, analysing trends in, and synergy between, state of the art and the state of practice.
    [Show full text]
  • CAN-To-Flexray Gateways and Configuration Tools
    CAN-to-Flexray gateways Device and confi guration tools lexray and CAN net- Listing bus data traffic toring channels it is possi- power management func- Fworks will coexists in (tracing) ble to compare timing rela- tionality offers configurable the next generation or pas- Graphic and text displays tionships and identify timing sleep, wake-up conditions, senger cars. Flexray orig- of signal values problems. and hold times. The data inally designed for x-by- Interactive sending of GTI has developed a manipulation functionality wire applications gains mar- pre-defined PDUs und gateway, which provides has been extended in or- ket acceptance particular- frames two CAN and two Flexray der to enable the user to ap- ly in driver assistance sys- Statistics on nodes and ports. It is based on the ply a specific manipulation tems. Nevertheless, Flexray messages with the Clus- MPC5554 micro-controller. function several times. Also applications need informa- ter Monitor The gateway is intended to available for TTXConnexion tion already available in ex- Logging messages for be used for diagnostic pur- is the PC tool TTXAnalyze, isting CAN in-vehicle net- later replay or offline poses, generating start-up/ which allows simultaneous works. Therefore, CAN-to- evaluation sync frames, and it can be viewing of traffic, carried on Flexray gateways are nec- Display of cycle multi- used with existing software the various bus systems. essary. Besides deeply em- plexing, in-cycle rep- tools. The Flexray/CAN bedded micro-controller etition and PDUs in the The TTXConnexion by gateway by Ixxat is a with CAN and Flexray inter- analysis windows TTControl is a gateway tool configurable PC application faces, there is also a need Agilent also provides an combining data manipula- allowing Flexray messag- for gateway devices as in- analyzing tool for Flexray tion, on-line viewing, and es and signals to be trans- terface modules for system and CAN.
    [Show full text]
  • Table of Contents
    Table of Contents Chapter 1 Bus Decode -------------------------------------------------------------- 1 Basic operation --------------------------------------------------------------------------------------------- 1 Add a Bus Decode ----------------------------------------------------------------------------------------------------- 1 Advance channel setting ---------------------------------------------------------------------------------------------- 2 Specially Bus Decode: ------------------------------------------------------------------------------------------------ 4 1-Wire ------------------------------------------------------------------------------------------------------------------- 7 3-Wire ------------------------------------------------------------------------------------------------------------------- 9 7-Segment -------------------------------------------------------------------------------------------------------------- 11 A/D Converter--------------------------------------------------------------------------------------------------------- 14 AcceleroMeter -------------------------------------------------------------------------------------------------------- 17 AD-Mux Flash -------------------------------------------------------------------------------------------------------- 19 Advanced Platform Management Link (APML) ---------------------------------------------------------------- 21 BiSS-C------------------------------------------------------------------------------------------------------------------ 23 BSD ---------------------------------------------------------------------------------------------------------------------
    [Show full text]
  • The Path to Robust Automotive Networking
    The Path to Robust Automotive Networking www.infineon.com/automotive-networking 2 Content Introduction 4 Products Overview 7 Automotive Transceivers 8 System Basis Chips (SBCs) 12 Infineon® Embedded Power ICs 18 Microcontrollers 25 Support Tools 28 System Basis Chips (SBCs) 28 Infineon® Embedded Power ICs 29 Microcontrollers 30 Packages Overview 32 3 Introduction Automotive Networking Automotive networking technology is evolving fast, driven World leader in automotive electronics for over 40 years, by a number of key trends. With an ever-increasing num- we actively engage with many industry, standardization ber of cars on the road and rising fuel costs, demands and research organizations to drive in-vehicle network- for energy efficiency are growing. Worldwide legislation ing innovations capable of meeting today’s demands for is establishing ever-stricter caps on CO2 emissions. The energy efficiency, safety, smooth interfacing and complex- spotlight is also on functional safety. With the ISO 26262 ity management. Our broad portfolio extends from stand- automotive standard increasingly moving into applications alone transceivers through system basis chips to embed- that were not typically safety-relevant, the bar is moving ded power solutions for CAN, LIN and FlexRay protocols. upwards and we are seeing increasingly granular system We also offer microcontrollers with enhanced communica- safety concepts. At the same time, complexity is on the tion capabilities to support multiple protocols. All of our increase. Growing consumer expectations are fuelling new products are designed to deliver the exceptional levels of comfort and safety features also in low-end segments, and ESD and EMC performance required in automotive environ- this, in turn, is placing pressure on semiconductor manu- ments.
    [Show full text]
  • Chapter 1 Introduction ------6
    Table Chapter 1 Introduction ------------------------------------------------------------- 6 1.1 Acute Logic Analyzers ------------------------------------------------------------------------ 7 1.2 Packing Lists ------------------------------------------------------------------------------------ 8 1.3 Specifications ----------------------------------------------------------------------------------11 1.4 System Requirement --------------------------------------------------------------------------14 Chapter 2 Installation ------------------------------------------------------------- 15 2.1 Hardware ----------------------------------------------------------------------------------------16 2.2 Software -----------------------------------------------------------------------------------------18 2.3 Driver --------------------------------------------------------------------------------------------19 2.4 Accessories -------------------------------------------------------------------------------------20 2.5 Questions ---------------------------------------------------------------------------------------21 Chapter 3 Operations ------------------------------------------------------------- 22 3.1 Window -----------------------------------------------------------------------------------------23 3.1.1 Timing Analysis --------------------------------------------------------------------------------------------- 23 3.1.2 State Analysis ------------------------------------------------------------------------------------------------ 24 3.1.3 Mark the invalid
    [Show full text]