Komatsu Integration

Reference data groups can be configured to allow integration between Pitram and Komatsu vehicle remote monitoring via CAN Bus.

Komatsu integration is designed as a direct replacement for sites currently using the SKZ integration. Like SKZ, it collects operational data from the truck’s CAN bus and generates the same set of Pitram events - such as fuel level, payload, engine hours, odometer readings, and cycle states (loading, hauling, traveling empty). This ensures a seamless transition for existing sites, with all key metrics and event logic preserved, while leveraging a dedicated Komatsu hardware profile and updated integration mapping for improved flexibility and maintainability.

For users, this means that the Komatsu integration will feel familiar, providing the same automated capture and reporting of truck metrics as SKZ, but with enhanced support for different Komatsu models and future updates. The system continues to use smoothing algorithms to handle fluctuating values (such as fuel level) and supports flexible configuration to accommodate different truck models and evolving DBC file versions.

The following information outlines how to configure Equipment Health Device and Komatsu device integration.

Reference Data Deployment

The following Mobile attributes should be deployed:

  • MobileSettings →KomatsuProfile

  • MobileUnitConfiguration

    • KomatsuProfile

    • EquipmentHealthProfile

  • Integrations

    • Integration

    • IntegrationMapping

    • IntegrationMappingAttributes

    • IntegrationCommand

    • AuxiliarySignals

The integration requires groups of reference data to be deployed:

  • Integration - Defines the integrations available.

  • IntegrationMapping - The mapping between Pitram tokens and tokens used in 3rd party integrations.

  • IntegrationMappingAttributes - Mapping between the Integration and the Pitram reference group and attribute.

  • IntegrationCommand - Contains pre-deployed reference data tokens representing the supported integrations.

  • AuxiliarySignals - Contains pre-deployed reference data tokens representing the supported signals.

To enable integration in Data Acquisition, reference groups must be deployed from Reference Edit.

To access the Integrations configuration screens:

Click on the Reference Edit icon to open the Reference Data service:

When these groups have been deployed, the Load Default Auxiliary Signals and Integration Commands option will be available from the Reference Edit → Other Actions menu.

You can load the Default Auxiliary Signals using the option:

DBC File

In Asset Health or Reference Data → Settings → DBC File, import the standard J1939 DBC file as well as the Komatsu DBC file and publish, noting the name of the CustomOrigin used for the Komatsu DBC

Note: To follow the procedure outlined below, use CustomOrigin = komatsu_HD465

  • If Asset Health is Enabled - publish via the Asset Health → Configuration → Reading Definitions screen.

  • If Asset Health is Disabled - publish via the Reference Data Settings → DBC File screen.

Mobile Profile

A new profile for Komatsu KOMTRAX (KomatsuProfile) needs to be defined/created using the KomatsuProfile reference attribute.

  1. Navigate to Mobile Settings → KomatsuProfile.

  2. Check Out the table and,

  3. Click New.

The following parameters must be configured:

Integration

An Integration token needs to be defined for each Komatsu equipment integration; e.g. KOMATSU_HD465.

The configuration screen lists the existing Integrations. To create a new Integration, Checkout the table and click New.

The following parameters must be configured:

Integration Mapping tokens need to be defined for each equipment used in the integration and measure codes for the configured source and target measures.

In the Integration Mapping configuration screen, Checkout the table and click New to create a new Integration Mapping.

For example, for the KOMATSU_HD465 Engine Hours reading, the following parameters must be configured. Mandatory attributes appear asterisked and in red:

Enter the applicable 3rd Party ID for the Integration in the field provided.

The Integration drop down is used to select the associated Integration to be mapped - in this example, KomatsuHD465 integration.

Select the Pitram Reference Group for the mapping from the drop down provided. For Komatsu Engine Hours integration, this is Measure.

Use the Pitram Reference Token drop down to select the relevant token from the selected reference group. For Komatsu Engine Hours integration, this is Engine Hours.

The Convert Cumulative To Summed field is used to configure whether to convert cumulative signal into a summed measure. It does this by using the difference between the value and the previous value. Defaults to off (0), specify 1 to turn on.

Use the Create Measure If Unchanged field to configure whether to create a measure if the signal has not changed. Defaults to off (0), specify 1 to turn on.

The Create Measure Frequency field is used to configure the time interval, in seconds, that needs to pass before a measure is created. Set to 0 to create measures for every sample.

Mobile Unit Configuration

With the Integration Profile and the Equipment Health Profile configured, you can configure the Mobile Unit Configuration for your Komatsu integration.

Select the required Equipment and set the KomatsuProfile and EquipmentHealthProfile to the reference data tokens that have been created/imported. In this example: 

  • EquipmentHealthProfile = Komatsu HD465 CAN Log File

  • KomatsuProfile = KomatsuHD465

Equipment Health Profile

An Equipment Health Profile for Komatsu integration must be imported/created if you have enabled Asset Heath. For Komatsu Integration, the profile is configured with the FileImport API Type.

The following parameters are configured in Reference Data using Configuration Items → Mobile Settings → EquipmentHealthProfile:

Note: DeviceID may need to be modified depending on other devices on the CAN bus.

Publish

Check in and publish all of the changes to Reference Data.

When you open Mobile for the Equipment that has been assigned the Komatsu profile, if the configuration was applied successfully, Komatsu Hardware Devices should be available in Mobile.

Note: The above is TEST data and for illustration purposes only.