DOCSLIB.ORG

Automotive Gateways Bridge & Gateway from Flexray/CAN/LIN to AVB Networks

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Automotive Gateways Bridge & Gateway from Flexray/CAN/LIN to AVB Networks Automotive Gateways Bridge & Gateway from FlexRay/CAN/LIN to AVB Networks [email protected] 1 Content Gateways in current/future architectures Main GW functions (Routing, Diagnostic, …) Main principles of GW’s functionality (SW aspects, protocol aspects, AUTOSAR aspects) LIN/CAN/FlexRay 2 Ethernet transport mechanisms (1722a) GW performance aspects Ethernet GW/Switch in future EE architectures Gateways in current/future architectures 3 Transition from Central Gateway to Backbone Arch CAN (FD) LIN FlexRay CGW MOST Ethernet Central CGW Gateway Domain DCU Control Unit Switch Today SW CGW SW SW SW Mid-term DCU DCU DCU SW SW Long-term Characteristics of different GW types* No. of interfaces No. of GWs Diagnostic Comments per vehicle interface Central GW any no. of <= 1 x Increasing LIN/CAN/FR no. of itfs. Local GW 1 x domain bus itf. >= 0 - n x subdomain bus itfs. Domain GW 1 x domain bus itf. >= 0 possible 1-2 x backbone itf. GW with any no. of >= 0 possible integrated LIN/CAN/FR/Eth Switch * From the EE architecture point of view Main GW functions (Routing, Diagnostic, …) 6 Routing Features • Message Routing • Packet Routing • Signal Routing (eventually with signal processing) • Routing with High Priority • Different sorts of rate adaption between received and transmitted message, e.g. Periodic & Immediate Transmit On Change (TOC) New Msg Data SOURCE t tCycle_S TOC Msg DESTINATION t tGDelay • Y Routing tCycle_D • Diagnostic Routing 7 Other Gateway Functions • Nominal-actual configuration comparison ECU_2 ECU_3 ECU_4 Components ECU_1 • Diagnostic tester …… Configuration – CAN and Ethernet interface provided Nominal 1 1 0 1 … Actual 1 0 0 1 … • Flash function • Message mirroring on diagnostic bus • Network management • OEM specific features 8 Main principles of GW’s functionality (SW aspects, protocol aspects, AUTOSAR aspects) 9 State of the Art: Software Gateway in Central Processing Unit (CPU) Application Software Application Security SoftwareSignal Signal GatewaySDU Gateway GatewayTunnel GatewayTransport L3/4 SDU Gateway CPU Security Memory I-PDUs (Software) (Hardware) CPU Bus queue Input schedule Output Queues … Queues CC 1..n NIC CC 1..n Transpor De-capsulation, t Encapsulation CPU L2 Software Ethernet MAC PDUs ECU Bus/Interfaces Bridge Security MACSec bus RBUF TBUF … schedule CC Automotive Ethernet CC HardwareHardware ECU Bus Source: ETAS Gateway Protocol Stack Overview Sensor/Actuato Gateway ECU r Actuator/Senso r APP APP SIGNAL GW APP APP Signal Signal Signal IL IL SDU GW IL TP TP L3TP GW TP Phy CAN CAN FLX FLX Phy Phy Phy Phy external cabling domain CAN Bus FlexRay Bus Discrete Sensor Gateway Actuator Actuator Senso ECU ECU r Actuator Sensor Source: ETAS CAN Bus FlexRay Bus Notes: IL = Interaction Layer according OSEK Comms 3.03 and AUTOSAR; adopts 11 messages/signals to PDUs AUTOSAR Aspects … App 1 App n Signal Process Signal GW Frame GW Internet Protocol • Message Routing performed in the PDU Router • Signal Routing performed in AUTOSAR COM • Signal Processing performed in Apps 12 LIN/CAN/FlexRay 2 Ethernet transport mechanisms (1722a) Gateway Protocol Stack with 1722 Tunneling Sensor Gateway ECU/Gateway Sensor APP SIGNAL GW APP Signal Signal Signal IL IL SDU GW IL TP TP L3TP GW TP CAN CAN CAN* CAN* Phy Phy P1722 TUNNEL GW P1722 MACL2TP-Relay GW 802.1Q x 802.1Q x 802.3 802.3802.1Q x802.3 802.3 MAC MAC MAC MAC PHY PHY PHY PHY internal external cabling domain CAN Bus Ethernet Ethernet Gateway Gateway Gateway Sens Actuato Sens Actuato or r or r Actuato Sensr ECU ECU ECU or Actuato Sens Actuato Sens r or r or Source: ETAS CAN Bus FlexRay Bus 1722a Ctrl Stream Data Generic Frame Format Ethernet header AVTP control stream data header Packet info LIN/CAN/FR message 1* … LIN/CAN/FR message n* * only messages of the same type allowed in one frame 1722a FlexRay PDU Format The FlexRay PDU consists of a control stream PDU and one or more FlexRay messages Source: IEEE 1722a/D3 1722a CAN PDU Format The CAN extended PDU consists of a control stream PDU and one or more CAN extended messages Source: IEEE 1722a/D3 1722a LIN PDU Format The LIN PDU consists of a control stream PDU and one or more LIN messages Source: IEEE 1722a/D3 ETAS Contribution to IEEE 1722a LIN/CAN/FR PDU Format Optimized Gateway Messages: The transport PDU consists of a control stream PDU and one or more LIN, CAN, FR messages Source: ETAS GW performance aspects GW performance aspects The routing performance should allow all messages received on several buses with 100% load to be loss-free transmitted on the destination interfaces (which are considered to be in ideal condition) Latency time requirements are strongly OEM specific, e.g.: OEM1: tlatency < 2 ms OEM2: tlatency < 500 µs Toyota’s ultra low latency: 100µs over 5 hops, i.e. 20µs/hop GW Msg Msg Msg Network RC TX Network A Buffer Buffer B tnetwork tlatency tnetwork t Delay Transmission Delay Operation Delay Transmission Startup time (time needed to start communication) Automotive Gateways Ethernet GW/Switch in future EE architectures Ethernet GW/Switch in future EE architectures CAN (FD) LIN Daisy Chain with FlexRay optional DCU DCU DCU SW redundant path Ethernet Central CGW Gateway Domain DCU Control Unit SW Switch Switched Architecture CGW inspired DCU DCU DCU DCU DCU SW SW DCU DCU Full Meshed redundant Backbone Gateway as possible Time Master •TBD hope to get the permission from an OEM to insert a slide Page <#> 24 Gateway as convergence device GW DCUR Converged data SMR Converged data GW1 GW2 AFS SML TRM BCMR BCMF GW DCUL Legende: Zone oriented architecture makes use of Ethernet Video camera backbone (which connects all main areas of the vehicle) GWx Gateway + Switch XYZ ECU Inside the zone CAN/LIN networks Ethernet Ethernet AVB ensures data type convergence on CAN (FD) backbone Thank you! [email protected] .
Load more

Recommended publications
  • Internationally Standardized As Part of the Train Communication Network (TCN) Applied in Light Rail Vehicles Including Metros, T
    September 2012 CANopen on track Consist network applications and subsystems Internationally standardized as part of the train communication network (TCN) Applied in light rail vehicles including metros, trams, and commuter trains www.can-cia.org International standard for CANopen in rail vehicles IEC 61375 standards In June 2012, the international electro technical commission (IEC) has en- hanced the existing and well-established standard for train communication X IEC 61375-1 systems (TCN; IEC 61375), by the CANopen Consist Network. IEC 61375-3-3 Electronic railway equipment - Train VSHFLÀHVWKHGDWDFRPPXQLFDWLRQEDVHGRQ&$1RSHQLQVLGHDVLQJOHUDLO communication network vehicle or a consist in which several rail vehicles share the same vehicle bus. (TCN) - Part 1: General In general, the lower communication layers as well as the application layer are IEC 61375-3-3 IEC architecture based on the well-proven standards for CAN (ISO 11898-1/-2) and CANopen (1 7KLVDOORZVRQWKHRQHKDQGSURÀWLQJIURPWKHDYDLODEOH&$1 X IEC 61375-2-1 Electronic railway WRROVRQWKHPDUNHW2QWKHRWKHUKDQGLWLVSRVVLEOHWREHQHÀWIURPWKHEURDG equipment - Train UDQJHRIDYDLODEOH&$1RSHQSURWRFROVWDFNV&$1RSHQFRQÀJXUDWLRQDQG communication network diagnostic tools as well as off-the-shelf devices (see CANopen product guide (TCN) - Part 2-1: Wire train DWZZZFLDSURGXFWJXLGHVRUJ :HOOGHÀQHGFRPPXQLFDWLRQLQWHUIDFHVZLOO bus (WTB) therefore simplify system design and maintenance. X IEC 61375-2-2 ,QDGGLWLRQWRHQKDQFHGORZHUOD\HUGHÀQLWLRQV VXFKDVHJ&$1,GHQ- Electronic railway WLÀHUIRUPDWW\SHRIFRQQHFWRUGHIDXOWELWUDWHHWF
    [Show full text]
  • 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]
  • UCC 1 USB-CAN CONVERTER Contents
    Owner’s Manual UCC 1 USB-CAN CONVERTER Contents 1. Description....................................................................................................................... 17 2. Controls and Connections................................................................................................ 18 3. Installation ....................................................................................................................... 19 3.1 Unpacking.................................................................................................................... 19 3.2 Rack-Mounting............................................................................................................ 19 4. Initial Operation............................................................................................................... 20 4.1 PC Connection and CAN Driver Installation .............................................................. 20 4.2 Installing IRIS.............................................................................................................. 20 4.3 CAN-Bus Connection.................................................................................................. 20 4.4 ISOLATED / GROUNDED Switch ............................................................................ 22 5. Monitor Bus..................................................................................................................... 23 6. Technical Information....................................................................................................
    [Show full text]
  • LK9893 Developed for Product Code LK7629 - CAN Bus Systems and Operation
    Page 1 CAN bus systems and operation Copyright 2009 Matrix Technology Solutions Limited Page 2 Contents CAN bus systems and operation Introduction 3 Overview 5 Building Node A 6 Building Node B 7 Building Node C 8 Building Node D 9 Building the Scan/Fuse Node 10 Wiring It All Up 11 Worksheet 1 - The Startup Routine 12 Worksheet 2 - Seeing the Messages 13 Worksheet 3 - Receiving Messages 15 Worksheet 4 - System Monitoring and ‘Pinging’ 16 Worksheet 5 - System Faults 17 Worksheet 6 - Circuit Faults 19 Worksheet 7 - Fault Diagnosis Using Charts 20 Worksheet 8 - Build Your Own Vehicle! 21 Instructor Guide 22 Scheme of Work 26 Message Code Summary 32 Kvaser Analyser Set Up 33 Programming the MIAC 34 System Graphics 35 About this document: Code: LK9893 Developed for product code LK7629 - CAN bus systems and operation Date Release notes Release version 01 01 2010 First version released LK9893-80-1 revision 1 10 06 2010 MIAC programming notes included LK8392-80-1 revision 2 01 10 2012 Programming notes revised LK9893-80-3 25 09 2013 Warning that some faults require reprogramming LK9893-80-4 22 06 2015 Updated sensing resistors and diagrams LK9893-80-5 13 09 2017 Added to introduction and made less car-specific LK9893-80-6 Copyright 2009 Matrix Technology Solutions Limited Page 3 Introduction CAN bus systems and operation What is this all about? protocol to be used ‘on top’ of the basic CAN The ‘CAN’ in CAN bus stands for ‘Controller Area bus protocol to give additional functionality Network’ and ‘bus’ a bundle of wires.
    [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]
  • LIN (LOCAL INTERCONNECT NETWORK) SOLUTIONS by Microcontroller Division Applications
    AN1278 APPLICATION NOTE LIN (LOCAL INTERCONNECT NETWORK) SOLUTIONS by Microcontroller Division Applications INTRODUCTION Many mechanical components in the automotive sector have been replaced or are now being replaced by intelligent mechatronical systems. A lot of wires are needed to connect these components. To reduce the amount of wires and to handle communications between these systems, many car manufacturers have created different bus systems that are incompatible with each other. In order to have a standard sub-bus, car manufacturers in Europe have formed a consortium to define a new communications standard for the automotive sector. The new bus, called LIN bus, was invented to be used in simple switching applications like car seats, door locks, sun roofs, rain sensors, mirrors and so on. The LIN bus is a sub-bus system based on a serial communications protocol. The bus is a single master / multiple slave bus that uses a single wire to transmit data. To reduce costs, components can be driven without crystal or ceramic resonators. Time syn- chronization permits the correct transmission and reception of data. The system is based on a UART / SCI hardware interface that is common to most microcontrollers. The bus detects defective nodes in the network. Data checksum and parity check guarantee safety and error detection. As a long-standing partner to the automotive industry, STMicroelectronics offers a complete range of LIN silicon products: slave and master LIN microcontrollers covering the protocol handler part and LIN transceivers for the physical line interface. For a quick start with LIN, STMicroelectronics supports you with LIN software enabling you to rapidly set up your first LIN communication and focus on your specific application requirements.
    [Show full text]
  • CAN / RS485 Interface Adapter for SHP Series
    Technical Reference Note CAN / RS485 Interface Adapter For SHP Series Total Power: < 1 Watts Input Voltage: 5V Internal Outputs: CAN, RS485, USB, I2C Special Features Product Description The new SHP Extension adapter enables both USB and Controller Area Network (CAN) or RS485 Bus connectivity, providing a complete interface between the • Input Protocols: SHP device and the I2C bus with a simple command set which enables the 1) RS485 using Modbus highest levels of configuration flexibility. 2) CAN using modified Modbus The CAN/RS485 to I2C interface adapter modules connect with CAN Bus • Output Protocol: architectures through CaseRx/CaseTx interfaces found on the SHP case. The I2C with SMBus Support modules communicate with on-board I2C Bus via MODbus Protocol for RS485 Bus and modified MODbus for CANbus. The new adapters now enable the SHP to be used in a host of new ruggedized applications including automotive networks, industrial networks, medical equipment and building automation systems. The RS485/CAN-to-I2C uses 2 Input Protocols and 1 Output Protocol. The Input Protocols used are: RS485 using Modbus (Command Index: 0x01), and CAN using modified Modus (Command Index: 0x02). The Output Protocol use is: I2C with SMBus support (Command Index: 0x80). www.solahd.com [email protected] Technical Reference Note Table of Contents 1. Model Number ………………………….………………………………………………………………. 4 2. General Description ……………………………………………………………………………………. 5 3. Electrical Specifications ……………………………………………………………………………..… 6 4. Mechanical Specification …………………………………………………….….…………………….. 9 5. Hardware Interfaces ………………………………………………………….……………………..... 12 6. Software Interfaces ……………………………………………………………................................ 13 6.1 Adapter Protocol Overview ……………………………………………………………………… 13 6.2 Protocol Transaction …………………………………………………………………………….. 13 6.3 Adapter Command and Response Packets …………………………………………….…..… 14 6.4 Adapter Control Commands ……………………………………………………………..……..
    [Show full text]
  • EN CAN-RS-485 BUS Gateway
    MTGW Installation Guide EN CAN-RS-485 BUS Gateway MTGW | Installation Instructions | 1.0 Overview CAN bus wiring requirements are as follows: Trademarks • CAN Bus Interface: Connect the CAN bus to the Microsoft® Windows® 98/2000/XP are registered MTR Communication Receiver with at least trademarks of Microsoft Corporation in the United 1.5 mm (16 AWG) shielded twisted-pair wire; States and other countries. maximum length: 2000 m (6500 ft). • RS-485 Buses 1-3: Use at least 1.0 mm (20 AWG) 1.0 Overview shielded twisted-pair wire for the RS-485 bus; maximum length: 1200 m (3900 ft). RS-485 bus 1.1 Multi-Tenant System (MTS) Overview wiring status is supervised. MTS is a distributed security system for monitoring 1.2 MTS Device Address and controlling a large number of small sites. You must assign an address to each device in the Examples include apartment and condominium system. The address consists of at least four segments. complexes, retail plazas, office buildings, and For example: educational and hospital campuses. 1.2.5.3.6 A typical MTS installation consists of the following components: • 1: This segment identifies the number assigned to the MTR central receiver (1 to 99). • MTSW Security Station Software: MTSW is an ® ® • 2: This segment identifies the CAN bus number application based on Microsoft Windows , occupied by the MTGW (1 or 2). installed on a PC and monitored by guard station • personnel. 5 : This segment identifies the MTGW’s CAN bus address (1 to 100). • MTR Communication Receiver: The MTR • receives and handles alarm events from devices 3 : This segment identifies the device’s RS-485 connected to the CAN RS-485 bus.
    [Show full text]
  • Local Interconnect Network Bus Application in Vehicle Presented By- Prashant M
    International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 2, February- 2013 Local Interconnect Network Bus Application In Vehicle Presented By- Prashant M. Ambure Guided By- Prof. Mrs. Aditi V. Vedalankar (MGM College of Engineering, Nanded) (Dept. Electronics and Telecommunication Engineering) Abstract busse interconnected between them as shown in the Local Interconnect Network bus was particularly figure below. This is a major difference with other low- designed for low-cost communication between smart cost busses as K-line which was intended to link all the sensors in automotive applications. It is used when ECUs to an external analyse tool for diagnosis purpose high bitrates communications as CAN bus are not The design consist of a central "Airbag needed. The LIN master initiates communication by control unit"(ACU) (a specific type of ECU) monitors a sending the “Header”. The “Data fields” are send by number of related sensors within the vehicle, including LIN master or a LIN slave. Only one slave will respond accelerometers, impact sensors, wheel speed sensors, to a given header. An airbag is part of a vehicle's gyroscopes, brake pressure sensors, and seat occupancy safety system, a flexible envelope designed for rapid sensors. When the requisite 'threshold' has been reached inflation in an automobile collision, to prevent vehicle or exceeded, the airbag control unit will trigger the occupants from striking hard interior objects such as ignition of a gas generator propellant to rapidly inflate a steering wheels. It is considered a "passive" safety nylon fabric bag. The inflated airbag reduces the component not requiring any input or action from the deceleration experienced by the passenger during the user, rather than an "active" component such as a seatIJERT IJERTcrash through the process of venting gas out of small belt, which requires fastening.
    [Show full text]
  • Technical Note TN 156 What Is CAN? Version 1.0
    Technical Note TN_156 What is CAN? Version 1.0 Issue Date: 2015-03-23 The purpose of this technical note is to explain the basics of CAN (Controller Area Network) which are a feature of FTDI’s MCUs. Use of FTDI devices in life support and/or safety applications is entirely at the user’s risk, and the user agrees to defend, indemnify and hold FTDI harmless from any and all damages, claims, suits or expense resulting from such use. Future Technology Devices International Limited (FTDI) Unit 1, 2 Seaward Place, Glasgow G41 1HH, United Kingdom Tel.: +44 (0) 141 429 2777 Fax: + 44 (0) 141 429 2758 Web Site: http://ftdichip.com Copyright © 2015 Future Technology Devices International Limited Technical Note TN_156 What is CAN? Version 1.0 Document Reference No.: FT_001079 Clearance No.: FTDI# 441 Table of Contents 1 Introduction .................................................................................................................................... 2 2 CAN Bus ........................................................................................................................................... 3 2.1 Signals ..................................................................................................................................... 4 2.1.1 MCU Signals .................................................................................................................... 4 2.1.2 PHY Signals ...................................................................................................................... 4 2.2 Typical interconnect
    [Show full text]