Beruflich Dokumente
Kultur Dokumente
i01489008
Illustration 1 g00490762
The display of most maintenance events is delayed with the 9.X class
of configuration software or later versions. The VIMS may wait up to
eight seconds from the start of an event before the event is
displayed. This delay is called debounce. This eight second delay is
included in the total duration time of the events that are recorded in
the event list. When the VIMS has received an event from an
electronic control via the CAT data link the VIMS adds zero time to
these events. the VIMS displays the events immediately. Debounce is
applied to many parameters in order to prevent false tripping of
events or debounce is applied to many parameters in order to reduce
false tripping of events.
Pressing the "F1" key will display the diagnostic information (MID, CID,
and FMI codes) for the event on the second line of the message area.
An example is shown here:
Illustration 3 g00490768
When the VIMS is in the gauge mode pressing the "F1" key will display
the failure on the message area. Pressing the "F1" key again will
display the FMI code definition. An example of the message is
"SHORTED LO".
If the Module Identifier is for a VIMS module use this Service Manual,
SENR6059 module to troubleshoot the failure. This Service Manual,
SENR6059 module contains troubleshooting procedures for VIMS
electronic control modules only. Refer to the Testing and Adjusting,
"Troubleshooting Procedures" section of this manual for the CID/FMI
troubleshooting procedures.
Table 1
Component Identifier (CID)
The Component Identifier (CID) is a code that describes the component
that is believed to have caused the failure. The MID/CID/FMI can be
used to see the whole story.
Table 2
( 1) The current Component Identifiers provided in the table, apply to any machine
that was equipped with the VIMS after 08January 1994. These Component
Identifiers also apply to machines that were updated with new software after
08January 1994.
Illustration 4 g00490995
Table 3
Detailed FMI Explanation
z Timing is retarded.
z Intermittent/erratic signal
z Noisy signal
codes.)
z Failed ECM
z The harness
harness that has the sensor signal wire shorted to any voltage that
Some Possible
causes of
FMI 04 are
listed here:
z The sensor
z The harness
input.
Responding Properly" A
Improper response of a
z Component failure
the data link. This code indicates that the communication link to the
ECM has been lost for more than five
seconds and The ECM will not respond.
Some possible causes of FMI 09 are listed here:
electronic controls
z Failure of the electronic control
For example, The ground speed increases too fast for normal
operation. The output of the transmission speed
z Calibration is required.
FMI 19 -"Conditions Not Met" This code is used when conditions that
are defined in the software are not met in order to store trend data.
FMI 19 or the actual FMI that is responsible for the failed trend
condition will be recorded.
Troubleshooting Procedures
Go to the procedure that corresponds to the CID and FMI that is
shown on the VIMS message center module. These procedures are
used for maintenance events (diagnostic codes)that originate with
the VIMS modules. These procedures are used for CID's that have an
MID of 49, 50, 57, 58, 59, 60, 65, 66, 67 or 68.
If the module identifier is not one of the previous listed numbers for the
VIMS modules, see the Module Identifier (MID) chart that is located on
the Electrical System Schematic for the machine that is being serviced.
After determining which electronic control module detected the event
or failure, see the service manual module for that control for
troubleshooting information (CID/FMI). The service manual modules for
each control are part of the Service Manual for the machine. See the
following sections for additional information:Module Identifier (MID)
and the Component Identifier (CID).