The display covered in the book is a touch screen display.
Reference: The Information Display Manual for your specific machine.
Reference: Use the most current version of VIMSTM . VIMS can be found at: https://mining.cat.com/vims > Software and Current Releases.
The VIMS 3G System is a state-of-the-art onboard system with the following features:
- Machine systems are monitored for the operator.
- Payload productivity information is measured by the system and stored in onboard memory. This information can be downloaded later for analysis.
- Abnormal machine conditions and/or incorrect machine operation are identified. The diagnosis of these abnormal conditions allows the operator to modify the machine operation to correct the problem. The service technician is able to schedule machine maintenance if the condition is not related to machine operation.
- Prognostic information that can help predict potential problems before failures can occur. This information allows machine maintenance to be scheduled during the preventive maintenance servicing interval.
VIMS communicates with other ECMs on the machine and VIMS communicates with systems off the machine through the data-links. The three data links for VIMS are:
CAN Data-Link - This three-wire data link allows communication between the VIMS ECM and other machine control systems for the transfer of data.
Cat Data-Link - This two-wire data-link allows communication between the VIMS ECM and other machine control systems. This data-link also allows communication with the Cat® Electronic Technician (Cat ET) service tool.
RS-232 Data-Link (Service Tool) - This serial three-wire data link allows communication between the VIMS ECM and the service tool (laptop computer).
RS-232 Data Link (Broadcast) - This serial three-wire data link allows communication between the VIMS ECM and other off-board systems that are not service tools. The onboard data can be passed from the machine when a radio telemetry system is connected to the port.
VIMS uses four types of data. The four types of data are:
Sensed - Data is read from the sensors and switches. The sensors and switches communicate with the VIMS ECM.
Internal - Data is generated within the VIMS ECM. The date and time are examples of internal data.
Communicated - Data is received through the Cat data-link from other machine systems. For example, the engine speed is received through the Cat data-link from the Engine ECM.
Calculated - Data mathematically determined by the VIMS ECM. For example, the event duration is calculated and stored in the event list.
Note: Multiple events for a single machine condition may occur. VIMS can inform the user if the actual cause of a stored event is due to a faulty component or a true abnormal condition.
The same VIMS operates on various different machines. All of the possible functions of VIMS are not performed on every machine. Configuration software is used to identify the type of VIMS machine. The configuration software also identifies the available functions of VIMS.
Diagnostic information is stored for all system events even if the event is not present at the time of troubleshooting. A personal computer (PC) is used as the VIMS service tool. See the VIMS VIMSpc Users Manual, FEB0047 for additional information.
The occurrence of certain events and machine conditions are recorded in the onboard memory. The information is organized into seven categories. This information is used to analyze problems with the machine. The information is typically used at a later date by service technicians or management. The categories of information follow:
Event List - The event list is a record of stored events that have occurred on the machine. Not all events are stored. The record contains the last 500 events (data or system) that are listed in chronological order. This means that the events are listed in the order of occurrence. The newest events appear at the top of the list. The event list transfers the oldest data into the "event summary list" when the event list exceeds 500 records. The "event summary list" includes the first five occurrences, the last five occurrences, and the worst five occurrences recorded for any of the "data events". The "event summary list" is limited to storing only 500 records. "System events" can be identified by the diagnostic codes (MID, CID, and FMI). All other events are "data events". The event list is accessible from the Advisor display or with VIMSpc.
Note: All events that contain diagnostic information (MID, CID, and FMI) are the diagnostic type of system events. Not all events without diagnostic information (MID, CID, and FMI) are data events. An example of a system event without diagnostic codes is an open wire in the circuit for the hydraulic oil level. Remember that the circuit of a switch (open switch) can report a true condition that relates to a parameter. This same switch can indicate a system failure (open wire) but the failure is reported as low hydraulic oil level.
Snapshot - The Snapshot stores a segment of history in real time for all parameters (channels) at a one second interval. The snapshot relates to a set of predefined events. A snapshot is triggered automatically for a severe event. The snapshot is then stored in memory. The configuration software designates the events that are considered to be severe events. The "Trigger Snapshot" menu option in the Advisor can be used to initiate a snapshot manually. A snapshot consists of a "flight recording" of all of the parameters that describe the conditions of the system. The snapshot records data from 5 minutes before the event to 1 minute after the event. This strategy is also applied to snapshots that are triggered immediately after key ON. However, a portion of the 5 minutes of data that occurred prior to the event was captured prior to turning the keyswitch off. This portion of data may have been stored hours or days before the event that triggered the snapshot. VIMS has the capability of storing two sets of snapshot information. If a snapshot is in the process of being recorded and a second snapshot is triggered, the second snapshot is ignored. The snapshot information is accessible only with the VIMSpc.
Data Logger - The data logger captures all of the parameters that are monitored by VIMS. The data logger is recorded in one-second intervals. The operation of the data logger is similar to the snapshot. However, the data logger cannot be triggered automatically. The manual triggering of the data logger can only be done by VIMSpc or the Advisor display. The data logger can be started and stopped with a total recording time of 30 minutes. The information that is recorded by the data logger is accessible only with VIMSpc. The data logger can be reset by VIMSpc or the Advisor display. The cycle data for the payload (time and date) can be used as basic information of data logger in place of this data logger.
Reference: See the System Operation, "Features" section of this manual for Data Logger details.
Trends - Trend information consists of the minimums, maximums, and averages of parameter data over time. Trend information is viewed with VIMSpc software. The trend information is displayed as a graph or the trend information is displayed as columns of data. An example of trend information is the average brake temperature per hour. Trend information is recorded for predefined parameters for each machine. Trend information is recorded under the following specified guidelines:
- All 1 hour continuous trends begin when the keyswitch is turned on.
- The data of the trend that is collected during a period less than 1 hour when the keyswitch is turned off is discarded.
- Trend points are the average of each trend that was captured during the past hour. Each trend must meet the conditions that are set for that trend. A single trend point for the designated hour is calculated and stored when the measured trends are averaged over 1 hour.
The data point or the responsible failure mode identifier (FMI) are stored according to the guidelines that are listed here:
- At least one "Trend condition" was met.
- "FMI 19 conditions not met" is stored or the FMI responsible for the conditions that were not met is stored.
Trends are accessible only with VIMSpc.
Cumulative - Information is the number of occurrences (counts) of specific events. An example of cumulative information is total engine revolutions or total fuel consumption over the life of the machine or component. Cumulative information is recorded for a standard set of parameters. The parameters are defined in the configuration software for each machine. The onboard system collects "life-time cumulatives" with no need to reset. The situations that will cause an automatic resetting of the "cumulatives" are:
- New onboard software is flashed into the onboard memory.
Note: The term "onboard software" describes the following information: System (VIMS) and Model of the machine.
- A configuration is loaded with any changes to the methods of calculating and storing cumulative data. The change indicates that a correction has been made to the configuration or the VIMS ECM has been installed from a different application. The new VIMS ECM may not recognize the methods of calculating and storing cumulative data that is used by the configuration.
Resetting of "cumulatives" manually is not required. However, if the user desires, the "cumulatives" may be reset manually. The reset process clears all "cumulatives". Because there is only one choice, "cumulatives" cannot be reset individually. If a reset of "cumulatives" is requested, all the "cumulatives" will be reset.
"Cumulatives" are accessible only with VIMSpc.
Histograms - Histogram information records the history of a parameter since last reset. For example: An engine speed histogram indicates the percentage of time the engine operated within a defined speed limit and the data time interval. Histograms can be used to evaluate the range of operation for a parameter. Histograms are accessible only with VIMSpc.
Payload - Payload information is recorded for the wheel loader, as required.