|
|
Post by matts5 on Feb 10, 2023 11:39:03 GMT
In short, someone took my car for a joy ride and did approximately $20,000 USD in damage to the drive train. Luckily I know who has the spare key.
I was wondering from the below codes, the vehicle speed accuracy?
Second question, anyone aware of any data log available that is time stamped to show the vehicle was on, moving, running, battery charging, etc?
Thank you,
Matt
P10A400 - Regulating flap for intake air Mechanical malfunction
Intermittent
Date: 2023-02-04 13:28:32
Mileage: 133730 km
Priority: 2
Malfunction frequency counter: 2
Unlearning counter: 255
Engine speed: 0.00 1/min
Normed load value: 0.0 %
Vehicle speed: 255 km/h
Coolant temperature: 44 °C
Intake air temperature: 39 °C
Ambient air pressure: 1020 mbar
Voltage terminal 30: 11.374 V
Dynamic environmental data: 209628117D0313E3C01358001359341353851357FF
P305400 - Starter does not turn Mechanically blocked or electrical malfunction
Intermittent
Date: 2023-02-04 13:28:24
Mileage: 133730 km
Priority: 2
Malfunction frequency counter: 3
Unlearning counter: 255
Engine speed: 0.00 1/min
Normed load value: 0.0 %
Vehicle speed: 255 km/h
Coolant temperature: 44 °C
Intake air temperature: 39 °C
Ambient air pressure: 1020 mbar
Voltage terminal 30: 6.804 V
Dynamic environmental data: 209628117D0011DC0011D17A110E0014A64015D201
|
|
|
|
Post by whataboutthis on Feb 11, 2023 9:08:38 GMT
I am afraid as far as I know the live data is as its name implies live data, the only sort of exception is the Freeze Frame data which is a recording of certain live data at the point of DTC being thrown. Happy to be proved wrong
With regards to accuracy I am afraid I dont know the answer
|
|
|
|
Post by dv52 (Australia) on Feb 11, 2023 23:20:07 GMT
To add to my colleague's sage advice - there are a multitude of records in live data that might be worth investigating - but the exact readings/records really does depend on the model/make of the car and in particular, the engine type. I assume that you have a PRO account and because it's an easy try - I suggest that you log into the engine module (@ address hex01) and select live data. With a few intelligent words entered into the search-box, you should be able to see the plethora of records stored in the module memory. In regards to your highlighted record Vehicle speed: 255 km/h (see my pic below - taken in a Golf mk7) - I make the following observation: I apologize if you know this stuff already - but because the control modules in modern vehicles are heavily computerized, the fundamental methods for reading/storing information in these modules don't use words/numbers that are familiar to most carbon based life units (i.e. humans like you and me)!  . This is because these modules talk in 0's and 1's (it's called "Binary") and it's mostly because computer efficiency means dollars for car manufacturers!! So, here's the thing - ever since humans crawled out-of the primordial slime, we have been taught to count on our fingers. This means that we use a form of mathematics that is based on the number 10 (i.e. Decimal, also called "Base 10").
However, computers (read "control modules" in vehicles) prefer Binary (Base 2) numbers and the programming of these modules use an allied form of language called Hexadecimal (i.e. Base 16) numbers. Now, I don't want to launch into an arcane discussion of why HEX is chosen -so please just accept my assertion that HEX mathematics is a far more efficient method of counting for computerized modules.
OK, with the above brief preface as context - let's look at the number in your highlighted freeze-frame record: 255 is of course a Base 10 number (i.e. Decimal). If I convert 255 into a Hexadecimal number, I get the value HexFF. And If I further convert hexFF into Binary, I get the value 11111111! The string of ones in the Binary number above means that there can be no higher number that can be measured for this record.
So, my observation/conclusion is that at the time that the 2 x errors were first registered in the engine module's error memory, this car was measured as traveling at a speed at least 255 km/hr!! Wow- I hope this car was on a race track!!! Finally, a closing observation - it is of course possible that the speed reading on this car was measured incorrectly (it happens)! However, I note that the 2 x errors that you posted happened 8 seconds apart (look at the time stamp). More importantly, I note that the speed reading is the same on both faults. Kind-of difficult to conclude that 255 km/h is an incorrect reading (IMHO, of course) Finally, finally - The freeze-frame data in a SCAN really does record a snap-shot of the conditions in the car when the fault is first registered in the module. If you take the time to understand the readings and if you intelligently connect the dots- it's possible to interpret the records like reading a book! Here's an example of what's possible:
- perhaps the most intriguing matter related to your 2 x faults (for me, at least) is puzzling coincidence of a car that is measured to be traveling at at-least 255 km/h and the error code P305400.
Is it possible that the driver of this car energized the starter motor when this car was traveling at near FULL speed? Shirley not - if so, it's not at all surprising that the fault descriptor is "Starter does not turn Mechanically blocked or electrical malfunction".
And it's also unsurprising that under this disastrous set of conditions, that the car's battery rail volts (T30 ) collapsed to 6.8V as the starter desperately tried to engage and that the engine speed momentarily drop to zero when the loose stools in the brown stuff collided with the fan blades!!
Why would any one do such a thing?
Don
PS: Please note that my observations are supposition - based entirely on the incomplete information in your post - I'm not offering anything that can be relied-upon in formal proceedings
|
|
. This is because these modules talk in 0's and 1's (it's called "Binary") and it's mostly because computer efficiency means dollars for car manufacturers!!