Browse Topic: Vehicle to everything (V2X)

Items (698)
ABSTRACT A simulation capable of modeling grid-tied electrical systems, vehicle-to-grid (V2G) and vehicle-to-vehicle(V2V) resource sharing was developed within the MATLAB/Simulink environment. Using the steady state admittance matrix approach, the unknown currents and voltages within the network are determined at each time step. This eliminates the need for states associated with the distributed system. Each vehicle has two dynamic states: (1) stored energy and (2) fuel consumed while the generators have only a single fuel consumed state. One of its potential uses is to assess the sensitivity of fuel consumption with respect to the control system parameters used to maintain a vehicle-centric bus voltage under dynamic loading conditions.
Jane, Robert S.Parker, Gordon G.Weaver, Wayne W.Goldsmith, Steven Y.
This document describes [motor] vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis. It provides a taxonomy with detailed definitions for six levels of driving automation, ranging from no driving automation (Level 0) to full driving automation (Level 5), in the context of [motor] vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways: Level 0: No Driving Automation Level 1: Driver Assistance Level 2: Partial Driving Automation Level 3: Conditional Driving Automation Level 4: High Driving Automation Level 5: Full Driving Automation These level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on [motor] vehicles in a functionally consistent and coherent manner. “On-road” refers to publicly accessible roadways (including parking areas and private campuses that permit
On-Road Automated Driving (ORAD) committee
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
Items per page:
1 – 50 of 698