This block causes the OBD fault manager to be generated. The fault manager must exist only once in the model to enable the fault blocks to be used. The OBD fault manager is designed to aid in the implementation of an OBD compliant application. Inclusion of the OBD fault manager in the model does not necessarily make an application OBD compliant. There are different types of fault manager which contain different features and options. Currently supported types are Standard and OBD Fault Manager.
Fault Operation
Each fault has twelve parallel states which are tracked. The tables below describes these states. Each fault uses an X/Y counter to filter the input. When the X/Y counter (fault definition block) has executed Y limit times or X limit times with an input 1 the test is considered complete. The next execution of the X/Y counter will begin a new test.
Fault States
State
Description
Storage Location
Suspected
Indicates the state of the most recent execution of the fault definition block.
Volatile (RAM)
Failing
Indicates that the fault has failed its last test.
Volatile (RAM)
Pending
Indicates that the fault is Pending.
NonVolatile (EEPROM)
Confirmed
Indicates that the fault is Confirmed.
NonVolatile (EEPROM)
Permanent
Indicates that the fault is Permanent
NonVolatile (EEPROM)
MIL
Used to aid in illuminating the Malfunction Indicator Lamp.
NonVolatile (EEPROM)
Ready
Indicates that the test has completed a test since the module started.
Volatile (RAM)
Test Compleded This Drive Cycle
Indicates that a test has run to completion at least once this drive cycle.
Volatile (RAM)
Failed This Drive Cycle
Indicates that the fault has entered the Failing state at least once on this drive cycle.
Volatile (RAM)
Previously Confirmed
Indicates that the fault has entered the Confirmed state at least once since faults were cleared.
NonVolatile (EEPROM)
Failed Since Clear
Indicates that the fault has entered the Failing state at least once since faults were cleared
NonVolatile (EEPROM)
Failed Last Drive Cycle
Indicates that fault entered the Failing state at least once during the last drive cycle.
NonVolatile (EEPROM)
Fault State Set/Clear Conditions
State
Type
Description
Suspected
Input to fault definition block is true.
Input to fault definition block is false.
Failing
X/Y counter exceeds X limit true inputs in the last Y limit inputs
X/Y Counter completes Y limit with less than X limit true inputs
Pending
Fault enters the Failing state.
Drive cycle completed AND fault is not in Failed This Drive Cycle
Confirmed
Fault enters the Failing state AND fault is Pending AND fault is not in Failed This Drive Cycle State
40 warm up drive cycles completed with Fault in Test Completed This Drive Cycle state AND NOT in Failed This Drive Cycle state. This count will be reset if the fault enters the Failing state
Permanent
Fault is set as a permanent fault AND enters the Confirmed state
3 drive cycles completed with Fault in Test Completed This Drive Cycle state AND NOT in Failed This Drive Cycle state. This count will be reset if the fault enters the Failing state
MIL
Fault is set as emissions related AND enters the Confirmed state
3 drive cycles completed with Fault in Test Completed This Drive Cycle state AND NOT in Failed This Drive Cycle state. This count will be reset if the fault enters the Failing state
Ready
X/Y counter completes Y limit inputs.
Controller reboot
Test Compleded This Drive Cycle
X/Y counter completes Y limit inputs
Drive cycle completed
Failed This Drive Cycle
Fault enters the Failing state
Drive cycle completed
Previously Confirmed
Fault enters the Confirmed state
Faults cleared
Failed Since Clear
Fault enters the Failed state
Faults cleared
Failed Last Drive Cycle
Drive cycle completed AND fault in Failed This Drive Cycle
Drive cycle completed AND NOT fault in Failed This Drive Cycle
Additional flexibility in the clearing of fault state can be achieved by setting the clearing method for a fault to User Defined. When the clearing method is set to User Defined the following state must be cleared by the user: Pending, MIL, Permanent, Confirmed. Executing the fault clear block on all faults or a specific fault will clear all the states.
Inputs
Input
Type
Description
Outputs
Output
Type
Description
Parameters
Parameter
Type
Description
Fault Map Tool
Launches the fault map tool used to map fault actions and triggers to faults.
Type
Chooses the type of fault manager.
Calibratable Fault Map
This enables the fault action and triggers maps to be calibrated from the calibration tool.
Min Fault Actions / Fault
Number
Controls the minimum number of fault actions allowed per fault.
Min Fault Triggers / Fault
Number
Controls the minimum number of fault triggers allowed per fault.
Access Level
Sets the access level of this item in the calibration tool.
Function
String
Sets the location where this item appears in the calibration tool. Use raptor_xcp_function(gcb) to create a function based on the variables location in the model.
