Release Notes for Cat® MineStar v3.x.x System{7605} Caterpillar

Machine Control and Guidance Products:

MINESTAR HEALTH (S/N: DNC1-UP)

MINESTAR ONBRD (S/N: ANM1-UP)

Introduction

This Special Instruction contains information about release notes that will provide details to aid the upgrade of a Cat^® MineStar v3.1.1 System to v3.1.1-45.

The Special Instruction also contains details of issues resolved since 3.1.1-34 and known limitations with associated workaround as applicable.

The information used within this document should be used as an input into the statement of work for the upgrade to occur at a customer site.

Note: v3.1.1 only supports the English language.

These upgrades should be requested by submitting a request through the appropriate service web portal:

https://login.salesforce.com/secur/login_portal.jsp?orgId=00D30000000YC8U&portalId
=06030000000rZAN

Information in this document is subject to change without notice. Information contained within this document and the features and changes described are accurate. Hence, Caterpillar cannot accept any type of liability for errors in, or omissions arising from, the use of this information.

Important Safety Information

Work safely. Most accidents that involve product operation, maintenance, and repair are caused by failure to observe basic safety rules or precautions. An accident can often be avoided by recognizing potentially hazardous situations before an accident occurs.

A person must be alert to potential hazards. This person should also have the necessary training, skills, and tools in order to perform these functions properly.

Safety precautions and warnings are provided in this instruction and on the product. If these hazard warnings are not heeded, bodily injury or death could occur to you or to other persons. Caterpillar cannot anticipate every possible circumstance that might involve a potential hazard. Therefore, the warnings in this publication and the warnings that are on the product are not all inclusive.

If a tool, a procedure, a work method, or operating technique that is not recommended by Caterpillar is used. Ensure that the tool, procedure, work method, or operating technique is safe to use. Ensure that the product will not be damaged or made unsafe by the operation, lubrication, maintenance, or the repair procedures that are used.

Release Notes for 3.1.1-45

Release Notes for 3.1.1-45 are listed below:

Fleet

• Situations occur where a truck has no current automatic assignment such as when the truck is manually assigned. When the current assignment is requested a null pointer exception appears in the logs. These situations are now prevented such that an assignment is only activated with an assignment object and assignment object is returned when no assignment exists.

• A null pointer exception is prevented from appearing in the Assignment logs when blending reports are enabled. The exception was triggered when a truck was not traveling from a loading tool or dump and to a loading tool or dump.

• The client should not freeze after changes made to prevent dead lock problems.

• Updated the computed properties of the attached roads, when a waypoint is moved. Added a Mine Model Validation scan to find and display these issues.

• Addressed an issue where upon creating a scheduled assignment, a user was unable to set a specific delay to start upon arrival.

• Addressed Cycle Assistant issue, so that invalid system-generated manual cycles that overlap good real cycles are no longer created. Invalid "blue cycle" gaps are no longer produced under the scenario of following an empty display of the current shift with a display of cycles from two or more shifts ago.

• Changing the duration type of a delay no longer affects the start date of the delay.

• Addressed an inaccurate hang time issue due to Wait for Spot Activities Not Working.

• Addressed Class Cast Exception issue, when the loading Tool grade block is changed in the loading tool assistant.

• Added new options to "exportData" and "ExportDataStores", which optionally enable e-mail when errors occur, but will not e-mail on error by default. False positive error e-mail could occur for large ZIP compression files due to a flaw in third-party compression libraries which perform the ZIP file validation.

• This update includes the state change handling for all machines in the pit model service, so that the change in state will be recorded and displayed as appropriate.

• The CleanExpiredFiles function is now capable of deleting {MSTAR_LOGS} UIFacade log files.

• Zero fluid amounts will display a warning, but will allow the user to save the values if required. Validation errors that prevent the saving of data are displayed as errors instead of warnings.

Health

• Added unit "power intensity" for parameter "Service Brake Power". This updated requires the execution of "makeDataStores ReferenceData" for MineStar 4.x or "makeDataStores Health" for MineStar 3.1.1.

• Conversion for fuel burn rate has been corrected. Addressed the problem with incorrect values being displayed for Fuel rate engine LH and Fuel rate engine RH. This updated requires the execution of "MakeDataStores ReferenceData" to be run for MineStar 4.x or "makeDataStores Health'" for MineStar 3.x.

• Updated the FPO Calculation limits to contain limits for 795F Off High-Way Trucks.

• Updated the core MineStar logic, so it finds the correct channels when importing datalogger files generated by TPI boxes.

• Updated the Site Editor, so it correctly plots VIMS3G events.

• Updated an issue with treating TPI/VIMS3G events from different sensors as duplicates (affected HE002 report). This change requires the execution of "makeDataStores UpdateHealth" (quick update) or "makeDataStores Health" (full update including VIMS definitions).

Release Notes for 3.1.1-44

Release Notes for 3.1.1-44 are listed below:

Fleet

• Updated to resolve an issue that would cause synchronization of grade block changes with GeoServer to fail. This issue is evident by "LazyInitializationExceptions" related to the GradeBlockWFSExporter in the server MineTracking log.

• Updated to resolve an issue where the Machine Types selected for each standard message group are displayed incorrectly in the MineStar Desktop Client.

• Updated to resolve an issue where deactivating blocks in the Mining Block Finder would fail causing an exception in the client log.

• Updated to resolve an issue where the server would revert to STANDBY after services are restarted during a Standby Snapshot.

• Added settings in supervisor to allow for periodic cleanup of the "onboard/MineStar" folder on the server. These settings are "Days to Delete" and "Days to Retain" and are used by the CleanExpiredFiles scheduled job.

• Updated to resolve an issue in Site Monitor where the Loading Tool way points would not update, if the "Field Update Assistant" is also open.

• Updated to resolve an issue in the MineStar Desktop Client, where the displayed machine selection on the scheduled jobs page is invalid when navigating between jobs.

• Removed the "Schema" option from makeDataStores when running in a production environment.

Also updated the message to the user, when database schema is invalid to suggest a "makeDataStores all" rather than "makeDataStores schema".

Health

• Updated the VIMS definitions to v13.0.0.4.

• Ensure that the channels with distinct Data Sources are listed as separate columns in VimsXP.

• Updated to resolve the issue with target values not showing up in HE420 reports. This update requires makeDataStores Health. Alternatively, contact Caterpillar support for a manual update using a SQL script without executing makeDataStores (MineStar needs to be updated to the latest update v3.1.1 or patched 3.1).

Note: This update is applicable to VIMS targets only, proper support for VIMS NFF target is still in progress.

• Update MineStar to have correct units and mappings for the following parameters.

- 0x820001E5

- 0x820001F5

- 0x820001FD

- 0x820001ED

- 0x820000A2

• The Health Data Delete job has been updated to ensure that it deletes the correct data based on its configuration.

Release Notes for 3.1.1-40

Release Notes for 3.1.1-40 are listed below:

Fleet

• Issue that prevented data from being in the Safety Check Record has been resolved.

• Resolved the issue that was causing duplicate scheduled breaks to be created when certain combination of options was selected in the UI.

• Prevent creation of two machines with the same name by displaying a warning to the user that a machine with this name exists.

• Improved the data cleanup and maintenance routines associated with the MineStar database.

• Updated to resolve an intermittent error in the MineTracking logs to do with default materials on load report events.

• Resolved the issue where the ECF component manager was incorrectly populating properties of related objects (TruckCycles) which populating an object (LoaderCycle). This eventually caused an invalid property exception which caused the BatchCycleUpdater to fail.

• For editing the mine model in Site Editor, it is now configurable to load the z-values from the surface, which is the default, or from the currently loaded DXF files as it was in MineStar v3.1. The user can see the z-value to be used in the coordinates panel at the bottom of the Site Editor screen.

• Manual assignments are now considered active, which means scheduled manual assignments are properly handled when determining if an assignment is locked. A truck assignment is locked when the truck is in same the lane/waypoint which requested the previous assignment. For example, if a truck state changes at the same waypoint which prompts two assignment requests, then the truck first assignment will not be overridden.

• Trucks which are sent an assignment and are not in radio contact can have the same assignment resent by the controller. The controller is now informed when an assignment sent to the truck fails due to poor radio contact. This resolves an issue where trucks are sent an assignment while outside of radio contact cannot have the same assignment resent because the assignment is a duplicate.

• The Schedule Break Editor no longer creates multiple records when creating a schedule break with multiple sessions.

• It is now possible to create a load-out unit and then refresh Site Editor and generate a Machine-Type onboard file. Previously machine-type dimension errors interfered with this process.

Health

• VimsPcsCycle2 messages are correctly processed by MineStar.

• Updated to resolve the issue where VIMS3G data is causing issues with Trend Config view and Histogram Config view (Update for HE010 reports).

• Updated the VIMS definitions to v13.0.0 (Fourth release).

• TMAC Message Log files will be downloaded from supporting machines.

• Corrected CID description for TPI Diagnostic Events.

Release Notes for 3.1.1-37

Release Notes for 3.1.1-37 are listed below:

Fleet

• Operators were unable to log in to auxiliary machines. This resulted in a ClassCastException occurring in the MineTracking log.

• The operator column in the Fleet Update Assistant is shown as "currentOperator.label". This has been corrected to show "Operator" as in previous versions of MineStar.

• MineStar does not process messages from the machines which are not configured in the system. But the FCM page should display the unknown machine URLs as it is required for site awareness.

• The CycleGenerator is not correctly reconciling a Delay with a Cycle if the Delay exactly matched the time period of the Cycle. This resulted in a WARNING message and a Cycle Activity of "Machine.Delay" being associated with the Cycle instead of the correct Cycle Delay.

• Corrected the issues in setting up a standby server and in particular with "Localising text: language code is en, country code is 1" creates extra logging. This is not expected by the eval() function as it expects "Integer value". The update trims off the string part and the integer value is passed ahead.

• Ensure that still the process state (waypoint) changes as long as the state change event is older the last update to the waypoint from a PR.

• Update the haulage map to handle unreachable destinations.

• Updated to resolve an issue with operators unable to log on to Auxiliary machines.

• If periods (for example: Day, Week, and Month) are set with the offset of 1 (finish date), then period selections will organize by shifts finishing in the selected period. This will allow all the period selectors to work correctly where periods are specified by finish time rather than start time. Also the shift label in the shift change editor defines the start and finish times of the shift to avoid ambiguity where sites have the finish time offset (1).

• Improved the way the Truck (and Auxiliary) tabs try to get the OnDelay status of the machines, so they retrieve more accurate and up-to-date information.

• The selection of the destination has been changed from a combo-box, to a popup to allow searching and filtering for easier selection.

Health

• Performance issues are addressed in the Jobs-Running Page. Showing the details of a currently running job would cause the client to freeze and run out of memory. This has been addressed.

• Updated to resolve the issue with not processing VimsTpmsCycle message from TPI device.

• Update to VIMS master database version 13.0.0, which provides the following enhancements:

- New UIDs for APECS support (issue #350)

- Added bitmap UIDs that are missed in the previous release

- Expanded event description from 80 to 255 chars (issue #356)

- Improvement made to "Forward Time: Gear 2" unit issue (issue # 349)

- 773E: Added new Histograms (9970 - 9982)

- 777F: Correct Actuate values for Event 13286 (Body Up) and 13231 (Ground Speed)

- 793D Mule: Added new event (13230 - Trn Oil Temp)

- 773F and 775F: Added new Events (13232-Trn Output Speed and 13233-Ground Speed)

- 773E: Added new Events (13234 - 13237 Engine Speed)

- 793D (High Altitude): Added new Altitude Derate event (13238)

- Hitachi Shovels, Ex-6 series

- Bucyrus Rope Shovels, 495

- Bucyrus Hydraulic Shovels, RH340B, RH400

- Liebherr Excavator

Release Notes for 3.1.1-34

Release Notes for 3.1.1-34 are listed below:

Fleet

• Updated to resolve several compatibility issues with the DataShare feature.

• Updated to resolve an issue with scheduled jobs being stacked up when a job takes a long time to run (for example: VIMS Import Job). The job is now skipped if another instance is still running. The user can configure this feature in supervisor.

• Updated to resolve an issue where a new operator is unable to be logged on to a machine.

• Updated to resolve an issue where the "Process Logs Directory" setting in Supervisor is not being set correctly.

• Updated to resolve an issue where the handling of tie-down to loading tools is not working correctly for machines that did not have the location set correctly.

Health

• Provided unit conversion based on localization settings for VIMS health event worst and first values.

• Corrected the decoding of Air Filter and Parking Brake channel and trend data.

• Improved the processing of HS3 VIMS reports containing undefined histograms.

• Updated to resolve an issue where the arrival time of Health events sourced from a VIMS EC3 report to the download time of the report is not set correctly.

• There is now support for additional transmission trends available on F series Large Mining Trucks with VIMS 3G NFF.

• VIMS file download now produces a single request at a time even after receiving an error from an VIMS 3G NFF device.

• Newer generation VIMS 3G units encourage a valid time zone to be set during VIMS configuration with Cat^® Electronic Technician (Cat ET). This change requires that MineStar Office communicates its time zone when attempting to synchronize the clock between device and MineStar office.

The clock synchronization can be performed the following ways:

- Through the Synchronize VIMS clock with office job.

- During VIMS file download if default Set VIMS clock supervisor option for VIMS file downloads.

- Between TOPE and VIMS via iDesk.

- Between VIMS and GPS.

This improvement adds an option to methods 1 & 2 will optionally include the time zone information of the MineStar Office installation.

Release Notes for 3.1.1-32

Release Notes for 3.1.1-32 are listed below:

Fleet

• Improved calculation time of "Recal Cycles KPI Summaries".

• The message group editor only allows for a limited set of machine classes for associations. This is resolved to use the same association list as is available in the Machine State Editor.

• Ensure that the mandatory title field has a value when sending an operator message.

• Updated to resolve an issue where on occasion operators could not log into machines, with error "ID already logged into another machine".

• Improved handling of daylight savings change over.

• Updated to resolve an issue with shovels not being marked as "unavailable for assignment" on shutdown.

• Improved the performance of the "delay finder".

• Updated to resolve an issue where the "Time Until Fuel Critical", and "Time Until Refuel" are not displayed consistent time format.

• Updated to resolve an issue where some messages from the office were delayed by up to an hour before going out to the machines.

• Updated to resolve an issue where files marked with the system attribute in Platforms.xml were being added to the build cards of all machine platforms.

• Updated to resolve an issue where on occasion, when attempting to log in to a machine, the operator is rejected as not having a valid license for the machine, even though in MineStar shows that the operator is licensed for the correctly.

• Updated to resolve an issue with archiving machines that were referenced in any existing templates.

• Updated to resolve an issue where the standby snapshots were being copied to an incorrect location.

• Updated to resolve a potential issue that could lead to an error in the delay deletion process.

• Updated to resolve an issue in the onboard file assistant, where light vehicles could not receive all applicable machine files (Activities, and Delays).

• Updated to resolve an issue where machines would not receive zone update messages, despite being configured with an onboard platform that receives zone machine files.

• Assignment calculates the optimal destination for a truck by considering a dynamic system of mine model parameters including material constraints, production requirements, and travel times. The travel times of a truck are important in the decision making process to optimize mine site production. Situations in under trucked areas of the mine require a greater utilization of the production requirements rather than shortest path algorithm in the decision making process to improve the production of the mine.

Under trucked sites can now achieve improved production with new penalty options in the Assignment Supervisor. Assignment Strategies (Assignment Supervisor > Policies) allows users to add values which will discourage over production and under production along between loader-dump combinations. Setting these options to a small value (For example: 0) enables Assignment to place a greater emphasis assigning trucks to the loader-dump combinations with the shorter travel times. Larger values in these new options enable assignment to distribute trucks across the shorter and long.

• Removed PC as a Configuration Name option for Machines since support for this platform has been deprecated.

• Updated to resolve an issue where ServiceMeterReading does not use Production_Event Values.

• Added timezone information in the VimsClockSet2 message for VIMS 3G.

• Before restoring a Road Segment, the system checks if any waypoint references that Road Segment. If it does, an error message is displayed stating the name of the inactive waypoints that references the Road Segment, preventing restoration.

• Updated to resolve an issue where Contents > Assignment > Decision Support was not being updated with changes to Restrictions.

• Improvements have been made to respect the priority of an alarm type and escalate it from there.

• Updated to resolve an issue where if a cycle was edited in the assistant, it would also appear in the monitor. This would make it difficult for the controller to monitor loads dumped.

• Added condition, so that when a machine goes from "in contact" to "out of contact", the last message (old message) does not get added to the buffer which would cause office lag.

• Improvements have been made to extend the "Infill" feature to include final roads at dumps.

• Allow truck tie down to a loader, if loader is at a station. Also make sure that the assignment message to the truck contains the loader and location in the destName if the tie down is to a loader at a station.

• When a road is deleted/archived, delete any delays that target the road.

• Improved the Grade Block Import/Export process by exporting all blocks for higher levels in the hierarchy.

• Updated to resolve an issue where modifying a cycle caused the system to add "nominal material moved" each time the cycle was modified.

• Updated to resolve an issue where splitting of Drill delays across cycle boundaries was not working correctly. The "not determined" delay time was being displayed as "available" time.

• Updated to resolve an issue where the Mine Block Job tab would take a long time to be displayed.

Health

• Improved performance in determining FMI values.

• Added support for the VIMS 11.0.5 Master database update.

• Updated to resolve an issue where VIMS 3G import fails, when "Create Service Meter Reading" option is checked.

• Updated to resolve an issue where ServiceMeterReading does not use Production_Event Values.

• Updated to resolve an issue where a user was unable to import VIMS 3G NFF TR3 files.

• Added support for new payload and retarder VIMS channels.

• Added support for FPO calculation for Continuous Loggers.

• Updated to resolve an issue where the tzBias value were not being set to zero when synchronize VIMS clock with office job is run when both timezone and send in UTC options were selected.