dpAtlanta
Well-Known Member
- Joined
- Apr 30, 2019
- Threads
- 34
- Messages
- 2,345
- Reaction score
- 5,642
- Location
- Atlanta, GA
- First Name
- Dave
- Vehicle(s)
- '19 GT350 (#K2503), '17 Cayman, '24 Bronco Badlands 2-door, '26 Ranger Raptor
- Thread starter
- #16
1. The data is temporarily held for near-deployment events. Most will hold several events, and it over-writes prior near-deployment events as additional ones occur.A few questions:
1) Is data permanently held for a near deployment event?
2) If it is, does that mean the EDR is toast?
3) If it’s not permanently held, how long is data held for a near deployment event?
4) Can the system keep multiple near deployment event data?
GM is the exception however. The last near-deployment event is only held for 250 key cycles, then it is erased.
2. Near-deployment events do not "toast" the module... a deployment event does however.
3. See answer #1.
4. See answer #1.
There is NO time stamp or date stamp with any of the data. The only thing that sort of dates the data is the number of key cycles since since the birth of the vehicle and the number of key cycles that existed at the time of either near-deployment, or a deployment event.
Sponsored