UN R157 Supplement 2 (00 series) · UNECE Regulation No. 157 (ECE R157) — Uniform provisions concerning the approval of vehicles with regard to Automated Lane Keeping Systems.
UN R157 — Supplement 2 to the 00 series of amendments
Supplement 1 → 2
- What changed
- New paragraph 9.3.1.1. requires an R157SWIN to identify the software of the System, as the Software Update and Software Update Management System Regulation specifies.
- If R157SWIN is not held on the vehicle, the manufacturer must declare to the Approval Authority the software version(s) of the vehicle or single ECUs. This declaration must give the connection to the relevant type approvals.
- Old paragraph 9.3.1. is deleted. It required an alternative software identification system if R157SWIN was not implemented.
- Why
- The proposal aimed to introduce the same level of requirements independently from the identification system chosen.
Q1What changed8 changes
Use of an R157SWIN (old para. 9.3.1., new para. 9.3.1.1.)
New paragraph 9.3.1.1. requires an R157SWIN to identify the software of the System, as the Software Update and Software Update Management System Regulation specifies. The R157SWIN may be held on the vehicle. If R157SWIN is not held on the vehicle, the manufacturer must declare to the Approval Authority the software version(s) of the vehicle or single ECUs. This declaration must give the connection to the relevant type approvals. Before this supplement, paragraph 9.3.1. said that an R157SWIN may be implemented by the vehicle manufacturer. If R157SWIN was not implemented, an alternative software identification system, that is, a software version, had to be implemented.
Other changes to paragraph 9.3. and its subparagraphs (paras. 9.3. to 9.3.4.)
Old paragraph 9.3.2., “If the manufacturer implements an R157WIN the following shall apply:”, is deleted. Old paragraphs 9.3.2.1., 9.3.2.2. and 9.3.2.3. are now paragraphs 9.3.1., 9.3.2. and 9.3.3. Paragraph 9.3.1. requires the vehicle manufacturer to have a valid approval according to UN Regulation No. 156 (Software Update and Software Update Management System). Paragraph 9.3.4. now has a comma after “are updated”, and the text of paragraph 9.3. now ends with a full stop.
Q2Why it changed
- Proposed by
- Experts from France
- Working party
- GRVA, 9th session (February 2021)
Reasons
The proposal aimed to introduce the same level of requirements independently from the identification system chosen.
Source
“The proposal above aims to introduce the same level of requirements independently from the identification system chosen”
Document trail
- 2020-11ProposalECE/TRANS/WP.29/GRVA/2021/17Proposal for amendments by the experts from France
- —Amended in sessionGRVA-09-40Alternative proposal by the expert of the UK, the basis of Annex III to the GRVA report
- —Working party adoptsECE/TRANS/WP.29/GRVA/9Session report, para. 26
- 2021-04Sent to WP.29ECE/TRANS/WP.29/2021/74Text that GRVA sent to WP.29 and AC.1
- 2021-06WP.29 adoptsECE/TRANS/WP.29/1159Adopted at the 184th session (session report, para. 127)
- 2022-01-07In forceC.N.21.2022.TREATIES-XI.B.16.157UN depositary notification
Q3Who is affected
Vehicle manufacturer
- Use an R157SWIN to identify the software of the System (paragraph 9.3.1.1.).
- If R157SWIN is not held on the vehicle, declare vehicle or single ECU software version(s) to the Approval Authority.
- In that declaration, give the connection to the relevant type approvals.
- Update your documents that refer to old paragraphs 9.3.2.1., 9.3.2.2. or 9.3.2.3.
Component supplier
- No direct action for this role.
Technical service / Approval authority
- Be ready for declarations of software version(s) when R157SWIN is not held on the vehicle (paragraph 9.3.1.1.).
See every change side by side
RegVault customers compare every version of UN regulations, read the consolidated text and download the PDF.
ⓘ This report gives advice only. It is not legal or type-approval advice.