This document specifies a conformance test for a vehicle manufacturer assessment of self-conformance of the VM RMI system. The conformance test cases follow the use case definition of ISO 18541‑1 and the requirements stated in ISO 18541‑2 and ISO 18541‑3. The primary, but not exclusive, purpose of this document is to provide information to the VM RMI system provider to build and test the VM RMI system against the conformance test cases. This final step in the development process of the VM RMI system is an enabler for all providers that their VM RMI system meets a high degree of functional requirements expected by the end user. Furthermore, this document defines in Annex A conformance test cases for the use cases and requirements versions that apply for granting access to security-related RMI following the SERMI scheme. This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [9].

  • Standard
    76 pages
    English language
    sale 15% off
  • Standard
    78 pages
    French language
    sale 15% off
  • Draft
    75 pages
    English language
    sale 15% off
  • Draft
    79 pages
    French language
    sale 15% off

This document includes technical requirements which are related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators. This document specifies the minimum set of technical requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1. Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme. This document is applicable to light passenger and commercial vehicles as defined in regulation (EC) 715/2007 Article 2 [15].

  • Standard
    32 pages
    English language
    sale 15% off
  • Standard
    36 pages
    French language
    sale 15% off
  • Draft
    32 pages
    English language
    sale 15% off
  • Draft
    36 pages
    French language
    sale 15% off

This document includes functional user interface requirements related to automotive repair and maintenance information (RMI) systems in order to standardize access to RMI for independent operators. This document specifies all functional user interface requirements related to a vehicle manufacturer's RMI system. These requirements will reflect the deriving needs from the use cases as specified in ISO 18541‑1.

  • Standard
    13 pages
    English language
    sale 15% off
  • Standard
    13 pages
    French language
    sale 15% off
  • Draft
    13 pages
    English language
    sale 15% off
  • Draft
    13 pages
    French language
    sale 15% off

This document provides a general overview and structure of each part of the ISO 18541 series. This document also describes the use cases applicable to the standardized access to automotive RMI. The use cases address real world scenarios (e.g. servicing vehicles) regarding the information access necessary to perform vehicle roadside assistance, inspection, diagnosis, repair and maintenance, including the updating and replacement of electronic control units (ECU). Furthermore, this document defines requirements for granting access to security-related RMI in Annex A following the SERMI scheme. The RMI systems used by personnel to perform the services consist of: —   a web-based system, which provides access to RMI needed to perform the service(s); —   contact information for specific RMI; —   a security framework to protect access to security-related RMI (vehicle theft protection measures). This document is applicable to light passenger vehicles and light commercial vehicles.

  • Standard
    40 pages
    English language
    sale 15% off
  • Standard
    44 pages
    French language
    sale 15% off
  • Draft
    41 pages
    English language
    sale 15% off
  • Draft
    45 pages
    French language
    sale 15% off

This document defines the Open Test sequence eXchange (OTX) additional extension requirements and data model specifications. The requirements are derived from the use cases described in ISO 13209-1. They are listed in Clause 4. The data model specification aims at an exhaustive definition of all features of the OTX extensions which have been implemented to satisfy the requirements. This document establishes rules for the syntactical entities of each extension. Each of these syntactical entities is accompanied by semantic rules which determine how OTX documents containing extension features are to be interpreted. The syntax rules are provided by UML class diagrams and XML schemas, whereas the semantics are given by UML activity diagrams and prose definitions.

  • Standard
    379 pages
    English language
    sale 15% off
  • Draft
    379 pages
    English language
    sale 15% off

This document is applicable to road vehicles, where the electronic vehicle interface is used to perform a test method that is part of a periodic technical inspection (ePTI). This document describes use cases and specifies technical requirements in order to support the ePTI-relevant vehicle safety system(s) checks during the periodic technical inspection via the electronic interface. This document references the ISO 14229 series, the unified diagnostic services implemented on diagnostic communication over controller area network (DoCAN) and the Internet protocol (DoIP) along with the required provision of data definitions. The technical requirements of diagnostic services and data definitions of emissions-related systems are specified in other International Standards, for example, ISO 15031 and ISO 27145. Other environmental systems' ePTI use cases and technical requirements can be considered in the future. This document defines: —   all requirements describing the vehicle-communication functionality via the diagnostic link connector related to ePTI, for example: 1)   discovery of the ePTI data link; 2)   discovery of the ePTI-relevant systems; 3)   query of ePTI-relevant systems’ information, including software identification, software integrity, current and/or stored values; 4)   query of ePTI-relevant systems’ error information; 5)   activation of ePTI-relevant systems’ actuators or routines; —   the use cases about the individual vehicle communication functionality, for example, query identification information, command functional test method. This document does not directly specify any type of test method or pass/fail criteria of the ePTI-relevant system during a PTI, but provides data, which may support PTI test methods. The document specifies: —   terminology; —   communication establishment between the ePTI external test equipment and the vehicle's ePTI-relevant systems; —   usage of a credentials-based authentication and authorisation mechanism between the ePTI external test equipment and the vehicle; —   protection against tampering of the defined ePTI methods; —   definition of ePTI-relevant use cases: —   ePTI external test equipment discovers available data identifier as specified in ISO 20730-3; —   ePTI external test equipment queries the ePTI-relevant system’s information, including software numbers, software integrity information, current and/or stored values, self-test completion status, system status, and error information (e.g. DTC and/or DID information); —   ePTI external test equipment activates the ePTI-relevant system’s actuators or routines; —   definition of ePTI-relevant technical requirements; —   ePTI external test equipment minimum requirements. This document excludes: —   process definitions for performing the PTI check; —   process and data definitions for off-board data provision; —   standardised data exchange formats; —   validation and verification of vehicle safety systems according to vehicle manufacturer specifications.

  • Standard
    42 pages
    English language
    sale 15% off

This document provides requirements for the operation (“user manual”) of vehicles using CNG (fossil and renewable) as fuel, giving recommendations of good, safe and environmental friendly practices for users, including transit through specific areas (tunnels, ferries, etc.), refuelling, parking, and workshops, and also giving instructions in case of accident. This document also provides requirements concerning competence, knowledge and ability of workshops' operatives as well as any other matter concerned with safety.

  • Standard
    31 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the number and the arrangement of temperature measuring points for anthropomorphic test devices in order to ensure that the temperature of the ATD is in accordance with the temperature corridor prescribed by the applied test procedure.

  • Technical report
    30 pages
    English language
    sale 15% off

EN-ISO 17268 defines the design, safety and operation characteristics of gaseous hydrogen land vehicle (GHLV) refuelling connectors.GHLV refuelling connectors consist of the following components, as applicable:- receptacle and protective cap (mounted on vehicle);- nozzle;- communication hardware.This document is applicable to refuelling connectors which have nominal working pressures or hydrogen service levels up to 70 MPa.This document is not applicable to refuelling connectors dispensing blends of hydrogen with natural gas.

  • Standard
    53 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the design, safety and operation characteristics of gaseous hydrogen land vehicle (GHLV) refuelling connectors.
GHLV refuelling connectors consist of the following components, as applicable:
— receptacle and protective cap (mounted on vehicle);
— nozzle;
— communication hardware.
This document is applicable to refuelling connectors which have nominal working pressures or hydrogen service levels up to 70 MPa.
This document is not applicable to refuelling connectors dispensing blends of hydrogen with natural gas.

  • Standard
    53 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the implementation of a common set of unified diagnostic services (UDS) on clock extension peripheral interface networks in road vehicles. The UDSonCXPI diagnostics defines methods to implement diagnostic data transfer between a client and the CXPI slave nodes via the CXPI master node. This document specifies support of three different diagnostic classes for CXPI slave nodes. This document references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the UDSonCXPI communication protocol for mainly HMI (Human Machine Interface), but not limited to, electric/electronic systems of road vehicles. UDSonCXPI defines how to implement the diagnostic data transfer between a client and CXPI slave nodes via CXPI master node. NOTE UDSonCXPI does not specify any requirement for the in-vehicle CXPI bus architecture. This document refers to information contained in ISO 14229-1, ISO 14229-2 and ISO 20794 (all parts). This document does not include any redundant information of the above-mentioned documents. It focuses on — additional requirements specific to the implementation of UDSonCXPI network, and — specific restrictions in the implementation of UDSonCXPI network.

  • Standard
    43 pages
    English language
    sale 15% off

This document defines the design, safety and operation characteristics of gaseous hydrogen land vehicle (GHLV) refuelling connectors. GHLV refuelling connectors consist of the following components, as applicable: — receptacle and protective cap (mounted on vehicle); — nozzle; — communication hardware. This document is applicable to refuelling connectors which have nominal working pressures or hydrogen service levels up to 70 MPa. This document is not applicable to refuelling connectors dispensing blends of hydrogen with natural gas.

  • Standard
    45 pages
    English language
    sale 15% off
  • Standard
    47 pages
    French language
    sale 15% off

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.

  • Standard
    466 pages
    English language
    sale 15% off

This European Standard applies to controller device interfaces that provide defined interfaces between low voltage switchgear, controlgear, control circuit devices, switching elements and controlling devices (e.g. programmable controllers, personal computers, etc.). It may also be applied for the interfacing of other devices and elements to a controller device interface. This standard specifies requirements for controllers and devices utilising these interfaces, including not only the communication protocol specification, but also associated relevant electrical and mechanical characteristics. It also specifies the electrical and EMC tests required to verify the performance of each controller device interface when connected to the appropriate controllers and devices. This part 1 establishes a consistent terminology and format for the subsequent interfaces. It also harmonises requirements of a general nature in order to reduce the need for testing to different standards, increase understanding and facilitate comparisons of controller device interface standards. Those requirements of the various controller device interface standards which can be considered as general have therefore been gathered in this part 1. In addition to meeting the specific requirements stated in this part 1, the controller device interfaces included in this standard  are documented in the English language in accordance with the requirements specified in this part 1,  are already in use in commercial products and running in industrial plants,  are available in quantity and at low price,  are available from several sources and commercialised openly,  to satisfy the tests specified, amongst others, in EN 61000 4 2, EN 61000 4 3, EN 61000 4 4, EN 61000 4 5, and EN 61000 4 6 against the test levels specified in EN 50082 2,  have appropriate mechanisms for transmission error detection,  are open, widely accepted, well documented, stable and support inter operability,  are complete and describe the necessary interfaces in sufficient detail to enable error free implementation,  are free of any restriction related to testing the implementation. For each controller device interface only two documents are necessary to determine all requirements and tests:  the general requirements of this standard, referred to as "part 1" in the relevant parts covering the various types of controller device interfaces;  the relevant controller device interface standard hereinafter referred to as the "relevant controller device interface standard" or "controller device interface standard". The solutions described in this standard have been used for many years by industry to solve application requirements involving low voltage switchgear and controlgear. They are characterised by:  their ability to power connected devices directly from the network;  their ability to operate in harsh environments typified by those encountered at the machine level by controls in industrial applications;  usage of the sophisticated medium access rules of CAN which allows both organisation of traffic based on user assigned priorities and efficient resolution of occasional access conflict;  a wide range of exchange services allowing precise tailoring of data exchange to the actual application needs as well as simultaneous distribution of data to a selected set of connected devices;  their capability to simultaneously support data acquisition, diagnostics, messaging and programming/configuration as required, amongst others, for systems interfacing controllers to low voltage switchgear and controlgear in industrial applications. NOTE The controller device interface standards currently part of this series are:  EN 50325 2: DeviceNet  EN 50325 3: Smart Distributed System (SDS)  EN 50325-4: CANopen  EN 50325-5 : Functional safety communication based on EN 50325-4

  • Standard
    14 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies the requirements for secured and unsecured diagnostic communication between client DoIP entity and server(s) installed in the vehicle using Internet protocol (IP) as well as the transmission control protocol (TCP) and user datagram protocol (UDP). This includes the definition of vehicle gateway requirements (e.g. for integration into an existing computer network) and test equipment (client DoIP entity) requirements (e.g. to detect and establish communication with a vehicle). This document specifies features that are used to detect a vehicle in a network and enable communication with the vehicle gateway as well as with its sub-components during the various vehicle states. These features are separated into two types: mandatory and optional. This document specifies the following mandatory features: — vehicle network integration (IP address assignment); — vehicle announcement and vehicle discovery; — vehicle basic status information retrieval (e.g. diagnostic power mode); — connection establishment (e.g. concurrent communication attempts), connection maintenance and vehicle gateway control; — data routing to and from the vehicle's sub-components; — error handling (e.g. physical network disconnect). This document specifies the following optional features: — DoIP entity status monitoring; — transport layer security (TLS); — DoIP entity firewall capabilities.

  • Standard
    78 pages
    English language
    sale 15% off

EN 16652-2 defines the competence profiles and establishes procedures for assessing the competence of persons who carry out the installation, repairing and maintaining of automotive LPG systems in workshops covered in EN 16652-1  The requirements of this document do not apply to “Car manufacturer network repairers” (see 3.8) when performing the activities of repairing, servicing and maintenance of vehicles from manufacturers for which they are authorized and duly trained.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines the competence profiles and establishes procedures for assessing the competence of persons who carry out the installation, repairing and maintaining of automotive LPG systems in workshops covered in EN 16652-1 [2].
The requirements of this document do not apply to "Car manufacturer network repairers" (see 3.9) when performing the activities of repairing, servicing and maintenance of vehicles from manufacturers for which they are authorized and duly trained.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies general requirements and constraints applicable to a remote diagnostic process, the use cases and scenarios to support the implementation of a remote diagnostic process using a standardized interface of the ExVe. It concerns: — the road vehicles with four or more wheels designed and constructed primarily for the carriage of persons that are defined as Category 1 vehicles in the United Nations Special Resolution No.1 in TRANS/WP.29/1045, as last amended on 19 June 2012, and — the road vehicle with four or more wheels designed and constructed primarily for the carriage of goods that are defined as Category 2 vehicles in the United Nations Special Resolution No.1 in TRANS/WP.29/1045, as last amended on 19 June 2012, where these road vehicles are still in accordance with the specifications of the vehicle manufacturer. This document does not define the interfaces provided by the ExVe nor the internal implementation inside the ExVe. Processes like repair, prognostics, monitoring, configuration, re-programming and variant coding are not part of this document. The prerequisites (e.g. authentication and authorization) for all use cases are not covered within this document. A possible specification of the required content for the implementation of a remote diagnostic application using the web interface of the ExVe according to ISO 20078 is given in Annex A.

  • Standard
    61 pages
    English language
    sale 15% off

This document specifies the dimensions of the test track for a closed-loop test method to subjectively determine a double lane-change which is one part of the vehicle dynamics and road-holding ability of passenger cars. It is applicable to passenger cars as defined in ISO 3833. It is also applicable to light commercial vehicles up to a gross vehicle mass of 3,5 t.

  • Standard
    6 pages
    English language
    sale 15% off

This document specifies requirements for applying and documenting methods for determining particulate contamination on functionally-relevant components and systems (cleanliness inspection) of road vehicles. A cleanliness inspection comprises the basis of an assessment of technical cleanliness, which is performed, for example, under the following circumstances: — initial inspection and evaluation; — inspection of incoming and outgoing components; and — quality control or monitoring of manufacturing processes relevant to cleanliness (e.g. cleaning, surface treatment and assembly processes). This document is intended to improve the informative quality and comparability of test results. It also defines the standardized expression of cleanliness specifications and cleanliness test results in the quality chain of the automotive industry. This document does not apply to the following: — detection of filmy contamination (grease, oils, etc.); — application of non-quantifiable particulate detection methods on test components (e.g. visual assessment, wipe test with clean cloth, etc.); and — characterization of operating fluids (fuel, oils, coolants, brake fluid, etc.). This document does not define any cleanliness limit values for specific components or systems. The degree of cleanliness required for a specific component or system is dependent on a number of highly-individual factors. Cleanliness specifications are intended to be undertaken only by specialists who not only know the component concerned but also the system it is built into, the later conditions of use, technically-feasible practices and possible consequences for manufacturing processes and the supply chain. Guidance for deriving limit values can be found in Annex H.

  • Standard
    178 pages
    English language
    sale 15% off
  • Standard
    2 pages
    English language
    sale 15% off

The standard 18541 is structured into following parts:
   Part 1: General information and use case definition
   Part 2: Technical requirements
   Part 3: Functional user interface requirements
   Part 4: Conformance test
   Part 5: Heavy duty specific provisions
   Part 7: Remote diagnostic support for heavy duty vehicles (currently under definition, see NWIP N421)
Reading part 1 of this standard will provide an overview about the entire standard and how it applies to the automotive industry.
This part of the standard 18541 includes a transposition of the contents in parts 1-4 to heavy duty motor vehicles as defined in regulation (EC) 595/2009 Article 2.
The parts of the standard 18541-1, -2, -3, -4 focus on the access to automotive repair and maintenance information for passenger cars and light commercial vehicles.
Remote Diagnostic Support is a specific requirement for Access to RMI for HD vehicles. It will be addressed separately in a new part of the standard 18541 (currently under definition, see NWIP N421).
The standard 18542 is a complementary standard that defines the ‘Standardized RMI terminology’ and consists of two parts:
   Part 1: General information and use case definition
   Part 2: Standardized process implementation requirements and Registration Authority
The standardized RMI terminology is contained in a so-called ‘Digital Annex’.

  • Standard
    57 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document focus on the access to automotive repair and maintenance information for
— heavy duty motor vehicles as defined in regulation (EC) 595/2009 Article 2;
— engines and after-treatment systems (family) if they are type-approved as a separate technical unit, e.g. according to Directive 2007/46/EC.
This document includes a transposition of the standards ISO 18541-1:2014, ISO 18541-2:2014, ISO 18541-3:2014, and ISO 18541-4:2015 to these vehicle types and systems. The standards ISO 18541-1:2014, ISO 18541-2:2014, ISO 18541-3:2014, and ISO 18541-4:2015 focus on the access to automotive repair and maintenance information for passenger cars and light commercial vehicles.
Remote Diagnostic Support is a specific requirement for Access to RMI for heavy duty vehicles. It will be addressed separately in a future standard.
The standardized RMI terminology is contained in a ?Digital Annex' developed and maintained according to the complementary standard ISO 18542.

  • Standard
    57 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document focus on the access to automotive repair and maintenance information for — heavy duty motor vehicles as defined in regulation (EC) 595/2009 Article 2; — engines and after-treatment systems (family) if they are type-approved as a separate technical unit, e.g. according to Directive 2007/46/EC. This document includes a transposition of the standards ISO 18541-1:2014, ISO 18541-2:2014, ISO 18541-3:2014, and ISO 18541-4:2015 to these vehicle types and systems. The standards ISO 18541-1:2014, ISO 18541-2:2014, ISO 18541-3:2014, and ISO 18541-4:2015 focus on the access to automotive repair and maintenance information for passenger cars and light commercial vehicles. Remote Diagnostic Support is a specific requirement for Access to RMI for heavy duty vehicles. It will be addressed separately in a future standard. The standardized RMI terminology is contained in a ?Digital Annex' developed and maintained according to the complementary standard ISO 18542.

  • Standard
    45 pages
    English language
    sale 15% off
  • Standard
    49 pages
    French language
    sale 15% off

Standards 18541-1 to 4 are covering the field of light vehicles and 18541-5 will cover the field of heavy-duty motor vehicles.
The purpose is to treat specificities of mopeds and motorbikes, as well as all-terrain vehicles (quads) and other small vehicles with 3 or 4 wheels.

  • Standard
    167 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    167 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO 18541-6:2018 contains all elements (definitions, use cases, technical requirements, functional user interfaces requirements and conformance test cases) applicable for the standardized access to repair and maintenance information for two-wheeled and three-wheeled vehicles and quadricycles (L-category vehicles)
The development of this document has been based on ISO 18541‑1, ISO 18541‑2, ISO 18541‑3 and ISO 18541‑4. This document constitutes an adaptation of standardized access to RMI prescriptions for passenger cars to L-category vehicles keeping the objectives and principles of the mandate M/421 from the European commission.
ISO 18541-6:2018 references the usage of a Digital Annex of standardized search terms for RMI. The provision of such a Digital Annex will follow the process described in ISO 18542.
CEN will nominate a Registration Authority according to ISO 18542 for the creation and maintenance of an appropriate Digital Annex.

  • Standard
    167 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Standard
    167 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO 22901-3:2018 specifies machine-readable descriptions of all fault symptom algorithms which are implemented as diagnostic software in an electronic control unit (ECU). The main use case is the standardized data exchange from a function & software supplier to a vehicle manufacturer (VM) in order to enable a tool-based information processing. Based on the FXD content and associated calibration values, several end user documents can be generated such as the "summary sheet" needed as part of the vehicle type approval documentation package or the "repair and maintenance information" (RMI). The expected main benefits of the FXD approach are an overall efficiency improvement as well as an independency of supplier- and VM-specific format handling.

  • Standard
    198 pages
    English language
    sale 15% off

ISO 18541-6:2018 contains all elements (definitions, use cases, technical requirements, functional user interfaces requirements and conformance test cases) applicable for the standardized access to repair and maintenance information for two-wheeled and three-wheeled vehicles and quadricycles (L-category vehicles) The development of this document has been based on ISO 18541‑1, ISO 18541‑2, ISO 18541‑3 and ISO 18541‑4. This document constitutes an adaptation of standardized access to RMI prescriptions for passenger cars to L-category vehicles keeping the objectives and principles of the mandate M/421 from the European commission. ISO 18541-6:2018 references the usage of a Digital Annex of standardized search terms for RMI. The provision of such a Digital Annex will follow the process described in ISO 18542. CEN will nominate a Registration Authority according to ISO 18542 for the creation and maintenance of an appropriate Digital Annex.

  • Standard
    155 pages
    English language
    sale 15% off
  • Standard
    155 pages
    English language
    sale 15% off
  • Standard
    170 pages
    French language
    sale 15% off
  • Standard
    1 page
    English language
    sale 15% off

ISO 13400-3:2016 specifies the vehicle communication interface and test equipment requirements for a physical and data link layer based on IEEE 802.3 100BASE-TX. This interface serves as the physical basis for IP-based communication between the vehicle and test equipment. This document specifies the following aspects: - requirements for signal and wiring schematics in order to ensure physical layer compatibility of the vehicle interface and Ethernet networks and test equipment communication interfaces; - discovery/identification of the in-vehicle diagnostic Ethernet interface; - activation and deactivation of the in-vehicle diagnostic Ethernet interface; - mechanical and electrical diagnostic connector requirements; - this edition has been modified to include the identification of two Ethernet pin assignments.

  • Standard
    14 pages
    English language
    sale 15% off

ISO/TR 17950:2016 specifies the conditions for the recommended placement of the Hybrid III 5th percentile female frontal impact dummy (HIII5F) when used in forward-facing outboard 2nd row rear seating positions of passenger cars (M Category) for frontal impact testing . For example: - Frontal Impact 0° and Pole (ISO 3560) - Frontal Impact Offset Deformable Barrier (ISO 15828)

  • Technical report
    9 pages
    English language
    sale 15% off

ISO 19689:2016 specifies a minimum set of requirements for a diagnostic connector used in communication between motorcycles and mopeds, and external equipment for diagnostics. Its aim is to promote the use of a common diagnostic connector throughout the motorcycle industry. The diagnostic connection consists of two mating connectors, the vehicle connector and the external test equipment connector. Applicable to all types of motorcycles and mopeds, the connector specified is sealed with positive locking feature and is intended for short-term diagnostic connection only. ISO 19689:2016 specifies functional requirements for a) the vehicle connector, separated into the four principal areas of - connector location, - connector design, - connector contact allocation, and - electrical requirements for connector and related electrical circuits, and b) the external test equipment connector, separated into the three principal areas of - connector design, - connector contact allocation, and - electrical requirements for connector and related electrical circuits. The dimensional requirements of the vehicle connector are given as a minimum specification, to allow design freedom.

  • Standard
    12 pages
    English language
    sale 15% off
  • Standard
    12 pages
    English language
    sale 15% off

ISO 14230-2:2016 specifies data link layer services tailored to meet the requirements of UART-based vehicle communication systems on K-Line as specified in ISO 14230‑1. It has been defined in accordance with the diagnostic services established in ISO 14229‑1 and ISO 15031‑5, but is not limited to use with them and is also compatible with most other communication needs for in-vehicle networks. The protocol specifies an unconfirmed communication. The diagnostic communication over K-Line (DoK-Line) protocol supports the standardized service primitive interface as specified in ISO 14229‑2. ISO 14230-2:2016 provides the data link layer services to support different application layer implementations like the following: - enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics); - emissions-related OBD as specified in ISO 15031, SAE J1979-DA and SAE J2012-DA; - in addition, ISO 14230-2:2016 clarifies the differences in initialization for K-line protocols defined in ISO 9141 and ISO 14230. This is important since a server supports only one of the protocols mentioned above and the client has to handle the coexistence of all protocols during the protocol determination procedure.

  • Standard
    50 pages
    English language
    sale 15% off

This European Standard sets out requirements for the working areas and procedures for the following types of work or activity:
a)   equipping vehicles to use LPG with permanently installed LPG containers;
b)   maintenance, servicing and repairs to the LPG systems installed in vehicles,
c)   vehicle maintenance, servicing and repairs not involving the LPG system,  
The operations described in Items a) and b) above are undertaken in specialist LPG working areas, whereas Item c) is undertaken in general service working areas.

  • Standard
    29 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This European Standard sets out the requirements for automotive LPG working areas and procedures, aimed at reducing the risk of fire and explosion of LPG when the following types of work or activity are carried out:
a)   equipping vehicles with an LPG system to use LPG for propulsion purposes;
b)   maintenance, servicing and repairs to the LPG system;
c)   any other LPG vehicle maintenance, servicing or repairs not involving the LPG system.
The operations described in items a) and b) above are undertaken in dedicated LPG working areas, whereas item c) is undertaken in general service working areas.
This Standard does not address how to equip a vehicle with an LPG retrofit system or how to repair or maintain an LPG vehicle.
NOTE   Such provisions are normally provided in the instruction manuals issued by the relevant manufacturers.

  • Standard
    29 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO 15765-2:2016 specifies a transport protocol and network layer services tailored to meet the requirements of CAN‑based vehicle network systems on controller area networks as specified in ISO 11898‑1. It has been defined in accordance with the diagnostic services established in ISO 14229‑1 and ISO 15031‑5 but is not limited to use with them and is also compatible with most other communication needs for in‑vehicle networks. ISO 11898‑1 specifies variable length CAN frames with a maximum payload size dependent on the protocol device used. A CLASSICAL CAN protocol device can transmit/receive frames with payload sizes ranging from 0 bytes to 8 bytes per frame. A CAN FD (flexible data rate) protocol device can transmit/receive frames with payload sizes from 0 bytes to 64 bytes. A CAN FD protocol device is also capable of transmitting/receiving CLASSICAL CAN frames. The diagnostic communication over controller area network (DoCAN) protocol supports the standardized service primitive interface as specified in ISO 14229‑2 (UDS). ISO 15765-2:2016 provides the transport protocol and network layer services to support different application-layer implementations such as - enhanced vehicle diagnostics (emissions-related system diagnostics beyond legislated functionality, non-emissions-related system diagnostics), - emissions-related on-board diagnostics (OBD) as specified in ISO 15031, - world-wide harmonized on-board diagnostics (WWH-OBD) as specified in ISO 27145, and - end of life activation on on-board pyrotechnic devices (ISO 26021). The transport protocol specifies an unconfirmed communication. NOTE This part of ISO 15765 does not determine whether CLASSICAL CAN, CAN FD or both are recommended or required to be implemented by other standards referencing this part of ISO 15765.

  • Standard
    51 pages
    English language
    sale 15% off
  • Standard
    51 pages
    English language
    sale 15% off

ISO 15765-4:2016 specifies requirements for Controller Area Networks (CAN) where one or more controllers comply with on-board diagnostics (OBD) or world-wide harmonized on-board diagnostics (WWH‑OBD) regulations. The network presumes the use of an external test equipment for inspection and repair diagnostics, as defined by the regulations. The CAN network requirements for the vehicle and the external test equipment are based on the specifications of ISO 15765-2, ISO 11898-1 and ISO 11898-2. ISO 15765-4:2016 places restrictions on those International Standards for the fulfilment of the regulations. It does not specify in-vehicle CAN bus architecture, but seeks to ensure that the vehicle's regulated CAN communications comply with external test equipment requirements. ISO 15765-4:2016 defines the requirements to successfully establish, maintain and terminate communication with a vehicle that implements the requirements of the OBD/WWH-OBD regulations. Plug‑and-play communication capabilities among vehicles and test equipment are defined to assure the interoperation of external test equipment and vehicles. This part of ISO 15765 details all of the OSI layer requirements to achieve this goal. ISO 15765-4:2016 is the entry point for DoCAN (Diagnostic communication over Controller Area Network). Based on the results of the initialization, the external test equipment determines which protocol and diagnostic services are supported by the vehicle's emissions-related system: - legislated OBD: ISO 15031 (all parts); - legislated WWH-OBD: ISO 27145 (all parts).

  • Standard
    27 pages
    English language
    sale 15% off
  • Standard
    27 pages
    English language
    sale 15% off

ISO 15031-3:2016 references the latest publication of SAE J1962. On-board diagnostic (OBD) regulations require road vehicles to be equipped with a standardized connector for purposes of access to OBD information by ISO 15031‑4 compliant external test equipment. This part of ISO 15031 describes the requirements for the physical connection and associated pin usage to allow for standard access to the OBD data. The first edition of this part of ISO 15031 was based on SAE J1962 and was intended to meet European OBD requirements for 2000 and later model year vehicles, and added a modified connector type to accommodate vehicles with a 24 V system. This revised part of ISO 15031 is technically equivalent to SAE J1962 with the exception of the specific requirements identified in the document. ISO 15031-3:2016 specifies additional requirements related to right hand driven (RHD) vehicles. Annex A and Annex B are for information and not required to fulfil emissions-related OBD.

  • Standard
    5 pages
    English language
    sale 15% off
  • Standard
    5 pages
    English language
    sale 15% off

ISO 27145-4:2016 defines the requirements to successfully establish, maintain and terminate communication with a vehicle that implements the requirements of the WWH-OBD GTR (Global technical regulation No. 5; see Reference [16]). This requires plug and play communication capabilities for the vehicle, as well as for any test equipment that intends to establish communication with a vehicle. This part of ISO 27145 details all the OSI layer requirements to achieve this goal. ISO 27145-4:2016 is intended to become the single communication standard for access to information relating to vehicle on-board diagnostics (VOBD). To allow for a smooth migration from the existing communication standards to this future world-wide standardized communication standard, the communication concept as specified in this part of ISO 27145 is based on two different data links: - diagnostic communication over Controller Area Network (DoCAN), ISO 15765‑4; - diagnostic communication over Internet Protocol (DoIP), ISO 13400 (all parts). NOTE It is intended that this part of ISO 27145 will be extended as necessary upon introduction of additional communication media. IMPORTANT ? Use cases deriving from country-specific implementation of GTR No. 5 into local legislation are not included in this part of ISO 27145.

  • Standard
    17 pages
    English language
    sale 15% off
  • Standard
    17 pages
    English language
    sale 15% off

ISO 13400-4:2016 specifies a minimum set of diagnostic Ethernet connector requirements which are based on ISO 15031‑3. The ISO 15031‑3 diagnostic connector is referenced by legislation in many countries. The diagnostic connection specified in this part of ISO 13400 consists of two mating connectors: the vehicle connector and the external test equipment connector as specified in ISO 15031‑3. ISO 13400-4:2016 specifies: - the functional requirements for the vehicle connector. These functional requirements are separated into two principal areas: connector contact allocation and electrical requirements for connector and related electrical circuits; - the functional requirements for the external test equipment connector. These functional requirements are separated into two principal areas: connector contact allocation and electrical requirements for connector and related electrical circuits. Two (2) different connector layouts and pin-outs are specified in this part of ISO 13400: a) Ethernet pin assignment option 1 (see Annex A); b) Ethernet pin assignment option 2 (see Annex B). Historically, option 1 is specified to meet Ethernet pin assignment of road vehicles already launched onto the market and may be used to resolve conflicts with vehicle manufacturer-specific usage of discretionary pins, e.g. pins 1 and 9. Option 2 is specified to meet the Ethernet pin assignment of road vehicles to resolve conflicts with vehicle manufacturer-specific usage of discretionary pins, e.g. pins 3 and 11. A discovery/identification and activation method of the vehicle's Ethernet via the "Ethernet Activation Line" is specified in ISO 13400‑3.

  • Standard
    11 pages
    English language
    sale 15% off
  • Standard
    11 pages
    English language
    sale 15% off

This part of the CEN standard specifies "Compliance Test" cases for a self-compliance test by the manufacturer of the RMI system. The compliance test cases will follow the use case definition of the part 1 document as well as the requirements stated in part 2 and 3. The sole purpose of this part of the CEN standard is to provide sufficient information to the RMI system manufacturer to build and test the RMI system against the compliance test cases. This final step in the development process of the RMI system is an enabler for all manufacturers that their RMI system meets a high degree of functional requirements expected by the end user. The work carried out in CEN/TC 301 and WG 1 interfaces with ISO and other WGs.

  • Standard
    91 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO 18541-4:2015 specifies a conformance test for a vehicle manufacturer assessment of self-conformance of the VM RMI system. The conformance test cases follow the use case definition of ISO 18541‑1 and the requirements stated in ISO 18541‑2 and ISO 18541‑3. The primary but not exclusive purpose of this part of ISO 18541 is to provide information to the VM RMI system provider to build and test the VM RMI system against the conformance test cases. This final step in the development process of the VM RMI system is an enabler for all providers that their VM RMI system meets a high degree of functional requirements expected by the end user.

  • Standard
    74 pages
    English language
    sale 15% off
  • Standard
    77 pages
    French language
    sale 15% off

ISO/TR 12349-1:2015 specifies the adult crash test dummies that are recommended by ISO for use in evaluating the occupant protection potential of restraint systems in frontal, side, and rear impact test procedures and out-of-position airbag test procedures.

  • Technical report
    6 pages
    English language
    sale 15% off

ISO/TR 12349-2:2015 specifies the infant and child crash test dummies that are recommended by ISO for use in evaluating child restraints in frontal impacts and out-of-position interactions with frontal or side airbags.

  • Technical report
    4 pages
    English language
    sale 15% off

This European Standard applies to the tyre pressure gauges (TPG) which operate using pressure equipment (devices used in fixed or mobile installations) to inflate the tyres of road using vehicles (M1 and M2 categories) and which may be capable of interacting with vehicles equipped with tyre pressure monitoring systems (TPMS) whereby the TPG may be steered by the TPMS/vehicle.
To set the correct tyre inflation, this European Standard defines requirements and processes for the interoperability of TPG with TPMS/vehicle, through standardized interfaces and data exchange formats allowing advanced information, management and control systems between TPG and TPMS/vehicle. The architecture is open and scalable to support the different levels of interoperability (from full interoperability to fully manual).
This European Standard does not define communication protocols (works specifically made under M/453 European mandate).
This European Standard may be applied to all TPG categories referenced in the revision of EN 12645.
The driver/operator is considered as being responsible for the validation of the parameters and tyre pressure.
This European Standard will be applicable upon development of Infrastructure solution (V2I-I2V communication solutions).

  • Standard
    25 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO 27145-6:2015 defines the requirements for the external test equipment as listed: - a means of establishing communications between a WWH-OBD-equipped vehicle and external test equipment; - a set of diagnostic services, including addressing methods, to be provided by the external test equipment in order to exercise the services defined in ISO 27145‑3. ISO 27145-6:2015 describes the minimum capabilities or functions in the external test equipment. Additional functionality, e.g. non WWH-OBD protocols or retrieval of repair and maintenance information, can be integrated into the external test equipment according to the test equipment manufacturer needs. The external test equipment designer ensures that no such capability or function can adversely affect either a WWH-OBD-equipped vehicle connected to the equipment, or the equipment itself. When the external test equipment implements functionality, which is not covered by ISO 27145‑3, this functionality is not linked to the timing requirements defined in this International Standard.

  • Standard
    32 pages
    English language
    sale 15% off

ISO 14229-7:2015 specifies the implementation of a common set of unified diagnostic services (UDS) on UART-based local interconnect networks in road vehicles. The UDSonLIN diagnostics defines methods to implement diagnostic data transfer between a client and the LIN slave nodes through the LIN master node. LIN slave nodes support three different diagnostic classes as defined in ISO 17987. UDSonLIN references ISO 14229-1 and ISO 14229-2 and specifies implementation requirements of the following: - diagnostic services to be used for diagnostic communication over LIN, - server memory programming for in-vehicle LIN servers with an external test equipment, and - configuration of a LIN slave node as specified in ISO 17987.

  • Standard
    14 pages
    English language
    sale 15% off

This part of the CEN standard shall deliver all "Functional User Interface require-ments" related to an RMI system. These requirements will reflect the deriving needs from the use cases as specified in part 1.
The following are examples (not a complete list):
   How a user performs login and authenticates himself,
   How a user specifies the vehicle manufacturer, vehicle make, vehicle model, model year, etc. This can be achieved by selection menues or VIN entry,
   How a user navigates through the product information structure,
   How a user specifies RMI search criteria from a list of standardized terms across all vehicle manufacturers;

  • Standard
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of the CEN standard shall deliver all "Technical Requirements" related to an RMI system These requirements will reflect the deriving needs from the use cases as specified in part 1.
The following are examples (not a complete list):
   Vehicle Identification requirements,
   Product Information Structure and Navigational Pathway requirements,
   Diagnostic Configuration Scenarios and Communication Interface require-ments,
   Security Access related requirements,
   Re-programing requirements

  • Standard
    39 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of the CEN standard includes "General Information" which provides a general overview and structure about each part of the CEN standard. It also specifies Repair and Maintenance Information (RMI) related "Use Case definition" related to the standardized access to an RMI system used in a repair shop environment.
Reading part 1 of the CEN standard will provide a good overview about the entire standard and how it applies to the automotive industry.

  • Standard
    48 pages
    English language
    sale 10% off
    e-Library read for
    1 day