Introduction

A BMENOR2200H module stores its configuration in an .xml file. You can use the import and export functions in the Control Expert DTM to share that file among different modules to implement the same configuration.

Use the Control Expert EXPORT/IMPORT functionality:

  • export: Record the module and protocol configurations into an .xml file.

  • import: Import .xml files that include configuration parameters and data mapping to one or more modules.

Use Cases

These practical examples represent some common implementations of the import and export functions:

Use Case

Action

Redundant Configuration

1

Export the .xml configuration file from a BMENOR2200H module.

2

Import the .xml configuration file to one or more BMENOR2200H modules.

3

Reuse the BMENOR2200H module’s configuration file in other BMENOR2200H modules

Project Migration

Migrate the configuration file from a BMXNOR0200H module to a BMENOR2200H module.

NOTE: All located addresses are lost after the import of .xml files from the BMXNOR0200H module. The type and length of the name are changed according to the new format. Account for the data type substitutions that are required when you migrate the XML file.

Import

Import an .xml configuration file:

Step

Action

1

Access the DTM configuration for your module.

2

In the CONFIGURATION menu, expand ( +) the General sub-menu.

3

Select Export / Import.

4

In the Import / Export dialog, click the Browse button in the Import File Name field to find the .xml configuration file name path you want to import, located on your local or network drive.

5

Select the respective configuration file and click the Open button to enter the file name path for the Import File Name field.

6

Select or deselect the Use system defined data mapping point names check box:

  • selected: The import setting allows you to import user-defined mapping point names.

  • deselected: Data mapping point name is assigned based on point type, point number, and point count.

7

Select the Import button.

8

Select Apply to record your changes, or select OK to record your changes and close the dialog.

Export

Export an .xml configuration file:

Step

Action

1

Access the DTM configuration for your module.

2

In the CONFIGURATION menu, expand ( +) the General sub-menu.

3

Select Export / Import.

4

In the Import / Export dialog, copy/paste the path file name of the .xml configuration file saved from the BMENOR module and protocol parameters, which you want to export to a local drive, in the Import File Name field.

5

Select or deselect the Use system defined data mapping point names check box:

  • selected: The import setting allows you to import user-defined mapping point names.

  • deselected: Data mapping point name is assigned based on point type, point number, and point count.

6

Select the Export button.

NOTE: The .xml configuration file is exported to a pre-determined location on your local or network drive.

7

Select Apply to record your changes, or select OK to record your changes and close the dialog.

Bulk Configuration

Step

Action

1

Access the DTM configuration for your module.

2

In the CONFIGURATION menu, expand ( +) the Communication sub-menu.

3

Select Channel Configuration.

4

To edit, double-click the pencil in the Bulk Configuration tab of the CLIENT CHANNELS dialog.

Result: An Open dialog box appears where you can navigate to the required bulk configuration file.

5

Select the DataMapping_BulkConfiguration.xlsm file to the required folder required in step 4 and open the Excel worksheet.

6

Based on the requirement, (data points for server and client for IEC or DNP3), copy the respective data to the IEC Client or IEC Server worksheet.

7

Open the corresponding data mapping, and the data should be successfully imported.

8

Record your changes and import the Excel worksheet.
NOTE: The execution of the bulk configuration requires Microsoft Excel 2007 or later.
Excel worksheet details:

  • IEC Server: IECDataPoint_Ref sheet to IECServer

  • IEC Client: IECDataPoint_Ref sheet to IECClient

  • DNP3 Server: DNP3DataPoints_Ref to DNP3Server

  • DNP3 Client: DNP3DataPoints_Ref to DNP3Client