SAE J 2284-5-2016 High-Speed CAN (HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 5 Mbps.pdf

《SAE J 2284-5-2016 High-Speed CAN (HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 5 Mbps.pdf》由会员分享，可在线阅读，更多相关《SAE J 2284-5-2016 High-Speed CAN (HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 5 Mbps.pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、_SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising theref

2、rom, is the sole responsibility of the user.”SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions.Copyright 2016 SAE InternationalAll rights reserved. No part of this publi

3、cation may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE.TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)Tel: +1 724-776-4970 (out

4、side USA)Fax: 724-776-0790Email: CustomerServicesae.orgSAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedbackon this Technical Report, please visithttp:/www.sae.org/technical/standards/J2284/5_201609SURFACE VEHICLERECOMMENDED PRACTICEJ2284-5 SEP2016Issued 2016-09High-Speed CAN

5、(HSC) for Vehicle Applications at 500 kbps with CAN FD Data at 5 MbpsRATIONALEFacilitate usage of the CAN with Flexible Data Rate (CAN FD) message format for data communication between a vehicle and off board tools.FOREWORDThe objective of SAE J2284-5 is to define a level of standardization in the i

6、mplementation of a 500 kbps arbitration bus with CAN FD Data at 5 Mbps for a point to point connection between a vehicle and off board tools using the Controller Area Network (CAN) protocol. The goal is to achieve a standard Electronic Control Unit (ECU) Physical Layer, Data Link Layer, and Media De

7、sign Criteria which will allow ECU and tool manufacturers to satisfy the needs of multiple end users with minimum modification to a basic design. Likewise, end users will benefit in lower ECU cost achieved from the high volumes of the basic design.TABLE OF CONTENTS1. SCOPE. 32. REFERENCES. 42.1 Appl

8、icable Documents . 42.1.1 SAE Publications 42.1.2 ISO Publications. 42.1.3 Other Publications 53. DEFINITIONS 54. ACRONYMS 95. SYSTEM LEVEL ATTRIBUTES OF THE NETWORK. 105.1 Message Format 105.2 Communication Rate 105.3 Basic Communication Network Parameters 105.4 Topology and Termination . 115.4.1 S

9、ingle On-Board ECU Configuration . 115.4.2 Additional Requirements 125.5 Unshielded Media 125.6 Communication/Survivability Under Faulted Conditions 13SAE INTERNATIONAL J2284-5 SEP2016 Page 2 of 305.7 EMC Criteria. 145.8 Off-Board Tool Requirements 145.8.1 Off-Board Tool Capacitive Load. 145.8.2 Off

10、-Board Tool Propagation Delay. 155.9 Off-Board Tool Cable Requirements 155.9.1 Cable Length 155.9.2 Cable Propagation Delay . 155.9.3 Cable Configuration . 166. ECU REQUIREMENTS 166.1 Absolute Maximum Ratings . 166.1.1 Direct Voltage Connection . 166.1.2 Unpowered Storage Temperature . 176.2 DC Oper

11、ating Parameters 176.2.1 DC Parameters Output Behavior - Recessive Bus State - Bus Disconnected . 186.2.2 DC Parameters Output Behavior - Dominant Bus State - Bus Disconnected 186.2.3 DC Parameters Output Behavior ECU unpowered/Bus Bias Off - Bus Disconnected 196.2.4 DC Parameters Input Behavior Bus

12、 Disconnected 196.2.5 AC Parameters Output Behavior Bus Disconnected . 196.2.6 DC Parameters - Recessive Bus State Normal Operating Mode - Bus Connected . 196.2.7 DC Parameters - Dominant Bus State Normal Operating Mode - Bus Connected 206.3 ECU Internal Capacitance . 206.4 Termination 206.5 Connect

13、or Parameters. 216.6 Bit Timing Requirements 216.6.1 Nominal Bit Time (tBIT) 216.6.2 Data Bit Time . 216.6.3 Data Sample Mode 216.6.4 CAN Bit Timing and Register Settings . 216.6.5 Transmitter Delay Compensation 236.7 Message Transmission and Reception 236.8 ECU Configuration Requirements 236.9 Elec

14、troMagnetic Compatibility (EMC) 247. CAN COMPONENT REQUIREMENTS. 247.1 Bus Transceiver Requirements 247.2 Bus Controller Requirements. 287.3 Microcontroller Requirements and Preferences 308. NOTES. 308.1 Revision Indicator. 30Figure 1 Single on-board ECU configuration A 11Figure 2 Single on-board EC

15、U configuration B 12Figure 3 Off-board tool parameters 14Table 1 Basic communication network parameters 10Table 2 Network topology requirements . 12Table 3 Physical media parameters for unshielded twisted pair. 13Table 4 Fault Behavior 13Table 5 Off-board tool capacitive load (without cable load) 14

16、Table 6 Off-board tool propagation delay (loop delay without cable delay) 15Table 7 Off-board tool cable length. 15Table 8 Off-board tool cable propagation delay (one-way delay without off-board tool delay) 15Table 9 ECU Maximum Bus Wire Voltage - No damage to ECU (12 V system) 16SAE INTERNATIONAL J

17、2284-5 SEP2016 Page 3 of 30Table 10 ECU Operating Parameters CAN Data Communication. 17Table 11 ECU DC Parameters Output Behavior Recessive - Bus Disconnected . 18Table 12 ECU DC Parameters Output Behavior Dominant - Bus Disconnected. 18Table 13 ECU DC Parameters Input Behavior ECU unpowered/Bus bia

18、s off Bus Disconnected. 19Table 14 ECU DC Parameters Input Behavior - Bus Disconnected 19Table 15 ECU AC Parameters Output Behavior - Bus Disconnected . 19Table 16 ECU DC Parameters Recessive Bus State Bus Connected . 19Table 17 ECU DC Parameters Dominant Bus State Bus Connected. 20Table 18 ECU Inte

19、rnal Capacitance ECU disconnected . 20Table 19 ECU Termination Characteristics. 20Table 20 ECU Connector Characteristics . 21Table 21 ECU CAN bit timing min/max 22Table 22 ECU CAN register settings for first standard time quanta . 22Table 23 ECU CAN register settings for second standard time quanta

20、. 22Table 24 ECU Basic CAN Interface Functional Requirements 23Table 25 Bus Transceiver Basic Requirements. 25Table 26 Bus Transceiver Maximum Bus Pin Voltage - No damage to transceiver (12 V system). 25Table 27 Bus Transceiver General Operating Conditions . 26Table 28 Bus Transceiver DC Parameters

21、Output Behavior Recessive/Off State 26Table 29 Bus Transceiver DC Parameters Output Behavior Dominant State . 27Table 30 Bus Transceiver DC Parameters Input Behavior/Threshold Sleep Mode Absent 27Table 31 Bus Transceiver DC Parameters Input Behavior/Threshold Sleep Mode Present. 27Table 32 Bus Trans

22、ceiver AC Parameters 28Table 33 CAN Controller Basic Requirements. 291. SCOPEThis SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the Open Systems Interconnection model (ISO 7498) for a 500 kbps arbitration bus with CAN FD Data at 5 Mbps High-Speed CAN

23、(HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation.Requirements will focus on a minimum standard level of performance from the High-Speed CAN (HSC) implementation. All ECUs an

24、d media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 500 kbps arbitration bus with CAN FD Data at 5 Mbps. The minimum performance level shall be specified by system level performance requirements or characteristi

25、cs described in detail in Section 6 of this document.This document is designed such that if the Electronic Control Unit (ECU) requirements defined in Section 6 are met, then the system level attributes should be obtainable.This document will address only requirements which may be tested at the ECU a

26、nd media level. No requirements which apply to the testing of the HSC implementation as integrated into a vehicle are contained in this document. However, compliance with all ECU and media requirements will increase the possibility of communication compatibility between separately procured component

27、s and will greatly simplify the task of successfully integrating a HSC communication system in a vehicle.SAE INTERNATIONAL J2284-5 SEP2016 Page 4 of 302. REFERENCESThis specification takes precedence over all conflicts in the documents cited in this section.2.1 Applicable DocumentsThe following publ

28、ications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest issue of SAE publications shall apply.2.1.1 SAE PublicationsAvailable from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada)

29、 or +1 724-776-4970 (outside USA), www.sae.org.SAE J551-15 Vehicle Electromagnetic Immunity Electrostatic Discharge (ESD)SAE J1213-1 Glossary of Vehicle Networks for Multiplexing and Data CommunicationsSAE J1930 Electrical/Electronic Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms

30、SAE J1962 Diagnostic ConnectorSAE J2190 Enhanced E/E Diagnostic Test ModesSAE J2962-2 Communication Transceivers Qualification Requirements CANSAE 970295 CAN Bit Timing Requirements2.1.2 ISO PublicationsCopies of these documents are available online at http:/webstore.ansi.org/ISO 7498 Data processin

31、g systems Open systems interconnection standard reference modelISO 7637-1 Road vehicles Electrical disturbance by conduction and couplingISO 10605 Road vehicles Test methods for electrical disturbances from electrostatic dischargeISO 11451-2 Road vehicles Vehicle test methods for electrical disturba

32、nces from narrowband radiated electromagnetic energy - Part 2: Off-vehicle radiation sourcesISO 11452-4 Road vehicles Component test methods for electrical disturbances from narrowband radiated electromagnetic energy Part 4: Harness excitation methodsISO 11898-1 :2015(E) Road vehicles Interchange of

33、 digital information Controller area network (CAN), Part 1: Data link layer and physical signalingISO 11898-2 :2016(E) Road vehicles Interchange of digital information Controller area network (CAN), Part 2: High-speed medium access unitISO 14229 Road vehicles Diagnostic systems Specification of diag

34、nostic servicesISO 26262 Road vehicles Functional safetySAE INTERNATIONAL J2284-5 SEP2016 Page 5 of 302.1.3 Other PublicationsCISPR 25 Limits and Methods of Measurement of Radio Disturbance Characteristics for the Protection of Receivers Used On-Board VehiclesAUTOSAR Release 4.2.2 www.autosar.org3.

35、DEFINITIONSThe definitions provided in SAE J1213-1 apply to this document. Additional or modified definitions, acronyms, and abbreviations included in this document or relevant to the communication of information in a vehicle are catalogued in this section.3.1 ARBITRATION BIT TIMESee Nominal Bit Tim

36、e.3.2 BUS TERMINATIONElements in a subnet (per default two) that implement presence of a defined resistance between CAN_H and CAN_L.3.3 CAN_HThe CAN_H bus wire is fixed to a mean voltage level during the recessive state and is driven in a positive voltage direction during the dominant bit state.3.4

37、CAN_LThe CAN_L bus wire is fixed to a mean voltage level during the recessive state and is driven in a negative voltage direction during the dominant bit state.3.5 CAN ACTIVITY FILTER TIMEDuration for which the bus needs to be continuously in the same state to enable the signal to pass the bus wake-

38、up filter.3.6 CAN BUSSubnet where a number of ECUs communicate via a two-wire link (CAN_H, CAN_L) and where the Controller Area Network protocol is used as data link layer (DLL).3.7 CAN IDENTIFIERBit pattern of 11 bits or 29 bits, located at the beginning of a message that denotes message content an

39、d also reflects message priority.3.8 CLASSICAL CAN MESSAGEBus message according to ISO 11898:1993/Amd.1:1995(E). Bus message according to ISO 11898-1 :2015(E) where the FDF bit is dominant, also known as CAN 2.0.3.9 CAN FD MESSAGEBus message according to ISO 11898-1:2015(E) where the FDF bit is rece

40、ssive. A CAN FD message typically employs different bit rates in the data field and in the arbitration field.SAE INTERNATIONAL J2284-5 SEP2016 Page 6 of 303.10 DATA BIT TIMELength of a single bit in those parts of CAN FD messages where a dedicated separately configurable data bit time is used. The d

41、ata bit time is not used anywhere in Classical CAN messages and is not used in those CAN FD messages where the BRS bit is dominant.3.11 DATA LINK LAYERProvides the reliable transfer of information across the Physical Layer. This includes message qualification and error control.3.12 DATA SAMPLE POINT

42、 (tSAMPLE)The sample point is the time within the bit period at which the single bit sample captures the state of the bus. The programmable bit sample point is located between tSEG1 and tSEG2. Equation 1 shows the relationship of tSAMPLE to tSEG2:(Eq. 1)3.13 DIAGNOSTIC CONNECTORProvides the electric

43、al connection between Off-Board and On-Board ECUs. For some vehicles, the diagnostic connector is the SAE J1962 connector.3.14 DISABLING OF DLC MATCHINGWhen this functionality is supported and active, then the bus transceiver will not compare message data length code (DLC) values as to whether or no

44、t they match to configured DLC values when scanning messages for presence of valid wake-up requests.3.15 DOMINANT STATEThe dominant state is represented by a differential voltage greater than a minimum threshold between the CAN_L and CAN_H bus wires. The dominant state overwrites the recessive state

45、 and represents a logic “0” bit value.3.16 ELECTRONIC CONTROL UNIT (ECU)An On- or Off-vehicle electronic assembly from which CAN SAE J2284-5 messages may be sent and/or received.3.17 ECU Delay (tECU)An ECUs loop delay includes the following four delays:a. Transmitter Propagation Delay (tTX, this inc

46、ludes device delay and slew)b. Receiver Propagation Delay (tRX)c. Receiver Logic Delay (tLOGIC)d. Common Mode Choke (tCHK, optional, Includes both Tx and Rx choke delays)(Eq. 2)tSAMPLE tBIT tSEG2=tECU tTX tRX tLOGIC tCHK+ + + =SAE INTERNATIONAL J2284-5 SEP2016 Page 7 of 303.18 FD_Receive / FD_Transm

47、itStatus flags indicating whether the bus controller employs CAN FD data bit timing presently. 3.19 HANDLEHardware object label of one or multiple LLC frames (LPDU). Identifies hardware element used for transaction. Used to facilitate cancellation of pending message transmission requests.3.20 MEDIAT

48、he physical entity which conveys the electrical (or equivalent means of communication) transmission between ECUs on the network (e.g., unshielded twisted pair wires). Media is defined as all elements between the connector pins of the communicating ECUs through which the signals pass.3.21 MEDIA DELAY

49、 (tBUS)Media delay is defined as the time required for a signal to pass through the media at the longest specified distance (see Table 1 in 5.3, Table 2 in 5.4, and Table 3 in 5.5).3.22 MUSTThe word “Must” is used to indicate that a binding requirement exists on components or devices which are outside the scope of this