SG2032 Automotive Controller Area Network

SG2032 Automotive Controller Area Network

In-Vehicle Networking Automotive Controller Area Network (CAN) Applications Overview Key Benefits The Controller Area Network (CAN) is needing high levels of data integrity and > The automotive networking a serial, asynchronous, multi-master data rates of up to 1 Mbit/s. Freescale standard protocol for Europe communication protocol for connecting Semiconductor has a complete line of > Supports the US automakers electronic control modules in automotive products to enable automotive electronics migration to CAN for body and industrial applications. CAN was designers to incorporate CAN into their electronics busses designed for automotive applications applications. > Provides plentiful and proven Freescale Semiconductor CAN products and tools > Exists in all levels of Freescale Semiconductor microcontrollers and DSPs > Provides connectivity and increased integration using Freescale Semiconductor SMARTMOS™ CAN physical layers and System Basis Chips AUTOMOTIVE CAN NETWORKS Engine Management Module Adaptive Cruise Control Module Active Suspension P Control Module R N Transmission D Control Module L Instrument Cluster/ Diagnostic Powertrain-Body Port Gateway Diagnostic Gateway Connector Central Body Control Module HVAC Climate Module LIN SUB-BUS Steering Column/ Ignition Module LIN SUB-BUS Driver Seat Module LIN SUB-BUS Driver-Side Door Module LIN SUB-BUS Passenger Seat Module LIN SUB-BUS Passenger-Side Door Module LIN SUB-BUS Rear Seat Module LIN SUB-BUS Occupant Safety Gateway FlexRayTM Multimedia Gateway/ Telematics Module MOST Rear Lighting/ Trunk Control SG2032-2 Freescale Ordering InformationNote Part Number Product Highlights Additional Information Analog Devices MC33388 Fault Tolerant CAN Interface www.freescale.com/analog MC33389 System Basis Chip with Low-Speed CAN MC33399 Local Interconnect Network (LIN) Physical Layer MC33661 eLIN – Enhanced LIN Physical Layer (Local Interconnect Network) MC33689 System Basis Chip with Enhanced LIN Physical Interface MC33742 System Basis Chip with Enhanced High-Speed CAN MC33889 System Basis Chip with Low-Speed Fault Tolerant CAN MC33897 Single-Wire CAN Transceiver MC33989 System Basis Chip with High-Speed CAN DSP Devices DSP56F803BU80 16-Bit (DSP/MCU) with 1 MSCAN12 Module www.freescale.com DSP56F805FV80 16-Bit (DSP/MCU) with 1 MSCAN12 Module DSP56F807PY80 16-Bit (DSP/MCU) with 1 MSCAN12 Module DSP56F807VF80 16-Bit (DSP/MCU) with 1 MSCAN12 Module HC08 HC08 Family Up to 60 K of Flash or ROM Memory; Enhanced SCI for LIN; SPI; Clock Generation Module; Freescale Semiconductor Scalable CAN MC68HC908AZxx Family 1 MSCAN08 Module HC12 HC12 Family Up to 128 K of Flash or ROM; SCI; SPI; Clock Generation Module; Up to Three CAN Modules XC68HC912BCxx Family 1 MSCAN12 Module MC68HC912Dxx(A) Family 2 MSCAN12 Modules MC68HC912DG128A 2 MSCAN12 Modules MC68HC912DT128A 3 MSCAN12 Modules HCS12 HCS12 Family Up to 512 K of Flash or ROM; Up to Two ESCI; Up to Three SPI; Up to 4 CAN Modules; Clock Generators; Excellent EMC and Stop Idd MC9S12DGxx Family 2 MSCAN12 (rev. 2.0) Modules MC9S12DJxx Family 2 MSCAN12 (rev. 2.0) Modules, 1 BDLC (J1850) Module MC9S12DPxx Family 5 MSCAN12 (rev. 2.0) Modules MC9S12DTxx Family 3 MSCAN12 (rev. 2.0) Modules MC9S12Dxx Family 1 MSCAN12 (rev. 2.0) Module MC9S12Hxx Family 2 MSCAN12 (rev. 2.0) Modules MC9S12Cxx Family 1 MSCAN12 (rev. 2.0) Module 32-Bit Microcontrollers MPC555/6LFMZP40(R2) 2 TouCAN Modules MPC561/2LFMZP40(R2) 3 TouCAN Modules MPC563/4LFMZP40(R2) 3 TouCAN Modules MPC565/6LFMZP40(R2) 3 TouCAN Modules MPC5200 32-bit Processors MPC5200 2 MSCAN12 2.0a/2.0b e-www.freescale.com/files/abstract/ overview/SPSMPC5200.htm Note: Search on the listed part number. SG2032-3 Design Challenges from the ISO/OSI seven layer stack considered high-speed and low-speed Different CAN Networks Have model and is responsible for current and CAN. Although both architectures use a Different Performance Needs voltage control for the bus. It deals with voltage difference on a pair of wires, the Not all CAN networks are created equal. current and voltage transients and termination methods for each are In the automotive environment, CAN signalling bus (line) faults and works to different and incompatible in production networks can be split into two distinct possibly correct them. systems. categories based on the nature of the The Bosch CAN specification does not One additional CAN physical layer has traffic on the network. Body control dictate physical layer specifications for recently been developed by General networks, dealing with passenger anyone implementing a CAN network. Motors. This physical layer uses only comfort and convenience systems for This is both a blessing and a curse to the one wire at all times that limits its speed example, deal with a wide range of designer. Over the course of the last performance to 33.33 kbit/s. This single- message identifiers that appear in no decade, two major physical layer wire CAN physical layer is very different particular order or frequency. In contrast, designs have come to the forefront and from the other two types and is not yet powertrain networks that pass become the basic physical layer designs widely accepted. information relating to engine and used in most CAN applications. They Because there are no requirements on transmission control have a much lower both communicate using a differential the physical layer in the CAN number of different messages to deal voltage on a pair of wires and are specification, other standards with, but the messages appear very commonly referred to as a high-speed organizations have developed standards rapidly and very regularly. These and a low-speed physical layer. The low- to help designers create compatible CAN differences in messaging result in very speed architecture has the ability to devices. The International Standards different approaches to designing change to a single-wire operating Organization (ISO) and Society of hardware and software systems to deal architecture (referenced off ground) Automotive Engineers (SAE) create the with the demands each type of network when one of the two wires is faulted standards for Europe and the United places on each node in that network. through a short or open. Because of the States respectively, to ensure Different CAN Networks Have nature of the circuitry required to perform interoperability of components at the Physical Layer Requirements this function, this architecture is very physical layer and recommended design CAN, like all major networking protocols, expensive to implement at bus speeds practices. requires a physical layer device to above 125 kbit/s. This is why 125 kbit/s communicate. This physical layer comes is the dividing line between what is Automotive CAN Standards in Europe and the United States CAN Physical Layer Type ISO Standards (Europe) SAE Standards (North America) www.iso.org www.sae.org Single-Wire CAN n/a SAE J2411 Single Wire CAN Network for Vehicle Applications Low-Speed Fault-Tolerant CAN ISO 11519-2 The ISO standard is generally used Road Vehicles—Low-Speed Serial Data Communication— Part 2: Low-Speed Controller Area Network (CAN) ISO 11898-3 may be replaced with 11519-2 High-Speed CAN ISO 11898 SAE J2284-125, SAE J2284-250, and SAE J2284-500 Road Vehicles—Interchange of Digital Information—Controller Area Network (CAN) for High-Speed Communication High Speed CAN (HSC) for Vehicle Application at 125 kbps, 250 kbps, and 500 kpbs, respectively Local Area Network LIN LIN Specification LIN Specification SG2032-4 Freescale Semiconductor Solution fast enough because multiple messages CAN physical layers, Freescale Different CAN Implementations to come in too quickly with the same Semiconductor offers a range of CAN Meet Different CAN Performance identifier, data can be lost. This is why physical layer devices designed to meet Needs mailbox architectures are not always or exceed the performance standards Freescale Semiconductor recognizes the suited to networks with unpredictable, set out by ISO and SAE. challenges that face designers of event-driven data. automotive CAN devices and systems. But a simple physical layer device is not Because different CAN networks have As stated before, body electronics always enough. For example, all different CAN messaging needs, networks have messaging that can be automotive modules need to run from a Freescale Semiconductor provides very sporadic and unpredictable in regulated power supply. Sometimes a different CAN hardware options to meet nature, which makes the Freescale local switch or sensor might need to these challenges. Semiconductor Scalable CAN (msCAN) wake up the module from sleep state to architecture so well suited to these active running state very quickly. That Freescale Semiconductor’s 32-bit applications. Since HC08, HC12, and switch or sensor might be running at microcontrollers use either the HCS12 microcontroller families are 8-bit vehicle battery levels. This is where the TouCAN™ or FlexCAN ™ hardware and 16-bit microcontrollers which are the Freescale Semiconductor System Basis modules to communicate on the CAN backbone of body electronics systems Chip (SBC) brings power and value to bus. These modules are based on the and components, the msCAN module is the automotive design table. SBCs traditional mailbox or “full-CAN” a perfect fit for these families. CAN combine the CAN physical layers hardware architecture that provides messages received by msCAN are needed for automotive CAN connectivity 16 message buffers. When messages placed into a single first-in, first-out with voltage

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    8 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us