Fordonssystem

This document specifies requirements for lithium-ion traction battery packs or systems used in battery electric, hybrid electric and fuel cell electric road vehicles. This document describes the most relevant environmental stresses and specifies tests and test boundary conditions. This document establishes a classification of battery packs or systems and defines different stress levels for testing when a classification is applicable and required. The objective of this document is to specify standard test procedures and conditions to enable the observation of the reliability of the lithium-ion traction battery in the vehicle.

This document specifies tests for a battery pack or system of voltage class A and B.

This document provides the necessary information to set up a dedicated test plan for a battery pack or system subject to agreement between the customer and supplier. If required, the relevant test procedures and/or test conditions can also be selected from this document.

NOTE This document only covers requirements and test conditions for a traction battery pack or system used in passenger cars.

ISO 15118-2:2014 specifies the communication between battery electric vehicles (BEV) or plug-in hybrid electric vehicles (PHEV) and the Electric Vehicle Supply Equipment. The application layer message set defined in ISO 15118-2:2014 is designed to support the energy transfer from an EVSE to an EV. ISO 15118-1 contains additional use case elements describing the bidirectional energy transfer. The implementation of these use cases requires enhancements of the application layer message set defined herein. The purpose of ISO 15118-2:2014 is to detail the communication between an EV (BEV or a PHEV) and an EVSE. Aspects are specified to detect a vehicle in a communication network and enable an Internet Protocol (IP) based communication between EVCC and SECC. ISO 15118-2:2014 defines messages, data model, XML/EXI based data representation format, usage of V2GTP, TLS, TCP and IPv6. In addition, it describes how data link layer services can be accessed from a layer 3 perspective. The Data Link Layer and Physical Layer functionality is described in ISO 15118-3.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available.

This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available.

This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available.

This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available.

This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available.

This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

ISO/SAE 1979-3 is intended to satisfy the data reporting requirements of regulations in the United States and Europe, and any other market that may adopt similar requirements in the future. This document specifies diagnostic services required to be supported by motor vehicles and external test equipment for diagnostic purposes which pertain to Zero Emission Vehicle (ZEV) propulsion related data. These messages are intended to be used by any external test equipment for retrieval of OBD information from a vehicle. This document specifies: 1. message formats for request and response messages, 2. application and session timing requirements between request messages from external test equipment and response messages from vehicles, and between those messages and subsequent request messages, 3. behavior of both, the vehicle and external test equipment if data is not available, 4. a set of diagnostic services, with corresponding content of request and response messages, and 5. standardized source and target addresses for external test equipment and vehicle. This document includes capabilities required to satisfy OBD requirements for multiple regions, model years, engine types, and vehicle types. At the time of publication many regional regulations are not yet final and are expected to change in the future. This document makes no attempt to interpret the regulations and does not include applicability of the included diagnostic services and data parameters for various vehicle applications. The user of this document is responsible to verify the applicability of each section of this document for a specific vehicle, propulsion system, model year, and region. This document provides an implementation guidance based on the principles of ISO 14229 series, focusing on standardization of data to ensure access to important repair information by independent repair facilities. The purpose of this standard is to focus on providing the necessary content and performance requirements. ISO/SAE 1979-3 specifies diagnostic functionalities, which utilize communication facilities over either Controller Area Network (CAN) or Ethernet data links. These requirements apply to all ECU’s that provide operational data and diagnose those components that are integral to provide propulsion on a Zero Emission Vehicle (ZEV). In general, if an ECU monitors a component, whose failure directly affects the ZEV propulsion system, the information reporting uses the diagnostic communication services as specified in ISO/SAE 1979-3. A government agency may have policy reasons for specifically tracking ZEV componentry (i.e., unique warranty requirements). In order to track the linkage between a diagnostic trouble code and a covered repair under a ZEV component warranty, provisions are made in ISO/SAE 1979-3 to highlight those failures that are ZEV propulsion related. These linkages can be thought of analogously to emissions-related failures requiring emissions-related warranty repair. Note: When referencing other documents to fulfil this set of requirements, the reader should substitute “emissions-related” for “ZEV propulsion". Global regulations may vary in the definition of ZEV propulsion componentry, therefore the applicability of ISO/SAE 1979-3 to various components may vary from region to region.

This document defines various parameters to be tested for the communication channel between two Ethernet devices (e.g. ECUs for automotive application) and also for the transmission media including cables and connectors as a single component of which the communication channel consists. This document also specifies the general RF requirements for a physical layer communication channel for ISO/IEC/IEEE 8802-3. These requirements are related to signal integrity of the communication channel.

Test methods for electrical performances of the communication channel/link and cables and connectors are also specified in this document.

This document is applicable to road vehicles with automated driving functions. The document specifies the logical interface between in-vehicle environmental perception sensors (for example, radar, lidar, camera, ultrasonic) and the fusion unit which generates a surround model and interprets the scene around the vehicle based on the sensor data. The interface is described in a modular and semantic representation and provides information on object level (for example, potentially moving objects, road objects, static objects) as well as information on feature and detection levels based on sensor technology specific information. Further supportive information is available.

This document does not provide electrical and mechanical interface specifications. Raw data interfaces are also excluded.

This document specifies physical medium attachment (PMA) sublayers for the controller area network (CAN). This includes the high-speed (HS) PMA without and with low-power mode capability, without and with selective wake-up functionality. Additionally, this document specifies PMAs supporting the signal improvement capability (SIC) mode and the FAST mode in Annex A. The physical medium dependent (PMD) sublayer is not in the scope of this document.