Proposal to:

• insert new paragraphs 2.71. to 2.78. defining
  • Position Code,
  • Turn Signal Switch Status,
  • Hazard Warning Signal Switch Status,
  • Hazard Warning Signal Lamp Status,
  • Turn Signal Lamp Status,
  • Gear Positions,
  • Seat-Track Position-1, and
  • Seat-Track Position-2,
• Delete existing data elements for Safety belt status by driver position, Frontal air bag deployment by driver and front passenger, Side air bag deployment by driver and front passenger, and Pretensioner deployment by driver and front passenger,
• Amend Table 1 to replace position-specific safety belt, frontal air bag, side air bag, knee airbag, far-side airbag, pretensioner, and occupant size classification entries with X-Y Position Code entries,
• Add Turn Signal Lamp status, Hazard Warning Signal Lamp Status, Turn Signal Switch Status, Hazard Warning Signal Switch Status, Gear Positions, and Seat-Track Position entries with recording intervals from -5.0 to 0 seconds or -1.0 seconds and sample rates of 2 samples per second.

Proposal to amend para. 5.1.1.3. to adjust the lower vertical datum point from 5 degrees to 4 degrees below the horizontal and update the corresponding figure in Annex 4, Figure 1. This harmonizes the location of the lower datum point with the angle of obstruction requirement in para. 5.1.3., resolving an inconsistency between the allowed area of obstruction and the mandated transparent area of the windscreen.

Proposal to increase yaw rate recording frequency to 10 Hz. Yaw-rate data recorded at 2 Hz corresponds to one measurement every 500 ms; increasing to 10 Hz provides a measurement every 100 ms, resulting in a fivefold improvement in temporal resolution. This enhancement significantly improves ability to reconstruct pre-crash vehicle dynamics, identify vehicle instability onset and progression, and evaluate Electronic Stability Control functionality. A yaw-rate recording frequency of at least 10 Hz reduces temporal uncertainty from 500 ms to 100 ms and enables more accurate reconstruction of loss-of-control events, vehicle rotation, ESC interventions, and driving dynamical issues.

Document presents automated shuttles as vehicles designed for public transport with autonomy by design, typically featuring fewer than 10 seats and often limited to 50 km/h maximum speed. Shuttles are deployed globally but are incompatible with current UN vehicle categories: category M₁ does not accommodate standing passengers and is incompatible with crashworthiness regulations, while M₂/M₃ Class A construction alignment is prevented by the fewer-than-10-seat threshold. Proposal calls for a workshop organized by the GRSG/GRVA task force on automated vehicle categories to engage stakeholders and confirm need for an international category or class, addressing administrative questions, alignment with M₂/M₃ regulations, seating capacity, dimensions, weight, speed limits, and bidirectionality options.

The agenda includes:

• DDAW system warnings and driver acknowledgement,
• microsleep detection requirements,
• system effectiveness under varied driving conditions and when DCAS is active,
• system functionality where driver occlusions occur,
• drowsiness thresholds for warnings,
• criteria for classifying false negatives,
• test methods,
• specificity and positive predictive value as performance metrics,
• observer-rated drowsiness,
• timing of future meetings.

Proposal to amend para. 1.4. to clarify obligations for recording data elements where sensors or systems cannot meet specified format requirements. Recording is not required if no system or sensor is designed to provide the trigger or data element, or if not operational at the time of the trigger condition or recording. However, if the vehicle is fitted with an original equipment manufacturer sensor or system designed to provide the trigger or data element in the specified format, reporting in that format is mandatory when operational. Where sensor or system design capabilities do not allow format requirements to be met, the data element shall nevertheless be recorded and the corresponding limitation reported. Failure states shall be recorded by the EDR.

Agenda for the 48th session of the Subgroup on EDR, a hybrid meeting scheduled for 15-16 September 2026 in Berlin. The agenda includes a final review of and potential amendments to official documents to GRSG regarding UN R160 and UN R169, discussion of the need for Step 3 and inventory of potential items for Step 3 workstream with presentations by IWG delegations expected, EDR for ADS, and a list of action items and schedule of future conference call meetings.

Document presents Korean research on event data recorder (EDR) data survivability in electric vehicles following post-crash fires. Analysis of nine Korean EV fire cases shows EDR data retrieval failed in three cases due to ACU damage in fully burned vehicles, while six cases achieved data retrieval despite water immersion from firefighting. The document proposes water immersion testing to assess EDR data survivability for inclusion in EDR Step 3, referencing international automotive standards for test method development.

Clean work-in-progress draft proposal to insert a new para. 0 establishing an introduction for vehicles of categories X and Y equipped with an Automated Driving System, and amend para. 6.1.5. to clarify that the exemption for sensors, cameras, and radar devices being part of driver assistance systems does not apply to automated driving systems unless the ADS performance of the DDT is not affected.

Proposal to insert definitions for Software Identification Number, insert requirements for manufacturers to provide necessary information allowing the Technical Service to uniquely identify hardware and software configurations, insert provisions allowing vehicle manufacturers to apply for new approvals to differentiate software versions for registered versus new vehicles, amend production discontinuation provisions to clarify that cessation is not deemed definitive if the manufacturer intends to obtain subsequent extensions for software updates of vehicles already registered in the market, renumber and insert new items in approval communication annexes regarding software identification and software updates including RxSWIN, and insert provisions allowing vehicle manufacturers to obtain new approvals for software version differentiation across multiple UN Regulations (13, 13-H, 79, 89, 130, 131, 139, 140, 152, 155, 156, 157, 171, 175, and 178).

Status report on activities of the IWG on CS/OTA since the 25th GRVA session. The IWG reviewed proposals for amendment of UN R155 and its interpretation document for multi-stage vehicles, proposals for approval-authority arrangements and Certificates of Compliance for UN R155 and R156, proposals integrating software identification and update text across several UNRs outlined in RE.3, component and STU approval concepts, and remote operation and automated driving systems. The IWG proposes updating regulatory text and interpretation documents for UN R155, revisions to software identification and update text across several regulations, and revised Terms of Reference for a mandate till November 2029.

Proposal to introduce a unified Position Code (X-Y) for all seating positions, add seven new mandatory data elements for driver operation and seat-track position to Annex 4 Table 1, and harmonize ADAS status enumerations into one unified set eliminating fragmented and inconsistent wording across system entries.

Proposal to add footnote 1 to para. 6.2. defining transparency as requisite for the driver’s forward field of vision, for the driver to see and to be seen, and insert new para. 6.3. stating that safety glazing located in a position requisite for driving visibility may not be treated such that it limits or restricts the visibility of the driver from outside, for example by applying a mirror or chameleon effect, with minimum light transmittance provisions as described in Annex 24 applying from both directions.

Proposal to add footnote 1 to para. 6.2. to clarify that safety glazing materials must be sufficiently transparent as a requisite for the driver’s forward field of vision, for the driver to see and to be seen. The amendment aims to clarify possible safety concerns to ensure that the driver can be seen from outside and does not introduce new provisions but clarifies the intent of existing provisions.

The Czech Republic requests guidance from GRSG on whether automatic activation of a dedicated “Call for Help” signal with higher flashing frequency, instead of the standard hazard warning signal following severe vehicle impact linked to UN Regulation No. 144 trigger criteria, conflicts with existing post-crash safety requirements under GRSG competence. A formal proposal to introduce this new signal within UN Regulation No. 48 has been submitted to GRE under document ECE/TRANS/WP.29/GRE/2026/2.

Letter of support from the International Federation of Pedestrians and the European Cyclists Federation for the proposal for Supplement 14 to the 01 series of amendments to UN R43. The submission supports efforts to clarify regulations and ensure that windows within the driver’s forward field of vision meet minimum light-transmission requirements when viewed from both inside and outside the vehicle, and opposes treatments or tints that prevent people outside the vehicle from seeing the driver.

The document describes automated shuttles as vehicles designed for public transport with autonomy by design, typically with fewer than 10 seats, constructed like Class A buses, and often limited in maximum speed or bidirectional. Automated shuttles are deployed globally and already comply with most technical requirements for M₂/M₃ vehicles except some UN R107 requirements and bidirectional aspects. Current UN vehicle categories are incompatible with shuttles: M₁ does not have provisions for standing passengers, and shuttles cannot be granted approvals to most UN Regulations because they have fewer than 10 seats. Three options for categorization are presented: a new category M₄, a new class of M₂/M₃ (Class C), or redefinition of M₂/M₃ Class A. A workshop is proposed for 4 December in Paris to determine whether an international category or class is necessary.

Final draft proposal to:

• Amend para. 1.4. to clarify recording obligations for data elements when sensors lack design capability to meet format requirements,
• Amend para. 2.20. to define engine throttle as driver-requested acceleration torque demand,
• Amend para. 2.73. to define trigger activated,
• Amend para. 5.4.3. to clarify crash test requirements and specify data retrievability after impacts of severity levels set by UN Regulations Nos. 94, 95 or 137,
• Insert new paras. 12.12. through 12.17. establishing transitional provisions with dates from entry into force through 1 September 2035,
• Amend Annex 4 Table 1 to add data elements including occupant size classification, vulnerable road user secondary safety system warning indicator status, and advanced driver distraction warning time since warning issued, with modified recording intervals, sample rates, and ranges for existing data elements.

Minutes of the 48th SG-EDR conference call meeting held 15-16 September 2026. The group conducted final review of official documents for UN R160 and UN R169, reaching agreement on multiple technical specifications: DDAW recording duration of 60 minutes (bracketed for GRSG consideration), DCAS duration of 1000 seconds and 10 warnings, LDWS and data element frequencies of 4 Hz and 10 Hz respectively, yaw rate frequency increased to 10 Hz, and airbag warning lamp adjustments. Transitional provisions set for 2030 and 2035. EDR Step 3 workstream planning identified topics including triggering sensitivity, data elements, L-category vehicles, and data survivability. Governance discussion noted DSSAD separation under IWG ADS2, with EDR work continuing under potential new taskforce structure.

Final draft proposal to amend para. 1.4. to clarify that recording requirements depend on availability of the trigger or data element itself, amend para. 5.3.1.2. to permit the EDR to write last stop trigger data in volatile memory only, accommodating at least five most recent stops to be overwritten on a first-in first-out basis until any other trigger occurs or the vehicle master control switch is deactivated, and amend paras. 2.5., 2.48. and 2.49. for clarity and consistency with UN Regulation No. 160.

Presentation on truck underrun accident prevention examining active safety system performance and rear underrun protection crashworthiness. ADAS testing of seven modern vehicles (2025–2026) at speeds 56–130 km/h toward stationary truck targets in four scenarios found systems currently unable to reliably prevent collisions on motorways. Conspicuity testing of trailers identified reduced performance with offset approaches and darkness. Crash testing of European UN R58.03 rear underrun protection against US IIHS Toughguard at 56 km/h demonstrated latest European RUP incapable of preventing underrun, with recommendation that regulation mandate tougher RUP standards.

Status report on the Special Interest Group on Component & Separate Technical Unit work on UN R158 and UN R159. The SIG-C&STU is developing proposals to add Component and Separate Technical Unit approval routes to UN R151, UN R158, UN R159, and UN R166. For UN R159, Supplement 4 is under review with documents at GRSG-132. For UN R158, a Proposal for Supplement 7 is in development. The group requests feedback on structural approaches and timelines for working document submissions by January 2027.

Proposal to introduce provisions for type approval of Moving Off Information System (MOIS) Component and Separate Technical Unit (STU) by establishing three approval pathways: Part I for vehicles with MOIS, Part II for vehicles with installation of approved MOIS Component or STU, and Part III for MOIS Component or STU themselves. The system detects pedestrians and cyclists in the forward blind spot area and provides information and collision warning signals during low-speed moving off manoeuvres at speeds of 10 km/h or less. Technical requirements cover detection performance for speeds 3–5 km/h for potential moving off and 0–10 km/h for low-speed operation, automatic deactivation on system failure or sensor contamination, manual deactivation through intentional driver actions, and signals that are deactivated together upon failure. Test procedures include static crossing tests, longitudinal stopping and moving off cyclist tests, and failure detection tests performed on flat dry asphalt under natural illumination conditions.

Proposal to introduce provisions for type approval of Moving Off Information System Component and Separate Technical Unit. The supplement adds Part III to UN R159 establishing approval requirements for MOIS Components and STUs, modifies Part I to align with the new component-based approval pathway, and adds Part II to govern vehicles installing previously approved Components or STUs. Manufacturers may choose between Component approval (largely vehicle-independent) or STU approval (tailored to specific vehicle families) to streamline market introduction of MOIS technology.

Proposal to introduce provisions for type approval of Moving Off Information System Component or Separate Technical Unit, establishing three approval routes: Part I for vehicles with integrated systems, Part II for vehicles with approved components or units installed, and Part III for component and separate technical unit approvals. The regulation requires systems to detect pedestrians and cyclists in the forward blind spot during potential moving-off manoeuvres and low-speed manoeuvres at speeds up to 10 km/h, providing information signals and collision warnings. Automatic deactivation occurs upon malfunction or sensor contamination; manual deactivation is permitted through intentional driver actions. Vehicles of category Y and category X without manual on-board operation are exempted. Testing includes static crossing tests, longitudinal stopping and moving-off cyclist tests, failure detection, and automatic deactivation verification.