1997/02/17 Caterpillar

VIMS-PC Version 2.1 Now Available {7601}

Usage:

5130 (5ZL, 7TJ),
5230 (7LL) Excavators;
784B (5RK) Tractor;
785B (6HK),
789B (7EK),
793B (1HL),
793C (4AR) Trucks;
994 (9YF) Wheel Loaders

Reference: Service Magazine Article, January 20, 1997, Page 25; "VIMS-PC Service Tool Operating System Environment Answers".

VIMS-PC version 2.1 continues the trend of improvements and enhancements started in version 2.0. The version 2.1 upgrade package includes Common Services System (CSS) version 1.3 upgrade, Information System Builder (ISB) version 1.1 upgrade, as well as VIMS-PC version 2.1 software. To ensure compatibility with some of the new features, upgrade all of the programs included in the upgrade package at the same time. It is strongly advised to use this bundle of three software programs to replace all present versions. These software programs are fully backwards compatible with all VIMS applications.

This document provides a brief description of changes made to each of the four VIMS-PC programs and to ISB. The changes represent new features as well as improvements to existing functionality. This article is a summary of the readme and on-help files released with the software programs. The readme and on-help files can be accessed while the programs are operating. Refer to these files for further assistance in resolving setup and operational questions.

Chart A shows program compatibility combinations with various PC operating systems. The complete upgrade will run with Microsoft Windows95, Microsoft Windows 3.1 and Microsoft Windows for Workgroups 3.11. This upgrade is not supported for the Windows NT or OS/2 operating systems.

When using Microsoft Windows 3.1 and 3.11 software, install the Microsoft Win32s program before installing ISB version 1.1 if the Win32s program is not already installed on the computer. The recommended version of Win32s is 1.20. Some known compatibility problems exist with some earlier and some later versions of Win32s. Do not install Win32s with Windows 95.

Because OS/2 does not recognize the Win32s functionality, ISB will not run in a DOS Window or Microsoft Windows window in OS/2. Use the dual-boot feature of OS/2 and run VIMS-PC and ISB from a DOS partition. Make sure Win32s is loaded into Windows from the DOS partition.

VIMS-PC 2.1 Enhancements

The following changes apply to all programs in VIMS-PC version 2.1.

* Most functions now have context-sensitive help. Pressing the (F1) key will bring up a help screen for the active function. The help screen text is from the on-line User Manual.

* With VIMS-PC 2.1, when report generation finishes, the report displays. If there is no data to report, no report will display. The system menu also has provisions to close a report.

While a report is generating, the ALT-F4 keystroke combination may cause a Windows General Protection Fault (GPF). This keystroke combination is a Windows command to close an application. If a Windows GPF message displays, Windows and any program running at the time of the GPF error message, must be restarted. Make sure the report generator finishes before using the ALT-F4 to exit from reports.

VIMS-PC Communicate Program Enhancements

VIMS-PC 2.1 Communicate program includes the following enhancements.

* The Communicate program will download and write scratch files (under score files) to the TEMP subdirectory in WINDOWS. These files can be converted at a later time if needed.

* On machines with 130-1345 Software and later, and version 3.0 hardware, the hardware part number will display on the Machine Status screen with VIMS-PC 2.1.

* In VIMS-PC 2.0, while downloading the .esl file, sometimes the download would never complete (the progress bar stays at 0%). When the user canceled the operation, the .ecl would not reset. VIMS-PC 2.1 detects this problem with the .esl download and stops the .esl download. The program moves on to download the next files and resets the .ecl. The .esl download is not good data.

* VIMS-PC 2.1 allows the user to copy a machine configuration file to a floppy drive or to the hard drive.

VIMS-PC Analysis Program Enhancements

* VIMS-PC 2.1 fixed a problem with the Loader Payload Chronological report header. The report header did not print correctly when materials are restricted.

* VIMS-PC 2.1 allows storage of up to 9 data logger files. This is similar to the expanded event recorder storage allowed in 2.0.

* The event list browser is improved to display correct event recorder or data logger links for up to 9 event recorders or 9 data loggers. Previous problems with linking from a system event are fixed in VIMS-2.1.

* The handling of unknown events in both browse and report formats is improved in VIMS-PC 2.1. Unknown events now display their warning catagory followed by their master event number.

* VIMS-PC 2.1 automatically sets the default time range for all reports. This prevents the user from having to guess the start and end points of a particular file.

* VIMS-PC 2.1 corrects the "Date Range: 99/99/99 to 00/00/00" and "SMU Range: 11934060 to 0" problem when displaying a .ESL file through use of the (File) button in a Browse-Event List screen.

* The open file dialog option "Download Files (*.hs/bo/)" file type for truck payload report & truck payload utilization report does down load a historical report file.

* Data Logger graph Y-axis range does not allow a user to enter minimum value greater than the maximum value.

Truck Payload Software Enhancements

The VIMS-PC 2.1 release addresses Truck Payload enhancements. These enhancements require version 9.3x and later on-board software to be fully operational. (Effective with 784B (5RK26), 785B (6HK687), 789B (7EK553), 793C (4AR122).

* Non-shift time range selection now correctly obtains all records between the start and end points specified in the dialog box.

* Shift definition program correctly restricts shifts to the user's selected times. The Truck Payload Shift Criteria start point radio buttons have been removed.

* In VIMS-PC 2.1, a shift is considered to wrap around a day if it ends before it starts (i.e. Start time of 06:00 PM and an End time of 06:00 AM). In this circumstance, the report data will begin being collected at 06:00 PM on the first date specified in the Start Date dialog. Consolidated and Combined shift functions have been removed to prevent confusion.

* Shift definitions default values in VIMS-PC 2.1 are: 1st shift: 8AM - 4PM, 2nd shift: 4PM - 12AM, 3rd shift: 12AM - 8AM.

* Shift Summary report data inaccuracy problems are fixed.

* The Utilization report no longer allows mismatches between event list and payload files.

* VIMS-PC 2.1 does not allow time stamps to print over each other on graphing functions. (Data Logger and Event Recorder)

* Truck payload reports now allow "less than or equal and more than or equal" field ranges to be consistent with the data used in the reports.

* Truck payload analysis criteria for graph average values now default to zero.

Loader Payload Software Enhancements

VIMS-PC 2.1 improved various areas of Loader Payload software functionality.

* With VIMS-PC 2.1 the default Loader Payload report is now the Summary report, not Chronological-Combined.

* A Summary report problem where the preview report on the display and hardcopy report were different is fixed with VIMS-PC 2.1.

* VIMS-PC 2.1 provides an additional title on the report header to show the shift (or non-shift) reported.

Enhancements All Reports

* VIMS-PC 2.1 automatically displays a preview of the report when the report is complete.

* The preview report remains displayed even after it is sent to the printer.

* VIMS-PC 2.1 does not display an empty report if there is no data for a report.

* VIMS-PC 2.1 allows the user to close the preview report window upon report completion by double-clicking on the report window system menu.

VIMS-PC Merge

VIMS-PC 2.1 Merge program includes the following enhancements.

* VIMS-PC 2.1 enhanced trend file merges for the 5230 shovels.

* VIMS-PC 2.1 added an hourglass pointer icon that displays while running lengthy merges.

VIMS-PC Utilities

The VIMS-PC Utilities program has no changes in this release.

Using the Event List Browser, Data Loggers, and Event Recorders.

VIMS-PC will now integrate event lists from a machine with previously stored event recorders and data loggers. A VIMS machine can only contain two event recorders and one data logger. However, an event list can span multiple data loggers or event recorders if it is not reset during a download. This more integrated view may be helpful when performing repeated tests on a machine and desiring to compare results between test runs.

The number of event recorders and data loggers displayed in conjunction with an event list is controlled by the same selection under the FILE - BROWSE PREFERENCES menu item that controls the number to be stored. If "Limit to only *.evr, *.ev2 Event Recorder files" is checked, then only the *.evr and *.ev2 files associated with the machine will be displayed in the "Link" column. Likewise, if "Limit to only *.dlr Data logger files" is checked, then only *.dlr files will be displayed.

Increasing the number of files downloaded and linked to the event list will increase the time it takes to bring up the event list browser. If 9 30-minute data loggers and 9 6-minute event recorders have been downloaded to an event list with 500 events, it can take over 5 minutes to display the event list depending on the speed of the PC.

When selecting an event to link to the data logger or event recorder files, a file list will be displayed and the file containing the information of interest will be highlighted. Any other file can be selected if desired. If a system event is selected and a link is attempted to a data logger or event recorder, the channel selection display will appear. This is because system events do not always correspond with a particular on-board channel.

VIMS-PC will only establish a link between an event list, data logger files, and event recorder files that are in the same subdirectory. While looking at an event list and after selecting a link button, a file can be selected from a different subdirectory.

Using More Data Loggers

VIMS-PC 2.1 now supports the storage of up to 9 data logger files for a given equipment number of machine. Use of this feature requires coordination between the Analysis and Communicate programs. The following is a step-by-step procedure to increase the number of data logger files allowed on the PC.

Step 1. Start Analysis.

Step 2. Select File.

Step 3. Select Browse Preferences.

Step 4. Uncheck the checkbox labeled "Limit to only *.dlr datalogger files."

Step 5. Exit Analysis.

Whenever files are downloaded or converted from a machine, the *.dlr file will contain the latest information, while *.dl2 to *.dl9 files will have increasingly older data.

Automatically Selecting Default Time Range for Reports

VIMS-PC 2.1 adds the ability to both automatically display the maximum range of data in the file and to remember a narrowed search range for the duration of a session. This functionality is controlled by the selector labeled "Display Maximum Ranges in the Report Dialogs" under FILE- REPORT-PRODUCTIVITY PREFERENCES. When this selector is enabled, the maximum range of the appropriate file displays every time a report runs. With this switch off, the maximum range of data displays the first time a file is opened. Subsequent uses of the same file during a session of Analysis will remember the previous time dialog settings.

Information System Builder Version 1.1

This release (V1.1) of Information System Builder is supported on Windows 3.1, Windows for Workgroups 3.11 and Windows 95. Common Services V1.3 is required if using Windows 95. Information System Builder V1.1 includes a startup compatibility check that will notify you if an incompatible combination is installed.

Caterpillar Common Services and VIMS-PC must be installed prior to installing or running Information System Builder. You must use the Caterpillar Common Services Install icon to install Information System Builder.

If you have a previous version of Information System Buider installed, you will be asked if you want to Reinstall or Upgrade. Usually, you will perform an Upgrade. Reinstall will write over your release and revision archive files, leaving configurations in your archives that Information System Builder cannot access. To regain access to orphaned configurations in the archives, import them directly from the archive directories. Importing the archived files will create new files. The old files remain in the archives and can be deleted after restoration.

The 32-Bit disk access option has been associated with data loss on laptops. Caterpillar recommends that this option be turned off in all cases. To change this option, select Main; Control Panel; 386 Enhanced; Virtual Memory; Change. Deselect "32-Bit disk access" to turn the option off.

Common Services Install creates an icon group labelled Caterpillar VIMS and installs the VIMS-PC icons into that group. However, if the group already exists, as in the case when VIMS-PC is already installed and you then install Information System Builder (or visa-versa), CCS Install places the 2nd set of icons into whatever group box is currently open and on top. This is usually the Common Services group. In the event that you experience this, open the Caterpillar VIMS group, then drag the icons from whatever group they were placed in by CCS Install, to the Caterpillar VIMS group.

If you experience strange start-up problems the first time you attempt to start Information System Builder with Windows 3.1, verify that Win32s is properly installed. To verify proper installation of Win32s, run the test game supplied in the Win32s install kit. Also verify that the Common Services program directory "CSSEXE" is in your Path statement in the Autoexec.Bat file. To verify this, type PATH at the C: prompt.

If "CSSEXE" is not in the path statement, edit the Autoexec.Bat file and add this to the path statement. Save the file. You must reboot the computer for the change to take effect.

Common Services V1.3 database services displays an icon on start-up in the lower left corner. If this icon is closed while any CSS program is running, the program will quit the next time it attempts to access a file. To help prevent this from happening, make the icon invisible.

To make the icon invisible, edit the bti.ini file, located in the windows sub-directory, with the Windows Write program. Start Write and select Open from the File menu. Select the Windows directory and select the All Files option. Scroll through the list of files to locate the bti.ini file, highlight it, click on OK to open it. Locate the line "desktopicon=Yes" and change to "desktopicon=No".

If you have installed Information System Builder using the Upgrade option, and experience an error message when opening the Loader Payload-Material window, this is due to an invalid entry in the ib.ini file.

To edit the ib.ini file with the Windows Write program. Start Write and select Open from the FILE menu. Select the C-Windows-isb-data directory and select the All Files option. Scroll through the list of files to locate the ib.ini file, highlight it, click on OK to open it. Locate the line "p2materialunits=" and change the value to "english" or "metric".