0% found this document useful (0 votes)
57 views43 pages

Core2 Cagt CP

This document contains definitions for several services related to collecting and managing diagnostic data. It includes services for collecting data, configuring data collection, retrieving fault counts, clearing faults, and accessing recorded diagnostic data. The services are designed to work with an embedded data collector to monitor systems, record issues, and provide diagnostic information.

Uploaded by

Mladen Stijepic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
57 views43 pages

Core2 Cagt CP

This document contains definitions for several services related to collecting and managing diagnostic data. It includes services for collecting data, configuring data collection, retrieving fault counts, clearing faults, and accessing recorded diagnostic data. The services are designed to work with an embedded data collector to monitor systems, record issues, and provide diagnostic information.

Uploaded by

Mladen Stijepic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 43

HD-X07-C-C18.00.00.08-ISX-8.0.0.

18_00
ID : 27620
ECM Type : CM87X

CAGT - Base Cummins Proprietary18.00.00.06


Service
CAGT_collect_data
Syntax :
void CAGT_collect_data (void)
Description :
Triggers the sampling of data collector data and runs data collection logic. Engineering Data Collector Execution
Manager
Rate : 1000

Offset : 3

Order : 1000

Schedule Type : Real-time exec

Obsolete : No

Check outstatus :IN by Joseph Gahimer on Nov 20, 2001


CAGT_critical_init
Syntax :
void CAGT_critical_init (void)
Description :
Calls XMGR_register to register the data collector with the Execution Manager. This is done so that data can be
collected at power up when the data collector function is enabled. Engineering Data Collector Execution Manager
Rate :

Offset : 0

Order : 1000

Schedule Type : Critical initialization

Obsolete : No

Check outstatus :IN by Joseph Gahimer on Nov 20, 2001


CAGT_diagnostics
Syntax :
void CAGT_diagnostics(void)
Description :
This service is called by the execution manager. It determines when errors have persisted long enough to declare the
presence of a Cummins Fault Code. It also creates data, from data provided to it from the communication manager in
the format required by the snapshot table, and fault count table.
Rate : 200

Offset : 2

Order : 999

Schedule Type : Real-time exec

Obsolete : No

Check outstatus :IN by Magdalena Purnama on Oct 23, 2003


EDC_cfgKeyOnMode
Syntax :
void EDC_cfgKeyOnMode()
Description :
This service configures the keyon mode of internal data collector.
Rate : 1

Offset : 0
Order : 1000

Schedule Type : Staged initialization

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_collectData
Syntax :
void EDC_collectData( void )
Description :

Rate : 1

Offset : 0

Order : 0

Schedule Type : Dynamic exec/interrupt

Obsolete : No

Check outstatus :IN by Duane Guingrich on Apr 25, 2003


EDC_config
Syntax :
void EDC_config( const uint8 collector_multiple, const uint8 collector_interrupt_schedule, const uint8
collector_mode, const ptr_edc_items_list_t collector_item_list_array, const uint16 collector_item_list_array_length,
uint16 *record_length, uint32 *status )
Description :
Tool operation CLIP_CfgDataCollector() uses this service to configure the Data Collector2. Service checks the validity
of input arguments, viz: collector_interrupt_schedule, collector_mode, collector_item_list_array. If all the input
arguments are valid, registers the EDC_collectData() service with the execution manger, sets the status to
OPERATION_SUCCESS(0) and returns. If any of the input argument is invalid, service sets the status to a non-zero code
and returns.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_getCapabilities
Syntax :
void EDC_getCapabilities( uint16 *collector_memory_size, uint16 *base_frame_rate, uint16 *clock_interrupt_rate )
Description :
This returns the Data Collector buffer size and the fastest frame and clock update rates that the ECM supports.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Duane Guingrich on Mar 14, 2003


EDC_getDcLogConfiguration
Syntax :
void EDC_getDcLogConfiguration( ptr_ptr_edc_items_list_t collector_item_list_array_ptr_ptr, uint8* collector_multiple,
uint8* collector_interrupt_schedule, uint8* collector_mode, uint16* collector_item_list_array_length, boolean*
getconfig_status )
Description :
Tool operation CLIP_GetDcLogConfiguration() calls this service to retrive the configuration information, viz: collector
mode, interrupt schedule, item list and number of data variables configured. If Data Collector2 had not been configured
successfully, service sets getconfig_status to a non zero value. Otherwise, sets getconfig_status to zero.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_getFullRecordIndex
Syntax :
void EDC_getFullRecordIndex( uint16 start_record_number, uint16 stop_record_number, uint16* start_index, uint16*
data_length, uint16* trigger_offset, uint32* result_status, boolean* endbuff_flag )
Description :
Tool operation CLIP_GetDcLog() calls this service to know the details of the data to be sent to tool. The service sets
the following output arguments: start_index: The index in the Data Collector buffer corresponding to the index of the
start_record_number. data_length: Length of data collected from start_record_number to stop_record_number.
trigger_offset: Size of stored records in 'GTIS_Collector_Buffer' when the T_GTIS_Collector_Trigger transitioned from
_RUN to _STOP. endbuff_flag: Flag indicating the end of buffer has been reached or not when the collection trigger
occurred.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_getNextBAMRecordIndex
Syntax :
uint16 EDC_getNextBAMRecordIndex( void )
Description :
This returns the index in Data Collector buffer where the next record of recorded data starts. This also increments the
start index so that the next time this service is called, the index of the following record will be returned.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Duane Guingrich on Mar 31, 2003


EDC_releaseBAMRecord
Syntax :
uint16 EDC_releaseBAMRecord( uint16 record_mode )
Description :
This releases the data space at the start of the data collector buffer so that it can be reused to store data. The
record_mode can be the following values: EDC_NEXT_RECORD - This will release the record at the start of the
data collector buffer so that it can be reused. EDC_TERMINATE_BAM - This will turn off BAM processing so that no
more data will be collected and no more data will be BAM transmitted
until the collector trigger transitions from _STOP to _RUN.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Duane Guingrich on Mar 31, 2003


EDC_setDcTrigger
Syntax :
void EDC_setDcTrigger(uint8 collector_trigger, uint8* status)
Description :
Tool operation CLIP_SetDCTrigger() uses this service. If the collector_trigger is either TIS_RUN or TIS_STOP,
T_GTIS_Collector_Trigger will be set to collector_trigger, status is set to 0 and service returns. Otherwise, status
is set to 1 and service returns.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_store_data_to_buffer
Syntax :
void EDC_store_data_to_buffer( uint8 *buffer, uint16 *buffer_index, uint16 buffer_size, uint32 **data_address_array,
uint16 *data_size_array, uint16 length_of_arrays )
Description :
This is the hand-coded service of the EDC Data Collector that is used to store the array of configured public ID
addresses to the GTIS_Collector_Buffer.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Duane Guingrich on Mar 14, 2003


FH_clearfaults
Syntax :
uint16 FH_clearfaults( uint16 mask, uint16 only_error_index )
Description :
Can clear faults by status mask, or by specific error_index. For example, the following would clear all faults, active
or inactive. Return values are 0x0000 - request completed successfully 0x8001 - did not clear inactive
faults 0x8002 - did not clear active faults 0x8003 - did not clear any faults (both active and inactive)
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Dec 19, 2001


FH_getFaultCount
Syntax :
uint32 FH_getFaultCount( uint32 fault_mask )
Description :
This service returns the number of faults that satisfy the fault_mask. If Bit 0 of the fault_mask is a '1', the active
faults should be included in the count. If Bit 1 of the fault_mask is a '1', the previously active faults should be
included in the count.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Oct 24, 2002


FH_getNextFault
Syntax :
boolean FH_getNextFault( uint32 *p_error_index, uint32 *p_count, boolean *p_active )
Description :
The FH_xxxx functions use a "cursor" to iterate through a list of faults. This service sets the "cursor" to the
beginning of the fault list. It should be called first, then FH_getNextFault() should be called repetitively to get
the faults one by one. The FH_getNextFault() service returns information about the next fault in the list (i.e. the
next fault which was dictated by the fault_mask when FH_resetFaultCursor() was called.) See examples & tips.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Oct 24, 2002


FH_getNextSnapshotInfo
Syntax :
boolean FH_getNextSnapshotInfo( uint32 *p_public_data_id, uint32 *p_offset )
Description :
The FH_rxx() functions use a "cursor" to iterate through the list of public data that is stored in snapshot records.
The FH_getNextSnapshotInfo() retrieves the ID and offset of the next Public Data item stored in snapshot records.
This is to be used in combination with FH_resetSnapshotInfoCursor(). See the "Examples and tips".
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Oct 24, 2002


FH_getSnapshotPtr
Syntax :
void FH_getSnapshotPtr( uint16 error_index, uint32 *first_snapshot_start_addr, uint32 *last_snapshot_start_addr )
Description :
Returns the start address of the first and last snapshots associated with the specified error_index.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Oct 24, 2002


FH_initialize
Syntax :
void FH_initialize( void )
Description :
Initializes the fault handling interfaces -- that is, the services whose names start with FH_xxxx().
Rate :

Offset : 0

Order : 1

Schedule Type : Critical initialization

Obsolete : No

Check outstatus :IN by Jon Broadwell on Jun 14, 2004


FH_resetFaultCursor
Syntax :
boolean FH_resetFaultCursor( uint32 fault_mask )
Description :
The FH_xxxx functions use a "cursor" to iterate through a list of faults. This service sets the "cursor" to the
beginning of the fault list. It should be called first, then FH_getNextFault() should be called repetitively to get
the faults one by one. See examples & tips. Returns TRUE if successfully reset.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Oct 24, 2002


FH_resetSnapshotInfoCursor
Syntax :
void FH_resetSnapshotInfoCursor(void)
Description :
The FH_rxx() functions use a "cursor" to iterate through the list of public data that is stored in snapshot records.
The FH_resetSnapshotInfoCursor() service moves a "cursor" to the first public data ID in the snapshot ID table. This
is to be used in combination with FH_getNextSnapshotInfo(). See the "Examples and tips".
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Keith Musser on Oct 24, 2002

Service Used
CLIP_UpdateDCInfo
Syntax :
void CLIP_UpdateDCInfo( uint8 mode, boolean status, boolean getdclog_inprogress, uint16 single_record_size, uint16
total_buffer_size)
Description :
This service updates the EDC2 configuration information. This service is called from CAGT CP Base's critical
initialization.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


CMGR_getPublicDataAddress
Syntax :
void* CMGR_getPublicDataAddress( uint32 id, uint16 *size)
Description :
Returns the address and the size of Public Data "id". Returns NULL and sets *size=0 if the ID is not found.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Srujan Kusumba on Aug 31, 2005


CMGR_getPublicDataByIndex
Syntax :
int16 CMGR_getPublicDataByIndex(uint32 data_index, void* data)
Description :
Use to get any public data in the system by index. The length must be known to the caller, who must provide the correct
storage for the data, which is copied via a data pointer. Return values 0x0000 ( 0 ) - DATA_VALID 0xFFFF ( -1 ) -
DATA_NOT_AVAILABLE = index is greater than size of table The data confidence level, where applicable to a public
data item, must be fetched separately with CMGR_getPublicDataStatus.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Steve Ferree on Jul 01, 2002


CMGR_getPublicDataByIndexSim
Syntax :
void CMGR_getPublicDataByIndexSim(uint32 data_index, int16* status, void* data)
Description :
This service allows both pure simulation and automatic code generation Use to get any public data in the system by
index. The length must be known to the caller, who must provide the correct storage for the data, which is copied via a
data pointer. Return values 0x0000 ( 0 ) - DATA_VALID 0xFFFF ( -1 ) - DATA_NOT_AVAILABLE = index is greater than
size of table The data confidence level, where applicable to a public data item, must be fetched separately with
CMGR_getPublicDataStatus.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Mark Pyclik on Feb 23, 2005


CMGR_getPublicDataIndex
Syntax :
int16 CMGR_getPublicDataIndex(uint32 public_data_id, uint32* data_index)
Description :
Use to get the public data id table index of any public data in the system. Return values 0x0000 ( 0 ) - value
found in table 0xFFFF ( -1 ) - data id is not in the table
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Steve Ferree on Jul 01, 2002


CMGR_get_error
Syntax :
boolean CMGR_get_error(uint16 error_index)
Description :
Service to return the error status for a specific system error, referenced by index. (First call CMGR_get_error_index
with the Error ID to get the index.) System returns the error status through the return value, error_set. Valid
error_set values: 0 - indicates the error is not set (FALSE) 1 - indicates that the error is set (TRUE)
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Fred Mehdian on Sep 30, 2005


CMGR_get_public_data
Syntax :
int16 CMGR_get_public_data(uint32 public_data_id, void* data)
Description :
Use to get any public data in the system. The length must be known to the caller, who must provide the correct storage
for the data, which is copied via a data pointer. Return values 0x0000 ( 0 ) - DATA_VALID 0xFFFF ( -1 ) -
DATA_NOT_AVAILABLE
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : Yes

Check outstatus :IN by Jim Dager on Jun 13, 2003


CMGR_get_public_data_size
Syntax :
void CMGR_get_public_data_size(uint32 public_data_id, uint16* data_size)
Description :
Given the public data ID (previously known as Name Table Name), the data length, in bytes, is returned. If data is
requested that is not in the system, the returned length will be zero. This service is only intended to be used to get
data sizes that are not specified by the ICD data base. This includes elements that vary in size from build to build
or are declared at time of build.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Joseph Gahimer on Nov 20, 2001


CMGR_ReadMemory
Syntax :
boolean CMGR_ReadMemory(uint8* destination, uint32 virtual_source, uint32 length)
Description :
This function will copy data from virtual source to destination. Right now, virtual source will simply be recast to
uint8*. Later, it may have a more elaborate virtual memory translation scheme. The derived pointer is tested with
VerifyAddress to make sure the source is somewhere that can be legitimately read.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Jim Dager on Jan 06, 2003


CMGR_translateAddress
Syntax :
void CMGR_translateAddress(uint8* in_address, uint32 length, uint8** out_address)
Description :
Translates virtual/rom addresses of eeprom and imaged calibration data to the actual data address in RAM.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Steve Ferree on Jul 11, 2003


EDC_cfgKeyOnMode
Syntax :
void EDC_cfgKeyOnMode()
Description :
This service configures the keyon mode of internal data collector.
Rate : 1

Offset : 0

Order : 1000

Schedule Type : Staged initialization

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_collectData
Syntax :
void EDC_collectData( void )
Description :

Rate : 1

Offset : 0

Order : 0

Schedule Type : Dynamic exec/interrupt

Obsolete : No

Check outstatus :IN by Duane Guingrich on Apr 25, 2003


EDC_config
Syntax :
void EDC_config( const uint8 collector_multiple, const uint8 collector_interrupt_schedule, const uint8
collector_mode, const ptr_edc_items_list_t collector_item_list_array, const uint16 collector_item_list_array_length,
uint16 *record_length, uint32 *status )
Description :
Tool operation CLIP_CfgDataCollector() uses this service to configure the Data Collector2. Service checks the validity
of input arguments, viz: collector_interrupt_schedule, collector_mode, collector_item_list_array. If all the input
arguments are valid, registers the EDC_collectData() service with the execution manger, sets the status to
OPERATION_SUCCESS(0) and returns. If any of the input argument is invalid, service sets the status to a non-zero code
and returns.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Chandan Nene on Mar 29, 2006


EDC_store_data_to_buffer
Syntax :
void EDC_store_data_to_buffer( uint8 *buffer, uint16 *buffer_index, uint16 buffer_size, uint32 **data_address_array,
uint16 *data_size_array, uint16 length_of_arrays )
Description :
This is the hand-coded service of the EDC Data Collector that is used to store the array of configured public ID
addresses to the GTIS_Collector_Buffer.
Rate : 0

Offset : 0

Order : 0

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Duane Guingrich on Mar 14, 2003


esm_clear_mux_fault_log
Syntax :
void esm_clear_mux_fault_log( )
Description :
Clear the timeout or configuration fault log table if there is no active corresponding multiplexing fault
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Joey Wu on Jan 05, 2004


OS_COPY_2_BYTES
Syntax :
#define OS_COPY_2_BYTES(_to,_from) {*(((unsigned char*)(_to))) = *(((unsigned char*)(_from))); *(((unsigned
char*)(_to)) + 1 ) = *(((unsigned char*)(_from)) + 1); }
Description :

Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Jon Broadwell on Oct 22, 2004


OS_COPY_4_BYTES
Syntax :
#define OS_COPY_4_BYTES(_to,_from) {*(_to) = *(_from); }
Description :

Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Jon Broadwell on Oct 22, 2004


XMGR_disable
Syntax :
uint16 XMGR_disable(task_pointer_t function)
Description :
This service is called on demand from anywhere in the system that requires the disabling of a task. The function
address is passed as the task identifier. The return value is 0 if the task is not found in the task list, 1 if it is
found and disabled.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Suraj Barkale on Mar 03, 2006


XMGR_register
Syntax :
uint16 XMGR_register(uint16 event, uint16 occurrence, uint16 offset, uint32 function)
Description :
Service to update execution parameters of an item in the task list. This only works on tasks that are listed in the
system as a result of schedule selection in the ICD database. Any attempt to register functions which were not
specified as scheduled will get an error status returned. The return value is 1 for functions which are found and
updated, 0 for functions not found or if an invalid event is specified.
Rate :

Offset : 0

Order : 1000

Schedule Type : Not scheduled

Obsolete : No

Check outstatus :IN by Joseph Gahimer on Nov 20, 2001

Data
Buffer_End
Data Type : uint32

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Pointer to the last byte of the GTIS_Data_Collector_Buffer. This value is suppose to be initialized at powerup to the
proper address. This will have to be added to Core II during phase 3.
Struct Default :

Chectout Status : IN by Kristina Gambrel on May 26, 2006

Obsolete : No
Buffer_Start
Data Type : uint32

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Pointer to the first byte of the GTIS_Data_Collector_Buffer. This value is suppose to be initialized at powerup to the
proper address. This will have to be added to Core II during phase 3.
Struct Default :

Chectout Status : IN by Kristina Gambrel on May 26, 2006

Obsolete : No
Cagtb_Obd_Fault_Stat_Ptr
Data Type : uint8*
Unit : None

Minimum Value : 0

Maximum Value : 4294967296

Accuracy :

BNumber : 32

Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This variable is pointer to OBD_Fault_Status_Table array. OBD_Fault_Status_Table is provided by CAGT OBD Base
component, which is optional component in build. So to avoid linker error OBD_Fault_Status_Table is accessed by Pointer
instead of accessing directly. This variable is data used by CAGT OBD Base and in critical init of CAGT OBD Base, it
will pass the address of OBD_Fault_Status_Table to Cagt_Obd_Fault_Stat_Ptr.
Struct Default :

Chectout Status : IN by Nishant Tholiya on May 03, 2005

Obsolete : No
CAGT_Block_Fault_Codes
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 2

Structure Array Size based on : 2

Description :
Array of fault codes to be blocked. Fault codes can be found in CES14602 specification. Size of this array and hence
the maximum number of faults that can be blocked, can be changed by setting the value of CAGT_Faults_To_Block via
"Configurable data" tab in a given build configuration. Build script limits the value of CAGT_Faults_To_Block to 30.
In this array, if a fault code is listed after a zero entry, that fault code will not be blocked. E.g Lets say
CAGT_Faults_To_Block has been over-ridden to 5 via "Configurable data" tab in a given build configuration. Now if,
CAGT_Block_Fault_Codes[1] =valid FC1, CAGT_Block_Fault_Codes[2]=valid FC2, CAGT_Block_Fault_Codes[3]=0,
CAGT_Block_Fault_Codes[4]=valid FC3, CAGT_Block_Fault_Codes[5]=valid FC4; In above case, only FC1 and FC2 will be
considered for fault blocking.
Struct Default :

Chectout Status : IN by Chandan Nene on Apr 18, 2006

Obsolete : No
CAGT_CFTR_ErrorIndexTable_End
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1
BNumber : 16

Max Latency :

Simple Default : 65535

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
This is a data indicator for the end of CFTR_ErrorIndexTable[ ]. It means there is no more valid error_index exists in
the table after CFTR_ErrorIndexTable[n] = CAGT_CFTR_ErrorIndexTable_End; Stop searching the table at this index.
Struct Default :

Chectout Status : IN by Fred Mehdian on Feb 10, 2006

Obsolete : No
CAGT_EdcLog_Num_Records
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Number of records that are collected via Data Collector2 after the data collection has been started.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
CAGT_Edc_Interrupt_Schedule
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Interrupt method with which Data Collector2 was configured for collecting data. Valid values are _CLOCK_INTERRUPT,
_ENGINE_SPEED_INTERRUPT, _ROAD_SPEED_INTERRUPT, _TURBO_SPEED_INTERRUPT and _FRAME_INTERRUPT.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006


Obsolete : No
CAGT_Edc_Item_List_Array
Data Type : edc_items_list_t[ ]

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber :

Max Latency :

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 120

Structure Array Size based on : 120

Description :
Each entry in this list contains the following: 1. item_id_or_addr: Public data ID or address of the variable to be
recorded via Data Collector2. 2. item_access_method: Indicates the type of the second member. If TRUE, the second
member is a public data ID, otherwise it is an address. 3. item_size: If second field is an address then this field
indicates the size of the data to be recorded via Data Collector2. Otherwise it is invalid.
Struct Default :

Chectout Status : IN by Jason Zhang on Mar 19, 2007

Obsolete : No
CAGT_Edc_Item_List_Array_Length
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This is the number of valid entries in the CAGT_Edc_Item_List_Array[]. This number indicates the number of data
variables configured to be recorded via Data Collector2.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
CAGT_Edc_KeyOn_Configured
Data Type : boolean

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy : 1

BNumber : 8

Max Latency : 0
Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
If Data Collector2 was configured successfully with keyon mode, then this parameter is set to 1 else it is set to 0.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
CAGT_Edc_Mode
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
The collector mode configured for collecting data via Data Collector2. Valid values are _BAM_TRANSMIT_TRIGGER,
_PRE_TRIGGER, _MID_TRIGGER,_POST_TRIGGER and _KEYON_TRIGGER.
Struct Default :

Chectout Status : IN by Chandan Nene on Jun 01, 2006

Obsolete : No
CAGT_Edc_Multiple
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 1

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
The number of occurrences of the collector interrupt to skip each time before recording the set of data via Data
Collector2.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
CAGT_Edc_VoidPtr
Data Type : void_ptr
Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy : 1

BNumber :

Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Dummy variable so that void_ptr gets pulled into the icd_types file for this component. Do not use this variable from
other components.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
CAGT_Faults_To_Block
Data Type : uint16

Unit : None

Minimum Value : 1

Maximum Value : 30

Accuracy : 1

BNumber :

Max Latency :

Simple Default : 1

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
Maximum number of faults that can be blocked. Size of CAGT_Block_Fault_Codes[ ] and hence the maximum number of faults
that can be blocked, can be changed by setting the value of CAGT_Faults_To_Block via "Configurable data" tab in a given
build configuration. Build script limits the value of CAGT_Faults_To_Block to 30.
Struct Default :

Chectout Status : IN by Chandan Nene on Apr 18, 2006

Obsolete : No
CAGT_FC_Blk_Err_Index
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default :

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :


Description :
Bitmap array storing the presence of error index related to fault code in CAGT_Block_Fault_Codes[]. If
(error_index+16)th bit from the least significant bit of CAGT_FC_Blk_Err_Index[0] is set, corresponding fault code is
to be blocked.
Struct Default :

Chectout Status : IN by Chandan Nene on Dec 01, 2005

Obsolete : No
CAGT_Max_Edc_Capacity
Data Type : uint8

Unit : None

Minimum Value : 1

Maximum Value : 255

Accuracy : 1

BNumber : 8

Max Latency :

Simple Default : 50

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
Maximum number of parameters can be logged for the IDL. The default is 50.
Struct Default :

Chectout Status : IN by Jason Zhang on Oct 26, 2006

Obsolete : No
CFTR_Fault_Status_Mismatch_Ctr
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This indicates that how many times there was mismatch in the CFTR_Fault_Status_Table.Every error in the
CFTR_ErrorIndexTable is searched in the ECM_Active_Error_Index and ECM_InActive_Error_Index. If the error is found in
the ECM_Active_Error_Index then the status for the error in the CFTR_Fault_Status_Table should be ACTIVE. If the status
for the error in the CFTR_Fault_Status_Table is not ACTIVE then the count is incremented and the errors removed from
the tables. Similarly for an error in ECM_InActive_Error_Index if the corresponding status in not INACTIVE in the
CFTR_Fault_Status_Table the count is incremented and the errors removed from the tables. This variable is just for
Engineering Testing only.
Struct Default :

Chectout Status : IN by Ashwin Patwekar on Jul 26, 2005

Obsolete : No
CFTR_Table_Inactive_Mismatch_Ctr
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This indicates that how many times there was mismatch in ECM_Inactive_Error_Index and CFTR_ErrorIndexTable. This
variable is just for Engineering Testing only.
Struct Default :

Chectout Status : IN by Ashwin Patwekar on Jul 26, 2005

Obsolete : No
CFTR_Table_Mismatch_Counter
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This indicates that how many times there was mismatch in ECM_Active_Error_Index and CFTR_ErrorIndexTable. This variable
is just for Engineering Testing only.
Struct Default :

Chectout Status : IN by Nishant Tholiya on Feb 14, 2005

Obsolete : No
Collector_Status
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 2

Accuracy :

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable


No of Array Elements : 0

Structure Array Size based on : 0

Description :
Status of the data collector function from Core I. This is added here to maintain backward compatibility. It must be
a uint16 at name table 0x36. This functionality will be added to Core II during phase 3. 0 = not collecting 1 =
collecting 2 = stopped collecting; buffer full
Struct Default :

Chectout Status : IN by Kristina Gambrel on May 26, 2006

Obsolete : No
Collector_Table_Address
Data Type : uint32

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Pointer to the first element of the Collector ID Table. The array pointed to by Collector_Table_Address shall contain
the addresses of the parameters identified in the T_EDC_Collector_ID_Table. When the data collector runs this is these
are the addresses from which the data is obtained for each sample. For example: If two - four byte parameters are
to be collected there would be eight addresses in the array pointed to by Collector_Table_Address.
Struct Default :

Chectout Status : IN by Kristina Gambrel on May 26, 2006

Obsolete : No
C_Collector_Interrupt_Options
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency :

Simple Default :

Software Parameter Type : Calibratible

No of Array Elements : 12

Structure Array Size based on : 12

Description :
The interrupt options that are available to use by the Data Collector. The data collection is done based on the
options included in this array. If for a system a particular option is not valid and needs to be removed then all the
entries in the table need to be moved 1 place up and an entry of 0xff needs to be added at the end. E.g. On a system
which does not have _ROAD_SPEED_INTERRUPT the entry needs to be removed from the table during calibration to disable
data collection based on _ROAD_SPEED_INTERRUPT. If a system supports data collection on some other events it can be
added to the list by replacing the last empty entry. The empty entries are marked as 0xff in the array.
Struct Default :
Chectout Status : IN by Chandan Nene on Jun 01, 2006

Obsolete : No
C_DIR_Fault_Countdown_Period
Data Type : fault_countdown_t

Unit : s

Minimum Value : 0

Maximum Value : 2147483648

Accuracy :

BNumber : 31

Max Latency : 0

Simple Default :

Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
This parameter is a structure containing 6 time intervals. Two intervals are used for each of trhree countdown modes.
The first entry identifies the time that must elapse before fault countdown may begin for mode 1,the second entry is
used for mode 2, and the third is used for mode 3. the fourth entry is the coundown rate after the initial coundown
time has expired for mode 1. The fifth entrie is used for mode 2. The sixth entrie is used for mode 3. The
definition of its type is: typedef { EB28 elapsed_time_mode_1; /* min=0. , max= 500000 seconds
*/ EB28 elapsed_time_mode_2; /* min=0. , max= 500000 seconds */ EB28 elapsed_time_mode_3;
/* min=0. , max= 500000 seconds */ EB28 countdown_rate_mode_1; /* min=0. , max= 500000
seconds/count */ EB28 countdown_rate_mode_2; /* min=0. , max= 500000 seconds/count */ EB28
countdown_rate_mode_3; /* min=0. , max= 500000 seconds/count */ } fault_countdown_t;
Struct Default :

Chectout Status : IN by Fred Mehdian on Aug 31, 2006

Obsolete : No
C_EDC_Collector2UserSelectable
Data Type : boolean

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 1

Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
This parameter indicates whether the Data Collector2 feature is available for selection by the tool.
Struct Default :

Chectout Status : IN by Chandan Nene on May 04, 2006

Obsolete : No
C_EDC_Collector_Mode_Options
Data Type : uint8[ ]

Unit : None
Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber :

Max Latency :

Simple Default :

Software Parameter Type : Calibratible

No of Array Elements : 5

Structure Array Size based on : 5

Description :
The mode options those are available for the Data collector2. The data collection is done based on the options included
in this array. If for a system a particular option is not valid and needs to be removed then all the entries in the
table need to be moved 1 place up and an entry of 0xff needs to be added at the end. E.g. On a system which does not
have _PRE_TRIGGER the entry needs to be removed from the table during calibration to disable data collection based on
_PRE_TRIGGER. If a system supports data collection on some other mode it can be added to the list by replacing the last
empty entry. The empty entries are marked as 0xff in the array.
Struct Default :

Chectout Status : IN by Chandan Nene on Jun 01, 2006

Obsolete : No
ECM_Active_Error_Index
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 31

Structure Array Size based on : 31

Description :
Parameter or table that stores the active error_index retrieved from CFTR_ErrorIndexTable. It only stores one of the
error_index of the errors, if multiple errors that mapped to the same service fault code happens. 0 indicates the last
entry of the table This table is closely related to ECM_Active_Fault_Count. It is indexed as 1 to 1 to this table.
Example: ECM_Active_Error_Index[0] = 12 ECM_Active_Fault_Count[0] contains the fault_count of
ECM_Active_Error_Index[0]. It is not counting on the error, but it is counting on the fault code which is mapped from
CFTR_Available_Fault_Table[ECM_Active_Error_Index[0]] Maximum of 31 error_index.
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
ECM_Active_Fault_Count
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16
Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 31

Structure Array Size based on : 31

Description :
Parameter or table that stores fault_count information of the currently active fault_code. The fault_count gets
incremented when there is a transition from inactive service fault (not error) to active service fault 0 indicates the
last entry of the table This table is closely related to ECM_Active_Error_Index. It is indexed as 1 to 1 to this
table. Example: ECM_Active_Error_Index[0] = 12 ECM_Active_Fault_Count[0] contains the fault_count of
ECM_Active_Error_Index[0]. It is not counting on the error, but it is counting on the fault code which is mapped from
CFTR_Available_Fault_Table[ECM_Active_Error_Index[0]] Maximum of 31 error_index.
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
ECM_Active_Index_Count
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 31

Structure Array Size based on : 31

Description :
Parameter or table that stores number of active or inactive errors with the same fault code, in which either one of
these error are currently active
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
ECM_Inactive_Error_Index
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 31

Structure Array Size based on : 31

Description :
Parameter or table that stores the inactive error_index retrieved from CFTR_ErrorIndexTable. It only stores one of the
error_index of the errors, if multiple errors that mapped to the same service fault code happens. 0 indicates the last
entry of the table This table is closely related to ECM_Inactive_Fault_Count. It is indexed as 1 to 1 to this table.
Example: ECM_Inactive_Error_Index[0] = 12 ECM_Inactive_Fault_Count[0] contains the fault_count of
ECM_Inactive_Error_Index[0]. It is not counting on the error, but it is counting on the fault code which is mapped from
CFTR_Available_Fault_Table[ECM_Inactive_Error_Index[0]] Maximum of 31 error_index.
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
ECM_Inactive_Fault_Count
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 31

Structure Array Size based on : 31

Description :
Parameter or table that stores fault_count information of the currently inactive fault_code. The fault_count does not
get incremented when there is a transition from active service fault (not error) to inactive service fault. It also
does not get decremented when the process countdown 0 indicates the last entry of the table This table is closely
related to ECM_Inactive_Error_Index. It is indexed as 1 to 1 to this table. Example: ECM_Inactive_Error_Index[0] = 12
ECM_Inactive_Fault_Count[0] contains the fault_count of ECM_Inactive_Error_Index[0]. It is not counting on the error,
but it is counting on the fault code which is mapped from CFTR_Available_Fault_Table[ECM_Inactive_Error_Index[0]]
Maximum of 31 error_index.
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
ECM_Inactive_Index_Count
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements : 31

Structure Array Size based on : 31

Description :
Parameter or table that stores number of inactive errors with the same fault code, in which all of these error are
currently inactive
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
EDC_baseFrameRate
Data Type : uint16

Unit : None

Minimum Value : 1

Maximum Value : 100

Accuracy :

BNumber : 16

Max Latency :

Simple Default : 5

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
This is the smallest frame rate supported by the ECM. It is used for configuring the Electronic Data Collector.
Struct Default :

Chectout Status : IN by Duane Guingrich on Mar 14, 2003

Obsolete : No
EDC_Max_Num_Data_Logged
Data Type : boolean

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Indicates the IDL data log capability for the maximum number of parameters has been reached.
Struct Default :

Chectout Status : IN by Jason Zhang on Mar 02, 2006

Obsolete : No
Error_Trans_Off_Table
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 9999

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements : 31

Structure Array Size based on : 31


Description :
Table that holds the inactive error index at the time the error transition from on to off. This inactive error index is
written to it once and cleared by another component.
Struct Default :

Chectout Status : IN by Fred Mehdian on Mar 28, 2005

Obsolete : No
GTIS_Auxil_Driver_Feedback_Data
Data Type : uint16

Unit : HEX

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Parameter used for relay and driver feedback indication. This value is intended to be bit-mapped with each bit
representing the on (1) or off (0) status of the drivers. In initial implementations, this value we be intialized to
zero and remain unchanged. This is done to meet GTIS 3.6 requirements which do not meet the intent of the interfaces
being designed for GTIS 5.0.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
GTIS_Collector2_Trigger
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 2

Accuracy :

BNumber : 8

Max Latency :

Simple Default : TIS_STOP

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This trigger initiates collection of data into the GTIS_Collector_Buffer for engineering use. Only complete samples are
collected. A complete sample is the collection of data configured by calling the TIS operation 'cfgDataCollector'.
valid values are: _RUN _STOP _ABORT
Struct Default :

Chectout Status : IN by Chandan Nene on Jun 01, 2006

Obsolete : No
GTIS_Collector_Status
Data Type : uint8
Unit : None

Minimum Value : 0

Maximum Value : 2

Accuracy :

BNumber : 8

Max Latency :

Simple Default : TIS_NOT_CONFIGURED

Software Parameter Type : Run-time variable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Status of the data collector. This indicates whether the data collector is not collecting data, not collecting data, or
not collecting data but transmitting the remaining buffer with BAM messages. ON = collecting OFF = not collecting
BAM_IN_PROGRESS = not collecting but still transmitting BAM messages until the collector buffer is empty.
TIS_NOT_CONFIGURED = Not yet configured successfully after the powerup.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
GTIS_System_Switch_Status
Data Type : uint16

Unit : HEX

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Parameter used for switch and discrete input indications. This parameter is a bitmapped represetnation of switch
positions (on = 1, off =0) according to a tool interface. Since this is not the long term strategy of Core II and GTIS
5.0, this parameter will simply be initialized to 0 and remain at zero. This will provide GTIS 3.6 compliance.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
GTIS_System_Switch_Status_2
Data Type : uint16

Unit : HEX

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable


No of Array Elements :

Structure Array Size based on :

Description :
Parameter used for switch and discrete input indications. This parameter is a bitmapped represetnation of switch
positions (on = 1, off =0) according to a tool interface. Since this is not the long term strategy of Core II and GTIS
5.0, this parameter will simply be initialized to 0 and remain at zero. This will provide GTIS 3.6 compliance.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
T_EDC_Collector_Center_Address
Data Type : uint32

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This is the GTIS_Collector_Buffer center address of 'Valid Data'. For T_EDC_Collector_Stop_Mode = Stop_on_Trigger
(0), T_EDC_Collector_Center_Address is the same as T_EDC_Collector_End_Address. For T_EDC_Collector_Stop_Mode =
Fill_Half_on_Trigger (1), T_EDC_Collector_Center_Address is (typically) the center address of the buffer. For
T_EDC_Collector_Stop_Mode = Fill_Full_on_Trigger (2), T_EDC_Collector_Center_Address is the same as
T_EDC_Collector_Start_Address.
Struct Default :

Chectout Status : IN by Fred Mehdian on Aug 30, 2005

Obsolete : No
T_EDC_Collector_Enable
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 0

Software Parameter Type : Trimmable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Enables/disables the engineering data collector functionality of the ECM.
Struct Default :

Chectout Status : IN by Duane Guingrich on Apr 01, 2003

Obsolete : No
T_EDC_Collector_End_Address
Data Type : uint32

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Address of the byte immediately following the last byte of valid data collected in the GTIS_Collector_Buffer regardless
of the mode set in T_EDC_Collector_Stop_Mode.
Struct Default :

Chectout Status : IN by Fred Mehdian on Aug 30, 2005

Obsolete : No
T_EDC_Collector_Interrupt_ID
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 4

Accuracy :

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Trimmable

No of Array Elements :

Structure Array Size based on :

Description :
Each value in the table corresponds to an interrupt. Interrupts include: EPS=1, VSS=2, JCOM=3, and PIT=4. When the
selected interrupt occurs, a complete sample may be collected, subject to other conditions, such as the state of
T_EDC_Collector_Trigger. Used as argument "event" for XMGR_register call to Execution Manager. Note: To be
compatible with the legacy (GTIS 3.6) data collector the value of 0 shall indicate that the collector is configured to
collect data at the EPS interrupt. When the value is 1 the data shall be collected at the PIT. This will be removed
when the legacy data collector meets the new vision interface (described above). The Comm Agent Base will make the
appropriate conversion to the values that the execution manager expects to see at the interface.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
T_EDC_Collector_Interval
Data Type : uint16

Unit : counts

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16
Max Latency : 0

Simple Default : 200

Software Parameter Type : Trimmable

No of Array Elements :

Structure Array Size based on :

Description :
Value k indicates that k-1 interrupts are to be ignored, then on every kth interrupt, a complete sample may be taken,
subject to other conditions, such as the state of T_EDC_Collector_Trigger. Used as argumet "occurrance" for
XMGR_register call to Execution Manager.
Struct Default :

Chectout Status : IN by David Glass on Feb 07, 2002

Obsolete : No
T_EDC_Collector_Offset
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Trimmable

No of Array Elements :

Structure Array Size based on :

Description :
-- offset description (parameter input into XMGR_register) For events 3 (RT exec), 4 (engine speed exec), and 5
(vehicle speed exec) the offset is the number of minor frames to wait before starting the cyclical execution every
occurrence number of minor frames. Offset is used to define a rate group for a task. It can exceed a theoretical major
frame (though there is no specific major frame enforced by the execution manager) for which the rate group would be the
offset%occurrence.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
T_EDC_Collector_Start_Address
Data Type : uint32

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
The GTIS_Collector_Buffer start address of 'Valid Data' regardless of the mode set in T_EDC_Collector_Stop_Mode. The
valid data begins either at the first complete sample collected (if the buffer has not been filled when
T_EDC_Collector_Trigger occurs), or the oldest complete sample in the buffer (if the buffer has been filled).
Struct Default :

Chectout Status : IN by Fred Mehdian on Aug 30, 2005

Obsolete : No
T_EDC_Collector_Stop_Mode
Data Type : uint16

Unit : None

Minimum Value : 0

Maximum Value : 2

Accuracy :

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Trimmable

No of Array Elements :

Structure Array Size based on :

Description :
Indicator as to how much data is to be recorded following occurrence of T_EDC_Collector_Trigger. The modes are: 0--
Stop_On_Trigger: data collection stops immediately when T_EDC_Collector_Trigger becomes TRUE. 1--Fill_Half_On_Trigger:
following T_EDC_Collector_Trigger becoming TRUE, an additional number of samples is collected, the number being half
the capacity of the buffer. 2--Fill_Full_On_Trigger: following T_EDC_Collector_Trigger becoming TRUE, an additional
number of samples is collected, the number being the entire capacity of the buffer.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
T_EDC_Collector_Trigger
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 8

Max Latency : 0

Simple Default : 0

Software Parameter Type : Trimmable

No of Array Elements :

Structure Array Size based on :

Description :
This trigger initiates collection of data into the GTIS_Collector_Buffer for engineering use. Only complete samples are
collected. A complete sample is the collection of data from every element that is specified in the
T_EDC_Collector_Name_Table.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
T_GTIS_Collector_Enable
Data Type : uint8

Unit : None
Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 8

Max Latency :

Simple Default : 1

Software Parameter Type : Trimmable

No of Array Elements : 0

Structure Array Size based on : 0

Description :
Enables/disables the Data Collector2 functionality of the ECM.
Struct Default :

Chectout Status : IN by Chandan Nene on Mar 29, 2006

Obsolete : No
X_CAGT_EnableDummy
Data Type : enable_t

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 0

Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Dummy item so that the enable_t type gets pulled into the icd_types file for this component. Do not use this data from
other components.
Struct Default :

Chectout Status : IN by Steve Ferree on Feb 13, 2004

Obsolete : No
X_CAGT_ES_HealthDummy
Data Type : es_health_t

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy :

BNumber : 0

Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Dummy variable so that es_health_t gets pulled into the icd_types file for this component. Do not use this variable
from other components.
Struct Default :

Chectout Status : IN by Steve Ferree on Feb 13, 2004

Obsolete : No

Data Used
CFTR_Available_Fault_Table
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
A one dimensional array whose index is the same as error_index. It stores the Cummins fault code associated with the
error_index.
Struct Default :

Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No
CFTR_ErrorIndexTable
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16

Max Latency :

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
List of error indices whose status is either active, inactive, or pending. An active error is one that is currently
being experienced and has persisted in time. An inactive error is one that is no longer currently being experienced but
has a fault count, as stored in the GTIS_Fault_Count_Table, of at least one. A pending error is one that is currently
being experienced but has not yet persisted in time. Only active errors will be translated into faults by the
communications translator. If an element (error_index) is removed from the list then the software shall use a value of
zero to indicate that the array element can be overwritten by the next error that has transitioned to pending.
Therefore the first zero in the array indicates an available slot for storing the error_index.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
CFTR_Error_Occurrence_Time
Data Type : uint32[ ]
Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency :

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This array stores the time of occurrence for all faults that are currently Active in the system. The index into this
array is associated with a system error by means of the index into the CFTR_Error_Index_Table. The maximum of this
array is 255 elements. B Type Size is filled in by build scripts (see gen_config_tracker_tables.pm)
Struct Default :

Chectout Status : IN by Glenda Henry on May 23, 2006

Obsolete : No
CFTR_Error_Persistence_Time
Data Type : uint32[ ]

Unit : None

Minimum Value : 0

Maximum Value : 4294967295

Accuracy :

BNumber : 32

Max Latency :

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This array is indexed with error_index and contains an instance of time (ECM_Run_Time) when the following occurs:
1. The corresponding value of CFTR_Fault_Status_Table[array_index] is ACTIVE and the CFTR_Error_Status_Table bit that
maps to the CFTR_Error_Index_Table[array_index] changes from "set" to "clear". The time is recorded to allow for a
countown to the INACTIVE state. OR 2. The corresponding value of CFTR_Fault_Status_Table[array_index] goes to
INACTIVE. In this case the time is held to allow a countown for the removal of the entries of the corresponding
error_index in the CFTR_Error_Index_Table. This is a powerdown table set dynamically while the code is executed.
The maximum size of this array is 255 elements. B Type Size is filled in by build scripts (see
gen_config_tracker_tables.pm)
Struct Default :

Chectout Status : IN by Glenda Henry on May 23, 2006

Obsolete : No
CFTR_Error_Status_Table
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16
Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Table that records the status of errors in the system. Error status can be determined by any component through the use
of the services CMGR_get_error_index(); and CMGR_get_error();. It is indexed by system error index number. An error
status of 0 means no error. An error status of 1 means error exists.
Struct Default :

Chectout Status : IN by Steve Ferree on Aug 17, 2005

Obsolete : No
CFTR_Fault_Count_Table
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency :

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This array contains the current fault count for each fault that is currently active in the system. The fault count for
each error is incremented each time the ACTIVE state is entered for each fault status table error entry. The index
into this array is associated with a system error by means of the error index into the CFTR_Error_Index_Table. This
array is limited to 255 elements.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
CFTR_Fault_Status_Table
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency :

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This array contains the current error state for each fault that is currently active in the system. The index into this
array is associated with a system error by means of the error index into the CFTR_Error_Index_Table. The valid
error states are defined as the following:
[b7??..b0] PENDING xx01xxx0 ACTIVE
xx00xxx1 INACTIVE xx00xxx0
ACTIVE_PENDING xx11xxx1 INACTIVE_PENDING
xx11xxx0 SNAPSHOT xxxxxx1x NO_SNAPSHOT
xxxxxx0x COUNTDOWN_MODE x1xxxxxx ELAPSED_TIME_MODE
x0xxxxxx This array has a maximum of 255 elements.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
CFTR_Multiple_Fault_Flag
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy : 1

BNumber : 8

Max Latency : 0

Simple Default : 0

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
A one dimensional array whose index is the same as error_index. It stores a TRUE (1) for errors that map to a service
fault code which is mapped to by one or more other errors. A FALSE(0) is stored for a corresponding error if it maps
to a unique service fault code.
Struct Default :

Chectout Status : IN by John Kalill on Apr 30, 2002

Obsolete : No
CFTR_SystemLatchErrorTable
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Table that latches the status of errors in the system. It is indexed by system error index number. An error status of
0 means no error. An error status of 1 means error exists.
Struct Default :

Chectout Status : IN by Steve Ferree on Aug 17, 2005

Obsolete : No
C_CFTR_Countdown_Mode
Data Type : uint16[ ]
Unit : None

Minimum Value : 0

Maximum Value : 3

Accuracy : 1

BNumber : 16

Max Latency : 0

Simple Default : 0

Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
A one dimensional array whose index is the same as error_index. It stores the countdown mode of each error id. The mode
will be used to determine how much time will elapse for an error associated fault that has been inactive, to be removed
from all tables. Specifically, this is done by using calibratible elapsed time and countdown rate, stored in
C_DIR_Fault_Countdown_Period. There are four modes; mode 0, 1, 2, and 3. Faults in mode 0 can only be cleared by a
tool command and therefore will not have a supported calibration for elapsed time and countdown rate.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
C_CFTR_Last_Snapshot
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy : 1

BNumber : 8

Max Latency : 0

Simple Default : 1

Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
A one dimensional array whose index is the same as error_index. It stores the boolean status of whether to log a
snapshot record if the system error, error id, reoccurs. If the boolean satus is TRUE (1) then the snapshot record of
this reoccurring error id will be logged in the last occurrence section of the snapshot table.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
C_CFTR_Persistent_Error_Dur
Data Type : int16[ ]

Unit : s

Minimum Value : 0

Maximum Value : 8000

Accuracy : 0.25

BNumber : 13

Max Latency : 0

Simple Default : 10
Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
An error indexed array of times. A time from this array is the required time each system error shall persist before an
associated fault code becomes active (an entry in the CXLT_Active_Fault_Table). The table is indexed by error_index
value like the other diagnostic tables in the configuration tracker.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
C_DIR_Log_Fault_Indicator
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy : 1

BNumber : 8

Max Latency : 0

Simple Default : 1

Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
A one dimensional array whose index is the same as error_index. It stores the boolean status of whether the error id
will be logged in the snapshot table.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
C_OBD_Enable
Data Type : uint8

Unit : None

Minimum Value : 0

Maximum Value : 1

Accuracy : 1

BNumber : 8

Max Latency : 0

Simple Default : 0

Software Parameter Type : Calibratible

No of Array Elements :

Structure Array Size based on :

Description :
This is the feature enable for On Board Diagnostic. When set to TRUE, all OBD data like operation cycles, warmupcycles,
MIL Status,etc., are updated except OBD_Pending_Errorindex which is independent of this enable.
Struct Default :

Chectout Status : IN by Suresh Cowlagi on Mar 22, 2005

Obsolete : No
DIR_Snapshot_ID_Table
Data Type : uint32[ ]

Unit : None

Minimum Value : 0

Maximum Value : 16777215

Accuracy : 1

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Data Constant

No of Array Elements :

Structure Array Size based on :

Description :
List of public Ids for snapshot record. This element is configured during the build process and should allow no larger
than 24 bits per entry to be used. It is not calibratible after build time but would be viewable for tools real time.
It will be maintained within the code subfile.
Struct Default :

Chectout Status : IN by Steve Ferree on Aug 13, 2003

Obsolete : No
GTIS_Collector_Buffer
Data Type : uint8[ ]

Unit : None

Minimum Value : 0

Maximum Value : 255

Accuracy :

BNumber : 8

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements : 32768

Structure Array Size based on : 32768

Description :
Buffer used by the data collector service to store data for later read by a Cummins Tool. The buffer is treated as a
ring buffer. Note that the size of the ring buffer varies based on the amount of data to be collected each interval
(e.g. a 5000 byte buffer with a collection of 3 bytes of data will wrap at floor(5000/3) = 1666 records or 4998 bytes).
In other words, no partial records will be kept. The size of the buffer is configured by each application at build
time based on the amount of space desired in the final build.
Struct Default :

Chectout Status : IN by Steve Ferree on Aug 13, 2004

Obsolete : No
GTIS_ECM_Run_Time
Data Type : uint32

Unit : s

Minimum Value : 0

Maximum Value : 1073741824

Accuracy : 0.25

BNumber : 30
Max Latency :

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
This data is an integer that counts up or increments every 250 ms.
Struct Default :

Chectout Status : IN by Poe Xayariboun on Sep 08, 2003

Obsolete : No
GTIS_Fault_Count_Table
Data Type : fault_count_t[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy : 1

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
GTIS_Fault_Count_Table contains information about the history and status of each fault. Because it's owned by the
configuration tracker, it's a table indexed to the error_index. Its format is an array of structures. Each element
structure contains four members, and they are: 1) Fault occurrence time 2) Fault decrement count 3) Fault status
4) Fault counts Fault occurrence time is ECM_Run_Time at when the fault associated error_index transitions to on.
Fault statuses are defined as follows: xxxx xx00 - Fault inactive, not in snapshot table xxxx xx01 - Fault active,
not in snapshot table xxxx xx10 - Fault inactive, in snapshot table xxxx xx11 - Fault active, in snapshot table xxx1
xx00 - Pending fault Bits 6,7 and 8 are reserved for engineering component design use, bits 2 and 3 are reserved for
tool interface expansion. The definition of the structure type is: typedef struct { uint32
fault_occurrence_time; /* min=0. , max= 4294967295 */ uint8 fault_decrement_count; /* min=0. ,
max= 255 seconds */ uint8 fault_status; /* min=0. , max= 1 */ uint16
fault_counts; /* min=0. , max= 200 } fault_count_t; The size of this table is determined
during build time.
Struct Default :

Chectout Status : IN by Jason Zhang on Jun 21, 2006

Obsolete : No
T_DIR_FaultSnapshotAssociation
Data Type : uint16[ ]

Unit : None

Minimum Value : 0

Maximum Value : 65535

Accuracy :

BNumber : 16

Max Latency :

Simple Default :

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :
Structure Array Size based on :

Description :
This array is provided for the fault snapshot utility to associate errors/faults with the specific snapshot records in
the snapshot table.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
T_DIR_Fault_Snapshot_Table
Data Type : int8[ ]

Unit : None

Minimum Value : -128

Maximum Value : 127

Accuracy :

BNumber : 7

Max Latency : 0

Simple Default : 0

Software Parameter Type : Powerdown-saved run-time variable

No of Array Elements :

Structure Array Size based on :

Description :
Table containing the snapshot information for an error that is active or was previously active. The size of the array
is determined at time of build and must be equal to: NUM_SNAPSHOTS * (size of parameter identified by ID in
DIR_Snapshot_ID_Table[0] + size of parameter identified by ID in
DIR_Snapshot_ID_Table[1] + ? + ?+ ? + ? + ? + ? + ? + ? + ? + ? + ? + ? + ? + ? +
size of parameter identified by ID in DIR_Snapshot_ID_Table[N])) The "size of
parameter ?" will be determined through the database types. DIR_Snapshot_ID_Table[] is a coded constant that is
configured per application at build time and that will be readable by tools but not editable (Subfile 3 edit level 0).
Default should be all zeros for released cals. Each set of snapshot data shall be delimited by the index value
into the GTIS_Fault_Count_Table array that is associated with the error that is being snapshot. Thus, each set of
snapshot data shall be proceeded by this index value.
Struct Default :

Chectout Status : IN by Steve Ferree on Dec 05, 2003

Obsolete : No
T_EDC_Collector_ID_Table
Data Type : uint32[ ]

Unit : None

Minimum Value : 0

Maximum Value : 16777215

Accuracy :

BNumber : 32

Max Latency : 0

Simple Default : 0

Software Parameter Type : Trimmable

No of Array Elements : 5

Structure Array Size based on : 5

Description :
List of public data identifiers to be saved for each data collector record.
Struct Default :
Chectout Status : IN by Joseph Gahimer on Nov 16, 2001

Obsolete : No

Error
Error Used
File

File Path File Name File Branch File File Type


Version
/vob/core2_cagt_base/design/fh_clearfaults/code fh_dummy /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_check_buffer_size.c /main 5 External Code
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_check_collector_config.c /main 4 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_check_for_error_status_off.c /main 13 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_check_for_error_status_on.c /main 22 External Code
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_collect_data.c /main 5 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_continue_error_status_on.c /main 19 External Code
/vob/core2_prototype/code/icd_gen cagt_cp_data.c /main 1 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_create_snapshot_storage.c /main 10 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_critical_init.c /main 22 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_diagnostics.c /main 17 Internal Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_enter_snapshot.c /main 14 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_error_state_on_transition.c /main 9 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_error_status_off_transition.c /main 20 External Code
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_get_data_by_address.c /main 2 External Code
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_get_data_sample.c /main 4 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_private_global_data.c /main 20 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_process_fault_countdown.c /main 19 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_oldest_active.c /main 9 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_oldest_inactive.c /main 12 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_oldest_pending.c /main 7 External Code
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_snapshot.c /main 9 External Code
/vob/core2_cagt_base/design/code edc_cfgkeyonmode.c /main 2 External Code
/vob/core2_cagt_base/design/code edc_collect_data_into_buffer.c /main 5 External Code
/vob/core2_cagt_base/design/code edc_collectdata.c /main 13 External Code
/vob/core2_cagt_base/design/code edc_config.c /main 12 External Code
/vob/core2_cagt_base/design/code edc_getcapabilities.c /main 6 External Code
/vob/core2_cagt_base/design/code edc_getdclogconfiguration.c /main 1 External Code
/vob/core2_cagt_base/design/code edc_getfullrecordindex.c /main 7 External Code
/vob/core2_cagt_base/design/code edc_getnextbamrecordindex.c /main 4 External Code
/vob/core2_cagt_base/design/code edc_releasebamrecord.c /main 5 External Code
/vob/core2_cagt_base/design/code edc_setdctrigger.c /main 3 External Code
/vob/core2_cagt_base/design/code edc_store_data_to_buffer.c /main 5 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_clearfaults.c /main 15 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_getnextfault.c /main 7 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_getnextsnapshotinfo.c /main 2 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_getsnapshotptr.c /main 4 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_initialize.c /main 7 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_resetfaultcursor.c /main 4 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_resetsnapshotinfocursor.c /main 2 External Code
/vob/core2_cagt_base/test/component_test test_cagt_base.c /main 1 Support
/vob/core2_cagt_base/design csdd_cagt_base.dct /main 10 None
/vob/core2_cagt_base/requirements crs_comm_agent_base_cp.fm /main 19 None
/vob/core2_cagt_base/test/component_test test_procedure_cagt_base.fm /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_check_buffer_size.h /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_check_collector_config.h /main 2 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_check_for_error_status_off.h /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_check_for_error_status_on.h /main 8 None
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_collect_data.h /main 1 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_continue_error_status_on.h /main 4 None
/vob/core2_prototype/code/icd_gen cagt_cp_data.h /main 1 None
/vob/core2_prototype/code/icd_gen cagt_cp_error_id.h /main 1 None
/vob/core2_prototype/code/icd_gen cagt_cp_external_data.h /main 1 None
/vob/core2_prototype/code/icd_gen cagt_cp_external_services.h /main 1 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_create_snapshot_storage.h /main 1 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_critical_init.h /main 4 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_diagnostics.h /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_enter_snapshot.h /main 4 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_error_state_on_transition.h /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_error_status_off_transition.h /main 4 None
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_get_data_by_address.h /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/code cagt_get_data_sample.h /main 2 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_private_global_data.h /main 28 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_process_fault_countdown.h /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_oldest_active.h /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_oldest_inactive.h /main 5 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_oldest_pending.h /main 2 None
/vob/core2_cagt_base/design/cagt_cp_base_main/code cagt_remove_snapshot.h /main 1 None
/vob/core2_cagt_base/design/code edc_cfgkeyonmode.h /main 1 None
/vob/core2_cagt_base/design/code edc_collect_data_into_buffer.h /main 1 None
/vob/core2_cagt_base/design/code edc_collectdata.h /main 1 None
/vob/core2_cagt_base/design/code edc_config.h /main 4 None
/vob/core2_cagt_base/design/code edc_getcapabilities.h /main 6 None
/vob/core2_cagt_base/design/code edc_getdclogconfiguration.h /main 1 None
/vob/core2_cagt_base/design/code edc_getfullrecordindex.h /main 5 None
/vob/core2_cagt_base/design/code edc_getnextbamrecordindex.h /main 1 None
/vob/core2_cagt_base/design/code edc_releasebamrecord.h /main 1 None
/vob/core2_cagt_base/design/code edc_setdctrigger.h /main 1 None
/vob/core2_cagt_base/design/fh_clearfaults/code fault_handler.h /main 6 External Code
/vob/core2_cagt_base/design/fh_clearfaults/code fh_clearfaults.h /main 1 None
/vob/core2_cagt_base/test/component_test test_cagt_base_io_data_max.h /main 1 None
/vob/core2_cagt_base/test/component_test test_cagt_base_io_data_mid.h /main 1 None
/vob/core2_cagt_base/test/component_test test_cagt_base_io_data_min.h /main 1 None
/vob/core2_cagt_base/design csdd_cagt_base.ini /main 4 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_check_buffer_size.ini /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_check_collector_config.ini /main 1 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_check_for_error_status_off.ini /main 4 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_check_for_error_status_on.ini /main 4 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_collect_data.ini /main 2 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_continue_error_status_on.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_create_snapshot_storage.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_critical_init.ini /main 7 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_diagnostics.ini /main 4 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_enter_snapshot.ini /main 5 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_error_state_off_transition.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_error_state_on_transition.ini /main 3 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_get_data_by_address.ini /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_get_data_sample.ini /main 1 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_process_fault_countdown.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_oldest_active.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_oldest_inactive.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_oldest_pending.ini /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_snapshot.ini /main 3 None
/vob/core2_cagt_base/design/fh_clearfaults/design sdd_fh_clearfaults.ini /main 3 None
/vob/core2_cagt_base/design csdd_cagt_base.mdl /main 18 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_check_buffer_size.mdl /main 3 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_check_collector_config.mdl /main 4 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_check_for_error_status_off.mdl /main 12 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_check_for_error_status_on.mdl /main 20 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_collect_data.mdl /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_continue_error_status_on.mdl /main 17 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_create_snapshot_storage.mdl /main 8 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_critical_init.mdl /main 18 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_diagnostics.mdl /main 15 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_enter_snapshot.mdl /main 15 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_error_state_on_transition.mdl /main 8 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_error_status_off_transition.mdl /main 18 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_get_data_by_address.mdl /main 1 None
/vob/core2_cagt_base/design/cagt_data_collector/design sdd_cagt_get_data_sample.mdl /main 3 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_process_fault_countdown.mdl /main 17 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_oldest_active.mdl /main 9 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_oldest_inactive.mdl /main 10 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_oldest_pending.mdl /main 5 None
/vob/core2_cagt_base/design/cagt_cp_base_main/design sdd_cagt_remove_snapshot.mdl /main 7 None
/vob/core2_cagt_base/design/fh_clearfaults/design sdd_fh_clearfaults.mdl /main 14 None
/vob/core2_cagt_base/test/component_test test_cagt_base.sh /main 1 None
/vob/core2_cagt_base/design cagt_base_design_dictionary.txt /main 37 None
/vob/core2_cagt_base/test/component_test cagt_base_test_results.txt /main 1 None

You might also like