CONNECTOR 1270593 - Caterpillar

The store and forward functionality for Cat® MineStar System was introduced to improve the two main scenarios associated with network outages:Scenario 1 – Temporary Communication Outage
A Temporary Communication Outage is normally associated with an area of the mine that does not have adequate network coverage to support communications in any form (black spot or spotty communications).Scenario 2 – Complete Communication Outage
Complete Communications Outage is a situation where communications between MineStar Office and one or many of the machines in the field is disrupted.This functionality has been designed to ensure that the minimum data requirements are met to enable creation of Cycle data in MineStar.Note: The functionality described here will never replace a well maintained Radio Network at site. The radio network should adhere to the Caterpillar recommended minimum requirements as per the requirements for your Application (Cat® Fleet, Cat® Detect, Autonomy and so on).Cycle States and Delay Data
The store and forward functionality from Fleet Onboard will retain State Change TMAC messages that have not been acknowledged by the MineStar Office system. Which means that during a period of a communications outage, the system will be able to record Truck states and all delay start and end times. The Truck states include "Dumping", "Traveling Empty" and so on.The quality of the stored data depends on the length of outage. If the outage is longer than the configured retry time of the state change message to the Office, the stored messages will be sent when the machine returns to good communications. But the messages will only contain basic information to complete the machine cycles. This includes all physical state changes and all delays entered during the outage time. There will be no soft state changes or actual road segments, and the cycles will use predicted materials and grades. In addition, the user logged in to the onboard display prior to the outage will be maintained for the recorded cycles.Configuration
Fleet Onboard activates the functionality by adding the key "$ MineStar Message Queue Retry 8505", which is the only key required to activate the functionality.Note: The following key must be removed when activating the Store and Forward function.
"$ MineStar Message 8505 =xx xxxxx x"
Table 1
Add "$ Minestar Message Queue Retry 8505"
Remove "$ Minestar Message 8505 =xx xxxxx x" The minimum requirements for Fleet Onboard Message retries are shown below:
"$ Minestar Message =20 20000 0"
"$ Minestar Message 48128 =7 1000 0"
"$ Minestar Message 48129 =7 1000 0"
"$ Minestar Message 8503 =7 1000 0"
"$ Minestar Message 8512 =7 1000 0"
"$ Minestar Message 8601 =7 1000 0"Version Compatibility and Known Limitations/Issues
Full Compatibility
Table 2
Onboard Software Office Software
CMPD – v3.8 and later Version 5.0 and later
G407 – v4.6 and later Partial Compatibility
Table 3
Issue Description Versions Affected Symptom
Delay Ending at Message Arrival Time not Timestamp time All Office versions Prior to 5.0 Delay will end when the message arrives in the office causing a mismatch with actual delay time.
Multiple assignments sent from office when machine is back in communications All Office versions Prior to 5.0 When there