Fordonsteknik

ISO 8820-3:2015 specifies fuse-links with tabs (blade-type) Type C (medium), Type E (high current), and Type F (miniature) for use in road vehicles. It establishes, for these fuse-link types, the rated current, test procedures, performance requirements, and dimensions.

ISO 8820-3:2015 is applicable for fuse-links with a rated voltage of 32 V or 58 V, a current rating of ≤100 A, and a breaking capacity of 1 000 A intended for use in road vehicles.

ISO 8820-3:2015 is intended to be used in conjunction with ISO 8820‑1 and ISO 8820‑2. The numbering of its clauses corresponds to that of ISO 8820‑1, whose requirements are applicable, except where modified by requirements particular to this part of ISO 8820.

AMENDMENT 1: AC DER service, MCS service, and improved security concept

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.

ISO 15118-4:2018 specifies conformance tests in the form of an Abstract Test Suite (ATS) for a System Under Test (SUT) implementing an EVCC or SECC according to ISO 15118-2. These conformance tests specify the testing of capabilities and behaviors of an SUT as well as checking what is observed against the conformance requirements specified in ISO 15118-2 and against what the supplier states the SUT implementation's capabilities are. The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements defined in ISO 15118-2. The behavior tests of the ATS examine an implementation as thoroughly as is practical over the full range of dynamic conformance requirements defined in ISO 15118-2 and within the capabilities of the SUT (see NOTE). A test architecture is described in correspondence to the ATS. The conformance test cases in this document are described leveraging this test architecture and are specified in TTCN-3 Core Language for ISO/OSI Network Layer (Layer 3) and above. The conformance test cases for the Data Link Layer (Layer 2) and Physical Layer (Layer 1) are described in ISO 15118-5. Test cases with overlapping scopes are explicitly detailed. This document does not include specific tests of other standards referenced within ISO 15118-2, e.g. IETF RFCs. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, nor the environment of the protocol implementation. Furthermore, the test cases defined in this document only consider the communication protocol defined ISO 15118-2. Power flow between the EVSE and the EV is not considered. NOTE 1 Practical limitations make it impossible to define an exhaustive test suite, and economic considerations can restrict testing even further. Hence, the purpose of this document is to increase the probability that different implementations are able to interwork. This is achieved by verifying them by means of a protocol test suite, thereby increasing the confidence that each implementation conforms to the protocol specification. However, the specified protocol test suite cannot guarantee conformance to the specification since it detects errors rather than their absence. Thus conformance to a test suite alone cannot guarantee interworking. What it does do is give confidence that an implementation has the required capabilities and that its behavior conforms consistently in representative instances of communication. NOTE 2 This document has some interdependencies to the conformance tests defined in ISO 15118-5 which result from ISO/OSI cross layer dependencies in the underlying protocol specification (e.g. for sleep mode)

ISO 18243:2017 specifies the test procedures for lithium-ion battery packs and systems used in electrically propelled mopeds and motorcycles. The specified test procedures enable the user of this document to determine the essential characteristics on performance, safety and reliability of lithium-ion battery packs and systems. The user is also supported to compare the test results achieved for different battery packs or systems. ISO 18243:2017 enables setting up a dedicated test plan for an individual battery pack or system subject to an agreement between customer and supplier. If required, the relevant test procedures and/or test conditions of lithium-ion battery packs and systems are selected from the standard tests provided in this document to configure a dedicated test plan. NOTE 1 Electrically power-assisted cycles (EPAC) cannot be considered as mopeds. The definition of electrically power-assisted cycles can differ from country to country. An example of definition can be found in the EU Directive 2002/24/EC. NOTE 2 Testing on cell level is specified in IEC 62660 (all parts).

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 data link independent requirements of diagnostic services, which allow a diagnostic tester (client) to control diagnostic functions in an on-vehicle electronic control unit (ECU, server) such as an electronic fuel injection, automatic gearbox, anti-lock braking system, etc. connected to a serial data link embedded in a road vehicle.

It specifies generic services, which allow the diagnostic tester (client) to stop or to resume non-diagnostic message transmission on the data link.

This document does not apply to non-diagnostic message transmission on the vehicle's communication data link between two electronic control units. However, this document does not restrict an in-vehicle on-board tester (client) implementation in an ECU in order to utilize the diagnostic services on the vehicle's communication data link to perform bidirectional diagnostic data exchange.

This document does not specify any implementation requirements.

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 contains technical safety requirements for the design, equipment and testing of brushless vehicle washing systems and vehicle washing systems with brushes for, indoor and outdoor operation, i.e. roll-over vehicle washing systems, vehicle washing tunnels, manually movable vehicle washing facilities. NOTE 1 Annex D covers the determination and control of Legionella and Pseudomonas aeruginosa concentration in stationary vehicle wash systems. Additionally, it can be applied to all vehicle washing systems that can form aerosols due to their cleaning systems. This document does not apply to hand-guided high pressure cleaners which are covered by EN 60335 2-79:2012, to water recycling systems, buildings and doors for entering the traffic zone, for powered ride-on machines and powered walk-behind machines with a traction drive. This document does not apply to bicycle cleaning systems. NOTE 2 Signals (example doors, lighting systems) can be provided by the vehicle washing system. This document contains requirements for the protection of persons and objects from accidents and damages during use and operation of vehicle washing systems. Persons to be protected are: - operators, - maintenance and monitoring personnel, - persons in the vicinity of vehicle washing systems, - persons sitting in the vehicle during cleaning. Objects to be protected are: - vehicles. Significant hazards associated with vehicle washing systems are listed in Clause 4. These hazards have been established by a risk assessment according to EN ISO 12100 and require measures to eliminate the hazard or to reduce the risk. These measures are specified in Clause 5 of this document. The safety requirements assume that vehicle washing systems are regularly maintained by trained and competent persons according to the manufacturer's information and that the operators, with the exception of users of self-service washing systems, have been instructed in the handling of vehicle washing systems.