Mainly was just pointing out that this is data recorded by the airbag module. It's not Tesla's logs, AP video/images, etc. The airbag module can record a handful of things, but the EDR data from it is generally less than 1KB.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Tesla releases new tool for people to retrieve ‘blackbox data’ after a crash
- Thread starter SucreTease
- Start date
-
- Tags
- Model S
Mainly was just pointing out that this is data recorded by the airbag module. It's not Tesla's logs, AP video/images, etc. The airbag module can record a handful of things, but the EDR data from it is generally less than 1KB.
scottf200
Well-Known Member
Unless you are in a wreck and it is not your fault and your insurance wants you to pay as the police give you the ticket. Geez.
Not sure EDR has the data you need for that, unless the fault is based on speed or swerving.
From NHTSA:
It could be valuable to tell that you were rear ended before running in to the car in front of you. Putting the full blame of the accident on the person behind you.
scottf200
Well-Known Member
I guess I was thinking of all the items in red. I recently saw a dashcam video on TMC where a Tesla was sitting at a light and another car in front of it decided it was too far into the intersection when it stopped. The person ahead of the Tesla decided to back up but ran into the Tesla. That person then said the Tesla rear-ended them! I'm sure there are many other examples where speed/brake/throttle/etc could lead to conclusions. i.e. I didn't run into my garage ... the Tesla just hit the throttle itself ... no, I didn't panic and miss the brake but hit the throttle. Wait the EDR data just told the insurance company that you lied. Food for thought on other examples.
Do insurance company give better rates to Mfr and models of their cars that have useable/verifiable EDR data? If so then we all benefit if we have that insurance company. i.e. sort of like the tracking OBDII data to see if the driver is safe or made a mistake. Just another thought.
Valid point, though I'd hope they would find it more likely that the last car rear ended the middle car into the front one vs both the middle and rear cars hit the car in front of them.
mspohr
Well-Known Member
Do we know which boxes in the chart Tesla ticks?I guess I was thinking of all the items in red. I recently saw a dashcam video on TMC where a Tesla was sitting at a light and another car in front of it decided it was too far into the intersection when it stopped. The person ahead of the Tesla decided to back up but ran into the Tesla. That person then said the Tesla rear-ended them! I'm sure there are many other examples where speed/brake/throttle/etc could lead to conclusions. i.e. I didn't run into my garage ... the Tesla just hit the throttle itself ... no, I didn't panic and miss the brake but hit the throttle. Wait the EDR data just told the insurance company that you lied. Food for thought on other examples.
Do insurance company give better rates to Mfr and models of their cars that have useable/verifiable EDR data? If so then we all benefit if we have that insurance company. i.e. sort of like the tracking OBDII data to see if the driver is safe or made a mistake. Just another thought.
In the event of an actual crash, Tesla will still be able to pull the much more detailed gateway log files and they will provide them to the relevant authorities. They have been doing this for years. This new tool has changed nothing.
Depends on the state of the car. The complete kit includes cables for connecting directly to the module and powering it.
The gateway log files are stored on an SD card. Unless the SD card was destroyed, they will be retrievable. Although, if the SD card was destroyed, the EDR most certainly suffered damage as well.
Gotcha, thought you were talking about Tesla pulling them remotely, not disassembling to get a card out.
Maps are stored on an SD card. I think it’s 16 GB. The gateway has a separate 4 GB SD card to store vehicle config, logs, etc.
Just got a PCAN-USB from eBay (who outbid me on the auction the other day?!)... building a cable now. Will see shortly what if any data this module actually provides (presumably not much without having been in a crash?)
Nope, Chassis Bus (CAN6).
*very* boring data indeed, especially if you haven't been in a crash. See attached for a sample report (manually redacted VIN/SN info and the raw data, as their "don't include VIN" option is apparently just for the filename and not the actual data/report...)
Hopefully this saves a curious few from shelling out for the cables/gear needed. While I suspect this might have more useful data about crash sensors, seatbelt tensioners and airbags if you're in a crash, without being in one it is pretty useless/has no interesting data at all. And as wk057 said, this is just reading data from one module (the RCM) on the car. No real telemetry, camera footage, or anything else really useful/interesting.
*very* boring data indeed, especially if you haven't been in a crash. See attached for a sample report (manually redacted VIN/SN info and the raw data, as their "don't include VIN" option is apparently just for the filename and not the actual data/report...)
Hopefully this saves a curious few from shelling out for the cables/gear needed. While I suspect this might have more useful data about crash sensors, seatbelt tensioners and airbags if you're in a crash, without being in one it is pretty useless/has no interesting data at all. And as wk057 said, this is just reading data from one module (the RCM) on the car. No real telemetry, camera footage, or anything else really useful/interesting.
Cool to see a list of things it can retrieve. I plan on trying this on a car with deployed airbags this week. Will post if I can get anything from it.
Also, in case anyone is curious as to the format of the .edr files that Tesla's site uses to generate the reports... they're just json:
Code:
{
"filetype": "Tesla EDR data file",
"hash": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
"payload": {
"F187": "ffffffffffffffffffffffffffffffff",
"F190": "0000000000000000000000000000000000",
"FD00": "0000000000000000",
"FD01": "ffffffffffffffffff",
"FD02": "00000000",
"FD03": "ffffffffffffffffffffffffffffffffffffffffff",
"FD14": "ffffffffffffff",
"FD52": "ffffffffffffffff",
"FD53": "00000000000000000000000000000000",
"FD60": "ffffffffffffffffffffffffffff",
"FD61": "ffffffffffffffffffffffffffff",
"FD62": "ffffffffffffffffffffffffffff",
"FD63": "ffffffffffffffffffffffffffff",
"FD64": "ffffffffffffffffffffffffffff",
"FD65": "ffffffffffffffffffffffffffff",
"FD66": "ffffffffffffffffffffffffffff",
"FD67": "ffffffffffffffffffffffffffff",
"FD80": "0000000000000000",
"created": "1520901458.84"
},
"retrieval_comment": "Tesla EDR Retrieval Program v17.32.1",
"user_comment": "Comment Here"
}Similar threads
