Data Classes Setup

Data Class Editor allows users to create, modify, delete data classes and map them to different mapping entities. In this way, Data Class Editor makes it possible to neatly organize monitoring of almost all live data supported by the controller firmware.

Generally speaking, a data class is a simple data item with several attributes such as name, description, type, unit, min and max values used for determining a simple physical quality, which can be, for example - wind speed, active power, pitch angle, etc.

Data class names are standardized by the IEC standard 61400-25 series, enabling uniform data presentation regardless of the vendor. Once created, a single data class can be easily re-used for various units, and different mapping can be applied depending on the variables used in the application running on the controller. Thus, MiScout SCADA Desk allows a user to create different types of mapping, including MODBUS mapping, OPC mapping, VMP mapping,, ADS Mapping, etc. Each type of mapping is described in more detail further in this section.

To be able to use Data Class Editor, the Data Class Editor(mtplDataClassEditor.bpl) plug-in is required. Therefore, first of all, make sure that it is already listed in the Plugin Configuration dialog. For more detail information, refer to Configuring Plug-ins.

As soon as the required plug-in is loaded to Plugin Configuration, the Data Class Editor tab appears on the main application ribbon. Therefore, click Data Class Editor on the ribbon to open its toolbar.

The Data Class Editor tab contains the following sections:

• Show section allows you to open either the Data Classes window or the Data Mappings window.
• New section provides a possibility of creating new items, including a Mapping Set, a Data Class, various types of Summation and Mappings as well as Vendor State.
• Modify section contains a different set of icons depending on whether Data Classes icon or Data Mappings icon in the Show section of the toolbar is currently enabled:
  • on activating Data Classes, Edit data class(es), Delete data class(es) and Undo data class(es) icons will be enabled allowing to edit data classes properties as well as remove them.
  • on activating the Data Mappings icon, Edit, Delete and Undo icons will appear on the toolbar instead allowing to change the data mappings properties as well as remove them.
• Calculate section displays the Thresholds icon allowing to perform threshold calculation based on user defined settings.
• Options section contains Auto edit data classes, Auto edit mappings, Custom Mapping and Mapping Thresholds check-boxes for enabling the following options:
  • Auto edit data classes - if selected, you'll be able to edit values in each column of the grid right after clicking it. Values in the selected column will be highlighted blue.

• Auto edit mappings - if selected, you'll be able to edit values in each column of the grid right after clicking it, which will be highlighted blue.
• Custom Mapping - enabling this check-box allows to have custom mapping displayed in the data mappings table.
• Mapping Thresholds - this option allows to view Warning min/max and Alert min/max columns in the Data mappings table with pre-configured values.

Import/Export section allows exporting data of the selected mapping sets into the.csv file format. And vice versa, using the Import icon it is possible to import data from the .csv file to the required mapping set.

Import - writes data from the .csv file to the prior selected mapping set;

• Overwrite - if selected, a data class in the selected mapping set will be replaced by the corresponding data class contained in the imported .csv file.
• Merge - if selected, default values in the mapping set will be replaced by the corresponding values from the .csv file; whereas the non-default values will be left unchanged (as before performing the import).
• Skip - if selected, identical data mapping(s) in the current mapping set won't be replaced by the corresponding mapping(s) from the csv file. As the system will "ignore" similar mapping(s) with the same data classes);

Export - writes data from the mapping set into the .csv file format.

Data Сlasses Tab

The Data classes window allows a user to perform the following actions:

• create new child and parent data classes;
• edit properties of available data classes;
• remove data classes, if required.

Further in this section you will find more detail instructions on how to perform each of the above mentioned actions.

According to the IEC 61400-25 standard, all data classes are grouped into the following logical nodes:

• WALM - Wind Power Plant Alarm Information
• WCNV - Wind Turbine Converter Information
• WGEN - Wind Turbine Generator Information
• WGEN2 - Second Wind Turbine Generator Information
• WMET - Wind Power Plant Meteorological Information
• WNAC - Wind Turbine Nacelle Information
• WROT - Wind Turbine Rotor Information
• WTOW - Wind Turbine Tower Information
• WTRF - Wind Turbine Transformer Information
• WTRM - Wind Turbine Transmission Information
• WTUR - Wind Turbine General Information
• WYAW - Wind Turbine Yawing Information

The attributes below could also be used in data classes manes according to the IEC-61400 format:

• instMag - magnitude of instantaneous value;
• mag - dead band filtered value, e.g. a production of previous day, completed data;
• d - indicates description;
• t - indicates time value;
• i - indicates integer value;
• f - indicates floating point value.
• stId - indicate local identifier for status data (status code number);
• Val - indicates specified value;
• Lev - indicates specified level;
• Evt - indicates specified event;
• Id - indicates specified event.

Data classes are grouped and displayed in the grid containing the following columns: Name, Description, Parent, Measure unit, Data type, Value type, IEC type and Modified.

• State - denotes the current state of the object. Possible object states are as follows:
• Original - the object is in its original state (i.e. without changes);
• New - the object has been recently created, therefore it is marked as a new one;
• Modified - the object properties have undergone recent changes;
• Removed - the object has been deleted;
• Apply Pending - the specific command has been sent to the server and a reply message is expected from the Notification Service.
• Name - the name of the data class according to IEC 61400-25;
• Description - a readable name given to a data class, which can appear when presenting this data class on a GUI;
• Parent - displays a parent data class. Select a parent data class, if you are configuring a data class for the summation field. A parent data class defines the summation itself, while child data classes describe the fields of summation (activations counter, total active time, etc.)
• Measure unit - allows setting the specific measurement unit for the data class;
• Data type - allows setting the data type for the data class. Use "default" for most data classes. Other options can be used for summations or for commands;
• Value type - allows setting the value type for the data class (i.e. Analog, Long, etc.);
• IEC type - basic data classes type (i.e. BOOLEAN and Int 64, etc.);
• Modified - indicates the time when a data class has been last modified.

Data classes filter

As already mentioned earlier in this section, all available data classes are gathered in separate groups, which can be expanded by clicking the plus icon.

All these data classes can be easily filtered by clicking the Group icon and by selecting the required data class(es) in the drop-down menu. MiScout Desk allows to filter data classes in each column of the grid using the filter icon next to the column name. So, all a user needs, is to set the required options in the Custom Filter dialog.

Click the Customize... icon at the bottom of the Data classes window to customize your filter by setting proper parameters and conditions.

Creating and configuring data classes

User can edit the value of each column or edit the whole data class by clicking the black square icon. Alternatively, you can double-click any of the data classes displayed in the Data classes window to activate the Edit data class(es) dialog. Right after the Edit data class(es) dialog appears, you can start configuring values in the property fields.

The same Edit data class(es) dialog will appear on clicking the Data Class icon, when adding a new data class. After right-clicking the selected data class, a menu opens allowing a user to create data class(es) as well as edit and delete the existing ones.

Also, a user can easily withdraw recent changes by clicking the Undo data class(es) changes option at the very bottom of the context-menu.

Configuring summations

In the New section of the Data Class Editor toolbar resides the Summation icon allowing you to create different types of summation data classes. Below you will find a step by step description on how to create and configure Energy Summation.

1. On clicking the Summation icon, select the Energy Summation option in the revealed menu. This menu lists all types of summation available in .

As a result, the Edit Summation Data Classes dialog appears allowing a user to configure properties for a new data class.

2. Make proper settings in the Edit Summation Data Classes dialog.

General properties - Property fields residing in this section specify a parent data class for the selected summation.

• Name - This property field allows a user to configure any suitable name for the parent data class.
• Description - If required, a user is able to enter any additional information referring to the corresponding parent data class.

Note. Fields found in the General properties section of the Edit Summation Data Classes dialog are common for all summation types and refer to only the parent data class. Name and Description are obligatory fields, which a user must necessarily configure, as rest dialog properties are assigned default settings based on configurations made in General properties. Rest dialog sections (i.e. Produced/Consumed Active Energy, etc.) contain property fields allowing to configure child data classes.

Start Time - Property fields of this section specify a child data class allowing time calculation.

• Name - This property field allows a user to configure any suitable name for the child data class.
• Description - If required, a user is able to enter any additional information referring to the corresponding child data class.

Note. Default child data class name consists of the name of the corresponding parent data class and the specific attribute standardized according to IEC 61400-25. In our case with Energy Summation, full default name for the child data class is "Active_EnergyTotEgyAt.mag.f", which consists of the parent data class name "Active_Energy" and the specific attribute "TotEgyAt.mag.f"S.

Produced Active Energy - Property fields of this section specify a child data class allowing calculation of produced active energy.

• Name - This property field is set automatically and it shows the name of the child data class. The only way to edit the child data class name is to change the name of the parent data class. Otherwise, this field cannot be edited.
• Description - This property field is set automatically and it shows some descriptive information about the child data class, being currently configured. If required, a user can enter a different message in this filed.
• Measure unit - Some default settings are already suggested for this property field. However, a user is free to select other values available in the drop-down menu of this property.
• IEC data type - Some default settings are already suggested for this property field. However, a user is free to select other settings available in the drop-down menu of this property.

Other dialog sections describing rest child data classes are listed below, each containing the same set of properties as Produced Active Energy.

Consumed Active Energy - Property fields of this section specify a child data class allowing to calculate the amount of consumed active energy.

Produced Reactive Energy - Property fields of this section specify a child data class allowing calculation of produced reactive energy.

Consumed Active Energy - Property fields of this section specify a child data class allowing to calculate the amount of consumed active energy.

Consumed Reactive Energy - Property fields of this section specify a child data class allowing calculation of consumed reactive energy.

3. On configuring all the dialog sections, press OK.

If done successfully, the following parent and child data classes will be created, which you'll be able to view in the Data classes window:

• One new parent data class will be added to the list named as
• Active_Energy
• Also, five new child data classes will be created.
• Active_EnergyEgyAtCons.mag.f
• Active_EnergyEgyReactCons.mag.f
• Active_EnergyEgyAt.mag.f
• Active_EnergyEgyReact.mag.f
• Active_Energy.stTm.tRs

4. Click the Commit Changes icon in the upper left corner, so that all configuration changes are successfully saved on the server.

The process of creating and configuring Service and Statistic Summations is similar to the one described for Energy Summation. For more detail instructions, see Configuring Summations described earlier in this section. However, the number of created child data classes differs for each summation type:

for Service Summation one parent and three child data classes will be created, while

for Statistic Summation one parent and four child data classes will be added.

You remember, of course, that for Energy Summation one parent and five child data classes are added. Further in this section, you will find screens showing possible configuration settings for Service and Statistic Summations.

Service summation

In the screen below possible configuration of Service Summation is provided.

As you can see, the Edit Summation Data Classes dialog presents a list of properties, which a user has to configure for the selected summation type. See also the Note above.

General properties - Property fields residing in this section specify a parent data class for the selected summation.

• Name - This property field allows a user to configure any suitable name for the parent data class.
• Description - If required, a user is able to enter any additional information referring to the corresponding parent data class.

Start Time - Property fields of this section specify a child data class allowing time calculation.

• Name - This property field allows a user to configure any suitable name for the child data class. See also the Note above.
• Description - If required, a user is able to enter any additional information referring to the corresponding child data class.

Activation Counts - Property fields of this section specify a child data class allowing calculation of yawing movements.

• Name - This property field is set automatically and it shows the name of the child data class. The only way to edit the child data class name is to change the name of the parent data class. Otherwise, this field cannot be edited.
• Description - This property field is set automatically and it shows some descriptive information about the child data class, being currently configured. If required, a user can enter a different message in this filed.
• Measure unit - Some default settings are already suggested for this property field. However, a user is free to select other values available in the drop-down menu of this property.
• IEC data type - Some default settings are already suggested for this property field. However, a user is free to select other settings available in the drop-down menu of this property.

Total Active Time - Property fields of this section specify a child data class allowing time calculation. This section contains the same property fields as presented in the Activation Counts section above. But we would like to draw your attention to min, a default setting in the Measure unit property. You can change this default value to s. As a result, the calculated yawing time will be shown in seconds instead of minutes.

Statistic summation

In the screen below possible configuration of Statistic Summation is provided.

As you can see, the Edit Summation Data Classes dialog presents a list of properties, which a user has to configure for the selected summation type. See also the Note above.

General properties - Property fields residing in this section specify a parent data class for the selected summation.

• Name - This property field allows a user to configure any suitable name for the parent data class.
• Description - If required, a user is able to enter any additional information referring to the corresponding parent data class.

Start Time - Property fields of this section specify a child data class allowing time calculation.

• Name - This property field allows a user to configure any suitable name for the child data class. See also the Note above.
• Description - If required, a user is able to enter any additional information referring to the corresponding child data class.

Mean Value - Property fields of this section specify a child data class allowing calculation of yawing movements.

• Name - This property field is set automatically and it shows the name of the child data class. The only way to edit the child data class name is to change the name of the parent data class. Otherwise, this field cannot be edited.
• Description - This property field is set automatically and it shows some descriptive information about the child data class, being currently configured. If required, a user can enter a different message in this filed.
• Measure unit - Some default settings - if any available - are already suggested for this property field. However, a user is free to select other values available in the drop-down menu of this property.
• IEC data type - Some default settings are already suggested for this property field. However, a user is free to select other settings available in the drop-down menu of this property.

Other dialog sections describing rest child data classes are listed below, each containing the same set of properties as Mean Value.

Max Value - Property fields of this section specify a child data class allowing calculation of maximum value.

Min Value - Property fields of this section specify a child data class allowing calculation of minimum value.

In case of successful configuration of summations, the following parent and child data classes will be created, which you'll be able to view in the Data classes window:

As seen on the screen above, all user configured summation data classes are found under the UNKNOWN node in the Data classes window. The thing is, that recently added data classes bear random names (i.e. any names desired by a user), not complying with the data class names standardized in the IEEC 61400-25 standard. The key advantage of this approach is to make the overall process of creating data classes easier and more user-friendly. For more information, see the IEC 61400-25 standard mentioned at the beginning of this section.

Data Mappings Tab

Data Mappings allows a user to create new data mappings as well as edit the existing mappings. You can easily reach the Data Mappings icon, which resides in the Show section on the toolbar.

To edit the existing data mapping, a user has to select the required mapping set in the Mapping sets panel found to the right of the main monitoring area. All listed mapping sets are grouped according to different protocol types (e.g. DCE3, MODBUS, MPP, etc.). Depending on the selected protocol type, the grid contains specific columns, which are available for editing. Columns Name and Description are common for all protocol types.

As shown on the above screen, with the help of a mouse right-click on the selected data mapping, a menu will open allowing you to edit or delete available data mapping(s).

A new mapping can be created by clicking the Mappings icon in the New section on the main toolbar. Clicking the downward-arrow icon of the Mappings icon reveals the following types of mapping:

Upon selecting one of the available mappings, the Edit mapping(s) dialog appears onscreen allowing a user to create a new data mapping. For more detail information, see Editing Data Mapping described further in this section.

Editing mapping

User can edit the value of each column or edit the whole data set by clicking the icon, which will reveal the Edit mapping(s) dialog on the main screen. This dialog allows a user to edit the following properties:

General properties are common for all protocol types.

General properties:

• Data class - select the required data class;
• Description - enter any logical and readable name for a data class;
• Measure unit - set the corresponding measure unit. This overwrites measure units from the data class. Furthermore, MiScout can provide automatic measurement adjustment. For example, if a data class contains measurement units in degree Celsius and mapping is overwritten in degree Fahrenheit, then the resulting variable will be automatically converted to Fahrenheit using the appropriate rules.

Value type properties are inherited from the selected data class:

• Data type - set the data type for the data class (e.g. Summations types, etc.);
• Value data type - set the value type for the data class (i.e. Analog, Long, etc.);
• IEC data type - set basic data classes type (i.e. BOOLEAN and Int 64, etc.).

Custom mapping is common for all protocol types.

• Request type - select the required request type, which must be the appropriate one for a specific data class set;
• Value type - choose the required value type (e.g. Int8, Float32, Boolean, etc);
• Value offset - enter proper value to define the data offset in the specific request type;
• Multiplier - enter proper multiplier value by which data received from controller will be multiplied;
• Measure unit - Specifying corresponding measurement units will overwrite the measurement units inherited from the data class. Furthermore, automatic measurement adjustment is also available in MiScout. For example, if a data class contains a measurement unit in degree Celsius and mapping is overwritten in degree Fahrenheit, then the resulting variable will be automatically converted to Fahrenheit using the appropriate rules.
• Measure factor - set the measuring coefficient for converting the online data retrieved from the controller.

If a user sets Min/Max values in the Warning and Alert property fields, this mapping will be marked by an Asterisk icon under the Threshold column of the Data mappings window. Also, to view Min/Max values pre-configured in the Warning/Alert fields in the Data mappings window, make sure that the Mapping Thresholds check-box is enabled in the Options section of the toolbar.

• Warning - enter minimum and maximum values in the corresponding Min and Max fields. These values will be represented as two yellow horizontal lines in some types of SCADA logs (see the Note below) to define the boundary values range for warning. Exceeding any of these values will be treated as reaching some critical level defined as warning.
• Alert - enter minimum and maximum values in the corresponding Min and Max fields. These values will be represented as two red horizontal lines in some types of SCADA logs (see the Note below) to define the boundary values range for an alert state. Exceeding any of these values will be treated as reaching some critical level defined as alerts.

Note.Yellow and red horizontal lines representing the upper/lower levels to define warning and alert ranges can be viewed in SCADA Log Monitor, SCADA Average Logs (Detail and Standard), SCADA High Resolution Log, SCADA Trigger Log.

MPP mapping

For MPP Protocol you can edit MPP mapping values including Variable Name, Measure Factor and Writable property fields:

MPP mapping configuration

• Variable name - set the required variable name;
• Multiplier - enter proper multiplier value by which data received from controller will be multiplied;
• Measure factor - set the measuring coefficient to convert online data retrieved from the controller;
• Writable - if this check-box is selected, data will be written into the variable.

If a user sets Min/Max values in the Warning and Alert property fields, this mapping will be marked by an Asterisk icon under the Threshold column of the Data mappings window. Also, to view Min/Max values pre-configured in the Warning/Alert fields in the Data mappings window, make sure that the Mapping Thresholds check-box is enabled in the Options section of the toolbar.

• Warning - enter minimum and maximum values in the corresponding Min and Max fields. These values will be represented as two yellow horizontal lines in some types of SCADA logs (see the Note below) to define the boundary values range for warning. Exceeding any of these values will be treated as reaching some critical level defined as warning.
• Alert - enter minimum and maximum values in the corresponding Min and Max fields. These values will be represented as two red horizontal lines in some types of SCADA logs (see the Note be below) to define the boundary values range for an alert state. Exceeding any of these values will be treated as reaching some critical level defined as alerts.

Note.Yellow and red horizontal lines representing the upper/lower levels to define warning and alert ranges in MiScout Desk can be viewed in SCADA Log Monitor, SCADA Average Logs (Detail and Standard), SCADA High Resolution Log, SCADA Trigger Log. In MiScout Web yellow and red horizontal lines representing thresholds appear in the Average Log tab.

Important Note. User can set Min and Max values for Warning and Alert property fields in the Edit mapping(s) dialog window in all types of mappings described further in the Data Mappings Tab section including ADS mapping, M1 mapping, etc.

OPC mapping

For OPC Protocol you can edit OPC mapping which includes filling in the following fields: OPC Item, Multiplier, Measure Factor, Value offset and Measure unit.

OPC mapping configuration

Set the following values for the OPC Protocol type:

• OPC item - enter the corresponding name for the OPC item, which will be used for requesting this variable from the OPC Server;
• Multiplier - enter proper multiplier value by which data received from controller will be multiplied;
• Measure factor - set the coefficient, if required, to convert raw values retrieved from the controller;
• Measure unit - set the corresponding measurement unit which will override the default measurement units inherited from the data class. Furthermore, MiScout can provide automatic measurement adjustment. For example, if a data class contains measurement units in degree Celsius and mapping is overwritten in degree Fahrenheit, then the resulting variable will be automatically converted to Fahrenheit using the appropriate rules.

MODBUS mapping

User can edit MODBUS mapping for a MODBUS protocol type filling in the property fields shown in the screen below:

MODBUS mapping configuration

For the MODBUS Protocol type, set values for the following property fields:

In the Address types property field a user is free to assign the following address types to data classes:

• Input Register - If selected, data becomes read-only.
• Holding Register - If selected, data can be both read and written.
• Discrete Input - If selected, data will be read-only as binary digits: 0 = False and 1 = True.
• Discrete Output - If selected, data will be read and written as binary digits: 0 = False and 1 = True.

Writable - If the check-box is selected for the Input Register address type, it automatically switches to => Holding Register and vice versa. Similarly, selecting this check-box for Discrete Input results in changing the address type to =>Discrete Output.

MODBUS mapping specific properties

• Start address - Entered value denotes the starting address of the register.
• End address - Entered value will denote the end of the register address range.
• Bit number - Enter any value within the range of 0-15 to assign a bit number.
• Data type - Select any of the available data types listed in the drop-down list to specify the order of bytes within the register. The selected data type has to coincide with the one expected by the Modbus client.

Based on the address type, user can select the following options provided in Data type.

For Input Registeror Holding Register address type: 

• Int 8 (also Int 64, Int 8U, Int 16U etc.) - Each data type indicates the total number of input bits: e.g. 16 bits = 1 register; 32 bits = 2 registers, etc.

For Discrete Input or Discrete Output address type: 

• Boolean - If selected, data will be read or written as binary digits: 0 (False) and 1 (True).
• Float 32 (also Float 64 - If selected, data will be read or written in binary format 32-bit or 64-bit float values: Float 32=32 bits=4 bytes=2 registers; Float 64=64 bits=8 bytes=4 registers.
• Timestamp - This data type is used to indicate time values only. The total number of contained input bits equals to 64.

Other Data type options are as follows:

• Unknown - If selected, it means that no specific data type has been assigned.
• String - This data type is not used in MODBUS mapping.

Other properties specific to MODBUS mapping:

• Multiplier - enter proper multiplier value by which data received from controller will be multiplied;
• Measure unit - Select a corresponding measurement unit which will override the default measurement from a data class.
• Measure factor - Set the measuring coefficient for converting online data retrieved from the controller.

ADS mapping

User can edit ADS mapping for the ADS protocol type filling in the property fields shown in the screen below.

ADS mapping configuration:

For the ADS protocol type, set values for the following property fields:

ADS mapping specific properties

• ADS Port - Normally, this property field is already filled in by default. Otherwise, a user has to specify the port number, which will be used for distinguishing the sub-elements in the connected ADS controller.

The port number distinguishes sub-elements in the connected device. The list bellow displays the following ADS port numbers being already assigned:

• Variable name - Enter a variable name to access it on the ADS controller.
• Group - Enter a group name a variable belongs to.
• Offset - Enter a value to define the variable offset.
• Type - Select any of the available data types (INT8, INT8U, INT16, INT16U, INT32, INT32U, INT64, INT64U, FLOAT, DOUBLE, STRING, WSTRING, BIT) to specify the order of bytes within the register.
• Bit number - Enter proper value defining a bit number within the variable.
• Size - This property field defines the variable size and is valid for STRING and WSTRING variable types only. If left empty, the number of symbols set by default will equal 80. However, if the entered value exceed 80 symbols, the system will "shorten" the string and will read only 80 symbols of the original variable size.
• Measure unit - Select a corresponding measure unit which will override the default measurement from a data class.
• Measure factor - Set the measuring coefficient for converting online data retrieved from the controller.
• Writable - Selecting this check-box allows writing data to a variable on the controller. Otherwise, data will not be written to the variable.

It should be pointed out, that while configuring ADS mapping there are two ways for identifying (i.e. reading) a variable in MiScout SCADA:

Condition A- This way of reading a variable will be implemented only on condition, that the ReadVariableInfo property field is set to True (see ReadVariableInfo in the Creating an ADS controller section).

Condition B- This way of reading variables will be enabled, if the ReadVariableInfo property field is set to False (see ReadVariableInfo in the Creating an ADS controller section).

Note. If the type of the configured variable is STRING, a user must necessarily configure the Size property field.

M1 mapping

User can edit M1 mapping for the M1 protocol type by filling in the property fields shown in the screen below:

M1 mapping configuration:

For the M1 protocol type, set values for the following property fields:

• Variable name - Enter a variable name to access it on the M1 controller.
• Writable - Selecting this check-box allows writing data to a variable on the controller. Otherwise, data will not be written to the variable.

MNet mapping

The screen below shows MNet mapping for the MNet type of controllers:

MNet mapping configuration:

For the MNet protocol type, set values for the following property fields:

• Main Id - enter a corresponding value denoting an address of the group of variables on the controller;
• Sub Id - enter a proper value denoting a variable address in the corresponding group of variables.

Custom mapping

Custom mapping for MNet controllers serves for defining the relation between the channel and the assigned data class. It is mainly used for the Average Log type. Thus, if required user is free to set properties for the custom mapping as shown in the screen below:

Data mappings for VMP protocol

User can edit Custom mapping for VMP Protocol including the following property fields: Request type, Raw data type, Value Offset, Value length, Multiplier and Measure Factor. More detail information you can find in Editing Data Mapping described earlier in this section.

The following mapping can be used for the VMP Protocol type:

Y Overview Current request type:

Each of the listed numbers defines a value offset in the specific request type:

• 0 – time
• 1 – generator speed
• 2 – rotor speed
• 3 – pitch angle
• 4 – yawing CW
• 5 – yawing CCW
• 6 – if “run state” then 1 if stop state then 2
• 7 – run
• 8 – stop or pause
• 9 – yawing
• 10 – active power
• 11 – stop
• 12 – pause
• 13 – service
• 14 – emergency
• 15 – wind speed
• 16 – command accepted
• 17 – local mode request
• 18 - generator 1 connected
• 19 – generator 2 connected

Y Overview Wind request type:

• 0 – wind speed
• 1 – relative wind direction
• 2 - absolute wind direction
• 3 – nacelle direction

Y Production request type:

• 0 – time
• 1 – active energy for generator 0
• 2 – active energy for generator 1
• 3 – active energy for generator 2
• 4 – active energy total
• 5 – reactive energy for generator 0
• 6 – reactive energy for generator 1
• 7 – reactive energy for generator 2
• 8 – reactive energy total

Y Temperatures actual request type:

VMP3500 controller type

• 101 – Hydraulic
• 102 – Environment
• 103 – Gear
• 104 – Generator1
• 105 – Generator2
• 106 – Bearing1
• 107 – Bearing2/ Top controller
• 108 – Nacelle
• 109 – Nacelle controller
• 110 – RCC
• 111 – Spinner
• 112 – HV transformer L1
• 113 – HV transformer L2
• 114 – HV transformer L3
• 115 – Genenerator bearing

VMP5000.01/02 controller type:

• 101 – Hydraulic
• 102 – Environment
• 103 – Gear
• 104 – Generator
• 105 – Slipring VCS
• 106 – Gear Bearing
• 107 – Hub controller/ Top controller
• 108 – Nacelle
• 109 – Top controller
• 110 – Bus bar
• 111 – Spinner
• 112 – HV transformer L1
• 113 – HV transformer L2
• 114 – HV transformer L3
• 115 – Genenerator bearing
• 116 - Cool Water VCS

Y Electrical current request type:

• 0 – Produced power
• 1 – Cos phi
• 2 – Frequency
• 3 – Voltage L1
• 4 – Voltage L2
• 5 – Voltage L3
• 6 – Current L1
• 7 – Current L2
• 8 – Current L3

Y Hour counters request type:

• 0 – Total availability percentage
• 1 – Total counter
• 2 – Grid ON counter
• 3 – Grid OK counter
• 4 – Turbine OK counter
• 5 – Run counter
• 6 – Generator 1 counter
• 7 – Generator 2 counter
• 8 – Yaw counter
• 9 – Service counter
• 10 – Amient OK counter
• 11 – Wind OK counter

B General Status request type:

• 1 – generator speed
• 2 – rotor speed
• 4 – yawing CW
• 5 – yawing CCW
• 9 – yawing
• 10 – power
• 11 – wind speed
• 12 – power
• 13 – number of errors
• 14 – Status letter
• 15 – brake
• 16 – yaw
• 17 – generator

Data Mappings for WP2000 Protocol.

Below you will find description of the default WP2000 mapping in MiScout Desk.

Standard data - a package supported by all types of wind turbines, containing key operational data, including the following:

• 0 - status code
• 1 - power
• 2 - wind speed
• 3 - hydraulic pressure
• 4 - temperature 1 (cooling water return)
• 5 - temperature 2 (generator 2)
• 6- temperature 3 (generator bearing DE)
• 7 - temperature 4 (generator 1)
• 8 - temperature 5 (gear bearing)
• 9 - temperature 6 (gear oil)
• 10 - temperature 7 (outdoor)
• 11 - production G2 (generator 2)
• 12 - consumption
• 13 - voltage L1
• 14 - voltage L2
• 15, voltage L3
• 16 - current L1
• 17 - current L2
• 18 - current L3
• 19 - cosinus Phi
• 20 - rotor speed
• 21 - yaw operation count
• 22 - generator speed
• 23 - yaw direction
• 24 - power at a stop
• 25 - wind at a stop
• 26 - production G1 (generator 1)
• 27 - grid Var
• 28 - get time
• 29 - total energy

Operation Data - a package supported by all types of wind turbines, containing the following summations data:

• 0 - sum cut-in 1
• 1 - sum cut-in 2
• 2 - sum operational time G1 (generator 1)
• 3 - sum operational time G2 (generator 2)
• 4 - sum operational brake count
• 5 - sum stopped time
• 6 - sum operational time
• 7 - sum yaw counterclockwise count
• 8 - yaw clockwise count
• 9 - sum yawing time
• 10 - sum stopped time

Temperature Data - a package, which is supported by the Nordex wind turbines.

• 0 – temperature of the control panel
• 1 – generator bearing NDE temperature
• 2 – cooling water forward temperature
• 3 – outdoor temperature

Weather data - a package supported by weather stations only.

• 0 - wind speed 1
• 1 - wind direction
• 2 - wind speed 2
• 3 - outdoor temperature
• 4 - air pressure
• 5 - relative humidity

Data mappings for DCE3 protocol

For DCE3 Protocol user can edit Custom mapping including Request type, Value type, Value Offset, Value length, Multiplier and Measure factor properties. More detail information on this topic can be found in Editing Data Mapping described earlier in this section.

The following mapping can be used for the DCE3 protocol type:

Each of the listed numbers defines a value offset in the specific request type

DCE3 Turbine Status request type:

• 1 - Timestamp
• 2 - Operation Mode
• 3 - Grid Power (30 sec)
• 4 - Grid Reactive Power (30 sec)
• 5 - Wind Speed (30 sec)
• 6 - Generator speed (rpm)
• 7 - Rotor Speed (rpm)
• 8 - Nacelle Direction
• 9 - Tip Pressure
• 10 - Brake Pressure Shaft
• 11 - Brake Operation Mode
• 12 - Yaw Motor 1

Grid data request type:

• 0 - Grid Voltage
• 1 - Grid Voltage phsB
• 2 - Grid Voltage phsC
• 3 - Grid Current and 3 Grid Current phsA
• 4 - Grid Current phsB
• 5 - Grid Current phsC
• 6 - Grid Power phsA
• 7 - Grid Power phsB
• 8 - Grid Power phsC
• 9 - Grid Reactive Power phsA
• 10 - Grid Reactive Power phsB
• 11 - Grid Reactive Power phsC
• 12 - Power Factor L1
• 13 - Power Factor L2
• 14 - Power Factor L3
• 15 - Power Factor
• 16 - Power Factor
• 17 - Grid Frequency

Temperatures request type:

• 0 - Temperature, Thyristor Block
• 1 - Temperature Power Panel
• 2 - Temperature, Generator
• 3 - Temperature, Generator 2
• 4 - Temperature Gear Bearing Front
• 5 - Temperature, Gear Oil
• 6 - Temperature, Outside
• 7 - Temperature, Nacelle
• 8 - Temperature, Yaw Gear
• 9 - Temperature, Gear Bearing Rear
• 10 - Temperature, Main Bearing
• 11 - Temperature, Transformer
• 12 - Temperature, Generator Bearing Drive-End
• 13 - Temperature, Generator Bearing Non Drive-End
• 14 - Temperature, Water Before Cooler
• 15 - Temperature, Water After Cooler
• 16 - Temperature, Gear Oil Tank
• 17 - Temperature, Main Bearing 2
• 18 - Temperature, Pitch Oil
• 19 - Temperature, Tower Base
• 20 - Temperature, Top Box
• 21 - Temperature, Transformer L1
• 22 - Temperature, Transformer L2
• 23 - Temperature, Transformer L3
• 24 - Temperature, Control Panel
• 25 - Temperature,Phase Compensator Panel
• 26 - Temperature, Small Generator L1
• 27 - Temperature, Small Generator L2
• 28 - Temperature, Small Generator L3
• 29 - Temperature, Big Generator L1
• 30 - Temperature, Big Generator L2
• 31 - Temperature, Big Generator L3
• 32 - Temperature, Hub Panel
• 33 - Temperature, Gear Oil Filter
• 34 - Temperature, Auxiliary Transformer
• 35 - Temperature, Transformer Room

Production data request type:

• 1 - Total Production (kWh)
• 2 - Total Production 2 (kWh)
• 3 - Subtotal Production (kWh)
• 4 - Subtotal Production Duration (hours)
• 5 - Released Brake Duration (hours)
• 6 - Yawing Clockwise Duration (hours)
• 7 - Yawing Counterclockwise Duration (hours)
• 8 - Total Production Subtotal Duration(hours)
• 9 - Total Production Duration (hours)
• 10 - Big Generator Production (kWh)
• 11 - Big Generator Duration (hours)
• 12 - Small Generator Production (kWh)
• 13 - Small Generator Duration (hours)
• 14 - Power Consumption (kWh)
• 15 - Reactive Power Production (kVArh)
• 16 - Power On Duration (hours)
• 17 - Alarm Duration (hours)
• 18 - Turbine State "Ok" Duration (hours)

Operation Duration counters request type:

• 1 - Big Generator Contactor Duration (hours)
• 2 - Small Generator Contactor Duration (hours)
• 3 - Bypass Contactor Duration (hours)
• 4 - Heater Wind Sensors Duration (hours)
• 5 - Phase 1 Compensation Duration (hours)
• 6 - Phase 2 Compensation Duration (hours)
• 7 - Phase 3 Compensation Duration (hours)
• 8 - Phase 4 Compensation Duration (hours)
• 9 - Phase 5 Compensation Duration (hours)
• 10 - Pump Gear Oil Duration (hours)
• 11 - Water Pump Duration (hours)
• 12 - Hydraulic Pump Tips Duration (hours)
• 13 - Hydraulic Pump Shaft Duration (hours)
• 14 - Yawing Clockwise Duration (hours)
• 15 - Yawing Counterclockwise Duration (hours)
• 16 - Main Panel Fan Duration (hours)
• 17 - Pump Lubrication Duration (hours)

Operation counters request type:

• 1 - Big Generator Contactor Count (times)
• 2 - Small Generator Contactor Count (times)
• 3 - Bypass Contactor Count (times)
• 4 - Heater Wind Sensors Count (times)
• 5 - Phase 1 Compensation Count (times)
• 6 - Phase 2 Compensation Count (times)
• 7 - Phase 3 Compensation Count (times)
• 8 - Phase 4 Compensation Count (times)
• 9 - Phase 5 Compensation Count (times)
• 10 - Gear Oil Pump Count (times)
• 11 - Water Pump Count (times)
• 12 - Hydraulic Pump Tips Count (hours)
• 13 - Hydraulic Pump Shaft Count (hours)
• 14 - Yawing Clockwise Count (times)
• 15 - Yawing Counterclockwise Count (times)
• 16 - Main Panel Fan Count (times)
• 17 - Pump Lubrication Count (times)

Data mappings for KK protocol

For KK Protocol a user can edit Custom mapping including Request type, Value type, Value Offset, Multiplier, Measure unit and Measure factor properties. More detail information on this topic can be found in Editing Data Mapping described earlier in this section.

The following mapping can be used for the KK protocol type:

Each of the listed numbers defines a value offset in the specific request type

KK Data request type:

• 1 - Time
• 2 - Operation Mode
• 3 - Brake status
• 4 - Operation mode 2
• 5 - Grid Power (30 sec)
• 6 - Wind Speed (30 sec)
• 7 - Generator RPM
• 8 - Rotor Speed (rpm)
• 9 - Temperature, Generator
• 10 - Temperature, Main bearing
• 11 - Temperature, Gear oil
• 12 - Temperature, Outside
• 13 - Grid Voltage phsA
• 14 - Grid Voltage phsB
• 15 - Grid Voltage phsC
• 16 - Grid Current phsA
• 17 - Grid Current phsB
• 18 - Grid Current phsC
• 19 - Energy subtotal G1
• 20 - Active time subtotal G1
• 21 - Energy subtotal G2
• 22 - Active time subtotal G2
• 23 - G1 Produced active
• 24 - G1 operational time
• 25 - G2 produced active
• 26 - G2 operational time
• 27 - Operation Mode
• 28 - Active Status Code
• 29 - Total produced Energy

Data mappings for WPST Protocol

For WPST -Protocol a user can edit Custom mapping including Request type, Value type, Value Offset, Multiplier, Measure unit and Measure factor properties. More detail information on this topic can be found in Editing Data Mapping described earlier in this section.

The following mapping can be used for the WPST Protocol type:

Each of the listed numbers defines a value offset in the specific request type

Yaw Status request type:

• 0 - Yaw status string from controller
• 1 - Yawing CW
• 2 - Yawing CCW
• 3 - G1 Production (by small generator)
• 4 - G2 Production (by large generator)
• 5 - Energy

Brake Status request type:

• 0 - Brake status string from controller
• 1 - Brakes applied

Energy request type:

• 0 - Total active production (G1 + G2)
• 1 - Total active consumption (G1 + G2)
• 2 - Total reactive production (G1 + G2)
• 3 - Total reactive consumption (G1 + G2)
• 11 - G1 active production
• 12 - G1 active consumption
• 13 - G1 reactive production
• 14 - G1 reactive consumption
• 15 - G2 active production
• 16 - G2 active consumption
• 17 - G2 reactive production
• 18 - G2 reactive consumption

Data mappings for WW-QCP-Protocol

For WW-QCP-Protocol a user can edit Custom mapping including Request type, Value type, Value Offset, Multiplier, Measure unit and Measure factor properties. More detail information on this topic can be found in Editing Data Mapping described earlier in this section.

The following mapping can be used for the WW-QCP-Protocol type:

Each of the listed numbers defines a value offset in the specific request type

Ww Qcp Overview request type:

• 1 - Grid Power (30 sec)
• 2 - Grid Cos Phi
• 3 - G1 Production (by small generator)
• 4 - G2 Production (by large generator)
• 5 - Energy subtotal produced by G1 (small generator)
• 6 - Energy subtotal produced by G2 (large generator)
• 7 - Grid Voltage phase A
• 8 - Grid Voltage phase B
• 9 - Grid Voltage phase C
• 10 - Grid Current phase A
• 11 - Grid Current phase B
• 12 - Grid Current phase C
• 13 - Grid Frequency
• 14 - Generator RPM
• 16 -Rotor Speed RPM
• 17 - Wind Direction (yaw angle)
• 18 - Outdoor Temperature
• 19 - Generator Temperature
• 20 -Gear Oil Temperature
• 21 - Thyristor Temperature
• 22 - Wind Speed (30 sec)
• 27 - Grid Reactive Power (30 sec)
• 28 - Temperature, HSS Bearing DE (front)
• 29 - Temperature, HSS Bearing NDE (back)
• 30 - Temperature, Generator NDE bearing
• 31 - Temperature, Gear Oil Tank
• 32 - Timestamp
• 33 - Vendor Status Code
• 35 - Pressure, Tip Brake
• 36 - Total Production ( small generator total production + large generator total production)

Turbine Status QCP request type:

• 1 - Average Period 1
• 2 - Average Power for Period 1
• 3 - Maximum Power for Period 1
• 4 - Minimum Power for Period 1
• 5 - Average Wind Speed for Period 1
• 6 - Maximum Wind Speed for Period 1
• 7 - Minimum Wind Speed for Period 1
• 8 - Average Temperature for Period 1
• 9 - Maximum Temperature for Period 1
• 10 - Minimum Temperature for Period 1
• 11 - Average Wind Direction for Period 1
• 12 - Maximum Wind Direction for Period 1
• 13 - Minimum Wind Direction for Period 1
• 14 - Average Period 2
• 15 - Average Power for Period 2
• 16 - Maximum Power for Period 2
• 17 - Minimum Power for Period 2
• 18 - Average Wind Speed for Period 2
• 19 - Maximum Wind Speed for Period 2
• 20 - Minimum Wind Speed for Period 2
• 21 - Average Temperature for Period 2
• 22 - Maximum Temperature for Period 2
• 23 - Minimum Temperature for Period 2
• 24 - Average Wind Direction for Period 2
• 25 - Maximum Wind Direction for Period 2
• 26 - Minimum Wind Direction for Period 2
• 27 - Value defining Turbine Status
• 28 - Turbine Status Description
• 29 - Value defining Brake Status
• 30 - Brake Status Description
• 31 - Value defining Yaw Status
• 32 - Yaw Status Description
• 33 -Value defining Generator Status
• 34 - Generator Status Description
• 35 - Value defining Phase Compensation
• 36 - Description of phase Compensation

Ww Qcp Summations request type:

• 1 - Brake
• 2 - Yaw CW
• 3 - Yaw CCW
• 4 - Retwist CW
• 5 - Retwist CCW
• 6- G1
• 7 - G2
• 8 - G1 phase compensation
• 9 - G2 phase compensation
• 10 - G1 thyristor bypass
• 11 - G2 thyristor bypass
• 12 - Hydraulic pump 1
• 13 - Hydraulic pump 2
• 14 - Gear oil pump
• 15 - G1 Contractor
• 16 - G2 Contractor
• 17 - Severe errors
• 18 - Manual resets
• 19 - Automatic Resets
• 20 - Remote Resets
• 21 - Manual Motor Start
• 22 - Automatic Motor Start
• 23 - Manual Remote Stops
• 24 - Remote Starts
• 25 - Manual Stops
• 26 - Manual Starts
• 27 - Automatic Stops
• 28 - Automatic Starts
• 29 - High Wind Stops
• 30 - Power Downs
• 31 - Fan Activations
• 32 - Soft Brake Filter
• 33 - Cooler
• 34 - Heater
• 35 - Low Wind Stops
• 36 - Turbine OK (millisec)
• 37 - Generator 1 (millisec)
• 38 - Generator 2 (millisec)
• 39 - Generator 1 subtime (millisec)
• 40 - Generator 2 subtime (millisec)
• 41 - Thyristor (millisec)
• 42 - Severe error (millisec)
• 43 - Yaw CW (millisec0
• 44 - Yaw CCW (millisec)
• 45 - Hydraulic Motor 1 (millisec)
• 46 - Hydraulic motor 2 (millisec)
• 47 - Oil Pump (millisec)
• 48 - Grid OK (millisec)
• 49 - Fan (millisec)
• 50 - Cooler (millisec)
• 51 - Heater (millisec)

Ww Qcp Production request types:

1 - Ww Qcp Hourly Production Current Day

1 - Ww Qcp Daily Production Current Month

1 - Monthly Production Current Year

Data mappings for WW-Optima-Protocol

For WW-Optima-Protocol a user can edit Custom mapping including Request type, Value type, Value Offset, Multiplier, Measure unit and Measure factor properties. More detail information on this topic can be found in Editing Data Mapping described earlier in this section.

The following mapping can be used for the WW-Optima-Protocol type:

Each of the listed numbers defines a value offset in the specific request type

Ww Optima Overview request type:

• 1 - Time
• 2 - First Item
• 3 - Wind Speed (1 sec)
• 4 - Wind Speed (10 min)
• 5 - Power (1 sec)
• 6 - Power (10 min)
• 7 - Active Power Total Production
• 8 - Operation mode (Vendor State)
• 9 - Active Status Code
• 10 - Grid Power (30 sec)
• 11 - Grid Power (10 min)
• 12 - Wind Speed (30 sec)
• 13 - Wind Speed (10 min)
• 14 - Wind Direction (30 sec)
• 15 - Last Item
• 101 - Operation Mode (vendor state) description

Vendor State

Vendor state is a functionality in scope of the Data Class Editor tab allowing customers define the states of the units just the way they wish, including:

• Wind turbine is serviced
• Wind Turbine is stopped
• Wind turbine stopped due to errors

In this section we will instruct you on how to configure a number of specific vendor states for the wind turbines. For example, let's configure the following wind turbine states:

• Running
• Wind speed too high
• Wind speed too low
• Error state

Configuring vendor states

In order to configure a vendor state, take the following workaround step by step.

1. Press the Vendor State icon on the toolbar to open the Edit vendor state(s) dialog. Alternatively, right-click within the Vendor State panel to open the context menu and select the Vendor state option.

As a result, the Edit vendor state(s) dialog reveals within the main monitoring area.

2. Configure the following property fields for the corresponding vendor state in the Edit vendor state(s) dialog:

General properties

• Vendor state - enter any value to define a corresponding vendor state;
• MITA state - click to open the drop-down menu and select the appropriate option:

Note. Mita states are pre-defined and hard coded in MiScout. These states are used by default, in case no user configured vendor states are currently available in the system.

• Description - this property field allows a user to enter some additional information specific to the current vendor state;
• Color - click to open the drop-down menu and select the appropriate color to define the current vendor state:

• Priority - enter any value to define the priority for the current vendor state. The bigger the assigned number, the higher the vendor state priority.

Note. Priority value is taken into account when defining a vendor state for the whole park of wind turbines. For example, if a number of turbines show different vendor states, the park icon will acquire the color defining the vendor state with the highest priority.

• Controller Icon - press the arrow icon to the right of this property to load a list of available images to denote wind turbines and select an appropriate option;
• Assembled Icon - press the arrow icon to the right of this property to load a list of available images to denote wind parks (farms, etc.) and select an appropriate option.

Note. For an image to be available on the drop-down list of Controller Icon and Assembled Icon property fields, it must be configured beforehand in the Images Configuration window. For more detail instructions, see the Images Configuration chapter.

3. On configuring all the property fields, press the OK button in the dialog.

4. Finally, to quickly apply the configuration changes click the Commit Changes icon at the left top corner of the main application window. Otherwise, click the Rollback Changes icon to withdraw the changes.

All recently configured vendor sates will be displayed in the Vendor state panel (see the screen in step 1).

Adding data items

To show the configured unit states, one or multiple data items must be added to the corresponding data set in the Data sets panel. For example, in our specific case we have added several data items: e.g. Turbine state (0 - OK; 1 - Warning; 2 - Error) and Wind speed. Possible configuration of these data items is shown in the following screens.

Configuring a threshold

On configuring all required vendor states and data items, the next step to take is creating a threshold. As soon as the threshold condition is fulfilled, the turbine icon will change its color according to configured vendor states.

Further in this section is shown possible threshold configuration, which will activate all prior configured vendor states (see Configuring vendor states described earlier in this section). For more detail instructions on creating and configuring thresholds, refer to Configuring Thresholds.

Besides, for the threshold to get activated based on pre-defined script conditions, we've created a special script called "Vendor_state_2.js" (see the script code on the screen below).

Please keep in mind, that "Vendor_state_2.js" is an example of a custom script, which users have to create and configure beforehand. For more detail instructions on creating and configuring scripts, refer to Scripts View.

As seen in the screen above, we have taken the following configuration steps:

1. We've created a threshold called "Vendor state".

2. Next, we've configured the threshold properties as follows:

• Activation properties
  • Type: Always execute
• Action properties
  • Type: Execute script
  • Value: Vendor_state_2.js

Note. In the Value field users can select any of the custom scripts with pre-set conditions to show different vendor states (for example, we've created a custom script "Vendor_state_2.js").

3. Reveal the Edit script dialog and make proper changes in the script as shown in the screen above and press OK.

4. Finally, to quickly apply the configuration changes click the Commit Changes icon at the left top corner of the main application window. Otherwise, click the Rollback Changes icon to withdraw the changes.

5. Now that the threshold is configured, we can assign it to the data items in the Data sets panel. Therefore, select the threshold by clicking it and using drag-and-drop assign it to the corresponding data items (see the screen above).

6. After the threshold is successfully assigned to the data items, we will configure its parameters in the Parameters dialog as shown in the screen below.

As a result, Turbine state (0 - OK; 1 - Warning; 2 - Error) and Wind speed will be assigned in the Parameters dialog of the Vendor sate threshold.

7. To save final changes in the threshold, click the Commit Changes icon at the left top corner of the main application window. Now the threshold will be enabled and executed in MiScout.

Viewing vendor states in MiScout

User can view all configured vendor states are in MiScout SCADA: for example, in MiScout Desk after opening the Home tab and pressing the Globe View icon on the toolbar (see the Home section for more information).

All configured vendor states can be easily removed from the system or can also be edited. To do this, user has to select the required vendor state and right-click it to open the context-menu.

In the revealed context menu click Edit to change the vendor state properties. To be able to remove a specific vendor state fro the system, select the Delete option.

Thresholds Calculation

In this section we will describe a step by step workaround of calculating thresholds in Data Class Editor. First of all, make sure that the Data Mappings icon has been activated so that the Thresholds icon in the Calculate section on the toolbar is enabled. Afterwards, take all the steps as described below.

1. Press the Thresholds icon in the Calculate section on the toolbar to open the Calculate Thresholds Welcoming window. To proceed, press Next in the dialog window.

2. Select required controller(s) by selecting corresponding check-boxes and press Next to proceed.

3. Specify the appropriate mapping set in the list and press Next to proceed.

4. Make proper parameter settings in the property fields displayed below.

• Source - click an arrow icon to the right of this property-field and specify the appropriate data source from the drop-down list:
  • Auto - on selecting this option, the system will automatically calculate thresholds for the log containing the biggest amount of data as compared to other log types;
  • Vendor - f selected, the system will calculate thresholds based on data retrieved from the Vendor Average Log;
  • CMS - if selected, the system will calculate thresholds based on CMS Logs;
  • SCADA 10 Min - the system will calculate thresholds based on data taken from the Standard SCADA Average Log;
  • SCADA 1 Min - thresholds will be calculated based on data from the Detail SCADA Average Log;
• Time from - specify the starting date for threshold calculation by selecting an appropriate date in the pop-up calendar;
• Time to - specify the end date for threshold calculation by selecting an appropriate date in the pop-up calendar;
• Variation percent - the minimum percentage of data presence during thresholds calculation - requires that data should be collected more or less evenly while performing calculations;
• Burst elimination - enables automatic elimination of rapid impact in data series;
• Lower bound - on selecting this check-box, a user will be able to view the lower bound of the calculated threshold;
• Min data count - the minimum amount of data presence required to start calculation of thresholds;
• Precision - number of digits after the decimal point.

On making all settings, press the Next icon to move to the next window.

5. Specify the appropriate channels on the list by selecting corresponding check-boxes and press Next to proceed with the configuration..

6. In the next window two tabs can be activated - Threshold or Status Page, each containing a specific set of icons and tools.

Under the Thresholds tab there are Warning coefficient and Alert coefficient property fields allowing a user to enter required values.

On pressing the Status Page tab appropriate information showing the status of calculated thresholds is displayed. On pressing Next, a user can move to the final configuration window.

7. Finally, press Finish to close the wizard and save the configuration.

Data Mappings Import/Export

As already mentioned at the beginning of this section, with the help of the buttons residing in the Import/Export of the Data Class Editor toolbar a user can export mapping set data to the .csv file; as well as import new data to the mapping set from the .csv file. More detail instructions on how to perform data mappings import/export in Data Class Editor is described below.

Importing data mappings

Import of data mappings is one of the key features in Data Class Editor, as it allows a user to quickly configure required data mappings in MiScout SCADA Desk by way of importing necessary data from the .csv file. Therefore, in this section we will first dwell on data mappings import.

In Data Class Editor we can import data contained in the .csv file to one of the available mapping sets. Alternatively, a new blank mapping set can be created, to which new data will be added by way of importing data mappings from the .csv file.

1. First, you have to create a new blank mapping set. Therefore, right-click within the Mapping sets panel to open the context-menu and select the Mapping Set option.

2. Next, enter any suitable name for the new mapping set (e.g. OPC - My new mapping set). Finally, press the Commit Changes icon to save new settings.

3. Select the mapping set in the Mapping sets panel to the right by clicking it.

4. Next, make some additional settings prior to importing:

• Overwrite - if selected, a data class in the selected mapping set will be replaced by the corresponding data class contained in the imported .csv file.
• Merge - if selected, default values in the mapping set will be replaced by the corresponding values from the .csv file; whereas the non-default values will be left unchanged (as before performing the import).
• Skip - if selected, identical data mappings in the current mapping set won't be replaced by their analogs from the csv file, so that only new data will be imported.

In our specific case, we will select the Overwrite option.

5. Press the Import icon residing in the he Import/Export section of the toolbar.

6. Browse to the location of the required .csv file, select it and press Open.

If done successfully, data from the .csv file will migrate to the selected mapping set. Please pay attention to the green icons next to the recently added data, meaning that the data is not saved yet. To proceed with saving data, press the Commit Changes icon.

Creating a csv file for various mapping types

For quick configuration of data mappings, a user can create a special .csv file with data mappings, which later on can be imported to MiScout Desk. Below, you can find an example of the typical .csv file with MPP mapping.

The picture above shows obligatory and optional fields for the MPP mapping. This means, that when creating a .csv file (to be further imported to the MPP mapping set), a user must necessarily enter proper values in the following fields, which are obligatory for this type of mapping. Whereas rest column fields are optional, so that they can be skipped and left blank when writing data mappings into the .csv file. In the table presented below you will find a list of obligatory column fields for each specific data mapping.

Note. If available in the .csv file, custom mapping can be simultaneously imported with the following mapping types: MPP mapping, ADS mapping, DAQ mapping, M1 mapping, MNet mapping, MODBUS mapping, OPC mapping.

Note. Custom mapping is not allowed to be simultaneously imported to MiScout Desk with the following mapping types: DCE3 mapping, KK mapping, VMP mapping.

Exporting data mappings

For exporting the mapping set data to the .csv file, take the steps as described below.

1. Select the mapping set in the Mapping sets panel to the right by clicking it.

2. Press the Export icon residing in the he Import/Export section of the toolbar.

3. Browse to the location of the required .csv file, select it and press Save.

If done successfully, new data will be saved to the .csv file. After opening the .csv file, you can see its data, which differ depending on the selected mappings type (see the example of the .csv file with mapping in Creating a csv file for various mapping types.