UNECE WP.29 R156 7.2.1.2.1: Each RXSWIN uniquely identifiable and updated on extension or new approval

What does 7.2.1.2.1 require?

Each RXSWIN is uniquely identifiable; when type-approval-relevant software is modified by the manufacturer the RXSWIN is updated if the change leads to a type approval extension or a new approval. The Interpretation Document asks for a demonstration of how each RXSWIN is generated and made unique and that each has a one-to-one relation with its Regulation.

Maintained by Gerard BlokdykVerified against the published standard 31 May 2026Control text last updated 21 May 2026

Other controls in Paragraph 7.2: Requirements for the vehicle type – UNECE WP.29 R156

7.2.1.1 7.2.1.1 Protect the authenticity and integrity of software updates on the vehicle
7.2.1.2.2 7.2.1.2.2 RXSWIN or software versions readable through a standard interface
7.2.1.2.3 7.2.1.2.3 Protect RXSWINs and software versions on the vehicle against unauthorised modification
7.2.2.1.1 7.2.2.1.1 Restore the previous version or reach a safe state after a failed or interrupted update
7.2.2.1.2 7.2.2.1.2 Execute updates only with enough power to complete or recover
7.2.2.1.3 7.2.2.1.3 Technical means ensure safe execution where an update may affect safety
7.2.2.2 7.2.2.2 Inform the user before execution: purpose, changes, duration, unavailable functions, instructions
7.2.2.3 7.2.2.3 Prevent driving and unsafe functions where execution while driving may be unsafe

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpoint All UNECE WP.29 R156 controls