Raptor:Standard Fault Manager: Difference between revisions

From NewEagleWiki
Jump to navigation Jump to search
No edit summary
 
Line 8: Line 8:
<p>This block causes the fault manager to be generated. The fault manager must exist only once in the model to enable the fault blocks to be used. There are different types of fault manager which contain different features and options. Currently supported types are Standard and OBD Fault Manager.</p>
<p>This block causes the fault manager to be generated. The fault manager must exist only once in the model to enable the fault blocks to be used. There are different types of fault manager which contain different features and options. Currently supported types are Standard and OBD Fault Manager.</p>


== Fault Operation ==
<p>Each fault can have one of the following states.</p>
{| class="wikitable" style="width:75%;"
|-
! scope="col" style="width: 15%;"|???
! scope="col" style="width: 15%;"|???
! scope="col" style="width: 70%;"|???
|}
<p>An X/Y counter is used to filter the input and avoid false trips. The X/Y counter monitors status of the fault and when it has been true for x of the last y executions of the fault def block the fault becomes active. Setting the x and y limit both to 1 disables the X/Y counter. When the fault is cleared it returns back to the Not Occurred state from any state, but the X and Y counters will retain their value.</p>
<p>Two variations on the standard fault state progression are the persistent and sticky fault types. A fault which is persistent will use Non Volatile memory to store its state so that the state will be remembered during a key cycle. A sticky fault is one which will only leave the Active state when cleared regardless of the value of the X/Y counter.</p>
== Inputs ==
{| class="wikitable" style="width:75%;"
|-
! scope="col" style="width: 15%;"|Input
! scope="col" style="width: 15%;"|Type
! scope="col" style="width: 70%;"|Description
|}
== Outputs ==
{| class="wikitable" style="width:75%;"
|-
! scope="col" style="width: 15%;"|Output
! scope="col" style="width: 15%;"|Type
! scope="col" style="width: 70%;"|Description
|}


== Parameters ==
== Parameters ==

Latest revision as of 15:16, 14 September 2023

Return to the main Raptor page

Return to Faults page

Raptor™ Standard Fault Manager

Description

This block causes the fault manager to be generated. The fault manager must exist only once in the model to enable the fault blocks to be used. There are different types of fault manager which contain different features and options. Currently supported types are Standard and OBD Fault Manager.


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.
Retrieved from "https://wiki.neweagle.net//index.php?title=Raptor:Standard_Fault_Manager&oldid=34127"