The logs include the following:
GENSET CONTROL - Events for the EMCP 4 GSC
ENGINE CONTROL - Events for a primary CAN data link compatible engine ECM
DIGITAL AVR - Events for the Caterpillar Digital Voltage Regulator (CDVR)
THERMOCOUPLE - Events for the thermocouple module
EXTERNAL I/O - Events for the Discrete Input/Output (DIO) module
RTD MODULE - Events for the Resistive Temperature Device (RTD) module
SCR MODULE - Events for engine aftertreatment systems
The genset control log stores events that are generated by the EMCP 4. Any other event is stored within the module that generated the event. Even if the EMCP annunciates an event, it does not mean that the EMCP logs that event. The event may be within the log of another module.
Each log is visible only if the module is connected to the appropriate data link, either the primary data link or the accessory data link, and is communicating with the EMCP 4.
The list of event logs can be viewed by pressing the event log hotkey or via the "VIEW" submenu. Select the log you wish to view and press the "OK" key to view the events.
The EMCP 4 supports more than one instance of some of the above modules. Those modules are uniquely identified with a number at the end of the log name.
The module number is software-configured, and is called the module's "ECU INSTANCE NUMBER". The ECU instance number can be viewed and modified by the Caterpillar service tool.
An event in the EMCP 4 genset control log can be in one of three states:
| Present | This state is only applicable to the genset control log. Present means that the condition that caused the event is still present. The condition must be addressed before the event can be reset.
This state only applies to EMCP events. Other modules will not have present in logs. |
| Active | The event was previously in a "Present" state, but it is no longer present. It has been latched by the event system and needs to be reset before the engine can be restarted.
Within the Genset Control Log, the condition that caused the event is still affecting the system, but may be reset. Warning type events automatically reset when the condition that caused the event is resolved and will never be Active. Within any log other than the Genset Control Log, the condition that caused the event is affecting the system. The event may, or may not, be resettable. If the Reset All command fails to reset the event, then this event is still occurring and must be resolved before the event can be reset. Many events go from present to active when the engine is shut down and may reoccur once the engine starts running again. Further action may be required to resolve the issue. |
| Inactive | The event has happened at some time in the past but is no longer affecting the system. Inactive events are stored for historical purposes only. |