Issuu

The P roceedings of The E DR User’s S ummit 2026 TM

The collected, distributable presentation materials from The EDR User’s Summit from Houston, TX March 23-25, 2026 TM

The 2026 User’s SummitTM Presentations • The 2026 EDR User’s SummitTM is in the books and we know everyone’s eager to get their copies of the presentations and that’s what this special issue contains; you may download a copy of this 900+ page issue in PDF format and save it to your computer • It is, however, protected to protect the work of the authors. Please understand that slides with videos don’t work well in PDF and several authors wanted to protect their proprietary video work so videos have been removed • Now, we’ve start making plans for the 2027 EDR user’s Summit. At this point, we’re planning for late February 2027, returning to the Sheraton in Houston (we’re actively working with the hotel on dates for February 2027) March 23-25, 2026

Slide 1

2026 User’s SummitTM Presentations Index – CDR Past, Present and P5 Bosch Future

Vehicle bus Information P229 Capturing in real time

The Crash Pulse CDX: Maintaining Vehicle Access Within the P93 Legacy Bosch CDR Ecosystem Through a Validated VCI

P259 Passenger Vehicle ADAS Testing

Beyond the OBD Port: P155 Accessing uncollected GTS+ vehicle data direct to modules

March 23-25, 2026

ADAS – P319 Genesis/Hyundai/Kia Preliminary Research Reference

P367 EDR/ADAS Crash Test Bus Communications and P493 CAN Data Synchronicity Slide 2

2026 User’s SummitTM Presentations Index P543 An Attorney’s Guide to Reports and Testimony – Avoid Getting Struck P569 Preservation & Analysis of Tesla in-car Video P617 EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

P709 Hyundai and Kia EDR Data Update P785 BMW AEB Testing with EDR Applications P845

Delta-V: Applications and

misapplications of delta-V data Slide 3

Bosch CDR DLC Tool Kit The Bosch CDR DLC Tool Kit contains all hardware required to perform a DLC/OBD retrieval of EDR data supported by the Bosch CDR 900 VCI as stated in the Bosch CDR Help File. This package also includes a 1-year Bosch CDR software license. The Bosch CDR DLC Tool Kit currently supports the largest number of vehicle manufacturers in North America.

March 23-25, 2026

Slide 4

CDR - PAST, PRESENT & FUTURE MAR 23, 2026

Agenda 1. Past - What’s New since 2025 Summit? 2. Present 3. Future

PAST

CDR – Past, Present & Future Past – What’s New since the 2025 Presentation CANplus to CDR 900 migration of MY2010 and newer vehicles was completed in 2025!  Systems migrated in 2024  Includes Mazda systems and  GM SDM10 – SDM40 systems ‒ Plan to release completed GM systems in 26.1 release CANplus systems will remain in the Legacy CDR software  Will continue to be bundled with CDR Software Continued to add new vehicle/OEM brand support to CDR2 application

CDR – Past, Present & Future Past - What’s New since the 2025 Presentation Bosch posted 11 releases (4 major and 7 patches) in 2025  24.3 release, December 2024  25.2 release, Oct 2025 ‒ 24.3 patch1 - Feb 2025 ‒ 25.2 patch1 – Oct 2025 ‒ 24.3 patch2 - Mar 2025  25.3 release, December 2025  v25.0 release, April 21, 2025 ‒ 25.3 Patch1 – Feb 2026 ‒ 25.0 Patch1 – May 2025  25.1 release - Jul 2024  26.0 release is planned for 1st ‒ 25.1 patch1 - Aug 2025 week of April ‒ 25.1 patch2 - Sept 2025 CDR Cable releases were delayed to 2026 9

CDR – Past, Present & Future Past - 24.3 Patch 1 Release (February 2025)  Corrected BMW steering input polarity for ACSM4i systems  Added unsupported VINs on MY24 Traverse Limited and Mercedes-Benz CLE  Cadillac MY21 Escalade and 2024 Chevrolet Traverse, FCMs: fixed error 13 when exporting images  Ford MY2017 Transit, fixed display of CDR report for CDR 900 downloads  Toyota MY24 Tacoma, fixed CDR reports to display all events (requires reimaging)  RAM MY24 Promaster, fixed a report issue where TPS precrash data does not match the graph  Mazda MY24 CX-90, addressed download issue with CDR 900  Mercedes-Benz MY23 S Class, added missing data elements in CDR report  Cadillac MY21 Escalade, FCM: addressed error “no images to be saved” when no images retrieved  Chevrolet, 2024 Traverse: addressed a download error  Added MY2025 coverage for various Ford and Lincoln vehicles 10

CDR – Past, Present & Future Past - 24.3 Patch 2 Release (March 2025) MY23 Ford Expedition, addressed an issue when displaying Time from event 1 to 2 data element Fixed a download issue (part number not supported) on a MY24 Explorer Interceptor Added support for MY25 Acura ADX to the help file

CDR – Past, Present & Future Past - 25.0 Release (April 2025) Added new vehicle support for MY2024 and newer brands for all supported markets Markets included: US, Canada, China, Japan, Europe, S. Korea and Thailand Added support for 2 new GM Active Safety Systems, ACSM & FCM CDR license activation done only in CDR2 17 digit VIN is now mandatory for all brands when starting a new download in Legacy CDR and CDR2 applications

Addressed various field support related issues

CDR – Past, Present & Future Past - 25.0 Patch 1 Release (May 2025) Addressed Volkswagen subscript out of range error and data translation issues Removed request for DID $4AC0 for all GM SDM50 systems which was causing some systems to fail during downloads Added GM EOCM and FCM coverage updates

CDR – Past, Present & Future Past - 25.1 Release (July 2025) Migrated support for several legacy brands to CDR2 and removed from Legacy CDR Software  Dacia, Ferrari, Ford, Jaguar, Karma, Land Rover, Lincoln, Lucid, Mercury, Mobilize, Oshkosh, Renault Migrated CANplus coverage to CDR 900 for remainder of supported Maserati vehicles- MY 2014 to 2024 (CDR Legacy Software) Added PCM support for 2008 – 2009 Ford/Lincoln and Mercury vehicles for NA market (required CANplus interface support) to Legacy CDR software Added carry over vehicle support for MY2024 thru 2026 for various brands and markets Addressed various field support related issues

CDR – Past, Present & Future Past - 25.1 Patch 1 Release (August 2025) Resolved CDR2 Installation, Code meter issues resolved and licensing issues Resolved a Ford download issue in CDR2 BMW ACSM6 data translation issues resolved in CDR2 Fixed data collection error with MY2025 Nissan Altima and Versa 2015 Jeep Renegade, fixed discrepancy with ignition cycles Mitsubishi AB12 an enumeration issues with RPM & Steering data elements GM SDM-50 ACM, fixed a download issue Fixed a performance issue when generating a CDR report for VWGroup vehicles Added MY2026 Jeep, Dodge and Chrysler vehicle coverage 15

CDR – Past, Present & Future Past - 25.1 Patch 2 Release (September 2025) Added support for 2025 MY Jeep Compass and corresponding system for EU Market

CDR – Past, Present & Future Past - 25.2 Release (October 2025)  Added new vehicle support for MY2025 and newer brands for all supported markets  Implemented support for 2 new OEMs (INEOS and VinFast) for US and EU markets  Continued migration of CDR helpfile data from CDR Legacy to CDR2 software  Added support for a new GM active safety system for MY 2024 to MY 2027 GM vehicles ‒ Requires Cable ID 870 (available Q1 2026)

 Various bug fixes

CDR – Past, Present & Future Past - 25.2 Patch 1 Release (October 2025) 2025 MY Fiat Grande Panda and Tipo (EU market) 2026 MY Jeep Cherokee (US market) Added missing VIN support for MY 2026 Pacifica (US market)

CDR – Past, Present & Future Past - 25.3 Release (December 2025) Added new MY26 vehicle coverage, worldwide Added support for 9 new ECUs on existing supported brands to support new vehicle coverage, including GM (FCM), Honda, Subaru, Toyota and Volvo for worldwide support Continued migration of CDR helpfile data from Legacy CDR to CDR2 software Various bug fixes addressed in this release

CDR – Past, Present & Future Past - 25.3 Patch 1 Release (February 2026) CDR 900 FW Update to support GM FCM camera with DoIP communications Fixed “software ID not supported” error for MY 2025 Ford Explorer Updated software for a specification to Nissan AB12 system EDR with DIC 72 – changed display criteria for Longitudinal / Lateral acceleration for DIC:72h Updated xFCA MY26 coverage for Chrysler and Jeep Gladiator Added new system support for GM ACP2 FCM various GM vehicles Updated various data elements for Toyota 24EDR S06 Std system Critical issues were addressed in CDR2 software for BMW, Suzuki and Volvo brands

PRESENT

CDR – Past, Present & Future Present – Discontinued Support for Windows 10 Starting CDR v26.0 (April release date) Window 10 OS is no longer supported. Although it may install, Bosch will no longer test it on Win 10 systems This is due to Microsoft’s discontinued support of Windows 10 since October 2025

CDR – Past, Present & Future Present – Current software Currently, there are the legacy and CDR2 side-by-side versions of the CDR Tool software

Legacy GUI 23

CDR2 GUI

CDR – Past, Present & Future Present – CDR 900 coverage migration  The larger plan, announced since 2019 at the EDR User’s Summit, has been to migrate supported vehicle coverage from CANplus module to CDR 900 (is now completed)  One driving reason was associated with the CANplus end-of-life and to migrate systems the CDR 900 as the common CDR Tool interface going forward  Starting in 2024, version number strategy was changed to associate the release number to the current year of the release  The “MV.VN.RRR” format (Major Ver . minor Version Number . build Revision number)  i.e.: 25.3.1617 (current CDR Legacy version) or 25.3.1254 (current CDR2 version)

CDR – Past, Present & Future Present – CDR2 Side menu  Be sure to check the side menu beyond the “basics”  There is a flyout for “Settings”  The “Additional” section expands in the side menu

CDR – Past, Present & Future Present– CDR2 Settings

CDR – Past, Present & Future Present – CDR2 Settings  (Data) “Logging” is for troubleshooting, it’s not a keystroke tracker  “VIN check digit” forces the CDR2 software to confirm the North American VIN structure based on the check digit, disabling it means the end user might inadvertently enter the wrong VIN – where a user entered VIN might not match the actual VIN on the vehicle or retrieved from the ECU  “CDR Application” – deactivate or active the CDR2 application software license certificate  “Language” – select English, German, Chinese or French for the GUI not the output report

CDR – Past, Present & Future Present – CDR2 Settings - “Language”  Notice the report language in the background, English but the message from the GUI is in German

CDR – Past, Present & Future Present – CDR2 Settings - “Language”  Notice the report language in the background

CDR – Past, Present & Future Present – CDR2 Settings  “Devices” – relates to the CDR 900 and CDR 500 for connectivity and firmware updates  Notably, the CANPlus is not listed here – the CANPlus is not supported in CDR2  The CDR 900 “Trash can” unregisters the device from the current computer

 “Units of measurement” – options are metric and Imperial and the selection is designed to affect the data translation report, does not change the underlying data units as recorded in the module in the car and may not change the OEM display formatting choices  49CFR563 still calls for units, where applicable, to be reported in metric

CDR – Past, Present & Future Present – CDR2 Settings – “Units of measurement”  “Units of measurement” – options are metric and Imperial  Changes the output in the data translation report PDF and the CSV output file  49CFR563 still calls for units, where applicable, to be reported in metric

CDR – Past, Present & Future Present – 49CFR563 compliance  Some OEMs are already moving toward 20sec of pre-crash data and Bosch is working with them to implement the changes going forward (example here: BMW)

INSTALLATION & CDR 900 UPDATES

CDR – Past, Present & Future Present - Installation notes  CDR v23.1 was the last CDR Legacy stand-alone version released  v24.0.550 – CDR2 patch includes an update to the CDR 900 firmware  Watch for an “Update your CDR 900 Device” dialog box during installation

 v24.1.197 – adds the build revision number (last three of the version number) to the setup file and the Legacy CDR software version number display  Starting at v24.3.576 a reboot is normally required at the end of the installation process  Some revision (patch) installations may not require a reboot

 Starting at v25.0.817 activation for both versions is done within the CDR2 interface with one activation certificate applied to both versions after activating CDR2 35

CDR – Past, Present & Future Present – latest release  The current version and some older versions remain available at https://cdr.boschdiagnostics.com/cdr/softwaredownloads

 “… IMPORTANT NOTICE: Robert Bosch LLC and the manufacturers whose vehicles are accessible using the CDR System urge end users to use the latest production release of the Crash Data Retrieval system software when viewing, printing or exporting any retrieved data from within the CDR program. Using the latest version of the CDR software is the best way to ensure that retrieved data has been translated using the most current information provided by the manufacturers of the vehicles supported by this product. …”

Latest CDR Software available

CDR – Past, Present & Future Present - CDR 900 firmware updates  Updates to the CDR 900 firmware are announced in the “What’s New in this Version” release notes  And, of course, by way of the “Update your CDR 900 Device” dialog box displayed during the installation sequence  Recent firmware updates were released with versions  v24.0.550  v25.3.1254 (current patch, firmware update required)

CDR – Past, Present & Future Present –CDR 900 firmware  Reprogram CDR 900 firmware within CDR2 software to take advantage of current operating functions

CDR – Past, Present & Future Present - CDR 900 firmware updates  If the CDR 900 firmware is not updated to the version of CDR2, the CDR2 software will display a popup dialog box indicating the CDR 900 firmware version is wrong and needs to be updated  There is no separate pop-up in the Legacy interface indicating the firmware in CDR 900 is incorrect  If the end user tires to “roll back” the CDR2 software (with a reinstallation of an older version the software) and the CDR 900 had been previously updated, that will also cause a “wrong firmware” error

CDR – Past, Present & Future Present - CDR 900 firmware updates  In the CDR Legacy software there is the “Connection Help” pulldown icon

 In CDR2, that utility is now in both the sidebar menu at “Additional” and in the Settings menu  The option to test the CDR 500 is there as well  But, not CANPlus… 40

(because…?)

CDR – Past, Present & Future Present - another note about the CDR 900  The CDR 900 is recognized in Windows as a network device (as seen here in Device Manager)  Notice that there are no COM ports in this device list, CDR 900 does not rely on a COM port selection or the USB to Serial (RS232) adapter

CDR – Past, Present & Future Present – another note about the CDR 900  CDR 900 is recognized as a network device in Windows  Where the CDR Tool software fails to communicate with the CDR 900 one of the more common reasons is that the laptop is connected to another network or the “IT guys” have restricted the laptop’s access to other networks or otherwise “unknown” networks  Your CDR 900 must be installed as separate network device for CDR software to see the device and connect to it

MIGRATION OF CDR COVERAGE INTO CDR2 (WITH THE EXCEPTION OF CANPLUS SYSTEMS)

CDR – Past, Present & Future Present - Vehicle/module coverage plan CDR2 Software is planned to support all vehicles with the CDR 900 interface module and will not support vehicles requiring the CANplus module  CDR 500 and other new vehicle interfaces will be supported by CDR2 software

Interface Module & Adapters

CDR 900 Interface

CDR2 software will provide Vehicle and Cable lookup information for all CDR supported vehicles including CANplus supported vehicles

‒ Migration of CDR 900 supported vehicles from CDR Legacy software is in progress and is planned to be completed end of 2026 Automotive Service Solutions | MA-AS/PAD-PRM2 | 2026-03-23 – EDR Summit © 2026 Bosch Automotive Service Solutions Inc. and affiliates. All rights reserved.

CDR 500 Adapter Other new adapters CANplus Interface (and associated adapters)

CDR2 Software

Legacy CDR Legacy CDR Software Software (final, (through end of 2026) 2027+)

CDR – Past, Present & Future Present - Vehicle/module coverage plan  Legacy CDR software - through end of 2026!  Non-migrated CDR 900 supported vehicles will be completed end of 2026  As CDR 900 systems are migrated to CDR2, these vehicles will be removed from CDR Legacy Interface Module & Adapters software  CDR 500 will be supported in Legacy CDR software until end of 2026

CDR 900 Interface CDR 500 Adapter

 Legacy CDR software (final ver 2027+)  Will support only vehicles requiring CANplus interface and associated adapters and cables  CDR 500 will not be supported  Will be distributed with CDR2 application 45

Other new adapters CANplus Interface (and associated adapters)

CDR2 Software

Legacy CDR Legacy CDR Software Software (final, (through end of 2026) 2027+)

CDR – Past, Present & Future Present - Vehicle/module coverage plan Migration of CDR supported vehicles is planned to be completed the end of 2026 Until end of migration plan, CDR coverage information may be a little awkward, but the following rules apply until then  When looking up supported vehicles, start with loading the Legacy CDR software and use the Vehicle and Cable Look Up section of the CDR help file  All CDR supported brands are included in the Help File but when you reach a brand where the information can be found in CDR2 software, it will let you know and provide a link to the CDR software application  The proceed to look up the vehicle in CDR2 software which will include the same the information as used to be in the CDR help file but in a different format 46

CDR – Past, Present & Future Present - Vehicle/module coverage plan When CDR2 migration is complete, you will use one CDR software (CDR2) for vehicle lookup, information, coverage, etc. The only reason to use the Legacy CDR software will be to open an old CDR/CDRx file and download via CANplus supported vehicles  Opening an old CDR file will be prompted by windows when a file is double clicked

The CDR2 application will inform users if CANplus and Legacy CDR software is needed

CDR – Past, Present & Future Present – New vehicle/module coverage look up  One of many improvements in CDR2 is to include vehicle coverage information in the CDR2 application  Over the last year, Bosch has been migrating Vehicle and Cable lookup help Information into the CDR2 application… but we are not quite finished …is planned to be finalized by the end of 2026  Below lists the vehicles that are not currently migrated to the help file in CDR v26.0

 Acura

 Chrysler

 Hummer

 RAM

 AVGM

 Dodge

 International

 Saab

 BrightDrop

 GM

 Isuzu

 Saturn

 Buick

 GMC

 Jeep

 SRT

 Cadillac

 Geo

 Oldsmobile

 Sterling

 Chevrolet

 Honda

 Pontiac

CDR – Past, Present & Future Present - Vehicle/module coverage lookup Until all vehicle coverage is migrated to CDR2 application, it is suggested to continue to open the Legacy CDR software first to use the Vehicle and Cable Lookup help file to check for supported vehicles

CDR – Past, Present & Future Present - Vehicle/module coverage lookup  The help file will provide “unmigrated” supported vehicles and information but for vehicles that are called out in the CDR2 application, it will direct users to the CDR2 software via a link  Because CDR2 has the look up information in the app, that does not mean you need to use CDR2, there still maybe an addition step to return the Legacy CDR software… so, don’t close the Legacy software Legacy CDR Software help file, listing Chevrolet vehicles

Legacy CDR Software help file, pointing to CDR2 application

Click to open CDR2

CDR – Past, Present & Future Present - Vehicle/module coverage lookup  NOTE: clicking on the CDR2 link seen here often results in a Window Security Warning related to ActiveX  This is a function outside the CDR application and is a local setting on the user’s PC  It does NOT disable accessing CDR2 from a desktop icon

CDR – Past, Present & Future Present - Vehicle/module coverage lookup  If CDR2 application does not start when the link is clicked, you will need to enable ActiveX in your PC’s Internet Options under security settings, but this requires administrative rights Internet Options

 Otherwise, you will need to launch CDR2 application manually Launch CDR2 from Windows Start

CDR – Past, Present & Future Present - Vehicle/module coverage  Over the last releases of CDR since 2024, the Supported Vehicles in Legacy helpfile have been migrating into to CDR2 software  The lookup format in CDR2 has improved from Legacy CDR but the content remains generally the same as the Help File

CDR – Past, Present & Future Present - Vehicle/module coverage  In CDR2 supported vehicle option, you can check if a vehicle is supported vehicles 2 ways,  Start a New CDR Download, or  Select the Supported Vehicles option from the left menu (or from the tile in the main screen  In both cases, it provides ECU location, what CDR application, VCI info, Cable number, notes as it would in the Help File New Download

Supported Vehicle & Cable lookup

CDR – Past, Present & Future Present - Vehicle/module coverage  Open CDR2 application and select the Supported Vehicles menu item on the left  Select “Brand”, “Year” and “Model” from the drop-down menus  The end-user must affirmatively select from each drop-down down menu  Otherwise, the vehicle is not selected in CDR2

CDR – Past, Present & Future Present - Vehicle/module coverage  Cable, notes, module location, supported markets, etc. are shown once the vehicle is selected

But careful reading of the CDR2 vehicle listing shows…

CDR – Past, Present & Future Present - Vehicle/module coverage – read the notes!!

CDR – Past, Present & Future Present - Variations on the available “Notes” information

CDR – Past, Present & Future Present - Vehicle/module coverage  Systems that are not supported by CDR 900 and/or CDR2 software are listed  i.e., the brand “Ford” is no longer listed in the Legacy CDR software’s Help File but certain systems are still supported and called out

CDR – Past, Present & Future Present - Vehicle/module coverage  Although “Ford” is no longer listed in the Legacy CDR software Help File, some systems are still supported in the Legacy software  Here ACM and PCM are both Legacy software accessible only

CDR – Past, Present & Future Present -“Market Code” is now “Supported Markets”  Pay attention to the Supported Markets which is same as Market Code in CDR Legacy software, for regional coverage

CDR – Past, Present & Future Present - Vehicle/module coverage  Supported markets are regionally specific

CDR – Past, Present & Future Present - Vehicle/module coverage  Most system coverage for these brands have also been migrated to CDR2 with some exceptions  CANPlus supported vehicles can only be downloaded with Legacy CDR software even though they may be listed in the CDR2 application  i.e.: the Ford PCM , Ford Takata ACMs, older GMs, etc.

 As of 25.3, brands marked with * in the list to the right have some CDR 900 supported systems still included in the CDR Legacy software  These systems are also identified in CDR2 Vehicle Support data 64

 This list will change as systems get migrated Automotive Service Solutions | MA-AS/PAD-PRM2 | 2026-03-23 – EDR Summit © 2026 Bosch Automotive Service Solutions Inc. and affiliates. All rights reserved.

CDR – Past, Present & Future Present - Vehicle/module coverage  In CDR2, if a vehicle is selected for download but is not supported in CDR2 during the retrieval setup process (normally at the brand selection and VIN entry screen) if the system is identified as not supported in CDR2, there may be a dialog box indicating the system will have to be accessed using the CDR Legacy Software

CDR READER

CDR – Past, Present & Future Present -“Reader Version” vs “Help File reader”  Prior to CDR v3.6 (in what is now referred to as the CDR Legacy application), the program could be installed and the end user could open a “.CDR” or “.CDRx” file in a reader format  It was often referred to as a “File Reader Version”

 That function was removed at v3.6 and later replaced with a “Help File Reader” version where the application could be installed but the data retrieval and data file opening (and printing, etc) functions are not available until the program is properly activated

CDR – Past, Present & Future Present -“Reader Version” vs “Help File reader”  In the CDR Legacy application, the Help file was stored in “.chm” format  A “CHM” file is a Microsoft Compiled HTML Help file  It is compressed archive format used primarily for offline documentation, digital books, and help systems  A “CHM” is portable and the “cdr.chm” Help file could be used independently of the CDR Legacy application for lookup ‒ Some copied the CHM file to smart phones with CHM file reader functions for use in the field

CDR – Past, Present & Future Present -“Reader Version” vs “Help File reader”  In CDR2, the Help file functions are built into the application  The Help file is not loaded into a separate, standalone file or document  Once CDR2 is installed, but not activated, the data retrieval, and file open/review functions are not enabled, but the Help File content is available as a “Help File Reader”

CDR – Past, Present & Future Present -“Reader Version” vs “Help File reader”  After CDR2 is installed, but not activated, the data retrieval, and file open/review functions are not enabled, but the Help File content and Settings (where it can be activated) are available

DATA FILE LOCATIONS FILE NAME CONVENTION

CDR – Past, Present & Future Present - File storage location by version  Starting with release 23.2, CDR2 is installed simultaneously with the Legacy CDR software  Two installation folders are created in the \Program Files (x86) folder

 Two data file folders are created in the \Documents folder  For CDR Legacy .CDRx files: Documents\Crash Data Retrieval  For .CDRnx files:

Documents\Bosch\Crash Data Retrieval 2  The actual path may be different if you’re using OneDrive 72

CDR – Past, Present & Future Present - File storage location by version  The default CDRx file folder can be user selected from the CDR Legacy software menu under “Setup”

 Currently, there is no option for changing the default file storage location in CDR2  A reminder of the default file location is displayed at the imaging options screen as “default folder”

CDR – Past, Present & Future Present - File name convention  The CDR Legacy file name extension is either .CDR (prior to CDR v3.5) or .CDRx (3.5 and later)  The CDR2 file name extension is .CDRnx  In the Legacy CDR software, “CDR files” (raw data files) retrieved with an older version of the software could be opened in the current version

CDR – Past, Present & Future Present - File name convention  CDR2 files (.CDRnx) cannot be opened in the CDR Legacy application  Currently, CDR Legacy files (.CDR and .CDRx) cannot be opened in the CDR2 application even if the vehicle system is currently supported in CDR2  But the files can still be opened in the current Legacy CDR software version

 On the end user’s computer, even if the extension isn’t visible, the icon will identify the association

TROUBLESHOOTING

CDR – Past, Present & Future Troubleshooting – element names  Not all data element names or acronyms are found in the Data Limitations text for all OEMs  One should always check the Help File Glossary for data element names which may not be defined in the Data Limitations text

 Another potential resource is the current version of SAE Recommended Practice J1698-1 “Event Data Recorder - Output Data Definition”  “… 1. SCOPE ‒ This Recommended Practice provides common data output formats and definitions for a variety of data elements that may be useful for analyzing vehicle crash and crash-like events that meet specified trigger criteria. The document is intended to govern data element definitions, to provide a minimum data element set, and to specify EDR record format as applicable for light-duty motor vehicle Original Equipment applications. …”

 The Help File Glossary has not currently been moved to or updated in the CDR2 application

CDR – Past, Present & Future Troubleshooting – element names  Other sources for element names include 49CFR563, the EU R160 regulation, and through the OEM themselves – their web sites, technical manuals, and products such as Toyota GTS+ (“Techstream”)  Examples:  Toyota “DCM date” is defined in the GTS+ Help file as coming from the "Data Communication Module," normally driven by telematics, the DCM date/time should be reported as UTC not the vehicle clock display  VW Group “MKB” – an event type associated with “external triggers” rather than qualifying collision events like AEB. In VWG documents, is used for Multi Collision Brake (“Multikollisionsbremse”)  “TVV” – “Type, Version and Variant” – normally marked N/A (or similar for North American sales vehicles, the element name remains in data translation reports as referenced in EU R160

CDR – Past, Present & Future Troubleshooting – “Known Issues”  In the CDR Legacy application Help File there is a “Known Issues an Information” table  While useful, as a part of the CDR Legacy Help file, this isn’t necessarily actively updated – content is limited, use with caution

CDR – Past, Present & Future Troubleshooting – “Known Issues” – example  From the CDR Legacy application Help File regarding “Events Recovered = Invalid, Unknown EDID”

CDR – Past, Present & Future Troubleshooting – “Known Issues” – example  “Events Recovered = Invalid, Unknown EDID” is not the same as “an “Invalid” event record or where the “Save without VIN Sequence Number” creates a “CRC Check” error

CDR – Past, Present & Future Troubleshooting – BMW “Unknown EDID” solution  One might find “Events Recovered = Invalid, Unknown EDID” in data from one of the multiple BMW Advanced Crash Safety Module variants currently supported (ACSM – the BMW designation for the ACM)  The “Unknown EDID” is associated with a use case where the original ACSM programming done by BMW might be updated (reflashed) later at a BMW dealer making whatever data set was or could have been there no longer translatable

 As it relates to retrieving data using the CDR Tool, there may be recorded events but with relatively older ACSM programming, they may not be translated in the CDR application  Working with BMW, Bosch has made software updates where data from some of these modules can now be retrieved and translated into a data translation report

 Potential Solution: If the end user has an older raw data file with the BMW “Unknown EDID” error, data may be accessible with a second (newer) data retrieval 82

CDR – Past, Present & Future Troubleshooting – Other “Unknown EDID”  One may find “Events Recovered = Invalid, Unknown EDID” for a system other than BMW (example here is a VW system)  For other than BMW systems, there is the potential that where there are no events recorded, the records space exists but there is no valid data to translate

CDR – Past, Present & Future Troubleshooting – GM SDM40 “no communication”  For some GM systems with the SDM40 SDM (ACM) there is a disconnect between the CDR Legacy application and communication with the SDM40 module type  Data retrieval may start and often gets to “Pass 1” then fails and the remaining passes do not run  This “feature” is isolated to GM not other OEM systems

CDR – Past, Present & Future Troubleshooting – GM SDM40 “no communication”  There is no way to identify specifically which vehicles have an installed SDM40 in advance but the label on the ACM itself will probably be marked as an “SDM40” (seen when going D2M)  Some GM systems which may have the SDM40 include:  Chevy: 2018-2021 Traverse, 2019-2022 Silverado, 2021 Suburban, 2021 Tahoe  Buick: 2018-2020 Regal, 2021 Enclave  Cadillac: 2021 Escalade  GMC: 2020-2022 Sierra, 2021 Yukon  … And there may be others

CDR – Past, Present & Future Troubleshooting – GM SDM40/41 “no communication”  The end user will initiate communication/being the imaging process and may see the “No Communication with Module” dialog box/error message  At this point, it appears that the disconnect occurred about Legacy v23.1.1  Retrieval with CDR Legacy v23.1.1 and older (where that vehicle/module is supported in that version) should connect with the module and properly retrieve data  The saved .CDRx file should then be opened in the latest version for the latest translation of the retrieved data  This is being addressed for 26.0 or 26.1 86

FUTURE

CDR – Past, Present & Future Future – New CDR Cables The following CDR (9) cables are planned for release in 2026, starting end of 2Q/2026 through end of year  Available from CDR Tool Distributor ~April/May time-frame ‒ Cable, ID865, CDR Toyota ACM 11 ‒ Cable, ID870, GM ASCM 5 (HC) ‒ Cable, ID867, CDR Ford ACM  Planning availability in Q3 and Q4 ‒ Cable, ID885, CDR Stellantis JT/JL ‒ Cable, ID884, CDR Lucid ACM (Gravity) ‒ Cable, ID882, CDR Volvo ACM (SPA3) ‒ Cable: ID886, CDR BMW ACM  To be determined ‒ Cable, ID881, CDR GM AOS (OCS system) 88 Automotive Service Solutions | MA-AS/PAD-PRM2 | 2026-03-23 – EDR Summit © 2026 Bosch Automotive Service Solutions Inc. and affiliates. All rights reserved.

CDR – Past, Present & Future Future – Wi-Fi Dongle  An updated Wi-Fi dongle will be available later in 2026/7  It will be compatible with CDR 900 firmware in 26.1  Both the new and older Wi-Fi dongles will be compatible

CDR – Past, Present & Future Future – “One-CDR” Project  The final phase of CDR legacy software migration is to add all CDR supported vehicles to be handled in the CDR2 software  except for CANplus supported vehicles  This is in process (Ford, Lucid, Ferrari, Karma are completed in 2025) and MB and VW and BMW brands are planned for 26.0 and all brands to be fully integrated by the end of 2026  This allows the user to launch only one CDR application  Legacy CDR help file content from “Vehicle and Cable Lookup” data will be moved into the CDR2 software, including CANplus supported vehicles  The CDR Glossary will be moved from the Legacy CDR help file directly into the CDR2 application  One-CDR is on schedule to be completed by the end of 2026 90

Experts in position, data logging, and video VBOXautomotive.com Automotive Service Solutions | MA-AS/PAD-PRM2 | 2026-03-23 – EDR Summit © 2026 Bosch Automotive Service Solutions Inc. and affiliates. All rights reserved.

The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI Jason Zeitler Crash Pulse Technologies

March 23-25, 2026

Slide 93

Jason Zeitler Crash Pulse Technologies - Founder NTSB - Senior Investigator Kineticorp - Senior Vehicle Reconstructionist PBSO - Law Enforcement Sergeant - Retired Bachelors of Science - Civil Engineering Masters of Science - Bioengineering (Biomedical) Former SAE Instructor: Vehicle Crash Reconstruction: Principles and Technology Author • •

2021-01-0907 -Validation of EEPROM Chip Removal and Reinstallation for Retrieval of Electronic Crash Data – Destructive and Non-Destructive Methods 2026-01-5009 – Validation of a Legacy-Compatible Vehicle Communication Interface for the Retrieval of Crash Data from Passenger Vehicles

March 23-25, 2026

Slide 94

Agenda • The problem & system constraints • Engineering challenges • CDX system overview • Testing overview – Beta & validation (SAE & ARJ) • Technical insight learned – CDR & Nissan ignition cycle count explanation • Current and future Crash Pulse direction

March 23-25, 2026

Slide 95

March 23-26, 2026

The Problem & System Constraints The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 96

The Problem • CANplus VCI discontinued – 2023 • Legacy vehicles dependency on CANplus hardware and workflows • No official or validated replacement hardware to fill void • Gap in available legacy hardware

March 23-25, 2026

Slide 97

The Problem • Many components to build a CANplus – long discontinued • Thousand+ vehicle entries require CANplus or similar technology • See initial v25.X help file for all CANplus only supported vehicles

March 23-25, 2026

Slide 98

System Constraints • New VCI’s bootloader/firmware must interface seamlessly with Bosch’s CDR software • Must replicate expected device behavior and timing • Multi-protocol vehicle communication required • Cannot legally distribute Bosch’s firmware • Must source long-discontinued components

March 23-25, 2026

Slide 99

March 23-26, 2026

Engineering Challenges The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 100

Engineering Challenges • To build a CANplus or a CDX • PCB with 167 components • ~65 components discontinued • ~1 component has no datasheet • Impossible to recreate • Virtually impossible to source

• Antiquated technology • Complex Programmable Logic Device (CPLD) PLCC-44 present

March 23-25, 2026

Slide 101

Chip Testing

March 23-25, 2026

Slide 102

Engineering Challenges

March 23-25, 2026

Slide 103

Engineering Challenges

March 23-25, 2026

Slide 104

Engineering Challenges

March 23-25, 2026

Slide 105

Engineering Challenges

March 23-25, 2026

Slide 106

March 23-26, 2026

CDX System Overview The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 107

CDX System Overview

March 23-25, 2026

Slide 108

CDX System Overview • CDX VCI • DLC cable • Serial to USB-A (Prolific DB9) cable • Serial to USB-C (Prolific DB9) cable • Extension cable for PCM and ACM Adapter • Power adapter • PLCC-32 chip remover

March 23-25, 2026

Slide 109

CDX System Overview • DTM Adapter - Functionally equivalent (FE) to the 387 • PCM Adapter - FE to the 221 • DLC Adapter 1 - FE to the 709 • DLC Adapter 2 - FE to the 784 • DLC Adapter 3 - FE to the DLC 3 1699200369 • DLC Adapter 4 - FE to the DLC 4 1699200510

March 23-25, 2026

Slide 110

CDX Programmer’s Edition • Allows user to: • Flash bootloader and firmware in real time • Via PLCC32 ROM - socket

• Load custom firmware onto CDX • Allows for quick and easy programming

March 23-25, 2026

Slide 111

March 23-26, 2026

Using the CDX The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 112

Using the CDX • First use • Bootloader interacts with CDR software • Requests an update • Update serial drivers

• Plug and play compatibility • DTM cables • Adapters • CDR software

• The CDX is functionality equivalent to the CANplus

March 23-25, 2026

Slide 113

March 23-26, 2026

Creating the CDX The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 114

Creating the CDX • Over 20 suppliers • MCU programming team • CPLD programming team • Hardware design team • EE diagnosing team • Chip and component sourcing team • Project management team • Testing and validation team • Many other teams… March 23-25, 2026

Slide 115

March 23-26, 2026

CDX Testing The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 116

Beta Testing • Extensive testing across 100’s of vehicles • 20+ vehicle brands • Bootloader compatibility with firmware • Vehicle protocol and timing compatibility • Several rounds of beta testing were required

March 23-25, 2026

Slide 117

Validation Testing

March 23-25, 2026

Slide 118

Validation Testing SAE • 30 vehicle comparison tests • 27 reliability tests • Published February of 2026 ARJ • Many additional tests performed • Additional ACMs and PCMs • Technical paper submitted January of 2026 for publication March 23-25, 2026

Slide 119

“The results of this study demonstrate that the Crash Pulse Technologies CDX VCI provides accurate, consistent, and repeatable crash data retrieval across DLC, DTM, and fuse box back-powering methodologies. Across all 30 test scenarios and 27 repeatability tests, crash data imaged using the CDX matched the output produced by the discontinued CANplus VCI, with differences limited to expected non-critical fields such as timestamps or user entered comments. Testing further confirmed full compatibility with existing Bosch DTM cables and adapters, as well as reliable performance when using replacement adapters and cables designed for legacy CANplus communication. These findings indicate that the CDX VCI is a functionally equivalent and technically reliable option for platforms that continue to require CANplus-based communication in connection with the Bosch CDR translation software. The demonstrated consistency of outputs aligns with Daubert expectations for accuracy and repeatability in forensic data acquisition. This study validates legacy compatibility. Future protocols, if introduced, would require separate assessment. Conclusions presented here are solely those of the author and are not affiliated with or endorsed by Bosch, Vetronix, the NTSB, or any federal government agency.”

March 23-25, 2026

Slide 120

March 23-26, 2026

Data Comparison The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 121

Data Comparison Example CANplus

CDX

March 23-25, 2026

Slide 122

Data Comparison Example CANplus

CDX

March 23-25, 2026

Slide 123

Data Comparison Example CANplus

CDX

March 23-25, 2026

Slide 124

Data Comparison Example CANplus

CDX

March 23-25, 2026

Slide 125

Reliability & Repeatability • Requested during SAE peer-review • 27 tests across three ACMs • Each ACM

• (4) CANplus downloads • (4) CDX downloads

• Consistent results across all vehicles and both VCIs Source: SAE 2026-01-5009

March 23-25, 2026

Slide 126

March 23-26, 2026

QA/QC The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 127

Stress Testing • Each CDX PCB

• ACM downloads of various vehicle brands • PCM downloads – 222, 223, 224 • ROS downloads • PCMs with RDS

• Power-on >1-hour

• Plus, thermal imaging to evaluate performance of chips and temperature

• Extreme testing using programmable power supply to simulate the harshest scenarios

March 23-25, 2026

Slide 128

Thermal Imaging

March 23-25, 2026

Slide 129

Thermal Imaging

March 23-25, 2026

Slide 130

Thermal Imaging

March 23-25, 2026

Slide 131

Programmable Power Supply

March 23-25, 2026

Slide 132

Programmable Power Supply

March 23-25, 2026

Slide 133

Chip-Level Evaluation – Logic Chip

March 23-25, 2026

Slide 134

Testing Hardware

March 23-25, 2026

Slide 135

March 23-26, 2026

Reliability & Warranty The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 136

Reliability & Warranty • Every CDX undergoes extensive testing • Date code of chips • Three-year warranty • Previously one-year

• If you ever have any issues, contact me

March 23-25, 2026

Slide 137

March 23-26, 2026

System-Level Takeaways The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 138

System-Level Takeaways • CDX maintains access to legacy vehicle crash data in the Bosch CDR ecosystem • Solves limited access to the aging discontinued CANplus hardware • While supplies last • There is a finite amount of chips

• Relieves migration pressure • Requires genuine Bosch CDR license to use the CDX March 23-25, 2026

Slide 139

March 23-26, 2026

What Does the Test CANplus Screen Really Mean? The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 140

Test CANplus

March 23-25, 2026

Slide 141

Test CANplus

March 23-25, 2026

Slide 142

Test CANplus

SW0 – General config SW1 – LS CAN* SW2 – The “catch all” SW3 – Toyota, Lexus, Scion SW4 – Dodge, Chrysler SW5 – Nissan SW6 – Honda, Acura, Mazda

March 23-25, 2026

Slide 143

March 23-26, 2026

Nissan: Double Ignition Cycle Anomaly Explained The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 144

Nissan: Double Ignition Cycle Anomaly

March 23-25, 2026

Slide 145

Nissan: Double Ignition Cycle Anomaly

March 23-25, 2026

Slide 146

zzzz…

Nissan: Double Ignition Cycle Anomaly

No data

DTM Adapter ACM Power off – try something else

March 23-25, 2026

Slide 147

Nissan: Double Ignition Cycle Anomaly

Save data? Yes! Save…

DTM Adapter

Then… ACM power off

March 23-25, 2026

Slide 148

Nissan: Double Ignition Cycle Anomaly

Do all Nissan ACMs increment twice? DTM Adapter

March 23-25, 2026

Why?

Slide 149

March 23-26, 2026

Current & Future Direction of Crash Pulse The Crash Pulse CDX: Maintaining Legacy Vehicle Access Within the Bosch CDR Ecosystem Through a Validated VCI

March 23-25, 2026

Slide 150

Current & Future Direction of Crash Pulse • CDX

• Requested projects

• Few smaller projects will be next • Collaborate with other engineers on larger projects

• Likely next project

• Soft launched in November • SAE technical paper – February 2026 • EDR Summit – March 2026 • NAPARs – April 2026 - attending • IPTM – May 2026 - speaking

March 23-25, 2026

• Discontinued ACM cables • Discontinued PCM cables • ACK Adapter • DLC power adapters • Voltage meters

• …?

Slide 151

Contact Information Jason Zeitler Crash Pulse Technologies (561) 504-0815 jason@crashpulse.com CrashPulse.com US Store: CrashPulseUS.com

March 23-25, 2026

Slide 152

Explore the library 1. Scan the QR code 2. Add any point cloud to your cart 3. Use the discount code in your flyer for a free download

February 5-7, 2024

Slide 153

February 5-7, 2024

Slide 154

Beyond the OBD Port:

Accessing uncollected GTS+ vehicle data direct to modules David Carr – Impact Collision Forensics LLC. Augspurger Komm Engineering Inc.

March 23-25, 2026

Slide 155

David Carr • Retired Vehicular Crimes Detective • Glendale, AZ

• Pedestrian and Motorcycle Crashes • Impairment • EDR

• Owner – Impact Collision Forensics LLC. • Reconstructionist • Testing

• Augspurger Komm Engineering Inc • Reconstructionist • Testing

March 23-25, 2026

Slide 156

March 23-26, 2026

Understand the Software Beyond the OBD Port: Accessing uncollected GTS+ vehicle data direct to modules

March 23-25, 2026

Slide 157

Understand the Software • Dealer level diagnostic tool • Toyota and Lexus vehicles

• Replacement to older Techstream Software • Integrated into TIS – Toyota Information System

March 23-25, 2026

Slide 158

Understand the Software • Use with J2534 compliant pass-thru devices • Mongoose Plus - MFC3 • Bosch CDR 900 • Snap-n Pass Thru Pro III • Nexiq • Autel MaxiSys and VCI (MS909)

March 23-25, 2026

Slide 159

Understand the Software Which is preferred? (cost) • Mongoose is the manufacturer’s tool of choice • Order (Bosch CDR or GTS+) • If using CDR 900 for both CDR and GTS+ • start with GTS+, then CDR

March 23-25, 2026

Slide 160

Understand the Software Technical Information System (TIS) Integration • Information related to the vehicle • Real-time service look up • Wiring diagrams • Technical Service Bulletins

March 23-25, 2026

Slide 161

Understand the Software Technical Information System (TIS) Integration • Information related to the Module / Data • RoB – Record of Behavior

• Does a trigger produce photos, or is there just a time-stamp with data? • How many Photos? • How many times will it store before it rewrites over data? • Should I expect data for the event I am investigating?

March 23-25, 2026

Slide 162

Understand the Software Key Features • Advanced Module Reprogramming • ADAS Calibration • Live Data Monitoring

March 23-25, 2026

Slide 163

Understand the Software Key Features • Support for variety of protocol

• Can (Controller Area Network) • Can FD (Flexible Data-Rate) • DolP (Diagnostics over Internet Protocol)

The Internet is needed for 2-day subscriptions Can go offline for 30 days with an annual

March 23-25, 2026

Slide 164

Understand the Software Difference between Can and Can FD

• Payload Capacity • Data Rate • Efficiency

March 23-25, 2026

CAN FD 64 bytes 5-8 Mbps

CAN 8 bytes 1 Mbps

Slide 165

Understand the Software Difference between Can and Can FD

• Improved Reliability • Compatibility

March 23-25, 2026

CAN FD Redundancy Checks Backwards compatible

CAN None Not compatible w/FD

Slide 166

March 23-26, 2026

Navigating the Software Beyond the OBD Port: Accessing uncollected GTS+ vehicle data direct to modules

March 23-25, 2026

Slide 167

Navigating the Software The largest hurdle with GTS+ software • Internet needed • Annual can go offline for 30 days • Lack of going back to older software versions • (bugs, problems with specific vehicles)

March 23-25, 2026

Slide 168

Navigating the Software

March 23-25, 2026

Slide 169

Navigating the Software • Use TIS login Each time you enter software Unless offline

March 23-25, 2026

Slide 170

Navigating the Software

March 23-25, 2026

Slide 171

Navigating the Software • Select VIM • Dropdown will provide all configured Vehicle Interfaces • Select Next on bottom right of screen

March 23-25, 2026

Slide 172

Navigating the Software

March 23-25, 2026

Slide 173

Navigating the Software

Problems with communication • Wrong VIM selection • CDR used with CDR 900 • Incorrect driver

March 23-25, 2026

Slide 174

Navigating the Software

Navigating the Software • Connect via vehicle - OBDII • Connect D2M – Simulated Veh.

March 23-25, 2026

Slide 175

Navigating the Software Navigating the Software • Grayed out icons • Battery voltage What is a normal voltage? • CDR 900 = 11.9v • Mongoose = 12.2v

March 23-25, 2026

Slide 176

March 23-26, 2026

Getting the Data (Direct 2 Module) Beyond the OBD Port: Accessing uncollected GTS+ vehicle data direct to modules

March 23-25, 2026

Slide 177

Getting the Data (Direct 2 Module) • Equipment needed from Vehicle • SRS Module • FRC – Forward Recognition Camera • Denso or Continental

• Network Gateway

March 23-25, 2026

Slide 178

Getting the Data (Direct 2 Module) • Needed Equipment • Vehicle Interface • J2534 tool

• Direct to Module Cable • Crash Data Group

March 23-25, 2026

Slide 179

Getting the Data (Direct 2 Module)

• D2M Rig

• Make your own • Connectors?

• Buy GTS+ D2M Interface

March 23-25, 2026

Slide 180

Getting the Data (Direct 2 Module)

• Wiring for FRC • 12 pin and 16 pin

• View is looking from front

March 23-25, 2026

Slide 181

Getting the Data (Direct 2 Module)

• Wiring for connections • Connector

• view is from the front Male Pins

Male Pins

• Harvest connectors from donor vehicle March 23-25, 2026

1 6

Slide 182

Getting the Data (Direct 2 Module)

• Standard benchtop download

• Clamp down the SRS module • Resistor switch to I for 120 ohms • Connect all components • Power up before connect to computer

March 23-25, 2026

Slide 183

Getting the Data (Direct 2 Module) • Components

• D2M Interface • FRC cables • DLC Adapter • Can/Can FD Cable • Power supply

**Each cable group has a different pin count to fit proper labels on the interface

March 23-25, 2026

Slide 184

Getting the Data (Direct 2 Module) • Network Gateway module • Does not have to be from the harvest vehicle

Connector

• Does need to be CAN FD Connector 90980 – 12E32

March 23-25, 2026

Slide 185

Getting the Data (Direct 2 Module) • Network Gateway module • CAN v. CAN FD • Needed for Images and CAN FD VCH • Not needed for Images only • Not needed for Can VCH with Images

March 23-25, 2026

Slide 186

Getting the Data (Direct 2 Module) • Network Gateway module • CAN FD VCH comes in the Gateway (From SRS) • Out Gateway to the DLC in CAN terminal wires

March 23-25, 2026

Slide 187

Getting the Data (Direct 2 Module) • Network Gateway module • New CDR2 does not show CDR900 only

• Shows CDR 900 • No differentiation between CDR900 only v. CDR900 or CANplus

• Install an Older version of CDR- print out/screenshot vehicle lookup • Veh Lookup – find model and year with CDR 900 only

March 23-25, 2026

Slide 188

Getting the Data (Direct 2 Module) • Best practice for Imaging data (Order of Operations) • Connect (Get your equipment set up) • Health Check (Ensure proper communication) • VCH and download as CSV (Default location is in downloads folder)

March 23-25, 2026

Slide 189

Getting the Data (Direct 2 Module) • Best practice for Imaging data (Order of Operations) • PCS Download (find folder where VDAS file is saved) • Go to stored data icon (Save data) • Power down • Disconnect from the vehicle, then modules

March 23-25, 2026

Slide 190

Getting the Data (Direct 2 Module) • Health Check (First step) • Main Menu (Light Green)

March 23-25, 2026

Slide 191

Getting the Data (Direct 2 Module) • Health Check • Connected modules • Calibration Information • RoB (Record of Behavior) information green • DTC’s present • Print Screen (Print as PDF)

March 23-25, 2026

Slide 192

Getting the Data (Direct 2 Module) • Toggle screens

• Hamburger (top left)

• Main Menu or Vehicle Control History

March 23-25, 2026

Slide 193

Getting the Data (Direct 2 Module)

• VCH Data

• Read Data (Time Estimation) • Progress bar

March 23-25, 2026

Slide 194

Getting the Data (Direct 2 Module) • VCH Data

• Export CSV • Know what file its saved in • Shows Images • Shows Overwrite data

March 23-25, 2026

Slide 195

Getting the Data (Direct 2 Module)

• PCS Data (Pre-Collision System) • FFD (Freeze Frame Data)

March 23-25, 2026

Slide 196

Getting the Data (Direct 2 Module) PCS Data

• Not supported

• Production date

• Wrong option in beginning of the connection • W or W/O ADK (Autonomous Driving Kits) • Examples: May Mobility and Aurora Innovations

March 23-25, 2026

Slide 197

Getting the Data (Direct 2 Module) PCS Data

• Legal Notice • Read or CSV

March 23-25, 2026

Slide 198

Getting the Data (Direct 2 Module) PCS Data

Select the data you want.

March 23-25, 2026

Slide 199

Getting the Data (Direct 2 Module) PCS Data • Estimated Time • Progress Bar

March 23-25, 2026

Slide 200

Getting the Data (Direct 2 Module) PCS Data • Complete notification • You now have options

March 23-25, 2026

Slide 201

Getting the Data (Direct 2 Module) Check PCS • Data charts

• Odometer • Date/Time • Key Cycle • What type of trigger • Number of overwrites

March 23-25, 2026

Slide 202

Getting the Data (Direct 2 Module) View PCS • Toggle between frames • Frame count • EDR data linked to Images • Only if EDR related • Some Triggers not EDR

March 23-25, 2026

Slide 203

Getting the Data (Direct 2 Module) View PCS • Print file (pdf) • Data • Photos on last page

March 23-25, 2026

Slide 204

Getting the Data (Direct 2 Module) • View PCS • Video screen record • Snipping tool

• Play images from the beginning • Video of 21 frames will play like video

March 23-25, 2026

Slide 205

Getting the Data (Direct 2 Module) • Stored Data • Use this feature to save files • VDAS • GTSE • CSV Click write to save…(Find file location)

March 23-25, 2026

Slide 206

March 23-26, 2026

Case Review Beyond the OBD Port: Accessing uncollected GTS+ vehicle data direct to modules

March 23-25, 2026

Slide 207

Getting the Data (Direct 2 Module) • Vehicle Lexus RX350

March 23-25, 2026

Slide 208

Getting the Data (Direct 2 Module) Background

Lexus

• Nighttime Crash • Freeway in Phoenix • ADOT photo of final rest

Chrysler March 23-25, 2026

Slide 209

Getting the Data (Direct 2 Module) Lexus statements • In #3 lane • Hit and started spinning/rear ended • Going straight, no lane changes

March 23-25, 2026

Slide 210

Getting the Data (Direct 2 Module) Chrysler statements • In #3 lane • Lexus merged into her lane • Causing her to rear-end Lexus

March 23-25, 2026

Slide 211

Getting the Data (Direct 2 Module) Witness to events • I Saw everything • Lexus in #2 lane, Chrysler in #3 lane • Lexus merged without blinker

March 23-25, 2026

Slide 212

Getting the Data (Direct 2 Module) Officers Report • Lexus labeled TU1, Chrysler TU2 • Lexus in #2 lane, Chrysler in #3 lane • Lexus merged without blinker

Report diagram – No photos at scene

March 23-25, 2026

Slide 213

Getting the Data (Direct 2 Module) Lexus Inspection Wall Damage

March 23-25, 2026

Side swipe/Pit marks

Slide 214

Getting the Data (Direct 2 Module) Data • Bosch CDR and GTS+ downloads • Lexus 55 mph • Released Accelerator • Accelerated by 5 mph • Two impacts (rear/3.25 secs/wall impact)

March 23-25, 2026

Slide 215

Getting the Data (Direct 2 Module) FRC Images

(23 images about .4 sec apart)

• Approx. 5 sec before Chrysler impact • Approx. 5 sec after

March 23-25, 2026

Slide 216

Getting the Data (Direct 2 Module) FRC Images

(23 images about .4 sec apart)

March 23-25, 2026

Slide 217

Getting the Data (Direct 2 Module) FRC Images

(23 images about .4 sec apart)

March 23-25, 2026

Slide 218

Getting the Data (Direct 2 Module) FRC Images

(23 images about .4 sec apart)

March 23-25, 2026

Slide 219

Getting the Data (Direct 2 Module) Conclusion • No one believed the Lexus Driver – No police photos • Witness only added more confusion • PCS/ Forward Recognition Camera Photos clearly show Lexus in #3 lane

March 23-25, 2026

Slide 220

Getting the Data (Direct 2 Module) Conclusion • Lexus driver telling truth, In lane #3 • Data shows the Chrysler struck the rear of Lexus • Driver yaws, counter steers • Chrysler does a Pit maneuver • Lexus rotates into the barrier / final rest March 23-25, 2026

Slide 221

March 23-26, 2026

Tips for success Beyond the OBD Port: Accessing uncollected GTS+ vehicle data direct to modules

March 23-25, 2026

Slide 222

Tips for success • Create a flow chart / Systematic • Be Patient • There is no one rule for each year and model (since 2020)

• Many trims • Chips were in high demand • Previous year modules used in new year builds (Especially in new TSS versions) • Third-party modifications and special builds

March 23-25, 2026

Slide 223

Tips for success • Practice using the software • Get used to restarting the software and logging back in • If all you have is FRC

• An SRS module needs to be plugged in for images • Does not need to be the one from the same vehicle. CAN or CAN FD both work

March 23-25, 2026

Slide 224

Tips for success • Again, be patient

• Discovering new things to date

• Select correct option

• Smart Key is not a big deal • W or W/out ADK - Autonomous Driving Kit – Looks for different equipment

• Some wiring we are finding is different depending on year and models • Get used to restarting program

March 23-25, 2026

Slide 225

Tips for success • Understand Equipment

• TSS model • RoB (Record of Behavior)

(TIS manuals) • Know CAN v. CAN FD

March 23-25, 2026

Slide 226

Tips for success • With proper saving, you can: • Check what you looked at (GTSE and VDAS files) • Retrieve the Vehicle Control History w/out reconnecting to vehicle

• Good Hotspot or offline Annual subscription for remote downloads

March 23-25, 2026

Slide 227

Online Database of Experts The Crash Hub is a specialized expert directory for crash reconstructionists and traffic investigators. This directory allows the visitor to review and retain crash experts around the world. Our directory creates hundreds of leads each year for new cases! www.thecrashhub.com March 23-25, 2026

Slide 228

Capturing Vehicle bus Information in real time CAN Bus Fundamentals, Access, and Sample Rates Jim Lau Racelogic

March 23-25, 2026

Slide 229

Jim Lau • Technical Director, Racelogic • Supporting VBOX data logging equipment since 2005 • Co-Instructor: SAE C2413: ADAS & Accident Reconstruction • Reverse Engineering vehicle CAN data • Executing complex AR and ADAS testing scenarios • Expertise in GNSS, IMU, RTK, video integration • Jim.Lau@racelogic.com March 23-25, 2026

Slide 230

Objectives • Understand the basics of CAN Bus Technology • Identify Methods for Accessing and Logging CAN Data • Interpret CAN Data at Varying Sample Rates

March 23-25, 2026

Slide 231

March 23-26, 2026

CAN Fundamentals Capturing Vehicle bus Information in real time CAN Bus Fundamentals, Access, and Sample Rates

March 23-25, 2026

Slide 232

CAN: Definitions • CAN stands for Controller Area Network. • Like a LAN for computers — sensors and modules share a single two-wire bus instead of individual point-to-point wires.

March 23-25, 2026

Slide 233

Diagnostic CAN • Request-reply protocol used for emissions testing and OEM scan tools. • Limitations:

• Limited bandwidth and response time • Generally focused on engine data • Steering angle, wheel speeds, brake pressure may not be available

March 23-25, 2026

Slide 234

High-Speed CAN • Module-level data broadcast onto the CAN bus constantly — no request needed. • Typically 20 to 100 Hz data rate • Used for testing - the data logger reads signals as fast as the vehicle's own systems.

March 23-25, 2026

Slide 235

CAN Bus Properties • CAN bus uses a two-wire twisted pair: CAN High and CAN Low. • Voltage levels:

• CAN High: between 2.5V and 3.75V • CAN Low: between 2.5V and 1.25V

• Differential signalling makes CAN resilient to noise and safe to tap.

March 23-25, 2026

Slide 236

CAN Bus Baud Rate • All nodes on a CAN Bus must run at the same baud rate or the bus will crash. • Standard CAN:

• Most common baud rate: 500 kbit

• CAN FD (Flexible Data-Rate):

• Newer protocol with higher data rates • All nodes must be CAN FD compliant • Common rates: 500 kbit bus / 2 Mbit data packets

March 23-25, 2026

Slide 237

CAN Bus IDs • Each message on a CAN bus has an ID.

• Lower ID = higher priority (safety-critical signals)

• Message sizes:

• Standard CAN: up to 8 bytes (64 bits) • CAN FD: up to 64 bytes (512 bits) • One message carries several signals.

March 23-25, 2026

Slide 238

CAN Data Format • Signals on a CAN bus can be:

• Single bit: on/off (e.g. brake light, blind spot warning) • Few bits: e.g. 2-bit turn signal (off, left, right, both) • Larger values: steering angle, accelerator position, engine speed

• Analog values are encoded as integers and can be scaled and offset.

March 23-25, 2026

Slide 239

Interpreting CAN Data • There is no legal or industry requirement to publish CAN bus data or specify its formatting. • Some standardization exists:

• Commercial trucks: J1939 standard - easier to interpret

• Publicly available CAN data exists for many vehicles from enthusiast communities and vehicle software projects. • Racelogic CAN Database

• Free library of decoded CAN signals for VBOX users — from reverse engineering and public sources.

March 23-25, 2026

Slide 240

March 23-26, 2026

How to Access CAN Capturing Vehicle bus Information in real time CAN Bus Fundamentals, Access, and Sample Rates

March 23-25, 2026

Slide 241

Where to Access the CAN Bus • OBD Port • Best success on American and Asian vehicles (~2004-2018).

• Limitations:

• Not used by BMW or VW/Audi/Porsche • Not available in many vehicles from 2018+ due to security requirements

March 23-25, 2026

Slide 242

Where to Access the CAN Bus • Twisted Pairs • Even with no OBD data, almost all modern vehicles use CAN bus accessible by tapping directly into vehicle wiring. • To find wiring:

• Start where lots of vehicle wiring comes together • Try the base of the A-pillar on the passenger side

March 23-25, 2026

Slide 243

Where to Access the CAN Bus • Look for twisted pairs of wires in the vehicle wiring harness. • Access areas where wiring is easy to reach, such as near the fuse box or A-pillar.

March 23-25, 2026

Slide 244

Identifying CAN Wires • Safety first! Do not tap into heavy-gauge wires. • Refer to a vehicle wiring diagram for wire colors and CAN bus names. • Example:

• High-Speed CAN 1 on a blue/white twisted pair - this is the first pair to look for.

March 23-25, 2026

Slide 245

Tools: Vehicle Spy • Vehicle Spy 3 by Intrepid Control Systems • A powerful, cost-effective tool for scanning, decoding, and logging data from CAN bus to a computer. • Bundle includes:

• 2-channel CAN interface • Software - all most users will need March 23-25, 2026

Slide 246

Tools: Pomona Probes • Pomona Insulation Piercing Clip Set • Quickly probe twisted pairs to find vehicle CAN buses. Banana connector connects to CAN interface.

March 23-25, 2026

Slide 247

Tools: Posi-Tap Connectors • Posi-Tap - No Crimp Tap (20-gauge) • Screw-in needle pierces insulation to make contact — no crimping or cutting. • Route CAN data to your logger via wire connected to the tap back. • When removed, leaves only a tiny hole in the insulation.

March 23-25, 2026

Slide 248

Notes of Caution • Avoid transmitting data onto a vehicle CAN bus.

• Risks:

• Connecting a device at a different baud rate causes communication errors • Adding extra traffic can 'confuse' vehicle systems • Disconnecting CAN wiring within the vehicle can cause onboard systems to fail

March 23-25, 2026

Slide 249

March 23-26, 2026

CAN Sample Rates Capturing Vehicle bus Information in real time CAN Bus Fundamentals, Access, and Sample Rates

March 23-25, 2026

Slide 250

Sample Rates • How often do you need to know?

• CAN bus bandwidth is not free — OEM engineers choose what to transmit and how often

• Time-critical signals

• Driver inputs (steering) • Vehicle movement (yaw rate)

• Update slowly:

• Temperatures • Window/door positions March 23-25, 2026

Screenshot from full CAN bus log from VBOX 4

Slide 251

Sample Rates: Example Data

March 23-25, 2026

Slide 252

Sample Rates • 100 Hz • 2 Hz • 50 Hz • 50 Hz • 50 Hz • 100 Hz Zoomed to show 1 second of data March 23-25, 2026

Slide 253

Sample Rates Data from same CAN ID is time-aligned

• 100 Hz • 2 Hz • 50 Hz • 50 Hz • 50 Hz • 100 Hz Zoomed to show 0.1 second of data March 23-25, 2026

Slide 254

Sample Rates: How “stale” is this data? Snapshot of data at a specific point on the bus:

• 0 s (logger) • 0.05 s • 0.005 s • 0.005 s • 0.015 s • 0.05 s Zoomed to show 0.1 second of data March 23-25, 2026

Slide 255

Sample Rates: How “stale” is this data? • When viewing a snapshot of CAN data from a log, sample rate must be considered for each channel.

Time

CAN ID

• Raw CAN logs use microsecond timing accuracy

March 23-25, 2026

Slide 256

CAN Data Summary • Fundamentals

• Two-wire shared network; differential signalling; ID-based priority; no publishing requirement

• Access

• OBD port (~2004-2018) or tap twisted pairs; use Posi-Tap for clean semi-permanent connections

• Sample Rates

• Each signal has its own rate; raw CAN logs use microsecond timing; always consider staleness

• Key reminders:

• Try related vehicle data first | Log everything once connected | Don’t probe the orange wires!

March 23-25, 2026

Slide 257

850+ vehicles

Passenger • Trucks • Trailers • Motorcycles Downloadable in seconds

February 5-7, 2024

Slide 258

Passenger Vehicle ADAS Testing Sundar Raman Nagarajan, Forensic Rock

February 5-7, 2024

Slide 259

Sundar Raman Nagarajan • Master of Science – Automotive Engineering • Bachelor of Engineering – Mechanical Engineering • Automotive Collision Engineer, Associate Accident Reconstructionist: ~ 4.5 years • Bosch CDR Technician • Part 107 sUAS Pilot • Works on Accident Reconstruction, ADAS testing • Active Researcher with SAE • Crash CAE Engineer, Nissan India ~ 3 years February 5-7, 2024

Slide 260

Agenda Topic 1: Tesla FCW/AEB Testing Topic 2: Jeep FCW/AEB Testing Topic 3: Genesis/Hyundai/Kia Prelim ADAS Research

February 5-7, 2024

Slide 261

Topic 1: High-Speed FCW & AEB Testing of Tesla Model 3's Across Software Updates (SAE 2025-01-8695) Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 262

Problem Statement General: • ADAS testing data at high speeds - unavailable • No standards/regulations for high-speed testing Tesla – Specific: • Frequent Over the Air (OTA) software updates • Unable to roll back to older versions • Lack of detailed documentation for public reference • Some updates depends on customer’s purchase choice (example: FSD) • Increasing incidents involving ADAS features.

February 5-7, 2024

Slide 263

Introduction/Objective • Evaluate the performance of Tesla’s FCW and AEB under the following conditions: • Test speeds: 35 mph to 80 mph • Vehicles: Five Tesla Model 3’s (2018 MY to 2020 MY) • Four different software versions • Total tests: 148 • Types of targets: 4 • Swerve and non swerve tests • Daytime and Nighttime • Traffic Aware Cruise Control (TACC): OFF and ON

February 5-7, 2024

Slide 264

Introduction – Test Vehicles

February 5-7, 2024

Slide 265

Introduction – Instrumentation

February 5-7, 2024

Slide 266

Introduction – Cameras & Radar

Source: Alldata.com

February 5-7, 2024

Slide 267

Introduction – Stationary Vehicle Targets

Has a corner radar target

February 5-7, 2024

Slide 268

Stationary Targets • Stationary Targets: Difficult to detect and track by ADAS sensors • A stopped car on the road: akin to a bridge pillar or a traffic sign • Radar: optimized for moving targets. Needs relative speeds. • Cameras: No relative motion, visual cues are weak. February 5-7, 2024

Slide 269

Operation of the System – Owners Manual

February 5-7, 2024

Slide 270

What is Autopilot in Tesla's? Autopilot: Traffic Aware Cruise Control (TACC) + Autosteer TACC: Manages speed and distance with lead vehicle. Can be used independent of Autosteer Autosteer: Tesla's version of lane keeping. TACC always on when Autosteer is on.

February 5-7, 2024

Slide 271

Hanging in there??

February 5-7, 2024

Slide 272

Test Matrix

User selectable FCW settings: Early/Medium/Late

February 5-7, 2024

Slide 273

Test Statistics Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 274

No. of tests based on lighting

104

Day

February 5-7, 2024

Night

Slide 275

Presentation of Warnings Grey – Object in path, not a threat

February 5-7, 2024

Red – Object in path, considered a threat

Slide 276

Effect of Software Versions Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 277

Avg. Distance at Warning

February 5-7, 2024

Slide 278

Avg. TTC at Warn

February 5-7, 2024

Slide 279

Avg. Distance at AEB

February 5-7, 2024

Slide 280

Avg. TTC at AEB

February 5-7, 2024

Slide 281

Avg. AEB Decelerations – 16 Impact tests

February 5-7, 2024

Slide 282

Summary – Effect of Software versions • Consistent and repeatable FCW/AEB across all S/W versions • S/W versions influence the issuance of FCW/AEB. • The influence was quantified and compared in terms of distances and TTC. • Peak AEB decelerations up to 1.2g could be achieved in Tesla’s. • Avg. TTC at FCW (all S/W and speeds): 1.26 s to 3.35 s • Avg. TTC at AEB (all S/W and speeds): 1.05 s to 1.64 s.

February 5-7, 2024

Slide 283

Discussion on TACC Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 284

TACC – CAN Data

No FCW/AEB CAN recorded

February 5-7, 2024

Slide 285

TACC – CAN Data

TACC engages brake pedal to decelerate Physical brake pedal depression observed

February 5-7, 2024

Slide 286

Comparison TACC ON v. OFF Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 287

80 mph Tests – v11.1 167 %

February 5-7, 2024

167 %

Slide 288

Conclusions • Consistent and repeatable FCW: 35 to 80 mph • S/W versions influence the issuance of FCW/AEB. • AEB decelerations greater than 1g was obtained in testing. • With TACC ON:

• No FCW/AEB issued, complete stop from 80 mph. • Physical brake pedal depression up to 70% • Avg. TTC at deceleration: 3.56 seconds. • 167% improvement in distances and TTC at decel compared to manual driving.

February 5-7, 2024

Slide 289

Almost there… but not yet!

February 5-7, 2024

Slide 290

Topic 2: An Evaluation of the performance of the AEB and FCW in a 2020 Jeep Grand Cherokee (SAE 2025-01-8698) Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 291

Introduction/Objective • Evaluate the performance of Jeep’s FCW and AEB under the following conditions: • Test speeds: 35 mph to 70 mph • Vehicles: Two Jeep Grand Cherokees (2020) • Total tests: 40 • Daytime tests: 29 • Nighttime tests: 11 (60 mph only) • Types of targets: 3 • Impact and Swerve tests

February 5-7, 2024

Slide 292

Introduction – Test Vehicles

February 5-7, 2024

Slide 293

Introduction – FFCM & Radar

Source: Alldata.com

February 5-7, 2024

Slide 294

Jeep - Instrumentation VBOX HD2 cameras and GoPro

VBOX HD2 & VBOX 3iSL RTK

CAN tapped from the Jeep

CAN Bus Multi Connector

IMU and Antennas

VBOX 3iSL RTK (target)

February 5-7, 2024

Slide 295

Jeep – Owner’s Manual • Forward Collision Warning with Mitigation: • Medium/Far/Near settings • Visual/Audible Warning • Brake Jerk (Haptic Warning) • AEB

February 5-7, 2024

Slide 296

Jeep – CAN Data

February 5-7, 2024

Slide 297

Effect of Speed Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 298

Analysis of average distances

February 5-7, 2024

Slide 299

Analysis of average TTC

February 5-7, 2024

Slide 300

Summary – Effect of Speed • Higher speeds trigger FCW, AEB at greater average distances. • AEB primarily initiates a small, rapid speed reduction before evasive steering is imparted. • Avg. TTC varies significantly with speed, becoming more critical at higher speeds where warning times shorten. • At 70 mph, FCW and AEB trigger at the same average distance and average TTC.

February 5-7, 2024

Slide 301

Effect of Lighting Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 302

Comparison based on Lighting Reminder: All nighttime tests were performed at 60 mph.

February 5-7, 2024

Slide 303

60 mph Day Tests v. 60 mph Night Tests

February 5-7, 2024

Slide 304

Summary – Effect of Lighting • In general, the daytime performance of the system is slightly better than nighttime performance. • More likely than not due to the camera and radar fusion, nighttime performance became nearly as effective as daytime.

February 5-7, 2024

Slide 305

Swerve v. Impact tests Passenger Vehicle ADAS Testing

February 5-7, 2024

Slide 306

60 mph Tests

February 5-7, 2024

Slide 307

60 mph Tests

February 5-7, 2024

Slide 308

Summary – Swerve v. Impact • There was no significant effect between swerve and non swerve tests in the performance of the FCW/AEB systems. • Minor variations (0.01 seconds to 0.15 seconds) existed in the average TTC at FCW/AEB.

February 5-7, 2024

Slide 309

Jeep 1 v. Jeep 2 Performance Note: Both Jeeps are 2020 Model Year.

February 5-7, 2024

Slide 310

60 mph Tests 91.3 %

100%

February 5-7, 2024

Slide 311

60 mph Tests

February 5-7, 2024

Slide 312

Summary – Jeep 1 v. Jeep 2 • No significant difference in FCW/AEB performance was observed between the two Jeeps • Consistent and repeatable FCW/AEB was observed. • Minor differences in performances: Not due to the system’s object detection/warning capabilities.

February 5-7, 2024

Slide 313

Conclusions • Consistent and repeatable FCW/AEB in all tests at an average of 1.91 seconds TTC (ALL tests) • FCW Brake Jerk  AEB. • Avg. TTC at FCW: 1.7 seconds to 2.2 seconds (35 mph to 70 mph tests) • Avg. TTC at AEB: 1.3 seconds to 1.7 seconds (35 mph to 70 mph tests) • Day/Nighttime testing: No significant impact on the average TTC at FCW/AEB. • Swerve/No swerve testing: No significant impact on the average TTC at FCW/AEB. • Jeep 1/ Jeep 2: No significant impact on the average TTC at FCW/AEB. • Avg. AEB decel (60 mph tests) : 0.44g, lasting for 1.5 seconds

February 5-7, 2024

Slide 314

Tesla v. Jeep Comparison – 60mph – Impact Test

February 5-7, 2024

Slide 315

Tesla AEB Decel Profile

February 5-7, 2024

Slide 316

Jeep AEB Decel Profile

February 5-7, 2024

Slide 317

Experts in position, data logging, and video VBOXautomotive.com

February 5-7, 2024

Slide 318

Genesis/Hyundai/Kia ADAS – Preliminary Research Reference A collaborative effort from Forensic Rock and Kent E. Boots & Associates

March 23-25, 2026

Slide 319

Disclaimer This presentation is a hypothetical research reference intended to outline Genesis/Hyundai/Kia vehicle models and model years that may potentially be supported for ADAS data-imaging by GIT in the future. • The information presented here is based solely on a working hypothesis developed from hardware components identified during our review of manufacturer service resources and review of 156 Genesis/Hyundai/Kia EDR reports. • The conclusions may ultimately prove accurate, inaccurate, or partially correct; however, they reflect the most informed assessment possible based on the data available to us at the time of research. •

March 23-25, 2026

Slide 320

Agenda What do we know and not know about G/H/K imaging? • Takeaways from research– Overview • Research methodology • Navigating OEM Service Site • Prelim Analysis • Conclusion •

March 23-25, 2026

Slide 321

What do we know? Product discontinued

March 23-25, 2026

New VCI released

Slide 322

What do we know?

Source: Hyundai/Kia EDR 2.0 manual March 23-25, 2026

Slide 323

What do we know? ADAS DRV2 ECU not found. Example shown is a ADAS DRV ECU from 2022 Kia EV6 (CV)

March 23-25, 2026

Slide 324

What do we know? S/W version 1.0

March 23-25, 2026

S/W version 2.0

Slide 325

What do we know? • Model/Variant codes exist for ALL Genesis/Hyundai/Kia vehicles • Similar to trim levels, dictates availability of features • Indicated within () • Examples: 2023 Kia Seltos (SP2), 2022 Hyundai Tucson (NX4A) • Same year/model vehicle could have different variant codes

March 23-25, 2026

Slide 326

What do we know?

March 23-25, 2026

Slide 327

What do we not know? Which vehicles/models/model year are supported for ADAS imaging? When can we expect an official response from GIT? Is the ADAS data stored in camera/ACM/somewhere else? What if older models get ADAS imaging support in the future? What type of ADAS data can be imaged? What modules need to be removed and preserved?

March 23-25, 2026

Slide 328

Takeaways from research - Overview Does current G/H/K EDR reports provide ADAS relevant data? Was there a pattern observed in vehicles that recorded ADAS in EDR? Was there an ADAS_DRV2 ECU in G/H/K vehicles? Which vehicles potentially may support ADAS imaging in the future? Why do we think certain vehicles may support ADAS imaging in the future? Was there a link between presence of ADAS in EDR and certain vehicle modules? What module(s), if any, should I preserve to future-proof my cases? March 23-25, 2026

Slide 329

Research Methodology 1. Review of EDR Reports

2. Review of OEM Service Info

• File Archives and

• Identify presence

or absence of ADAS DRV ECU

CISS cases • Identify presence/absence of ADAS data

March 23-25, 2026

3. Prepare a Vehicle Coverage Chart

4 Analysis of data

• Vehicles that list

• Trends & Patterns

and do not list ADAS ECU • Highlight vehicles for which ADAS data was recorded in EDR

Slide 330

Review of EDR Reports

March 23-25, 2026

Slide 331

Review of EDR Reports

March 23-25, 2026

Slide 332

Review of EDR Reports

Present in ALL EDR reports, irrespective of presence or absence of the actual ADAS data

March 23-25, 2026

Slide 333

Special Note (1/2) - EDR imaging! Pop Quiz: What happens when you try to image a Hyundai Tucson by wrongly selecting the model as an Elantra and manually entered the correct Tucson VIN? You will still get an EDR report ! However, you will be misled by the headers and footers of the EDR report!

March 23-25, 2026

Slide 334

Special Note (2/2) - EDR imaging! Pop Quiz: What happens when you try to image a Hyundai Tucson (NX4A) by wrongly selecting a Tucson (TL) and manually entered the correct Tucson (NX4A) VIN? You will still get an EDR report ! However, you will be misled by the headers and footers of the EDR report!

March 23-25, 2026

Slide 335

Special Note - EDR imaging!

March 23-25, 2026

Slide 336

Cautionary Steps – EDR Imaging • When you cannot Auto Read VIN from vehicle: • Decode VIN (OEM service site) and know the model/variant code for sure as a part of inspection prep.

• Be cautious of fat-fingering when making model selection. • No raw data file, cannot re-translate!

March 23-25, 2026

Slide 337

Navigating Service Site Genesis: https://www.genesistechinfo.com/ Hyundai: https://www.hyundaitechinfo.com Kia: https://kiatechinfo.snapon.com/ OEM

1- week ($)

1- month ($)

1-Year ($)

Genesis

100

250

2500

Hyundai

600

Kia

150

1500

** 72-hour subscription: $19

March 23-25, 2026

Slide 338

Navigating Service Site What do you get? • • • • • • •

VIN decoding Complete wiring diagrams ADAS operation notes Locations of ADAS components Manuals, Technical Service Bulletins (TSB) Tech Videos Removal/installation instructions……

March 23-25, 2026

Slide 339

Where should I start?

Start with the VIN/Year/Make/Model Use keyword: SRS Click on: SHOP Click any link from SHOP.

March 23-25, 2026

Slide 340

Where should I start?

Brings up the “tree” Expand ADAS

March 23-25, 2026

Slide 341

Where should I start?

• • • • •

March 23-25, 2026

Look up ECU’s Sensors Operation notes Locations of ECU Videos on removal

Slide 342

Research Methodology 1. Review of EDR Reports

2. Review of OEM Service Info

• File Archives and

• Identify presence

or absence of ADAS DRV ECU

CISS cases • Identify presence/absence of ADAS data

March 23-25, 2026

3. Prepare a Vehicle Coverage Chart

4 Analysis of data

• Vehicles that list

• Trends & Patterns

and do not list ADAS ECU • Highlight vehicles for which ADAS data was recorded in EDR

Slide 343

Review of OEM Service Info Review of all G/H/K models between 2020 to 2027 for ADAS ECU components

Example of ADAS not listed (X in charts)

Genesis: https://www.genesistechinfo.com/ Hyundai: https://www.hyundaitechinfo.com Kia: https://kiatechinfo.snapon.com/ March 23-25, 2026

Slide 344

Review of OEM Service Info Review of all G/H/K models between 2020 to 2027 for ADAS ECU components

Example of ADAS listed, but no ADAS ECU’s (XX in charts)

Genesis: https://www.genesistechinfo.com/ Hyundai: https://www.hyundaitechinfo.com Kia: https://kiatechinfo.snapon.com/ March 23-25, 2026

Slide 345

Review of OEM Service Info

Example of ADAS listed with a driving and parking ECU (ADAS_DRV in charts)

Genesis: https://www.genesistechinfo.com/ Hyundai: https://www.hyundaitechinfo.com Kia: https://kiatechinfo.snapon.com/ March 23-25, 2026

Slide 346

Review of OEM Service Info Example of ADAS listed with a driving and parking ECU (ADAS_DRV 1.5 in charts)

Genesis: https://www.genesistechinfo.com/ Hyundai: https://www.hyundaitechinfo.com Kia: https://kiatechinfo.snapon.com/ March 23-25, 2026

Slide 347

Vehicle Coverage Chart

March 23-25, 2026

Slide 348

Vehicle Coverage Chart

March 23-25, 2026

Slide 349

Vehicle Coverage Chart

March 23-25, 2026

Slide 350

Vehicle Coverage Chart

March 23-25, 2026

Slide 351

Vehicle Coverage Chart

March 23-25, 2026

Slide 352

Vehicle Coverage Chart

March 23-25, 2026

Slide 353

Vehicle Coverage Chart

March 23-25, 2026

Slide 354

Analysis – Trends & Patterns • ADAS in EDR reports: Yes • OEM Service site: No ADAS /ECUs listed (marked as X)

March 23-25, 2026

Slide 355

Analysis – Trends & Patterns • ADAS in EDR reports: Yes • OEM Service site: ADAS listed, no driving or parking ECU (marked as XX)

March 23-25, 2026

Slide 356

Analysis – Trends & Patterns • ADAS in EDR reports: Yes • OEM Service site: Listed only parking ECU (marked as Y)

March 23-25, 2026

Slide 357

Analysis – Trends & Patterns • ADAS in EDR reports: Yes • OEM Service site: Listed an ADAS_DRV ECU & a PARK ECU (marked as ADAS_DRV)

March 23-25, 2026

Slide 358

Analysis – Trends & Patterns • ADAS in EDR reports: Yes • OEM Service site: Listed an ADAS_DRV 1.5 ECU (marked as ADAS_DRV 1.5)

March 23-25, 2026

Slide 359

Analysis – Trends & Patterns • Earliest ADAS_DRV ECU located in : • 2021 Genesis G80 (RG3) • 2022 Hyundai Ioniq 5 (NE EV) • 2022 Kia EV6 (CV) • Earliest ADAS_DRV1.5 ECU located in: • 2023 Genesis GV 90 (RS4) • 2023 Hyundai Ioniq 6 (CE EV) • Kia: N/A • ADAS_DRV2 ECU: N/A in any G/H/K vehicles (2020 to 2027)

March 23-25, 2026

Slide 360

Appeal to the community! We need your help!

If you have an EDR report from a Genesis/Hyundai/Kia vehicle that we do not already have information on (cells with no background color in the charts), we would appreciate the following information sent via email to kent@getedrdata.com.

• Model year • Make • Model • Model/Variant Code (e.g. BDm, SP2, etc.) • VIN (if possible) • Type of event

March 23-25, 2026

Slide 361

Conclusions 1. What module(s)*, if any, should I remove to future-proof my cases? • ADAS_DRV ECU** • ADAS_DRV 1.5 ECU** • ADAS_PRK ECU** • SRS/ACM

*Refer to OEM service manual for the location of these modules **These three modules are NOT the ADAS_DRV2 ECU referred to in the GIT Hyundai/Kia EDR 2.0 manual.

March 23-25, 2026

Slide 362

Conclusions 2. Was there a pattern/trend observed between the presence/absence of ADAS ECU and the presence/absence of ADAS parameters in EDR ? • No. Some vehicles recorded ADAS parameters in the EDR although these ECU were not present in the vehicle. 3. Was there an ADAS_DRV2 ECU in G/H/K vehicles? • Service site did not list this even for MY 2027 vehicles

March 23-25, 2026

Slide 363

Ok Done.! Save the knowledge!

March 23-25, 2026

Slide 364

March 23-25, 2026

Slide 365

February 5-7, 2024

Slide 366

EDR/ADAS Crash Test Shawn Harrington Forensic Rock

March 23-25, 2026

Slide 367

March 23-26, 2026

Introduction EDR/ADAS Crash Test

March 23-25, 2026

Slide 368

Shawn Harrington, BSESM, ACTAR •

Principal & Founder of Forensic Rock

•

19+ years experience in Accident Reconstruction, Forensics, & ADAS

•

Testified in State & Federal Courts throughout Country

•

Teaches SAE International Course, C2413: “ADAS Testing & Reconstruction” w/ Jim Lau

•

Volunteer Firefighter

•

Published in SAE, Collision Magazine, ASME

•

Actively researching, publishing, and presenting in the areas of ADAS on passenger vehicles and heavy trucks

March 23-25, 2026

Slide 369

March 23-26, 2026

Overview EDR/ADAS Crash Test

March 23-25, 2026

Slide 370

Overview of EDR/ADAS Crash Test • • • • • • • • • • • • • • •

Introduction What vehicle was tested? What target was tested? Who is testing ADAS? What is TTC and TTC2? What was the test scenario? Instrumentation & Video Sources Testing Videos, Data Analysis & Results What Happened? EDR Download EDR – Finding Time Zero in the Crash Comparing EDR Data to VBOX Photogrammetry & ADS Sequencer in VCRASH Modeling the collision in VCRASH GoPro Revival (thanks Lou Peck!) Thank You – Matt Tarczewski & Roberto Aguirre!

March 23-25, 2026

Slide 371

March 23-26, 2026

What Vehicle was Tested? EDR/ADAS Crash Test

March 23-25, 2026

Slide 372

What Vehicle? • VUT: 2020 Ford Transit T-350 XLT • VUT: Vehicle Under Test

• 15-Passenger Van • RWD • How do we know what ADAS is on the VUT before we test it? • Date of Test: July 10, 2024 • Thus, the tech is current as of summertime 2024

March 23-25, 2026

Slide 373

Monroney Labels • Pull your Monroney label! (I.e., the “window sticker”) • https://monroneylabels.com/

March 23-25, 2026

Slide 374

Monroney Labels • Pulled the Monroney for the VUT • 2020 Ford Transit T-350 RWD

March 23-25, 2026

Slide 375

Owner’s Manual • What ADAS does the 2020 Ford Transit have? • Use your Monroney Label to Start! • Then, go to your Owner’s Manual

March 23-25, 2026

Slide 376

Owner’s Manual No upper bound speed in OM

March 23-25, 2026

Slide 377

ADAS Levels of Functionality

March 23-25, 2026

Slide 378

Alert Sensitivity Settings

March 23-25, 2026

Slide 379

Pre-Collision Assist System Sensors – Camera

March 23-25, 2026

Slide 380

Pre-Collision Assist System Sensors – Radar

March 23-25, 2026

Slide 381

March 23-26, 2026

What Target was Tested? EDR/ADAS Crash Test

March 23-25, 2026

Slide 382

What Target? • POV: 2022 International MV607 • POV: Principal Other Vehicle

• Box Truck rented from Ryder

March 23-25, 2026

Slide 383

What Target? • Tested in a stationary condition • Rear of the truck was facing the front of the VUT

March 23-25, 2026

Slide 384

March 23-26, 2026

Who is Testing ADAS? What is TTC and TTC2? EDR/ADAS Crash Test

March 23-25, 2026

Slide 385

Background –Testing - FCW  Government funded.  Pass/Fail type tests.  FCW test data not easily publicly available.  Does not evaluate AEB/speed reduction. Test vehicle speed (mph)

Target vehicle status

Pass/Fail criteria

Stopped

TTC at least 2.1 s

Decelerating

TTC at least 2.4 s

Slow moving

TTC at least 2.0 s

National Highway Traffic Safety Administration

March 23-25, 2026

Slide 386

Background –Testing - FCW

WAIT!!! TTC  Government funded.  Pass/Fail type tests.  FCW test data not easily publicly available.  Does not evaluate AEB/speed reduction.

Test vehicle speed (mph)

Target vehicle status

Pass/Fail criteria

Stopped

TTC at least 2.1 s

Decelerating

TTC at least 2.4 s

Slow moving

TTC at least 2.0 s

National Highway Traffic Safety Administration

March 23-25, 2026

Slide 387

Definition of Time to Collision (TTC)

March 23-25, 2026

Slide 388

Definition of Time to Collision (TTC)

March 23-25, 2026

Slide 389

Definition of Time to Collision 2 (TTCTest2)

TTC2 becomes significantly more complicated as compared to TTC…why???

March 23-25, 2026

Slide 390

Definition of Time to Collision 2 (TTCTest2)

March 23-25, 2026

Slide 391

Definition of Time to Collision 2 (TTCTest2)

The issue is relative acceleration

March 23-25, 2026

Slide 392

Background –Testing - FCW  Government funded.  Pass/Fail type tests.  FCW test data not easily publicly available.  Does not evaluate AEB/speed reduction. Test vehicle speed (mph)

Target vehicle status

Pass/Fail criteria

1.Stopped

TTC at least 2.1 s

2. Decelerating

TTC2 at least 2.4 s

3. Slow moving

TTC at least 2.0 s

National Highway Traffic Safety Administration

March 23-25, 2026

Slide 393

Background – Testing - FCW  Private, Nonprofit, funded by insurance companies.  Star rating-based evaluation.  Test data publicly available.  Evaluates FCW & AEB/speed reduction.

12 mph tests

25 mph tests

FCW

Speed reduction (mph)

5 to 9

>10

5 to 9

10 to 21

>22

Points

March 23-25, 2026

Slide 394

Background – Testing – FCW

March 23-25, 2026

Slide 395

Background – Testing – FCW

March 23-25, 2026

Slide 396

Background – Testing – FCW

March 23-25, 2026

Slide 397

Background – Testing – FCW 80 km/h ~= 50 mph

50 km/h ~= 31 mph

20 km/h ~= 12 mph

March 23-25, 2026

Slide 398

Background – Testing – FCW

5 km/h ~= 3 mph 15 km/h ~= 9 mph

March 23-25, 2026

Slide 399

Who else is testing FCW & AEB?

March 23-25, 2026

Slide 400

Who else is testing FCW & AEB?

Auto Manufacturers & Suppliers – Is this public? March 23-25, 2026

Slide 401

Who else is testing FCW & AEB?

A lack of public real-world testing above the tests we have previously discussed is exactly why we are here. Auto Manufacturers & Suppliers – Is this public? March 23-25, 2026

Slide 402

March 23-26, 2026

What was the Test Scenario? EDR/ADAS Crash Test

March 23-25, 2026

Slide 403

What was the Test Scenario? • POV was tested in a stationary condition

• ADAS Tip! “Stationary” is different than “Stopped” in object classification

• Rear of the truck was facing the front of the VUT • Collinear testing • Swerve to the left around the rear of the box as late as possible

March 23-25, 2026

Slide 404

What was the Test Scenario?

March 23-25, 2026

Slide 405

What was the Test Scenario?

March 23-25, 2026

Slide 406

Speeds • Four different speeds were tested: • 25 mph • 35 mph • 45 mph • 53 mph

• Swerves were all to the left • Protocol was changed at the end of the test series! • Right swerve tests were added

March 23-25, 2026

Slide 407

March 23-26, 2026

Instrumentation & Video EDR/ADAS Crash Test

March 23-25, 2026

Slide 408

Instrumentation • Two (2) VBOX Dual Antenna 3iSL-RTK’s • One each in the VUT and POV

• VBOX Video HD2 - VUT

• Windshield View • Instrument Cluster View

• Three (3) GoPro Hero 8’s - VUT • Windshield • Over Shoulder • Left front wheel

• VBOX Touch

• Driver speed monitoring • Live CAN feedback

March 23-25, 2026

Slide 409

Instrumentation • CAN Data!

• NeoVI Red 2 • Before VBOX 4 CAN Logging!

• Tapped into CAN via a twisted pair • No data through the DLC

March 23-25, 2026

Slide 410

Video (sUAS) • Three (3) DJI Mini 3 Pro’s

• Great sUAS for all kinds of purposes • Cheap & good obstacle avoidance • Great video & Photo capabilities (esp. Mini 5P)

• Positions

• Nadir (100 to 400 feet) • Nadir (-100 to 250 feet) • Surveillance (Oblique)

March 23-25, 2026

Slide 411

Video (sUAS) • Three (3) DJI Mini 3 Pro’s

• Great sUAS for all kinds of purposes • Cheap & good obstacle avoidance • Great video & Photo capabilities (esp. Mini 5P)

• Positions

• Nadir (100 to 400 feet) • Nadir (-100 to 250 feet) • Surveillance (Oblique)

March 23-25, 2026

Slide 412

Video (sUAS) • Three (3) DJI Mini 3 Pro’s

• Great sUAS for all kinds of purposes • Cheap & good obstacle avoidance • Great video & Photo capabilities (esp. Mini 5P)

• Positions

• Nadir (100 to 400 feet) • Nadir (-100 to 250 feet) • Surveillance (Oblique)

March 23-25, 2026

Slide 413

Rendered & Synced Video Surveillance2

Nadir 2

Nadir 1

GP - Windshield

NOTE: See FR SAE Papers on how we do this

HD2 Windshield

GP – Over Shoulder HD2 - IC

March 23-25, 2026

Steering Wheel Speed* (tens cutoff) Brake & Accel % UTC Time!

GP - LFW

Slide 414

March 23-26, 2026

Testing Videos, Data Analysis & Results EDR/ADAS Crash Test

March 23-25, 2026

Slide 415

Testing Video – 25 mph Surveillance2

Nadir 2

Nadir 1

GP - Windshield

HD2 Windshield

GP – Over Shoulder HD2 - IC

March 23-25, 2026

Steering Wheel Speed* Brake & Accel % UTC Time!

GP - LFW

Slide 416

FCW (Forward Collision Warning) & AEB HD2 Windshield

• FCW presented visually and audibly in IC • Listen for the grind of the AEB (automatic emergency braking) Steering Wheel Speed* Brake & Accel % UTC Time!

HD2 - IC

March 23-25, 2026

Slide 417

Data Analysis – TTC @ FCW • Data was analyzed by first combining the video from the VBOX HD2 video and the 100 Hz data from the VBOX 3i data acquisition system.

• Using the Video Sync channel in File Processor, the 3i .VBO file was merged with the HD2 video file.

• The forward collision warning was presented on the display screen as a flashing “Pre-Collision Assist” message on the instrument cluster. • The point at which the FCW CAN signal changed from ‘0’ to ‘1’ was used to record the data for the FCW. • Adobe Premier was used to determine the timing between the visual and audio FCW signal and then that timing was used to mark the audio FCW in the data. • Parameters such as the speed of the Ford, the distance from the front bumper of the Ford to the rear bumper of the box truck, the TTC to the box truck, and the lateral offset from the centerline of the Ford to the centerline of the box truck were documented and recorded in a spreadsheet. March 23-25, 2026

Slide 418

Data Analysis – TTC @ AEB • Initiation of AEB was recorded when the AEB CAN signal changed from ‘0’ to ‘1’. • Parameters such as the speed of the Ford, the distance from the front bumper of the Ford to the rear bumper of the box truck, the TTC to the box truck, and the lateral offset from the centerline of the Ford to the centerline of the box truck were documented. • The braking due to the AEB was characterized by recording the average longitudinal deceleration, the peak deceleration, the duration of the braking response, and the speed lost during the braking response.

March 23-25, 2026

Slide 419

Data Analysis – TTC @ Swerve

March 23-25, 2026

Slide 420

Data Analysis – TTC @ Swerve • The point at which the steering angle increased to 10 degrees was used to record the data for the beginning of the evasive swerve maneuver. • A second methodology that analyzed the effect of the test driver beginning to anticipate the swerve, and focused on the steering wheel angle velocity (i.e. steering slope) instead, was analyzed and is labeled as ‘Velo’ in the data.

March 23-25, 2026

Slide 421

Results – 25 mph Swerve Tests – FCW Test Date Test Vehicle

7/10/2024 2020 Ford Transit FCW (CAN)

VBOX Speed Sep. Dist TTC (s) File (mph) (ft)

25 mph AVG

1.79 1.92 2.16 1.78 2.02 1.93

24.5 29.3 25.7 25.3 27.6 26.5

64.3 82.4 81.5 65.7 81.3 75.0

March 23-25, 2026

Offset to left (ft) -0.05 -0.25 -0.31 0.07 -0.42 -0.19

FCW (Audio) UTC 15:27:35.620 15:30:00.080 15:31:38.190 15:33:13.890 15:34:48.450

Sep. Dist TTC (s) Speed (mph) (ft) 1.77 1.89 2.12 1.76 1.95 1.9

24.3 29.0 25.8 25.2 27.6 26.4

63.2 80.3 79.9 65.0 78.8 73.5

Offset to left (ft) -0.04 -0.23 -0.3 0.06 -0.41 -0.18

UTC 15:27:35.670 15:30:00.130 15:31:38.230 15:33:13.910 15:34:48.491

Slide 422

Time Visual Time after Warning after CAN signal Audio (s) Warning (s) 0.05 0.23 0.05 0.30 0.04 0.20 0.02 0.20 0.04 0.23 0.04 0.23

Results – 25 mph – AEB & Swerve

AEB

AEB Phase Analysis

1.36

24.8

49.4

0.03

Time after Avg Decel Peak UTC CAN Decel (g) (g) FCW (s) 15:27:36.030 0.41 -0.11 -0.15

1.42 1.55

26.1 25.2

54.4 57.3

-0.13 0.08

15:31:38.900 15:33:14.120

1.44

25.3

53.7

-0.01

Speed Sep. Dist TTC (s) (mph) (ft)

Offset to left (ft)

March 23-25, 2026

Swerve

Speed Loss (g)

Duration (s)

-2.7

1.53

0.71 0.23

-0.13 -0.12

-0.26 -0.27

-3.5 -3.1

1.63 1.76

0.45

-0.12

-0.23

-3.1

1.64

TTC (s)

Speed (mph)

1.21 1.43 1.12 1.3 1.56 1.32

24.3 28.7 24.8 24.8 27.2 26.0

Sep. Dist Offset to (ft) left (ft) 43.0 60.4 40.8 47.3 62.1 50.7

Slide 423

0.13 -0.17 -0.03 0.06 -0.33 -0.07

UTC 15:27:36.210 15:30:00.590 15:31:39.260 15:33:14.390 15:34:48.900

Time After CAN FCW (s) 0.54 0.46 1.03 0.48 0.41 0.58

Testing Video – 35 mph Nadir 2 Surveillance2

GP - Windshield

HD2 Windshield

GP – Over Shoulder HD2 - IC

March 23-25, 2026

• FCW presented visually and audibly in IC • Listen for the grind of the AEB (automatic emergency braking)

Steering Wheel Speed* Brake & Accel % UTC Time!

GP - LFW

Slide 424

Results – 35 mph Swerve Tests – FCW Test Date Test Vehicle

7/10/2024 2020 Ford Transit FCW (CAN)

VBOX Speed Sep. Dist TTC (s) File (mph) (ft)

0 1 35 mph AVG

2.67 2.19 2.39 2.21 2.38 2.37

33.0 34.9 34.8 35.4 34.2 34.5

133.3 112.0 122.1 115.0 119.5 120.4

March 23-25, 2026

Offset to left (ft) 1.76 1.43 2.28 0.43 -0.02 1.18

FCW (Audio) UTC 15:38:25.000 15:39:58.020 15:41:27.400 15:42:53.310 16:20:17.540

TTC (s) Speed (mph)

Sep. Dist (ft)

Offset to left (ft)

2.67 2.18 2.36 2.17 2.35 2.35

133.3 111.4 120.7 113.4 118.0 119.4

1.76 1.44 2.36 0.44 -0.02 1.2

33.0 35.0 34.8 35.6 34.3 34.6

UTC 15:38:25.071 15:39:58.050 15:41:27.444 15:42:53.340 16:20:17.580

Slide 425

Time Visual Time after Warning after CAN signal Audio (s) Warning (s) 0.07 0.27 0.03 0.23 0.04 0.20 0.03 0.20 0.04 0.30 0.04 0.24

Results – 35 mph – AEB & Swerve

AEB Phase Analysis

AEB TC (s)

1.35 1.24 1.40 1.33

Speed Sep. Dist (mph) (ft)

34.5 34.6 34.1 34.4

68.4 62.8 69.9 67.0

Offset to left (ft)

3.21 0.79 0.08 1.36

UTC

15:41:28.470 15:42:54.320 16:20:18.530

March 23-25, 2026

Time after Avg Decel Peak CAN (g) Decel (g) FCW (s)

1.07 0.29 0.99 0.78

-0.11 -0.09 -0.09 -0.10

-0.19 -0.15 -0.21 -0.18

Speed Loss (g)

-3.0 -1.8 -1.7 -2.2

Swerve Duration (s)

1.48 1.33 1.51 1.44

TTC (s)

Speed (mph)

1.49 1.45 1.27 1.15 1.24 1.32

33.0 34.9 33.7 34.5 34.3 34.1

Sep. Dist Offset to (ft) left (ft) 72.7 73.8 62.9 58.3 62.3 66.0

Slide 426

1.81 1.61 3.39 0.88 0.06 1.55

UTC 15:38:25.770 15:39:58.800 15:41:28.580 15:42:54.410 16:20:18.680

Time After CAN FCW (s) 0.70 0.75 1.14 1.07 1.10 0.95

Testing Video – 45 mph HD2 Windshield

• FCW presented visually and audibly in IC • Listen for the grind of the AEB (automatic emergency braking) HD2 - IC

March 23-25, 2026

Steering Wheel Speed* Brake & Accel % UTC Time!

Slide 427

Results – 45 mph Swerve Tests – FCW Test Date Test Vehicle

7/10/2024 2020 Ford Transit FCW (CAN)

VBOX Speed Sep. Dist TTC (s) File (mph) (ft)

2 45 mph AVG

2.35 2.60 2.39 2.37 2.32 2.37 1.41 2.31 2.16

45.5 44.8 35.5 44.4 45.4 44.8 44.0 43.7 44.5

156.7 170.4 124.3 154.7 154.7 156.0 90.4 148.2 140.8

March 23-25, 2026

Offset to left (ft) -0.07 0.13 0.62 0.78 -0.48 -1.03 -0.97 -1.03 -0.55

FCW (Audio) UTC 16:21:54.170 16:24:13.070 16:26:44.530 16:28:28.080 16:48:04.200 16:49:48.460 16:51:24.890 16:52:57.950

TTC (s) Speed (mph)

Sep. Dist (ft)

Offset to left (ft)

2.28 2.54 2.30 2.34 2.32 2.37 2.06 2.31 2.28

152.0 166.5 119.6 152.1 154.7 156.0 134.6 147.6 149.0

-0.09 0.14 0.63 0.76 -0.48 -1.03 -1.01 -1.03 -0.56

45.5 44.7 35.4 44.4 45.4 44.8 44.6 43.6 44.6

UTC 16:21:54.240 16:24:13.130 16:26:44.620 16:28:28.120 16:48:04.200 16:49:48.460 16:51:24.190 16:52:57.960

Slide 428

Time Visual Time after Warning after CAN signal Audio (s) Warning (s) 0.07 0.23 0.06 0.23 0.09 0.27 0.04 0.20 0.03 0.27 0.03 0.27 0.05 0.27 0.04 0.27 0.04 0.26

Results – 45 mph – AEB & Swerve AEB Phase Analysis

AEB TTC (s)

Speed Sep. Dist (mph) (ft)

Offset to left (ft)

UTC

Time after Avg Decel Peak CAN (g) Decel (g) FCW (s) -0.11 -0.20

Swerve

Speed Loss (g)

Duration (s)

-2.9

1.30

1.31

35.7

68.7

0.68

16:26:45.600

1.07

-0.07

-0.20

-1.3

1.41

1.27 1.25 1.29 1.27

44.1 44.3 42.9 43.7

81.9 81.4 81.1 81.4

-0.90 -0.91 -0.67 -0.83

16:49:49.600 16:51:25.010 16:52:59.030

1.14 0.12 1.08 0.78

-0.15 -0.12 -0.13 -0.13

-0.25 -0.20 -0.23 -0.23

-4.1 -3.1 -3.2 -3.5

1.40 1.35 1.37 1.37

March 23-25, 2026

TTC (s)

Speed (mph)

1.18 1.45 1.26 1.21 1.20 1.19 1.18 1.22 1.2

45.5 44.3 35.9 43.4 45.1 43.8 44.0 42.5 43.8

Slide 429

Sep. Dist Offset to (ft) left (ft) 78.7 94.4 66.1 76.8 79.3 76.1 76.2 76.1 76.9

-0.07 0.03 0.74 0.93 -0.28 -0.81 -0.86 -0.59 -0.32

UTC 16:21:55.340 16:24:14.240 16:26:45.650 16:28:29.290 16:48:05.340 16:49:49.690 16:51:25.090 16:52:59.110

Testing Video – 53 mph Surveillance2

Nadir 2

Nadir 1

HD2 Windshield

GP - Windshield

GP – Over Shoulder HD2 - IC

March 23-25, 2026

• FCW presented visually and audibly in IC • Listen for the grind of the AEB (automatic emergency braking)

Steering Wheel Speed* Brake & Accel % UTC Time!

GP - LFW

Slide 430

Results – 53 mph Swerve Tests – FCW Test Date Test Vehicle

7/10/2024 2020 Ford Transit FCW (CAN)

VBOX Speed Sep. Dist TTC (s) File (ft) (mph)

53 mph AVG

2.41 0.97 1.60 2.31 2.06 1.62 2.48 2.36 1.36 1.73 2.15 2.12 2.38 2.24 1.59 2.44 1.30 1.99

53.2 51.5 53.5 52.0 52.7 50.9 52.4 52.1 53.9 52.4 52.2 52.2 51.3 52.8 53.3 53.5 53.6 52.9

188.5 73.5 125.5 176.0 159.2 120.6 190.4 180.3 107.3 132.9 164.1 162.5 179.1 173.8 124.6 190.8 102.5 154.2

Offset to left (ft) -0.05 0.56 -0.58 -0.47 -0.48 -0.16 -0.16 -0.19 -0.25 0.13 -0.07 0.72 -1.02 -2.28 -2.16 0.68 -0.10 -0.98

March 23-25, 2026

FCW (Audio) UTC 16:54:48.170 16:56:26.920 16:58:03.000 16:59:38.500 17:01:14.840 17:02:52.590 18:48:54.160 18:50:47.840 18:52:40.080 18:55:11.410 18:57:19.050 18:59:16.850 19:01:06.780 19:03:08.100 19:04:58.600 19:06:56.070 19:08:48.090

Sep. Dist TTC (s) Speed (mph) (ft) 2.40 2.31 1.58 2.27 2.06 1.84 2.44 2.27 1.31 1.61 2.08 2.06 2.32 2.16 1.52 2.40 1.25 1.93

53.2 52.2 53.5 52.0 52.7 50.8 52.4 52.1 53.8 52.5 52.3 52.3 51.4 52.7 53.5 53.5 53.4 52.9

186.9 176.7 123.9 173.0 159.2 137.0 187.3 173.4 103.4 123.7 159.5 157.9 174.6 166.9 119.2 188.5 97.8 149.4

Offset to left (ft) -0.05 -0.64 -0.59 -0.47 -0.48 -0.24 -0.16 -0.18 -0.29 0.10 -0.12 0.65 -1.02 -2.28 -2.18 0.66 -0.11 -0.99

UTC 16:54:48.190 16:56:25.550 16:58:03.020 16:59:38.540 17:01:14.840 17:02:52.380 18:48:54.200 18:50:47.900 18:52:40.130 18:55:11.490 18:57:19.120 18:59:16.910 19:01:06.840 19:03:08.180 19:04:58.670 19:06:56.100 19:08:48.130

Time Visual Time after Warning after CAN signal Audio (s) Warning (s) 0.05 0.27 0.04 0.20 0.05 0.20 0.07 0.17 0.03 0.27 0.04 0.23 0.04 0.20 0.06 0.27 0.05 0.27 0.08 0.23 0.07 0.23 0.06 0.27 0.06 0.20 0.08 0.23 0.07 0.20 0.03 0.23 0.04 0.23 0.06 0.22

Slide 431

Results – 53 mph Swerve Tests – FCW

FCW (CAN)

VBOX File

25 mph AVG 35 mph AVG 45 mph AVG 53 mph AVG

FCW (Audio)

TTC (s)

Speed (mph)

Sep. Dist (ft)

TTC (s)

Speed (mph)

1.93 2.37 2.16 1.99

26.45 34.49 44.47 52.9

75.04 120.37 140.82 154.18

1.9 2.35 2.28 1.93

26.38 34.55 44.57 52.89

March 23-25, 2026

Time Visual Time after Warning Sep. Dist after CAN (ft) Audio signal (s) Warning (s) 73.45 0.04 0.23 119.36 0.04 0.24 149.01 0.04 0.26 149.38 0.06 0.22

AEB

AEB Phase Analysis

Swerve

TTC (s)

Speed (mph)

Time after Sep. Dist Avg Decel Peak CAN FCW (ft) (g) Decel (g) (s)

Speed Loss (g)

Duration (s)

TTC (s)

Speed (mph)

Time After Sep. Dist CAN FCW (ft) (s)

1.44 1.33 1.27 1.24

25.33 34.4 43.73 52.56

53.71 67.02 81.44 95.3

-3.06 -2.18 -3.47 -5.35

1.64 1.44 1.37 1.32

1.32 1.32 1.2 1.03

25.96 34.07 43.75 52.49

50.73 66 76.91 79.45

0.45 0.78 0.78 0.74

-0.12 -0.1 -0.13 -0.2

-0.23 -0.18 -0.23 -0.36

Slide 432

0.58 0.95 1.12 0.91

Results – 53 mph Swerve Tests – FCW

March 23-25, 2026

Slide 433

Results – 53 mph Swerve Tests – FCW But, WAIT! Are all 53 mph tests the same?

March 23-25, 2026

Slide 434

Results – 53 mph – AEB & Swerve AEB Phase Analysis

AEB TTC (s)

Speed Sep. Dist (mph) (ft)

Offset to left (ft)

UTC

Time after Avg Decel Peak CAN (g) Decel (g) FCW (s)

Speed Loss (g)

Swerve Duration (s)

TTC @ L Swerve: 1.19 secs 1.38 1.27 1.33 1.36 1.30 1.22 1.29 1.24 1.27 1.12 1.26 1.24

52.6 51.7 53.9 52.4 52.1 52.0 50.5 52.8 53.2 52.8 53.5 52.6

106.5 96.3 104.9 104.5 99.7 93.3 96.0 96.2 98.8 86.9 98.6 95.3

-0.56 -0.46 -0.28 -0.05 -0.35 0.04 -1.06 -2.63 -2.26 -0.09 -0.11 -1.23

18:48:55.270 18:50:48.910 18:52:40.110 18:55:11.740 18:57:19.900 18:59:17.760 19:01:07.910 19:03:09.090 19:04:58.930 19:06:57.400 19:08:48.120

1.08 1.04 0.00 0.30 0.82 0.88 1.10 0.96 0.30 1.30 0.03 0.74

-0.15 -0.16 -0.19 -0.18 -0.23 -0.21 -0.21 -0.16 -0.21 -0.19 -0.21 -0.20

-0.30 -0.30 -0.39 -0.32 -0.42 -0.37 -0.36 -0.30 -0.42 -0.33 -0.38 -0.36

-4.7 -4.0 -5.7 -5.2 -6.9 -5.4 -5.7 -4.4 -6.1 -4.6 -6.0 -5.4

TTC @ L Swerve: 1.04 secs

Changed Swerve to Right for Final Two Tests (on fly w/o practice) March 23-25, 2026

1.46 1.35 1.44 1.46 1.41 1.30 1.37 1.33 1.37 1.18 1.35 1.32

TTC (s)

Speed (mph)

1.24 1.30 1.10 1.18 1.08 1.24 1.17 1.04 0.95 1.03 1.05 1.09 0.99 1.11 0.90 1.27 0.89 1.03

52.3 51.2 53.2 51.2 52.2 50.2 52.3 52.3 53.1 52.3 52.5 52.4 50.5 53.1 52.9 53.0 53.0 52.5

Sep. Dist Offset to (ft) left (ft) 95.0 97.6 85.7 88.2 82.4 90.9 89.6 79.5 73.6 79.2 80.5 84.1 73.6 86.1 70.0 98.6 68.9 79.5

-0.18 -0.37 -0.41 0.06 -0.17 0.02 -0.71 -0.59 -0.53 -0.19 -0.38 -0.02 -1.04 -2.70 -2.49 0.13 -0.11 -1.24

Slide 435

UTC 16:54:49.370 16:56:26.590 16:58:03.520 16:59:39.660 17:01:15.840 17:02:52.990 18:48:55.470 18:50:49.130 18:52:40.510 18:55:12.070 18:57:20.140 18:59:17.870 19:01:08.190 19:03:09.220 19:04:59.300 19:06:57.250 19:08:48.500

Time After CAN FCW (s) 1.18 1.04 0.50 1.12 1.00 0.61 1.27 1.23 0.38 0.58 1.02 0.96 1.35 1.04 0.63 1.15 0.37 0.91

Testing Video – 53 mph – Swerve to Right Nadir 2

Surveillance2

Nadir 1

TTC @ FCW: 2.40 secs TTC @ AEB: 1.12 secs

GP Windshield

HD2 Windshield

TTC @ R Swerve: 1.27 secs

GP – Over Shoulder March 23-25, 2026

HD2 - IC

Steering Wheel Speed* Brake & Accel % UTC Time!

GP - LFW Slide 436

Testing Video – 53 mph – Swerve to Right Nadir 2 TTC @ FCW: 1.25 secs

Surveillance2

TTC @ AEB: 1.26 secs GP Windshield

Nadir 1

HD2 Windshield

TTC @ R Swerve: 0.89 secs

Steering Wheel Speed* Brake & Accel % UTC Time! GP – Over Shoulder March 23-25, 2026

HD2 - IC

GP - LFW Slide 437

Testing Video – 53 mph – Swerve to Right

TTC @ R Swerve: 0.89 secs March 23-25, 2026

Slide 438

Testing Video – 53 mph – Swerve to Right

TTC @ R Swerve: 0.89 secs March 23-25, 2026

Slide 439

March 23-26, 2026

What Happened? EDR/ADAS Crash Test

March 23-25, 2026

Slide 440

What happened? • Switched on the fly without practice • The importance of practicing the evasive swerve cannot be understated! • Everyone was OK and no injuries! (Thank goodness) • Thank you to Dino Handzic and Nick Martin who were passengers • So, once everyone is OK, what does any good recon do? • Investigate! March 23-25, 2026

Slide 441

What happened?

March 23-25, 2026

Slide 442

What happened?

March 23-25, 2026

Slide 443

What happened?

March 23-25, 2026

Slide 444

Sideswipe!

March 23-25, 2026

Slide 445

What happened?

0.25 second March 23-25, 2026

Slide 446

What happened?

Dino Handzic March 23-25, 2026

Nick Martin Slide 447

What happened?

Controlled POFR March 23-25, 2026

Slide 448

What happened?

Debris Field March 23-25, 2026

Slide 449

What happened?

Damage March 23-25, 2026

Slide 450

What happened?

Sideswipe March 23-25, 2026

Damage Slide 451

What happened?

Damage to Right Rear Corner March 23-25, 2026

Slide 452

What happened?

Always tape your VBOX Antennae! Survived! March 23-25, 2026

Airbags – Curtain and Thorax w/ Pretensioners Slide 453

Of Course…3D Scans & sUAS

Leica RTC360 Point Cloud March 23-25, 2026

DJI Mini 3 Pro Point Cloud Slide 454

Of Course…EDR Download

AND?!?

March 23-25, 2026

Slide 455

Of Course…EDR Download

AND?!?

March 23-25, 2026

Slide 456

March 23-26, 2026

EDR Download EDR/ADAS Crash Test

March 23-25, 2026

Slide 457

Comparing v24.1.197 to v25.3.1586

v24.1.197

March 23-25, 2026

v25.3.1586

Slide 458

Comparing v24.1.197 to v25.3.1586

v24.1.197

March 23-25, 2026

v25.3.1586

Slide 459

Comparing v24.1.197 to v25.3.1586

v24.1.197

March 23-25, 2026

v25.3.1586

Slide 460

System Status at Event (First Record)

v25.3.1586 March 23-25, 2026

Slide 461

Faults Present (First Record)

v25.3.1586 March 23-25, 2026

Slide 462

Deployment Data (First Record)

v25.3.1586 March 23-25, 2026

Slide 463

Pre-Crash Data -1 sec (First Record)

v25.3.1586 March 23-25, 2026

Slide 464

Pre-Crash Data -5 to 0 sec [10 samples/sec]

v25.3.1586 March 23-25, 2026

Slide 465

Pre-Crash Data -5 to 0 sec [10 samples/sec]

v25.3.1586 March 23-25, 2026

Slide 466

Pre-Crash Data -5 to 0 sec [10 samples/sec]

March 23-25, 2026

Slide 467

Pre-Crash Data -5 to 0 sec [10 samples/sec]

v25.3.1586 March 23-25, 2026

Slide 468

Pre-Crash Data -5 to 0 sec [10 samples/sec]

WAIT!!! What is Time Zero? March 23-25, 2026

Slide 469

March 23-26, 2026

EDR Data – Finding Time Zero EDR/ADAS Crash Test

March 23-25, 2026

Slide 470

Analysis of Damage

March 23-25, 2026

Slide 471

Analysis of Damage – First Contact

March 23-25, 2026

Slide 472

Testing Video – 53 mph – Swerve to Right

March 23-25, 2026

Slide 473

Analysis of Damage – Airbag Deployment

March 23-25, 2026

Slide 474

Analysis of Damage – Algorithm Enable

90 ms after AE 30 fps sUAS video 3 frames before a/b is AE

March 23-25, 2026

Slide 475

Analysis of Damage – Algorithm Enable

3 frames before a/b is AE

March 23-25, 2026

Slide 476

Analysis of Damage – Algorithm Enable

Matched frames using left headlight

March 23-25, 2026

Slide 477

Analysis of Damage – Algorithm Enable

March 23-25, 2026

Slide 478

Analysis of Damage – Algorithm Enable

March 23-25, 2026

Slide 479

Algorithm Enable in Test Suite

March 23-25, 2026

Slide 480

VBOX & EDR: Now Linked to AE!

TTC is ~ -0.2s at Algorithm Enable March 23-25, 2026

Slide 481

March 23-26, 2026

Comparing EDR to VBOX EDR/ADAS Crash Test

March 23-25, 2026

Slide 482

Pre-Crash Data -5 to 0 sec [5 samples/sec]

March 23-25, 2026

Slide 483

Pre-Crash Data -5 to 0 sec [5 samples/sec]

March 23-25, 2026

Slide 484

Pre-Crash Data -5 to 0 sec [5 samples/sec]

Speed in VBOX is 46.7 mph March 23-25, 2026

Slide 485

Pre-Crash Data -5 to 0 sec [5 samples/sec]

March 23-25, 2026

Slide 486

Pre-Crash Data -5 to 0 sec [5 samples/sec]

-1.27 + -0.17 = -1.43 s TTC March 23-25, 2026

Slide 487

Pre-Crash Data -5 to 0 sec [5 samples/sec]

-0.72 + -0.17 = -0.89 s TTC March 23-25, 2026

Slide 488

Summary of EDR • Was there any FCW data in the EDR? • No!

• Do we have any information about the level of braking commanded by the AEB?

Avg. VBOX X_Accel: -0.27g

• Yes

March 23-25, 2026

Slide 489

Questions? Contact & SAE C2413

Shawn Harrington 215 620 1288 sharrington@forensicrock.com SAE C2413 November 3-5, 2026 Mohnton, PA (hour from Philly)

March 23-25, 2026

Slide 490

Slide 491

March 23-26, 2026

Experts in position, data logging, and video VBOXautomotive.com

March 23-25, 2026

Slide 492

CAN Bus Communications and Data Synchronicity Mike Stogsdill J.S. Held, LLC

March 23-25, 2026

Slide 493

Mike Stogsdill • ACTAR - 2268 • CDR Technician Trainer/Mentor • Berla Certified Vehicle System Examiner • Berla Certified Vehicle System Technician • Volvo/Mack, HVEDR Technician • Retired Law Enforcement • mike.stogsdill@jsheld.com

March 23-25, 2026

Senior Accident Reconstructionist

Slide 494

March 23-26, 2026

CAN (Controller Area Network) Additional vehicle network types: FlexRay, Ethernet, Local Interconnect Network, Ethernet AVB, Ethernet TSN

March 23-25, 2026

Slide 495

Time Zero – 49 CFR §563 Definition Time zero means whichever of the following occurs first: (1) For systems with “wake-up” air bag control systems, the time at which the occupant restraint control algorithm is activated; or (2) For continuously running algorithms, (i) The first point in the interval where a longitudinal cumulative delta-V of over 0.8 km/h (0.5 mph) is reached within a 20 ms time period; or (ii) For vehicles that record “delta-V, lateral,” the first point in the interval where a lateral cumulative delta-V of over 0.8 km/h (0.5 mph) is reached within a 5 ms time period; or (3) Deployment of a non-reversible deployable restraint. March 23-25, 2026

Slide 496

49 CFR §563.7 – Data Elements

1Pre-crash data and crash data are asynchronous data.

• Table I – Data Elements Required for All Vehicles Equipped with an EDR • Delta-V, longitudinal • Speed, vehicle indicated • Engine throttle, % full • Ignition cycle, crash • Ignition cycle, download • Safety belt status, driver • Frontal air bag deployment, time to deploy… driver • Frontal airbag deployment, time to deploy… front passenger • Multi-event, number event • Time from event 1 to 2 • Complete file recorded (yes, no) March 23-25, 2026

Slide 497

Sample Rates: How “stale” is this data? Snapshot of data at a specific point on the bus:

• 0 s (logger) • 0.05 s • 0.005 s • 0.005 s • 0.015 s • 0.005 s

Slide Courtesy of Jim Lau and Racelogic March 23-25, 2026

Zoomed to show 0.1 second of data Slide 498

Pre-crash data examples

March 23-25, 2026

Slide 499

March 23-26, 2026

Bosch Crash Data Retrieval System Pre-Crash and Crash Data

March 23-25, 2026

Slide 500

GM “last sample” timing • GM systems that report Pre-Crash data captured at 1s intervals report the last sample as “-1s” and we find in the Data Limitations:

• “…The 1.0 second Pre-crash data value (most recent recorded data point) is the data • point last sampled before AE. That is to say, the last data point may have been captured just before AE but no more than 1.0 second before AE. All subsequent Precrash data values are referenced from this data point. …” - 01029_SDMGT-2001 (emphasis added)

March 23-25, 2026

Slide 501

GM “last sample” timing • Where Pre-Crash data is captured at 0.5s intervals:

• “… Pre-Crash data is recorded asynchronously. The 0.5 second Pre-crash data value (most recent recorded data point) is the data point last sampled before Time Zero. That is to say, the last data point may have been captured just before Time Zero but no more than 0.5 second before Time Zero. All subsequent Pre-crash data values are referenced from this data point.…” - 01050_SDM30-delphi (emphasis added)

March 23-25, 2026

Slide 502

GM “last sample” timing • We know the time range for the last sample before T0 but not the specific time

1.0sec

“… All subsequent Precrash data values are referenced from this data point. ....”

1.0sec

0.5sec

“… no more than 1.0 second before AE. …”

AE/Algorithm Enable ≡ “Time Zero” March 23-25, 2026

0.5sec

“… no more than 0.5 seconds before Time Zero. …”

Slide 503

Pre-crash data timing Pre-Crash data as it would be recorded in the ACM then retrieved

$020

$010

1.0 sec Pre-Crash data as it would be re-ordered by the CDR software during the translation relative to the pointer

$040

$050

$030

1.0 sec

$040

$050

Pointer/flag

$010

$020

$030 “Time Zero”

1.0 sec

Pointer/flag March 23-25, 2026

Slide 504

Pre-crash data timing Pre-Crash data as it would be re-ordered by the CDR software during the translation relative to the pointer

$050

$040

$010

$020

$030 “Time Zero”

0.5 sec

Pointer/flag

March 23-25, 2026

Slide 505

Pre-Crash data from most other OEMs • Most other OEMs Pre-Crash data timing is comparable to the “-0.5 to -5.0s” GM type system(s) except for the time series numbering • Most of the other OEMs identify the last sample before T0 as “0.0 (sec)” because:

- 49CFR563 - Event Data Recorders

• BUT there are exceptions including a newer GM system and most don’t identify the time between the last sample an T0, however, some do… March 23-25, 2026

Slide 506

(some) German OEMs “last sample timing” detail • “… Pre-Crash Data:

• - Pre-Crash Data is recorded at 2 samples per second starting 5 seconds before t0. … • - Recorded Pre-Crash Data have a time resolution of 500ms. This can cause a possible delay of the collected data up to 500ms. …” - 0803_BMW_ACSM4i

• “…The data element "Time from Last Speed Data Sample (Precrash) to Time Zero“ indicates the time delay between the most recent pre-crash data sample and Time - 13001_VWG1000CO Zero (0 to 500ms). …” • “…The data element "Time from Last Speed Data Sample (Precrash) to Time Zero“ indicates the time delay between the most recent pre-crash data sample and Time Zero (0 to 500ms). The reported time in this element has to be subtrated from - (sic) 14002_VWG2100CO (emphasis added) 500ms in order to obtain the correct time. …”

March 23-25, 2026

Slide 507

BMW last sample before T0 timing example • Time from last sample is given as 19 ms • The Pre-Crash data marked as “0.0(sec)” was captured 19 ms before T0

• The Pre-Crash data marked as “-0.5 (sec)” is 500 ms older than the “0.0” data making it 519ms old when T0 is set • Older data frames are 500ms older than the one at “-0.5 (sec)”

March 23-25, 2026

Slide 508

Last sample before T0 timing example • Time from last sample is given as 277ms -5.277 -4.777 -4.277 -3.777 -3.277 -2.777 -2.277 -1.777 -1.277 -0.777 -0.277

• The Pre-Crash data marked as “0.0(sec)” was captured 227ms before T0

• The Pre-Crash data marked as “-0.5 (sec)” is 500 ms older than the “0.0” data making it 777ms old when T0 is set • Older data frames are 500ms older than the one at “-0.5 (sec)”

March 23-25, 2026

Slide 509

(some) German OEMs “last sample timing” detail

March 23-25, 2026

Slide 510

Variants for Toyota Pre-Crash data capture • “Pre-563” Toyota systems (00EDR / 02EDR / 04EDR / 06EDR / 10EDR)

• 5 samples of Pre-Crash data captured every 1 sec • The last sample before TRG/T0 is reported with a “Time from Pre-Crash to TRG“ element indicating how long it had been in EDR memory pre-TRG (T0) with 100 – 102.4 ms resolution • A separate Pre-Crash snapshot captured within the last 100 ms of T0 and marked as “0 TRG” in the Pre-Crash data table

March 23-25, 2026

Slide 511

“Pre-563” (00EDR / 02EDR / 04EDR / 06EDR / 10EDR) “… Resolution of the last sample identified with the "Time from Pre-Crash to TRG" is 100[ms] or 102.4[ms] for ECUs with 1.024 data sampling intervals, and the value is rounded down and recorded. …” -05002_ToyotaTRW

4 samples captured every 1s referenced to the “last sample” before TRG

Here -0.8(sec) identifies a sample that has been in memory for between 800 and 900ms at TRG (T0). The displayed -0.8s time “… is rounded down and recorded…”

March 23-25, 2026

Slide 512

A separate snapshot captured within the last 100ms of TRG/T0

Variants for Toyota Pre-Crash data reporting • “563 compliant” (12EDR / 13EDR / 15EDR / 17EDR / 19EDR / 21EDR / 22EDR / 23EDR / 24EDR) • 10 samples of Pre-Crash data captured every 0.5 sec

• “… Resolution of the "Time from Pre-Crash to TRG" is 50 [ms], and the value is rounded up and recorded. … A separate Pre-Crash snapshot captured within the last 50 ms of T0 and marked as “0 TRG” in the Pre-Crash data table. …” -05013_ToyotaS00std

March 23-25, 2026

Slide 513

“563 compliant” (12EDR and newer systems) “… Resolution of the "Time from Pre-Crash to TRG" is 50 [ms], and the value is rounded up and recorded. …” 05013_ToyotaS00std

10 samples captured every 500ms referenced to the “last sample” before TRG

Here -0.15(sec) identifies a sample that has been in memory for between 100 and 150ms at TRG (T0). The displayed -0.15s time “… is rounded up and recorded…”

March 23-25, 2026

Slide 514

“… A separate Pre-Crash snapshot captured within the last 50ms of T0 and marked as “0 TRG” in the Pre-Crash data table. …”

Variants for Toyota Pre-Crash data reporting “Time from Pre-Crash to TRG” Less than 1000ms, here btn 800-900ms

1.0sec

“Time from PreCrash to TRG”

Less than 500ms, here btn 200-250ms Less than 50ms

0.5sec March 23-25, 2026

Slide 515

TRG / T0

Less than 100ms

GM “last sample” timing (SDM50) • “…Pre-Crash data samples are captured prior to Time Zero … at 500 millisecond intervals with an additional sample captured at Time Zero (referred as 0.0 second sample). … • … The -0.5 second Pre-Crash sample (most recent recorded data point) is sampled within 500 milliseconds prior to Time Zero. All other Pre-Crash samples are referenced from this data point. … • … Additionally, the data point sampled at 0.0 second is captured within 100 milliseconds prior to Time Zero. …” March 23-25, 2026

- 01065_SDM50-veoneer (emphasis added)

Slide 516

GM “last sample” timing (SDM50) • “…Pre-Crash data samples are captured prior to Time Zero … at 500 millisecond intervals with an additional sample captured at Time Zero (referred as 0.0 second sample). … • … The -0.5 second Pre-Crash sample (most recent recorded data point) is sampled within 500 milliseconds prior to Time Zero. All other PreCrash samples are referenced from this data point. … • … Additionally, the data point sampled at 0.0 second is captured within 100 milliseconds prior to Time Zero. …”

0.5sec

“Time Zero” - 01065_SDM50-veoneer (emphasis added)

March 23-25, 2026

Slide 517

The Honda “0.0” sample • “… Pre-crash data is recorded at 2 samples per second within the 5 seconds before T0. The sampling point at 0.0 is taken at T0 and is asynchronous with the other sample points. Time between -0.5 and Time zero is given and is between 1 and 500ms. …” - (emphasis added) • Found in the Data Limitations for Honda systems identified by the codes • 04001_HondaSRS_GEN1 • 04003_HondaSRS_GEN3

04002_HondaSRS_GEN2 04004_HondaSRS_GEN4

• The time “is given?”

• There is no element like that seen in the German cars for the specific time from the last sample to T0 March 23-25, 2026

Slide 518

The Honda “0.0” sample • “… The sampling point at 0.0 is taken at T0 and is asynchronous with the other sample points. Time between -0.5 and Time zero is given and is - (emphasis added) between 1 and 500ms. …” • How does that align with the notation on the Pre-Crash data table?

March 23-25, 2026

Slide 519

The Honda “0.0” sample • “… The sampling point at 0.0 is taken at T0 and is asynchronous with the other sample points. Time between -0.5 and Time zero is given and is between 1 and 500ms. …”

- (emphasis added)

• How can a sample be taken “at” T0?

• Wouldn’t the module (a) have to know when T0 was going to occur ahead of time and (b) which conditions would be met in that crash at T0 to be able to capture that snapshot of data at T0?

• So, in reality, wouldn’t there necessarily be a programming delay that reads something like… 1. 2. 3.

detect crash begin algorithm to protect the occupants (“Time Zero”) capture one more frame of external data (and we’ll call it the 0.0 sample) • But the capture is really after T0 at that point

March 23-25, 2026

Slide 520

Honda “Pre-Crash” timing • If the “-0.5s” sample was taken closer to 500ms before T0 • Then the ACM set T0 after a relative longer time (i.e.: an underride) • Then another capture of “Pre-Crash” data was taken after T0 • For a time & distance analysis, can we use the 0.0 data set as “Pre-Crash”?

March 23-25, 2026

Slide 521

Honda “Pre-Crash” timing • Even if the “0.0” sample is captured before T0 (using the GM SDM50 or Toyota systems for comparison) wouldn’t that “0.0” sample be within the period between the “-0.5s” sample and T0?

• So, would we use it “again” in, for example, a pre-crash time and distance analysis?

March 23-25, 2026

Slide 522

Pre-Crash data as it would be re-ordered by the CDR software during the translation relative to the pointer

$050

$040

0.5 sec

$010

$020

0.5 sec

“Time Zero”

Pre-crash data timing $030

0.5 sec

<0.5 sec

Pointer/flag

March 23-25, 2026

Slide 523

$07F

~0.1 sec

March 23-26, 2026

Toyota Global TechStream (GTS)+

March 23-25, 2026

Slide 524

Abbreviation Table – VCH/FFD Data Report

March 23-25, 2026

Slide 525

Pre-Collision Safety (PCS) Data

March 23-25, 2026

Slide 526

Vehicle Control History (VCH)

March 23-25, 2026

Slide 527

Vehicle Control History (VCH) Trigger Point

Time Stamp

Vehicle Accelerato Engine Speed r Opening RPM Data [km/h] Ratio [%] [rpm]

Sensor Type Identification (G Sensor)

READY Signal

Cruise Control

Yaw G Sensor Installation Information

Sensor Type Identification (Yaw Rate Sensor)

Gear Position Signal

Turbine RPM/Input Shaft RPM [rpm]

Yaw Rate Shift Brake Oil Sensor Position Pressure Signal Signal Brake SW [MPa] [deg/s]

Under VSC Control

March 23-25, 2026

Shift Gear

Under ABS Control

Longitudin al G Lateral G Sensor Sensor Throttle Signal Signal Opening [m/s^2] [m/s^2] Ratio [%]

Power Train Mode

Under VDM Control

SNOW Mode

Sensor Type Steering HV Identificati Signal Recognitio on Sensor Type Identification (G [deg] n Flag Diesel Flag (Security) Sensor Layout)

Valid/Invali d of Driving VSC OFF Mode Lamp

Under TRC FR Wheel Operation Flag Speed [km/h]

Valid/Invali d of Valid/Invali Drive Mode TRC OFF TRC/VSC Select d of EV Lamp Signal OFF Lamp EV Mode Mode

FL Wheel Speed [km/h]

RR Wheel Speed [km/h]

Slide 528

RL Wheel Speed [km/h]

EPS Torque Sensor Value [Nm]

Trigger List

March 23-25, 2026

Slide 529

Vehicle Control History (VCH)

March 23-25, 2026

Slide 530

Vehicle Control History (VCH)

March 23-25, 2026

Slide 531

Vehicle Control History (VCH)

March 23-25, 2026

Slide 532

Images FFD

March 23-25, 2026

Slide 533

Image FFD

March 23-25, 2026

Slide 534

March 23-26, 2026

Infotainment Systems

March 23-25, 2026

Slide 535

Pre-Crash Data

March 23-25, 2026

Slide 536

Log file/CAN data prior to crash

March 23-25, 2026

Slide 537

Log file/CAN data prior to crash

March 23-25, 2026

Slide 538

Ford Sync Gen 3 Log Files

March 23-25, 2026

Slide 539

Berla iVE Software

March 23-25, 2026

Slide 540

bullseyeholsters.com

March 23-25, 2026

Slide 541

850+ vehicles

Passenger • Trucks • Trailers • Motorcycles Downloadable in seconds

March 23-25, 2026

Slide 542

An Attorney’s Guide to Reports and Testimony – Avoid Getting Struck Jerome R. Kelly, Esq. MARTINEZ & DIETERECH LEGAL GROUP

March 23-25, 2026

Slide 543

Jerome R. Kelly, Esq. Resume: • Has tried over 100 cases to a jury in Texas • Current Senior Attorney for MD Legal Group, Staff Counsel for Loya Insurance Group. • Currently manages 10 trial attorneys in the Houston office • Has worked as an insurance defense civil trial attorneys for 14 years

March 23-25, 2026

Contact information:

Slide 544

March 23-26, 2026

Texas Expert Witness Rules: What do experts need to know? An Attorney’s Guide to Reports and Testimony

March 23-25, 2026

Slide 545

Expert Designation Requirements: • Under Texas Rule of Civil Procedure 194.3, a party must formally designate their expert witness in response to a proper discovery request. • Failure to TIMELY and PROPERLY designate an expert may result in exclusion under TRCP Rule 193.6, unless the party demonstrates good cause or failure does not unfairly surprise or prejudice the other side

March 23-25, 2026

Slide 546

Expert Designation Requirements Cont’d: • Rule 195.2 Schedule for Designation Experts: Unless otherwise ordered by the court, a party must designate experts – that is, furnish information described in Rule 195.5(a) – by the following dates: • (1) with regard to all experts testifying for a party seeking affirmative relief, 90 days before the end of the discovery period; • (2) with regard to all other experts, 60 days before the end of the discovery period.

March 23-25, 2026

Slide 547

Expert Designation Requirements Cont’d: • Rule 195.5 Expert Disclosures and Reports: • Disclosures. Without awaiting a discovery request, a party must provide the following for any testifying expert:(1) the expert’s name, address, and telephone number; • (2) the subject matter on which the expert will testify; • (3) the general substance of the expert’s mental impressions and opinions and a brief summary of the basis for them, or if the expert is not retained by, employed by, or otherwise subject to the control of the responding party, documents reflecting such information; • (4) if the expert is retained by, employed by, or otherwise subject to the control of the responding party:

• (A) all documents, tangible things, reports, models, or data compilations that have been provided to, reviewed by, or prepared by or for the expert in anticipation of the expert’s testimony; • (B) the expert’s current resume and bibliography; • (C) the expert’s qualifications, including a list of all publications authored in the previous 10 years; • (D) except when the expert is the responding party’s attorney and is testifying to attorney fees, a list of all other cases in which, during the previous four years, the expert testified as an expert at trial or by deposition; and • (E) a statement of the compensation to be paid for the expert’s study and testimony in the case.

March 23-25, 2026

Slide 548

Expert Reports: 195.5 – Court-Ordered Reports • If the discoverable factual observations, tests, supporting data, calculations, photographs, or opinions of an expert have NOT been recorded and reduced to tangible form, the court may order these matters reduced to tangible form and produced in addition to the deposition.

March 23-25, 2026

Slide 549

Expert Reports: 195.7 – Cost of Expert Witnesses

• When a party takes the oral deposition of an expert witness retained by the opposing party, all reasonable fees charged by the expert for time spent in preparing for, giving, reviewing, and correcting the deposition MUST be paid by the party that RETAINED the expert. • In Texas and some other states

March 23-25, 2026

Slide 550

Exclusion Rule: 193.6 – Failing to Timely Respond • Exclusion of evidence and exceptions. A party who fails to make, amend, or supplement a discovery response in a timely manner may not introduce in evidence the material or information that was not timely disclosed, or offer the testimony of a witness (other than a named party) who was not timely identified, unless the court finds that: (1) there was good cause for the failure to timely make, amend, or supplement the discovery response; or (2) the failure to timely make, amend, or supplement the discovery response will not unfairly surprise or unfairly prejudice the other parties.

March 23-25, 2026

Slide 551

March 23-26, 2026

Part I: Tips for surviving the Expert Designation as a Testifying Expert An Attorney’s Guide to Reports and Testimony

March 23-25, 2026

Slide 552

Expert Designation Tips • Communication is key! Do you need the report to be expedited? • Ask for the Expert Designation Deadline in addition to your internal deadline • Keep an updated list of the following for EACH case:

• (C) the expert’s qualifications, including a list of all publications authored in the previous 10 years; • (D) except when the expert is the responding party’s attorney and is testifying to attorney fees, a list of all other cases in which, during the previous four years, the expert testified as an expert at trial or by deposition; and • (E) a statement of the compensation to be paid for the expert’s study and testimony in the case.

March 23-25, 2026

Slide 553

Expert Designation Tips Cont’d • Work with attorney to provide the following: • The subject matter on which the expert will testify; • The general substance of the expert’s mental impressions and opinions and a brief summary of the basis for them, or if the expert is not retained by, employed by, or otherwise subject to the control of the responding party, documents reflecting such information;

March 23-25, 2026

Slide 554

March 23-26, 2026

Part II: Tips for surviving the Motion to Strike Defendant’s Expert An Attorney’s Guide to Reports and Testimony

March 23-25, 2026

Slide 555

Plaintiff’s Motion to Strike Defendant’s Expert Witness • Make sure that you know the deadline for Plaintiff’s Motion to Strike an expert witness • Make sure that the handling attorney or their team informs you that Plaintiff has filed a Motion to Strike, challenging your expert testimony • Inquire about the Defendant’s Response to Plaintiff’s Motion to Strike and the deadline for the response

March 23-25, 2026

Slide 556

Sample Docket Control Order:

March 23-25, 2026

Slide 557

When is a Motion to Strike Expert Likely? • Within the timeframe of the Docket Control Order (within the discovery period of the case) • Immediately following the deposition of the expert witness • Make sure that the hiring attorney adequately prepares you for the expert deposition.

March 23-25, 2026

Slide 558

Preparing an expert witness for trial: • Review initial expert designation • Review all material in the expert’s file. The Expert’s file is discoverable • Lock Down Opinions: The expert must stay in their field of expertise • Be prepared to defend your METHODOLOGY • You must be prepared for a Daubert Challenge

March 23-25, 2026

Slide 559

Sample Response to Plaintiff’s Motion to Strike Expert Witness:

March 23-25, 2026

Slide 560

March 23-26, 2026

Part III: Tips for Surviving the Daubert Challenge at trial An Attorney’s Guide to Reports and Testimony

March 23-25, 2026

Slide 561

What is a Daubert Challenge? • A Daubert challenge is a legal motion or objection raised in court to exclude the testimony of an expert witness on the grounds that it is not reliable or relevant. The challenge requires the party presenting the expert to prove that the expert's methodology and opinions are scientifically sound and applicable to the specific case under the standards set by the U.S. Supreme Court in Daubert v. Merrell Dow Pharmaceuticals, Inc.

March 23-25, 2026

Slide 562

Texas Rules of Evidence 702 • Rule 702. Testimony by Expert Witnesses • A witness who is qualified as an expert by knowledge, skill, experience, training, or education may testify in the form of an opinion or otherwise if the expert’s scientific, technical, or other specialized knowledge will help the trier of fact to understand the evidence or to determine a fact in issue.

March 23-25, 2026

Slide 563

Daubert Factors: • Testing: Whether the expert's theory or technique can be, and has been, tested. • Peer Review and Publication: Whether the theory or technique has been subjected to peer review and publication. • Known or Potential Rate of Error: The existence of a known or potential rate of error for the methodology. • Standards and Controls: The existence and maintenance of standards and controls governing the technique's operation. • General Acceptance: Whether the theory or methodology is generally accepted within the relevant scientific or professional community. March 23-25, 2026

Slide 564

Defending the Daubert Challenge: • To survive a Daubert challenge, an expert witness must demonstrate that their testimony is both reliable and relevant to the facts of the case, using the same intellectual rigor as in their professional field. • Expect questions from Opposing Counsel, Hiring attorney and possibly the judge.

March 23-25, 2026

Slide 565

Where does EDR data come into play?: • EDR data can strengthen the argument regarding reliability; thus helping the expert survive a Daubert challenge • Ask if either vehicle has EDR Data • Ask to Inspect the vehicles involved in the MVA

• Attorney can seek to compel production of subject vehicles

March 23-25, 2026

Slide 566

PREMIUM SUMMIT SPONSOR

March 23-25, 2026

Slide 567

bullseyeholsters.com

March 23-25, 2026

Slide 568

Preservation & Analysis of Tesla in-car Video Mike Merolli Aperture TRUTH IN FOCUS

March 23-25, 2026

Slide 569

Mike Merolli Aperture Forensic Expert – Accident Reconstruction ACTAR #1518

30 Years of Experience

Tesla – Senior Incident Investigator

MAPFRE Insurance – SIU Crash Reconstructionist

Central Massachusetts Law Enforcement Council Crash Reconstruction Team (508) 498-7733 Mike.merolli@aperturellc.com March 23-25, 2026

Slide 570

570

March 23-26, 2026

Introduction Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 571

Introduction This presentation is designed to review new META data imbedded in Tesla DashCam videos and how to manage the footage •

In November 2025 Tesla began release of Software Version 2025.44.25 for HW 3 & 4; which added Supplemental Enhancement Information (SEI)

• In conjunction, Tesla released an Open-Source Tool that allows the data to be viewed and exported • This presentation will review the process and show an example of the SEI Open-Source Tool as well as a Commercially Available Tools

March 23-25, 2026

Slide 572

March 23-26, 2026

Tesla Dash-Cam Basics Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 573

Tesla DashCam Tool • The Tesla Dashcam tool is an integrated, continuous recording system that utilizes the vehicle's four external cameras (front, rear, and both side pillars/fenders) to capture 360-degree video footage while driving. • It functions by creating a looping, roughly one-hour recording on a, required, user-supplied or factory-installed USB drive, which overwrites the oldest footage unless saved March 23-25, 2026

Slide 574

Dash-Cam Viewer

March 23-25, 2026

Slide 575

575

Dash Cam Clips

March 23-25, 2026

Slide 576

DELETE CLIPS !!!!!

Delete Clips

March 23-25, 2026

Slide 577

Tesla Dash-Cam Basics

March 23-25, 2026

Slide 578

578

March 23-26, 2026

Tesla Flash Drive Folders Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 579

579

Tesla USB Drive • The Tesla USB Drive is a 128 GB, pre-formatted flash drive included with new vehicles, specifically designed to store Sentry Mode and Dashcam video footage. It plugs into a dedicated USB-A port, typically located in the glovebox for security, and ensures continuous recording of driving and parking events.

March 23-25, 2026

Slide 580

580

Important Notes • Folder Setup: The folder MUST be named exactly TeslaCam (case-sensitive) in the root directory of the USB drive. • Format: The USB drive should be formatted as exFAT (recommended) or FAT32. • Viewing: When viewing on a computer, files are organized by date and time in a YYYY-MM-DD-HHMMSS format. • Alternative Folder: In some configurations or newer vehicles, you may see TeslaTrackMode for track-specific driving data.

March 23-25, 2026

Slide 581

581

Required Root Folder Structure • The main Folder MUST be named TeslaCam • There are four required SubFolders & three possible additions • Recent Clips • Saved Clips • Sentry Clips • Encrypted • Possible additions • Photobooth • Lightshow • TeslaTrackMode March 23-25, 2026

Slide 582

582

Recent Clips •Purpose: Stores the most recent, continuous dashcam recordings while driving. • Behavior: It holds up to 60 minutes of footage (usually broken into 1-minute files). • Management: Once the 60-minute limit is reached, the oldest files are overwritten by newer ones automatically. March 23-25, 2026

Slide 583

583

SavedClips • Purpose: Stores videos that you have manually saved by tapping the dashcam icon on the touchscreen, pressing the horn, or using voice commands. • Behavior: Files in this folder are not automatically overwritten. • Content: Contains 10-minute snippets (representing the 10 minutes prior to saving) separated into 1-minute segments for each camera.

March 23-25, 2026

Slide 584

584

SentryClips (Now called EncriptedClips) • Purpose: Stores recordings from Sentry Mode security events (e.g., if someone gets too close, bumps, or breaks into the car). • Behavior: These are automatically saved when an alert or alarm state is triggered. • Management: If the USB drive runs out of space, the oldest clips in this folder are deleted to make room for new ones. March 23-25, 2026

Slide 585

585

Tesla Phone App

March 23-25, 2026

Slide 586

Tesla Phone App

March 23-25, 2026

Slide 587

Tesla Phone App

March 23-25, 2026

Slide 588

Tesla USB Requirements • Format: The drive must be formatted as exFAT, FAT32, or MS-DOS FAT (for Mac) • Location: Plug the drive into a data-capable USB port, usually located in the glovebox. • Setup: You can create the folder manually or use the car to format it by going to Controls > Safety > Format USB Drive. • Capacity: A minimum of 64 GB is recommended for consistent recording • The “Factory” USB has a 128 GB Capacity

March 23-25, 2026

Slide 589

589

Tesla USB Requirements (Cont’d) • Port Selection: Use the glovebox USB port for data-heavy features like Dashcam and Sentry Mode, as many newer Teslas (post-late 2021) only support charging on center console ports. • Automatic Setup: You can let the car handle formatting by navigating to Controls > Safety > Format USB Drive, which automatically creates the TeslaCam folder.

March 23-25, 2026

Slide 590

590

March 23-26, 2026

Supplemental Enhancement Information (SEI) Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 591

591

What Data Is Included

• Tesla's SEI metadata typically includes information such as • Timestamp data – Precise date/time for each frame • GPS coordinates (latitude/longitude) • Vehicle state information (gear, turn signals, braking, etc.) • Camera identifier (front, rear, left repeater, right repeater) • Compass Heading/ Direction of Travel March 23-25, 2026

Slide 592

592

How it Works

• Accepts a Tesla dashcam video file — usually .mp4 files from the USB drive or SSD used for TeslaCam •Parses the H.264/H.265 NAL units — specifically extracting SEI payloads •Displays the embedded metadata in a humanreadable format (CSV), allowing users to explore frame-by-frame information March 23-25, 2026

Slide 593

593

Why Network Abstraction Layer (NAL) Units Exist

• Raw video is enormous. A single uncompressed 1080p frame at 30 frames per second (fps) generates ~1.5 Gbps of data. Compression solves this, but the compressed data needs to be: • Organized into logical pieces • Transportable across different networks and storage media • Self-describing so decoders know what each piece contains • Network Abstract Layer (NAL) units provide this structure. March 23-25, 2026

Slide 594

594

H.264/H.265 NAL Units Explained • The Basics •NAL stands for Network Abstraction Layer. NAL units are the fundamental building blocks/packet structure that make up an H.264 (AVC) or H.265 (HEVC) video stream. •Think of them as individually packaged chunks of data that together form a complete video. March 23-25, 2026

Slide 595

595

H.264/H.265 Standard •H.264 (AVC) and H.265 (HEVC) are dominant video compression standards that reduce file sizes while maintaining quality, with H.265 offering roughly 50% better compression than H.264. H.264 is the widely compatible industry standard for streaming and web, while H.265 is superior for 4K/8K, surveillance, and storage efficiency. March 23-25, 2026

Slide 596

Relevance to Tesla Dashcam SEI Explorer

•The SEI Explorer specifically: •Reads the Tesla dashcam .mp4 file •Parses through the NAL units in the video stream •Filters for NAL units of type SEI •Decodes Tesla's custom SEI payloads containing vehicle data, Frame by Frame March 23-25, 2026

Slide 597

597

March 23-26, 2026

Using the SEI Viewer Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 598

598

Tesla Dashcam Tools • https://teslamotors.github.io/dashcam/index.html • For viewing and extracting metadata from supported Tesla Dashcam videos

• SEI Explorer — view dashcam footage with SEI metadata displayed alongside video playback. • Python CLI — Python-based metadata extractor for extracting SEI data from MP4 files. • Protobuf schema — the specifications and documentation for Google's Protocol Buffers (Protobuf), a mechanism for serializing structured data used to decode SEI data in the MP4 file(s). • Not all Tesla-generated dashcam clips contain SEI data. Only clips recorded on Tesla firmware 2025.44.25 or later and HW3 or above contain SEI data. If car is parked, SEI data may not be present. March 23-25, 2026

Slide 599

Tesla Dashcam SEI Explorer

March 23-25, 2026

Slide 600

Tesla Dashcam SEI Explorer

• https://teslamotors.github.io/dashcam/sei_explorer.html

March 23-25, 2026

Slide 601

601

Exporting the META Data

Export Data

March 23-25, 2026

Slide 602

602

CSV of the META Data

March 23-25, 2026

Slide 603

603

Exported META Data / CAN Signal Breakdown • Software version • gear_state • accelerator_pedal_position • steering_wheel_angle • blinker_on_left • blinker_on_right • brake_applied

March 23-25, 2026

• autopilot_state • longitude_deg • latitude_deg • heading_deg • linear_acceleration_mps2_y • linear_acceleration_mps2_y • linear_acceleration_mps2_z

Slide 604

604

Defintions • Version = SEI Player Version • gear_state = Park/Reverse/Neutral/Drive • accelerator_pedal_position = Driver application %; NOTE Pedal Position always = 0 when Autopilot State = Self_Driving • steering_wheel_angle = Degrees ( Clockwise = +) • blinker_on_left = True/False ; True means activated • blinker_on_right = True/False ; True Means Activated • brake_applied = True/False ; True means Driver Applied; NOTE Brake Applied = False when Autopilot State = Self_Driving March 23-25, 2026

Slide 605

605

Definitions (Continued) • Autopilot State = SELF_DRIVING when active; = None when Not Active • Longitude_deg – East/West position from the Prime Meridian in Degrees • Latitude_deg – North/South position from the Equator in Degrees • Heading_deg – Horizontal direction of Tesla longitudinal axis with negative degrees = west; positive degrees = east; due north = 0 degrees • Linear_acceleration_mps2_x – Rate/change in longitudinal direction with negative polarity = acceleration; positive = deceleration (Regenerative braking) • Linear_acceleration_mps2_y – Rate/change in lateral direction with right turn showing positive polarity and left turn showing negative polarity • Linear_acceleration_mps2_z – Rate/change in normal/vertical direction with negative grade = positive acceleration; positive grade = negative; i.e gravity

March 23-25, 2026

Slide 606

606

March 23-26, 2026

Telemetry Overlay Viewer Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 607

607

What is Telemetry Overlay Viewer? •Telemetry Overlay is a user-friendly software for Windows, macOS, and Linux that creates, customizes, and adds gauge overlays (speed, maps, altitude, G-force) to action camera and drone footage. It supports devices from GoPro, DJI, Insta360, and Garmin, allowing users to drag and drop videos to visualize embedded sensor data. March 23-25, 2026

Slide 608

March 23-26, 2026

TesClip Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 609

609

TesClip

March 23-25, 2026

Slide 610

March 23-26, 2026

SEI TELEMETRY TOOL Preservation & Analysis of Tesla in-car Video

March 23-25, 2026

Slide 611

611

SEI TELEMETRYTool

March 23-25, 2026

Slide 612

Exporting the META Data

Export Data

March 23-25, 2026

Slide 613

613

Export CSV

March 23-25, 2026

Slide 614

614

SEI Telemetry Viewer

March 23-25, 2026

Slide 615

PREMIUM SUMMIT SPONSOR

March 23-25, 2026

Slide 616

EDR Testing of non-Bosch CDR Tool Supported Automobiles Robert D. Anderson, M.S. Biomechanics Analysis, LLC

March 23-25, 2026

Slide 617

Robert D. Anderson (Bob) • Biomechanical Engineer/Biomechanics Analysis collision reconstruction and injury mechanics • ARC-CSI crash instrumentation 2006 - 2017 • SATAI’s crash program since 2007 • 100’s of crash demonstrations • Dozens of crash related publications • Crash Team Boot Camp Instructor March 23-25, 2026

Slide 618

March 23-26, 2026

Jaguar & Land Rover Crash Tests EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 619

SATAI 2026 Two crash test vehicles • 2018 Land Rover Range Rover Evoque • 2018 Jaguar XE 2.5T

March 23-25, 2026

Slide 620

SATAI 2026 2018 Jaguar XE 2.5T 3 front-to-barrier 4 rear-to-barrier 1 front-to-barrier Total 8 low-speed tests

March 23-25, 2026

Slide 621

SATAI 2026 2018 Land Rover Range Rover Evoque 1 front-to-barrier 2 rear-to-barrier 1 front-to-barrier Total 4 low-speed tests

March 23-25, 2026

Slide 622

Annual Sales in the United States • ~ 3k – Jaguar • ~ 20k – Land Rover • ~ 980k – Hyundai • ~1.8M - GM

March 23-25, 2026

Slide 623

Title 49 CFR Part 563 Event Data Recorders

March 23-25, 2026

Slide 624

Title 49 CFR Part 563 Event Data Recorders

March 23-25, 2026

Slide 625

March 23-26, 2026

Outline EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 626

Outline • Obtaining EDR data from Jaguar/Land Rover (JLR) vehicles • Crash Scan – how it works • EDR Test Results • Case Examples

March 23-25, 2026

Slide 627

March 23-26, 2026

Obtaining EDR data from JLR EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 628

March 23-25, 2026

Slide 629

March 23-25, 2026

Slide 630

March 23-25, 2026

Slide 631

March 23-25, 2026

Slide 632

March 23-25, 2026

Slide 633

• Prove you are not a robot • VIN • Search for Event Data Recorder

https://www.ownerinfo.jaguar.com/document/4N/2018/1667898/proc/G1 815999/G1993797?vin=SAJAR4FX6JCP27649 March 23-25, 2026

Slide 634

March 23-25, 2026

Slide 635

March 23-25, 2026

Slide 636

March 23-25, 2026

Slide 637

Obtaining Jaguar – Land Rover (JLR) EDR data • Bob’s experience – not yet successful

March 23-25, 2026

Slide 638

Obtaining EDR data from JLR – my adventure • Step 1 contact Veoneer with VIN requesting instructions on obtaining EDR translation • Step 2 send photograph of the ACM to Veoneer • Step 3 provide proof of ownership, such as vehicle title or court order/search warrant

March 23-25, 2026

Slide 639

Obtaining EDR data from JLR – my adventure • Step 4 complete and return Authorization/Privacy Notice form • Step 5 return signed quotation • Step 6 send $2000 US

March 23-25, 2026

Slide 640

Obtaining EDR data from JLR – my adventure • Step 7 ship ACM to Veoneer in France • Step 8 receive EDR data • Step 9 get ACM returned

March 23-25, 2026

Slide 641

Timeline for Obtaining EDR data from JLR • SATAI crash conference concluded - February 28, 2026

• Step 1 contact Veoneer with VIN requesting instructions on obtaining EDR translation – March 4

• Step 2 send photograph of the ACM to Veoneer – March 6

• Step 3 provide proof of ownership, such as vehicle title or court order/search warrant – March 8

March 23-25, 2026

Slide 642

Timeline for Obtaining EDR data from JLR • Step 4 complete and return Authorization and provide “Invoicing Address” - March 10

• Step 5 return signed quotation – March 11

(currently waiting for quotation)

March 23-25, 2026

Slide 643

EDR data from JLR Has JLR provided a commercially available tool for obtaining EDR? • Low speed cases where vehicles are still in service? • Crashes where the JLR vehicle is not the client vehicle? • How do we do we test JLR EDR, like we have for vehicles from other brands?

March 23-25, 2026

Slide 644

March 23-26, 2026

Disclaimer EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 645

Disclaimer: Bob Anderson, Biomechanics Analysis, LLC (BA), and Southwestern Association of Technical Accident Investigators (SATAI) are not affiliated with Collision Sciences/Crash Scan (CS). This presentation does not address issues of Bosch EULA violations by CS, or attempt to address how CS obtained its translations.

March 23-25, 2026

Slide 646

Disclaimer: Collision Sciences donated to SATAI. That donation was used to purchase test vehicles. CS RD reports were provided for free. The research, this presentation, etc. does not address, nor does it endorse or encourage, the use of CS for Bosch supported vehicles.

March 23-25, 2026

Slide 647

March 23-26, 2026

Crash Scan – how it works EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 648

Crash Scan Vehicle Interface

March 23-25, 2026

Slide 649

Recommended Accessory

March 23-25, 2026

Slide 650

Crash Scan Program • Play Store or Apple App Store

• Then go through sign-up process

March 23-25, 2026

Slide 651

Crash Scan – Connect to Vehicle

March 23-25, 2026

Slide 652

March 23-25, 2026

Slide 653

March 23-25, 2026

Slide 654

March 23-25, 2026

Slide 655

March 23-25, 2026

Slide 656

Collision Sciences – Crash Scan • Claims (CL) – Primary Product and is the default

• Generic injury risk for both subject vehicle and presumed collision partner • Issues with Collision Sciences Claims Report Previously Addressed • Don Phillips - CSI EDR Summit 2025 “Analysis of the application of "non-standard" (hacked) data retrieval tools” • Not supported by any OEM • Missing data compared to standard EDR • No versioning of translation • Opening for possible ethical based attacks • Risk exclusion of reversed engineered data undermines manufacturer supported EDR data

March 23-25, 2026

Slide 657

Collision Sciences – Crash Scan • Claims (CL) – Primary Product and is the default

• Generic injury risk for both subject vehicle and presumed collision partner • Issues with Collision Sciences Claims Report Previously Addressed • Billy S. Cox, Jr. - NAPARS Symposium on EDR 2025 “Compare and Contrast Bosch and Hyundai/Kia EDR Data vs. Collision Sciences CrashScan Data” • No data limitations • No other modules, e.g., GM FCM/ASCM/OCS or Toyota VCH/PCS • Some driver input events labeled as “crash” events with an assigned injury probability • Caution adopting injury risk and thresholds

March 23-25, 2026

Slide 658

Collision Sciences – Crash Scan Other CS report

• Raw Data (RD)

• Must be requested • More crash information than CL • Only event related information without any injury risk or threshold language • Similar to standard EDR report, but • No data limitations • No polarity specifications table • No description of EDR behavior

March 23-25, 2026

Slide 659

Collision Sciences – Crash Scan Disclaimer Please note that EDR reports for Jaguar-Land Rover vehicles are prepared using a combination of known data decoding algorithms and expertise. While CrashScan possesses some specifications from Jaguar-Land Rover, we may not possess the official OEM specifications for this particular vehicle model. The data presented in reports is based on our best efforts and current knowledge. By purchasing a Jaguar-Land Rover EDR report, you accept this disclaimer. We strongly recommend that you corroborate this report with other available case information, such as police reports, statements, as well as scene, vehicle data and photographs, accident reconstruction calculations and vehicle simulation software, to corroborate the accuracy and reasonableness of the information. Please contact us at support@collisionsciences.ca with any questions. The Preview Report provided by Collision Sciences is intended solely as an initial summary and should not be used as the basis for concluding the assessment of a vehicle or any related findings. This preview offers a snapshot of the available data and is not an exhaustive analysis. For a comprehensive understanding of the crash data and contextual information, it is imperative to consult the complete, paid report. Users who rely solely on the Preview Report do so at their own risk. Collision Sciences assumes no responsibility for any decisions made or actions taken based solely on the information contained within the Preview Report. We strongly recommend reviewing the full report for accurate, detailed, and actionable insights

March 23-25, 2026

Slide 660

March 23-26, 2026

EDR Testing EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 661

What would we like to know about EDR data? • Record threshold • Types of pre-crash data • Types of crash data • Polarity • Resolution • Sample rate • Number of events • Over-writing • Etc.

March 23-25, 2026

Slide 662

Crash Program 2018 Land Rover Evoque

March 23-25, 2026

2018 Jaguar XE 2.5T

Slide 663

2018 Range Rover Evoque Baseline download – no events Test D • 5 mph front-to-barrier • -5.9 mph Delta V • Event 1 recorded Test D

March 23-25, 2026

Slide 664

2018 Range Rover Evoque Test J • 3ish mph rear-to-barrier • +4 mph Delta V • No new event recorded, Event 1 is Test D

March 23-25, 2026

Slide 665

2018 Range Rover Evoque Test K • 4.8 mph rear-to-barrier • +5.6 mph Delta V* • No new event recorded, Event 1 is Test D

• *from Slamstick

March 23-25, 2026

Slide 666

2018 Range Rover Evoque Test L • 5 mph front-to-barrier • -6 mph Delta V • Event 2 is Test L, Event 1 is Test D

March 23-25, 2026

Slide 667

Range Rover Test D Pre-crash data

March 23-25, 2026

Slide 668

Gear Selection - Jaguar

March 23-25, 2026

Slide 669

Range Rover Test L Pre-crash Speed

March 23-25, 2026

Slide 670

Range Rover Test L Pre-crash Steering

March 23-25, 2026

Slide 671

Rang Rover Test L Pre-crash Steering

March 23-25, 2026

Slide 672

Range Rover Test L Delta Vx

March 23-25, 2026

Slide 673

Range Rover Test L Delta Vx

March 23-25, 2026

Slide 674

Range Rover Test D Delta Vx

March 23-25, 2026

Slide 675

Range Rover Test L Delta Vy

March 23-25, 2026

Slide 676

Range Rover Test D Delta Vy

March 23-25, 2026

Slide 677

Range Rover Test D Roll Angle

March 23-25, 2026

Slide 678

Range Rover Test D: SWA vs Yaw

March 23-25, 2026

Slide 679

2018 Jaguar XE 2.5T Test A • 6 mph front-to-barrier • -6.2 mph Delta V • Event (operating time 14,293,917 s) is Test A • Event (operating time 6,213,671 s) prior recording

March 23-25, 2026

Slide 680

2018 Jaguar XE 2.5T Test B • -4.2 mph Delta V • Event (operating time 14,293,917 s) is Test A • Event (operating time 6,213,671 s) prior recording Test C • -5.3 mph Delta V • Event (operating time 14,293,917 s) is Test A • Event (operating time 14,296,596 s) is Test C

March 23-25, 2026

Slide 681

2018 Jaguar XE 2.5T Test E, F, G • +2.9 mph, +4.3 mph, +4.95 mph Delta V • Event (operating time 14,293,917 s) is Test A • Event (operating time 14,296,596 s) is Test C

March 23-25, 2026

Slide 682

2018 Jaguar XE 2.5T Test H • +7.3 mph Delta V • Event (operating time 14,303,301 s) is Test H • Event (operating time 14,296,596 s) is Test C • Plus Apple Watch Crash Notification • Plus Jaguar Automatic Crash Notification • Plus visit from officer

March 23-25, 2026

Slide 683

2018 Jaguar XE 2.5T Test I • +5.6 mph Delta V • Event (operating time 14,304,552 s) is Test I • Event (operating time 14,303,301 s) is Test H

March 23-25, 2026

Slide 684

2018 Jaguar XE 2.5T In all recordings: • Buckle status unavailable • Lateral Delta V all zeros • Pre-crash roll angle all zeros when roll rate is non-zero

March 23-25, 2026

Slide 685

2018 Jaguar XE 2.5T - Test H

March 23-25, 2026

Slide 686

2018 Jaguar XE 2.5T - Test H Steering wheel angle

• Instrumentation failure • Comparison with video appears appropriate • Future comparison with JLR EDR • Future testing with deliberate pre-crash roll and yaw

Yaw Rate and Roll Rate

• signal too small and noisy on reference instrumentation • Comparison with video appears appropriate • Future comparison with JLR EDR • Future testing with deliberate pre-crash roll and yaw

March 23-25, 2026

Slide 687

2018 Jaguar XE 2.5T - Test H

March 23-25, 2026

Slide 688

2018 Jaguar XE 2.5T - Test H - speed from Ax

March 23-25, 2026

Slide 689

2018 Jaguar XE 2.5T - Test H

March 23-25, 2026

Slide 690

2018 Jaguar XE 2.5T - Test H

March 23-25, 2026

Slide 691

JLR seat belt buckle status • Jaguar:

• buckle status unavailable

• Range Rover:

• Driver buckle – correct half the time (sensor issue?) only correct in frontal impacts? • RF buckle – correctly reported • LR, CR, RR – reported unbuckled in all four tests with EDR recording • RR buckled occupant in three of the four tests with EDR recording

March 23-25, 2026

Slide 692

JLR Manufacture Tool • Can obtain copy of EDR data, but parameters are (mostly) not translated • Showed that two events can be recorded at a time

March 23-25, 2026

Slide 693

JLR Manufacturer Tool (legacy) • Parameters include

• IC at crash and download, lifetime timer, key-on timer, global real time • Number of events, time between events, record complete • Tell tales, times when sensors lost, deployment times • buckle status, seat track status, OCS status, etc. • Pre-crash SWA, Ax, Ay, Az (heave), roll, pitch and yaw rates • Pre-crash speed, acc pedal, brake on/off, brake pressure, RPM, engine torque, gear selection, cruise control status, CC over-ride, brake pre-charge, etc. • DVx, Dvy

March 23-25, 2026

Slide 694

Conclusions from testing • Test vehicles store two events at a time • Oldest ND events over-written by new events • Consistent with 5 mph Delta V record threshold • Delta V’s, speeds, SWA, Yaw, Roll and brake appear to be appropriate (when reported)

• Polarity issue with pre-crash Jaguar longitudinal acceleration • Gear selection, shifting appear appropriate • Buckle status may or may not be reliable • Incomplete – waiting on JLR EDR March 23-25, 2026

Slide 695

March 23-26, 2026

Case Examples EDR Testing of non-Bosch CDR Tool Supported Automobiles

March 23-25, 2026

Slide 696

Case example 1 - SUA • Event #1, -17 mph Delta V • Dr & RF +SB • Pretensioner & AB deployments • Pre-crash data:

March 23-25, 2026

Slide 697

Case example 1 - SUA

March 23-25, 2026

Slide 698

Case example 1 - SUA

• Did Land Rover have a problem?

March 23-25, 2026

Slide 699

Case example 2

Veh 1: 2019 LR Range Rover Veh 2: 2021 Dodge Charger

March 23-25, 2026

Slide 700

Case example 2

Veh 1: 2019 LR Range Rover • Unrepaired • Going to be sold

March 23-25, 2026

Slide 701

Case example 2

Veh 2: 2021 Dodge Charger • Vehicle unavailable • Driver has substantial injury claim • knee surgery • spinal injections • etc

March 23-25, 2026

Slide 702

Case example 2

CS shows 1 event on IC 9126 and DL at IC 11,946 • IC analysis predicts date 3 weeks before date of crash • Driver buckled • Accelerated from 2 to 16 mph • -8 mph Delta V

March 23-25, 2026

Dodge Charger • +10 mph Delta V • 15 mph impact speed (COM)

Slide 703

Case example 3 – Middle in chain reaction

March 23-25, 2026

Slide 704

Case example 3 – Middle in chain reaction • Injuries claimed:

• Neck, back, pelvis • Dental problems, cloudy urine • Seat belt breast trauma necessitating surgery

March 23-25, 2026

Slide 705

Case example 3 – Middle in chain reaction

March 23-25, 2026

Slide 706

March 23-25, 2026

Slide 707

March 23-25, 2026

Slide 708

Hyundai and Kia EDR Data Update John DiTallo, Kevin Vosburgh & Shawn Gyorke On behalf of the ADAS Testing Alliance

March 23-25, 2026

Slide 709

March 23-25, 2026

Slide 710

ADAS Testing Alliance • Comprised of several experts across numerous areas of EDR and vehicle technology. • Michael DiTallo – DSLLC • Kevin Vosburgh – DSLLC • John DiTallo – DSLLC • Eric Paul – DSLLC • Shawn Gyorke – CDSLLC • Peter Leiss – Robson Forensics • Rusty Haight – CSI • Adam Grill – Legacy March 23-25, 2026

Slide 711

March 23-26, 2026

Other ADAS Testing Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 712

Commercial Vehicles Location: Action, Montana / Dates: May 16-17, 2025

2024 Kenworth W990

March 23-25, 2026

2024 Freightliner Cascadia

Slide 713

Passenger Cars Location: Houston, TX / Date: March 21st, 2026

2023 Audi A3

March 23-25, 2026

Slide 714

Passenger Cars Location: Houston, TX & Kildeer, IL

2026 BMW X5

March 23-25, 2026

2025 BMW X6

Slide 715

March 23-26, 2026

Prior Presentations Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 716

Past Updates (2024 EDR Summit) ADAS • Reviewed New Data Parameters • Smart Cruise Control Ex: Gear position, Mode Status • Forward Collision Avoidance Ex: Warning Levels

March 23-25, 2026

Testing • Introduced Zenith Z5 Scan Tool • Bar Pressure Ex: Average, Maximum • Regenerative Braking with Full EV • Truncating method for steering

Slide 717

Past Updates (2025 EDR Summit) Software Version 2.0 • ADAS Data Logger (ADL) • Software Functionality • Future ADAS coverage? • ADAS Driver 2 ECU

• VCIs vs ADLs

March 23-25, 2026

New Data Parameters • Vehicles with three (3) Events • 2025 Testing

• Pre-Crash Data Sections 4 & 5 • Pre-Crash Longitudinal and Lateral Accel • Pre-Crash Yaw Rate • Updated Longitudinal and Lateral Accel

Slide 718

March 23-26, 2026

Topics for 2026 Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 719

Overview EDR / CAN Bus Data Validation • Pre-crash Speed • Pre-crash Long and Lat Acceleration • Pre-crash Yaw Rate

March 23-25, 2026

Data precision during dynamic scenarios • Automatic Emergency Braking (AEB events • Heavy acceleration • Turning

Slide 720

March 23-26, 2026

Miscellaneous Observations for 2026 Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 721

Fail to automatically enter the VIN • Occasionally, despite communication with the Engine Management System (EMS), the GIT Software will not automatically populate the VIN. Observed, primarily, on new model year vehicles. Requires manually entry of the VIN during DLC imaging sessions.

March 23-25, 2026

Slide 722

Incorrect make/model selection • As of March 2026, when communicating with a 2025 or 2026 Genesis GV80, the GIT software selects the same model year Hyundai Kona.

Could result in incomplete data collection!

March 23-25, 2026

Slide 723

2026 Hyundai Kona vs. 2026 Genesis GV80

March 23-25, 2026

Slide 724

2026 Hyundai Kona vs. 2026 Genesis GV80

March 23-25, 2026

Slide 725

2026 Hyundai Kona vs. 2026 Genesis GV80

Majority of data translations are correct/identical.

“Advanced emergency braking system status”

ADAS / Automation Fields only exist in the GV80.

“Automatically commanded steering function category A/B1/C status”

The Kona report contains none of these sections.

“Highway Driving Assist Status”

March 23-25, 2026

Slide 726

Pre-Crash Data Section 4

• Advanced Emergency Braking (on/engaged) • Cruise Control Status (on/off) • Adaptive Cruise (off/engaged) • Lane Departure Warning System (on/off) • Corrective Steering Function • Emergency Steering Function

March 23-25, 2026

Slide 727

Pre-Crash Data Section 5- Highway Driving Assist • Automatically Commanded Steering • Category A • Category B1 • Category C

March 23-25, 2026

Slide 728

“Communication Fail!” Error Message

• When DLC:

• Ignition not in the ‘Run’ position • Damaged wiring, communication bus or ACU

March 23-25, 2026

Slide 729

2026 Hyundai Sonata example

“Communication Fail!” Error Message • Some new (2026) Hyundai vehicles are equipped with an OBDII bracket that interferes with the DLC cable. • May need to remove the OBDII port from its bracket to get the DLC cable to properly fit.

2026 Hyundai Sonata example

March 23-25, 2026

Slide 730

2026 Hyundai Sonata example

Beginning in 2025, there was a phase in of ACUs with 3 Events.

2025 Hyundai Santa Cruz 2025 Kia EV9

2025 Kia Carnival

March 23-25, 2026

GIT Superfan

Slide 731

Vehicles with 3 Events

March 23-25, 2026

Slide 732

March 23-26, 2026

EDR Data Validation / AEB Tests Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 733

Wide Variety of Results Excellent performance

March 23-25, 2026

Less than superior

Slide 734

Location: Kildeer, IL / Dates: February 9th – 12th, 2026 2026 Kia Carnival Hybrid

2025 Hyundai Santa Fe

2025 Kia Sorento

March 23-25, 2026

Slide 735

Testing Overview 2026 Kia Carnival Hybrid

6 Tests

Maximum speeds of about 30 - 44 MPH Target speed at AEB activation 20 – 30 MPH

9 Tests

6 Tests

2025 Kia Sorento

March 23-25, 2026

2025 Hyundai Santa Fe

Slide 736

Forward Collision Avoidance “Cascade” Level 1: Audible/Visual Level: Haptic (steering wheel) Level 3: Active Braking

March 23-25, 2026

Slide 737

March 23-26, 2026

External and CAN Bus Data Acquisition Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 738

Stationary Vehicle Target (SVT)

March 23-25, 2026

Slide 739

External Data Acquisition Equipment

VBOX4 ADAS & HD2 (Video) Included secondary (redundant) data/video loggers

March 23-25, 2026

Slide 740

The Zenith Z5

Zenith Z5 Scan tool

The Zenith Z5 is registered with Hyundai Kia to gain access to the Security Gateway (SGW)*. The SGW is a Central Gateway security feature that allows only authorized access to perform special functions and actuator tests.

March 23-25, 2026

*Internet authentication required before use.

Slide 741

The Zenith Z5

March 23-25, 2026

Slide 742

Data Acquisition

March 23-25, 2026

Slide 743

Data “Limitations” Recording resolution

March 23-25, 2026

Only record 1 ACU

Slide 744

ABS/ESC module monitors: • Pre-crash Speed • Pre-crash Longitudinal and Lateral Acceleration • Yaw Rate

March 23-25, 2026

Slide 745

March 23-26, 2026

Speed Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 746

Test Course

March 23-25, 2026

Slide 747

ADAS Settings • Driver alert settings are generally programmable. IIHS protocol requires “timing of the warning or intervention activation are set to the middle setting.” Vehicle-to-Vehicle Front Crash Prevention 2.0; Test Protocol; Version I; April 2024

2025 Hyundai Santa Fe

March 23-25, 2026

Slide 748

Speed

2025 Kia Sorento Test 7

Average Error 0.97 (kph) Standard Dev. 0.8 (kph)

March 23-25, 2026

Slide 749

Speed

2026 Kia Carnival Hybrid Test 3

Average Error 0.71 (KPH) Standard Dev. 0.7 (KPH)

March 23-25, 2026

Slide 750

Speed

2025 Hyundai Santa Fe Test 1

Average Error 0.96 (KPH) Standard Dev. 0.7 (KPH)

March 23-25, 2026

Slide 751

Summary • Error rate for CAN (EDR) Speed is generally +/- 1 KPH • Speed remained accurate during heavy acceleration • Speed remained accurate during hard turns • Speed remained accurate during AEB events Note: Did not test critical speed yaw or events involving significant wheel slip.

March 23-25, 2026

Slide 752

March 23-26, 2026

Yaw Rate Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 753

Speed

2025 Kia Sorento Test 7

Average Error 0.40 (deg) Standard Dev. 0.6 (deg)

March 23-25, 2026

Slide 754

Speed

2026 Kia Carnival Hybrid Test 3

Average Error 0.70 (deg) Standard Dev. 0.4 (deg)

March 23-25, 2026

Slide 755

Speed

2025 Hyundai Santa Fe Test 2

Average Error 0.83 (deg.) Standard Dev. 1.1 (deg.)

March 23-25, 2026

Slide 756

Summary • Error rate for Yaw data is generally +/- 1 degree • Yaw rate remained accurate during hard turns Note: Did not test critical speed yaw or events involving significant wheel slip.

March 23-25, 2026

Slide 757

March 23-26, 2026

Pre-crash Longitudinal Acceleration Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 758

Pre-crash Longitudinal Acceleration Rate

2025 Kia Sorento Test 7

Average Error 0.09 Standard Dev. 0.14

March 23-25, 2026

Slide 759

Pre-crash Longitudinal Acceleration Rate

2026 Kia Carnival Hybrid Test 3

Average Error 0.08g Standard Dev. 0.12g

March 23-25, 2026

Slide 760

Pre-crash Longitudinal Acceleration Rate

2025 Hyundai Santa Fe Terst 2

Average Error 0.08 Standard Dev. 0.10

March 23-25, 2026

Slide 761

Summary • Error rate for Long Accel data is generally +/- 0.1 g • HOWEVER, the reporting resolution for Hyundai/Kia Pre-crash longitudinal data (EDR) is 0.1g

March 23-25, 2026

Slide 762

Pre-crash Longitudinal Acceleration Rate

2026 Genesis GV80

• Appears to truncate

March 23-25, 2026

Slide 763

Evidence of Truncation for CAN Longitudinal Acceleration Rate

2025 Kia Sorento Test 7

The recorded data from the ABS/ESC module truncates in the same way as the EDR readout.

March 23-25, 2026

Slide 764

Other data that truncates (steering) • Set steering wheel angle to 27 degrees and triggered an event • Set steering wheel angle to 29 degrees and triggered an event Zenith Z5

EDR Readout

Results: • In both cases, Steering rounded down to 25 degrees

Conclusion: • Hyundai, Kia & Genesis Vehicles will truncate, not round to the closest multiple of 5

March 23-25, 2026

Slide 765

March 23-26, 2026

Pre-crash Lateral Acceleration Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 766

Pre-crash Lateral Acceleration Rate

• The Lateral Acceleration rate recorded via the ABS/ESC module does NOT truncate. • Reporting resolution is 0.01g (not 0.1g). • Cannot use for specific EDR validation. • However, CAN Acceleration may be compared to VBOX Lateral Acceleration to emphasize the effect of low resolution and truncation (instead of rounding). March 23-25, 2026

Slide 767

Lateral Acceleration Rate

2026 Kia Carnival Hybrid Test 2

Average Error 0.06g Standard Dev. 0.06g

March 23-25, 2026

Slide 768

Long Accel vs. Lat Accel Error Rate Lateral Acceleration

Longitudinal Acceleration

Average Error 0.06g Standard Dev. 0.06g

Average Error 0.08g Standard Dev. 0.12g

2026 Kia Carnival Hybrid : Test 2

March 23-25, 2026

Slide 769

March 23-26, 2026

Other Data Observations

(with EDR applications)

Hyundai and Kia EDR Data Update

March 23-25, 2026

Slide 770

Owner’s Manual for ADAS

March 23-25, 2026

Slide 771

Owner’s Manual for ADAS May not function when: “Driving in a car park.”

March 23-25, 2026

Slide 772

Relationship between Yaw and Steering?

Sample: 2025 Kia K5

March 23-25, 2026

Slide 773

Relationship between Yaw and Steering?

• Three (3) hard rights and one (1) soft left

2025 Kia Sorento Test 9

March 23-25, 2026

Slide 774

March 23-25, 2026

Slide 775

Relationship between Yaw and Steering

March 23-25, 2026

Slide 776

Relationship between steering and yaw.

• Good linear region between about –40° and –40° of steering; and/or low speed.

• For every 1° of steering input, the vehicle produces about 0.03°/s of yaw rate in the linear region.

March 23-25, 2026

Slide 777

Relationship between BAR Pressure and Acceleration Rate?

March 23-25, 2026

Slide 778

Prior Bar Testing (2024) All Data Tucson 1.20

1.00

0.80

Limited examination of the relationship between maximum values.

0.60

0.40

0.20

0.00

100

120

140

160

180

Bar (max)

2024 Hyundai Tucson

March 23-25, 2026

Avg

Max

Slide 779

Previous Conclusions (2024) : • Routine braking (.20g - .40g) involved Bar pressure at/below 20 Bar • Moderate braking (.40g - .70g) involved Bar pressure between 20 – 50 Bar • Emergency braking (over .80g) involved Bar pressure over 90 Bar • Static maximum application was not a good predictor of maximum Bar pressure during emergency braking in the 2023 Kia Niro • Static maximum application was a good predictor of maximum Bar pressure during emergency braking in the 2024 Hyundai Tucson

Limits: • Only two (2) vehicle sample size • Only 2wo (2) dry surfaces tested; majority conducted on high Mu surface (newer concrete) • Only compared maximum March 23-25, 2026

Slide 780

Relationship between BAR Pressure and Acceleration Rate

March 23-25, 2026

Slide 781

Relationship between BAR Pressure and Acceleration Rate

March 23-25, 2026

Slide 782

March 23-25, 2026

Slide 783

March 23-26, 2026

March 23-25, 2026

Slide 784

BMW AEB Testing with EDR Applications John DiTallo, Kevin Vosburgh & Shawn Gyorke On behalf of the ADAS Testing Alliance

March 23-25, 2026

Slide 785

March 23-25, 2026

Slide 786

Slide 787

BMW Drive Recorder

March 23-25, 2026

Slide 788

BMW Drive Recorder • BMW DRIVE RECORDER. OPERATING SYSTEM 7 / 8 I 8.5 / 9 • Uses the integrated on-board cameras • Automatic and Manual recording can be started by long press of the parking button. • Videos can be downloaded directly to a USB device or exported to a mobile device. • Up to 10 videos can be stored. March 23-25, 2026

Slide 789

BMW Drive Recorder • Automatic recording In the case of an accident, BMW Drive Recorder can automatically record videos before and after the event, including embedded data (time, date, vehicle speed, GPS coordinates). In the event of a theft, videos are recorded only after the event.

Note: Must be enabled by the vehicle owner.

March 23-25, 2026

Slide 790

BMW Drive Recorder • First introduced in 2019 on the BMW 8 Series (G15).

March 23-25, 2026

Slide 791

BMW Drive Recorder Required Hardware: Vehicle must be equipped with Parking Assistant Plus (includes the 4-camera Surround View system).

March 23-25, 2026

Slide 792

BMW Drive Recorder • Video: Resolution varies; H.264; 4 possible cameras (selectable); 30 fps; 20 – 80 seconds in duration (selectable); GOP is 1 i-frame/29 p-frame; static • Data: GPS location, speed, date/time stamps included in an .xml or metadata file • Storage: 10 video events; new record overwrites oldest record • Export: Via in-car USB port (type A or type C) • Trigger threshold: Do NOT require a crash; acceleration based or manually triggered by driver • Vehicle must be in “Run” mode

March 23-25, 2026

Slide 793

Basic export process • Requires in-vehicle power to remain on throughout export Drive Recorder: • 1. From main iDrive menu, select Apps Menu • 2. Select "All apps" • 3. Select "Drive Recorder" • 4. Select "Recordings" • 5. Choose "Export recording" (for specific recordings) OR “Export all” (some variation in GUI)

March 23-25, 2026

Slide 794

BMW Drive Recorder

March 23-25, 2026

Slide 795

BMW Drive Recorder

March 23-25, 2026

Slide 796

BMW Drive Recorder

March 23-25, 2026

Slide 797

2026 BMW IX EV

March 23-25, 2026

Slide 798

2026 BMW IX EV

March 23-25, 2026

Slide 799

Theft Detection

March 23-25, 2026

Slide 800

March 23-25, 2026

Slide 801

AEB / Data Validation Testing

March 23-25, 2026

Slide 802

March 23-26, 2026

BMW Testing Location: Dates:

Lake Zurich, Illinois February 9 -13, 2026

Location:

Houston, Texas

Dates:

March 21 and 23, 2026

March 23-25, 2026

Slide 803

BMW Vehicles Tested • 2025 BMW X7 • 2026 BMW X3 • 2025 BMW X6 • 2026 BMW X5 • 2026 BMW X1 March 23-25, 2026

Slide 804

BMW EDR ADAS Data Limitations

March 23-25, 2026

Slide 805

Previous version EDR Limitations Language

March 23-25, 2026

Slide 806

BMW Ignition Cycle Issue • During testing we noted that even though the vehicle was powered completely off, the ignition cycle counter was not changing • We found that the ignition cycle counter would only increase if the vehicle was turned completely off and the key fob was physically outside the body of the vehicle • If the vehicle was powered off, but the key fob remained in the vehicle, the ignition cycle remained the same

March 23-25, 2026

Slide 807

BMW AEB Recording Issue • With an elegant key off / power down, an event will be recorded every time with no issues • Within one ignition cycle, 4 events max in BMW

March 23-25, 2026

Slide 808

Forward Collision Mitigation Options • Contained within the “Driver Assistance” Menu • Allowed for changes to the detection distance • Tests run at both Early and Medium

• Allowed for changes to the Audible Alert tone volume

March 23-25, 2026

Slide 809

BMW Visual Warning Cycle

March 23-25, 2026

Slide 810

BMW X3

March 23-25, 2026

Slide 811

BMW X3 Test 3 • Test Notes • Target Speed: 15 MPH • Audible Alert and AEB braking functioned • Used right and then left turn signal • Stopped 1.21 m (4 ft) prior to the stationary target

March 23-25, 2026

Slide 812

BMW X3 Test 3

March 23-25, 2026

Slide 813

BMW X3 Test 3 • Test successfully resulted in a recorded event • 20 seconds of pre-trigger data • 0.5 seconds of post-trigger data • DOES NOT RECORD ALL THE WAY TO A STOP

March 23-25, 2026

Slide 814

BMW X3 Test 3 • Table shows the AEB system started warning between -0.5 and -0.25 seconds prior to AEB braking engaging

March 23-25, 2026

Slide 815

BMW X3 Test 3 • Service Brake Application

• Time 0 is when the AEB braking activates • Does not show a service brake application even though the vehicle is slowing

March 23-25, 2026

Slide 816

BMW X3 Test 3 • VBOX HD2 video shows at Frame 1217 the visual alert goes off

March 23-25, 2026

Slide 817

BMW X3 Test 3 • VBOX HD2 video shows at Frame 1222 the visual alert intensifies

March 23-25, 2026

Slide 818

BMW X3 Test 3 • VBOX HD2 video shows at Frame 1232 AEB activated

March 23-25, 2026

Slide 819

-20.00 -19.60 -19.20 -18.80 -18.40 -18.00 -17.60 -17.20 -16.80 -16.40 -16.00 -15.60 -15.20 -14.80 -14.40 -14.00 -13.60 -13.20 -12.80 -12.40 -12.00 -11.60 -11.20 -10.80 -10.40 -10.00 -9.60 -9.20 -8.80 -8.40 -8.00 -7.60 -7.20 -6.80 -6.40 -6.00 -5.60 -5.20 -4.80 -4.40 -4.00 -3.60 -3.20 -2.80 -2.40 -2.00 -1.60 -1.20 -0.80 -0.40 0.00 0.40

BMW X3 VBOX v EDR Speed VBOX v EDR Speed (mph)

30.00

25.00

20.00

• Average difference between VBOX and EDR – 0.1 MPH

15.00

10.00

5.00

• Maximum difference of 1.1 MPH

0.00

VBOX Speed (MPH)

March 23-25, 2026 CDR Speed, Vehicle Indicated (mph)

Slide 820

BMW X5

March 23-25, 2026

Slide 821

BMW X5 Test 3 • Test Notes • Target Speed: 30 MPH • Audible Alert and AEB braking functioned • Used left and then right turn signal • Stopped 1.31 m (4.3 ft) prior to the stationary target

March 23-25, 2026

Slide 822

BMW X5 Test 3

March 23-25, 2026

Slide 823

BMW X5 Test 3

March 23-25, 2026

• Test successfully resulted in a recorded event • 20 seconds of pre-trigger data • 0.5 seconds of post-trigger data Slide 824

Test 3 Exterior Video

March 23-25, 2026

Slide 825

BMW X5 Test 3 • Table shows the AEB system started warning between -0.5 and -0.25 seconds prior to AEB braking engaging

March 23-25, 2026

Slide 826

BMW X5 Test 3 Service Brake Application • Time 0 is when the AEB braking activates • Does not show a service brake application even though the vehicle is slowing

March 23-25, 2026

Slide 827

-20 -19.6 -19.2 -18.8 -18.4 -18 -17.6 -17.2 -16.8 -16.4 -16 -15.6 -15.2 -14.8 -14.4 -14 -13.6 -13.2 -12.8 -12.4 -12 -11.6 -11.2 -10.8 -10.4 -10 -9.6 -9.2 -8.8 -8.4 -8 -7.6 -7.2 -6.8 -6.4 -6 -5.6 -5.2 -4.8 -4.4 -4 -3.6 -3.2 -2.8 -2.4 -2 -1.6 -1.2 -0.8 -0.4 0 0.4

BMW X5 VBOX v EDR Speed BMW x5 Test 3 CDR v VBOX

• Average difference between EDR and VBOX data was 0.25 mph

March 23-25, 2026 Slide 828

March 23-26, 2026

BMW Overall Results

March 23-25, 2026

Slide 829

BMW Visual Alert Distance at Alert 130

R² = 0.846

110

March 23-25, 2026

Slide 830

BMW Visual Alert Intensification Distance at Alert 120.00

100.00 R² = 0.8832 80.00

60.00

40.00

20.00

0.00 10.00

15.00

20.00

March 23-25, 2026

25.00

30.00

35.00

40.00

Slide 831

BMW Audible Alert Distance at Alert 120

100

80 R² = 0.7555 60

March 23-25, 2026

Slide 832

BMW AEB Braking

Distance at Alert

60.00 R² = 0.9226 50.00

40.00

30.00

20.00

10.00

0.00 10.00

15.00

March 23-25, 2026

20.00

25.00

30.00

35.00

Slide 833

BMW AEB Deceleration X7 1 2 3 4 5

-0.67 -0.65 Maximum -0.65 Minimum -0.58 Average -0.57 S.D.

X5 1 -0.66 2 -0.61 3 -0.69 4 -0.66 5 -0.75 Maximum 6 -0.73 Minimum 7 N/A Average 8 -0.59 S.D. 9 -0.66 10 -0.62 11 -0.68

X3 -0.67 -0.57 -0.62 0.04

-0.75 -0.59 -0.67 0.05

1 2 3 4 5

-0.6 -0.62 Maximum -0.62 Minimum -0.64 Average -0.67 S.D.

X6 1 -0.58 2 -0.7 3 -0.67 4 -0.67 5 -0.72 Maximum 6 -0.69 Minimum 7 -0.59 Average 8 -0.63 S.D. 9 -0.69 10 -0.63 11 -0.66

March 23-25, 2026

X1 -0.67 -0.6 -0.63 0.02

-0.72 -0.58 -0.66 0.04

1 -0.74 2 -0.68 3 N/A 4 -0.68 5 -0.75 Maximum 6 -0.57 Minimum 7 -0.69 Average 8 -0.73 S.D. 9 -0.72 10 -0.68 11 -0.7

-0.75 -0.57 -0.69 0.05

Overall Results Maximum

-0.75

Minimum

-0.57

Average

-0.66

S.D

0.05

Slide 834

BMW Conclusions • It is possible to have an AEB event without an event recording in the EDR • Every new AEB event becomes record 1 (most recent event) and each record is pushed down after an additional event. The oldest record will drop off after 6 more events. • In order for an ignition cycle to register, the key fob needs to leave the vehicle. • From our testing, EDR accurately records the AEB events. March 23-25, 2026

Slide 835

An early look at VW/Audi…

March 23-25, 2026

Slide 836

An early look at VW / Audi… • Alert System Sequence • Visual Alert • Audible Alert • “Wake-up” braking • AEB Braking

March 23-25, 2026

Slide 837

Audi Visual Warning Cycle

March 23-25, 2026

Slide 838

An early look at VW / Audi… Distance at Visual Alert

150 130

R² = 0.9531

110 90 70 50 30 10

100 90 80 70 60 50 40 30 20 10 0

Distance at First Brake R² = 0.9935

Distance at Audible Alert

Distance at AEB Braking

120.00

60.00 R² = 0.9647

100.00

40.00

60.00

30.00

40.00

20.00

10.00 15.00

20.00

25.00

March 23-25, 2026

30.00

R² = 0.9709

50.00

80.00

0.00 10.00

35.00

0.00 10.00

15.00

20.00

25.00

Slide 839

30.00

35.00

An early look at VW / Audi… A3 – Average First Brake Application 1

-0.18

-0.16

Maximum

-0.18

-0.16

Minimum

-0.15

-0.18

Average

-0.17

-0.15

S.D.

0.01

-0.17

• Average Peak Friction during first brake “wake up” was -0.44

A3 – Average AEB Brake Application 1

-0.43

-0.51

Maximum

-0.73

-0.5

Minimum

-0.43

-0.6

Average

-0.56

-0.61

S.D.

0.10

-0.73

March 23-25, 2026

Slide 840

Audi customizable choices

March 23-25, 2026

Slide 841

Questions? John DiTallo - Dynamic Safety, LLC jditallo@dynamicsafetyllc.com Office: 847-550-8560 Cell: 847-254-4647 Kevin Vosburgh - Dynamic Safety, LLC kvosburgh@dynamicsafetyllc.com Office: 847-550-8560 Cell: 630-920-3469

Shawn Gyorke – Crash Data Services info@crashdataservices.com Office/Cell: 847-217-6644 March 23-25, 2026

Slide 842

Built for accident reconstruction Registered with forensic accuracy

February 5-7, 2024

Slide 843

February 5-7, 2024

Slide 844

Delta-V:

Applications and misapplications of delta-V data W. R. Rusty Haight Collision Safety Institute

March 23-25, 2026

Slide 845

W. R. Rusty Haight • Collision Safety Institute (2002-)

• TEEX Texas A&M, Staff (1990-2001) • NUTI, adjunct instructor (1990-1991)

• Began teaching EDR/CDR in 2000 (Vetronix/GM)

• NHTSA EDR Training Curriculum Committee (2002)

• Founding ACTAR rep (#135)

• First ACTAR Vice Chair & Administrator • Second ACTAR Chair March 23-25, 2026

Slide 846

Content overview • Concept overview • Resources

• Data Limitations • Bosch CDR Tool Help File Glossary

• OEM and regulatory conditions • 49CFR563 • EU160 • Chinese UDR GB 39732-2020 EDR

March 23-25, 2026

• Misapplications

• End of event time • Underreporting delta-V • Effect of underreporting delta-V

• Applications

• Delta-V, longitudinal* • Maximum delta-V, longitudinal* • Maximum delta-V, resultant

• *applications to lateral data element(s)

Slide 847

Is this really an indication of the “end of crash?”

March 23-25, 2026

Slide 848

Does this really mean the crash is not over?

March 23-25, 2026

Slide 849

What is the “common denominator?”

March 23-25, 2026

Slide 850

What is the “common denominator?” The common denominator, the underlying error, is: looking at a graph without taking into account (a) the resolution or scale of the graph, (b) the underlying purpose of the graphed data, (c) what the data is designed to represent and why and (d) adopting an arbitrary “end” while ignoring other available data elements

March 23-25, 2026

Slide 851

What is the basis for this statement? • … the end user of data displayed (reported) to comply with 49CFR563 to make “adjustments” to the reported data?

• “Always review the Delta V graph to make sure the end of event choice for the single value was rationale.” (sic)

• Or put it another way, can we just use the graphical representation of the data to almost arbitrarily make adjustments to the reported delta-V data when the OEM reporting for delta-V is …

• (1) interpretatively compliant with 49CFR563, • (2) that adjustment doesn’t account for the totality of the remaining available data, • (3) and the proposed adjustment discounts the stated/OEM definitions?

March 23-25, 2026

Slide 852

49CFR563 • Terms and definitions for the data elements for this discussion are mainly from 49CFR563 because that would relate to the data translation report • We may know how we would handle and report data if we were collecting it ourselves from, for example, a crash test we might do it differently • We’d define the crash pulse based on acceleration not averaged delta-V

• This discussion is about how the data related to delta-V is represented in EDR data translation reports and how it might be (is being) misinterpreted and then misapplied March 23-25, 2026

Slide 853

March 23-26, 2026

Concept overview - Or “let’s agree that…”

Delta-V: Applications and misapplications of delta-V data

March 23-25, 2026

Slide 854

Select references • Title 49 of the Code of Federal Regulations, part 563 (49CFR563) • NHTSA TP-563

• Laboratory Test Procedure for Part 563, Event Data Recorders

• UN Regulation No. 160

• SAE Recommended Practices • SAE J1698 (series)

• SAE J1698: Event Data Recorder • SAE J1698 – 1: Event Data Recorder - Output Data Definition • SAE J1698 – 3: Event Data Recorder Compliance Assessment

• SAE J1528

• Glossary of Automotive Inflatable Restraint Systems

• SAE J211 • Bosch CDR Tool Help File – glossary

• Data translation reports – Data Limitations texts

• Instrumentation for Impact Test – Electronic Instrumentation

• Chidester, A., et al, “Recording Automotive Crash Event Data”

• ASTM E29-08

• Standard Practice for Using Significant Digits in Test Data to Determine Conformance with Specifications

March 23-25, 2026

• Haight, S.; “Basic Integral Calculus for Crash Reconstruction” Slide 855

Conventions and communication • Any meaningful conversation should be bound by some sort of common understanding • A common language • Adopted common conventions, words, and terms • Scope – here data from vehicles where 49CFR563 would apply

• We can then focus the disagreement or debate to application/misapplication • As it relates to EDR technology, there are or should be a common “language”

March 23-25, 2026

Slide 856

Should be… • As it relates to EDR technology, there are or should be a common “language”… • The problem is, as anyone that works with EDR data knows, it seems like no two OEMs use the same words, terms, or conventions the same way • Algorithm enable • Wakeup • Algorithm wakeup… • Algo start • “Time Zero” • Trigger threshold

March 23-25, 2026

Slide 857

Should be… • 49CFR563 is often subject to “interpretative compliance” • Where we start to see commonality fail between how we might examine data from, for example, a crash test versus how the OEMs might report it in a EDR data translation report for compliance • Where the OEMs are often left to establish words, terms, and conventions for data reporting those may not easily fit into another context or application

March 23-25, 2026

Slide 858

Delta-V (ΔV) • The delta-V – the “area under the curve” • To define the “curve” (waveshape/waveform) we need to find the bounds of the data that makes up that “curve” • Where the crash pulse starts • Where the crash pulse ends

March 23-25, 2026

∆V = at Slide 859

Delta-V (ΔV) • Delta-V is not an instrument or sensor measured quantity • There is no separate “delta-V sensor”

• In the context of an airbag control module (ACM), the sensors are the accelerometers relative to the longitudinal and lateral axes t

March 23-25, 2026

∆V = at Slide 860

Crash pulse duration and delta-V

Pulse start

Time Zero

Pulse end

∆V = at March 23-25, 2026 861

Slide 861

2 - Integral calculus.pdf

49CFR563.5 - “Time zero” • “… Time zero means whichever of the following occurs first: • (1) For systems with “wake-up” air bag control systems, the time at which the occupant restraint control algorithm is activated; or • (2) For continuously running algorithms,

• (i) The first point in the interval where a longitudinal cumulative delta-V of over 0.8 km/h (0.5 mph) is reached within a 20ms time period; or • (ii) For vehicles that record “delta-V, lateral,” the first point in the interval where a lateral cumulative delta-V of over 0.8 km/h (0.5 mph) is reached within a 5ms time period; or

• (3) Deployment of a non-reversible deployable restraint. …” March 23-25, 2026

- 49CFR563.5 Slide 862

Approximate timeline

Normally “Time Zero”

-20 to -8 to -5 sec before T0

0.015 to 0.05+s

0.1 to 0.3+s

~0.4 to +5.0s

Times are approximate and may not be applicable in all situations or for all systems March 23-25, 2026 863

Slide 863

Delta-V (ΔV) elements reporting • “Delta-V, longitudinal means the cumulative change in velocity, as recorded by the EDR of the vehicle, along the longitudinal axis, starting from crash time zero and ending at 0.25 seconds, recorded every 0.01 seconds. …” • The same applies to “Delta-V, lateral”

• “Maximum delta-V, longitudinal means the maximum value of the cumulative change in velocity, as recorded by the EDR, of the vehicle along the longitudinal axis, starting from crash time zero and ending at 0.3 seconds. …” • The same applies to “Maximum Delta-V, lateral”

- 49CFR563.5, emphasis added March 23-25, 2026

Slide 864

Reporting ΔV

Maximum delta-V, longitudinal – ONE POINT ≤250ms Delta-V, longitudinal - up to 25 points

March 23-25, 2026

≤300ms

Time Zero

Slide 865

Reporting ΔV

Maximum delta-V, longitudinal – ONE POINT ≤250ms Delta-V, longitudinal - up to 25 points

March 23-25, 2026

≤300ms

Time Zero

Slide 866

Reporting ΔV

Maximum delta-V, longitudinal – ONE POINT ≤250ms Delta-V, longitudinal - up to 25 points

March 23-25, 2026

≤300ms

Time Zero

Slide 867

868

“End of event time” • “… End of event time means the moment at which the resultant cumulative delta-V within a 20 ms time period becomes 0.8 km/h (0.5 mph) or less, or the moment at which the crash detection algorithm of the air bag control - 49CFR563.5, emphasis added unit resets. …”

“Becomes” should really be understood to mean for a “end of event (reporting) time,” “doesn’t change by more than” March 23-25, 2026

Slide 868

- Emphasis added

869

Not every data translation report includes a “resultant” March 23-25, 2026

Slide 869

- Emphasis added

Delta-V (ΔV) - Maximum delta-V, resultant • “Maximum delta-V, resultant means the time-correlated maximum value of the cumulative change in velocity, as recorded by the EDR or processed during data download, along the vector-added longitudinal and lateral axes. - 49CFR563.5 …” • The maximum resultant isn’t frequently reported and, when it is, may be reported in km/h2 and the “resultant” element reporting may “still need some work”

2450 km/h2 49.5 km/h 48.9 km/h

March 23-25, 2026

Slide 870

Delta-V (ΔV) - Maximum delta-V, resultant • The maximum resultant may also be reported with a different data element name (not found in the Data Limitations or Glossary)

8405 km/h2

91.7 km/h

22EDR 89170-04740

March 23-25, 2026

Slide 871

Delta-V (ΔV) - Maximum delta-V, resultant • The maximum resultant may also be reported with a different data element name (not found in the Data Limitations or Glossary) 135.8 km/h

18419 (km/h)2

22EDR 89170-02W61

Note the apparent difference is likely related to how the calculated resultant with calculated using data at select points in the dataset March 23-25, 2026

Slide 872

Delta-V (ΔV) - Maximum delta-V, resultant • The maximum resultant may also be “suggested” by the individual components rather than a individual reported (calculated) resultant

March 23-25, 2026

Slide 873

Delta-V (ΔV) - Maximum delta-V, resultant • The maximum resultant may also be “suggested” by the individual components rather than a individual reported (calculated) resultant

March 23-25, 2026

Slide 874

Delta-V (ΔV) - Maximum delta-V, resultant

March 23-25, 2026

Slide 875

Delta-V (ΔV) • “Delta-V, longitudinal … starting from crash time zero and ending at 0.25 seconds, recorded every 0.01 seconds. …” • At 49CFR563.8, Table 3: 1km/h resolution (– up to 25 data points)

• “Maximum delta-V, longitudinal means the maximum value … as recorded by the EDR, of the vehicle along the longitudinal axis, starting from crash time zero and ending at 0.3 seconds. …” • At 49CFR563.8, Table 3: 1km/h resolution and 2.5ms resolution for the reported time to “Maximum delta-V, longitudinal” (– a single data point)

• The elements are reported at different time resolution and to different end points but both start effectively at “Time Zero”

March 23-25, 2026

Slide 876

“End of event time” • For delta-V reporting within the scope of 49CFR563, the end of the event is specified and then further described in SAE J1698 • “… End of event time means the moment at which the resultant cumulative delta-V within a 20 ms time period becomes 0.8 km/h (0.5 mph) or less, or the moment at which the crash detection algorithm of the air bag control unit resets. …” -

49CFR563.5, emphasis added

- SAE J1698

877

March 23-25, 2026

Slide 877

- Emphasis added

878

“End of event time” • “… End of event time means the moment at which the resultant cumulative delta-V within a 20 ms time period becomes 0.8 km/h (0.5 mph) or less …”

49CFR563.5, emphasis added

≤300ms

Time Zero

Tend

- SAE J1698

March 23-25, 2026

Slide 878

- Emphasis added

879

“End of event time”

Time Zero

Tend

• “… End of event time means the moment at which … the crash detection algorithm of the air bag control unit resets. …” - 49CFR563.5, emphasis added

- SAE J1698

March 23-25, 2026

Slide 879

- Emphasis added

Using “End of Event time” in a table/graph

• “End of Event Time” has to do with defining a reporting period not necessarily the point where one with the underlying accelerometer data would define the event as actually “over” or not March 23-25, 2026

Slide 880

Using “End of Event time” in a table/graph

March 23-25, 2026

Slide 881

Using “End of Event time” in a table/graph

March 23-25, 2026

Slide 882

Using “End of Event time” in a table/graph

March 23-25, 2026

Slide 883

Data Limitations and the Help File Glossary • Some OEMs describe how they report delta-V in the various data limitations for their module types • Some OEMs report delta-V data following 49CFR563 and may have special definitions found separately in the Bosch CDR Tool Glossary • Some OEMs assume we know what the terms mean (mainly as a function of 49CFR563) and don’t really elaborate

March 23-25, 2026

Slide 884

Beginning of Impact Event (Time Zero) • “…The beginning of an impact event (time zero) is defined by: • (1a) For systems with “wake-up” occupant protection control algorithms, the time at which the occupant protection control algorithm is activated. or • (1b) For continuously running occupant protection control algorithms, the time when the cumulative Delta-V of over 0.8 km/h (0.5 mph) is reached within a 20-ms time period in the longitudinal direction for a frontal/rear event or within a 5-ms time period in the lateral direction for a side impact event or • (2) A deployment of a non-reversible deployable protection device occurs. This does not include the deployment of subsequent stages of a multi-stage deployable protection device. …” - SAE J1698-1 - “Event Data Recorder - Output Data Definition” March 23-25, 2026

Slide 885

• SAE J1698.4: • 4. EVENT DEFINITIONS, 4.1 Front/Side/Rear Impact Event, Figure 1 • “… This figure is a very simplified image of event data to illustrate common referencing data points and it is not drawn to scale. Depending on the direction of impact, delta-V and/or acceleration data may be in either positive or negative values. …”

- SAE J1698 - “Event Data Recorder - Output Data Definition”

March 23-25, 2026

Slide 886

“… 4.1.1 Beginning of Impact Event (Time Zero) …” • The beginning of an impact event (defined herein) shall not be interpreted as the moment when the subject vehicle makes a first physical contact with another object. … • … The beginning of an event also does not mark the condition that determines whether to record the event data associated with the event for subsequent retrieval. The purpose of defining the beginning of an event is to enable the alignment of data elements from multiple recording devices on a vehicle. …” - emphasis added - SAE J1698 - “Event Data Recorder - Output Data Definition”

March 23-25, 2026

Slide 887

• This might more clearly show that that “impact” and “Time Zero” are not the same • “ The beginning of an impact event (defined herein) shall not be interpreted as the moment when the subject vehicle makes a first physical contact with another object. …” - SAE J1698 - “Event Data Recorder - Output Data Definition”

March 23-25, 2026

Slide 888

Toyota-specific definitions as found in the Bosch Help File Glossary • “…Time from Time Zero to TRG (Toyota) - "Time from Time Zero to TRG" indicates the time from time zero to the establishment of the frontal crash recording trigger. …” • “… Length of Delta-V - Indicates the record period (in milliseconds) of "Delta- emphasis added V, Longitudinal”…”

March 23-25, 2026

Slide 889

From the Bosch Help File Glossary and Data Limitations • “…Time from Time Zero to TRG (Toyota) - "Time from Time Zero to TRG" indicates the time from time zero to the establishment of the frontal crash - From the Help File Glossary (emphasis added) recording trigger. …” • “… In frontal and rear collision events, the first point where a longitudinal cumulative delta-V of over 0.8 km/h (0.5 mph) is reached is regarded as time - From the 05013_ToyotaS00std Data Limitations (emphasis added) zero for the recorded data. …” • Read carefully, one can see these do not mean the same thing March 23-25, 2026

Slide 890

This is about a reporting requirement • “… In frontal and rear collision events, the first point where a longitudinal cumulative delta-V of over 0.8 km/h (0.5 mph) is reached is regarded as time zero for the recorded data. …”

- From the 05013_ToyotaS00std Data Limitations (emphasis added)

March 23-25, 2026

Slide 891

What about braking during the crash pulse?

March 23-25, 2026

Slide 892

“Time from PreCrash to TRG”

Less than 500ms, here btn 200-250ms

TRG / T0

Variants for Toyota Pre-Crash data reporting

Less than 50ms

0.5sec

March 23-25, 2026 893

Slide 893

March 23-26, 2026

What is tested vs reported? Delta-V: Applications and misapplications of delta-V data

March 23-25, 2026

Slide 894

SAE J1698-3 “Event Data Recorder - Compliance Assessment” • Recommended best practice guideline, not regulatory • 5.1 Delta V Longitudinal

• “… To verify that the EDR output conforms with the requirements stated, the EDR output is compared with the reference accelerometer sensor data according to the following process… • …Unless otherwise noted, the t_deploy is the first deployed restraint … • … t(0) = vehicle contact with barrier (typically derived from related contact switch) …”

March 23-25, 2026

Slide 895

NHTSA COMPLIANCE PROC TP-563-00 • None of the OEMs address or reference the NHTSA Compliance Procedure in the Data Limitations or in the Bosch Help file Glossary • None of the OEMs address or reference SAE J1698-3 “Event Data Recorder Compliance Assessment”, either

• In the US, as it relates to 49CFR563, compliance is self-certified by the OEMs • At “14. POST-TEST REQUIREMENTS” in the TP there is a description of how acceleration is captured and analyzed and then compared to delta-V

March 23-25, 2026

Slide 896

NHTSA COMPLIANCE PROC TP-563-00 • “… Install 2 triaxial accelerometers near the vehicle’s central body longitudinal acceleration/delta-v sensor(s). The first accelerometer shall be mounted on rigid vehicle structure on the longitudinal centerline passing through the vehicle’s longitudinal crash sensor. The second triaxial accelerometer shall be on the vertical centerline passing through the vehicle’s longitudinal crash sensor, either on the outer cover of the module containing the vehicle crash sensor or a nearby rigid structure. The accelerometer axes should be aligned with the vehicles primary axes within +/- 2 degrees. …” (emphasis added)

March 23-25, 2026

Slide 897

TP-563-00 “14.2 – POST CRASH DATA ANALYSIS” • “… a. Save the collected accelerometer and restraint system deployment data in unfiltered form. Default system filtering shall be set to 4 kHz or higher. • b. Filter x-axis accelerometer data to SAE J211 Class 180 and plot versus time. • c. Add error corridor of +/- TBD g’s for entire data set. (Error corridor based on +/- 10% of sensor full scale range.) • d. Check data clip status for acceleration or delta-v in downloaded data • e. Compare recorded acceleration and delta-v against the manufacturer supplied full scale range of sensor(s). • f. Truncate longitudinal acceleration at the time where the sensor full scale range is exceeded in the raw laboratory data or the time recorded by the EDR for clipping of the longitudinal signal. Use the shortest time for the truncation • g. Integrate the accelerometer data to obtain velocity data and plot versus time. • h. Apply an error corridor of +/- 10 km/hr to the entire data set. • i. Plot the EDR reported longitudinal acceleration and/or delta-v on the respective plots. • j. Align the EDR data time with the Laboratory data time using the time of the first air bag stage deployment as the alignment mark based on the firing current recorded for the air bags. …” (emphasis added) March 23-25, 2026

Slide 898

TP-563-00 “14.2 – POST CRASH DATA ANALYSIS” • “… i. Plot the EDR reported longitudinal acceleration and/or delta-v on the respective plots. • j. Align the EDR data time with the Laboratory data time using the time of the first air bag stage deployment as the alignment mark based on the firing (emphasis added) current recorded for the air bags. …”

• By definition then, the testing alignment and comparisons are different than how data would be displayed in a data translation report unless the Time Zero element in the report is also based on deployment timing

March 23-25, 2026

Slide 899

The compliant display for 49CFR563 is then… • Reported as the up to 250ms of “Delta-V, longitudinal” and the single point “Maximum delta-V, longitudinal” data elements • These are not the same, one is reported as blocks of averaged delta-V displayed in 10ms intervals (for up to ~250ms) • The other is the maximum value – as established by the OEM – to a single point (up to ~300ms)

March 23-25, 2026

Slide 900

The TP vs the data translation report • The TP analysis of delta-V is initially tied to the accelerometer data and deployment timing • The data translation report is designed for compliance assessment and is tied to the defined Time Zero and End of Event Time • Some, but not all data translation reports include accelerometer data and the displayed resolution is at different time resolution than the accelerometer data as captured and then analyzed in the ACM • Even before the post processing in the CDR Tool software March 23-25, 2026

Slide 901

Range and clipping • Range

• The +/- maximum amplitude that an accelerometer can measure before distorting or clipping the signal

• Amplitude is the absolute value of the maximum displacement from a zero value

• Acceleration is typically specified in g’s or as an acceleration rate

March 23-25, 2026 902

Slide 902

Range and clipping • Range

• The +/- maximum amplitude that an accelerometer can measure before distorting or clipping the signal

• Amplitude is the absolute value of the maximum displacement from a zero value

• Acceleration is typically specified in g’s or as an acceleration rate

Range Range

March 23-25, 2026 903

Slide 903

Range – “a field of values” • Range may be indicated in data translation reports in different ways

March 23-25, 2026 904

Slide 904

905

Clipping • “…approximately…”

March 23-25, 2026

Slide 905

906

Range – “a field of values” • Range may be indicated in data translation reports in different ways • “… The reported range of the longitudinal and lateral acceleration values is approximately ± 50 g. …” – 01043_SDM10P-conti • “… The design range for the angular rate data is:

• - +/- 240 deg/sec for Bosch ACMs unless specifically called out below • - +/- 299.48 deg/sec for the 2023-2024 MY Alfa Romeo Tonale and Dodge Hornet … • - +/- 300 deg/sec for TRW ACMs, the 2019 MY RAM 1500, and the 2018+ MY Dodge Journey • - +/- 290 deg/sec for 2008+ MY minivans and 2009-2017 MY Dodge Journey • - +/- 340 deg/sec for 2017+ MY Chrysler Pacifica and new 2017+ MY Jeep Compass • - -416.67 deg/sec to +413.41 deg/sec for 2014+ MY Jeep Cherokee …” – 03002_Chrysler March 23-25, 2026

Slide 906

March 23-26, 2026

Conclusions Delta-V: Applications and misapplications of delta-V data

March 23-25, 2026

Slide 907

Conclusions • The original, raw data is captured, then, in post-processing, the data translation reports are developed to convey that information primarily to comply with the reporting requirements of 49CFR563 • Reporting requirements drive the display in a data translation report not the way you or I might want to see the data generated/reported/displayed after, for exmaple, a crash test • The data translation report isn’t for the end user as much as it is for NHTSA and the OEMs March 23-25, 2026

Slide 908

Conclusions • The maximum resultant isn’t frequently reported and, when it is, may be reported in “oddly” calculated values in km/h2 • Reporting that element may still “need some work”

• There are normally multiple data elements in a data translation report associated with delta-V that may influence the way it is displayed with respect to time or the magnitude of the delta-V • Relying on an interpretation of a graph and chart to the exclusion of the underlying tabular or specific data can quickly lead to faulty conclusions March 23-25, 2026

Slide 909

Conclusions • Assuming that the first time one sees two paired data samples at 10ms resolution that don’t appear to change by more than 0.5mph (0.8km/h) without applying … • Terms and definitions as used in the regulations, Data Limitations and Help file • Considering the underlying data • Considering the potential for the effect of braking during the crash pulse

• … is unsupported and does not support that point the “end of the crash”

March 23-25, 2026

Slide 910

Tesla EDR Tool Kit Crash Data Group is the North American distributor for the Tesla EDR Hardware Tool Kit. This EDR Tool kit contains all hardware required to download the Event Data Recorder (EDR) data for supported Tesla vehicles.

www.crashdatagroup.co m February 5-7, 2024

This is the only kit contains genuine Tesla EDR cables

Slide 911

850+ vehicles

Passenger • Trucks • Trailers • Motorcycles Downloadable in seconds

February 5-7, 2024

Slide 912