Master file and Configuration file keys are still set in the respective files for each. The MCU contains default settings for each machine type. All new machines created in Cat MineStar System need editing in the MCU. The minimum extra settings needed are security keys and codes.
Reference: For information about creating machines, refer to the "MCU Getting Started Guide". The guide also contains a tutorial for first-time users. The guide is located in "Start" > "Programs" > "Cat MineStar System and Tools" > "Machine Configuration Utility" > "Getting Started Guide".
Upgrade a Pre v4.0 Machine Configuration
When a machine is imported into Cat MineStar System, a new directory is created for the machine.
All existing machines created in Cat MineStar System need editing in the MCU. The minimum extra settings needed are upgraded security keys and codes.
Reference: For information about importing legacy machines, refer to the "MCU Getting Started Guide".
Security Upgrade for Existing Machines
The software security that allows the on-board application to run is stored in the machine configuration file.
Note: Software Security was changed in CAESultra version 2003.1.0
When an existing machine is upgraded to CAESultra version 2003.1.0 or later, then new security setting codes must be entered in the MCU.
Note: Failure to remove old security settings will result in the machine configuration file functioning as a previous version with no upgraded features.
The on-board software supports the use of the following communication protocols:
File Transfer Protocol (FTP) - Configures the office to use only FTP for communication with the machines. This option is the same as the IP option that is available in v3.1 and earlier on-board software. FTP is the default protocol that is used by the on-board software.
User Datagram Protocol (UDP) ) - File transfer over TMAC: Configures the office to use only UDP for communication with the machines. This option cannot be used if machines prior to v3.2 are in use on the site.
UDP is designed primarily for use with the TC900 radio network. Reliable UDP significantly improves file transfer rates over the TC900 radio network compared to FTP.
In v4.0, file transfer over TMAC (UDP file transfer protocol) is not supported for any machines. However, UDP is still used for other functions, for example messaging.
Existing machines using UDP communications protocol are automatically reconfigured by the MCU to use FTP. No intervention is required by the end user or the installer. There is no notification that this change has occurred.
Note: The MCU automatically sets the "Office Comms Protocol" setting in the mach_cfg.txt file.
Optional Settings for the On-board Software
This section provides a short description of both the setup and use of some of the optional machine configuration settings.
The system may be interfaced to either the satellite receiver or a third-party positioning device.
When interfaced to a satellite receiver, the on-board software uses the GPS week and GPS seconds that are supplied by the receiver. These settings are used to determine both current UTC date and time. For the on-board software to provide local time, a local time offset (in minutes) must be supplied.
"Time Zone Minutes" - The "Time Zone Minutes" is the number of minutes that the local time is offset from Greenwich Mean Time (GMT)
"Standard Time Date" - Specifies information regarding the change from daylight savings to standard time
"Daylight Time Date" - Specifies information regarding the change from standard time to daylight savings time
Use the "Time Zone Minutes" setting to define the offset to local time. Both the on-board clock and the clock in the display are set once the local date and time are calculated. The on-board software requires either a fixed position or float position solution before date and time are calculated.
When interfaced to a third-party positioning device, the system requires the NMEA ZDA date and time message. The position and the date and time are not updated until a good NMEA ZDA and a fixed position solution or float position solution are provided. The on-board software extracts the time and date from the ZDA message. Any time zone information in the ZDA message is ignored.
For the on-board software to provide local time, a local time offset must be supplied. Use the "Time Zone Minutes" setting to define the offset to local time. Both the on-board clock and the clock in the display are set once the local date and time are calculated.
"GPS Time Resync Interval" - This setting is used to modify the interval at which the clocks are synchronized with time from the positioning system. Both the local date and the local time are updated every 60 seconds by default in the on-board clock and the clock in the display.
"GPS Time Resync Threshold" - Use this setting to modify the threshold within which time synchronization is expected. The on-board software provides a warning if the clock is not synchronized again within 1 hour.
"Diag Include Message n =GPS week and GPS seconds" (41021) - When the clock is synchronized again, a message can be logged by using this setting. This message will also list the GPS week and GPS seconds which may be useful for testing.
As discussed above, positions will not be generated from a third-party device input until valid ZDA messages are received. A message is added to the log file advising that a valid ZDA is required when using a third-party position device.
The ZDA is used to ensure that the date and time are accurately set up during startup. If ZDA messages later cease, the on-board software continues to use the UTC time in the third-party position message for time synchronization. The on-board software logs a warning after 30 minutes with no ZDA input.
Note: Productivity measurement is not started until the on-board software has determined a date and time.
Data such as productivity records are time stamped with UTC time rather than local time. The operating system used for the office system must be configured with the same time zone as the machines. This requirement ensures that correct dates and times are reported in the office.
The internal clock in the display module, like all PC clocks, is prone to drift. The date and time can also be incorrectly set in the BIOS of the display.
The on-board software uses GPS Time to maintain the date and time on the display while the on-board software is running. Using GPS Time ensures that accurate date and time are used in data time stamps. The use of GPS Time also ensures that all machine times are exactly synchronized. Accurate and synchronized time is critical to productivity reports and peer to peer updates.
The on-board software uses the GPS seconds that are embedded in the position message from the satellite receiver. The on-board software uses the National Marine Electronics Association (NMEA) ZDA sentence for date and time synchronization when a third-party position system is used.
At startup the on-board software requires a valid position, date, and time. Positioning will not start on third-party systems until the system has received an NMEA ZDA sentence and has decoded date and time from the sentence.
Once the on-board software is started, the clock in the display is continually synchronized with the GPS Time. If the synchronization between the clock of the display and the satellite receiver has a difference greater than 5 seconds, an error is written. The error goes to the productivity files and the diagnostic message log file.
The error may indicate that there are problems with the CMOS battery or the clock of the display. If the time synchronization fails for some reason, system will continue to use the clock time in the display. A warning message is posted to the diagnostic file each time the maximum delay between clock synchronization is exceeded. The default maximum delay is 10 minutes.
Reference: Refer to "G610 Display Ethernet Port Activation" section of this manual in the "Incorrect Dates" and "Battery Failure Message" sections for additional information.
The following settings can be used to control functions regarding the GPS Time.
"GPS Time Resync Threshold" - This setting sets the threshold for the warning message.
"GPS Time Resync Interval" - This setting sets the synchronization rate.
"Diag Include Message" - This setting displays a counter in milliseconds in the diagnostics log file.
Login and user settings provide some useful data to operations and maintenance personnel.
Reference: For additional information on login procedures, refer to the MCU Help file, "Login and User Settings - Reference".
"Login Required" - This setting displays the "Login confirmation" dialog when the system is started.
"Save User" - This setting specifies whether to save the identity of the operator when the system is shut down.
When the two settings above are set, the system records the user that is logged in when the machine is shut down. This login is helpful during situations such as refueling when the machine will be shut down. At startup, the machine will recall who was logged in prior to the shutdown.
"Hours Required" - This setting displays the "Hour entry" dialog when a new operator signs in. Enable this setting to force the operator to input the machine hours prior to using the on-board software.
The following settings are associated with productivity on the machine.
"Volume Design Limited" - This setting limits volume calculations between subsequent passes to the area that is covered by the Primary Elevation design.
| |
| Illustration 1 | g01415930 |
|
Operation of "Volume Design Limited" setting (1) Pass 1 (2) Pass 2 (3) Primary Elevation | |
"Utilization Stationary Threshold" - This setting sets the number of seconds that a machine has to be stationary before the productivity calculation begins to accumulate stationary time.
"Dozer Cycle Minimum Leg Distance" - This setting sets the minimum distance for a forward log or a reverse leg in order for the cycles to be considered valid.
"Dozer Cycle Minimum Leg Points" - This setting sets the minimum number of move positions for a forward leg or a reverse leg to considered valid.
"Dozer Cycle Distance Tolerance" - This setting sets the percentage of the reverse leg distance that is used to validate a Dozer cycle.
The settings in Table 1 can be used to configure the way track-type tractor cycles will be determined.
Note: The units for the three settings below are in meters.
| Track-type Tractor Cycles | |
| Dozer Cycle Minimum Leg Distance =10.0
Dozer Cycle Minimum Leg Points =5 Dozer Cycle Distance Tolerance =100 |
|
Screens - This feature limits an operator form being able to access specific on-board screens that are displaying the Terrain productivity information.
The settings in Table 2 prevent operator access to Utilization Cycle Volume information.
| Disable Screen Access | |
| "Disable Screen Utilization"
"Disable Screen Cycle" "Disable Screen Volume" |
|
Reference: For additional information on productivity, refer to Systems Operation, "Productivity File" in this manual.
Sometimes the interface between Modular Mining System (MMS) and the on-board software presents an error message to MMS. The on-board software can record and play back MMS data to help troubleshoot problems in the interface.
- In the MCU, select "3rd Party Dispatch Interface" > "Modular Mining System" > "File Options" > "MMS File Options".
- Select "Write" from the drop-down menu.
- Send the mach_cfg.txt file to the machine.
- Check that the mach_cfg.txt file has been transferred. For example, use the file transfer messages in the office software.
- Ensure that the on-board system and MMS system are correctly connected.
- Restart the on-board software. The software records MMS data to the following files in the \caes\temp directory on the machine:
"mmsrx.bin" - Contains raw binary data received from MMS
"mmsrx.txt" - Contains MMS messages recorded for review
- Stop the on-board software to stop the recording.
- In the \caes\temp directory, rename the file "mmsrx.bin" to "mmsinput.bin".
- In the MCU, select third Party Dispatch Interface > Modular Mining System > File Options > MMS File Options.
- Select "Read" from the drop-down menu.
- Send the mach_cfg.txt file to the machine.
- Ensure that the mach_cfg.txt file has been transferred. For example, use the file transfer messages in the office software.
- Restart the on-board software. The on-board software plays the MMS data contained in the "mmsinput.bin" file.
- Stop the on-board software once sufficient data has displayed.
When the problem is resolved, deselect the "MMS File Options" checkbox, resend the mach_cfg.txt file, and restart the on-board system. These actions stop the on-board software from recording more MMS data.
"Send Loads To MMS" - This setting enables information from the "Dispatch" system of the Modular Mining System
"Baud" - This setting sets the baud rate for the serial ports that are available to the on-board software.
The settings in Table 3 must be used if communications with MMS are desired.
| Modular Mining Settings | |
| "Send Loads To MMS"
"Baud 1" |
|
Automatic Ore Status Maintenance Settings
Automatic ore status maintenance settings create a "OreStat.cat" file. The new settings are created under either of the following conditions:
- A design file with a different group association becomes the primary file.
- A machine begins working on a new, predefined elevation.
If the elevation mode is selected, then settings must be used to assign specific benches. Specific benches are defined by explicitly naming the bench elevations. The benches are also defined by providing a base elevation and an offset from that elevation for subsequent benches.
If the group mode is selected, then the system creates and uses a different "OreStat.cat" file for each group associated with the primary material design files. By default, the system creates only one "OreStat.cat" file regardless of either the elevation or the group association of the file.
Note: This setting is only an on-board setting. The groups in the office are not affected by this selection.
"Ore Status Maint Enable" - This setting enables automatic Ore Status file update. Values are "L" = Level, "G" = Group, or "Off". In the following code, automatic ore status maintenance will be based on the group of the "Prime" Material Design.
"Ore Status Maint Retention" - This setting sets the number of "OreStat.cat" files that the on-board software will retain for automatic ore status maintenance. In the following example, up to five "OreStat.cat" files will be retained by the on-board software.
"Ore Status Maint Retention =5"
"Elevation Base" - This setting sets the reference elevation for the "Elevation Offset" setting.
"Elevation Offset" - This setting sets the increment from the reference elevation specified by the "Elevation Base" setting.
"Elevation Level" - This setting explicitly defines elevation levels that are to be used for automatic ore status maintenance.
"Elevation Level Range" - This setting defines the range between which the on-board software considers a machine to be at a given elevation.
"Elevation Residency Threshold" - This setting defines the time period that a machine must be in the range of an elevation level for the range to be considered valid.
Two methods, one for uniform benches and the other for irregular benches are used to set the bench elevation. Refer to Table 4 for the required code for each of these methods.
Note: In the syntax for the next eight settings, the "#" character represents the elevation in meters.
| Uniform Benches using Base/Offset Method | |
| Elevation Base =#
Elevation Offset =# |
|
| Irregular Benches | |
| Elevation Level 0 =#
Elevation Level 1 =# Elevation Level 2 =# Elevation Level 3 =# Elevation Level Range =50 Elevation Residency Threshold =30 |
|
Reference: For additional information on automatic ore status settings, refer to "Automatic Ore Status Maintenance" section of this manual or to the MCU Help file, "Automatic Ore Status Maintenance - Reference".