《SAE-J1939-82-2008.pdf》由会员分享，可在线阅读，更多相关《SAE-J1939-82-2008.pdf（40页珍藏版）》请在三一文库上搜索。
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 ther
2、efrom, 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 2008 SAE International All rights reserved. No part of this publication
3、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: 724-776-4970 (outside USA
4、) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org J1939-82 AUG2008 SURFACE VEHICLE RECOMMENDED PRACTICE Issued2008-08 ComplianceTruck and Bus RATIONALE Not applicable. FOREWORD This series of SAE Recommended Practices has been developed by the Truck and Bus Control
5、 and Communications Network Subcommittee of the Truck and Bus Electrical and Electronics Committee. The objectives of the subcommittee are to develop information reports, recommended practices, and standards concerned with the requirements, design, and usage of devices that transmit electronic signa
6、ls and control information among vehicle components. The usage of these Recommended Practices is not limited to truck and bus applications. Other applications may be accommodated with immediate support being provided for construction and agricultural equipment, and stationary power systems. These SA
7、E Recommended Practices are intended as a guide toward standard practice and are subject to change so as to keep pace with experience and technical advances. This particular document, SAE J1939-82, describes the compliance tests and procedures to verify an SAE J1939 ECU will operate correctly on a S
8、AE J1939 network. This compliance document is used for all SAE J1939 applications. TABLE OF CONTENTS 1.SCOPE 2 2.REFERENCES 3 2.1Applicable Publications3 2.1.1SAE Publications 3 2.1.2ISO Publications .3 3.DEFINITIONS3 3.1Certification3 3.2Compliance3 3.3Self-Compliance 3 4.ABBREVIATIONS4 5.EQUIPMENT
9、4 5.1Compliance Test Computer (CTC)4 5.1.1Message Transmission.4 5.1.2Message Reception4 5.1.3Time Stamp.4 5.1.4Time Resolution4 SAE J1939-82 Issued AUG2008 - 2 - 5.1.5Time Stamp Accuracy.4 5.1.6Time Stamp Latency Error4 5.1.7Transmission Synchronization4 5.1.8Reception Timeout4 5.1.9CAN Interface .
10、4 5.2Device Under Test (DUT)5 5.2.1Operation5 5.2.2Controls.5 6.SETUP.5 6.1Minimum Network5 6.2Message Traffic .5 6.3Test Message Set5 7.TEST SELECTION 5 7.1Document Identifying Test.5 7.2Requirement versus Device Characteristics .5 8.RUNNING A TEST 5 8.1Identify Test .5 8.2Report Generation.6 9.REP
11、ORTING COMPLIANCE TEST RESULTS.6 9.1Self-Compliance 6 9.2Device Support 6 APPENDIX A - COMPLIANCE TESTS.7 APPENDIX B - FORMAT FOR COMPLIANCE TEST REPORTING FORMS39 TABLE A1 - TEST REQUIREMENT CODES .8 TABLE A2 - ECU CLASS CODES8 TABLE A3 - DATA LINK TRANSMIT TESTS - GENERAL.10 TABLE A4 - DATA LINK R
12、ECEIVE TESTS - GENERAL .12 TABLE A5 - DATA LINK TRANSMIT TEST - TP BAM.18 TABLE A6 - DATA LINK RECEIVE TESTS - TP BAM .20 TABLE A7 - DATA LINK TRANSMIT TESTS - TP RTS/CTS.22 TABLE A8 - DATA LINK RECEIVE TESTS - TP RTS/CTS27 TABLE A9 - NETWORK LAYER TESTS32 TABLE A10 - NETWORK MANAGEMENT TESTS35 TABL
13、E A11 - PHYSICAL LAYER TESTS.38 TABLE B1 - SAMPLE REPORTING FORM .40 1. SCOPE The purpose of these compliance procedures is to generate one or more test documents that outline the tests needed to assure that an ECU that is designed to operate as a node on a SAE J1939 network would do so correctly. S
14、AE does not certify devices and these tests and their results do not constitute endorsement by SAE of any particular device. These tests are presented to allow testing of a Device to determine self-compliance by the manufacturer of a device. The manufacturer can use its record of what procedures wer
15、e run successfully to show the level of compliance with SAE J1939. SAE J1939-82 Issued AUG2008 - 3 - 2. REFERENCES This specification takes precedence over all conflicts in the documents cited in this section. 2.1 Applicable Publications The following publications form a part of this specification t
16、o the extent specified herein. Unless otherwise specified, the latest issue of SAE publications shall apply. 2.1.1 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.or
17、g. SAE J1455 Recommended Environmental Practices for Electronic Equipment Design in Heavy-Duty Vehicle Applications SAE J1939 Recommended Practice for a Serial Control and Communications Vehicle Network SAE J1939-11 Physical Layer, 250K bits/s, Twisted Shielded Pair SAE J1939-15 Reduced Physical Lay
18、er, 250K Bits/Sec, Un-Shielded Twisted Pair (UTP) SAE J1939-21 Data Link Layer SAE J1939-31 Network Layer SAE J1939-81 Network Management 2.1.2 ISO Publications Available from American National Standards Institute (ANSI), 25 West 43rd Street, New York, NY 10036-8002, Tel: 212-642-4900, www.ansi.org.
19、 ISO 11898-1 Road vehiclesController area network (CAN)Part 1: Data link layer and physical signaling 3. DEFINITIONS Terms and definitions are defined in SAE J1939, except the following: 3.1 Certification Public announcement, using documentation with signatures from a member of a duly recognized com
20、petent body (i.e. UL, TUV, CSA), to give notice that a given device has been tested and found to meet all necessary issues of a particular requirement or standard, whether legislated or of purely common industrial usage. 3.2 Compliance Announcement that a device has been tested and found to meet a p
21、articular set (not necessarily all) of issues of a particular requirement or standard, without any supporting signatures from a recognized standard agency as performed by a third party investigator. 3.3 Self-Compliance Announcement that a device has been tested and found to meet a particular set (no
22、t necessarily all) of issues of a particular requirement or standard, without any supporting signatures from a recognized standard agency. -,-,- SAE J1939-82 Issued AUG2008 - 4 - 4. ABBREVIATIONS CTC Compliance Test Computer DUT Device Under Test 5. EQUIPMENT The Standard Test Configuration will con
23、tain two nodes, the Compliance Test Computer (CTC) and the Device Under Test (DUT), with appropriate media and termination, as well as power supplies and DUT loads. 5.1 Compliance Test Computer (CTC) A Compliance Test Computer with the following capabilities: 5.1.1 Message Transmission Must be able
24、to send any specified message. 5.1.2 Message Reception Must be able to receive all bus messages. 5.1.3 Time Stamp Must be able to time stamp at the beginning of received messages at the required resolution. 5.1.4 Time Resolution Must possess a minimum time resolution of 10 microsecond. The actual ti
25、me resolution must be specified. 5.1.5 Time Stamp Accuracy The error between any two timestamps shall be less than 1% of the time difference between the two timestamps or 1 millisecond, whichever is greater. 5.1.6 Time Stamp Latency Error Must be less than 1 count of the time resolution. 5.1.7 Trans
26、mission Synchronization Must be able to control the time between messages it transmits. 5.1.8 Reception Timeout In cases where DUT should have no response the CTC must be able to monitor that no response message is transmitted by the DUT for a minimum time equal to the allowed transmission response
27、time plus two times the allowed latency (for example when transmission should be within 200 milliseconds and 50 millisecond latency is allowed then CTC must check for a minimum time of 300 milliseconds). Longer times are at the discretion of the designers. 5.1.9 CAN Interface At least one CAN interf
28、ace is required. Two CAN interfaces are required for testing Bridge functions. SAE J1939-82 Issued AUG2008 - 5 - 5.2 Device Under Test (DUT) The Device Under Test with the following features: 5.2.1 Operation Must be able to perform its normal intended use (not operating any special testing mode of o
29、peration). 5.2.2 Controls Must be able to initiate the action under test when directed. 6. SETUP The setup will consist of a minimum network with two nodes. Any additional requirements for a specific test procedure will be specified within that procedure. 6.1 Minimum Network Two nodes, the DUT and t
30、he CTC, with terminations, a short length of the appropriate media, power supplies. 6.2 Message Traffic Minimal normal network traffic, only the messages necessary for the specific test procedure (see 5.2.1). 6.3 Test Message Set Messages that are applicable to a specific test procedure will be list
31、ed in the test outline. This message list will be broken into two pieces: those supported for reception and those supported for transmission. 7. TEST SELECTION The procedure to select a test or set thereof, necessary to check for compliance to a particular function or set of functions from the stand
32、ard, are outlined within Appendix A. Appendix A is broken into tables, which identify functions, based on which document section(s) they are described within. Some tests will be pointed to by more than one entry. 7.1 Document Identifying Test The specific document identifying a particular function w
33、ill be outlined with any necessary cross-references within a Table for the specific task force document. 7.2 Requirement versus Device Characteristics The SAE and User Requirements status of each function will be cross referenced with the Device Characteristics (such as: Arbitrary Address Capable, C
34、ommand Configurable, Diagnostic Tool, etc.) that will affect whether a device should provide said function. 8. RUNNING A TEST The steps necessary to run a test are outlined as follows: 8.1 Identify Test Using Appendix A the reviewer should identify the test number(s) necessary to check any particula
35、r function(s) that they desire. Note that all tests are not applicable to all systems. The “ Requiring Document” column refers the reviewer to the appropriate document section the test is intended to cover. SAE J1939-82 Issued AUG2008 - 6 - 8.2 Report Generation Using APPENDIX A the reviewer should
36、document the test(s) performed and the results, as well as whether the device had requirement exceptions (additions or exclusions) for each of the particular functions. 9. REPORTING COMPLIANCE TEST RESULTS Appendix A, Compliance Tests, contains columns in the forms for reporting the results of compl
37、iance testing. These columns are used to report the test date, whether a particular test is required for the specific device being tested and whether the test has been run, as well as whether the device passed (complied with) the test. 9.1 Self-Compliance Appendix A is intended to be used by an OEM
38、as self-compliance documentation. When certifying a device the OEM can indicate whether that the device is intended to provide each function, as well as the general level to which the device is designed. The passage of each function by the particular device can then be documented along with the date
39、 of testing. The inclusion of the specific test number(s) should enable future comparison among devices, as well as, among testers. 9.2 Device Support The reporting forms record the test(s) conducted, the test results, and whether a device is intended to support a particular function, which makes th
40、ese reporting forms very helpful to a customer locating a desired device. PREPARED BY THE SAE TRUCK AND BUS CONTROL AND COMMUNICATIONS NETWORK SUBCOMMITTEE OF THE SAE TRUCK AND BUS ELECTRICAL AND ELECTRONICS COMMITTEE SAE J1939-82 Issued AUG2008 - 7 - APPENDIX A - COMPLIANCE TESTS A.1 INTRODUCTION T
41、ables herein describe tests and/or procedures needed to check compliance of a device against each requirement of the SAE J1939 document set. The sections are divided by document title with section number references to the specific text defining a function and its operation. The tables include all de
42、scribed network functions not simply minimum requirements. The requirement to perform a test or procedure for an ECU can be discerned by looking in the applicable ECU Class columns under the SAE and User Requirements heading. See Section A.2.5 below for more details about interpreting testing requir
43、ements. A.2 TEST OUTLINE TABLE STRUCTURE AND COLUMN DEFINITIONS The following definitions and values are identified to enable completion of the entries into the respective columns of the compliance test tables. A.2.1 Row Provides a numeric tag to use in references to particular tests. A.2.2 Test Nam
44、e Name or title for the particular test. A.2.3 Requiring Document Specifies the source of the particular item. Usually this will be a particular section of a SAE J1939-xx document. A.2.4 Description Provides a short outline of the identified feature and the test. A.2.5 SAE and User Requirements The
45、SAE and User Requirements consists of several ECU Classes columns and a User column. The set of columns under the ECU Class heading are used to identify the necessity to check compliance to a particular test, based upon the ECU class. The column under the User Add./Excl. heading is provided to allow
46、 users to customize the necessity to check compliance to a particular test. An X in any of the ECU Classes columns implies the test is required by SAE for that ECU Class (see A.2.5.2 below for ECU Class definition). A D in the User column implies this test is desired as an additional feature for the
47、 particular ECU under test. An E implies that the ECU under test is not required to provide this feature even when it might be a requirement. The presence of a code in an ECU Class column conveys a requirement to evaluate the test for an ECU of that class. The presence of a code in the User Add./Exc
48、l. column conveys a requirement to evaluate the test per the requirements of the user. The absence of a code in a SAE and User Requirements column indicates there is no explicit requirement to evaluate the test for an ECU of that class or per the requirements of the user. A.2.5.1 Requirement Codes T
49、here are currently three (3) codes defined to denote the requirement for evaluating a particular test. New codes will be added as the need is identified. The test requirement codes supported for the Test Outlines are summarized in Table A1. SAE J1939-82 Issued AUG2008 - 8 - TABLE A1 - TEST REQUIREMENT CODES Code Meaning Specified By X Compliance to the