@isakhansen: hmm.... thanks for the additional information (each piece of new data adds extra flesh to the diagnostic skeleton - so always a good thing!!)
As I said, my first response was purely about the hex 6C module - but a further observation regarding your latest chronology of events might be useful (maybe?). And, please accept my apology in advance if you already know this stuff and my further apology if my amateur explanation differs from the official version - but here goes:
I suspect a good place to start is to make sure that there is a proper understanding of the anatomy of the Freeze Frame information that accompanies (some) . Here is an example of the details from your auto-scan:
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 8
Reset counter: 95
Mileage: 67163 km
Date: 2021.12.09
Time: 14:30:00
Whilst Freeze Frame might appear at first blush to be thing, the information and the underlying data structure is in reality a product of the underpinning OBD Standards (in your case, OBD-II/EOBD). really is nothing more than the messenger extracting reports that the module has been designed to spit-out when certain events occur.
In my first response, I told you a "porkie" in that I suggested that the Freeze Frame information is related to an "ignition cycle". This was a (little) white-lie that I used for simplicity. In truth, the foundational basis for Freeze Frame data is a construct that the OBD Standard calls a
Drive Cycle, which differs from an ignition cycle - but for ease of understanding, let's not worry about the pedant details of the variations.
So - like death-and-taxes, modules are programmed to undertake a range of self-test exercises with monotonous certainty and regularity whenever the ignition is turned-on (Drive cycle). If a set of predefined thresholds is exceeded as a result of these tests, a will be registered and elements of Freeze Frame information may be populated/updated as shown above.
Date/Time = self explanatory albeit sometimes (not infrequently with older modules?) these data-stamps can be wrong. In your case, these fields appear to be correct
Mileage = self explanatory
Fault Status: This is a single Byte (meaning that it has 8 x Bits of information) that indicates the timing of the occurrence in regard to current/previous test cycle. For example, in the above, Bit 0 is set (Bytes are read from right-to-left), which means that the test failed on the current operation cycle
Fault Priority: This is measure of fault severity defined as follows:
| # | Explanation |
|---|
| 1 | The fault has a strong influence on drivability, an immediate stop is required. |
| 2 | The fault requires an immediate service appointment. |
| 3 | The fault doesn’t require an immediate service appointment, but it should be corrected with the next service appointment. |
| 4 | The fault recommends an action to be taken, otherwise drivability might be affected. |
| 5 | The fault has no influence on drivability. |
| 6 | The fault has a long term influence on drivability. |
| 7 | The fault has an influence on the comfort functions but doesn’t influence the car’s drivability. |
Counters-
Fault Frequency and
Reset Counter : I've coupled these "counters" together because they really measure the same thing - but in opposite directions! If self-test process is undertaken in an ignition cycle
and a has been registered in a previous ignition cycle:
- if the same fault is evident, the Fault Frequency number will increase
- if the same fault is not evident, the Reset Counter will decrease
- the initial number for Reset Counter is established when the is first registered depending on the nature of the fault.
- When the number for Reset Counter decreases to zero, the is cleared automatically
So - what does this all mean? Well.... it means that according to your explanation of events, unless a happened
for the first time on
"Date: 15/12-21 Time: 21:00", your auto-scan won't report that particular date/time stamp. Instead, and again if the same event happened earlier - any new occurrence will simply increase the Fault Frequency number.
You could try clearing the - which will then reset the Freeze Frame counters and the date/time stamp. So any new registration of the will show the new date/time
Don
