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

SAE J4002-2004 (R)H-点机器和工具的设计规程和规范

This Standard provides the specifications and procedures for using the H-point machine (HPM1) to audit vehicle seating positions. The HPM is a physical tool used to establish key reference points and measurements in a vehicle. The H-point design tool (HPD) is a simplified CAD2 version of the HPM, which can be used in conjunction with the HPM to take the optional measurements specified in this document, or used independently during product design. These H-point devices provide a method for reliable layout and measurement of occupant seating compartments and/or seats. This document specifies the procedures for using the H-point machine (HPM) to audit (verify) key reference points and measurements in a vehicle. The devices are intended for application at designated seating positions. They are not to be construed as tools that measure or indicate occupant capabilities or comfort. They are not intended for use in defining or assessing temporary seating, such as folding jump seats.

(R) H-Point Machine and Design Tool Procedures and Specifications

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

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 JA1002-2004 软件可靠性程序标准

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 JA1003-2004 软件可靠性计划实施指南

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 JA1006-2004 软件支持的概念

This SAE Recommended Pratice provides a framework for the establishment of a software support concept related to the support and supportability of both custom- developed and Off-the-Shelf (OTS) software. This document complements SAE AIR 5121, JA 1004, and JA 1005 by providing information needed to understand the support aspects that should be covered by a software supportability program. It should be noted that particular information indicated here should not be considered a complete list of all aspects of the support concept. In particular, the information should not be confused with a list of data elements. This document has general applicability to all sectors of industry and commerce and to all types of equipment that contain software. The target audience for this document includes software acquisition organizations, logisticians, developers, supporters, and customers. This document 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 support-critical software.

Software Support Concept

SAE J2399-2003 自适应巡航控制(ACC)运行特性和用户界面

Adaptive cruise control (ACC) is an enhancement of conventional cruise control systems that allows the ACC equipped vehicle to follow a forward vehicle at a pre-selected time gap by controlling the engine, power train, and/or service brakes. This SAE Standard focuses on specifying the minimum requirements for ACC system operating characteristics and elements of the user interface. This document applies to original equipment and aftermarket ACC systems for passenger vehicles (including motorcycles). This document does not apply to commercial vehicles. Furthermore, this document does not address future variation on ACC, such as stop&go ACC, that can bring the equipped vehicle to a stop and reaccelerate. Future revisions of this document should consider enhanced versions of ACC, as well as the integration of ACC with forward collision warning (FCW).

Adaptive Cruise Control (ACC) Operating Characteristics and User Interface

KS R ISO 11898-1:2003 道路车辆.控制器局域网络.第1部分:数据链层和物理信令

이 규격은 지역 제어망(CAN)의 데이터 링크층(DLL)과 물리적 신호 방식을 서술한

Road vehicles-Controller area network (CAN)-Part 1:Data link layer and physical signalling

SAE J2630-2003 从ASN.1至XML转换ATIS信息标准

This SAE Standard presents a set of rules for transforming an Abstract Syntax Notation (ASN.1) message set definition into an eXtensible Markup Language (XML) schema. The result is intended to be a stand-alone XML Schema that is fully consistent with an existing ASN.1 information model. This is a different goal from other related work by other standards bodies developing a set of XML encoding rules for ASN.1 or ASN.1 encodings for XML Schema. These rules were initially developed in order to produce an XML schema for the SAE ATIS standard. While other standards may also choose to use these rules, the rules may not be applicable for all environments. The goal for these transformation rules is twofold. The first goal is to provide a uniform set of such rules that all interested parties can use. The second goal is to use such rules to define an adopted schema for traveler information that reflects the preferred translation of ASN.1 message sets to XML for use by ITS system implementers. The first goal is met by this document. The second goal is met by employing this document to produce XML information as part of the periodic re-balloting of the SAE ATIS standard. This is a parallel standards effort with this document. These rules were developed as part of the process to draft an XML version of the ATIS data element and message set standards. The original effort focused upon the needs found in the currently adopted October 2000 SAE J2354 standard for ATIS message sets. SAE J2354 makes extensive use of elements from the ITETMDD work and from ITE-TCIP work. In addition, the draft 'Event Report Message' (ERM) portion of the Message Sets for External Traffic Management Center Communication (MS/ETMCC) standard was also examined and translated. Message and data elements from the IEEE Incident Management standard (IEEE 1512-2000) were also examined. By this effort, every major message set of ITS was considered to some degree to ensure that the resulting translations could be successfully employed by others toward a common result. It is intended that the resulting ATIS schema will be voted on as an SAE ATIS standard. Other standards-developing organizations may also choose to use these rules; however, it is recognized that translations may not be necessary in some environments and that these rules may not be applicable to all environments within ITS. It is left to each standards-development organization to make such determinations for their specific environments. Section 4 is the complete set of conversion rules. An example of use for each rule is given, showing an original ASN.1 definition, the resulting XML schema definition, and a sample XML document element where applicable. Section 5 of this document discusses the background of some non-obvious conversion rules presented in Section 4.2 These include methods of handling the XML representation of enumerations, octet strings, and bit strings. Section 5 also describes how XML namespaces can be used to point to types defined in the Traffic Management Data Dictionary (TMDD), the Transit Communications Interface Profiles (TCIP) standard, the Location Reference Message Set (LRMS), or the International Traveler Information Systems (ITIS) phrase lists. It also discusses additional translation refinements proposed for the conversion of the ATIS message standard. Some omissions in the SAE standards required new types to be defined in order to have a valid XML schema. In addition, some new types must be defined to implement the representation of octet strings and bit strings. These changes are documented in Section 6. In the currently adopted revision of the standard the use of inline definitions rather than the more proper use of formal Type Definitions is also a challenge for conversion. Section 6 also documents a number of common types that were defined globally at the start of the schema rather than being redefined identically, in-line multiple times in the schema.

Converting ATIS Message Standards From ASN.1 to XML

ISO 11898-2:2003 道路车辆.控制器局域网络.第2部分:高速媒体存取单元

This part of ISO 11898 specifies the high-speed (transmission rates of up to 1 Mbit/s) medium access unit (MAU), and some medium dependent interface (MDI) features (according to ISO 8802-3), which comprise the physical layer of the controller area network (CAN): a serial communication protocol that supports distributed real-time control and multiplexing for use within road vehicles.

Road vehicles - Controller area network (CAN) - Part 2: High-speed medium access unit

ISO 11898-1:2003 道路车辆.控制器局域网络.第1部分:数据链层和物理信令

This part of ISO 11898 specifies the data link layer (DLL) and physical signalling of the controller area network (CAN): a serial communication protocol that supports distributed real-time control and multiplexing for use within road vehicles. While describing the general architecture of CAN in terms of hierarchical layers according to the ISO reference model for open systems interconnection (OSI) established in ISO/IEC 7498-1, it provides the characteristics for setting up an interchange of digital information between modules implementing the CAN DLL —itself specified according to ISO/IEC 8802-2 and ISO/IEC 8802-3 — with detailed specification of the logical link control (LLC) sublayer and medium access control (MAC) sublayer.

Road vehicles - Controller area network (CAN) - Part 1: Data link layer and physical signalling

SAE J2540-2002 ATIS标准中处理字符串和查找表的信息

This SAE Standard defines methods and messages to efficiently translate sequences of text and other types of data into and out of indexed values and look-up tables for effective transmission. This document defines: a. methods and data elements for handling indexes and strings in ATIS applications and message sets; b. message sets to support the delivery and translations of tables used in such strings; and c. tables of nationally standardized strings for use in ATIS message descriptions. And examples of each in illustrative portions. While developed for ATIS use, the methods defined in this document are useful for any textual strings in any telematics applications found both in intelligent vehicles and elsewhere.

Messages for Handling Strings and Look-Up Tables in ATIS Standards

SAE J2610-2002 串行数据通讯界面

The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in DaimlerChrysler Corporation (Chrysler Group) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding pass-thru programming of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU. It further specifies additional requirements for the application of a flash strobe voltage multiplexed on the SCI communication link for purposes of ECU reprogramming. This document does not specify the content or meaning of the application messages or diagnostic protocol to be transmitted on the SCI communication link. It only defines a generic method to transfer data between a diagnostic tester and an ECU, regardless of application messaging structure. This specification will be referenced from within SAE J2534 Pass-Thru Programming as a technical information report. In this regard, the inclusion of the SCI communication link is in addition to the approved OBD communication links previously specified in SAE J2534, and constitutes unique DaimlerChrysler Corporation (Chrysler Group) manufacturer-specific requirements.

Serial Data Communication Interface

SAE J1978-2002 等效于ISO/DIS 15031-4-2001标准的OBD II型扫描工具

This SAE Recommended Practice supersedes SAE J1978 FEB1998, and is technically equivalentto ISO/DIS 15031-4:December 14, 2001.This document is intended to satisfy the requirements of an OBD scan tool as required by U.S. On-BoardDiagnostic (OBD) regulations.The document specifies:a. A means of establishing communications between an OBD-equipped vehicle and external testequipment,b. A set of diagnostic services to be provided by the external test equipment in order to exercise theservices defined in SAE J1979,c. Conformance criteria for the external test equipment.1.2 Differences from ISO Document—The ISO 15031-4 document is intended to satisfy the requirements ofOBD requirements in countries other than the U.S., and includes functionality not required or not allowed in theU.S.Notable exceptions are:a. Proposed U.S. OBD regulations will allow ISO 15765-4 as an allowable OBD serial data link at500 kbps only. Only those provisions of ISO 15765-4 that pertain to 500 kbps are required to besupported by an SAE J1978 diagnostic scan tool.b. Proposed U.S. OBD regulations will not allow greater than 20 V at the SAE J1962 connector. Only theType A connector as defined in SAE J1962 needs to be supported by an SAE J1978 diagnostic scantool.Differences between the documents are highlighted in the technical requirements sections of this document.Deleted text is highlighted with and new text is highlighted with bold italic.NOTE— To maintain equivalency of the documents, a comma is used as a decimal marker for numericvalues in this document.

OBD II Scan Tool Equivalent to ISO/DIS 15031-4:December 14, 2001

SAE J2366/7-2002 ITS数据总线应用程序消息层

This SAE Surface Vehicle Recommended Practice defines an Application Message Layer, which may be used as part of a complete protocol stack with the other protocol layers in the SAE J2366 family.

ITS Data BusApplication Message Layer

SAE J2623-2002 标准雨量文件格式

This SAE Standard provides a definition of a rainflow file format. This type of simple text file would contain all relevant information about the rainflow cycle content of a time history. Included information are Comments, Signal Range, Signal Mean, Number of Cycles, Signal Maximum, Signal Minimum. Rainflow cycle counting has become the most accepted procedure for identifying material fatigue relevant cycles in complex variable amplitude load time histories. The cycle counting methods account for the effects of material plasticity and material memory of prior deformation, and the resulting compressed history information is used by durability analysts to estimate the effects of a given service or test history. Standardization of the rainflow counting methods output files, which is the format addressed by the present standard, is important for reliable information transfer between test and design groups, or different calculation software packages, and thus forms a critical step in the evaluation of components and vehicles. Further background information can be found in the SAE publication AE-10 cited in 2.1.1.

Standard Rainflow File Format

SAE J2284-2-2002 在250 Kbps情况下,针对车辆应用的高速CAN(HSC)

This document will define the Physical Layer and portions of the Data Link Layer of the ISO model for a 250 Kbps High Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation.

High Speed CAN (HSC) for Vehicle Applications at 250 Kbps

SAE J2366/4-2002 ITS数据总线薄传输层

This SAE Recommended Practice details the Thin Transport Layer of the Intelligent Transportation Systems (ITS) Data Bus, which is generally intended for in-vehicle use.

ITS Data BusThin Transport Layer

SAE J2284-1-2002 车辆速度为125 Kbps时使用的高速容器(HSC)

This document will define the Physical Layer and portions of the Data Link Layer of the ISO model for a 125 Kbps High Speed CAN (HSC) protocol implementation. Both ECU and media design requirements for networks will be specified. Requirements will primarily address the CAN physical layer implementation.

High Speed CAN (HSC) for Vehicle Applications at 125 Kbps

SAE J2546-2002 模型设定过程标准

The modeling requirements listed in this document provide guidelines for specifying: Analysis requirements; Computer-Aided Engineering (CAE) simulator; Model fidelity; System assumptions; Model architecture; Validation requirements Deliverables; for electrical/electronic components and the integral interfacing systems (mechanical, thermal, hydraulic) associated with these components. The simulation models are primarily intended to facilitate functional specification and operational evaluation between component and system manufacturers, and are not intended to otherwise constrain or restrict the use of CAE simulation tools for automotive design, analysis and validation.

Model Specification Process Standard

SAE J2395-2002 车上信息传送系统的消息优先级

This SAE Recommended Practice applies to both Original Equipment Manufacturer (OEM) and aftermarket ITS message- generating systems for passenger vehicles and heavy trucks. The recommended practice describes the method for prioritizing ITS in-vehicle messages and/or displayed information based on a defined set of criteria. Each criterion has a fixed number of levels that are used to rate/rank a given message or information item to determine its prioritization value. The prioritization value is used to determine the priority in which simultaneous, or overlapping, in-vehicle messages are presented to the driver.

ITS In-Vehicle Message Priority