Rivian Data

About 175,000 Rivians have been delivered to date, and with R2 deliveries imminent, I suspect that number is likely to grow rapidly. So, what data do these things hold and how do we get it?

​Troy Kranz recently worked with Rivian to extract data from an R1T, shared his experience in an INCR post, and kindly gave me permission to summarize what he learned here. Rivian flew two employees out for the interrogation, so Troy was able to learn a lot.

First, Rivian provides portals for owners, private parties, and law enforcement to request data on this page. There are three known sources of data: EDR, CAN bus, and video. The CAN data is sent to the manufacturer via cellular, while the EDR and video interrogations require local hookup. A commercial EDR tool isn’t yet available but is expected to be released with the R2. It’s unknown if they’ll use Bosch.

EDR: Nothing special here. Solid 563 data.

CAN Bus: Unlike Tesla, there’s no SD card. So, if the data isn’t transmitted, a component swap or chip-off interrogation is required. Rivian provided Troy with a .csv containing nine minutes of very detailed data, including: speed, brake status, pedal position, steering, accelerations, yaw, roll, driver attention info, door open events, etc.

Video: The vehicle automatically saves ~15 seconds of event video (collision or hard brake) from six cameras. To acquire the data, you must insert a USB drive and go through the appropriate menus, which are detailed in the owner’s manual. If the related computer is damaged, a chip-off interrogation might be possible, but they haven’t done one yet.

It’s very valuable to know what data we should be gunning for. Thanks to Troy for asking so many questions and sharing his findings, and thanks to you for reading.

Keep exploring,

​Lou Peck
​Lightpoint| JS Forensics