Loadscan Integration

Reference data groups can be configured to allow integration between Pitram and Loadscan 3D volumetric scanners. Information on payload weight, distribution and density is automatically collected by defining the integration between Pitram and the Loadscan system.

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.

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

The Integrations groups in the Reference Data Deployment dialog

To access the Integrations configuration screens:

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

Integration

An Integration token needs to be defined for Loadscan integration. The code of the token should be set to “LOADSCAN“.

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

The following parameters must be configured:

An Integration Mapping token needs 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.

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, the Loadscan integration.

Select the Pitram Reference Group for the mapping from the drop down provided.

Use the Pitram Reference Token drop down to select the relevant token from the selected reference group.

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.

General Configuration

The GeneralConfiguration.xml file is found in the root folder of where the Loadscan Connector is installed e.g. C:\Program Files (x86)\Micromine Pty Ltd\Loadscan Connector.

The following details are set in the configuration file:

Field Definition
LoadscanAddress The web address of the MyScanner API to retrieve the payload information from. Defaults to https://www.loadscan.com

Note: While provided, the LoadscanAddress under normal operation should not be changed as the provided service is not hosted by the mine site but instead by Loadscan.
SerialNumbers A list of serial numbers that the Loadscan should query
MyScannerToken The token that has been configured in MyScanner that grants access to the configured scanners
PollingIntervalSeconds How often the connector will query the API, the default is 60 seconds
ShiftRoster The roster code to submit the equipment payload events with
MeasureCode The code of the measure that is the target measure of the payload event
SourceMeasureCode The code of the measure the Loadscan device is recording in (it appears that this is tonnes)
TraceLevel The level of trace to write to the log files. Values can be Off, Error, Warning, Info, Verbose. Defaults to Error
NumberOfDaysToKeepTracing Defines how old a file must be before it is deleted. Defaults to 14 days
PRIS_Server Address to the PRIS server used to submit the equipment payload events
UseTokenAuthentication Whether or not token authentication should be used when accessing PRIS
TokenAuthenticationUsername The user name that should be used to authenticate access to PRIS
TokenAuthenticationPassword The password that should be used to authenticate access to PRIS
TokenAuthenticationClientId The identifier of the client as configured in Pitram Portal > System > Manage Connectors
TokenAuthenticationDeviceId The identifier of the device that the application is running on
SendCarrybackAdjustment Send payload readings specifically marked as carryback

Note: While provided, the LoadscanAddress under normal operation should not be changed as the provided service is not hosted by the mine site but instead by Loadscan.

Database Marker Configuration

The DatabaseMarkerConfiguration.xml file is found in the root folder of where the Loadscan Connector is installed e.g. C:\Program Files (x86)\Micromine Pty Ltd\Loadscan Connector.

  • DatabaseMarkers – A list of the times the Loadscan Connector last queried the API for information keyed on the scanners id.