Browse Topic: Telecommunications

Items (2,253)
J1939 Digital AnnexJ1939DA_201402 (Current)12/8/2025
The J1939 Digital Annex 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. For all other SPNs and PGNs which are published in a document other than SAE J1939-71, J1939DA lists only basic details along with a reference to the document that contains the complete technical details. J1939DA replaces, and expands upon, the 1939 Companion Spreadsheet (CS1939), which was last published through November 2012. The data fields included in J1939DA for PGNs are: PGN Parameter Group Label Acronyn EDP DP PF PGN Length PS PGN Description Multipacket Transmission Rate PGN Data Length Default Priority PGN Reference PGN Document The data fields included in J1939DA for SPNs are: SPN SPN Name SPN Description SPN Length Resolution Offset Data Range Operational Range Units SLOT Identifier SPN Type SPN Reference SPN Document The J1939 Digital Annex is current through Fourth Quarter 2013 and can be purchased separately or as part of the SAE J1939 Standards Collection on the Web.
Truck Bus Control and Communications Network Committee
This document applies to safety observers or spotters involved with the use of outdoor laser systems. It may be used in conjunction with SAE Aerospace Standard (AS4970) “Human Factors Considerations for Outdoor Laser Operations in the Navigable Airspace.” Additional control measures may be applicable and are listed in ANSI Z136.6.
G10T Laser Safety Hazards Committee
This document covers the requirements for SAE implementations based on ISO 17987:2016. 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 adding additional requirements that are not present in ISO 17987:2016 (e.g., fault tolerant operation, network topology, etc.).The intended audience includes, but is not limited to, ECU suppliers, LIN controller suppliers, LIN transceiver suppliers, component release engineers, and vehicle system engineers.The term “master” has been replaced by “commander” and term “slave” with “responder” in the following sections.
Vehicle Architecture For Data Communications Standards
Rotorcraft continue to experience higher fatal accident rates compared to fixed-wing aircraft, primarily due to low altitude flight operations and reduced situational awareness in complex environments. A critical factor is the limited availability of accurate, up-to-date information on helipads and surrounding obstacles - such as trees, poles, and buildings - that pose significant risks during takeoff and landing. Existing resources, including the Federal Aviation Administration's heliport registry, are often outdated and incomplete, particularly for private or state-operated sites, and fail to report nearby obstacles. This lack of up-to-date data is largely due to privacy restrictions at certain locations and the high cost associated with comprehensive obstacle surveys. To address this challenge, we develop a deep learning (DL) framework that automatically detects helipads and nearby obstacles from high-resolution satellite imagery. Our approach combines Mask R-CNN for precise pixel-level helipad segmentation with Grounding DINO, a zero-shot vision-language model that identifies obstacles using flexible text prompts (e.g., "Pole", "Tree") without task-specific training. This text-guided, scalable detection method adapts to diverse and evolving operational settings. We validate our framework across helipads in the United States, and demonstrate strong performance in both helipad localization and obstacle detection. In addition, we build a web-based application that automates image processing, updates incorrect heliport coordinates, and provides obstacle reports. This work aims to enhance aviation safety, modernize infrastructure records, and deliver scalable tools to the aviation and machine learning communities.
Khelifi, AmineCarannante, GiuseppinaBouaynaya, NidhalJohnson, Charles
ABSTRACT A simulation capable of modeling grid-tied electrical systems, vehicle-to-grid (V2G) and vehicle-to-vehicle(V2V) resource sharing was developed within the MATLAB/Simulink environment. Using the steady state admittance matrix approach, the unknown currents and voltages within the network are determined at each time step. This eliminates the need for states associated with the distributed system. Each vehicle has two dynamic states: (1) stored energy and (2) fuel consumed while the generators have only a single fuel consumed state. One of its potential uses is to assess the sensitivity of fuel consumption with respect to the control system parameters used to maintain a vehicle-centric bus voltage under dynamic loading conditions.
Jane, Robert S.Parker, Gordon G.Weaver, Wayne W.Goldsmith, Steven Y.
ABSTRACT The authors studied the effects of different types of armor on the performance of spin-torque microwave detectors (STMD). Working prototypes of novel nano-sized spintronic sensors of microwave radiation for battlefield anti-radar and wireless communications applications are being integrated into Sensor Enhanced Armor (SEA) and Multifunctional Armor (MFA) and tested in SEA-NDE Lab at TARDEC. The preliminary theoretical estimations have shown that STMD based on the spin-torque effect in magnetic tunnel junctions (MTJ), when placed in the external electromagnetic field of a microwave frequency, can work as diode detectors with the maximum theoretical sensitivity of 1000 V/W. These STNO detectors could be scaled to sub-micron size, are frequency-selective and tunable, and are tolerant to ionizing radiation. We studied the performance of a STMD in two different dynamical regimes of detector operation: in well-known traditional in-plane regime of STMD operation and in recently discovered novel out-of-plane regime.
Bankowski, ElenaMeitzler, ThomasPesys, Tomas
To this point in aviation history, a typical aircraft type certification program has focused on the constituent systems that make up the aircraft, decomposing them further and further down until reaching their elemental parts and how they interact. This approach has traditionally treated the actual communication technology as only an interface, with technology and implementation based on a decision between multiple stakeholders via an ICD and high-level requirements. This has been necessary to ensure the accurate and on-time delivery of safety-critical data between nodes. When using legacy point-to-point or bus-based data communication technologies like ARINC 429 or MIL-STD-1553, this approach has worked well enough as these technologies are relatively straightforward and proven technologies. However, as onboard bandwidth needs for safety-critical data increase, these legacy technologies are increasingly no longer capable of meeting the needs of system integrators. Ubiquitous, high-bandwidth Ethernet is the obvious solution to these needs and, indeed, it has been used for quite some time in onboard networking applications for low Development Assurance Level (DAL)/non-safety critical data. However, as Ethernet moves into high-DAL applications, the certification of the Ethernet network itself becomes a major complexity that must be addressed directly.
Mustillo, MichaelFinnegan, DanielZischka, Wolfram
There is a shift in the industry driving avionics manufactures to provide more interactive connectivity than they have had to in the past. The increasing threat of cyber security attacks in our communication systems is an increasing problem in our society and the avionics industry cannot ignore the fact that the threats are real and they must protect the systems from these attacks. Another element driving these concerns is the implementation of the FAA's NextGen or EASA's SESAR technologies which will require avionics vendors to replace their proprietary, relatively isolated embedded computer systems with information systems that interoperate and share data throughout FAA's/EASA's operations. In order to make the National Airspace (NAS) operate in the most efficient way all aircraft and ground systems will need to share information. The FAA and EASA have released standards to address these systems. This paper is only going to address aspects of security from a software perspective; more specifically, what an operating system and its environment should provide as a foundation for the security requirements. It is important to note that a generic solution to any security problem does not exist. Providing a complete security solution is the result of going through and addressing the airworthiness security process (AWSP).
Gilliland, Gary
This SAE Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing the performance of automated driving system (ADS) during an event that meets the trigger threshold criteria specified in this document. The document is intended to govern data element definitions, to provide a minimum data element set, and to specify a common ADS data logger record format as applicable for motor vehicle applications. Automated driving systems (ADSs) perform the complete dynamic driving task (DDT) while engaged. In the absence of a human “driver,” the ADS itself could be the only witness of a collision event. As such, a definition of the ADS data recording is necessary in order to standardize information available to the accident reconstructionist. For this purpose, the data elements defined herein supplement the SAE J1698-1 defined EDR in order to facilitate the determination of the background and events leading up to a collision in an ADS-operated vehicle. The data elements defined in this document are unique to Level 3, 4, or 5 ADS features, as defined by SAE J3016, and provide additional background of the events leading up to a crash or crash-like event. The data from sensors such as camera(s), LiDAR(s) etc. will provide information in the absence of a human driver. The data included in the ADS data logger is expected to be used in conjunction with the SAE J1698 event data recorder (EDR) record and traditional accident reconstruction analysis. The EDR and ADS data logger will capture information leading up to the triggered event, at a minimum. There are no facts to support that recording data for greater than 5 seconds pre-event would change the outcome of any crash analysis. Thus, the recommended recording duration for a data logger is 5 seconds pre-event, same as an EDR. Due to the potential for sensor and/or communication failure during a crash event, the recommendation is that data should be collected post-crash for impact and rollover sensors for up to 250 ms. ADS technology is still being developed and is not yet commercially deployed. Therefore, this SAE Recommended Practice is intended as a guide toward standard practice and is subject to change to keep pace with experience and technical advances.
Event Data Recorder Committee
This document describes machine-to-machine (M2M) communication to enable cooperation between two or more participating entities or communication devices possessed or controlled by those entities. The cooperation supports or enables performance of the dynamic driving task (DDT) for a subject vehicle with driving automation feature(s) engaged. Other participants may include other vehicles with driving automation feature(s) engaged, shared road users (e.g., drivers of manually operated vehicles or pedestrians or cyclists carrying personal devices), or road operators (e.g., those who maintain or operate traffic signals or workzones). Cooperative driving automation (CDA) aims to improve the safety and flow of traffic and/or facilitate road operations by supporting the movement of multiple vehicles in proximity to one another. This is accomplished, for example, by sharing information that can be used to influence (directly or indirectly) DDT performance by one or more nearby road users. Vehicles and infrastructure elements engaged in cooperative automation may share information, such as state (e.g., vehicle position, signal phase), intent (e.g., planned vehicle trajectory, signal timing), or seek agreement on a plan (e.g., coordinated merge). Cooperation among multiple participants and perspectives in traffic can improve safety, mobility, situational awareness, and operations. However, nothing in this document is intended to suggest that driving automation requires such cooperation in order to be performed safely. Cooperative strategies may be enabled by the sharing of information in a way that meets the needs of a given application. The needs may be expressed in terms of performance characteristics, such as latency, transmission mode (e.g., one-way, two-way), range, privacy and security, and information content and quality. There are several potential technologies for communicating information between the subject vehicle and other participants. This document focuses on application-oriented functionality and does not imply the need for or require any specific functionality associated with communications protocols or the open systems interconnection model layers in a protocol stack. This document addresses the operational and tactical timescales of dynamic driving on ADS-operated vehicles, and excludes strategic functions such as trip scheduling and selection of destinations and waypoints. This information report is intended to facilitate communication and awareness for the design and anticipated development and validation of cooperative driving automation.
Cooperative Driving Automation(CDA) Committee
This SAE Information Report classifies and defines a harmonized set of safety principles intended to be considered by ADS and ADS-equipped vehicle development stakeholders. The set of safety principles herein is based on the collection and analysis of existing information from multiple entities, reflecting the content and spirit of their efforts, including: SAE ITC AVSC Best Practices CAMP Automated Vehicle Research for Enhanced Safety - Final Report RAND Report - Measuring Automated Vehicle Safety: Forging a Framework U.S. DOT: Automated Driving Systems 2.0 - A Vision for Safety Safety First for Automated Driving (SaFAD) UNECE WP29 amendment proposal UNECE/TRANS/WP.29/GRVA/2019/13 On a Formal Model of Safe and Scalable Self-Driving Cars (Intel RSS model) SAE J3018 This SAE Information Report provides guidance for the consideration and application of the safety principles for the development and deployment of ADS and ADS-equipped vehicles. This SAE Information Report is not intended to encompass all aspects of system-level safety for an ADS-equipped vehicle, including communication with other traffic participants. Addressing all identified safety principles is intended to support, but not fully ensure, comprehensive system-level safety. As an SAE Information Report, this document is non-normative, imposes no requirements, and does not address: Requirements for methodology, metrics, and/or acceptance thresholds. Ethics-related safety principles, or any link between the safety principles defined in this document and ethical studies/frameworks. Conformance with safety principles for purposes of liability and/or fault assignment. As ADS technology and deployment are expanded in the future, this document may be reconsidered for future revision including normative requirements.
On-Road Automated Driving (ORAD) committee
ABSTRACT
Johnson, CharlesSpecht, DavidBouaynaya,  NidhalRasool,  Ghulam
This document describes [motor] vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis. It provides a taxonomy with detailed definitions for six levels of driving automation, ranging from no driving automation (Level 0) to full driving automation (Level 5), in the context of [motor] vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways: Level 0: No Driving Automation Level 1: Driver Assistance Level 2: Partial Driving Automation Level 3: Conditional Driving Automation Level 4: High Driving Automation Level 5: Full Driving Automation These level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on [motor] vehicles in a functionally consistent and coherent manner. “On-road” refers to publicly accessible roadways (including parking areas and private campuses that permit public access) that collectively serve all road users, including cyclists, pedestrians, and users of vehicles with and without driving automation features. The levels apply to the driving automation feature(s) that are engaged in any given instance of on-road operation of an equipped vehicle. As such, although a given vehicle may be equipped with a driving automation system that is capable of delivering multiple driving automation features that perform at different levels, the level of driving automation exhibited in any given instance is determined by the feature(s) that are engaged. This document also refers to three primary actors in driving: the (human) user, the driving automation system, and other vehicle systems and components. These other vehicle systems and components (or the vehicle in general terms) do not include the driving automation system in this model, even though as a practical matter a driving automation system may actually share hardware and software components with other vehicle systems, such as a processing module(s) or operating code. The levels of driving automation are defined by reference to the specific role played by each of the three primary actors in performance of the DDT and/or DDT fallback. “Role” in this context refers to the expected role of a given primary actor, based on the design of the driving automation system in question and not necessarily to the actual performance of a given primary actor. For example, a driver who fails to monitor the roadway during engagement of a Level 1 adaptive cruise control (ACC) system still has the role of driver, even while s/he is neglecting it. Active safety systems, such as electronic stability control (ESC) and automatic emergency braking (AEB), and certain types of driver assistance systems, such as lane keeping assistance (LKA), are excluded from the scope of this driving automation taxonomy because they do not perform part or all of the DDT on a sustained basis, but rather provide momentary intervention during potentially hazardous situations. Due to the momentary nature of the actions of active safety systems, their intervention does not change or eliminate the role of the driver in performing part or all of the DDT, and thus are not considered to be driving automation, even though they perform automated functions. In addition, systems that inform, alert, or warn the driver about hazards in the driving environment are also outside the scope of this driving automation taxonomy, as they neither automate part or all of the DDT, nor change the driver’s role in performance of the DDT (see 8.13). It should be noted, however, that crash avoidance features, including intervention-type active safety systems, may be included in vehicles equipped with driving automation systems at any level. For automated driving system (ADS) features (i.e., Levels 3 to 5) that perform the complete DDT, crash mitigation and avoidance capability is part of ADS functionality (see also 8.13).
On-Road Automated Driving (ORAD) committee
With the development of cellular communication technology and for the sake of reducing drag resistance, the multi-lane platoon technology will be more prosperous in the future. In this article, the cooperative vehicle platoon method on the public road is represented. The method’s architecture is mainly composed of the following parts: decision-making, path planning and control command generation. The decision-making uses the finite state machine to make decision and judgment on the cooperative lane change of vehicles, and starts to execute the lane change step when the lane change requirements are met. In terms of path planning, with the goal of ensuring comfort, the continuity of the vehicle state and no collision between vehicles, a fifth-order polynomial is used to fit every vehicle trajectory. In terms of control command generation module, a model predictive control algorithm is used to solve the multi-vehicle centralized optimization control problem. We use the two DOF vehicle model to simulate vehicle dynamics. The front wheel angle and acceleration or braking commands of multiple vehicles are optimized to ensure that the vehicle can well follow the trajectory of the vehicle which is calculated by the control command generation module. At the same time, the energy consumed by performing steering, acceleration and deceleration is also minimized. Finally, in the simulation process, we simulate one direction two lanes scenario. The result shows that the proposed method can effectively handle multi-lane platoon re-configuration scenario.
Chen, GuoshengWu, JianLi, ShuaiZhang, JinghuaDu, ZhiqiangWang, GuojunChen, Zhicheng
csp1071 test Construction of The Traffic Law and Regulation Framework for Automated DrivingSAE-PP-002902/18/2021
Road automated driving as a new generation of information technology and the integration of the transport industry's development has become a new round of global scientific and technological innovation and industrial transformation. This technology will promote the continuous upgrading of the field of road traffic. At present, the government, enterprises, and investors all take this as the goal and direction to accelerate automated driving in China. A reasonable traffic law and regulation system is required to promote the healthy development of automatic driving and fully release scientific and technological innovation subjects' vitality. Until now, China has formulated an official rule concerning the road testing of automated driving. According to this rule, no passenger and freight transportation can be officially applied using automatic vehicles. Therefore, this paper tries to construct the traffic law and regulation framework to promote automated driving development. This paper firstly summarizes the profound reform of automated driving on the road traffic industry in terms of vehicles, infrastructure, practitioners, and transportation services. Based on China's current administrative rules and traffic regulations, the legal and institutional obstacles in automatic driving are analyzed. This paper proposes a traffic law and regulation framework to promote the development of automated driving. The proposed framework can help the transport authority administrate automated driving in legal identity, demonstration application, transportation operation, practitioner management, and scene management. Finally, the policy suggestions to help develop automated driving are put forward. Through enhanced supervision, mutual recognition of qualification, regulation mode innovation, ecosystem construction, and multi-party cooperation, the automated driving market and partners' vitality can be significantly stimulated
SintzADMIN, JeneaneAnthony, Lindsay
7.0.108 - Challenges Faced for Parameterization & Validation of a Small Gasoline Engine Plant Model for Application of EMS DevelopmentSAE-PP-002842/4/2021
Control algorithm development for typical Engine Management System is a challenging task. To develop a reliable control algorithm, proper closed loop testing environment is required. In such development activity, it is of prime importance to validate the algorithm on a standalone target engine. This can be achieved in engine test cell where the actual engine will be controlled by prototype ECU. But this process has drawbacks like higher testing cost, time consuming, non-reusability of test bed etc. Simulation based engine plant model development for closed loop ECU testing is an effective technique for such application. Various generic engine models are available for such application.to suit a particular target engine these model need to be parameterized with precise engine data. The vehicle parameters used for parameterization are typically obtained from actual test and engine design data. This paper elaborates the process and challenges faced while parameterization and validation of engine plant model in simulation environment and steps followed while parameterizing a two cylinder gasoline engine to suit EMS development. Simulations were carried out in Model In Loop (MIL) and Hardware In Loop (HIL). Validation results were compared with actual vehicle data from dynamometer trials and are presented in corresponding sections.
Lname, Fname
7.0.107 - Design and Development of Capacitance Type Level Sensor for Automotive Vehicle ApplicationSAE-PP-002832/4/2021
Fuel level sensor is a device to indicate the level of the fuel in fuel tank fitted in an automobile. This will have features to communicate the fuel level to the dashboard of the vehicle and is of significant attention to the driver during vehicle usage. The advanced instrumentation provides a lot of information on the dashboard display such as information about fuel level, computing mileage, miles to go or miles to empty, fuel economy, average mileage, etc. Presently, the float arm type with Thick Film Resistor(TFR) and Reed switch type fuel level sensors are being used. To have accurate information for computing, the present sensors are not supporting due to its limitations like nonlinearity, fluctuating output due to slosh, output variations in steps and not continuous. The measurement accuracy of the fuel level sensor needs to be focused to rely on the information available on the dashboard instrument. Hence, it is vital to have a sensor with better reliability, accuracy and adaptability. Capacitance technology based level sensor is identified for development as one of the solutions to meet the demands of the above requirements and this paper portrays the complete perspective and design methodology of capacitance based fuel level sensor. The basics of capacitance measurement, design concepts, design validations, proto-type results are elaborated in this paper.
Lname, Fname
Construction of The Traffic Law and Regulation Framework for Automated DrivingSAE-PP-002462/3/2021
Road automated driving as a new generation of information technology and the integration of the transport industry's development has become a new round of global scientific and technological innovation and industrial transformation. This technology will promote the continuous upgrading of the field of road traffic. At present, the government, enterprises, and investors all take this as the goal and direction to accelerate automated driving in China. A reasonable traffic law and regulation system is required to promote the healthy development of automatic driving and fully release scientific and technological innovation subjects' vitality. Until now, China has formulated an official rule concerning the road testing of automated driving. According to this rule, no passenger and freight transportation can be officially applied using automatic vehicles. Therefore, this paper tries to construct the traffic law and regulation framework to promote automated driving development. This paper firstly summarizes the profound reform of automated driving on the road traffic industry in terms of vehicles, infrastructure, practitioners, and transportation services. Based on China's current administrative rules and traffic regulations, the legal and institutional obstacles in automatic driving are analyzed. This paper proposes a traffic law and regulation framework to promote the development of automated driving. The proposed framework can help the transport authority administrate automated driving in legal identity, demonstration application, transportation operation, practitioner management, and scene management. Finally, the policy suggestions to help develop automated driving are put forward. Through enhanced supervision, mutual recognition of qualification, regulation mode innovation, ecosystem construction, and multi-party cooperation, the automated driving market and partners' vitality can be significantly stimulated. Keywords: Traffic Law and Regulation, Automated Driving, Administrative Rules and regulations, Road Testing, Demonstration Application, Commercial Operation
MobrxivNonAdmin, Lindsay
1.1.216 - Tailored Design and Layout for Loss Minimization or Cost-Effective Commonality of Parts - A Contradictory ConflictSAE-PP-002422/3/2021
In order to minimize the development and production costs in the automotive industry, despite steadily increasing variety of models and applications offered by the OEMs, the pressure on standardization of components and production processes is increasing continuously. As a direct consequence, modular engine families are already established with high degrees of common parts and kits as well as standardized interfaces for all vehicle platforms by most manufacturers these days. At the same time, the world adopted and announced massive legal demands concerning the reduction of CO2 emissions for the entire vehicle fleet. In addition to the optimization of the combustion process, the exhaust gas aftertreatment and thermal management, the use of improved and more resilient materials for higher reduction of mechanical friction leads to a significant amount of the realized lowering in fuel consumption respective CO2 emissions. Significant future potential for friction reduction and loss minimization is expected to result from, for example, one for the particular application optimized, on-demand component dimensioning and tailored calibrations. This dedicated fine-tuning approach is contrary to the widely spread application of a clear common part strategy. In the course of this paper the question will be discussed whether the additional cost of a component diversification can be justified within an engine family in contradiction to a best cost approach by using the scaling effects of parts communization.
Mutagaana, Festo
2.0.104 - Tackling Three Critical Issues of Transportation: Environment, Safety and Congestion Via Semi-autonomous PlatooningSAE-PP-002142/1/2021
In recent years, platooning emerged as a realistic configuration for semi-autonomous driving. In the SARTRE project, simulation and physical tests were performed to validate the platooning system not only in testing facilities but also in conventional highways. Five vehicles were adapted with autonomous driving systems to have platooning functionalities, enabling to perform platoon tests and assess the feasibility, safety and benefits. Although the tested system was in a prototype, it demonstrated sturdiness and good functionality, allowing performing conventional road tests. First of all the fuel consumption decreased up to 16% in some configurations and different gaps between the vehicles were tested in order to establish the most suitable for platooning in terms of safety and economy. Additionally, the platooning technology enables a new level of safety in highways. Around 85% of the accident causation is the human factor. With platooning, the human factor is reduced almost entirely, making it a more efficient and safer system. With platooning, the traffic flow is more homogeneous with several vehicles travelling at the same speed and therefore accident situations are less probable while helping to maintain a steady traffic flow with no stop and go situations. For the same reason, the traffic flow is more manageable enabling advanced traffic management. Thus, the traffic congestion can be reduced and, again, reducing another source of emissions. All the potential advantages of a platooning technology which has been developed and tested are studied in this paper through test results and simulations.
Mutagaana, Festo
SAE J2534-1 defines a standard vehicle network interface that can be used to reprogram emission-related control modules. However, there is a need to support vehicles prior to the 2004 model year, as well as non-emission related control modules. The SAE J2534-2 document meets these needs by detailing extensions to API version 04.04 of the SAE J2534-1 specification. It is not required for an interface to be fully compliant with API version 04.04 of the SAE J2534-1 specification to implement some of the features specified in this document. Together, these extensions provide the framework for a common interface to protect the software investment of the vehicle OEMs and scan tool manufacturers. Only the optional features will be described by this document and are based on the December 2004 publication of SAE J2534-1.
Vehicle E E System Diagnostic Standards Committee
ITIS Phrase Lists (International Traveler Information Systems)J2540/2_202012 (Current)12/6/2020
This standard provides a table of textual messages meeting the requirements for expressing International Traveler Information Systems (ITIS) phrases commonly used in the ITS industry. The tables provided herein follow the rules of SAE J2540 and therefore allow a local representation in various different languages, media expressions, etc., to allow true international use of these phrases. The phrases are predominantly intended for use in the description of traffic-related events of interest to travelers and other traffic practitioners. Other phrases exist for other specific specialty areas of ITS, and all such phrases follow a set of encoding and decoding rules outlined in SAE J2540 to ensure that the use of these phrases in messages remain interoperable between disparate types of user equipment. Implementers are cautioned to obtain the most recent set of tables by means of the ITS data registry, a process which involves SAE and other standards-setting organizations, and which is intended to maintain and enhance the level of harmonization among ITS standards set by each of the organizations. This standard defines the normative index values to be used to provide phrases needed by ITS practitioners. This standard provides non-normative textual phrases which MAY be used by implementers to ensure intelligible results. This standard follows the formats and rules established in SAE J2540 in the expressions, manipulations, and use of such tables. It should be pointed out that within the rules established by this standard, a variety of final tables are all considered “conformant” with the standard, and may vary as fits the needs of implementers.
V2X Core Technical Committee
This document sets forth general, functional, procedural, and design criteria and recommendations concerning human engineering of data link systems. The recommendations are based on limited evidence from empirical and analytic studies of simulated data link communication, and on experience from operational tests and actual use of data link. However, because data are not yet available to support recommendations on all potentially critical human engineering issues these recommendations necessarily go beyond the data link research and include requirements based on related research and human factors engineering practice. It is also recognized that evolution of these recommendations will be appropriate as experience with data link accumulates and new applications are implemented. This document focuses primarily on recommendations for data link communications between an air traffic specialist and a pilot, i.e., air traffic services communications, although some recommendations address use of data link for flight information services. Unless otherwise specified within the text, all recommendations apply to both flight deck and ground-based data link systems. This document is intended as a guide for development and evaluation of data link systems. Human engineering considerations are an important element of data link system performance. As illustrated in Figure 1, human engineering recommendations address many component functions required for effective data link communication services in the operational environment. For presentation purposes, the recommendations are divided into five sections: General, functional, procedures, flight deck/air traffic service (ATS) workstation integration, and human-computer interface. To facilitate understanding and use of this document appropriate cross-references to interrelated recommendations appear in parentheses throughout the text.
G-10 Executive Advisory Group
This document is not a standard, it is a candidate for a standard being submitted to SAE for their consideration as a comment to SAE J2735. The term SAE J2735 SE candidate is used within this document to refer to this submission. This document specifies dialogs, messages, and the data frames and data elements that make up the messages specifically for use by applications intended to utilize the 5.9 GHz Dedicated Short Range Communications for Wireless Access in Vehicular Environments (DSRC/WAVE, referenced in this document simply as “DSRC"), communications systems. Although the scope of this Standard is focused on DSRC, these dialogs, messages, data frames and data elements have been designed, to the extent possible, to be of use for applications that may be deployed in conjunction with other wireless communications technologies. This standard therefore specifies the definitive message structure and provides sufficient background information to allow readers to properly interpret the message definitions from the point of view of an application developer implementing the messages according to the DSRC Standards.
V2X Communications Steering Committee
This SAE Aerospace Information Report (AIR) reviews technical, operational, and maintenance data being exchanged between key stakeholders in aerospace asset lifecycle and data standards available for such exchanges. It identifies gaps and non-availability of data standards in certain areas. The scope of the current document is limited to aircraft operations, maintenance and disposal stages post-build phase, and does not include the detailed interactions during the aircraft build phase.
G-31 Electronic Transactions for Aerospace Committee
Items per page:
1 – 50 of 2253