Skip to content

Importing datasource configurations for MindConnect Nano

To receive the data from the MindConnect Nano, you need to add datasource configurations with a datapoint. This can also done by uploading datasource file or uploading a updated template file.

Prerequisites

The prerequisites to configure the data sources are:

  • Asset and aspect are created.
  • MindConnect Nano is connected.
  • Prepare a file to import according to the following guidelines.
  • Check the structure in the template file. It differs for each plugin type.
  • The mapping notation should be in following format : AssetName->AspectName->VariableName.

Procedure

To import the datasource configuration for an asset of the type MindConnect Nano, follow these steps:

  1. In the "Assets" tab, select the asset.

  2. Click MindConnect Nano plugin. For example, "MindConnect Nano".

  3. In "Datasource Configuration" view, click "Import" to import a configuration file.

    import-configuration-Nano

  4. In the "Import File" tab, click "Browse" and select the data source configuration file and click Next step.

    Import Datasources

    Note

    Import now supports uploading of XML file only for OPCUA datasource configuration.

  5. After browsing the datasource configuration, check the preview and modify the datasource information and click Next step.

    Import Datasources 2

    Note

    • To check the format of the data configuration file before importing the configuration, download the template file by clicking download template.
    • The template file consists of an example data configuration. In the below given screenshot, the information related to data source and datapoint declarations for S7 and it can switch to each protocol from the bottom of the file (e.g S7, OpcUa, modbus-tcp, etc).
    • "Export" option makes the user to export the existing data source configuration of an asset, where the existing data source configuration is exported as file and can be imported to overwrite or add to the existing configuration.
      Export option
    • The supported protocols for import and export configurations are S7, OPC UA, Modbus-TCP, Modbus-RTU, Rockwell and System.
    • For OPC UA Data source, configurations like OPC UA security certificates need to be added manually and are not supported via export and import.

    Warning

    In the event of failed datasource validation, the import of datasource and the datapoints of datasource is skipped. However, if the error is on the datapoint level then the respective datapoint is skipped.

  6. To delete and add new data configuration, select "Overwrite existing configuration" or to add new data configuration to the existing data configuration, select "Add to existing configuration" and Click "Start import".

Import datasource 1

The latest import feature now supports the import of Multimapped datapoints, allowing upto 5 datapoints mapped with a variable. The below image displays the import file details.
import-and-export-configuration-iot2040
① Data source configuration information
② Datapoint mapping information (optional)

Note

  • Track the errors or warnings from “Import Configuration” or “Export Configuration”.
  • If the values for datasource Import and Export are not specified during import replace the values by default values. For the list of default values, refer to Default values for datasource Import and Export.

Result

Data source configuration are imported with mapped datapoints. The new data sources is available at the asset details of MindConnect IoT2040. Datamapping is available at the corresponding datapoints.

data-source-configuration-imported-nano

  • Asset name needs to be unique in the environment. If multiple assets are with the same name in the environment, then the datapoint mappings may have discrepancy.
  • Asset needs to be available before importing the configuration. Asset will not be created during import configuration.
  • Datapoint name needs to be unique in excel sheet across data sources and protocols.
  • Datapoint mapping of a datapoint with multiple variables of multiple assets is not supported.
  • Importing of datapoint mappings is an async process.

Info

The mapping process is performed asynchronously, once the import operation is finalized. Depending on the data size, the mapping creation process will vary on time.

Limitations of Import features

The limitations of Import feature are,

  • Refreshing the browser page during import will interrupt the import process.
  • Leading space characters in the AssetName field can result in mapping issues during Excel export and import procedures.
  • Ensure reading cycle has integer values before importing.
  • Double-check the hysteresis values as per the data type.
  • For boolean fields, any values other than true will be imported as false.
  • Non mandatory fields will be imported as blank in case fields are not specified.
  • Validate that the Asset, Aspects and variable exists in the tenant before importing.
Last update: May 8, 2025