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.

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

SB 06 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.

SB 00 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).

SB 01 Malfunction found at least once during the current driving cycle 

Shows if the control module has detected the malfunction anytime 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.

SB 05 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.

SB 04 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.

SB 07 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).

SB 02 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.

SB 03 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.