Browse Topic: Communication protocols

Items (1,010)
Find
Towards a Smarter E-Bike: Enhancing Energy Efficiency through Adaptive Speed Control2026-01-0736To be published on 07/01/2026
This paper presents the development of a speed controller for e-bikes, designed as part of an energy-adaptive assistance system. The controller provides riders with appropriate support along planned routes, based on the available battery capacity. The control concept is intended for integration into existing commercial e-bikes without requiring extensive modifications to the drive system. Therefore, the rider remains part of the control loop, adjusting the support mode according to instructions from the controller. The speed controller is implemented as a rule-based state machine, enabling comprehensible design and parameterization Since the rider must manually switch between support modes while riding, the control logic incorporates hysteresis and dead times to ensure stability, prevent oscillations and avoid frequent mode switching. The user interface is a smartphone application that issues visual and audio instructions for switching support modes. An initial, system-independent
Rauch, Yannick, Simmann, Gabriel, Schneider, Manuel, Goss, Christian, Kriesten, Reiner
Vehicle OBD II Compliance Test CasesJ1699/3_202104 (Historical)5/24/2026
The main purpose of this SAE Recommended Practice is to verify that vehicles are capable of communicating a minimum subset of information in accordance with the diagnostic test services specified in SAE J1979, or the equivalent document ISO 15031-5. Any software meeting these specifications will utilize the vehicle interface that is defined in SAE J2534. SAE J1699-3 tests shall be run using an SAE J2534-1 (API Version 04.04) Interface. However, the use of an SAE J2534-2 (API Version 04.04) Interface shall be permitted if the following conditions are met: The number of 29-bit ISO 15765 OBD ECUs exceeds the capability of the SAE J2534-1 Interface. The SAE J2534-2 Interface meets or exceeds all of the SAE J2534-1 requirements and also supports the SAE J2534-2 feature “Mixed Format Frames on a CAN Network.”
Vehicle E E System Diagnostic Standards Committee
CLASS B DATA COMMUNICATIONS NETWORK INTERFACEJ1850_199507 (Current)5/24/2026
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
Vehicle Architecture For Data Communications Standards
E/E Data Link SecurityJ2186_201907 (Current)5/24/2026
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Vehicle E E System Diagnostic Standards Committee
OBD II Scan Tool — Equivalent to ISO/DIS 15031-4:December 14, 2001J1978_200204 (Historical)5/24/2026
This SAE Recommended Practice supersedes SAE J1978 FEB1998, and is technically equivalent to ISO/DIS 15031-4:December 14, 2001. This document is intended to satisfy the requirements of an OBD scan tool as required by U.S. On-Board Diagnostic (OBD) regulations. The document specifies: a A means of establishing communications between an OBD-equipped vehicle and external test equipment, b A set of diagnostic services to be provided by the external test equipment in order to exercise the services defined in SAE J1979, c Conformance criteria for the external test equipment.
Vehicle E E System Diagnostic Standards Committee
Recommended Practice for Pass-Thru Vehicle ProgrammingJ2534/1_200412 (Current)5/24/2026
This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECUs) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. U.S. Environmental Protection Agency (EPA) and the California Air Resources
Vehicle E E System Diagnostic Standards Committee
OBD-II Scan ToolJ1978_202205 (Historical)5/24/2026
SAE J1978/ISO 15031-4 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which is compliant with SAE J1978/ISO 15031-4. The SAE J1978 content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. on-board diagnostic (OBD) regulations. The ISO 15031-4 content of this document is intended to satisfy the requirements of OBD requirements in countries other than the U.S., and includes functionality not required or not allowed in the U.S. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979/ISO 15031-5. SAE J1978/ISO 15031-4 does not preclude the inclusion of additional capabilities or functions
Vehicle E E System Diagnostic Standards Committee
General Motors UART Serial Data CommunicationsJ2740_201905 (Current)5/24/2026
This Technical Information Report defines the General Motors UART Serial Data Communications Bus, commonly referred to as GM UART. This document should be used in conjunction with SAE J2534-2 in order to enhance an SAE J2534 interface to also provide the capability to program ECUs with GM UART. SAE J2534-1 includes requirements for an interface that can be used to program certain emission-related Electronic Control Units (ECUs) as required by U.S. regulations, and SAE J2534-2 defines enhanced functionality required to program additional ECUs not mandated by current U.S. regulations. The purpose of this document is to specify the requirements necessary to implement GM UART in an enhanced SAE J2534 interface intended for use by independent automotive service facilities to program GM UART ECUs in General Motors vehicles.
Vehicle E E System Diagnostic Standards Committee
Class B Data Communications Network InterfaceJ1850_200606 (Historical)5/24/2026
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On- and Off-Road Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
Vehicle Architecture For Data Communications Standards
Optional Pass-Thru FeaturesJ2534-2_202012 (Current)5/24/2026
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
High-Speed CAN (HSC) for Vehicle Applications at 500 KBPSJ2284/3_200203 (Current)5/24/2026
This SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the ISO model for a 500 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 50 KBPS. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 6 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. This document will address only requirements which may be tested at the ECU and
Vehicle Architecture For Data Communications Standards
E/E Data Link SecurityJ2186_200506 (Current)5/24/2026
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Vehicle E E System Diagnostic Standards Committee
Serial Data Communication InterfaceJ2610_202101 (Current)5/23/2026
The purpose of this SAE Information Report is to specify the requirements necessary to fully define the Serial Data Communication Interface (SCI) used in the reprogramming of emission-related powertrain Electronic Control Units (ECU) in Fiat Chrysler Automobiles (FCA) vehicles. It is intended to satisfy new regulations proposed by the federal U.S. Environmental Protection Agency (EPA) and California Air Resource Board (CARB) regulatory agencies regarding “pass-thru programming” of all On-Board Diagnostic (OBD) compliant emission-related powertrain devices. These requirements are necessary to provide independent automotive service organizations and after-market scan tool suppliers the ability to reprogram emission-related powertrain ECUs for all manufacturers of automotive vehicles. Specifically, this document details the SCI physical layer and SCI data link layer requirements necessary to establish communications between a diagnostic tester and an ECU. It further specifies additional
Vehicle E E System Diagnostic Standards Committee
Keyword Protocol 1281J2818_201905 (Current)5/23/2026
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.
Vehicle E E System Diagnostic Standards Committee
Honda Diagnostic Serial Data Link Protocol - ABS/VSA SystemJ2809_201710 (Current)5/23/2026
This Technical Information Report defines the proprietary diagnostic communication protocol for ABS or VSA ECU (Electronic Control Unit) implemented on some Honda vehicles. This protocol does not apply to all Honda vehicles. This document should be used in conjunction with SAE J2534-2 in order to fully implement the communication protocol in an enhanced SAE J2534 interface. The purpose of this document is to specify the requirements necessary to implement the communication protocol in an enhanced SAE J2534 interface.
Vehicle E E System Diagnostic Standards Committee
TP2.0 Vehicle Diagnostic ProtocolJ2819_201905 (Current)5/23/2026
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.
Vehicle E E System Diagnostic Standards Committee
Class B Data Communications Network InterfaceJ1850_202212 (Historical)5/22/2026
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On-and OffRoad Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
Vehicle Architecture For Data Communications Standards
Recommended Practice for Pass-Thru Vehicle ProgrammingJ2534/1_200411 (Historical)5/22/2026
This SAE Recommended Practice provides the framework to allow reprogramming software applications from all vehicle manufacturers the flexibility to work with multiple vehicle data link interface tools from multiple tool suppliers. This system enables each vehicle manufacturer to control the programming sequence for electronic control units (ECUs) in their vehicles, but allows a single set of programming hardware and vehicle interface to be used to program modules for all vehicle manufacturers. This document does not limit the hardware possibilities for the connection between the PC used for the software application and the tool (e.g., RS-232, RS-485, USB, Ethernet…). Tool suppliers are free to choose the hardware interface appropriate for their tool. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with hardware supplied by any tool manufacturer. U.S. Environmental Protection Agency (EPA) and the California Air Resources
Vehicle E E System Diagnostic Standards Committee
E/E DATA LINK SECURITYJ2186_199610 (Historical)5/22/2026
This SAE Recommended Practice establishes a uniform practice for protecting vehicle components from "unauthorized" access through a vehicle data link connector (DLC). The document defines a security system for motor vehicle and tool manufacturers. It will provide flexibility to tailor systems to the security needs of the vehicle manufacturer. The vehicle modules addressed are those that are capable of having solid state memory contents accessed or altered through the data link connector. Improper memory content alteration could potentially damage the electronics or other vehicle modules; risk the vehicle compliance to government legislated requirements; or risk the vehicle manufacturer's security interests. This document does not imply that other security measures are not required nor possible.
Vehicle E E System Diagnostic Standards Committee
Optional Pass-Thru FeaturesJ2534/2_201010 (Historical)5/21/2026
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 an SAE J2534-1 specification. It is not required for an interface to be fully compliant with 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
Recommended Practice for Pass-Thru Vehicle ProgrammingJ2534/1_201510 (Historical)5/21/2026
This SAE Recommended Practice describes a standardized interface that connects between a standard personal computer (PC) and vehicle. The purpose of this interface is to enable the reprogramming of emission-related control modules, in 2004 and later model year vehicles. The interface shall consist of the necessary hardware and/or software to support the requirements defined in this document. It is expected that vehicle manufacturers will provide the software application that will control the Pass-Thru Interface, to perform the actual reprogramming. The goal of this document is to ensure that reprogramming software from any vehicle manufacturer is compatible with interface supplied by any tool manufacturer. A common interface for all vehicle manufacturers reduces the tool costs for aftermarket garages, while allowing each vehicle manufacturer to control the programming sequence for the electronic control units (ECUs) in their vehicles. Aftermarket garages will be able to obtain a
Vehicle E E System Diagnostic Standards Committee
High-Speed CAN (HSC) for Vehicle Applications at 500 KBPSJ2284/3_201611 (Historical)5/21/2026
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 500 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 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 500 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 (ECU) requirements defined in Section 6 are met, then the system level attributes should be obtainable. This document will address only requirements which may
Vehicle Architecture For Data Communications Standards
Class B Data Communications Network InterfaceJ1850_201510 (Historical)5/21/2026
This SAE Standard establishes the requirements for a Class B Data Communication Network Interface applicable to all On-and OffRoad Land-Based Vehicles. It defines a minimum set of data communication requirements such that the resulting network is cost effective for simple applications and flexible enough to use in complex applications. Taken in total, the requirements contained in this document specify a data communications network that satisfies the needs of automotive manufacturers. This specification describes two specific implementations of the network, based on media/Physical Layer differences. One Physical Layer is optimized for a data rate of 10.4 Kbps while the other Physical Layer is optimized for a data rate of 41.6 Kbps (see Appendix A for a checklist of application-specific features). The Physical Layer parameters are specified as they would be detected on the network media, not within any particular module or integrated circuit implementation. Although devices may be
Vehicle Architecture For Data Communications Standards
High-Speed CAN (HSC) for Vehicle Applications at 500 kbpsJ2284/3_202210 (Historical)5/21/2026
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 500 kbps high-speed CAN (HSC) protocol implementation. Both electronic control unit (ECU) and media design requirements for networks will be specified. Requirements will primarily address the controller area network (CAN) physical layer implementation. Requirements will focus on a minimum standard level of performance from the 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 500 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 ECU requirements defined in Section 6 are met, then the system level attributes should be obtainable. This document will address
Vehicle Architecture For Data Communications Standards
High-Speed CAN (HSC) for Vehicle Applications at 500 KBPSJ2284/3_201003 (Historical)5/20/2026
This SAE Recommended Practice will define the Physical Layer and portions of the Data Link Layer of the ISO model for a 500 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 500 KBPS. The minimum performance level shall be specified by system level performance requirements or characteristics described in detail in Section 6 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. This document will address only requirements which may be tested at the ECU and
Vehicle Architecture For Data Communications Standards
Optional Pass-Thru FeaturesJ2534/2_201901 (Historical)5/19/2026
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 an SAE J2534-1 specification. It is not required for an interface to be fully compliant with 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
E/E Diagnostic Test Modes: OBDonUDSJ1979-2_202604 (Current)5/2/2026
SAE J1979-2 describes the communication between the vehicle’s OBD systems and test equipment required by OBD regulations. OBD regulations require passenger cars and light-, medium-, and heavy-duty trucks to support a minimum set of diagnostic information to external (off-board) “generic” test equipment. To achieve this, SAE J1979-2 is based on the Open Systems Interconnection (OSI) Basic Reference Model in accordance with ISO/IEC 7498-1 and ISO/IEC 10731, which structures communication systems into seven layers. When mapped on this model, the services specified are broken into: Diagnostic services (layer 7), specified in: ISO 14229-1 SAE J1979-2 OBDonUDS Presentation layer (layer 6), specified in: SAE J1930, SAE J1930DA SAE J1979DA SAE J2012, SAE J2012DA SAE J1939DA, SAE J1939-73 Session layer services (layer 5), specified in: ISO 14229-2 Transport layer services (layer 4), specified in: DoCAN: ISO 15765-2 Transport protocol and network layer services ISO 15765-4 Requirements for
Vehicle E E System Diagnostic Standards Committee
OBD-II Scan Tool: First Generation ProtocolsJ1978-1_202604 (Current)4/20/2026
SAE J1978-1 specifies a complementary set of functions to be provided by an OBD-II scan tool. These functions provide complete, efficient, and safe access to all regulated OBD (on-board diagnostic) services on any vehicle which complies to SAE J1979. The content of this document is intended to satisfy the requirements of an OBD-II scan tool as required by current U.S. OBD regulations. This document specifies: A means of establishing communications between an OBD-equipped vehicle and an OBD-II scan tool. A set of diagnostic services to be provided by an OBD-II scan tool in order to exercise the services defined in SAE J1979. In addition, SAE J1978-1 covers first generation protocol functionality defined in SAE J1979 plus automatic protocol determination for all SAE J1979/J1979-2/J1979-3 application content. The presentation of the SAE J1978 document family, where SAE J1978-1 covers first generation protocol functionality defined in SAE J1979 and protocol determination for SAE J1979, SAE
Vehicle E E System Diagnostic Standards Committee
J1939 Digital AnnexJ1939DA_202604 (Current)4/10/2026
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
Embedded Real-Time Control of a Distributed Trailer Propulsion System with Regenerative Braking for Net Neutral Load Towing2026-01-00654/7/2026
Towing imposes substantial efficiency penalties on both battery-electric vehicles (BEVs) and internal combustion engine (ICE) vehicles, reducing range by 30-50%. This paper presents a proof-of-concept embedded control architecture for distributed trailer propulsion that actively regulates drawbar force to reduce towing loads. Unlike proprietary e-trailer systems requiring specialized hardware, the proposed implementation demonstrates feasibility using commercial off-the-shelf (COTS) components and open-source software. The distributed architecture employs dual Raspberry Pi 4B single-board computers communicating via ROS 2 at 20 Hz. The trailer-mounted controller executes a Simulink-generated control node coordinating load cell acquisition (HX711 ADC), motor CAN bus telemetry, and throttle commands to a 5 kW BLDC traction motor powered by a 5 kWh LiFePO4 battery pack. A vehicle-mounted controller logs OBD-II/CAN validation data. The control pipeline implements cascaded EWMA/Hampel
Joshi, Gaurav, Adelman, Ian, Liu, Jun, Donnaway, Ruthie
The Simple Complexity of Reverse Engineering a Vehicle CAN Bus2026-01-00704/7/2026
Automotive Original Equipment Manufacturers (OEMs) closely guard information about their products due to the significant investment in vehicle research and development. However, advancing automotive innovation often requires insights from existing systems to improve safety, efficiency, and performance. The Controller Area Network (CAN) bus remains the industry standard for communication between electronic control units (ECUs), yet CAN message specifications are typically proprietary and undocumented. This paper presents a case study involving the reverse engineering of CAN messages from a 2024 Toyota Grand Highlander powertrain. By capturing and analyzing communication between a diagnostics tester and the vehicle’s ECUs and replicating the communication, substituting A CANcase and software in place of a diagnostics tester, we were able to reverse engineer the vehicle’s CAN bus, demonstrating a practical methodology for decoding and interpreting CAN traffic without prior access to
Bolarinwa, Emmanuel, Peters, Diane
Optimizing Custom Hybrid Solutions for Low-Volume Specialist Equipment2026-01-04794/7/2026
Off-road vehicles are typically powered by diesel engines, sized to cover the highest peak loads in their dutycycles. Such applications can be designed with downsized engines, using hybridization to supplement engine power with electrical power for short periods. However, many applications are low-volume and specialized, making it impractical to deploy heavy engineering resources to optimize each one. For this reason, manufacturers tend to produce maid-of-all-work vehicles to cover every situation. This paper demonstrates the benefits of custom hybridization for specialist applications, and addresses the lack of accessible software tools for evaluating such opportunities. Analysis is applied with a fast, low-cost, Concept-based software tool named “ePOP Concept”, suited to original equipment manufacturers (OEMs) who seek to provide custom low-volume vehicles. It allows many different powertrain architectures to be evaluated rapidly at the product planning stage, and can be quickly set
De Salis, Rupert, Fons, Daniel
A Simple Analytical Model for Predicting Cooperative Ratio in Agreement-Seeking Cooperative Driving Automation with C-V2X Communication2026-01-00784/7/2026
Cooperative Driving Automation (CDA) has emerged as an active research area in recent years, categorized into four classes of operations with varying levels of cooperation as defined in the SAE J3216 standard. Among these, Class C CDA, referred to as Agreement-Seeking Cooperation (ASC), has received limited attention in literature. Unlike Cooperative Adaptive Cruise Control (CACC), which typically engages when lead vehicles are identified as cooperative and disagree under manual override or safety-critical conditions, ASC requires agents to exchange messages interactively to reach consensus on a proposed plan and its implementation. This necessitates more sophisticated communication and control designs, which in turn influences customized ASC efficiency. Previous work has examined, through simulation, the impact of three key parameters on ASC system performance: CDA message transmission frequency, Packet Drop Ratio (PDR), and Cooperation Duration Length (CDL). In this paper, we extend
Zhan, Lu, Di Russo, Miriam, Das, Debashis, Stutenberg, Kevin, Misra, Priyash, Jeong, Jongryeol, Hyeon, Eunjeong
Signal Integrity in Distributed BMS: Reliable SPI and Ethernet Communication for Next-Gen Evs2026-01-01714/7/2026
Distributed battery management systems (BMS) are critical for scaling electric vehicle packs to hundreds of cells, but reliable high-speed communication between modules remains a challenge. Daisy-chained SPI and CAN FD are widely deployed today, while Ethernet is being evaluated for next-generation systems that require higher bandwidth, synchronization, and diagnostics. This paper examines the signal integrity (SI) challenges facing distributed BMS communication, including skew, jitter, crosstalk, and electromagnetic interference (EMI) across PCB traces and wiring harnesses. HyperLynx and SPICE-based simulations are combined with experimental results on a 192-cell test platform to quantify the impact of layout constraints, impedance mismatches, and harness parasitic. Results show that poor SI design can reduce signal margins by more than 18 dB, leading to data corruption and diagnostic failures. Results show poor SI design can reduce signal margins by 18 dB, causing data errors
Abdul Karim, Abdul Salam
Quantifying the Impact of Towing on BEV Energy Use: Instrumented On Road Testing and Chassis Dynamometer Reproduction2026-01-04314/7/2026
Electrification is rapidly entering all vehicle classes, including light- and heavy-duty trucks designed for heavy towing capabilities. Still, the quantitative impact of towing on battery-electric vehicle (BEV) energy use and range remains under-characterized. We conducted controlled towing tests with a Ford F-150 Lightning using two trailers of different sizes and varying payloads to isolate aerodynamic and mass effects and to span the full range of towable payloads within the vehicle’s rated capacity. The vehicle was instrumented at the CAN bus level, capturing motor power, torque, speed, and related internal signals from different control modules. On-road testing consisted of repeated back-and-forth passes on level, straight road segments at set speeds focusing on highway operation, where aerodynamic drag is stronger and real-world towing use cases occur. From these data, we extracted road load equations and dynamometer coefficients for each trailer combination, then reproduced
Timermans Ladero, Inigo
Mitigation of Sensor-Level Cyber-Physical Attacks on Electric Vehicle Powertrains: A Simulation-Based Study2026-01-00914/7/2026
Electric vehicles (EVs) rely extensively on sensor feedback for safe and efficient powertrain operation. However, this dependency introduces cyber-physical vulnerabilities, especially when sensor signals are maliciously manipulated. This paper presents a simulation-based investigation into sensor-level cyberattacks on a mid-sized EV powertrain model developed in MATLAB/Simulink. The study quantifies mechanical consequences and evaluates mitigation strategies to enhance system resilience. Four representative attack scenarios were simulated. Speed sensor spoofing led the controller to misinterpret vehicle velocity, causing a 41% overshoot beyond the 50 km/h setpoint. False data injection into torque/current sensors triggered an unintended torque surge of approximately 20%, resulting in inverter current saturation within 2 seconds. Battery temperature spoofing delayed thermal protection, allowing a deviation of 1.5 °C/min beyond safe operating limits. A hybrid attack combining frozen
Tariq, Usama, Sahandabadi, Sahereh, Dianat, Ali
Application Layer - Generator Sets and IndustrialJ1939/75_202603 (Current)3/19/2026
SAE J1939-75 defines the set of data parameters (SPs) and messages (PGs) for information predominantly associated with monitoring and control generators and driven equipment in electric power generation and industrial applications. The data parameters (SPs) and messages (PGs) previously published within this document are published in SAE J1939DA. Applications using the SAE J1939-75 document must refer to SAE J1939DA for the SAE J1939 parameters and messages for monitoring and controlling the power units, e.g., engines and turbines, that power the generators and driven industrial equipment.
Truck and Bus Control and Communications Network Committee
Serial Control and Communications Heavy-Duty Vehicle Network - Top-Level DocumentJ1939_202603 (Current)3/17/2026
This top-level document provides a general overview of the SAE J1939 network and describes the subordinate document structure. This document includes definitions of terms and abbreviations which are used among the various SAE J1939 subordinate documents.
Truck and Bus Control and Communications Network Committee
J1939 Enhanced DBCJ1939DBC_2026033/10/2026
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 2026. 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
IoT-Enabled Cloud-Integrated Smart Parking System with Real-Time Monitoring and AI-Based Space Optimization for Next-Gen Mobility2026-28-01132/12/2026
This study presents the design and implementation of an advanced IoT-enabled, cloud-integrated smart parking system, engineered to address the critical challenges of urban parking management and next-generation mobility. The proposed architecture utilizes a distributed network of ultrasonic and infrared occupancy sensors, each interfaced with a NodeMCU ESP8266 microcontroller, to enable precise, real-time monitoring of individual parking spaces. Sensor data is transmitted via secure MQTT protocol to a centralized cloud platform (AWS IoT Core), where it is aggregated, timestamped, and stored in a NoSQL database for scalable, low-latency access. A key innovation of this system is the integration of artificial intelligence (AI)-based space optimization algorithms, leveraging historical occupancy patterns and predictive analytics (using LSTM neural networks) to dynamically allocate parking spaces and forecast demand. The cloud platform exposes RESTful APIs, facilitating seamless
Deepan Kumar, Sadhasivam, S, Balakrishnan, Dhayaneethi, Sivaji, Boobalan, Saravanan, Abdul Rahim, Mohamed Arshad, S, Manikandan, R, Jamuna, L, Rishi Kannan
AI Smart Timer-Based Power Control and Energy Monitoring System for Home Appliances2026-28-00602/12/2026
The paper presents the design and implementation of an AI-enabled smart timer-based power control and energy monitoring solution for household appliances. The proposed system integrates real-time sensing of electrical device parameters with cloud artificial intelligence for predictive analytics and automatic control. Continuous measurement of voltage, current and power consumption of the connected appliances are performed for analysis of the usage patterns. The appliance operation is completely automated by choosing between the best option which is the user-defined schedule or the load shifted schedule recommended by AI. The AI recommendation depends on peak demand of the day and the current load requirement thereby aiding approximate smoothening of daily load curve and improving load factor. The data collected is transmitted to the cloud for real-time and historical data collection, for prediction of consumption patterns, anomaly detection, and clustering appliances according to their
D, Anitha, D, Suchitra, Jain, Utsav, Maity, Souvik, Dinda, Atish
Automotive Ethernet Proxy-Based Security Architecture in Vehicle Computers2026-28-01212/12/2026
Modern vehicles require sophisticated, secure communication systems to handle the growing complexity of automotive technology. As in-vehicle networks become more integrated with external wireless services, they face increasing cybersecurity vulnerabilities. This paper introduces a specialized Proxy based security architecture designed specifically for Internet Protocol (IP) based communication within vehicles. The framework utilizes proxy servers as security gatekeepers that mediate data exchanges between Electronic Control Units (ECUs) and outside networks. At its foundation, this architecture implements comprehensive traffic management capabilities including filtering, validation, and encryption to ensure only legitimate data traverses the vehicle's internal systems. By embedding proxies within the automotive middleware layer, the framework enables advanced protective measures such as intrusion detection systems, granular access controls, and protected over-the-air (OTA) update
M, Arvind, Praneetha, Appana Durga, Remalli, Ravi Teja
Assessment of Cybersecurity Risks in State-Operated Connected Electric Passenger Buses in India2026-26-06101/16/2026
State Transport Units (STUs) are increasingly using electric buses (EVs) as a result of India's quick shift to sustainable mobility. Although there are many operational and environmental benefits to this development, like lower fuel prices, fewer greenhouse gas emissions, and quieter urban transportation, there are also serious cybersecurity dangers. The attack surface for potential cyber threats is expanded by the integration of connected technologies, such as cloud-based fleet management, real-time monitoring, and vehicle telematics. Although these systems make fleet operations smarter and more efficient, they are intrinsically susceptible to remote manipulation, data breaches, and unwanted access. This study looks on cybersecurity flaws unique to connected passenger electric vehicles (EVs) that run on India's public transit system. Electric vehicle supply equipment (EVSE), telematics control units (TCUs), over-the-air (OTA) update systems, and in-car networks (such as the Controller
Mokhare, Devendra Ashok
Automotive Cybersecurity: Regulatory Landscape, Type Approval and the Road Ahead2026-26-02461/16/2026
Effective communication is the key for bringing harmony - be it the communication between humans and humans, or communication between machine and machine. Today’s car is a sophisticated gadget, equipped with the best of technologies running using millions of lines of codes of software. The effective use of these technologies involve communication between car to car and car to infrastructure using Dedicated Short-Range Communication (DSRC), C-V2X (Cellular Vehicle-to-Everything). It is pertinent that any communication using the internet needs to be digitally secure and that the systems are designed to mitigate the perceived threats. The methods used for ensuring cyber safety of automobiles need to be verified before the end product is put to use. Automotive Industry Standards AIS-189 and AIS-190 have been formulated to provide a harmonized verification framework. Both the vehicle manufacturer and the test agency need to equip themselves with necessary skills and tools to ensure
Nayak, Pratik, Tandon, Vikram, Badusha, Akbar, Desai, Manoj, Sathianesan, Rejin
Cybersecurity in Electric Vehicle Charging Infrastructure: A Review of Threats, Vulnerabilities, and Mitigation Strategies2026-26-06141/16/2026
The rapid expansion of electric vehicle (EV) charging infrastructure introduces complex cybersecurity challenges across hardware, software, network, and cloud layers. This review paper synthesizes existing research, standards, and documented incidents to identify critical vulnerabilities and propose layered mitigation strategies. We present a structured threat taxonomy based on the STRIDE model, enriched with real-world attack vectors and mapped to mitigation controls. Our analysis spans physical tampering, insecure firmware updates, protocol-level flaws in OCPP and ISO 15118, and cloud misconfigurations. While prior studies often focus on isolated domains, this work unifies fragmented insights into a cohesive framework. We highlight gaps in current literature, such as inconsistent adoption of secure protocols and limited validation of EVSE identity formats. By aligning threats with industry standards (SAE J3061, NIST CSF, IEC 62443) and scoring risks using CVSS v3.1, we offer a
Aggarwal, Akshit, Gupta, Saurabh, Sirohi, Kapil, Arisetty, Venkatesh, Chatterjee, Avik
Automotive Cybersecurity Incident Response (CSIR) Framework and Its Integration into OEM Processes2026-26-06131/16/2026
The exponential growth of connected and autonomous vehicles has significantly escalated cybersecurity threats, compelling automotive Original Equipment Manufacturers (OEMs) to adopt robust and structured Cybersecurity Incident Response (CSIR) capabilities. Current automotive cybersecurity regulations, such as AIS 189 in India and UNECE WP.29 globally, mandate precise frameworks for proactive threat detection, timely response, and comprehensive incident documentation. This research presents an innovative, comprehensive CSIR framework specifically tailored to integrate seamlessly into OEM cybersecurity management processes. Leveraging a combination of real-time monitoring systems, structured threat categorization methodologies, and integrated escalation and communication protocols, the proposed CSIR framework ensures efficient incident handling aligned with stringent regulatory compliance. The framework encompasses advanced methodologies including Vehicle Security Operations Center (VSOC
Chaudhary lng, Vikash, Desai, Manoj, Chatterjee, Avik, Chatterjee lng, Avik
Resilient Design Strategies for Wireless Charger ECUs: A Proactive Threat Analysis and Risk Assessment Framework for Ensuring Cybersecurity in EV Charging Ecosystems2026-26-01731/16/2026
The proliferation of wireless charging technology in electric vehicles (EVs) introduces novel cybersecurity challenges that require comprehensive threat analysis and resilient design strategies. This paper presents a proactive framework for assessing and mitigating cybersecurity risks in wireless charger Electronic Control Units (ECUs), addressing the unique vulnerabilities inherent in electromagnetic power transfer systems. Through systematic threat modeling, vulnerability assessment, and the development of defense-in-depth strategies, this research establishes design principles for creating robust wireless charging ecosystems resistant to cyber threats. The proposed framework integrates hardware security modules, encrypted communication protocols, and adaptive threat detection mechanisms to ensure operational integrity while maintaining charging efficiency. Experimental validation demonstrates the effectiveness of the proposed security measures in preventing unauthorized access, data
Uthaman, Sreekumar, Mulay, Abhijit B, Gadekar, Pundlik
To Study and Compare Communication Protocol for Fast Charging in Electric Two-Wheeler with Respect to CCS 2.0: An Indian Perspective2026-26-01981/16/2026
This comprehensive research presents an in-depth analysis of communication protocols essential for implementing fast charging systems in India's rapidly expanding electric two-wheeler and three-wheeler market. As India witnesses unprecedented growth in electric mobility, with two-wheelers representing over 95% of current EV sales, the establishment of standardized, secure, and efficient charging protocols becomes paramount for widespread adoption. This study examines the current landscape of AC charging methodologies, evaluates the technical and economic feasibility of DC fast charging implementation, and provides detailed comparative analysis of existing international standards including IS 17017-25, IS 17017-31, ChaoJi, and CCS 2.0. The research concludes with strategic recommendations for developing cyber-secure, cost-effective charging infrastructure specifically tailored to meet India's unique market requirements and operational constraints.
Uthaman, Sreekumar, Mulay, Abhijit B
Development of an Optimized XCP Software Stack for Real-Time Validation of Vehicle Control Units Using Next-Generation Communication Protocols2026-26-01901/16/2026
With the rapid adoption of electric vehicles (EVs), ensuring the reliability, safety, and cost-effectiveness of power electronic subsystems such as onboard chargers, DC-DC converters, and vehicle control units (VCUs) has become a critical engineering focus. These components require thorough validation using precise calibration and communication protocols. This paper presents the development and implementation of an optimized software stack for the Universal Measurement and Calibration Protocol (XCP), aimed at real-time validation of VCUs using next-generation communication methods such as CAN, CAN-FD, and Ethernet. The stack facilitates read/write access to the ECU’s internal memory in runtime, enabling efficient diagnostics, calibration, and parameter tuning without hardware modifications. It is designed to be modular, platform-independent, and compatible with microcontrollers across different EV platforms. By utilizing the ASAM-compliant protocol architecture, the proposed system
Uthaman, Sreekumar
Impact of Virtual ECUs on Software Development and Validation Using the Shift Left Strategy2026-26-06811/16/2026
The automotive industry is undergoing a transformational shift with the addition of Virtual ECU in the development of software and validation. The Level 3 Virtual ECU concept will lead to the transformation in the SDLC process, as early detection of defects will have a significant impact on cost and effort reduction. This paper explains the application of a Level 3 virtual ECU which can enable to perform testing in initial period considering the Shift Left Strategy, which will significantly reduce development time. This paper demonstrates various development and validation strategies of virtual ECU and how it can impact project timeline.
Bhopi, Amey, Sengar, Bhan
Items per page:
1 – 50 of 1010