Frequently Asked Questions

Collision Sciences offers a universal, mobile-app-based EDR (Event Data Recorder) tool, and is the only market option that offers affordable hardware, included user training, dedicated client centric data collection, customizable cloud data analysis, strategic alerting and reporting, and engineering tech support for users.

FAQ: CrashScan & EDR Reports

Vehicle support varies by vehicle make and region.  Please check the list for the most up to date support: https://collisionsciences.ca/reports/check_support/

The CrashScan app is the most universal EDR tool available worldwide; however, there are a few vehicles makes that are not supported, although these vehicles may have EDRs and can have data retrieved through other methods, these include:
- 1996-1999 GM vehicles (using non-standard OBD-1)
- Subaru (use local expert)
- Jaguar/Land Rover (use manufacturer)

Passenger vehicle Event Data Recorders (EDRs) can store between 2 and 6 crash events, for all severities of collision, such as for "airbag deployment events" and also for minor "non-deployment crash events".  

These crash events DO NOT automatically erase, with one exeption: 2011 and older General Motors (GM) brand vehicles that experience minor non-deployment events.  

Advice 
Determine the vehicle usage, estimate its ignition cycles would be much less than 250 times since the accident.

(North American Low-Velocity Impact Investigations): 
This data clearing factor would make a difference if it's an LVI report and proof of a non-event is needed.  The Collision Sciences EDR report has a disclaimer note.

Key definitions:
* Minimalistic, extremely easy-to-use interface
* Mobile-friendliness, latest website blocks and techniques "out-the-box"
* Free for commercial and non-profit use

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur in nulla ut magna vehicula libero luctus in ipsum consequat faucibus. Ut porta nulla ac dapibus convallis. Curabitur sit amet massa quam. In ut ex auctor, porta neque quis, sagittis purus. Nunc auctor gravida magna, sed efficitur tortor tristique quis.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur in nulla ut magna vehicula libero luctus in ipsum consequat faucibus. Ut porta nulla ac dapibus convallis. Curabitur sit amet massa quam. In ut ex auctor, porta neque quis, sagittis purus. Nunc auctor gravida magna, sed efficitur tortor tristique quis.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur in nulla ut magna vehicula libero luctus in ipsum consequat faucibus. Ut porta nulla ac dapibus convallis. Curabitur sit amet massa quam. In ut ex auctor, porta neque quis, sagittis purus. Nunc auctor gravida magna, sed efficitur tortor tristique quis.

Field User: Troubleshooting

The following information may help field users experiencing issues collecting data

1

Connecting OBDLink to Phone's Bluetooth

If you have not yet

2

Full Phone Restart. Re-insert Dongle.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam erat libero, bibendum in libero tempor, luctus volutpat ligula. Integer fringilla porttitor pretium. Nam erat felis, iaculis id justo ut, ullamcorper feugiat elit. Proin vel lectus auctor, porttitor ligula vitae, convallis leo. In eget massa elit.

3

Deployment

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam erat libero, bibendum in libero tempor, luctus volutpat ligula. Integer fringilla porttitor pretium. Nam erat felis, iaculis id justo ut, ullamcorper feugiat elit. Proin vel lectus auctor, porttitor ligula vitae, convallis leo. In eget massa elit.