Criteria

Text:
Content:
Display:

Results

Viewing 1 to 30 of 397
2017-10-12
WIP Standard
J2931/7
This SAE Information Report J2931/7 establishes the security requirements for digital communication between Plug-In Electric Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility, ESI, Advanced Metering Infrastructure (AMI) and/or Home Area Network (HAN).
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-02
Standard
J2931/7_201710
This SAE Information Report J2931/7 establishes the security requirements for digital communication between Plug-In Electric Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility, ESI, Advanced Metering Infrastructure (AMI) and/or Home Area Network (HAN).
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.
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.
2017-08-18
WIP Standard
J1939/15
This document describes a physical layer utilizing Unshielded Twisted Pair (UTP) cable with extended stub lengths for flexibility in ECU placement and network topology. Also, connectors are not specified. CAN controllers are now available which support the newly introduced CAN Flexible Data Rate Frame format (known as “CAN FD”). These controllers, when used on SAE J1939-15 networks, must be restricted to use only the Classical Frame format compliant to ISO 11898-1 (2003). These SAE Recommended Practices are 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.
CURRENT
2017-08-18
Standard
AS4113A
This test plan is broken into three major sections for the testing of bus controllers Electrical, Protocol and Noise tests.
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.
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.
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-15
WIP Standard
J1939-17
This document defines a physical layer having a higher bandwidth capacity than the classic physical layers defined for SAE J1939-14 by using flexible data rates. CAN controllers are now available which support the Flexible Data Rate Frame Format as defined in ISO 11898-1:2015. These controllers and compatible high speed transceivers are required for use on SAE J1939-17 networks. 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.
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.
CURRENT
2017-05-12
Standard
J1939/73_201705
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.
2017-05-10
WIP Standard
J1939-76
This document provides the technical requirements for implementing the SAE J1939 Functional Safety Communication Protocol in a manner determined suitable for meeting industry applicable functional safety standards.
2017-04-25
WIP Standard
J2602/2
This document covers the tests to be performed on all SAE J2602-1 defined Master and Slave nodes. Tests described in this document will ensure a minimum standard level of performance to which all compatible Electronic Control Unit (ECUs) and media shall be designed. This will assure full serial data communication among all connected devices regardless of supplier. The goal of SAE J2602-2 is to improve the interoperability and interchangeability of LIN devices within a network by verifying the devices pass a minimum set of tests. To allow for easy cross-reference, this document is arranged such that the conformance test for a given section in SAE J2602-1 is in the same section in SAE J2602-2. This document is to be referenced by the particular vehicle Original Equipment Manufacturer (OEM) component technical specification that describes any given ECU in which the LIN data link controller and physical layer interface is located.
2017-03-23
WIP Standard
J2602/1
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 ECUs and media shall be designed. This will assure full serial data communication among all connected devices regardless of supplier. The goal of SAE J2602-1 is 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-1 provides additional requirements that are not present in LIN 2.0 (e.g., fault tolerant operation, network topology, etc.). This document is to be referenced by the particular vehicle OEM component technical specification that describes any given ECU in which the single wire data link controller and physical layer interface is located. Primarily, the performance of the physical layer is specified in this document.
CURRENT
2017-03-21
Standard
AS15531A
This SAE Aerospace Standard (AS) contains requirements for a digital time division command/response multiplex data bus, for use in systems integration, that is functionally equivalent to MIL-STD-1553B with Notice 2. Even with the use of this document, differences may exist between multiplex data buses in different system applications due to particular application requirements and the options allowed in this document. The system designer must recognize this fact and design the multiplex bus controller (BC) hardware and software to accommodate such differences. These designer selected options must exist to allow the necessary flexibility in the design of specific multiplex systems in order to provide for the control mechanism, architectural redundancy, degradation concept, and traffic patterns peculiar to the specific application requirements.
Viewing 1 to 30 of 397

Filter

  • Standard
    397