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.

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.

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.

A study of 24 professional truck drivers investigated how drowsiness develops during real-road driving to test a DDAW system. At night, 17 of 24 drivers reached a KSS level of 8, with average time to reach KSS 8 being 56 minutes. Ten drivers chose to stop or were requested to stop in the sleep-deprived condition. A DDAW recording window of 600 s would fail to capture information relevant to the EDR, whereas time windows of up to one hour could provide important indications of increased driver fatigue.

Proposals for EDR Step 3:

• Improved triggering to increase detection rate of vehicle-to-vulnerable road user collisions and low-severity vehicle-to-vehicle collisions by considering delta-v and jerk-based trigger thresholds and developing updated triggering thresholds,
• Overwriting and multi-event issues by reviewing crash reconstruction experiences and developing updated requirements on overlapping events and overwriting,
• Data elements and formats to improve meaningfulness and close gaps by considering new data elements, modifications to data element format specifications, deviating recording duration, and focus on functions compared to specific systems,
• EDR for vehicles of category L₁–L₇ to establish relevant EDR requirements by understanding specificities of vehicles of category L₁–L₇ and developing triggering conditions, events, data elements, and survivability requirements.

For vehicles equipped with an Automated Driving System, it shall be possible to retrieve DSSAD time-stamp data elements specified under paragraph 5.2. of Annex 8 of UN Regulation No. 185 recorded within at least the last 30 seconds prior to triggering of the respective EDR event, regardless of whether the DSSAD and the EDR are implemented as a single system or as separate systems. The time-stamp data elements retrievable from the DSSAD shall include the record for the last activation or deactivation of the feature used at the time of the event within the same power cycle. The data elements shall be retrievable in the format specified in Annex 8 of UN Regulation No. 185, though DSSAD location data may be omitted and dates and times recorded may be replaced with information representing the time elapsed between the recording of each DSSAD data element and the triggering of the EDR.

Proposal to clarify that the EDR volatile memory buffer for last stop trigger activation shall accommodate data related to at least five different stops to be overwritten on a first-in first-out basis, and that data for the most recent stops shall be written to non-volatile memory in a way that does not interfere with the event record related to any other trigger of paragraph 5.3.1.

Proposal to amend para. 4.1. to condition approval on meeting requirements in para. 5., insert new paras. 4.2. to 4.2.4. to establish approval criteria for vehicles up to 12,000 kg maximum mass equipped with deployable occupant restraint systems meeting UN R160 01 or later, requiring equivalence demonstration of EDR triggering performance for vehicles of 8,000–12,000 kg derived from M₁ or N₁ vehicle types through manufacturer determination of restraint deployment thresholds and physical or simulation testing, renumber former paras. 4.2. to 4.6. as paras. 4.3. to 4.7., amend para. 6.2. to specify communication of approval confirmation or refusal to Contracting Parties, and amend Annex 3 heading to reference paras. 4.5. to 4.5.1.

European Commission priorities for EDR Step 3 include improving detection of vehicle-to-vulnerable road user collisions and low-severity vehicle-to-vehicle collisions through adjusting delta-v trigger thresholds, developing new jerk-based trigger criteria, and exploring ADS collision detection for EDR triggering in automated vehicles on a long-term timeline. Data elements and format must be ensured to remain up-to-date with new safety system developments and close gaps between light and heavy vehicles through reviewing data elements in light of newly regulated safety systems and mirroring DDAW, ADDW and DCAS data elements from UN R160 to UN R169 on short-term and ongoing timelines.

Document SG-EDR-47-02 and SG-EDR-47-03 were discussed. The group agreed to include definitions 2.8, 2.10, 2.11, and 2.20 with edits. Proposed definitions will be circulated by June 15 for review with comments due June 26. For data elements, disagreements on frequency rates between contracting parties and industry remain in square brackets. EDR for ADS will be addressed under GRVA and the ADS IWG. An October in-person meeting in Berlin is planned, pending WP.29 direction on integrating DSSAD into the ADS IWG.

Proposal to amend Annex 4 Table 1 to modify the Vulnerable road user secondary safety system warning indicator status data element to record interval -1.1 to 0 sec, modify the VRU Accident emergency call system status data element to recording interval 0-300 ms or 0 to end of event time plus 30 ms whichever is shorter, add Advanced driver distraction warning (ADDW) status as mandatory with On and Off values for Planar, VRU, Rollover, and AEBS events, add ADDW time since warning issued as mandatory with 0 to 240 sec range and +/-1% accuracy at 1 sec resolution, add Driver control assistance system driver monitoring system time since disengagement warning issued as mandatory with 0 to 1000 sec or 0 to 240 sec range and +/-1% accuracy at 1 sec resolution, add Driver drowsiness and attention warning (DDAW) status as mandatory with On and Off values for Planar, VRU, Rollover, and AEBS events, and add DDAW time since warning issued as mandatory with 0 to 60 min or 0 to 600 seconds range, +/-1% accuracy, and 1 min or 1 sec resolution.

Proposal to amend UN R18, UN R39, UN R46, UN R55, UN R58, UN R67, UN R73, UN R93, UN R97, UN R102, UN R105, UN R107, UN R110, UN R116, UN R121, UN R122, UN R125, UN R144, UN R147, UN R151, UN R158, UN R159, UN R160, UN R161, UN R162, UN R163, UN R166, UN R169, UN R176, UN R181, UN R182 and UN R183:

• Add new paragraphs defining Software Identification Number by reference to Consolidated Resolution on the Construction of Vehicles (R.E.3) Annex 7, para. 2,
• amend paragraphs concerning production discontinuation to clarify that production is not considered definitively discontinued if vehicle manufacturers intend to obtain subsequent extensions of approval for software updates of vehicles already registered in the market,
• add new paragraphs requiring manufacturers to provide Technical Services with information on all hardware and software having an influence on performance,
• add new paragraphs allowing vehicle manufacturers to apply for new vehicle approvals to differentiate software versions for vehicles already registered in the market from those for new vehicles,
• add new paragraphs to approval forms requesting additional information regarding software identification and software updates, including whether Software Identification Number is held on the vehicle and relevant parameters for identification of vehicles that can be updated with the represented software.

Proposal to amend para. 2.5. to change “a potential” to “an imminent” forward collision, insert new paras. 2.48. and 2.49. defining “Non-volatile memory” and “Volatile memory” respectively, and amend para. 5.3.1.2. to permit the EDR to write captured data from Last Stop trigger threshold criterion (a) in volatile memory only, with transfer to non-volatile memory upon occurrence of any other trigger of para. 5.3.1. or deactivation of vehicle master control switch, effective upon entry into force of Supplement 2 to UN R169.

Proposal to amend definitions 2.22 and 2.49 to modify the descriptions of non-volatile and volatile memory, and amend para. 5.3.1.2. to permit the EDR to write captured data from threshold criterion (a) in volatile memory only, with data from volatile memory written to non-volatile memory if any other trigger of para. 5.3.1. occurs or the vehicle master control switch is deactivated. The modification reduces memory wear in vehicles characterized by frequent stops. A version with tracked changes is available.

The agenda includes discussion of EDR Step 2 documents and EDR for ADS documents, review of action items and schedule of future meetings, and adjournment. Future meetings are scheduled for September 8, 2026, and October 6-8, 2026.

The 32nd EDR-DSSAD IWG session convened virtually on May 7, 2026. The previous session report and agenda were approved without objection. Discussion addressed the group’s future structure, with consensus that EDR work continue under GRSG direction while DSSAD work be directed by the ADS IWG. EDR/DSSAD-31-02 on DSSAD regulatory text would be submitted to GRVA in May. A Guidance and Interpretation Document addressing “readily accessible” and access provisions is planned for July submission. EDR Step 2 discussions covered ADDW, DDAW, and DCAS data elements with resolutions agreed at +/-1%, recording intervals for collision scenarios, and outstanding items for June 11 finalization. Future meetings scheduled for June 11, September 8, and October 6-8, 2026.

The 33rd session of the Event Data Recorders/Data Storage Systems for Automated Driving Informal Working Group is scheduled for October 6-8, 2026, in a hybrid format with meetings held at the Ministry of Transport Berlin, Germany. The session will address DSSAD Phase 2 documents, EDR Step 2, EDR Step 3, and EDR for ADS, with meetings conducted via Google Meet and in-person attendance. Chairpersons are from the Netherlands, Japan, and the USA.

The agenda includes discussion of DSSAD regulatory text guidance, EDR Step 2 proposals comments, and EDR for ADS. The next meeting is scheduled for September 15-17, 2026, as a hybrid event in Europe.

The ADS regulations (GTR and UNR) include definitions for reporting thresholds based on EDR triggering. Time-series data recording for heavy vehicles under UN R169 requires triggers and trigger thresholds to record data in specified time periods, which may not immediately precede, follow, or coincide with crashes. Last Stop, Safety Systems, and Sudden Deceleration triggers are unreliable crash indications. Sudden Deceleration is too sensitive for storing time-series data over several months. Optional SRS or a new independent trigger alongside Detected Collision offers the only viable possibility for effective time-series data recording.