Display:

Results

Viewing 1 to 30 of 1338
CURRENT
2016-11-21
Standard
J2284/1_201611
This SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the Open Systems Interconnection model (ISO 7498) 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. Requirements will focus on a minimum standard level of performance from the High Speed CAN (HSC) implementation. All ECUs and media shall be designed to meet certain component level requirements in order to ensure the HSC implementation system level performance at 125 kbps. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 5 of this document. This document is designed such that if the Electronic Control Unit requirements defined in Section 6 are met, then the system level attributes should be obtainable.
CURRENT
2016-11-08
Standard
J2561_201611
This SAE Information Report defines the functionality of typical Bluetooth applications used for remotely accessing in-vehicle automotive installations of electronic devices. Remote access may be achieved directly with on-board Bluetooth modules, or indirectly via a custom designed gateway that communicates with Bluetooth and non-Bluetooth modules alike. Access to the vehicle, in the form of two-way communications, may be made via a single master port, or via multiple ports on the vehicle. The Bluetooth technology may also be used in conjunction with other types of off-board wireless technology. This report recommends using a message strategy that is already defined in one or more of the documents listed in 2.1.1, 2.1.4, 2.1.5, and 2.1.6. Those strategies may be used for some of the typical remote communications with a vehicle. It is recognized, however, that there may be specific applications requiring a unique message strategy or structure.
CURRENT
2016-10-25
Standard
J1939/71_201610
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. This document previously contained the majority of the SAE J1939 data parameters and messages for information exchange between the ECU applications connected to the SAE J1939 communications network.
CURRENT
2016-10-21
Standard
AS15532A
The emphasis in this standard is the development of data word and message formats for AS15531 or MIL-STD-1553 data bus applications. This standard is intended as a guide for the designer to identify standard data words and messages for use in avionics systems and subsystems. These standard words and messages, as well as the doumentation format for interface control document (ICD) sheets, provide the basis for defining 15531/1553 systems. Also provided in this standard is the method for developing additional data word formats and messages that may be required by a particular system but are not covered by the formats provided herein. It is essential that any new word formats or message formats that are developed for a 15531/1553 application follow the fundamental guidelines estalbished in this standard in order to ease future standardization of these words an messages. The standard word formats presented represent a composite result of studies conducted by the U.S.
CURRENT
2016-10-21
Standard
AS4074/3B
This slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: a. the physical media interface: this slash sheet specifies the characteristics of the optical interface to the physical bus media; b the minimum and maximum timing requirements for operation of this implementation of the LTPB; c. the data coding used to encode and decode the data for transmission; and d. the default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.
CURRENT
2016-10-21
Standard
AS4074/1B
This slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: a. the physical media interface: this slash sheet specifies the characteristics of the optical interface to the physical bus media; b. the minimum and maximum timing requirements for operation of this implementation of the LTPB; c. the data coding used to encode and decode the data for transmission; and d. the default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.
CURRENT
2016-10-21
Standard
AS4074/2B
This slash sheet specifies the operational parameters and characteristics of a particular implementation of the SAE Linear, Token Passing Bus (LTPB) Interface Unit. This slash sheet defines the following: a. the physical media interface: this slash sheet specifies the characteristics of the optical interface to the physical bus media; b. the minimum and maximum timing requirements for operation of this implementation of the LTPB; c. the data coding used to encode and decode the data for transmission; and d. the default values to be loaded into the timers of the LTPB interface at power-up prior to intervention by the host processor.
CURRENT
2016-10-21
Standard
AIR4271A
This Aerospace Information Report (AIR) has been prepared by the Systems Applications and Requirements Subcommittee of SAE Committee AS-2. It is intended to provide guidance primarily, but not exclusively, for specifiers and designers of data communication systems for real time military avionics applications within a platform. The subject of high speed data transmission is addressed from two standpoints 1) the influence of developments in technology on avionics architectures as a whole and 2) the way in which specific problems, such as video, voice, closed loop control, and security may be handled. While the material has been prepared against a background of experience within SAE AS-2 relating to the development of a family of high speed interconnect standards, reference to specific standards and interconnect systems is minimized.
CURRENT
2016-10-21
Standard
AIR4295A
This document contains guidance for using SAE publications, AS 4112 through AS 4117 (MIL-STD-1553 related Test Plans). Included herein are the referenced test plan paragraphs numbers and titles, the purpose of the test, the associated MIL-STD-1553 paragraph, commentary concerning test methods and rationale, and instrumentation requirements.
CURRENT
2016-10-21
Standard
AIR4886A
The purpose of this document is to establish the requirements for Real-Time Communication Protocols (RTCP). Systems for real-time applications are characterized by the presence of hard deadlines where failure to meet a deadline must be considered a system fault. These requirements have been drive predominantly, but not exclusively, by aerospace type military platforms and commercial aircraft, but are generally applicable to any distributed, real-time, control systems. These requirements are primarily targeted for the Transport and Network Layers of peer to peer protocols, as referenced in the Open System Interconnect Reference Model (2.2.1 and 2.2.2), developed by the International Standards Organization (ISO). These requirements are intended to complement SAE AS4074 (2.1.1) and AS4075 (2.1.2), and future SAE communications standards.
CURRENT
2016-10-21
Standard
AIR5683A
MIL-STD-1553 establishes requirements for digital command/response time division multiplexing (TDM) techniques on military vehicles, especially aircraft. The existing MIL-STD-1553 network operates at a baud rate of 1 Mbps and is limited by the protocol to a maximum data payload capacity of approximately 700 kilobits per second. The limited capacity of MIL-STD-1553 buses coupled with emering data rich applications for avionics platforms plus the expense involved with changing or adding wires to thousands of aircraft in the fleet has driven the need for expanding the data carrying capacity of the existing MIL-STD-1553 infrastructure.
2016-10-03
Magazine
Achieving Performance Advantages in Unmanned Systems Unmanned Vehicle Systems (UVS) are reaching new levels of functionality and performance, and it's not just for air vehicles either. COTS Embedded Systems and Link Budgets The days of proprietary embedded computing systems in military systems are numbered. Custom Designing Enclosures Using 3-D CAD Modeling Due to the advancement of 3-D computer-aided design software, enclosure manufacturing is not what it used to be. Technology advances industry. Fiber Optic Multi-Sensing Platforms Enabling Innovation Across Aerospace Organizations RECAT Wake Turbulence Recategorization New Concept for Improving the Performance of Electrically Small Antennas Microwave Radiometer for Advanced Nanosatellite Control Systems Secret Sharing Schemes and Advanced Encryption Standard SIPHER: Scalable Implementation of Primitives for Homomorphic Encryption Using Mathematics to Make Computing on Encrypted Data Secure and Practical
2016-10-03
Journal Article
2016-01-9044
Eric Gingrich, Daniel Janecek, Jaal Ghandhi
Abstract An experimental investigation was conducted to explore the impact in-cylinder pressure oscillations have on piston heat transfer. Two fast-response surface thermocouples embedded in the piston top measured transient temperature and a commercial wireless telemetry system was used to transmit thermocouple signals from the moving piston. Measurements were made in a light-duty single-cylinder research engine operated under low temperature combustion regimes including Homogeneous Charge Compression Ignition (HCCI) and Reactivity Controlled Compression Ignition (RCCI) and Conventional Diesel (CDC). The HCCI data showed a correlated trend of higher heat transfer with increased pressure oscillation strength, while the RCCI and CDC data did not. An extensive HCCI data set was acquired. The heat transfer rate - when corrected for differences in cylinder pressure and gas temperature - was found to positively correlate with increased pressure oscillations.
2016-09-30
WIP Standard
J2945/4
This standard will serve to re-work and extend the existing SAE J2735 message elements in order to include additional travel and roadway information from the infrastructure to enhance safety awareness and promote the exchange and transfer of such messages types between vehicles and the infrastructure (V2I). Fundamentally this document will outline the needs and detail the system requirements to support a variety of use cases linking to the J2735 effort as other J2945/x documents do. The initial scope will be to revise the structure of the existing “TIM” message to reflect the lessons learned from the various deployment activities such as the BIM developed by an automotive OEM consortium. The objective is to improve the general functionality of the message set in key areas such as message linking, content segmentation, message forwarding within a security framework, and new application areas beyond what is enabled by the TIM.
2016-09-27
Technical Paper
2016-01-2125
Henry Hameister
This paper presents an approach to how existing production systems can benefit from Industry 4.0 driven concepts. This attempt is based on a communication gateway and a cloud-based system, that hosts all algorithms and models to calculate a prediction of the tool wear. As an example we will show the Refill Friction Stir Spot Welding (RFSSW), a solid state joining technique, which is examined at the Institute of Production Engineering (LaFT) of the Helmut-Schmidt-University, University of the Federal Armed Forces Hamburg, for years. RFSSW is a sub-section of friction welding, where a rotating tool that consists out of three parts is used to heat up material to a dough-like state. Since Refill Friction Stir Spot Welding produces a selective dot-shaped connection of overlapping materials, the production requirements are similar to riveting or resistance spot welding.
2016-09-20
Journal Article
2016-01-2042
Chad N. Miller, Michael Boyd
Abstract This paper introduces a method for conducting experimental hardware-in-the-loop (xHIL), in which behavioral-level models are coupled with an advanced power emulator (APE) to emulate an electrical load on a power generation system. The emulator is commanded by behavioral-level models running on an advanced real-time simulator that has the capability to leverage Central Processing Units (CPUs) and field programmable gate arrays (FPGA) to meet strict real-time execution requirements. The paper will be broken down into four topics: 1) the development of a solution to target behavioral-level models to an advanced, real-time simulation device, 2) the development of a high-bandwidth, high-power emulation capability, 3) the integration of the real-time simulation device and the APE, and 4) the application of the emulation system (simulator and emulator) in an xHIL experiment.
2016-09-20
Journal Article
2016-01-2051
Andreas Himmler, Lars Stockmann, Dominik Holler
Abstract The application of a communication infrastructure for hybrid test systems is currently a topic in the aerospace industry, as also in other industries. One main reason is flexibility. Future laboratory tests means (LTMs) need to be easier to exchange and reuse than they are today. They may originate from different suppliers and parts of them may need to fulfill special requirements and thus be based on dedicated technologies. The desired exchangeability needs to be achieved although suppliers employ different technologies with regard to specific needs. To achieve interoperability, a standardized transport mechanism between test systems is required. Designing such a mechanism poses a challenge as there are several different types of data that have to be exchanged. Simulation data is a prominent example. It has to be handled differently than control data, for example. No one technique or technology fits perfectly for all types of data.
CURRENT
2016-09-16
Standard
AIR6114
This document was prepared by the SAE AS-1B1 IMM Task Group to explain and document background information and design decisions made during the development of AS5726. This handbook is published separately to preserve information that is not required or provided in the AS5726 but may be important to system designers to ensure interoperability between the Micro Munition Host and Micro Munition. As a handbook, it cannot be invoked as a requirement in a contract. The structure and numbering of this document mirrors that of AS5726 for the convenience of readers. Headings such as “Requirements” in this handbook should not be interpreted as invoking requirements.
2016-09-14
WIP 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.
2016-09-14
Technical Paper
2016-01-1890
Jun Ma, Zaiyan Gong, Yiwei Dong
Abstract With the development of automotive HMI and mobile internet, many interactive modes are available for drivers to fulfill the in-vehicle secondary tasks, e.g. dialing, volume adjustment, music playing. For driving safety and drivers’ high expectation for HMI, it is urgent to effectively evaluate interactive mode with good efficiency, safety and good user experience for each secondary tasks, e.g. steering wheel buttons, voice control. This study uses a static driving simulation cockpit to provide driving environment, and sets up a high-fidelity driving cockpit based on OKTAL SacnerStudio and three-dimensional modeling technology. The secondary tasks supported by HMI platform are designed by customer demands research. The secondary task test is carried out based on usability test theory, and the influence on driving safety by different interactive modes is analyzed.
2016-09-06
WIP Standard
J2818
This Technical Information Report defines the diagnostic communication protocol Keyword Protocol 1281 (KWP1281). This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECUs, in which a KWP1281 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the KWP1281 protocol in enough detail to support the requirements necessary to implement the communication protocol in an SAE J2534 interface device.
2016-09-06
WIP Standard
J2819
This Technical Information Report defines the diagnostic communication protocol TP2.0. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an SAE J2534 interface. Some Volkswagen of America and Audi of America vehicles are equipped with ECU(s), in which a TP2.0 proprietary diagnostic communication protocol is implemented. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an SAE J2534 interface.
2016-08-25
WIP Standard
ARP6857
This recommended practice defines the technical requirements for a terrestrial based PNT system to improve unmanned vehicle navigation solutions and ensure critical infrastructure security.
2016-08-25
WIP Standard
ARP6856
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.
2016-08-01
Magazine
Seeing the Light Achieving Full-Color, Day or Night Readability for Flat-Panel Displays Multiple Node Networking Using PCIe Interconnects PCI Express (PCIe) interconnects, and how they can be used to support multiple node low latency data transfers over copper or optical cables, is gaining momentum in embedded computing solutions. Zero-Emissions Electric Aircraft Theory vs Reality Analyzing Radar Signals With Demodulation Combining Software and Hardware for Highly Specialized Multichannel Spectrum Monitoring Advanced Thermal Management Solutions Thermoelectric Cooling Thermal Ground Planes Thermal Management of Laser Diodes The Effect of Substrate Emissivity on the Spectral Emission of a Hot-Gas Overlayer Process Approach to Determining Quality Inspection Deployment Experimental Setup to Assess Blast and Penetration-Induced Secondary Debris in a Military Operations in Urban Terrain (MOUT) Environment Non-Contact Circuit for Real-Time Electric and Magnetic Field Measurements
2016-07-27
WIP Standard
J2945/12
This recommended practice will provide guidance on Traffic Probe Use data to manufacturers that are either Transportation System Management (TSM) core or aligned entities. The recommended practice originates from prior work of the Society of Automotive Engineers (SAE) Dedicated Short Range Communication (DSRC) Technical Committee, as well as existing practices implemented by industry, academia and government. The recommended practice informs manufacturers and practitioners of message use and operation within an automated collection system involved in the orchestration of safe, efficient, and reliable movement of people and goods. The recommended practice for Traffic Probe Use and Operation will support practitioners through the definition of message structure, on-board processing and storage requirements, the operational preservation of vehicle anonymity, and message event management criteria.
2016-07-14
Book
Eric Walter, Richard Walter
Modern vehicles have electronic control units (ECUs) to control various subsystems such as the engine, brakes, steering, air conditioning, and infotainment. These ECUs (or simply ‘controllers’) are networked together to share information, and output directly measured and calculated data to each other. This in-vehicle network is a data goldmine for improved maintenance, measuring vehicle performance and its subsystems, fleet management, warranty and legal issues, reliability, durability, and accident reconstruction. The focus of Data Acquisition from HD Vehicles Using J1939 CAN Bus is to guide the reader on how to acquire and correctly interpret data from the in-vehicle network of heavy-duty (HD) vehicles. The reader will learn how to convert messages to scaled engineering parameters, and how to determine the available parameters on HD vehicles, along with their accuracy and update rate. Written by two specialists in this field, Richard (Rick) P. Walter and Eric P.
CURRENT
2016-06-28
Standard
EIA511
The Manufacturing Message Specification is an application layer standard designed to support messaging communications to and from programmable devices in a Computer Integrated Manufacturing (CIM) environment. This environment is referred to in this standard as the manufacturing environment. This standard does not specify a complete set of services for remote programming of devices, although provision or such a set of services may be subject of future standardization efforts.
2016-06-02
WIP Standard
J2836/5
This SAE Information Report J2836/5™ establishes the use cases for communications between Plug-In Electric Vehicles (PEV) and their customers. The use case scenarios define the information to be communicated related to customer convenience features for charge on/off control, charge power curtailment, customer preference settings, charging status, EVSE availability/access, and electricity usage. Also addresses customer information resulting from conflicts to customer charging preferences. This document only provides the use cases that define the communications requirements to enable customers to interact with the PEV and to optimize their experience with driving a Plug-In Electric Vehicle. Specifications such as protocols and physical transfer methods for communicating information are not within the scope of this document.
2016-05-17
Magazine
Base-engine value engineering for higher fuel efficiency and enhanced performance Continuous improvement in existing engines can be efficiently achieved with a value engineering approach. The integration of product development with value engineering ensures the achievement of specified targets in a systematic manner and within a defined timeframe. Integrated system engineering for valvetrain design and development of a high-speed diesel engine The lead time for engine development has reduced significantly with the advent of advanced simulation techniques. Cars poised to become 'a thing' Making automobiles part of the Internet of Things brings both risks and rewards. Agility training for cars Chassis component suppliers refine vehicle dynamics at the high end and entry level with four-wheel steering and adaptive damping.
Viewing 1 to 30 of 1338

Filter