MotoHawk:Blocks:Fault Manager Definition

From MotoHawk
Jump to navigationJump to search

Fault Manager Definition

This MotoHawk™ block defines the Fault Manager, and one must exist in each model that contains Fault blocks.

Note: The Classic Fault Manager can define a limited number of faults. The size depends on the settings in the Fault Manager, but is typically around 300 faults. For systems with a large number of faults, consider using the OBD Fault Manager (FM).

Block ID

motohawk_fault_manager

Library

MotoHawk_lib/Fault Management Blocks

Description

Fault Manager Definition.PNG

Code is generated to cache the faults in a memory-efficient manner, and an interface is generated in MotoTune to display and configure the faults.

The X/Y Storage Type affects how large the X out of Y counts may be, but larger values increase total RAM and FLASH usage.

Block Parameters

Parameter Field Values Comments/Description
Storage Define type of storage for fault setup information
Flash Use Flash memory (volatile) in module
EEPROM Use EEPROM memory (nonvolatile) in module
Read Access Level 1-4 Sets security level 1 lowest, 4 highest, for user access to read fault value
Write Access Level 1-4 Sets security level 1 lowest, 4 highest, for user access to write fault value
Clear Access Level 1-4 Sets security level 1 lowest, 4 highest, for user access to clear fault
X/Y Data Type uint8, uint16, uint32 Select data type for X out of Y counts.
MotoTune Group String Alpha-numeric text Determines Folder name and hierarchy as displayed in MotoTune. Use "|" character between folder names to delineate subfolder structure