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
|
|
GM Vehicle Support
-
Most GM products get ignition cycles at event, not all get cycles at investigation. What a given download is dependent on the version of software and the module's cababilities. Whether or not a line item or "field" appears in a report/template is dependent on whether or not the module CAN store that element. It is not directly related to a specific car.
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
-
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
-
There are more than 12 different variants of GM airbag control modules each which are capable of capturing various data elements relating to a crash using the EDR sub component. Even, for example, for model year 07 if you include variations for example relating to some vehicle which have a RollOver Sensor and some which don't, there are several potential lists of data elements available but no ONE single, all-inclusive list.
The common data elements on GM vehicles since model year 03 include pre-crash speed, percent throttle, brake switch on-off, engine RPM, delta-V (for as little as less than 150 to approaching 300ms) as well as other status elements such as whether or not the driver's belt was sensed as buckled. Some vehicles in that model year range get significantly more data, some get those elements and a little more. The common thread is the vehicle's capabilities together with the airbag control module's capabilities rather than simply model year or vehicle line (for example, there are significant differences between an 04 Malibu and Malibu Maxx).
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
That vehicle is not currently supported by CDR version 3.0 and "spoofing" is not recommended and may result in inanticipated consequences. That vehicle will probably be supported in an upcoming release of the CDR software.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
No. Coverage for GM vehicles is phased in starting in the mid-90's, for Ford, it starts with model year 2001. Cars sold overseas may or may not be accessible even if that model is sold in the US.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Maybe, maybe not. Even though a vehicle may be sold in both the US and UAE, the VIN structure may be one factor in limiting access using the CDR system. Another limiting consideration is the specific module's software ID. You cannot assume a model sold in the US and sold overseas using the same name would be accessible "everywhere."
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Since you describe the van as "badly burned," I'm assuming you're trying a "desktop" download. You mentioned you've tested the interface communications so, while there are two potential modules that error message refers to, you seem to have narrowed it down to communication with the airbag control module. What's missing is an indication of (a) whether or not the module itself was burned or appears, at the connector, melted/damage in some way and (b) whether or not you're using the GM Power Booster AND have the external power applied, per instruction, to the booster and NOT the interface module. Once you attach the booster and power it properly, if the SDM still won't download, you need to establish whether or not there's damage to the module then, the SDM supplier (Delphi, not Bosch) may be able to tell you whether or not they can download it for you but it's a bit pricey.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Regarding the switch, assuming that switch was monitored by the airbag control module then "airbag suppressed" means the manual switch was in the "suppressed" position.
The hex data is translated by the CDR software and reflects all monitored conditions. Whether or not the switch was in one position or the other - assuming it was monitored by the airbag control module - is reflected as described above.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
"Time difference?" Your question is pretty vague. Then comparied to what and under what conditions? Many of the apparent differences between timing - for various elements - are addressed in the CDR Training and testing examples from the various conferences.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
The current 02002829 cable being shipped does NOT have a yellow casing.
Scott Baker
Crash Data Group
www.cdr-system.com
-
Questions like this can't be answered "in the blind." Complete answers require a review of the CDR report in its native format done by one trained to properly analyze the data found in the report with a situationally complete crash reconstruction and, at times, a mechanical inspection of the vehicle.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
That is correct, there is no listing for an 2009 Cavalier. I believe they stopped making the Cavalier in 2005. Check the 10th digit of the VIN fo confirm the model year.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Perhaps. The most likely culprit is a power interruption leading to a power disruption before the data was recorded but, on that vehicle, such a complete power disruption *completely* eliminating *any* data from being recorded. You wrote, the "CDR stated..." What does that mean, specifically? Was there a file recovered that read: "events=none?" Did it error out and indicate "unable to retrieve..." Was there an error message along the lines of "no communication..." The specifics of the result (dialog box or file and report) are key to troubleshooting. Another possibility is that there was no deployment and the bags being "out" was a function of someone cutting them loose rather than an actual deployment. An inspection of the bag cover can often lead to a conclusion in that regard.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
Actually, that question is NOT so simple. Depending on the type of vehicle you're asking about there may be more than one "brake switch" referenced in a CDR report. Generally speaking; however, an indication of "brake switch = 'off'" - assuming it is actually a monitored parameter - means the switch isn't closed, not whether ornot there was braking or the brakes were "applied."
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
One should always use the most recent release of the CDR program and you question doesn't indicate which version you're using so there may not be a complete answer available. With that in mind, without looking at the actual CDR file, this question simply can't be answered. There may be indications one needs to seek out in the report that would indicate why the system calledd for a "deployment."
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
No, it is not. What you're proposing is called "VIN Spoofing" and it is specifically NOT a supported process and is strongly discouraged. Assuming that you DO actually get the CDR program to communicate with the otherwise UNsupported module, you CANNOT be sure any recovered data is translated correctly. Part of the proper translation process often includes a reliance on the VIN and "spoofing"a VIN may result in data being incorrectly translated.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
-
No, 158 mph isn't a "default" nor is it data that is "lost." "Default" means a value automatically assigned by the system. 158 is a translated value not one automatically assigned. In that same context, you mention 0mph...why wouldn't you instead wonder if 0 mph is the "default?"
158 is something else, it is typically an UNwritten value or one associated with an error in transmission. Data is never "lost" in the context of being scrambled or "gone missing." 158 is a translated value from the hex data as stored and MAY indicte a transmission error or an unwritten data byte depending on the car line (i.e.: here we're talking about GM, but there are other translations or possible meanings for Ford and Chrysler and which may also vary depending on the version of the CDR program you're using and not all are laid out in the Data Limitations text).
A more thorough explanation, with examples, is found in the CDR Analyst Class handout materials. The background is more complex than one would find in the Data Limitations alone.
Rusty Haight
Collision Safety Institute
www.collisionsafety.net
|
|
