SAE J 2602-3-2010 File Structures for a Node Capability File (NCF)《节点容量文件用文档结构(NCF)》.pdf

《SAE J 2602-3-2010 File Structures for a Node Capability File (NCF)《节点容量文件用文档结构(NCF)》.pdf》由会员分享，可在线阅读，更多相关《SAE J 2602-3-2010 File Structures for a Node Capability File (NCF)《节点容量文件用文档结构(NCF)》.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

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 there

2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions. Copyright 2010 SAE International All rights reserved. No part of this publication m

3、ay 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: 724-776-4970 (outside USA)

4、 Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/j2602_3_201001J2602-3 JAN2010 SURFACE VEHICLE RECOMMENDED PRACTICE Issued 2010-01 File Structure

5、s for a Node Capability File (NCF) RATIONALE The scope of this document covers the outcome of an analysis, performed by the SAE J2602-3 Task Force, of the Application Program Interface, Node Configuration File, and LIN Description File portions of the LIN 2.0 specification. The purpose of the analys

6、is was to identify and resolve requirements in these specific specifications that are ambiguous, conflicting, or optional and to document a method for accommodating SAE J2602 node and network specific data elements in the LIN 2.0 NCF/LDF file structure(s). Development and adoption of this recommende

7、d practice will allow the design and development tools to consistently identify, extract, interpret and utilize the required information relative to specific network operational characteristics. FOREWORD SAE J2602-3 provides additional requirements that are not present in LIN 2.0 (e.g., NCF syntax,

8、LDF syntax, data definitions, etc.). This document is to be utilized by Tier 1 suppliers of components, software developers, tool developers, vehicle or OEM system engineers, and vehicle or OEM communications engineers. INTRODUCTION LIN is a single wire, low cost, Class A communication protocol. LIN

9、 is a master-slave protocol, and utilizes the basic functionality of most Universal Asynchronous Receiver Transmitter (UART) or Serial Communication Interface (SCI) devices as the protocol controllers in both Master and Slave devices. To meet the target of “Lower cost than either an OEM proprietary

10、communications link or CAN link” for low speed data transfer requirements, a single wire transmission media based on the ISO 9141 specification was chosen. The protocol is implemented around a UART/SCI capability set, because the silicon footprint is small (lower cost), many small microprocessors ar

11、e equipped with either a UART or SCI interface (lower cost), and the software interface to these devices is relatively simple to implement (lower software cost). Finally, the relatively simplistic nature of the protocol controller (UART/SCI) and the nature of state-based operation, enable the creati

12、on of Application Specific Integrated Circuits (ASICs) to perform as input sensor gathering and actuator output controlling devices, in the vein of Mechatronics. All message traffic on the bus is initiated by the Master device. Slave devices receive commands and respond to requests from the Master.

13、Since the Master initiates all bus traffic, it follows that the Slaves cannot communicate unless requested by the Master. However, Slave devices can generate a bus wakeup, if their inherent functionality requires this feature. The “LIN Consortium” developed the set of LIN specifications. The Consort

14、ium is a group of automotive OEMs, semiconductor manufacturers, and communication software and tool developers. The LIN specification set is “released” by the LIN Steering Committee, a closed subset of the members. Associate Consortium members contribute to the formation of the specifications throug

15、h participation in LIN Work Groups; however, the direction of the Work Groups and the final released content of the specifications is the responsibility of the LIN Steering Committee. SAE J2602-3 Issued JAN2010 Page 2 of 13 The LIN Specifications contain more than just a definition of the LIN protoc

16、ol and physical layer. In addition, a Work Flow Process, Diagnostics and Configuration methods, definition of an Application Program Interface (API), file structures for a Node Capability File (NCF) and a LIN Description File (LDF) and semantics are identified as required (mandatory in all implement

17、ations). However, since there is a great deal of flexibility in the protocol and physical layer, applicability of these specifications to SAE J2602 networks will be further specified in this document. TABLE OF CONTENTS 1. SCOPE 3 1.1 Purpose. 3 2. REFERENCES 3 2.1 Applicable Publications . 3 2.1.1 S

18、AE Publications. 3 2.1.2 ISO Publication . 4 3. DEFINITIONS AND ACRONYMS. 4 3.1 Definitions . 4 3.2 Acronyms 5 4. COMPATIBILITY WITH LIN 2.0 6 4.1 String Variable Type Node Attributes . 6 4.2 Optional Node Attributes. 6 4.3 Frames Defined in NCF 6 4.4 Message_ID in NCF 6 4.5 Frame Length Definition

19、6 4.6 Definition of Encoding Bytes . 6 4.7 Error Signal . 6 4.8 Free Text in NCF. 7 4.9 Additional Master Parameters. 7 4.10 Additional Node Attributes 7 4.11 Dynamic Frames. 7 4.12 Event-Triggered Frames . 7 4.13 Sporadic Frames. 7 5. LIN APPLICATION PROGRAM INTERFACE REQUIREMENTS 7 5.1 LIN 2.0 Nod

20、e Configuration API 7 5.2 LIN 2.0 Diagnostic API 7 5.3 SAE J2602 Status Byte. 7 5.3.1 Signal Consistency . 7 5.3.2 Functional Partitioning 7 5.4 Signal Management 8 5.4.1 Same Signal in Multiple Frames . 8 5.4.2 Unique Name 8 5.4.3 Broadcast and Command Frames 8 5.4.4 SAE J2602 Status Byte. 8 5.5 Ch

21、anging Active Schedule Table Clarification 8 6. LIN NODE CAPABILITY LANGUAGE SPECIFICATION . 8 6.1 Generic NCF . 8 6.2 Message Identifier Clarification in the NCF 9 6.3 General Node Attributes . 9 6.3.1 General Definition . 9 6.3.2 Diagnostic Definition . 9 6.3.3 Frame Definition 9 6.3.4 Encoding De

22、finition . 10 6.3.5 Status Management 10 SAE J2602-3 Issued JAN2010 Page 3 of 13 7. LIN DESCRIPTION FILE DESCRIPTION 10 7.1 Protocol, Language, and Conformance Declarations. 10 7.2 Master Frame Header and Response Tolerances .10 7.2.1 Node Attributes Frame Tolerence 11 8. NOTES 11 8.1 Marginal Indic

23、ia. 11 APPENDIX A SAE J2602 TO LIN 2.0 SIGNAL ENCODING AND DATA TYPES 12 1. SCOPE This document covers the requirements for SAE implementations based on LIN 2.0. Requirements stated in this document will provide a minimum standard level of performance to which all compatible systems, design and deve

24、lopment tools, software, ECUs and media shall be designed. This will assure consistent and unambiguous serial data communication among all connected devices regardless of supplier. This document may be referenced by any vehicle OEM component technical specification that describes any given ECU in wh

25、ich the single wire data link controller and physical layer interface is located. The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers and vehicle system engineers. 1.1 Purpose The goal of SAE J2602 is

26、to improve the interoperability and interchangeability of LIN devices within a network by resolving those LIN 2.0 requirements that are ambiguous, conflicting, or optional. Moreover, SAE J2602 provides additional requirements that are not present in LIN 2.0 (e.g., fault tolerant operation, network t

27、opology, etc.). 2. REFERENCES 2.1 Applicable Publications The following publications form a part of this specification to the extent specified herein. Unless otherwise specified, the latest issue of SAE publications shall apply. In the event of a conflict between this document and one of the referen

28、ced documents this document takes precedence. LIN Specification Package version 2.0 dated September 23, 2003 available at www.lin-subbus.org. LIN Specification package version 2.1 dated November 24th, 2006 available at www.lin-subbus.org. See Appendix A for list of supplier documents/devices. 2.1.1

29、SAE Publications Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or 724-776-4970 (outside USA), www.sae.org. SAE J1213-1 Glossary of Vehicle Networks for Multiplexing and Data Communications SAE J1930 Electrical/Electroni

30、c Systems Diagnostic Terms, Definitions, Abbreviations, and Acronyms SAE J2602-1 LIN Network for Vehicle Applications SAE J2602-3 Issued JAN2010 Page 4 of 13 2.1.2 ISO Publication Available from ANSI, 25 West 43rd Street, New York, NY 10036-8002, Tel: 212-642-4900, www.ansi.org. ISO 7498 Open system

31、s interconnection (OSI) 3. DEFINITIONS AND ACRONYMS 3.1 Definitions 3.1.1 Command Frame A frame with data published by the slave task in the Master Node and subscribed to by one or more slave tasks in slave nodes. 3.1.2 Data Link Layer This provides for the reliable transfer of information across th

32、e physical layer. It includes the message structure, framing and error control. 3.1.3 Dominant Signal The driven and low voltage state of the LIN bus. If multiple devices access the bus, this state dominates the recessive or non-driven state. 3.1.4 “Dormant” State The state in which the slave task s

33、tate machine is waiting for reception of the Break / Synch sequence. 3.1.5 Master Node Responsible for initiating all message traffic. See the Glossary of the LIN Specification Package for additional information. 3.1.6 Media The physical entity that conveys the electrical (or equivalent means of com

34、munication) signal transmission among ECUs on the network. 3.1.7 Must The word “Must” is used to indicate that a binding requirement exists on components or devices which are outside the scope of this specification. 3.1.8 Physical Layer This ISO 7498 subsection consists of the media, mechanical inte

35、rconnections, and transceivers that provide the interconnection between all ECU nodes. 3.1.9 Protocol The formal set of conventions or rules for the exchange of information among the ECUs. This includes the specification of the signal frame administration, frame transfer and physical layer. 3.1.10 P

36、ublisher A Master or Slave Node that is the source of the data transmitted onto the bus within a LIN message. SAE J2602-3 Issued JAN2010 Page 5 of 13 3.1.11 Radiated Emissions The energy that radiates from the LIN physical layer. 3.1.12 Radiated Immunity The level of susceptibility of physical layer

37、 components to communication errors in the presence of high energy electromagnetic fields. 3.1.13 Recessive Signal The undriven and high voltage state of the LIN bus. If multiple devices access the bus, this state is overridden by the dominant state. 3.1.14 Request Frame A frame with data published

38、by the slave task in one and only one Slave Node and only subscribed to by the slave task in the Master Node. 3.1.15 Shall The word “Shall” is to be used in the following ways: a. To state a binding requirement on the LIN interfaces which comprise the ECU, which is verifiable by external manipulatio

39、n and/or observation of an input or output. b. To state a binding requirement upon an ECUs NCF that is verifiable through a review of the document. 3.1.16 Should The word “Should” is used to denote a preference or desired conformance. 3.1.17 Slave Node A device that receives messages from the Master

40、 Node, or responds to messages initiated by the Master Node. See the Glossary of the LIN Specification Package for additional information. 3.1.18 Subscriber A Master or Slave Node that receives the data within a LIN message. 3.1.19 Will The word “Will” is used to state an immutable law of physics. 3

41、.2 Acronyms API Application Program Interface ASIC Application Specific Integrated Circuit CAN Controller Area Network DLC Diagnostic Link Connector DNN Device Node Number ECU Electronic Control Unit EMC Electromagnetic Compatibility ESD Electrostatic Discharge ISO International Organization for Sta

42、ndardization Kbits/sec Thousands of data bits per second SAE J2602-3 Issued JAN2010 Page 6 of 13 LDF LIN Description File LIN Local Interconnect Network LSB Least Significant Byte lsb least significant bit MSB Most Significant Byte msb most significant bit NAD Node Address (for Diagnostics) NCF Node

43、 Capability File OEM Original Equipment Manufacturer RE Radiated Emissions RI Radiated Immunity SAE SAE International SCI Serial Communication Interface UART Universal Asynchronous Receiver/Transmitter 4. COMPATIBILITY WITH LIN 2.0 4.1 String Variable Type Node Attributes Node Attributes “LIN Protoc

44、ol Version” in both the LDF and NCF is defined as a string variable type instead of as a “real” or “integer” value. 4.2 Optional Node Attributes The following Node Attributes are optional for SAE J2602 Slaves: P2_min in NCF and LDF (default = 0 mS) ST_min in NCF and LDF (default = 0 mS) Configurable

45、 Frames in LDF (only needed if NAD = 0x6s) response_tolerance (default = 40 %) wakeup_time (default = 100 ms) poweron_time (default = 100 ms) Support_SID in NCF Max Message Length in NCF (default = 0) 4.3 Frames Defined in NCF Frames defined in NCF must have signals, i.e., the definition of an empty

46、 frame is not allowed. 4.4 Message_ID in NCF Message_ID in NCF is mandatory for SAE J2602. 4.5 Frame Length Definition Frame length definition in NCF is mandatory for SAE J2602. 4.6 Definition of Encoding Bytes The definition of encoding bytes is also allowed for byte array signals, i.e., it is poss

47、ible to define physical and logical encodings for signals larger than 16 bits. 4.7 Error Signal The Error Signal must be a 3 bit signal and should be defined in the NCF using the keyword error_response (as it is in the LDF). SAE J2602-3 Issued JAN2010 Page 7 of 13 4.8 Free Text in NCF Free Text in N

48、CF should be defined as a char string. Note that this change corresponds to the definition in the LIN 2.1 specification. 4.9 Additional Master Parameters Additional Master parameters have been added to the LDF definition for max. header length and Master response tolerance. 4.10 Additional Node Attr

49、ibutes Additional node attributes have been added to NCF and LDF definitions for Slave response tolerance, wakeup time and power on time. 4.11 Dynamic Frames Dynamic frames shall not be used for SAE J2602 networks. 4.12 Event-Triggered Frames Event-triggered frames shall not be used for SAE J2602 networks. 4.13 Sporadic Frames Sporadic frames shall only be published by the Maste