LEMON Manuals: Even more car manuals for everyone: 1960-2025
Home >> Volvo >> 2010 >> V70 R-Design, 3.2 96 >> Repair and Diagnosis >> Engine Performance >> Testing & Diagnosis >> Differential Electronic Module (DEM), Driver Information Module (Dim), Engine And Engine Control Module (ECM) - Design And Function >> Diagnosis (2008-2010) >> Diagnostics And Services >> Status Identifier >> Status Identifier VOLVO Diagnostics II
April 5, 2026: LEMON Manuals is launched! Read the announcement.

Status Identifier VOLVO Diagnostics II

The following identifiers are available (showed values apply until updated with a new read-out):

Abbreviation SB is from the English 'Status Bit'.

Fig 1: Identifying Status Identifier Volvo Diagnostics II Graph
GLL161238Courtesy of VOLVO CARS CORPORATION

The upper graph shows a varying signal value. If the signal value exceeds a max. value, which is considered a malfunction by the control module, then a sporadic malfunction is registered, that is, a malfunction is about to occur. Then the grey-marked surface indicates the signal considered to be incorrect.

The text below uses the term Driving cycle, which may also be called Operation cycle.

NOTE:

If the diagnostic trouble codes are erased, the status identifiers are also erased

SB01 Diagnostic trouble code test run in progress (second paragraph from top). 

Shows if the diagnostic trouble code test runs or not right now (in current driving cycle). It is only when the test runs that the control module can detect malfunctions and generate diagnostic trouble codes.

Grey-marked surface means that the test runs and can detect a malfunction if it occurs. The surface is "dashed", showing that when the diagnostic trouble codes runs, it runs in a cyclic, pre-determined pattern.

Status identifier 03 and 04 shows if a malfunction is detected or not. In this case, a malfunction is detected 3 times, see status identifier 03 in in, see Fig 1.

Status alternative when reading out is Yes (test runs now) or No (test is not run now).

SB02 Diagnostic trouble code test run at least once during current driving cycle (third graph from the top). 

Shows if the diagnostic trouble code test has been run or not during the current driving cycle. If it has been possible for the control module to detect malfunctions and generate diagnostic trouble code any time during the current driving cycle.

Grey-marked surface means that the diagnostic trouble code test has been run at some time. If the diagnostic trouble code test has been run at some time in this driving cycle, status will always be Yes and remain so until the ignition is turned on off and a new driving cycle starts. When a new driving cycle starts, status identifiers are "reset" and is initially No.

Status identifier 03 and 04 shows if a malfunction is detected or not.

Status alternative when reading out is Yes (test completed) or No (test not completed).

SB03 Sporadic/single malfunctions found the last time diagnostic trouble code test was run during current driving cycle (fourth graph from the top). 

A sporadic malfunction (intermittent malfunction) has been detected 3 times the last  time the diagnostic trouble code test was run during current driving cycle. During the diagnostic trouble code test run the last time (see status identifier 01 in, see Fig 1) a malfunction has been detected 3 times.

Status alternative when reading out is Yes (sporadic malfunction found) or No (no sporadic malfunction found).

NOTE:

When the control module detects the malfunction for the first time(status identifier 03 and 04), a diagnostic trouble code has not yet been stored (see last graph in, see Fig 1). It is first when the malfunction detection counter 08 reaches a certain value that the control module considers that a real malfunction exists (a confirmed malfunction) and the diagnostic trouble code is stored.

SB 04 Sporadic/single malfunctions found at least once during current driving cycle (fifth graph from the top). 

A sporadic malfunction (intermittent malfunction) has been detected at some time during current driving cycle. Grey. marked surface means that a malfunction has been detected at some time.

If the diagnostic trouble code test has been run at some time in this driving cycle, status will always be Yes and remain so until the ignition is turned on off and a new driving cycle starts. When a new driving cycle starts, status identifiers are "reset" and is initially No. Status identifier 03 and 04 shows if a malfunction is detected or not.

Status alternative when reading out is Yes (test has been run earlier) or No (test has not been run).

SB 05 Request light warning light/text message due to detected malfunction (sixth paragraph from the top). 

Information that diagnostic trouble code activates a warning light or text message in driver information module. In this case, lighting of warning light is requested when the diagnostic trouble code has been confirmed and stored.

Status alternative when reading out is Yes (request performed) or No (no request).

SB06 Diagnostic trouble code test blocked (seventh graph from top). 

Information that diagnostic trouble code test is turned off as a result of another malfunction and diagnostic trouble code is generated where the root cause is detected. If this in turn results in subsequent malfunctions, it prevents generation of subsequent diagnostic trouble codes. In this case, the diagnostic trouble code test is not blocked.

Status alternative when reading out is Yes (diagnostic trouble code test blocked) or No (diagnostic trouble code test not blocked).

SB08 Malfunction detection counter, current value (eight graph from top). 

When a sporadic malfunction is detected by the control module the malfunction detection counter counts up as long as the malfunction exists.

When the malfunction no longer exists the counter counts down again. This is the basis for the control module's decision to store the diagnostic trouble code and the diagnostic trouble code is stored in the vehicle first when the counter reaches a certain max. value. This max. value varies between different diagnostic trouble codes.

Count rate of the counter is controlled as long as the malfunction exists before it causes customer symptom. The counter is used to decide if it is a real malfunction that has occurred and that has existed for some time. It is the control module's way of confirming the diagnostic trouble code, that is, confirming that a real malfunction exists.

SB09 Malfunction detection counter, max. value during current operation cycle 

Shows max. value that status identifier 08 has reached during current driving cycle. When a new driving cycle starts, the counter is "reset".