T07 电子计算机应用 标准查询与下载

SAE J2012-2013 故障诊断编码定义

This document supersedes SAE J2012 DEC2007, and is technically equivalent to ISO 15031-6:2010 with the exceptions described in Section 1.2. This document is intended to define the standardized Diagnostic Trouble Codes (DTC) that On-Board Diagnostic (OBD) systems in vehicles are required to report when malfunctions are detected. SAE J2012 may also be used for decoding of enhanced diagnositc DTCs and specifies the ranges reserved for vehicle manufacturer specific usage. This document includes: a. Diagnostic Trouble Code format; b. A description of the standardized set of Diagnostic Trouble Codes and descriptions contained in SAE J2012-DA. The two most signifi

Diagnostic Trouble Code Definitions

BS ISO 17458-4:2013 道路车辆.FlexRay通信系统.电气物理层规范

Road vehicles. FlexRay communications system. Electrical physical layer specification

ISO/TR 12204:2012 道路车辆.运输信息和控制系统人类工效学因素.集成化严格安全性和严格时间警报信号的引入

Road vehicles - Ergonomic aspects of transport information and control systems - Introduction to integrating safety critical and time critical warning signals

ISO/TS 14198:2012 道路车辆.运输信息和控制系统的人类工效学方面.由车载系统使用的评定驾驶员需求方法用测试任务

Road vehicles - Ergonomic aspects of transport information and control systems - Calibration tasks for methods which assess driver demand due to the use of in-vehicle systems

SAE J2931-1-2012 插电式电动车辆数字通信

This SAE Information Report SAE J2931 establishes the requirements for digital communication between Plug-in Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility or service provider, Energy Services Interface (ESI), Advanced Metering Infrastructure (AMI) and Home Area Network (HAN). This is the second version of this document and completes the step 2 effort that specifies the digital communication protocol stack between Plug-in Electric Vehicles (PEV) and the Electric Vehicle Supply Equipment (EVSE). The purpose of the stack outlined in Figure 1 and defined by layers 3 to 6 of the OSI Reference Model is to use the functions of Layers 1 and 2 specified in SAE J 2931/4 and export eht functionalities to Layer 7 as specified in SAE J 2847/2 (as of August 1, 2012, revision) and SAE J 2847/1 (targeting revision at the end of 2012).

Digital Communications for Plug-in Electric Vehicles

ISO 13209-2:2012 道路车辆.开路测试序列交换格式(OTX).第2部分:核心数据模型规范和要求

Road vehicles - Open Test sequence eXchange format (OTX) - Part 2: Core data model specification and requirements

ISO 13209-3:2012 道路车辆.开路测试序列交换格式(OTX).第3部分:标准扩展和要求

Road vehicles - Open Test sequence eXchange format (OTX) - Part 3: Standard extensions and requirements

ISO 14230-1:2012 道路车辆.K-Line(DoK-Line)诊断系统.第1部分:物理层

This part of ISO 14230 specifies the physical layer, based on ISO 9141, on which the diagnostic services will be implemented. It is based on the physical layer described in ISO 9141-2, but expanded to allow for road vehicles with either 12 V d.c. or 24 V d.c. voltage supply. NOTE In this part of ISO 14230, values given in parentheses apply to 24 V d.c. systems.

Road vehicles - Diagnostic communication over K-Line (DoK-Line) - Part 1: Physical layer

SAE J1939/71-2012 车辆应用层(2010年5月通过)

As described in the parent document, SAE J1939, there is a minimum of seven documents required to fully define a complete version of this network. This particular SAE Recommended Practice, J1939-71, describes an Application Layer for vehicle use.

Vehicle Application Layer (Through May 2011)

SAE JA1003-2012 软件可靠性计划实施指南

This document provides methods and techniques for implementing a reliability program throughout the full life cycle of a software product, whether the product is considered as standalone or part of a system. This document is the companion to the Software Reliability Program Standard (JA1002). The Standard describes the requirements of a software reliability program to define, meet, and demonstrate assurance of software product reliability using a Plan-Case framework and implemented within the context of a system application. This document has general applicability to all sectors of industry and commerce and to all types of equipment whose functionality is to some degree implemented by software components. It is intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of software whose reliability is an important performance parameter. Applicability of specific practices will depend on the reliability-significance of the software, application domain, and life cycle stage of the software. Following guidelines in this document does not guarantee required reliability will be achieved, or that any certification authority will accept the results as sufficient evidence that requisite reliability has been achieved. Following guidelines in this document will provide insight into what level of reliability has been achieved. With proper customer, certification authority, and supplier negotiation and interaction in accordance with these guidelines, it is more likely that the achieved reliability will be acceptable.

Software Reliability Program Implementation Guide

SAE JA1002-2012 软件可靠性程序标准

This SAE Standard provides a framework for the management of software reliability within system reliability requirements. It is based around the Software Reliability Plan and Software Reliability Case and emphasizes the importance of evaluating progress towards meeting software reliability requirements throughout the project life-cycle. This document can be applied to all projects that incorporate software. This includes the integration of off the shelf (OTS) software products and custom software. OTS software sources include commercial vendors, government, and industry (e.g., reused library software). Custom software is generally newly developed software or a significant rework/upgrade of existing software that is for use with a specific application.

Software Reliability Program Standard

SAE JA1004-2012 软件保障性程序标准

This SAE Standard defines the basic structural elements, and guidance on compilation and management, for a software supportability program. Software supportability considerations include initial design influence and through-life support embracing the operational use, post-delivery modification, and logistics management of software. This document requires that the processes of design, development, selection, and production of software include software supportability considerations, as relevant to particular project needs. This document generally applies to all types of computer-based systems and throughout the project life-cycle. The developmental scope of the project and other issues as covered within the document determine how this document needs to be tailored.

Software Supportability Program Standard

SAE J1939/14-2011 物理层,500 Kbps

This document defines a physical layer having a higher bandwidth capacity than other physical layers defined for SAE J1939. Newer transceiver technologies are utilized to minimize EMI. This SAE Recommended Practice is intended for light- and heavy-duty vehicles on- or off-road as well as appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include but are not limited to: on- and off-highway trucks and their trailers; construction equipment; and agricultural equipment and implements. Implementing a robust CAN network involves many tradeoffs affecting both the network layout and ECU design. This document presents a standard by which ECUs, tools, and vehicle networks from different sources may be compatible. The document is intended to stand alone, yet borrows from the many existing standards and papers for its methodology.

Physical Layer, 500 Kbps

DIN EN ISO 24534-3:2011 机动车辆和设备识别.车辆的电子注册识别(ERI).第3部分:车辆数据(ISO 24534-3-2010);英文版本EN ISO 24534-3-2010

Automatic vehicle and equipment identification - Electronic Registration Identification (ERI) for vehicles - Part 3: Vehicle data (ISO 24534-3:2010); English version EN ISO 24534-3:2010

SAE J2496-2011 运输区网络布线

This series of SAE Recommended Practices was developed to provide an open architecture system for on-board electronic systems. It is the intention of these documents to allow electronic devices to communicate with each other by providing a standard architecture. This particular document describes the Network Interface and Cabling which defines the requirements needed for communicating between devices that are on different segments of the SAE J2496 Transport Area Network. While these recommended practices may be used in retrofitting older vehicles, the primary intent is for implementation in new bus procurements.

Transport Area Network Cabling

SAE J1939-2011 串行控制和通信重型载重车网络高级文件

This top level document describes the network in general, the OSI layering structure, the subordinate document structure, and provides control for all preassigned values and names. The Appendices of this document lists all SPN assignments, PGN assignments, NAME Function assignments, Manufacturer Code assignments, and Preferred Address assignments. All SPN and PGN assignments are listed in this document even though the complete definition details might be recorded in another standard. The SPN and PGN listings in this document identify the standard document that either contains the definition details or is associated with the identifier.

Serial Control and Communications Heavy Duty Vehicle Network Top Level Document

SAE J2178/4-2011 三字节标题用B类数据通信网络信息定义

This SAE Recommended Practice defines the information contained in the header and data fields of non-diagnostic messages for automotive serial communications based on SAE J1850 Class B networks. This document describes and specifies the header fields, data fields, field sizes, scaling, representations, and data positions used within messages.

Class B Data Communication Network Messages Message Definitions for Three Byte Headers

SAE J2178-1-2011 B类数据通信网络信息详细标题格式和物理地址分配

This SAE Recommended Practice defines the information contained in the header and data fields of non-diagnostic messages for automotive serial communications based on SAE J1850 Class B networks. This document describes and specifies the header fields, data fields, field sizes, scaling, representations, and data positions used within messages. The general structure of a SAE J1850 message frame without in-frame response is shown in Figure 1. The structure of a SAE J1850 message with in-frame response is shown in Figure 2. Figures 1 and 2 also show the scope of frame fields defined by this document for non-diagnostic messages. Refer to SAE J1979 for specifications of emissions related diagnostic message header and data fields. Refer to SAE J2190 for the definition of other diagnostic data fields. The description of the network interface hardware, basic protocol definition, the electrical specifications, and the CRC byte are given in SAE J1850.

Class B Data Communication Network Messages Detailed Header Formats and Physical Address Assignments

SAE J1939/71-2011 车辆应用层(2010年5月通过)

As described in the parent document, SAE J1939, there is a minimum of seven documents required to fully define a complete version of this network. This particular SAE Recommended Practice, J1939-71, describes an Application Layer for vehicle use.

Vehicle Application Layer (Through May 2010)

ANSI/IEEE 1609.4:2011 车载环境下的无线访问(WAVE)标准.多通道运行

Standard for Wireless Access in Vehicular Environments (WAVE) - Multi-Channel Operation