LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Subaru >> 2022 >> Forester Base >> Repair and Diagnosis >> Engine Performance >> System >> Common Diagnostic Operations >> Time Stamp >> General Description
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Time Stamp: General Description

There are three types of record data for the information of time stamp, and they are stored together with diagnostic codes.

NOTE: Depending on DTCs, time stamp may not be stored.
  1. Trip Count [count] 

    This indicates the number of times that the ignition has been turned to ON since the vehicle was manufactured. The ignition ON count of when the diagnostic code is stored is displayed on the diagnostic code check screen.

    NOTE: Subaru Select Monitor 4 screen (A/C system diagnostic code and time stamp)
    Code Description & trouble part Trip Count [count] Time Count Group
    B14E1 AIR MIX DOOR ACTUATOR STEPPING MOTOR CIRCUIT WIRE BREAK (DRIVER'S SEAT) 983  18000 Common
    B14E7 HEATER CORE REAR SENSOR CIRCUIT WIRE BREAK 984  117800 Common

    Furthermore, the current IG ON count (times) can be checked at the data monitor of body control.

    By comparing the current Trip Count and the Trip Count of when the diagnostic code was stored, it is possible to determine that it is how many ignition-ON operations ago that DTC was stored.

  2. Time Count 

    The elapsed time from when the ignition is turned to ON to when the diagnostic code is stored is displayed on the diagnostic code check screen. It is possible to determine the length of time that passed between when the user started driving and when the diagnostic code was stored. Therefore, if Trip Count until the vehicle-received-date is determined by interviewing the user, it is possible to estimate where the user was driving when the diagnostic code was stored, using the information such as Trip Count and Time Count. This estimate is useful information to perform diagnosis including checking of repeatability.

    NOTE: Subaru Select Monitor 4 screen (A/C system diagnostic code and time stamp)
    Code Description & trouble part Trip Count [count] Time [msec] Group
    B14E1 AIR MIX DOOR ACTUATOR STEPPING MOTOR CIRCUIT WIRE BREAK (DRIVER'S SEAT) 983 18000  Common
    B14E7 HEATER CORE REAR SENSOR CIRCUIT WIRE BREAK 984 117800  Common

    When multiple diagnostic codes are recorded for one trouble, it is extremely important to determine the diagnostic code that was stored first. (It is important to perform the diagnosis for the first recorded diagnostic code.) In this case, it is also possible to immediately determine which diagnostic code was recorded first, using the information such as Trip Count and Time Count.

  3. Group 

    Each unit individually counts the elapsed time since the ignition is turned to ON. However, these time counts may have some errors, and therefore, the control modules need to be adjusted to the time carried by the master-time unit (the body integrated unit). When the count is set as common, it means that each control module is already adjusted to the master time, and the display for the master integrated unit is always indicated as Common. When the count is indicated as Originally, it means that the time is not synchronized with the master time. In this case, check the communication between the corresponding control module and integrated unit. When all controls other than the body integrated unit is indicated as Originally, perform the basic inspection for the body integrated unit. Ref. to BODY CONTROL (DIAGNOSTICS)>BASIC DIAGNOSTIC PROCEDURE>PROCEDURE .

    NOTE: Subaru Select Monitor 4 screen (A/C system diagnostic code and time stamp)
    Code Description & trouble part Trip Count [count] Time Count [msec] Group
    B14E1 AIR MIX DOOR ACTUATOR STEPPING MOTOR CIRCUIT WIRE BREAK (DRIVER'S SEAT) 983 18000 Common 
    B14E7 HEATER CORE REAR SENSOR CIRCUIT WIRE BREAK 984 117800 Common 

    Even when multiple diagnostic codes are stored in multiple control modules, it is possible to determine the code stored first through the count function.

    NOTE: Troubleshooting for CAN system U-code occurrence
    When the first stored diagnostic code is a U-code for CAN system, perform the troubleshooting as a U code combination, instead of a U code alone. In addition, when CAN open circuit occurs, communication of the diagnostic device itself becomes impossible beyond the particular areas. However, trouble positions can also be determined by the combination of initial communication success/failure. Thus, by performing the basic diagnostic procedure in LAN system, trouble positions can be determined efficiently on the principle above. Ref. to LAN SYSTEM (DIAGNOSTICS)>BASIC DIAGNOSTIC PROCEDURE>PROCEDURE .