ISO 26021-3:2022

INTERNATIONAL ISO
STANDARD 26021-3
Second edition
2022-05
Road vehicles — End-of-life activation
of in-vehicle pyrotechnic devices —
Part 3:
Data definitions
Véhicules routiers — Activation en fin de vie des dispositifs
pyrotechniques embarqués —
Partie 3: Définition des données
Reference number
© ISO 2022
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Parameter specification. 2
Annex A (normative) Data identifier (DID) parameter definitions . 3
Annex B (normative) Deployment loop parameter definitions . 7
Annex C (normative) Routine control parameter definitions .13
Bibliography .14
iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 31,
Data communication.
This second edition cancels and replaces the first edition of ISO 26021-1:2008, ISO 26021-2:2008,
ISO 26021-2:2008/Cor 1:2009, ISO 26021-3:2009, ISO 26021-4:2009, ISO 26021-5:2009, which has been
technically revised.
The main changes are as follows:
— restructuring of four parts into a new Part 1 document including use cases and application
requirements and a new Part 3 document including data definitions;
— introduction of requirement structure with numbering and name;
— support of ISO 13400 DoIP (diagnostic communication over Internet Protocol);
— support of ISO 13400-4 DoIP diagnostic connector.
A list of all parts in the ISO 26021 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
End-of-life deployment activation of on-board pyrotechnical devices is part of a wider regime designed
to ensure that pyrotechnical devices in road vehicles are scrapped in a safe and environmentally
acceptable condition after their use.
The ISO 26021 series is based on the Open Systems Interconnection (OSI) basic reference model specified
[2] [4]
in ISO/IEC 7498-1 and ISO/IEC 10731 , which structures communication systems into seven layers.
When mapped on this model, the application protocol and data link framework requirements specified/
referenced in the ISO 26021 series are structured according to Figure 1.
Figure 1 illustrates a standard-based documentation concept, which consists of the following main
clusters:
— vehicle diagnostic communication framework: covers all relevant basic vehicle diagnostic
communication specifications of OSI layers 7, 6 and 5;
— vehicle diagnostic communication use case framework: covers the master specification, which
specifies the use cases and requirements of the subject matter of OSI layer 7;
— presentation layer framework: covers all data relevant specifications of OSI layer 6;
— conformance test plan: covers the conformance test plan requirements of the use cases and
communication requirements of OSI layers 7, 6 and 5;
— lower OSI layer framework: covers all vehicle diagnostic protocol standards of OSI layers 4, 3, 2 and
1, which are relevant and referenced by the use case specific standard.
Figure 1 shows the document reference according to OSI model.
v
Figure 1 — ISO 26021 documents reference according to OSI model
vi
INTERNATIONAL STANDARD ISO 26021-3:2022(E)
Road vehicles — End-of-life activation of in-vehicle
pyrotechnic devices —
Part 3:
Data definitions
1 Scope
This document specifies all end-of-life activation of in-vehicle pyrotechnical devices identifiers, data
identifiers, routine identifiers, data types, computations, and units.
This document is based on:
— new safety-relevant system technology designed into the vehicles,
— new or more effective end-of-life activation of in-vehicle pyrotechnical devices, which requires
additional test data, and routine controls.
This document describes the end-of-life activation of in-vehicle pyrotechnical devices data definitions
and associated technical requirements.
This document specifies:
— identifiers for end-of-life activation of in-vehicle pyrotechnical devices data definitions and
associated technical requirements,
— data identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data
definitions and associated technical requirements,
— routine identifiers applicable to end-of-life activation of in-vehicle pyrotechnical devices data
definitions and associated technical requirements.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 14229-1, Road vehicles — Unified diagnostic services (UDS) — Part 1: Application layer
ISO 15765-5, Road vehicles — Diagnostic communication over Controller Area Network (DoCAN) — Part 5:
Specification for an in-vehicle network connected to the diagnostic link connector
ISO 26021-1:2022, Road vehicles — End-of-life activation of in-vehicle pyrotechnical devices — Part 1:
Application and communication interface
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO 14229-1 and ISO 26021-1:2022
apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 Abbreviated terms
DID data identifier
MI malfunction indicator
RCOR routineControlOptionRecord
RCTP routineControlParameter
SF SubFunction
VM vehicle manufacturer
5 Parameter specification
Annex A specifies the data identifier (DID) parameters and shall be followed.
Annex B specifies the deployment loop parameters and shall be followed.
Annex C specifies the routine control parameters and shall be followed.
Annex A
(normative)
Data identifier (DID) parameter definitions
A.1 DID = NumberOfPcu
Table A.1 specifies the DID, which contains the overall number of PCUs (including the mandatory fixed-
address PCU) installed in the vehicle (default 1).
EXAMPLE If there is only one fixed-address PCU in the vehicle, a value of one (1) is reported. If there are two
(2) additional PCUs in the vehicle, a value of three (3) is reported.
Table A.1 — DID = NumberOfPcu
DID Definition Symbolic name A_Data Scaling
byte
FA00 NumberOfPcu DID_NUM_PCU — —
This DID shall be read-only and shall be supported by the 1 8 bit unsigned numeric
fixed-address PCU in the vehicle.
00 : not valid
01 to F0 : valid number
16 16
F0 to FF : reserved by
16 16
this document
A.2 DID = PcuHardwareDeploymentMethod
Table A.2 specifies the data identifier, which contains the version of the PCU deployment method
implemented by the PCU and an identification string for the PCU. This data identifier is read-only.
Table A.2 — DID = PcuHardwareDeploymentMethod
DID Definition Symbolic name A_Data Scaling
byte
FA01 PcuHardwareDeploymentMethodVersion DID_HW_DPLY_MV — —
This parameter of the PcuHardwareDeploymentMethodVer- 1 8 bit unsigned charac-
sion contains the deployment method version of the diagnostic ter00 : default value:
protocol services and the sequence used for the PCU deploy-
01 : ISO 26021-2 Edition 1
ment.
02 : ISO 26021-1 Edition 2
03 to FF : reserved by
16 16
this document
PcuIdentificationString 2 to 10 8 bit unsigned character
This parameter of the PcuHardwareDeploymentMethod con- 00 : default value
tains the PCU identification string that is assigned to the PCU
01 to FF : VM-specific
16 16
by the vehicle manufacturer (VM).
Additional data reserved for future use. --- reserved by this document
A.3 DID = PcuAddressInfo
Table A.3 specifies the data identifier, which contains the address type (11 bit, 29 bit) and address
numbers (request and response) to be used to communicate with the PCUs in the vehicle. This
information is dependent upon the physical link (see ISO 15765-5). Only “normal addressing” and
“normal fixed addressing” as defined in ISO 15765-5 shall be supported on CAN. This data identifier
shall only be supported by the fixed-address PCU in the vehicle.
The structure defined below shall be repeated in the response message for each PCU (including the
fixed-address PCU) in the vehicle. This data identifier is read-only.
Table A.3 — DID = PcuAddressInfo
DID Definition Symbolic name A_Data Scaling
byte
FA02 PcuAddressInfo DID_PCU_ADDR_ — —
INFO
PcuAddressFormatId #1 1 8 bit unsigned numeric
st
This format identifier specifies the format of the 1 01 : 11 bit normal addressing
st
PCU's address information. The 1 PCU address infor-
02 : 11 bit extended addressing
mation type contains the address format of the PCU to
be deployed first. 03 : 11 bit mixed addressing
Address information types are defined in ISO 26021-1.
04 : 29 bit normal fixed addressing
05 : 29 bit mixed addressing
06 : 29 bit unique addressing
PcuRequestMsgAddr #1 2 to 5 32 bit unsigned numeric
This parameter contains the diagnostic request ad-
dress to which the PDT shall transmit the diagnostic
requests to communicate with a PCU. Depending on
the address information format, this is either an 11-bit
st
or a 29-bit CAN-identifier. The 1 PCU request address
shall be that of the PCU to be fired first.
The unused most significant bits shall be padded with
zeros (0).
PcuResponseMsgAddr #1 6 to 9 32 bit unsigned numeric
This parameter contains the diagnostic response ad-
dress to which the PCU will respond to the requests of
the PDT. Dependent upon the address information for-
mat this is either an 11-bit or 29-bit CAN-identifier or
st
an 8-bit K-Line address. The 1 PCU request address
shall be that of the PCU to be fired first.
The unused most significant bits shall be padded with
zeros (0).
PcuAddressFormatId #n (n – 1) × 8 bit unsigned numeric
9 + 1
th
This format identifier specifies the format of the n (see PCU address format #1)
PCU's address information.
RequestMsgAddrPcu #n (n – 1) × 32 bit unsigned numeric
9 + 2 to
th
This is the diagnostic request address of the n PCU in
(n – 1) ×
the vehicle.
9 + 5
ResponseMsgAddrPcu #n (n – 1) × 32 bit unsigned numeric
9 + 6 to
th
This is the diagnostic response address of the n PCU
(n – 1) ×
in the vehicle.
9 + 9
A.4 DID = DeploymentLoopIdTable
Table A.4 specifies the data identifier, which contains the number of loop table records in this PCU.
Every loop record is made up of the type and the associated status of the deployment loops supported
by the PCU. This data identifier is read-only.
Table A.4 — DID = DeploymentLoopIdTable
DID Definition Symbolic name A_Data Scaling
byte
FA06 DeploymentLoopIdTable DID_DPLY_LIDT — —
ACLType 1 8 bit unsigned numeric
The PCU deployment identifies the type of ACL required 01 : No_ACL_Line
by the diagnostic protocol services and the sequence
02 : ACL_CommMode_12V
used for deployment of the pyrotechnic device. It shall
be incremented every time a protocol service or a data 03 : ACL_PWM_FixedLevel_8V
identifier is changed and is no longer backward-compat-
04 : ACL_CommMode_24V
ible.
05 : ACL_PWM_UBattLevel_12V
06 : ACL_PWM_UBattLevel_24V
07 to FF : reserved by this
16 16
document
ACLMethodVersion 2 8 bit unsigned character
The ACL method version identifies the version of the 02 : ISO 26021:2022 series
diagnostic protocol services and sequence used for (this document series)
PCU deployment. It shall be incremented every time a
protocol service or a data identifier is changed in the
relevant parts of the ISO 26021 series and is no longer
backward-compatible.
NumOfLoopTableRecords 3 8 bit unsigned numeric
00 : not valid
01 to F0 : number
16 16
F0 to FF : reserved by this
16 16
document
DeploymentLoopId #1 4 8 bit unsigned numeric
st
This parameter contains the identificati
...