Criteria

Text:
Topic:
Content:
Display:

Results

Viewing 1 to 30 of 639
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.
CURRENT
2017-03-21
Standard
AS20708/50B
Scope is unavailable.
CURRENT
2017-03-21
Standard
AS20708/46B
No Scope Available
CURRENT
2017-03-21
Standard
AS20708/52B
No Scope Available
CURRENT
2017-03-21
Standard
AS20708/53B
No Scope Available
CURRENT
2017-03-21
Standard
AS20708/55B
No Scope Available
CURRENT
2017-03-21
Standard
AS20708/56B
Scope is unavailable.
CURRENT
2017-03-20
Standard
AS20708/47B
No Scope Available
CURRENT
2017-03-20
Standard
AS20708/49B
No Scope Available
CURRENT
2017-03-20
Standard
AS20708/48B
No Scope Available
CURRENT
2017-03-20
Standard
AS20708/54B
No Scope Available
2017-03-17
WIP Standard
AIR6388
The information presented in this AIR is intended to provide information about current remote identification methods and practical considerations for remotely identifying UAS. Depending on rigor and adherence requirements, Aerospace Standard (AS) and Aerospace Recommended Practice (ARP) documents may be developed. For example, ARPs may provide methods to remotely identify UAS using existing hardware technologies typically available to most consumers. ARPs may also specify the information exchange and message format between unmanned aerial systems and remote interrogation instruments. An AS, however, may highlight the wireless frequency band, message type, message encoding bits, and message contents.
2017-03-17
WIP Standard
AS20708/62B
No Scope Available
2017-03-17
WIP Standard
AS20708/66B
No Scope Available
2017-03-17
WIP Standard
AS20708/67B
No Scope Available
2017-03-17
WIP Standard
AS20708/74B
No Scope Available
2017-03-17
WIP Standard
AS20708/78B
No Scope Available
2017-03-17
WIP Standard
AS20708/79B
No Scope Available
2017-03-17
WIP Standard
AS20708/80B
No Scope Available
2017-03-17
WIP Standard
AS20708/68B
No scope available.
2017-03-17
WIP Standard
AS20708/76B
No Scope Available
2017-03-17
WIP Standard
AS20708/70B
No Scope Available
CURRENT
2017-03-09
Standard
J1939/81_201703
SAE J1939-81 Network Management defines the processes and messages associated with managing the source addresses of applications communicating on an SAE J1939 network. Network management is concerned with the management of source addresses and the association of those addresses with an actual function and with the detection and reporting of network related errors. Due to the nature of management of source addresses, network management also specifies initialization processes, requirements for reaction to brief power outages and minimum requirements for ECUs on the network.
2017-03-06
WIP Standard
J1939-91
This document will provide recommendations to vehicle manufacturers and component suppliers in securing the SAE J1939-13 connector interface from the cybersecurity risks posed by the existence of this connector.
CURRENT
2017-03-02
Standard
AS6858
This is a joint SAE/EUROCAE development. This document will be released as both an SAE Aerospace Specification (AS) and a EUROCAE Minimum Aviation System Performance Standard (MASPS). This document defines the technical requirements for the safe integration of gaseous hydrogen fueled Proton Exchange Membrane (PEM) Fuel Cell Systems (FCS) within the aircraft. Most of the technical concepts and approaches covered by this document represent current industry "best practice". Others require specific approval from the procuring activity before use. This requirement for approval is not intended to prohibit their use; but rather to ensure that the prime contractor has fully investigated their capability to perform reliably and to be sufficiently durable under the required conditions and that the prime contractor can present substantiating evidence for approval before the design is committed to.
CURRENT
2017-02-21
Standard
AS4074B
This standard specifies the characteristics of the SAE Linear Token Passing Bus (LTPB) Interface Unit. The LTPB provides a high reliability, high bandwidth, low latency serial interconnection network suitable for utilization in real time military and commercial applications. Multiple redundant data paths can be implemented to enhance reliability and survivability in those applications which require these attributes. The token passing and data exchange protocols are optimized to provide low latency and fast failure detection and correction. Physical configurations with bus lengths up to 1000 m can be accommodated. This specification defines the following: a. General Description (3.1): An overview of the LTPB protocol. b. Physical Media Interface (3.2): This portion of the standard defines the physical interface to both optical and electrical bus media. c.
2017-02-21
WIP Standard
J1939DA
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. The J1939 Digital Annex, introduced in August 2013, offers key J1939 technical data in an Electronic Spreadsheet that can be easily searched, sorted, and adapted to other formats. J1939DA contains all of the SPNs (parameters), PGNs (messages), and other J1939 data previously published in the SAE J1939 top level document. J1939DA also contains all of the SLOTs, Manufacturer ID Codes, NAME Functions, and Preferred Addresses previously published in the SAE J1939 top level and the J1939-71 document. J1939DA contains the complete technical details for all of the SPNs and PGNs previously published in the SAE J1939-71 document. It also includes the supporting descriptions and figures previously published in the SAE J1939-71 document.
2017-02-20
WIP Standard
AS5506/3
(1) The Behavior Annex document 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-02-10
WIP Standard
J3076-1
This document is a recommended practice and intended to provide a minimum set of implementation requirements of the Clock Extension Peripheral Interface (CXPI) protocol. This document specifies the parameter requirements of the CXPI protocol. The CXPI protocol provides some selected features of the Controller Area Network (CAN) protocol implemented on a UART-based data link for mainly HMI (Human Machine Interface) of road vehicles electric systems.
Viewing 1 to 30 of 639

Filter

  • Standard
    639