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 Download Support
-
At this time (Feb 08), that PCM should be marked, in the Help File, "DLC access only." Bosch announced at the Houston conference that they're working on direct-to-PCM cable for the PCM in the Fusion, Milan, Zephyr, MKZ. The cable indicate in the Help file now will not work with these vehicle's PCMs.
Set it aside for now or put it into another like car and go through the DLC with the proper DLC cable and Ford PCM Adapter in place. I'm sure Bosch will announce when there's an appropriate cable available as soon as that plan's in place.
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
-
Downloads with older versions can be opened in newer versions and the features and formatting of newer versions would be applied to the file previously downloaded. In the case of the "additional" 3 seconds of brake switch, that's additional interpretation by the CDR software of data stored but not previously interpreted. In the case of the "missing graph" it was removed but the same data remains in the data table, nothing is lost other than a formatting change long called for by users who believe - as I do - that the graph dumbed down the CDR report and end user applications.
It really sounds like the end user is out of date in his training and with the system. These are topics covered at the CDR User's Conference and in the CDR training.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
A Windows error, some component or DLL is missing. Probably oledlg.dll from the WindowsSystem32 folder
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
We've seen this from time-to-time where someone goes to reprogram the interface and it fails in 2.9. In class I have them roll back to 2.8, reprogram the interface, install back to 2.9 and then try again. Seems to work.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Yes. GM pre-crash data is a collection of individually captured data elements coming from various sources in the car, truck or SUV normally through the PCM and ultimately being captured at the airbag control module for storage after an "event." Any one of theose elements may be flagged "invalid" but, inasmuch as they come from different sources, they should be considered and evaluated individually. One or more elements marked "invalid" would not necessarily impact one of the others.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
You are apparently using an out of date version of the program, in 3.0 it indicates that the 2007 Escalade requires the 3320 cable, not the 3003. We recommend against "VIN spoofing" because data translation may not function as intended later.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Check your SDM data limitations file, just before SDM data source, it should say "If power to the SDM is lost during a crash event, all or part of the crash record may If power was lost during the crash the module may not be recorded." At the time of the crash the data is stored in RAM. According to a 1999 paper by Chidester et al, including GM's Tom Mercer, at 150msec after algorithm enable, if there is sufficient power, the data begins to write to EEPROM. This takes about 0.7 seconds. If power goes out before the data is transferred, it is possible to have no record of the deployment crash. (Was the vehicle electrical system intact, were you able to turn the key on and see lights in the instrument cluster? If not, and you had to do a benchtop download, this could indicate you had a power loss during the accident.)
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The "recorder" is a function of the airbag control module and not a stand alone device. Where the airbag control module is badly damaged, there are ways some have explored to move the appropriate chip from module-to-module; however, that is not recommended in most instances and for those not very familiar with that sort of activity. The recommended practice is to contact the module supplier and seek their assistance.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Yes, the cigarette lighter in a normally functioning vehicle can carry sufficient amps and is normally connected to a battery that smooths out any spikes in power. If the vehicle has been sitting at a salvage yard, I strongly recommend you check battery voltage and only proceed if you have 11+ volts. You do not want to have voltage decay below the level where the system stops communicating (about 9 volts) and cannot maintain sufficient voltage to keep the module in programming mode.
-
That depends on the method of download (ie: desktop or DLC) and whether or not you need a USB to Serial adapter and its cable(s). In either case, the cable numbers for access to any model of supported vehicle are found in the CDR Help file and reflect cables that should be available for your licensed copy of the CDR software.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
"The VIN showed ACM data available...How is it possible for the CDR to report viable data on this vehicle?"
No, that's not what was happening. There is no indication, based on a VIN alone, that there is "data available." That VIN was simply not excluded from the program because Bosch assumes people won't try to run VINs for vehicles not listed as supported. to exclude the many VINs for veicles NOT supported would mean a programming database that would do nothing more than increase the cost of the program unnecessarily.
"attempted the D/L and got a S/W error, so no data could be D/L..."
This follows the information above and is THe indication of accessibility as indicated in the Bosch approved CDR Technician Course. The software (S/W) ID error indicates the module you were trying to communicate with is NOT supported, there is no data retrievable with the CDR system.
"I am using Vista Home 64 bit OS. Is the CDR software compatible with 64 bit systems?"
Yes, if you're using CDR version 3.1, that version supports Vista.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Toyota vehicles are not accessible using the Boach CDR systema t this time.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
|
|
