Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 270
CURRENT
2017-10-18
Standard
J1939/84_201710
The purpose of this Recommended Practice is to verify that vehicles and/or components are capable of communicating a required set of information, in accordance with the diagnostic messages specified in SAE J1939-73, to fulfill the off-board diagnostic tool interface requirements contained in the government regulations cited below. This document describes the tests, methods, and results for verifying diagnostic communications from an off board diagnostic tool (i.e., scan tool) to a vehicle and/or component. SAE members have generated this document to serve as a guide for testing vehicles for compliance with ARB and other requirements for emissions-related on-board diagnostic (OBD) functions for heavy duty engines used in medium and heavy duty vehicles. The development of HD OBD regulations by US EPA and California’s Air Resources Board (ARB) require that diagnostic message services are exercised to evaluate diagnostic communication standardization requirements on production vehicles.
CURRENT
2017-10-11
Standard
AS6089
This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Controller (NC) complies with the NC requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all of the requirements invoked by documents that are referenced by AS5653. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653 and in this verification document.
CURRENT
2017-10-10
Standard
J1939DA_201710
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
CURRENT
2017-10-09
Standard
J2809_201710
This Technical Information Report defines the proprietary diagnostic communication protocol for ABS or VSA ECU (Electronic Control Unit) implemented on some Honda vehicles. This protocol does not apply to all Honda vehicles. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an enhanced SAE J2534 interface. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface.
2017-09-20
WIP Standard
AS6062A
This document defines a set of standard application layer interfaces called JAUS Mission Spooling Services. JAUS Services provide the means for software entities in an unmanned system or system of unmanned systems to communicate and coordinate their activities. The Mission Spooling Services represent the platform-independent capabilities commonly found across all domains and types of unmanned systems. At present, 1 service is defined in this document (more services are planned for future versions of this document): • Mission Spooler: Stores mission plans, coordinates mission plans, and parcels out elements of the mission plan for execution The Mission Spooler service is described by a JAUS Service Definition (JSD) which specifies the message set and protocol required for compliance. The JSD is fully compliant with the JAUS Service Interface Definition Language [JSIDL].
2017-09-18
WIP Standard
J1939/73
SAE J1939-73 Diagnostics Application Layer defines the SAE J1939 messages to accomplish diagnostic services and identifies the diagnostic connector to be used for the vehicle service tool interface. Diagnostic messages (DMs) provide the utility needed when the vehicle is being repaired. Diagnostic messages are also used during vehicle operation by the networked electronic control modules to allow them to report diagnostic information and self-compensate as appropriate, based on information received. Diagnostic messages include services such as periodically broadcasting active diagnostic trouble codes, identifying operator diagnostic lamp status, reading or clearing diagnostic trouble codes, reading or writing control module memory, providing a security function, stopping/starting message broadcasts, reporting diagnostic readiness, monitoring engine parametric data, etc.
CURRENT
2017-09-13
Standard
AS5659/4
This Aerospace Standard (AS) 5659/4 Physical Layer Specification provides guidance for the physical layer of optical networks which use Wavelength Division Multiplexing (WDM), within the AS5659 WDM LAN specification document family. The physical layer consists of the optical interconnections between the functional components of the network. Performance requirements for general interconnections are described. For guidance, standards are identified, corresponding to each of several environments, which describe physical layer design, installation, maintenance, and training.
2017-09-12
WIP Standard
SAE6856
This recommended practice provides users with the technical requirements and methods for accessing, viewing, and processing raw GNSS receiver measurements for improved unmanned vehicle navigation solutions.
2017-09-12
WIP Standard
SAE6857
This recommended practice defines the technical requirements for a terrestrial-based PNT system to improve vehicle (e.g. unmanned, aerial, ground, maritime) positioning/navigation solutions and ensure critical infrastructure security, complimenting GNSS technologies.
CURRENT
2017-08-22
Standard
AS5506/3
This Behavior Annex provides a standard sublanguage extension to allow behavior specifications to be attached to AADL components. The aim of the Behavior Annex is to refine the implicit behavior specifications that are specified by the core of the language. The Behavior Annex targets the following goals: - Describe the internal behavior of component implementations as a state transition system with guards and actions. However, the aim is not to replace software programming languages or to express complex subprogram computations. - Extend the default run-time execution semantics that is specified by the core of the standard, such as thread dispatch protocols. - Provide more precise subprogram calls synchronization protocols for client-server architectures.
CURRENT
2017-08-15
Standard
AS4115A
This test plan consists of two major sections for testing of MIL-STD-1553B data bus systems: Bus Network and System Integration Tests.
2017-08-15
WIP Standard
J1939/71
The SAE J1939 communications network is developed for use in heavy-duty environments and suitable for horizontally integrated vehicle industries. The SAE J1939 communications network is applicable for light-duty, medium-duty, and heavy- duty vehicles used on-road or off-road, and for appropriate stationary applications which use vehicle derived components (e.g., generator sets). Vehicles of interest include, but are not limited to, on-highway and off-highway trucks and their trailers, construction equipment, and agricultural equipment and implements.   SAE J1939-71 Vehicle Application Layer is the SAE J1939 reference document for the conventions and notations that specify parameter placement in PGN data fields, the conventions for ASCII parameters, and conventions for PGN transmission rates.
CURRENT
2017-08-14
Standard
AS4116A
This Aerospace Standard (AS) defines the test requirements for determining that bus monitors meet the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.
CURRENT
2017-08-14
Standard
AS4114A
This test plan consists of two major sections for the production testing of bus controllers: Electrical tests and Protocol tests.
CURRENT
2017-08-10
Standard
AS4111A
This SAE Aerospace Standard (AS) contains a sample test plan for AS15531 or MIL-STD-1553B Remote Terminals (RT) that may serve several different purposes. This document is intended to be contractually binding when specifically called out in a specification, Statement of Work (SOW), or when required by a Data Item Description (DID). Any and all contractor changes, alterations, or testing deviations to this section shall be separately listed for easy review.
CURRENT
2017-08-10
Standard
AS4112A
This test plan is broken into two major sections for the production testing of remote terminals: Electrical and Protocol.
CURRENT
2017-08-10
Standard
AS4117A
This test plan defines the requirements of data bus components which comply with the requirements of MIL-STD-1553B, Digital Time Division Command/Response Multiplex Data Bus.
2017-08-09
WIP Standard
AS42702
This document establishes techniques for verifying that a Mission Store Interface (MSI) complies with the interface requirements delineated in MIL-STD-1760 Revision E.
2017-08-01
WIP Standard
ARP7208
This ARP establishes guidelines for the use of IEEE-802.3 as a data bus network in military and aerospace vehicles. It encompasses the data cable and its connections for a system utilizing 10Base-T, 100Base-T, 1000BASE-T and 10GBASE-T over copper medium dependent interfaces (MDI). This document contains extensions/restrictions to “off-the-shelf” IEEE-802.3 standards, and assumes that the reader already has a working knowledge of IEEE-802.3.
CURRENT
2017-07-21
Standard
J1699/3_201707
The main purpose of this Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information, in accordance with the diagnostic test services specified in SAE J1979: E/E Diagnostic Test Modes, or the equivalent document ISO 15031-5: Communication Between Vehicle and External Equipment for Emissions-Related Diagnostics – Part 5: Emissions-related diagnostic services. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534, Recommended Practice for Pass-Thru Vehicle Programming.
HISTORICAL
2017-07-19
Standard
J1939DA_201707
This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and search for easier use.
CURRENT
2017-06-28
Standard
AS47642B
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760C. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies. For validation of aircraft designed to MIL-STD-1760B Notice 3 AS47641 Issued 1999-08 applies.
CURRENT
2017-06-28
Standard
AS47641A
This document establishes techniques for validating that an Aircraft Station Interface (ASI) complies with the interface requirements delineated in MIL-STD-1760B Notice 3. For validation of aircraft designed to MIL-STD-1760A Notice 2 AS4764 Issued 1995-04 applies.
CURRENT
2017-06-27
Standard
AS4270A
This document establishes techniques for validating that a mission store complies with the interface requirements delineated in MIL-STD-1760.
CURRENT
2017-06-27
Standard
AS4764A
This document establishes techniques for validating that an aircraft station complies with the interface requirements delineated in MIL-STD-1760.
CURRENT
2017-06-26
Standard
J2836/4_201706
This SAE Information Report J2836/4 establishes diagnostic use cases between plug-in electric vehicles and the EV Supply Equipment (EVSE). As Plug-In Vehicles (PEV) are deployed and include both Plug-In Hybrid Electric (PHEV) and Battery Electric (BEV) variations, failures of the charging session between the EVSE and PEV may include diagnostics particular to the vehicle variations. This document will describe the general information required for diagnostics and J2847/4 will include the detail messages to provide accurate information to the customer and/or service personnel to identify the source of the issue and assist in resolution. Existing vehicle diagnostics can also be added and included during this charging session regarding issues that have occurred or are imminent to the EVSE or PEV, to assist in resolution of these items.
2017-06-23
WIP Standard
J2945/3
This effort will serve for the development of a new standard to define requirements to support V2I weather applications interface in a connected vehicle environment. USDOT has provided funding for this standard and has requested that the Technical Committee (TC) approve using the Systems Engineering Process (SEP) as defined in J2945/0. Initial works in the field of road weather applications have been conducted by stakeholders from both the public and private sector. USDOT has offered a high level Concept of Operations for Road Weather Connected Vehicle and Automated Vehicle Applications to the TC as a basis for consideration to initiate the dialog for J2945/3. This Concept of Operations contains 8 Proposed Applications and 13 Operational Scenarios for the TC and V2I TF to consider. The TC also has material in SAE J3067 as a basis for its consideration. The focus is on information exchanges between the infrastructure and connected vehicles.
2017-06-19
WIP Standard
J2847/6
This SAE Recommended Practice SAE J2847-6 establishes requirements and specifications for communications messages between wirelessly charged electric vehicles and the wireless charger. Where relevant, this document notes, but does not formally specify, interactions between the vehicle and vehicle operator. This is the 1st version of this document and captures the initial objectives of the SAE task force. The intent of step 1 is to record as much information on “what we think works” and publish. The effort continues however, to step 2 that allows public review for additional comments and viewpoints, while the task force also continues additional testing and early implementation. Results of step 2 effort will then be incorporated into updates of this document and lead to a republished version. The next revision will address the harmonization between SAE J2847-6 and ISO/IEC 15118-7 to ensure interoperability.
2017-06-19
WIP Standard
J2931/6
This SAE Information Report J2931/6 establishes the requirements for physical and data link layer communications between Plug-in Electric Vehicles (PEV) and the Electric Vehicle Supply Equipment (EVSE).
2017-05-23
WIP Standard
AS5680B
This interface standard applies to fuzes used in airborne weapons that use a 3-in fuze well. It defines: - Physical envelope of the fuze well at the interface with the fuze. - Load bearing surfaces of the fuze well. - Physical envelope of the fuze and its connector. - Mechanical features (e.g., clocking feature). - Connector type, size, location and orientation. - Retaining ring and its mechanical features (e.g., thread, tool interface). - Physical envelope of the retaining ring at the interface with the fuze. - Physical space available for installation tools. - Torque that the installation tool shall be capable of providing. This standard does not address: - Materials used or their properties. - Protective finish. - Physical environment of the weapon. - Explosive interface or features (e.g., insensitive munitions (IM) mitigation). - Charging tube. - Torque on the retaining ring or loads on the load bearing surfaces.
Viewing 1 to 30 of 270