ARnews: Re: DERM- Automotive Black Boxes-

The Traffic Accident Reconstruction Origin -ARnews-

Re: DERM- Automotive Black Boxes-

Bill Wright (bwright@tarorigin.com)
Thu, 18 Mar 1999 08:16:56 -0500 (EST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Tim Scheiidt: "policies and procedures"
Previous message: Ted Boyne: "Re: vehicle data systems chip"
Maybe in reply to: Bill Wright: "DERM- Automotive Black Boxes-"
Next in thread: Bob Cole: "Re: DERM- Automotive Black Boxes-"

Each major onboard computer system (ABS, ECM, Air Bag, etc)
has its own diagnostic capabilities. This is a necessity as
these systems are complex and require a system check to be
sure all is working fine before they attempt to perform their
tasks. Currently each of these systems are independent, meaning
there is not one single "Black Box" that records everything.
Instead, several "black Boxes" record some information. I agree
with Ed, there is potentially, some good stuff here.

If a system fails the diagnostic, the unit generates a trouble
code (the reason for failing the diagnostic). An idiot light
is usually displayed to alert the driver to the problem.
Sometimes the trouble code is actually displayed in the
idiot light. In these cases the code can be read by counting
the 'blinks". Whether displayed or not the code is stored and
easily retrievable by technicians that are charged with fixing
the problem. Any modern repair shop should have a tool that can
read trouble codes. I think we will universally agree this is
a good thing.

A Little History

In the past, each automaker had its own method for retrieving
information. OBDII (On Board Diagnostics (Generation) Two)
standardized the diagnostic part of the computer output. So,
GM trouble codes can be retrieved by the same instrument that
retrieves codes from Fords, Jaguars, etc. Unfortunately, all the
information contained in the computer is not addressed in OBDII
standards.

For example, an airbag trouble code might be generated if the
clock spring in the steering wheel fails. This trouble code is
easily retrievable under OBDII standards. But (and I think the
point of Ted's original post), many modules gather more information
than is required by OBDII. In some cases, airbag modules are capable
of counting the number of engine starts after the trouble code was
generated. This information is accessible only with proprietary
software or hardware. The intent of gathering this information is
clear.

This brings me back to the original question I posed. While it may
be that only the manufacturer has the equipment to access the data,

WHO OWNS THE DATA?

Does the manufacturer have the right to retrieve it?
Must the owner/driver disclose the results?
Must the manufacturer disclose his findings?

I do not know of a case where these questions have been tested.

I personally have not had a case that hinged on having this information
(at least I don't think so- this is a frightening thought), but I am looking.

Bill

Bill Wright
bwright@tarorigin.com

Next message: Tim Scheiidt: "policies and procedures"
Previous message: Ted Boyne: "Re: vehicle data systems chip"
Maybe in reply to: Bill Wright: "DERM- Automotive Black Boxes-"
Next in thread: Bob Cole: "Re: DERM- Automotive Black Boxes-"

NOTE: You are reading in an archived session of ARnews. It is possible that this topic is still being discussed. To see if this topic is still active, or of there were any more recent posts on this topic, check later archives of ARnews.

If there is no current post, and you would like to add to this topic, link to the Current ARnews Discussion and begin a new thread. Be sure that if you are starting a new post that the thread title does not contain the abbreviation RE: Placing RE: at the beginning of a new post will confuse Hypermail and prevent others from answering your post in the future.