removing B10A2 error code and GLOBTIM interpretation

[wmj]

Hi,

Using FORScan I read code B10A2 (BCMii DTC B10A2:00-2F) in my Ford S-Max with the following freeze frame:

-GLOBTIM: 3191061 min
-TOTDIST: 114320.0 km
-MAINECUV: 12.00 V
-ESTSECRK: No
-ESTSERUN: No
-INCARTMP: 17 °C

I have two questions:
1) I interpret TOTDIST as a total distance when the event happened, but how to interpret GLOBTIM? If the value is in minutes from some point lined to manufacturing the car, then it should mean that it happened 319061/60/24/365=6.07 years from manufacturing the car, which would indicate a future event. So I am puzzled.

2) Is it possible to remove this code using FORScan? (I can remove all other errors, but this one persists)

Thanks in advance,
wmj

[FORScan]

1) There is no exact information about it, but we believe it means the overall time ECU was online since the moment vehicle was built. However, it seems there is a but in FORScan in this PID: the number is correct but the measurement unit must be seconds and not minutes (we have fixed it, so there will be this bug in the next release). So the correct value should be:

3191061 seconds -> 3191061/3600 = 886.41 hours

Ford IDS and some other testers would show it as the following:

886 hours 24 minutes 21 seconds

How to use this freeze frame PID: you can read current value of global real time from the module, compare it with the freeze frame one and try to understand when the DTC happened. We don't know any better way yet.

2. It looks like the special crash reset service function has to be performed in order to reset this DTC. This function is not implemented in FORScan yet.

[wmj]

886 h would mean 37 days, which is impossible, because the car was built in 2008. I realized however that, contrary to what I believed, the freeze frame is not linked to the error B10A2 (I thought so because it was shown in the BCMii section). The freeze frame is updated on each error code (e.g., it was updated today once I got P1202).

So I realized that minutes might be fine as for units for 3191061. My car is 6 years and 4 months old, so 6.07 is very roughly correct (or this is a coincidence).

2. It looks like the special crash reset service function has to be performed in order to reset this DTC. This function is not implemented in FORScan yet.

I looking forward it!

[FORScan]

886 h would mean 37 days, which is impossible, because the car was built in 2008.

886 hours online (ignition is on). So if your vehicle is driven 30 minutes per day (avg), you will have only 180 hours per year. Although we agree that it seems to be too small number for 6 year old vehicle. So, it seems correct interpretation of this PID is still a problem.

I realized however that, contrary to what I believed, the freeze frame is not linked to the error B10A2 (I thought so because it was shown in the BCMii section). The freeze frame is updated on each error code (e.g., it was updated today once I got P1202).

The freeze frame is exactly linked to a specific DTC. However the on-board diagnostic system does a refresh of the DTC list, so if some error is still exists, it may update their timestamp.