Cart (0)
- No items in cart.
Total
$0
There is a technical issue about last added item. You can click "Report to us" button to let us know and we resolve the issue and return back to you or you can continue without last item via click to continue button.
Not a subscriber? Register for a trial account.
Already a subscriber? 
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
| Email * | |
| Password * | |
| Confirm * | |
| First Name * | |
| Last Name * | |
| Title | |
| Company Name * | |
| Company Size * | |
| Industry * | |
| Address * | |
| Address 2 | |
| City * | |
| State * |
Zip *
|
| Country * | |
| Phone * | |
| How did you hear about MADCAD.com? * |
|
Reset password
Enter your personal account email address to request
a password reset:
a password reset:
Reset password
Enter your account email address to request
a password reset:
a password reset:
Security check
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
Report To Us
Contact us for a custom quote
⨯To continue with accurate pricing,
please select your company type below:
⨯We need your input!
Are you a code official in a jurisdiction with less than 300,000 population?
⨯ We need your input!
⨯We need your input!
Are you an existing Madcad user?
If so, please login to continue with the free items in your cart.
⨯We need your input!
This bundle includes subscribed items.
Download File
eLibrary >
BS ISO 26021-1:2022 Road vehicles. End-of-life activation of in-vehicle pyrotechnic devices - Application and communication interface >
Expand All
TOC Search:
BS ISO 26021-1:2022 Road vehicles. End-of-life activation of in-vehicle pyrotechnic devices - Application and communication interface, 2022
- National foreword
- ISO26021-1.pdf [Go to Page]
- Foreword
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms and definitions
- 4 Symbols and abbreviated terms [Go to Page]
- 4.1 Symbols
- 4.2 Abbreviated terms
- 5 Conventions
- 6 Basic principles and use cases overview [Go to Page]
- 6.1 Basic principles
- 6.2 Use case groups and associated use cases
- 7 Use cases definition (UC) [Go to Page]
- 7.1 UCG 1 – Perform communication interface discovery [Go to Page]
- 7.1.1 UC 1.1 – Discover DoCAN communication interface
- 7.1.2 UC 1.2 – Discover DoIP communication interface
- 7.2 UCG-2 – Perform authentication [Go to Page]
- 7.2.1 UC 2.1 – Perform PDT authentication
- 7.2.2 UC 2.2 – Perform fixed-address PCU/PCU(s) authentication
- 7.3 UCG 3 – Perform system initialisation (Sys-Init) [Go to Page]
- 7.3.1 UC 3.1 – Report PCU hardware deployment method
- 7.3.2 UC 3.2 – Report number of PCU(s)
- 7.3.3 UC 3.3 – Report address information of PCU(s)
- 7.3.4 UC 3.4 – Report vehicle identification number
- 7.3.5 UC 3.5 – Report dismantling documentation of PCU
- 7.4 UCG 4 – Perform PCU initialisation (PCU-Init) [Go to Page]
- 7.4.1 UC 4.1 – Report PCU deployment loop identification table
- 7.4.2 UC 4.2 – Initiate safetySystemDiagnosticSession
- 7.4.3 UC 4.3 – Keep-alive safetySystemDiagnosticSession
- 7.4.4 UC 4.4 – Unlock security of PCU
- 7.4.5 UC 4.5 – Execute PCU(s) scrapping program module loader
- 7.5 UCG 5 – Perform PCU and ACL sequence (PCU- and ACL-Scrapping) [Go to Page]
- 7.5.1 UC 5.1 – Report ACL deployment sequence (ACL-Init)
- 7.5.2 UC 5.2 – Write dismantling documentation into PCU (Device-Deploy)
- 7.5.3 UC 5.3 – Perform ACL deployment confirmation sequence (Device-Deploy)
- 7.5.4 UC 5.4 – Perform PCU pyrotechnic device scrapping via loop identification (Device-Deploy)
- 7.6 UCG 6 – Terminate PCU pyrotechnic device deployment (PCU-End) [Go to Page]
- 7.6.1 UC 6.1 – Terminate PCU pyrotechnic device scrapping via communication interface
- 7.6.2 UC 6.2 – Terminate PCU pyrotechnic device scrapping via ACL
- 8 Application (APP) [Go to Page]
- 8.1 APP – Preconditions of end-of-life activation of pyrotechnic devices
- 8.2 APP – Overview of end-of-life activation of pyrotechnic devices sequence
- 8.3 APP – Software provisions [Go to Page]
- 8.3.1 APP – Scrapping program module (SPM)
- 8.3.2 APP – Scrapping program module loader (SPL)
- 8.3.3 APP – PCU loop identification table
- 8.4 APP – Mapping of use cases to requirements
- 8.5 APP – Application timing definition
- 8.6 APP – Discovery of communication interface (Com I/F-Discovery) [Go to Page]
- 8.6.1 APP – Overview of discovery of communication interface (Com-Discovery)
- 8.6.2 APP – Setup DoCAN communication interface
- 8.6.3 APP – Setup DoIP communication interface
- 8.6.4 APP – Determination of DoCAN or DoIP communication interface in the vehicle
- 8.7 APP – Perform authentication – Optional (Sys-Auth) [Go to Page]
- 8.7.1 APP – Overview of the authentication – Optional (Sys-Auth)
- 8.7.2 APP – PDT authentication against fixed-address PCU – Optional (Sys-Auth)
- 8.7.3 APP – Fixed-address PCU authentication against PDT – Optional (Sys-Auth)
- 8.8 APP – Perform system initialisation (Sys-Init) [Go to Page]
- 8.8.1 APP – Overview of the system initialisation (Sys-Init)
- 8.8.2 APP – Report PcuHardwareDeploymentMethod (Sys-Init)
- 8.8.3 APP – Report number of PCUs (Sys-Init)
- 8.8.4 APP – Report DoCAN address information of PCUs (Sys-Init)
- 8.8.5 APP – Report DoIP address information of PCUs (Sys-Init)
- 8.8.6 APP – Report vehicle identification number (Sys-Init)
- 8.8.7 APP – Report dismantling documentation of PCU (Sys-Init)
- 8.9 APP – Perform PCU initialisation (PCU-Seq) [Go to Page]
- 8.9.1 APP – Overview of the PCU initialisation (PCU-Seq)
- 8.9.2 APP – Report PCU deployment loop identification table (PCU-Seq)
- 8.9.3 APP – Initiate safetySystemDiagnosticSession (PCU-Seq)
- 8.9.4 APP – Keep-alive safetySystemDiagnosticSession (PCU-Seq)
- 8.9.5 APP – Unlock security of PCU (PCU-Seq)
- 8.9.6 APP – Execute PCU scrapping program module loader (PCU-Seq)
- 8.10 APP – Perform PCU and ACL scrapping (Device-Deploy) [Go to Page]
- 8.10.1 APP – Overview of the PCU- and ACL-Scrapping (Device-Deploy)
- 8.10.2 APP – Report ACL deployment sequence (ACL-Prep)
- 8.10.3 APP – Write dismantling documentation into PCU (Device-Deploy)
- 8.10.4 APP – Confirm ACL deployment sequence (Device-Deploy)
- 8.10.5 APP – Perform device scrapping (Device-Deploy)
- 8.10.6 APP – Evaluation of device scrapping (Device-Deploy)
- 8.10.7 APP – Next pyrotechnic device (Device-Deploy)
- 8.11 APP – Terminate PCU and ACL pyrotechnic device deployment (PCU-End) [Go to Page]
- 8.11.1 APP – Overview of the PCU- and ACL-Termination (PCU-End)
- 8.11.2 APP – Terminate PCU pyrotechnic device scrapping (PCU-End)
- 8.11.3 APP – Terminate PCU pyrotechnic device scrapping via ACL (PCU-End)
- 8.12 APP – Terminate system deployment (Sys-End)
- 9 Service interface (SI) definition between application and OSI layers [Go to Page]
- 9.1 SI — A_Data.req, A_Data.ind, and A_Data.conf service interface (SI)
- 9.2 SI — A_Data.req, A_Data.ind, and A_Data.conf service interface (SI) parameter mapping
- 9.3 Service interface parameters (SIP) [Go to Page]
- 9.3.1 SIP – General
- 9.3.2 SIP – Data type definitions
- 9.3.3 SIP – Mtype, message type
- 9.3.4 SIP – TAtype, target address type
- 9.3.5 SIP – AE, address extension
- 9.3.6 SIP – TA, target address
- 9.3.7 SIP – SA, source address
- 9.3.8 SIP – Length, length of PDU
- 9.3.9 SIP – PDU, protocol data unit
- 9.3.10 SIP – Result, result
- 10 Application layer (AL) [Go to Page]
- 10.1 AL – Applicable ISO 14229-1 UDS functionality
- 10.2 AL – PCU timing parameters
- 10.3 AL – Authentication [Go to Page]
- 10.3.1 AL – Requirements specification – PDT authentication
- 10.3.2 AL – Requirements specification – Fixed-address PCU/PCU(s) authentication
- 10.4 AL – ReadDataByIdentifier – Read PCU hardware deployment method [Go to Page]
- 10.4.1 AL – Requirements specification – Read PCU hardware deployment method
- 10.4.2 AL – Message sequence requirements – Read PcuHardwareDeploymentMethod
- 10.4.3 AL – Message sequence example – Read PcuHardwareDeploymentMethod
- 10.5 AL – ReadDataByIdentifier – Read NumberOfPcu in vehicle [Go to Page]
- 10.5.1 AL – Requirements specification – Read NumberOfPcu in vehicle
- 10.5.2 AL – Message sequence requirements – Read number of PCUs in vehicle
- 10.5.3 AL – Message sequence example – Read NumberOfPcu in vehicle
- 10.6 AL – ReadDataByIdentifier – Read PcuAddressInfo [Go to Page]
- 10.6.1 AL – Requirements specification – Read PcuAddressInfo
- 10.6.2 AL – Message sequence requirements – Read PcuAddressInfo of PCU
- 10.6.3 AL – Message sequence example – Read PcuAddressInfo of DoCAN PCU
- 10.6.4 AL – Message sequence example – Read PcuAddressInfo of DoIP PCU
- 10.7 AL – ReadDataByIdentifier – Report VIN from PCU [Go to Page]
- 10.7.1 AL – Requirements specification – Report VIN from PCU
- 10.7.2 AL – Message sequence requirements – Report VIN from PCU
- 10.7.3 AL – Message sequence example – Report VIN from PCU
- 10.8 AL – ReadDataByIdentifier – Report dismantler information [Go to Page]
- 10.8.1 AL – Requirements specification – Report dismantler information
- 10.8.2 AL – Message sequence requirements – Report dismantler information
- 10.8.3 AL – Message sequence example – Report dismantler information
- 10.9 AL – ReadDataByIdentifier – Read deployment loop identification table [Go to Page]
- 10.9.1 AL – Requirements specification – Read deployment loop identification table
- 10.9.2 AL – Message sequence requirements – Read deployment loop identification table
- 10.9.3 AL – Message sequence example – Read deployment loop identification table
- 10.10 AL – DiagnosticSessionControl – safetySystemDiagnosticSession [Go to Page]
- 10.10.1 AL – Requirements specification – safetySystemDiagnosticSession
- 10.10.2 AL – Message sequence requirements – safetySystemDiagnosticSession
- 10.10.3 AL – Message sequence example – safetySystemDiagnosticSession
- 10.11 AL – TesterPresent [Go to Page]
- 10.11.1 AL – Requirements specification – TesterPresent
- 10.11.2 AL – Message sequence requirements – TesterPresent
- 10.11.3 AL – Message sequence example – TesterPresent
- 10.12 AL – SecurityAccess [Go to Page]
- 10.12.1 AL – Requirements specification – SecurityAccess
- 10.12.2 AL – Message sequence requirements – SecurityAccess
- 10.12.3 AL – Message sequence example – SecurityAccessType = RequestSeed
- 10.12.4 AL – Message sequence example – SecurityAccessType = SendDeploymentKey
- 10.13 AL – WriteDataByIdentifier – Write dismantler information [Go to Page]
- 10.13.1 AL – Requirements specification – Write dismantler identification information
- 10.13.2 AL – Message sequence requirements – Write dismantler identification information
- 10.13.3 AL – Message sequence example – Write dismantler identification information
- 10.14 AL – RoutineControl [Go to Page]
- 10.14.1 AL – Requirements specification – RoutineControl
- 10.14.2 AL – Message sequence requirements – RoutineControl
- 10.14.3 AL – Message sequence example – ExecuteSPL with SF = startRoutine
- 10.14.4 AL – Message sequence example – ExecuteSPL with SF = requestRoutineResult
- 10.14.5 AL – Message sequence example – DeployLoopRoutineID with SF = startRoutine
- 10.14.6 AL – Message sequence example – DeployLoopRoutineID with SF = requestRoutineResult
- 10.15 AL – ACL request deployment sequence (optional) [Go to Page]
- 10.15.1 AL – Requirements specification – ACL request deployment sequence
- 10.15.2 AL – Message sequence requirements – ACL request deployment sequence
- 10.16 AL – ACL confirm deployment sequence (optional) [Go to Page]
- 10.16.1 AL – Requirements specification – ACL confirm deployment sequence
- 10.16.2 AL – Message sequence requirements – ACL confirm deployment sequence (optional)
- 10.17 AL – ACL terminate deployment sequence (optional) [Go to Page]
- 10.17.1 AL – Requirements specification – ACL terminate deployment sequence (optional)
- 10.17.2 AL – Message sequence requirements – ACL terminate deployment sequence
- 10.18 AL – EcuReset [Go to Page]
- 10.18.1 AL – Requirements specification – EcuReset
- 10.18.2 AL – Message sequence requirements – EcuReset
- 10.18.3 AL – Message sequence example – hardReset
- 11 Presentation layer (PL) [Go to Page]
- 11.1 PL – Data type UNUM8
- 11.2 PL – Data type UNUM16
- 11.3 PL – Data type UNUM32
- 11.4 PL – Data type UCHAR8
- 12 Session layer (SL) [Go to Page]
- 12.1 SL – Timing parameters
- 12.2 SL – Error detection
- 13 Transport layer (TL) [Go to Page]
- 13.1 TL – DoCAN
- 13.2 TL – DoIP
- 14 Network layer (NL) [Go to Page]
- 14.1 NL – DoCAN
- 14.2 NL – DoIP
- 15 Data link layer (DLL) [Go to Page]
- 15.1 DLL – CAN L_Data frame padding bytes
- 15.2 DLL – ACL with bidirectional communication [Go to Page]
- 15.2.1 DLL – tP4_Sender timing specification
- 15.2.2 DLL – Bit rate and byte format specification
- 16 Physical layer (PHY) [Go to Page]
- 16.1 PHY – Connection between PDT and vehicle PCU(s)
- 16.2 PHY – Conformance to CAN
- 16.3 PHY – Conformance to Ethernet
- 16.4 PHY – In-vehicle ACL with bidirectional communication (optional) [Go to Page]
- 16.4.1 PHY – Determine ACLType
- 16.4.2 PHY – ACL_CommMode hardware provision
- 16.4.3 PHY – ACL_CommMode conformance to ISO 14230-1
- 16.5 PHY – In-vehicle ACL with PWM signal (optional) [Go to Page]
- 16.5.1 PHY – Determine ACLType
- 16.5.2 PHY – ACL_PWMMode hardware provision
- 16.5.3 PHY – ACL PWM signal specification
- Annex A (informative) Typical configuration of PDT and vehicle PCU
- Annex B (informative) Network architecture examples
- Bibliography [Go to Page]
Copyright 2025 Compu-tecture, Inc.
All Rights Reserved.
About Us /
Careers /
support@madcad.com /
1.800.798.9296