Browse Topic: Communication protocols
In the automotive industry, the zonal architecture is a design approach that organizes a vehicle’s electronic and communication systems into specific zones. These zones group components based on their function and physical location, enabling more efficient integration and simplified communication between the vehicle’s various systems. An important aspect of this architecture is the implementation of the Controller Area Network (CAN) protocol. CAN is a serial communication protocol developed specifically for automotive applications, allowing various electronic devices within a vehicle, such as sensors, actuators, and Electronic Control Units (ECUs), to communicate with each other quickly and reliably, sharing information essential for the vehicle’s operation. However, due to its limitations, there is a need for more efficient protocols like Automotive Ethernet and Controller Area Network Flexible (CAN FD), which allow for higher transmission rates and larger data packets. To centralize
This SAE Technical Information Report (TIR) establishes the instructions for the documents required for the variety of potential functions for PEV communications, energy transfer options, interoperability, and security. This includes the history, current status, and future plans for migrating through these documents created in the Hybrid Communication and Interoperability Task Force, based on functional objective (e.g., [1] If I want to do V2G with an off-board inverter, what documents and items within them do I need, [2] What do we intend for V3 of SAE J2953, …).
Wearable devices that use sensors to monitor biological signals can play an important role in health care. These devices provide valuable information that allows providers to predict, diagnose, and treat a variety of conditions while improving access to care and reducing costs.
This SAE Standard specifies a message set, and its data frames and data elements, for use by applications that use vehicle-to-everything (V2X) communications systems.
This article offers an algorithmic solution for moving a homogeneous platoon of position-controlled vehicles on a curved path with varying speeds and in the presence of communication losses and delays. This article considers a trajectory-based platooning with the leader–following communication topology, where the lead vehicle communicates its reference position and orientation to each autonomous follower vehicle. A follower vehicle stores this communicated information for a specific period as a virtual trail of the lead vehicle starting from the lead vehicle’s initial position and orientation. An algorithm uses this trail to find the follower vehicle’s reference position and orientation on that trail, such that the follower vehicle maintains a constant distance from the lead vehicle. The proposed algorithm helps form a platoon where each vehicle can traverse a curve with varying speeds. In contrast, in the existing literature, most of the solutions for vehicle platooning on a curved
In the context of urban smart mobility, vehicles have to communicate with each other, surrounding infrastructure, and other traffic participants. By using Vehicle2X communication, it is possible to exchange the vehicles’ position, driving dynamics data, or driving intention. This concept yields the use for cooperative driving in urban environments. Based on current V2X-communication standards, a methodology for cooperative driving of automated vehicles in mixed traffic scenarios is presented. Initially, all communication participants communicate their dynamic data and planned trajectory, based on which a prioritization is calculated. Therefore, a decentralized cooperation algorithm is introduced. The approach of this algorithm is that every traffic scenario is translatable to a directed graph, based in which a solution for the cooperation problem is computed via an optimization algorithm. This solution is either computed decentralized by various traffic participants, who share and
This standard specifies the communications hardware and software requirements for fueling hydrogen surface vehicles (HSV), such as fuel cell vehicles, but may also be used where appropriate with heavy-duty vehicles (e.g., buses) and industrial trucks (e.g., forklifts) with compressed hydrogen storage. It contains a description of the communications hardware and communications protocol that may be used to refuel the HSV. The intent of this standard is to enable harmonized development and implementation of the hydrogen fueling interfaces. This standard is intended to be used in conjunction with the hydrogen fueling protocols in SAE J2601 and nozzles and receptacles conforming with SAE J2600.
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
This chapter delves into the field of multi-agent collaborative perception (MCP) for autonomous driving: an area that remains unresolved. Current single-agent perception systems suffer from limitations, such as occlusion and sparse sensor observation at a far distance. To address this, three unsettled topics have been identified that demand immediate attention. First, it is crucial to establish normative communication protocols to facilitate seamless information sharing among vehicles. Second, collaboration strategies need to be defined, including identifying the need for specific collaboration projects, determining the collaboration partners, defining the content of collaboration, and establishing the integration mechanism. Finally, collecting sufficient data for MCP model training is vital. This includes capturing diverse modal data and labeling various downstream tasks as accurately as possible.
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
Recently, as part of the effort to enhance fuel efficiency and reduce costs for eco-friendly vehicles, the R-gearless system has been implemented in the TMED (P)HEV system. Due to the removal of the reverse gear, a distinct backward driving method needs to be developed, allowing the Electronic Motor (e-Motor) system to facilitate backward movement in the TMED (P)HEV system. However, the capability of backward driving with the e-Motor is limited because of partial failure in the high-voltage system of an R-gearless system. Thus, we demonstrate that it is possible to improve backward driving problems by applying a new fail-safe strategy. In the event of a high-voltage battery system failure, backward driving can be achieved using the e-Motor with constant voltage control by the Hybrid Starter Generator (HSG), as proposed in this study. The introduction of feed-forward compensation for variable constant voltage control allows for the securement of more active output power within the
This SAE Recommended Practice covers the requirements for ethernet physical layer (PHY) qualification (and as applicable to other high-speed networks [i.e., Audio Bus, LVDS, Ser-Des, etc.]). Requirements stated in this document provide a minimum standard level of performance for the PHY in the IC to which all compatible ethernet communications PHY shall be designed. When the communications chipset is an ethernet switch with an integrated automotive PHY (xBASE-T1), then the testing shall include performance for all switch PHY ports as well as each controller interface. No other features in the IC are tested or qualified as part of this SAE Recommended Practice. This assures robust serial data communication among all connected devices regardless of supplier. The goal of SAE J2962-3 is to commonize approval processes of ethernet PHYs across OEMs. The intended audience includes, but is not limited to, ethernet PHY suppliers, component release engineers, and vehicle system engineers.
Items per page:
50
1 – 50 of 934