Status Identifier

Status identifier

General
There are status indicator (status identifiers) that can be read out for every diagnostic trouble code. The control module tests every connection (signal) or function more or less periodically, depending on the self-diagnosis' conditions for start.
By reading out the diagnostic trouble code with associated status identifier, then you obtain status for the diagnostic trouble code test that detects the malfunction, as well as if the malfunction exists now or not.

Note! Status identifier, Counter and Frozen values are the most important factors to deciding the malfunction's nature, that is, to decide:

- when the malfunction was detected (frozen values, counters)
- what the driving conditions were at the time (frozen values)
- status for the test (self-diagnosis) (status identifier)
- how frequent the malfunction is (counter).
All status identifiers (or malfunction detection counters) do not have to be introduced in one control module, this varies from system too system. All status identifiers restarts the count every time a new driving cycle/operation cycle starts or when erasing diagnostic trouble codes. Status identifiers should be read off continuously as the different identifiers can be updated later on.
The following describes possible status identifiers.

Note! Status identifiers for systems with diagnostics Volvo Diagnos II is slightly different from status identifiers for diagnostic version Generic Global Diagnostics (GGD). See below.

When erasing diagnostic trouble codes, the diagnostic trouble code's status identifier is erased.

Status identifier Volvo Diagnostics II
The following identifiers are available (showed values apply until updated with a new read-out):
- SB 01 Diagnostic trouble code test run in progress.
- SB 02 Diagnostic trouble code test run at least once during current driving cycle.
- SB 03 Sporadic/single malfunctions found the last time diagnostic trouble code test was run during current driving cycle/operation cycle.
- SB 04 Sporadic/single malfunctions found at least once during current driving cycle.
- SB 05 Request light warning light/text message due to detected malfunction.
- SB 06 Diagnostic trouble code test blocked due to malfunction found by another diagnostic trouble code test.
- SB 08 Malfunction detection counter, current value.
- SB 09 Malfunction detection counter, maximum value reached some time during current operation cycle.
Abbreviation SB is from the English 'Status Bit'.




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.
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) 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). 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".

Status identifier Generic Global Diagnostics (GGD)
The following identifiers are available (showed values apply until updated with a new read-out):
- SB 00 Malfunction found the last time that the diagnostic trouble code test was run during current driving cycle
- SB 01 Malfunction found at least once during the current driving cycle
- SB 02 Malfunction found at least once during the current and previous driving cycles
- SB 03 Malfunction found recently since erasing of diagnostic trouble codes
- SB 04 Diagnostic trouble code test run at least once since erasing of diagnostic trouble codes
- SB 05 Malfunction found at least once since erasing of diagnostic trouble codes
- SB 06 Diagnostic trouble code test run at least once during current operation cycle.
- SB 07 Request light warning light/text message due to detected malfunction.




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. The order of status identifiers in illustration and in the list below are presented as they belong to each other, not in numerical order!

Note! If the diagnostic trouble codes are restored, the status identifiers are also restored!

Graph A Diagnostic trouble code test active
Shows if the control module's diagnostic trouble code test is active or not. The blue surface indicates when the test is active. The surface is "dashed", which shows when the diagnostic trouble code test runs it runs in a cyclically pre-determined pattern. Not included as a status identifier.
Graph B Malfunction active
Shows if the malfunction in the vehicle is active or not. The red surface indicates when the malfunction is present (active). Not included as a status identifier.
Graph C Counter 6 malfunction detection (C#6)
The counter counts the number of internal detections of the malfunction that have been performed for the diagnostic trouble code. Not included as a status identifier, see further on in the information. When this counter reaches value +127 the control module considers the malfunction to be active right now.
When the counter is at value -128, the malfunction is not active. The value is reset for every new driving cycle.
If the value increases towards +127, the control module has detected a malfunction and for every internal test the value is counted up. When the malfunction no longer exists, the control module counts down to minimum -128.
The value on the control module can only be changed when it has started the test for the diagnostic trouble code. How big each step is that the control module counts up or down the value by to reach the limits +127 or -128 may vary between control modules. Limits +127 and -128 are pre-defined limits in the control module.
In the graph, the counter first counts down to -128 when the diagnostic trouble code test starts (graph A). When a malfunction occurs (graph B) and the diagnostic trouble code test detects the malfunction, first the counter's value is reset to 0, then it scrolls up to +127. Only then the malfunction is considered to exist. If the malfunction disappears and the diagnostic trouble code test is active, the counter counts down to -128.
SB06 Diagnostic trouble code test run at least once during current operation cycle
Shows if the control module has performed diagnostic trouble code test for this diagnostic trouble code in current driving cycle. When the diagnostic trouble code test starts and counter 6 (malfunction detection) counts down to -128 (no malfunction found) or up to +127 (malfunction found), the control module considers that diagnostic trouble code test has been run.
Yellow-marked surface means that diagnostic trouble code test is not yet run.
Status alternative when reading out is Run or Not run.
SB00 Malfunction found the last time that the diagnostic trouble code test was run during current driving cycle
Shows if the control module detects the malfunction right now. It is only when the test runs that the control module can detect malfunctions and generate diagnostic trouble codes. A malfunction has been detected 2 times during the current driving cycle. Note that only when counter 6 (malfunction detection) reaches the value +127 is it considered to be a malfunction. When the value gas dropped from +127 to 0, it is considered that there is no longer a malfunction.
Status alternative when reading out is Yes (malfunction detected right now) or No (no malfunction detected right now).
SB01 Malfunction found at least once during the current driving cycle
Shows if the control module has detected the malfunctionanytime during the current driving cycle. It is only when the test runs that the control module can detect malfunctions and generate diagnostic trouble codes. The diagnostic trouble code test has started and a malfunction has been detected at least 1 time during the current driving cycle.
Status alternative when reading out is Yes (malfunction found) or No (malfunction not found).
This status identifier is generated at the same time as status identifier SB00 and will remain in status Yes for the rest of the current driving cycle. At start of a new driving cycle, it has changed to status No until a malfunction is detected again.
SB05 Malfunction found at least once since erasing of diagnostic trouble codes
Shows if the control module has detected the malfunction during earlier driving cycle. A malfunction has been detected at least 1 time since the diagnostic trouble code was erased the last time.

Status alternative when reading out is Yes (malfunction found) or No (malfunction not found).
This status identifier is generated at the same time as status identifier SB 00 and will remain in status Yes until diagnostic trouble codes are erased once again.
SB04 Diagnostic trouble code test run at least once since erasing of diagnostic trouble codes
Shows if the control module has performed diagnostic trouble code test for this diagnostic trouble code in current and/or earlier driving cycle since the diagnostic trouble code was erased the last time. This means that if diagnostic trouble code test has been run after erasing of diagnostic trouble codes, it will remain in Run until diagnostic trouble codes are erased once again.
Yellow-marked surface means that diagnostic trouble code test has been run.
Status alternative when reading out is Run or Not run.
This status identifier is generated at the same time as status identifier SB 06.
SB07 Request for lit warning light/text message
Information about the diagnostic trouble code activates a warning light or text message. In this case, lighting of the warning light is requested when a diagnostic trouble code is stored.
Status alternative when reading out is Yes (request performed) or No (no request).
SB02 Malfunction found at least once during the current and previous driving cycles
Pending not yet confirmed diagnostic trouble code.
Status alternative when reading out is Yes (malfunction found but not confirmed) or No (no malfunction found).
This status identifier is generated at the same time as status identifier SB 00 is generated for the first time and will remain in status Yes until certain driving cycle conditions are fulfilled and no malfunctions are detected. After a certain number of driving cycles without detected malfunction, it returns to status No. Number of driving cycles required depends on the system.
SB03 Malfunction found recently since erasing of diagnostic trouble codes
Confirmed diagnostic trouble code.
Status alternative when reading out is Yes (malfunction found and confirmed) or No (no malfunction found).
This status identifier is generated at the same time as status identifier SB 00 is generated for the first time and will remain in status Yes until certain driving cycle conditions are fulfilled and no malfunctions are detected. After a certain number of driving cycles without detected malfunction, it returns to status No. That is, if a malfunction becomes intermittent and no longer is detected, the status will change to No. Number of driving cycles required depends on the system.

Note! For emission-related control system, this status identifier is generated to status Yes (Malfunction found and confirmed), first after status identifier SB02 has had status Yes (Malfunction found but not confirmed) for 2 driving cycles in a row with malfunction detected.