CDR Products
Complete CDR Catalog
New Releases
CDR System Kits
CDR Software
CDR Cables
CDR Adapters
CDR Power
CDR Carrying Case
Specials
CDR Resources
Am I Current with CDR?
Vehicle Coverage List
Help Database
CDR News & Research
Training & Certification
Conferences & Summits
Videos & Presentations
CDR Experts Directory
User Groups & Forums
Computer Requirements
Why Do I Need CDR?
Accident Reconstruction
Police Agencies
Insurance Agencies
Fleet Managers
CDR Tools
CSV-Pro
CDR-PSU
Orders
Request a Quote
View Shopping Cart
Shipping
Online Security
Refund Policy
Warranty
Crash Data Group
About Us
Contact Us
|
|
CDR product information and updates
-
CDR version 3.0 shipped in December 07. No future release dates have been announced at this time. Check back at cdr-system.com for announced released dates in the future.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The 03003350 and 02002877 are the same cable, they have just been assigned different part numbers. The "03003350" number was assigned under an older part number system. Newer cables will similarly have different numbers under the system Bosch currently uses. For example, the OBD II cable to be used with Ford PCM downloads is part number F-OOK-108-287.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
-
As long as the "Blue" module has "CAN plus" printed on the casing of the module, you have the most recent module in production.
Scott Baker
Crash Data Group
www.cdr-system.com
-
The subscription offered through Bosch is a software only subscription and does not include hardware updates. Due to the varying costs of cable manufacturing and the unknown of when and what cables will be available with newly supported vehicles, Bosch can't offer hardware on a subscription basis.
Scott Baker
Crash Data Group
www.cdr-system.com
-
Without doing an inventory of what you have currently in your kit, we can't provide an accurate assessment of what you need. Please download the CDR Hardware Checklist that is found on our web site and run an inventory check on your current kit. Then, let us know the hardware you are missing and we will email you an estimate. The checklist is located at: www.cdr-system.com/catalog/CDRKITChecklist.pdf
Scott Baker
Crash Data Group
www.cdr-system.com
-
Please refer to the catalog at at http://www.cdr-system.com/catalog/
and specifically the listing for this cable at: http://www.cdr-system.com/catalog/02002877.html (also available from the same main page where you posted this question). These cables are identical.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
First, one should nomally check the current component checklist at http://www.cdr-system.com/catalog/CDRKITChecklist.pdf for an inventory list. With that in mind, the cable you're asking about is NOT listed there so one of two things has happened: (a) it's been replaced by a newer version of that cable or (b) it's been discontinued.
One clue is the 0300 prefix which generally meant a system cable not an OE specific cable (i.e.: the 02002829 cable would be a GM module type specific cable and the 03001070 cable would be an external DC power cable).
Since the 03003350 cable is not listed, it's probably best to call Bosch tech support or customer service directly and see if they have a listed replacement cable.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The starter kit would get you data from supported cars at most crash scenes assuming you wanted to take the time to get the car repowered or that it could be repowered in the first place. The starter kit includes the hardware and software to do in-car downloads. the expanded kits give you access to the modules directly which, while some would contend is required more often, may be unnecessary in many cases.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The warning message must say more than that. Dialog boxes whether generated by Windows or the CDR program give more detail and may indicate a solution. It "sounds like" you haven't installed a COM port or there's not one on your computer. You should reinstall CDR and watch for options to install the Bosch USB to RS232 (serial) port adapter. In the alternative, you mayhave to buy a suitable adapter on your own.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The error "run-time error 8020 - error reading communication device" is not a CDR software problem. CDR works well under Vista 32bit as well as 64bit and when there's a CDR problem, there's a CDR generated error dialog box but this error is not a CDR generated dialog box. A couple solutions are found at Microsoft's Help and Support site at http://support.microsoft.com/default.aspx?scid=kb;en-us;957264&sd=rss&spid=3223 and http://support.microsoft.com/kb/841700
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
At the same place where you found this FAQ, you will find this link: http://www.cdr-system.com/resources/coverage.html which is the current "Crash Data Retrieval Vehicle Coverage List." It indicates that the Bosch system covers Ford, GM and Chrysler vehicles. While there is, for example, Saab coverage under the heading "GM," lines like Opel and, at this point, Holden, are not supported.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Q: I was wondering if it is standard practice to try to retrieve event data recorders (EDRs) from vehicles equipped with them after fatal crashes, as far as most police departments go?
A: There is no simple answer here, "most police departments" is too broad and there are too many varying laws, policies and departmental processes/procedures to recount them all here.
Q: What kinds of situations warrant the inspection of information from an EDR?
A: Crashes involving passenger cars, light trucks and SUVs.
Q: Is there some kind of special equipment that is needed to remove the EDR or EDRs from a vehicle?
A: There is no such thing as a stand-alone "EDR" installed by an OE in the context of the information available on this site and relating to the Bosch Crash Data Retrieval System. One would not "remove" an EDR. One may remove the safety device control device in which there may be a conditionally functional EDR subcomponent or subsystem but then that would render the safety device (i.e.: air bag) inoperable.
Q: How long does it usually take to process this kind of data once a request is made?
A: Depending on the complexity of the crash, the process includes imaging the data from the relevant control module, then comparing it to a crash analysis of varying complexity and detail which, by itself, can take weeks.
Q: What is used to process or remove the data from an EDR (specialized computer program or equipment)?
A: Review the remainder of this web site where the Bosch Crash Data Retrieval System is sold and you will find the various components of the Bosch CDR system which, together with pretty much any laptop or desktop computer, will run the CD software.
Q: How accurate is data from an EDR?
A: First, in the context of OE installed devices and those which are accessible using the Bosch CDR system, an EDR subcomponent is not a stand alone device; it is a storage process for the data generated largely in other components or sensors and then relayed to the relevant control unit which then stores - when and if the EDR functionality is engaged - that data for later retrieval. So, asking "is data from an EDR accurate" is like asking "if I save something I typed in Word on my computer to my hard drive and then to a thumb drive, would the thumb drive accurately save the data?" Experientially, we can each answer that question. The question you probably mean to ask is: "how accurate is the underlying data which is ultimately stored by the EDR functionality?" The answer to that is "for the most part, depending on how one understands the difference between 'accurate' and 'precise' and then within a larger appreciation for what is and is not stored, the data that can be recovered is generally very accurate."
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The current version of CDR is version 3.5 (just released this week, 7/10). One can print the Help file vehicle coverage list and get the currrent list of accessaible vehicles. No one should be using version 2.8 at this point, it is very much out of date. If you have a question as to whether "vehicle"x" was accessible using version 2.8, back in 2006 when that was the current version, opening a copy of version 2.8 and printing the accessible vehicle list there would address that narrow point; however, today, that coverage is irrelevant. For example, Chrysler and additional Ford vehicles were introduced in version 3.0 in 2007 and they would not have been listed in version 2.8 but are listed as accessible today. So, if someone is using 2.8 today and you're concerned as to whether or not that version will access a specific vehicle, really, the greater concern is the fact that someone using that old a version is seriously out of date with the technology.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
|
|
