Big Brother in my S
Registered User
Joined: Aug 2001
Posts: 2,735
Likes: 0
From: WASTED in Margaritaville
I still say no way.
Like I said they did a story about OBDIII on the vettes when they were new. I remember the big stink.
I SERIOUSLY doubt the computer remember anything but what caused the Check Engine Light to come on.
Like I said they did a story about OBDIII on the vettes when they were new. I remember the big stink.
I SERIOUSLY doubt the computer remember anything but what caused the Check Engine Light to come on.
Former Moderator
Joined: Oct 2000
Posts: 3,826
Likes: 5
From: Denver CO
Let's not forget that we have heard about several suspicious warranty claims on this board. If the dealer could absolutely prove what happened I'm sure some of those claims would have been rejected. The claim that Honda had to honor where a member overrevved the engine by a couple grand comes to mind.
Registered User
Joined: May 2001
Posts: 2,997
Likes: 0
From: Rome, GA
I don't know if there are data acquisition devices on the S2000 but it would not be hard:
Lets assume 2 bytes (16 bits) a piece for 8 (Speed, RPM, Throttle position, temp, exhaust 02 and some other stuff) data samples, and let assume they sample this data 3 times a second. That's 8 * 8 * 3 = 192 bytes a second.
A 256 mb flash memory module is less than 100 dollars so lets go with 256 mb storage (256 million bytes)
256000000 / 192 =1333333(approx) / 60 = 22222 minuets (approx) / 60 > 370 hours of storage
they could do it.
Lets assume 2 bytes (16 bits) a piece for 8 (Speed, RPM, Throttle position, temp, exhaust 02 and some other stuff) data samples, and let assume they sample this data 3 times a second. That's 8 * 8 * 3 = 192 bytes a second.
A 256 mb flash memory module is less than 100 dollars so lets go with 256 mb storage (256 million bytes)
256000000 / 192 =1333333(approx) / 60 = 22222 minuets (approx) / 60 > 370 hours of storage
they could do it.
Registered User
Joined: Feb 2001
Posts: 1,291
Likes: 1
From: Brussels, Belgium
Hi All:
The only thing I know for sure is that the OBD-II system is required by EPA law to store all circumstances during which the MIL (Malfuncion Indicator Light) comes on; this is normal!
I wouldn't be surprised though if manufacturers voluntarily 'expand' the storage capabilities to become some sort of black box for warrantee issues though. Would that be illegal? The manufacturers would have a strong point in suggesting that it is required by law to store the circumstances, and why than not only just at a certain point in time, but a complete history...
Just my two cents!
Siepel
The only thing I know for sure is that the OBD-II system is required by EPA law to store all circumstances during which the MIL (Malfuncion Indicator Light) comes on; this is normal!
I wouldn't be surprised though if manufacturers voluntarily 'expand' the storage capabilities to become some sort of black box for warrantee issues though. Would that be illegal? The manufacturers would have a strong point in suggesting that it is required by law to store the circumstances, and why than not only just at a certain point in time, but a complete history...
Just my two cents!
Siepel
Registered User
Joined: Nov 2000
Posts: 407
Likes: 0
From: Pleasanton
Well, the dash is digital, so a snapshot of the dash would be no problem. The brake and clutch trigger disabling cruise control, so it would not be a big deal to see if they were depressed, although I doubt they could see how far.
I would imagine the system records ALL of this information any time it detects any engine malfunction, airbag deployment, etc.
I seriously doubt it is recording this information continuously except maybe to record the top speed and top RPM, and I would imaging it has room for several snapshots in a rotating buffer that just overwrite each other.
It would be unwise to record this information continuously on a flash chip (and there is definitely no disk!!) because flash chips have limited write cycles. The cheap ones can handle 300,000 write, and the good ones 1,000,000 writes before data loss. If they were recording continuous data, it would burn up the flash mighty quick. When that happened, it is likely that the entire computer would fail due to a parity error. This would be bad.
For a car that is expected to still be on the road 10,15 or 20 years from now, they would be very careful about how often the tickle that flash chip.
I would imagine the system records ALL of this information any time it detects any engine malfunction, airbag deployment, etc.
I seriously doubt it is recording this information continuously except maybe to record the top speed and top RPM, and I would imaging it has room for several snapshots in a rotating buffer that just overwrite each other.
It would be unwise to record this information continuously on a flash chip (and there is definitely no disk!!) because flash chips have limited write cycles. The cheap ones can handle 300,000 write, and the good ones 1,000,000 writes before data loss. If they were recording continuous data, it would burn up the flash mighty quick. When that happened, it is likely that the entire computer would fail due to a parity error. This would be bad.
For a car that is expected to still be on the road 10,15 or 20 years from now, they would be very careful about how often the tickle that flash chip.
