Browse Topic: Vehicle networking

Items (688)

Improving Speed Trajectory Optimization for Electric Vehicles with Pre-Calculated Energy Maps and Dynamic Profile Discretization

2025-01-0318To be published on 07/02/2025

Ongoing research and development in the field of electric vehicles (EVs) have resulted in a continuous expansion of their range. Additionally, advancements in vehicle connectivity have created new opportunities for intelligent driving assistance and energy optimization, particularly through the use of cloud data. However, the integration of eco-driving assistance with numerical optimization of speed trajectories remains challenging due to the high computational demands of these methods. To address this challenge and make such a system feasible for integration into vehicle systems, the computational effort required for an optimized driving trajectory must be minimized. This paper presents a method to accelerate speed trajectory optimization using pre-calculated energy and time consumption maps. For this purpose, a dynamic discretization of the anticipated driving profile is applied. Initial results show a substantial reduction in computation time, varying with different scenarios

Schilling Johnson, Rene, Henke, Markus

IEEE-1394b Interface Requirements for Military and Aerospace Vehicle Applications

AS5643B (Current)

04/28/2025

IEEE-1394b, Interface Requirements for Military and Aerospace Vehicle Applications, establishes the requirements for the use of IEEE Std 1394™-2008 as a data bus network in military and aerospace vehicles. The portion of IEEE Std 1394™-2008 standard used by AS5643 is referred to as IEEE-1394 Beta (formerly referred to as IEEE-1394b.) It defines the concept of operations and information flow on the network. As discussed in 1.4, this specification contains extensions/restrictions to “off-the-shelf” IEEE-1394 standards and assumes the reader already has a working knowledge of IEEE-1394. This document is referred to as the “base” specification, containing the generic requirements that specify data bus characteristics, data formats, and node operation. It is important to note that this specification is not designed to be stand-alone; several requirements leave the details to the implementations and delegate the actual implementation to be specified by the network architect/integrator for a

AS-1A Avionic Networks Committee

Verification Methods for AS5653 Network Terminal

AS6088 (Current)

04/25/2025

This document was prepared by the SAE AS-1A2 Committee to establish techniques for validating the Network Terminal (NT) complies with the NT requirements specified in AS5653, Revision B. Note that this verification document only verifies the specific requirements from AS5653 and does not verify all 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.

AS-1A Avionic Networks Committee

Test Plan/Procedure for AS5643 IEEE-1394b Interface Requirements for Military and Aerospace Vehicle Applications

AS5657 (Current)

04/25/2025

This document establishes test plans/procedures for the AS5643 Standard that by itself defines guidelines for the use of IEEE-1394b as a data bus network in military and aerospace vehicles. This test specification defines procedures and criteria for testing device compliance with the AS5643 Standard.

AS-1A Avionic Networks Committee

Verification Methods for AS5653 Network Controller, Network Terminal, and Switch Physical Layer

AS6260 (Current)

04/25/2025

This document was prepared by the SAE AS-1A2 Committee to establish techniques for verifying that Network Controllers (NCs), Network Terminals (NTs), switches, cables, and connectors comply with the physical layer requirements specified in AS5653B. Note that this verification document only verifies the specific requirements from AS5653B and does not verify all of the requirements invoked by documents that are referenced by AS5653B. The procuring authority may require further testing to verify the requirements not explicitly defined in AS5653B and in this verification document.

AS-1A Avionic Networks Committee

J1939 Enhanced DBC

J1939DBC-20250304/22/2025

The SAE J1939 Enhanced DBC file contains decoding rules for converting raw J1939 data to 'physical values' (Mph, %, etc.). This file lets you easily decode data from heavy duty vehicles (trucks, buses, tractors, etc.). This DBC file download includes: The SAE J1939 Enhanced DBC file with Includes 2,400+ Parameter Group Numbers (PGNs) and 16,000+ Suspect Parameter Numbers (SPNs), derived from the J1939 Digital Annex (DA) released in March 2025. One legal license (1 user, 1 PC) matching the DA license DECODE J1939: Convert J1939 data in wide range of software/API tools Combines the J1939DBC and J1939-73DBC files into a single resource REVIEW FIRST: Use our CAN ID converter to check if your PGNs are covered CROWD INPUT: Benefit from free corrections based on large user base SAVE HOURS: Avoid manually constructing the DBC file from scratch Improved Accuracy & Reliability A fully standardized DBC file ensures precise signal decoding, eliminating errors and ensuring reliable data

Designing Software for SAE J1939 ECUs to Improve Cybersecurity

2025-01-8082

04/01/2025

SAE J1939 is a CAN-based standard used for connecting various ECUs together within a vehicle. There are also some related protocols sharing many of the features of SAE J1939 across other industries including ISO11783, RVC and NMEA 2000. The standard has enabled the easy integration of electronic devices into a vehicle. However, as with all CAN-based protocols, several vulnerabilities to cyberattacks have been identified and are discussed in this paper. Many are at the CAN-level, whilst others are in common with those protocols from the SAE J1939 family of protocols. This paper reviews the known vulnerabilities that have been identified with the SAE J1939 protocol at CAN and J1939-levels, along with proposed mitigation strategies that can be implemented in software. At the CAN-level, the weaknesses include ways to spoof the network by exploiting parts of the protocol. Denial of Service is also possible at the CAN-level. At the SAE J1939-level, weaknesses include Denial of Service type

Quigley, Christopher

A Time-Aware Shaper-Based Method for Addressing Traffic Bursts and out-of-Order Induced by IEEE 802.1CB in in-Vehicle Networks

2025-01-8079

04/01/2025

The trends of intelligence and connectivity are continuously driving innovation in automotive technology. With the deployment of more safety-critical applications, the demand for communication reliability in in-vehicle networks (IVNs) has increased significantly. As a result, Time-Sensitive Networking (TSN) standards have been adopted in the automotive domain to ensure highly reliable and real-time data transmission. IEEE 802.1CB is one of the TSN standards that proposes a Frame Replication and Elimination for Reliability (FRER) mechanism. With FRER, streams requiring reliable transmission are duplicated and sent over disjoint paths in the network. FRER enhances reliability without sacrificing real-time data transmission through redundancy in both temporal and spatial dimensions, in contrast to the acknowledgment and retransmission mechanisms used in traditional Ethernet. However, previous studies have demonstrated that, under specific conditions, FRER can lead to traffic bursts and

Luo, Feng, Ren, Yi, Zhu, Yian, Wang, Zitong, Guo, Yi, Yang, Zhenyu

J1939 Digital Annex

J1939DA_202503 (Current)03/31/2025

This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and searched for easier use.

Truck and Bus Control and Communications Network Committee

Security Recommendations for Interfaces to On-Vehicle Networks

J1939-91A (Current)

03/19/2025

This document provides recommendations to vehicle manufacturers, ECU developers, and other device suppliers in securing the SAE J1939 network from cybersecurity risks. This document focuses on security measures related to on-vehicle network architecture and security measures for communication interfaces between devices, ECUs, or networks. The focus is on security related to network communications on the vehicle side of off-vehicle interfaces, such as the SAE J1939-13 connector. The recommendations in this document aim to address cybersecurity risks presented by communication between the vehicle and the rest of the supporting ecosystem via the vehicle networks. The risk focus is on safety and operational risks, although other risks are possible. This document should be used as a reference to current best practices for addressing off-vehicle communication security. This document focuses on recommendations related to the Secure Architecture and Secure Connectivity aspects of vehicle

Truck and Bus Control and Communications Network Committee

Digital Annex of Medium/Heavy-Duty E/E Systems Diagnosis Nomenclature

J2403DA_202503 (Current)03/10/2025

This document is intended to supplement SAE J2403 by providing the content of Table 1, Table 2, and Table 3 from SAE J2403 in a form that can be sorted and searched for easier use. It is NOT intended as a substitute for the actual document, and any discrepancies between this Digital Annex and the published SAE J2403 document must be resolved in favor of the published document. This document provides the content of Table 1 and Table 2 published in SAE J2403 into the single table in the 'Term' tab, while the 'Recommended Term Definitions' tab provides the content of Table 3 in SAE J2403 and the 'Glossary' tab provides the content of Table 4 in SAE J2403.

Truck and Bus Control and Communications Network Committee

Vehicle Application Layer

J1939/71_202502 (Current)02/25/2025

The SAE J1939 communications network is developed for use in heavy-duty environments and is 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 is the SAE J1939 reference document describing SAE J1939 parameter (SP) and message (PG) definitions, SLOT (standard data encoding) definitions, conventions and notations used to specify the parameter (SP) placement in PG data, conventions for text data parameters, and conventions for PG transmission rates. This document previously contained the majority of the SAE J1939 OSI application layer data parameters and messages for

Truck and Bus Control and Communications Network Committee

In-Vehicle Network Anomaly Detection Based on a Graph Attention Network

12-08-04-0034

01/10/2025

The increased connectivity of vehicles expands the attack surface of in-vehicle networks, enabling attackers to infiltrate through external interfaces and inject malicious traffic. These malicious flows often contain anomalous semantic information, potentially leading to misleading control instructions or erroneous decisions. While most semantic-based anomaly detection methods for in-vehicle networks focus on extracting semantic context, they often overlook interactions and associations between multiple semantics, resulting in a high false positive rate (FPR). To address these challenges, the Adaptive Structure Graph Attention Network Model (AS-GAT) is proposed for in-vehicle network anomaly detection. Our approach combines a semantic extractor with a continuously updated graph structure learning method based on attention weight similarity constraints. The semantic extractor identifies semantic features within messages, while the graph structure learning module adaptively updates the

Luo, Feng, Luo, Cheng, Wang, Jiajia, Li, Zhihao

J1939 Digital Annex

J1939DA_202412 (Historical)12/29/2024

This document is intended to supplement the J1939 documents by offering the J1939 information in a form that can be sorted and searched for easier use.

Truck and Bus Control and Communications Network Committee

A Fuzz Testing Method Based on DDPM for Intelligent Connected Vehicles CAN Communication

2024-01-7044

12/13/2024

Modern vehicles are increasingly integrating electronic control units (ECUs), enhancing their intelligence but also amplifying potential security threats. Vehicle network security testing is crucial for ensuring the safety of passengers and vehicles. ECUs communicate via the in-vehicle network, adhering to the Controller Area Network (CAN) bus protocol. Due to its exposed interfaces, lack of data encryption, and absence of identity authentication, the CAN network is susceptible to exploitation by attackers. Fuzz testing is a critical technique for uncovering vulnerabilities in CAN network. However, existing fuzz testing methods primarily generate message randomly, lacking learning from the data, which results in numerous ineffective test cases, affecting the efficiency of fuzz testing. To improve the effectiveness and specificity of testing, understanding of the CAN message format is essential. However, the communication matrix of CAN messages is proprietary to the Original Equipment

Shen, Lin, Xiu, Jiapeng, Zhang, Zhuopeng, Yang, Zhengqiu

The Software-defined Vehicle: Its Current Trajectory and Execution Challenges

EPR2024027

11/25/2024

Original equipment manufacturers, Tier 1 suppliers, and the rest of the value chain, including the semiconductor industry, are reshaping their product portfolios, development processes, and business models to support this transformation to software-defined vehicles (SDVs). The focus on software is rippling out through the automotive sector, forcing the industry to rethink organization, leadership, processes, and future roadmaps. The Software-defined Vehicle: Its Current Trajectory and Execution Challenges assesses the state of SDVs and explores the potential hurdles to execution and examines the work being done in the industry. The goal is to evaluate whether the implementation of SDVs will encounter the same fate as electrification or autonomous technologies, which after some level of disillusionment, are expected to pick up momentum in a more mature way. Click here to access the full SAE EDGETM Research Report portfolio.

Goswami, Partha

Cyber Security Challenges in V2C and in Vehicle Network

2024-28-0035

10/17/2024

Based on advanced Automotive functionality, Vehicle networks has enabled the exchange of data to multiple domains and to meet these demands, more complex software applications, some of which require service-based cloud are developed. Exposure of data creates multiple threats for attacker to tamper security and privacy. Automotive cybersecurity topic has gained momentum based on multiple gaps identified in Automotive In vehicle and around the vehicle networks. In this paper, we provide an extensive overview on V2C (Vehicle to Cloud) and In-vehicle data protection, we also highlight methods to identify threats on any vehicle network connected to V2C and identify methods to verify security functionality using Fuzz or Penetration test protocol, we have identified gaps in existing security solutions and outline possible open issues and probable solution.

Panda, Jyotiprakash, Jain, Rushabh Deepakchand

Inline Optical Power Monitoring, Network End-to-End Data Link Evaluation System

AIR6552/1 (Current)10/07/2024

This document establishes methods to obtain, store, and access data about the health of a fiber optic network using commercially available inline optical power monitoring sensors. This document is intended for: Managers Engineers Technicians Contracting officers Third party maintenance agencies Quality assurance

AS-3 Fiber Optics and Applied Photonics Committee

J1939 Digital Annex

J1939DA_202409 (Historical)09/30/2024

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

Truck and Bus Control and Communications Network Committee

2.5/5/10GBASE-T1 Shielded Balanced Single Pair Ethernet Cable

J3117/3_202409 (Current)09/10/2024

This standard covers a single shielded balanced pair (twisted or parallel) jacketed data cable intended for use in surface vehicle cables for 2.5, 5, and 10 Gb/s Ethernet applications. The tests in this standard are intended to qualify cables for normal operation in an automotive environment while maintaining the necessary electrical properties for reliable data transmission.

Cable Standards Committee

Research on Automated Testing of In-Vehicle Time-Sensitive Network Time Synchronization Mechanism

12-07-04-0027

08/21/2024

With the development of automotive intelligence and networking, the communication architecture of automotive network is evolving toward Ethernet. To improve the real-time performance and reliability of data transmission in traditional Ethernet, time-sensitive network (TSN) has become the development direction of next-generation of automotive networks. The real-time advantage of TSN is based on accurate time synchronization. Therefore, a reliable time synchronization mechanism has become one of the key technologies for the application of automotive Ethernet technology. The protocol used to achieve accurate time synchronization in TSN is IEEE 802.1AS. This protocol defines a time synchronization mechanism suitable for automotive Ethernet. Through the master clock selection algorithm, peer link delay measurement, and clock synchronization and calibration mechanism, the time of each node in the vehicle network is synchronized to a reference master clock. In addition, the protocol clearly

Guo, Yi, Luo, Feng, Wang, Zitong, Gan, Haotian, Wu, Mingzhi, Liu, Hongqian

Engineering Autonomous Mobility: Wired and Wireless CAN Bus Design Principles

14-14-01-0002

07/15/2024

The controller area network (CAN) bus, the prevailing standard for in-vehicle networking (IVN), has been used for more than four decades, despite its simple architecture, to establish communications between electronic control units (ECUs). Weight, maintenance overheads, improved flexibility, and wiring complexity escalate as the quantity of ECUs rises, especially for high-demand autonomous vehicles (AVs). The primary objective of this study is to examine and discuss the significant challenges that arise during the migration from a wired CAN to a wireless CAN (WCAN). Suggested remedies include changing the configuration of the conventional ECU, creating a hidden wireless communication domain for each AV, and developing a plan to counteract the jamming signals. The simulation of the proposed WCAN was done using MATLAB and validated using OPNET analysis. The results showed that the packet loss of the eavesdropping electronic control unit ranged from 63% to 100%. Anti-jamming results show

Ali, Zeina, Ibrahim , Qutaiba

J1939 Digital Annex

J1939DA_202406 (Historical)06/25/2024

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

Truck and Bus Control and Communications Network Committee

PRODUCT SHOWCASE

24TOFHP06_05

06/01/2024

Axiomatic AX141155, compact CAN-Bluetooth® Low Energy Converter, is IP67-rated, CE, FCC, and vibration compliant for off-highway. Operate in SAE J1939 interface or CAN (protocol independent) Bridge modes. Power from 12V, 24V or 48Vdc and temperature range from 30 to +85°C. Configure via the Axiomatic CAN2BT app on compatible Apple iOS or Android devices. axiomatic.com

Vehicle Experience and Human Interaction: Vol. 1

EPRCOMPV172023

05/03/2024

Connected and autonomous vehicles (CAVs) and their productization are a major focus of the automotive and mobility industries as a whole. However, despite significant investments in this technology, CAVs are still at risk of collisions, particularly in unforeseen circumstances or “edge cases.” It is also critical to ensure that redundant environmental data are available to provide additional information for the autonomous driving software stack in case of emergencies. Additionally, vehicle-to-everything (V2X) technologies can be included in discussions on safer autonomous driving design. Recently, there has been a slight increase in interest in the use of responder-to-vehicle (R2V) technology for emergency vehicles, such as ambulances, fire trucks, and police cars. R2V technology allows for the exchange of information between different types of responder vehicles, including CAVs. It can be used in collision avoidance or emergency situations involving CAV responder vehicles. The

Abdul Hamid, Umar Zakir, Roth, Christian, Nickerson, Jeffrey, Lyytinen, Kalle, King, John Leslie

NXP S32 CoreRide Platform simplifies development of software-defined vehicles

24AUTD05_10

05/01/2024

A new industry-first open platform for developing the software-defined vehicle (SDV) combines processing, vehicle networking and system power management with integrated software. NXP Semiconductors' new S32 CoreRide Platform was designed to run “multiple time-critical, safety-critical, security-critical applications in parallel,” Henri Ardevol, executive vice president and general manager of Automotive Embedded Systems for NXP Semiconductors, told SAE Media. NXP's new foundation platform for SDVs differs from the traditional approach of using multiple electronic control units (ECUs), each designed to handle specific vehicle system control tasks. Since each unit requires its own integration work, the integration workload exponentially increases with each additional ECU on a vehicle.

Buchholz, Kami

J1939 Digital Annex

J1939DA_202404 (Historical)04/10/2024

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

Truck and Bus Control and Communications Network Committee

Vehicle E/E Architecture and Key Technologies Enabling Software-Defined Vehicle

2024-01-2035

04/09/2024

The automotive industry is currently undergoing a significant transformation characterized by technological and commercial trends involving autonomous driving, connectivity, electrification, and shared service. Vehicles are becoming an integral part of a much broader ecosystem. In light of various new developments, the Software-Defined Vehicle (SDV) concept is gaining substantial attention and momentum. SDV emphasizes the central role of software in realizing and enhancing vehicle functions, enriching features, improving performance, adapting to surrounding environment and external conditions, customizing user experience, addressing changing customer needs, and enabling vehicles to dynamically evolve over their entire life cycle. The advancements in vehicle Electrical/Electronic (E/E) architecture and various key technologies serve as the technical foundation for the emergence of SDV. This paper gives a definition of the SDV concept, provides views from different aspects, discusses the

Jiang, Shugang

Security Requirements for Vehicle Security Gateways

2024-01-2806

04/09/2024

The NMFTA’s Vehicle Cybersecurity Requirements Woking Group (VCRWG), comprised of fleets, OEMs and cybersecurity experts, has worked the past few years to produce security requirements for Vehicle Network Gateways. Vehicle Network Gateways play an important role in vehicle cybersecurity – they are the component responsible for assuring vehicle network operations in the presence of untrustworthy devices on the aftermarket or diagnostics connectors. This paper offers security requirements for these gateways in design, implementation and operation. The requirements are specified at levels of abstraction applicable to all vehicle networks down to CAN networks specifically. These requirements were captured using the https://github.com/strictdoc-project/strictdoc requirements management tool and will be made available also as a ReqIF format along with the paper at https://github.com/nmfta-repo/vcr-experiment.

Gardiner, Ben, Maag, John, Tindell, Ken

Structural Validation and Correlation of Inverter Gasket

2024-01-2744

04/09/2024

Inverter is the power electronics component that drives the electrical motor of the electrical driven compressor (EDC) and communicates with the car network. The main function of the inverter is to convert the direct current (DC) voltage of the car battery into alternating current (AC) voltage, which is used to drive the three-phase electric motor. In recent days, inverters are present in all automotive products due to electrification. Inverter contains a printed circuit board (PCB) and electronic components, which are mounted inside a mechanical housing and enclosed by a protective cover. The performance of the electrical drive depends upon the functioning of the inverter. There is a strong demand from the customer to withstand the harsh environmental and testing conditions during its lifetime such as leakage, dust, vibration, thermal tests etc. The failure of the inverter leads to malfunction of the product, hence proper sealing and validation is necessary for inverters to protect

Duraipandi, Arumuga Pandian, Leon, Renan, Ribot, Herve, Raja, Antony Vinoth, Farooqui, Altafhussain, Chandrasekaran, Vinoth-Roy

A Zero Trust Architecture for Automotive Networks

2024-01-2793

04/09/2024

Since the early 1990’s, commercial vehicles have suffered from repeated vulnerability exploitations that resulted in a need for improved automotive cybersecurity. This paper outlines the strategies and challenges of implementing an automotive Zero Trust Architecture (ZTA) to secure intra-vehicle networks. Zero Trust (ZT) originated as an Information Technology (IT) principle of “never trust, always verify”; it is the concept that a network must never assume assets can be trusted regardless of their ownership or network location. This research focused on drastically improving security of the cyber-physical vehicle network, with minimal performance impact measured as timing, bandwidth, and processing power. The automotive ZTA was tested using a software-in-the-loop vehicle simulation paired with resource constrained hardware that closely emulated a production vehicle network. For example, the vehicle’s Advanced Gateway electronic control unit (ECU) is utilized to enforce cyber policy

Shipman, Maggie E., Millwater, Nathan, Owens, Kyle, Smith, Seth

Modelling and Analysis of a Cooperative Adaptive Cruise Control (CACC) Algorithm for Fuel Economy

2024-01-2564

04/09/2024

Connectivity in ground vehicles allows vehicles to share crucial vehicle data, such as vehicle acceleration and speed, with each other. Using sensors such as radars and lidars, on the other hand, the intravehicular distance between a leader vehicle and a host vehicle can be detected. Cooperative Adaptive Cruise Control (CACC) builds upon ground vehicle connectivity and sensor information to form convoys with automated car following. CACC can also be used to improve fuel economy and mobility performance of vehicles in the said convoy. In this paper, a CACC system is presented, where the acceleration of the lead vehicle is used in the calculation of desired vehicle speed. In addition to the smooth car following abilities, the proposed CACC also has the capability to calculate a speed profile for the ego vehicle that is fuel efficient, making it an Ecological CACC (Eco-CACC) model. Simulations were run to model and test the Eco-CACC algorithms with different lead vehicle driving behaviors

Kavas-Torris, Ozgenur, Guvenc, Levent

J1939 Digital Annex

J1939DA_202402 (Historical)02/08/2024

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

Truck and Bus Control and Communications Network Committee

SAE J1939 Network Compliance

J1939/82_202312 (Current)12/14/2023

SAE J1939-82 compliance describes the compliance tests and procedures to verify an SAE J1939 electronic control unit (ECU) operates correctly on a SAE J1939 network. The purpose of these compliance procedures is to generate one or more test documents that outline the tests needed to assure that an ECU that is designed to operate as a node on a SAE J1939 network would do so correctly. SAE does not certify devices and these tests and their results do not constitute endorsement by SAE of any particular ECU. These tests are presented to allow testing of an ECU to determine self-compliance by the manufacturer of an ECU. The manufacturer can use its record of what procedures were run successfully to show the level of compliance with SAE J1939.

Truck and Bus Control and Communications Network Committee

Agricultural Forestry Off-Road Machinery Control and Communication Network

J1939-02_202311 (Historical)11/03/2023

Truck and Bus Control and Communications Network Committee

Power Line Carrier Communications for Commercial Vehicles

J2497_202311 (Current)

11/01/2023

This SAE Recommended Practice defines a method for implementing a bidirectional, serial communications link over the vehicle power supply line among modules containing microcomputers. This document defines those parameters of the serial link that relate primarily to hardware and software compatibility such as interface requirements, system protocol, and message format that pertain to Power Line Communications (PLC) between Tractors and Trailers. This document defines a method of activating the trailer ABS Indicator Lamp that is located in the tractor.

Truck and Bus Control and Communications Network Committee

J1939-73 Digital Annex DBC

J1939-73DBC10/11/2023

J1939-73 DBC File - Heavy Duty Diagnostics (DM1, DM2, ...) The SAE J1939-73 DBC file contains decoding rules for converting 'version 4' J1939 diagnostic messages (DM1, DM2, ...) to 'physical values'. This lets you identify issues in e.g. trucks, tractors and buses. DBC is a CAN database format used in most automotive tools.

J1939 Digital Annex

J1939DA_202310 (Historical)10/05/2023

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

Truck and Bus Control and Communications Network Committee

Utilization of Waste Electricity in Microgrid Environments

2023-01-1507

09/05/2023

With the increased demand for electricity due to the rapid expansion of EV charging infrastructure, weather events, and a shift towards smaller, more environmentally responsible forms of renewable sources of energy, Microgrids are increasing in growth and popularity. The integration of real time communication between all PGSs (Power Generating Sources) and loadbanks has allowed the re-utilization of waste electricity. Pop-up Microgrids in PSPS events have become more popular and feasible in providing small to medium size transmission and distribution. Due to the differing characteristics of the PGSs, it is a challenge to efficiently engage the combined PGSs in harmony and have them share and carry the load of the microgrid with minimal ‘infighting.’ Different Power generating sources each have their own personality and unique ‘quirks.’ With loadbanks being able to perform various functions automatically by monitoring and responding to individual PGSs needs and demands, efficiency is

Tyne, Shelby

Cybersecurity for Propulsion Systems

AIR7368 (Current)

09/05/2023

The purpose of this SAE Aerospace Information Report (AIR) is to provide guidance for aircraft engine and propeller systems (hereafter referred to as propulsion systems) certification for cybersecurity. Compliance for cybersecurity requires that the engine control, propeller control, monitoring system, and all auxiliary equipment systems and networks associated with the propulsion system (such as nacelle systems, overspeed governors, and thrust reversers) be protected from intentional unauthorized electronic interactions (IUEI) that may result in an adverse effect on the safety of the propulsion system or the airplane. This involves identification of security risks, their mitigation, verification of protections, and their maintenance in service. This document is intended to serve as suitable guidance for propulsion system manufacturers and applicants for propulsion system type certification. It is also intended to provide guidance for subsequent propulsion system integration into

E-36 Electronic Engine Controls Committee

How Thunderbolt 4 Helps Bring Fault-Tolerant, Distributed Systems to Market

23AERP09_01

09/01/2023

In an embedded world gone SOSA sensational, one might believe that centralized ATR-style OpenVPX systems are the best way to architect your next rugged system. While these chassis are routinely and successfully deployed on airborne, shipboard, and vetronics platforms, they are big, heavy, costly, and a real challenge to cool and connect. An alternate but equivalent rugged, deployable approach uses one or more small form factor chassis modules, distributed into any available space in the vehicle, interconnected via Apple® and Intel's® 40Gbps Thunderbolt™ 4, a commercial open standard that uses USB Type-C connectors with a single, thin bi-directional copper or fiber cable. With 4, 8, even 16 3U or 6U LRU (line replacement unit) boards inside an ATR chassis, 600 watts is on the low end of systems that can push well over 2,000 watts in a 200 square inch footprint or less. Assuming one can find the space for such a chassis in the vehicle or platform, there's also the issue of cooling it

Q&A

23AUTP09_15

09/01/2023

Elektrobit CEO discusses the landscape of automotive software development and explains why a lot of software doesn't have to be all that transformational. The phrase “software-defined vehicle” has embedded in the vehicle-development lexicon as the catchall for a new era of digitally driven products. But there is persistent disagreement about even the phrase's definition, much less the engineering scope required to transition from the industry's hardware-intensive history to a software-driven environment.

ADVANCED MODULAR VEHICLE ARCHITECTURES AND CYBER RESILIANCE IN THE SOFTWARE DEFINED VEHICLE

2024-01-4035

08/10/2023

ABSTRACT Automotive electrical/electronic (E/E) architectures are continuously evolving to meet the technological challenges of the highly connected, software-defined vehicle. Advances are being made in µController/µProcessor compute hardware, software, and cyber security methodologies, to provide enhanced security, safety, flexibility and functionality. These advancements will mature through millions of miles of road/lab testing and reach TRLs suitable for use by the Army to implement safe and secure cyber-resilient platforms for manned and unmanned ground vehicle systems. This paper will describe three specific advances that will benefit Army vehicle programs of the future: Software that leverages the Modular Open Systems Approach (MOSA) as a secure and flexible Service Oriented Architecture (SOA) framework; Hardware-based Communication Engines for high bandwidth/low latency network communications; and a Hardware Security Module (HSM) that enhances the cyber-resilience of the next

Cates, Jamey, Nielson, Karl, Stempnik, Joe

Adaptive Headlamp and Side Mirror Using Linear Regression Based on Raspberry Pi3

SAE-PP-0035007/31/2023

The greatest number of fatal traffic accidents occurs on curved roads at nighttime. In most cases, the late recognition of objects in the traffic zone plays an important role. This highlights to the importance of the role of automobile forward lighting systems. This paper developed a proto-type auto adjustable headlamp and mirror tilt to improve cost and reliability. Also, an adaptive mirror is implemented to remove the blind spots while taking turns. The methodology used here adaptive headlamps and mirrors are developed using Raspberry Pi3 as hardware and Python is used as programming language. Machine learning algorithm “Linear regression” is used for computing the output. Machine Learning Linear regression is considered here as it simple and efficient algorithm in terms of implementation and memory usage. Easily available components like Raspberry Pi3, LDR Sensor, ADXL Gyroscope are used and the design is developed to provide the steering mechanism for the headlamps and mirror which

Ekatpure, Rahul

Vehicle Electronic Programming Stations (VEPS) System Specification for Win32®

J2461_202307 (Current)

07/31/2023

SAE J2461 specifies the recommended practices of a Vehicle Electronics Programming Stations (VEPS) architecture.in a Win32® environment. This system specification, SAE J2461, was a revision of the requirements for Vehicle Electronics Programming Stations (VEPS) set forth in SAE J2214, Vehicle Electronics Programming Stations (VEPS) System Specification for Programming Components at OEM Assembly Plants (Cancelled Jun 2004). The J2214 standard has been cancelled indicating that it is no longer needed or relevant.

Truck and Bus Control and Communications Network Committee

J1939 Digital Annex

J1939DA_202307 (Historical)07/31/2023

This document is intended to supplement the SAE J1939 documents by offering the SAE J1939 information in a form that can be sorted and search for easier use.

Truck and Bus Control and Communications Network Committee

Un-Shielded Balanced Single Twisted Pair Ethernet Cable

J3117_202307 (Current)07/10/2023

This document covers un-shielded balanced single twisted pair data cable intended for use in surface vehicle cables for 100 Mbps Ethernet applications. The tests in this document are intended to qualify cables for normal operation in an automotive environment while maintaining the necessary electrical properties for reliable data transmission.

Cable Standards Committee

Low Voltage Ultra-Thin Wall Primary Cable

J1678_202306 (Current)

06/19/2023

This standard covers ultra-thin wall low voltage primary cable intended for use at a nominal system voltage of 60 VDC (60 VAC rms) or less in surface vehicle electrical systems. The tests are intended to qualify cables for normal applications with limited exposure to fluids and physical abuse. This standard covers SAE conductor sizes which usually differ from ISO conductor sizes.

Cable Standards Committee

Network Layer

J1939/31_202306 (Current)06/06/2023

SAE J1939-31 network layer describes the requirements and services for network interconnection ECUs (NIECU) that enable electronic control units (ECUs) on an SAE J1939 network segment to intercommunicate with other ECUs on different network segments of the vehicle or system network. This document defines various types of NIECUs. The information in this document applies only to ECUs that are intended to provide networking services. It is not necessary for an ECU to provide any of these services in order to be compliant with the SAE J1939 protocol.

Truck and Bus Control and Communications Network Committee

Responder-to-Vehicle Technologies for Connected and Autonomous Vehicles

EPR2023010

05/15/2023

Recently, there has been a slight increase in interest in the use of responder-to-vehicle (R2V) technology for emergency vehicles, such as ambulances, fire trucks, and police cars. R2V technology allows for the exchange of information between different types of responder vehicles, including connected and automated vehicles (CAVs). It can be used in collision avoidance or emergency situations involving CAV responder vehicles. The benefits of R2V are not limited to fully autonomous vehicles (e.g., SAE Level 4), but can also be used in Level 2 CAV scenarios. However, despite the potential benefits of R2V, discussions on this topic are still limited. Responder-to-Vehicle Technologies for Connected and Autonomous Vehicles aims to provide an overview of R2V technology and its applications for CAV systems, particularly in the context of collision avoidance features. The responder vehicles in question can be autonomous or non-autonomous. It is hoped that it will provide valuable information

Abdul Hamid, Umar Zakir

Items per page:

1 – 50 of 688