In the generic section:

• Name → reset
• File name → reset

In the MMS sever configuration section:

• NIC name → keep
• IP address → keep
• TCP port → keep

In the data model section, only applicable parameters are in the data attributes:

• Name → reset
• Functional constraint → reset
• Data set reference(s) → reset
• Control block reference(s) → reset
• Add MMS data point → keep

The information below applies only if the FC (Functional Constraint) was and remained MX (measurement):

• Output RMS → keep
• RMS number of samples → keep
• RMS gain → keep

In the Data sets section, FCDAs can only be flagged as added or removed. This happens when the combination of node path, data object, data attribute and functional constraint cannot be found in both files.
Therefore, it can be said that the entire contents of a data set is reset. For each FCDA of the data set:

• Node path → reset
• Data object → reset
• Data attribute → reset
• Functional constraint → reset

• SV ID → reset
• SV control block name → reset
• SV path → reset
• SV type → reset
• Sampling rate → reset
• Nominal frequency → keep
• Dataset → reset
• Dataset path → reset
• Description → reset
• Configuration revision → reset
• Number of ASDU → reset

In the Publish section:

• Enable publishing → keep
• Publishing ethernet adapter → keep
• Publishing IED → reset

In the Subscribe section:

• Enable subscribing → keep
• Subscribing ethernet adapter → keep
• Subscribing IED → keep
  (IED that were removed during the file change will also be removed from this field)

In the SV elements section:

• MAC address → keep or reset
• App ID → reset
• VLAN ID → keep or reset
• VLAN priority → keep or reset

• Rpt ID → reset
• Report control block name → reset
• RCB path → reset
• RCB type → reset
• Dataset → reset
• Dataset path → reset
• Description → reset
• Configuration revision → reset

In the Report section:

• Enable reporting → keep
• Server IED → reset
• Client LN → reset
• Maximum number of clients → reset
• Indexed reports → reset
• Integrity period [ms] → reset
• Buffer time [ms] → reset

In the Trigger options section:

• Data change (dchg) → keep or reset
• Quality change (qchg)  → keep or reset
• Data update (dupd)  → keep or reset
• Periodic integrity → keep or reset
• General interrogation (gi) → keep or reset

In the Optional fields section:

• Sequence number (seqNum) → keep or reset
• Timestamp (timeStamp) → keep or reset
• Dataset (dataSet) → keep or reset
• Reason code (reasonCode) → keep or reset
• Data reference (dataRef) → keep or reset
• Entry identification (entryID) → keep or reset
• Configuration reference (confRef) → keep or reset
• Buffer overflow (bufOvfl) → keep or reset

Add the data attribute to the MMS server instantiated on the simulator. This means that any client connecting to the server will be able to read the attribute and/or write into it (if the functional constraint permits it).
Enabling a report using a dataset that contains this attribute will cause this field to be automatically enabled as well.

If this field is grayed out, there are several explanations:

• if the FC is CO, it means the current attribute can only be enabled through its parent object's Enable as controllable object field
• if the FC is not CO and:
  • the field is enabled, it means the current attribute is in use by a report control block; the field is grayed out to prevent disabling it while a report needs it
  • the field is disabled, it means the FC of the current attribute is not supported

Note: since attributes with FC = CO are parameters for control commands sent by the client, they are considered pseudo-attributes. Therefore, they cannot be read or written the same way as other attributes. They can be added to the IED tree but they will not have any connection points to allow their control by the user in the model.

The value placed in the server for the attribute will be its RMS calculation.
This field is only available for attributes with the MX (measurement) functional constraint and it can be changed only if the field Add MMS data point above is enabled.

Number of samples to accumulate for each RMS calculation.
This field is only available for attributes with the MX (measurement) functional constraint. It can be changed only if the fields Add MMS data point and Output RMS above are enabled.

Gain to apply to each RMS calculation. The value placed in the server contains this gain.
This field is only available for attributes with the MX (measurement) functional constraint. It can be changed only if the fields Add MMS data point and Output RMS above are enabled.

The network interface card name used to publish the GOOSE message.
The proper adapter should be selected based on the information given by the Linux command "ifconfig" or Windows command "ipconfig".

The name of the IED publishing the GOOSE message.
This field is non-editable.

This section contains fields to configure the subscription to the GOOSE message.

Enable subscribing to the GOOSE message.
Having this box checked will create the connection points associated with the subscription to the message. It will also ensure that subscription will start as soon as the simulation will start.

The network interface card name used to subscribe to the GOOSE message.
The proper adapter should be selected based on the information given by the Linux command "ifconfig" or Windows command "ipconfig".

List of subscribing IED. This list is built manually according to the user's setup, with more than one choice possible. The options offered are the elements of the interface's IED list.
This field is not used in the real time simulation.

This section contains fields specific to GOOSE messages.

The MAC multicast destination address associated with the GOOSE message (e.g. '01-0C-CD-04-00-00'). This field is initially filled based on information from the SCL file but it can be changed by the user as needed.
It must respect the following format: 'xx-xx-xx-xx-xx-xx', where x represents a hexadecimal digit. 

The App ID associated with the GOOSE message. It is automatically filled based on information from the SCL file and it should be unique within the entire IEC 61850 network.
This field is non-editable.

The VLAN identifier associated with the GOOSE message. Along with the VLAN priority parameter below, it allows advanced configuration of smart switches to handle packet priorities on the network. 
This parameter is only taken into account if the Enable use of VLAN for SV and GOOSE telegrams checkbox in the General configuration is enabled.
The field is initially filled based on information from the SCL file but it can be changed by the user as needed.
Values accepted are between 1 and 4095.

The VLAN priority associated with the GOOSE message. Along with the VLAN ID parameter above, it allows advanced configuration of smart switches to handle packet priorities on the network. 
This parameter is only taken into account if the Enable use of VLAN for SV and GOOSE telegrams checkbox in the General configuration is enabled.
The field is initially filled based on information from the SCL file but it can be changed by the user as needed.
Values accepted are between 1 and 7.

The message retransmission delay used immediately following a change in any of the dataset members of the GOOSE message. The field is initially filled based on information from the SCL file. If the information is missing in the file, a default value of 62.5 ms is used. This value can be changed by the user as needed.

The maximum message retransmission delay reached when no changes occurred in any of the dataset members of the GOOSE message. The field is initially filled based on information from the SCL file. If the information is missing in the file, a default value of 1000 ms is used. This value can be changed by the user as needed.

The unique identification of the SV message.

For SV type 9-2LE: This field is editable. The user convention IEC61850-9-2LE recommends using the following format: "xxxxMUnn", where "xxxx" is the concatenation of the substation name, voltage and bay levels and "nn" identifies the measuring point. 
For SV type IEC 61869-9: This field is non-editable.

The name of the control block describing the SV message.

For SV type 9-2LE: Not applicable, field not used for this type.
For SV type IEC 61869-9: This field is non-editable.

The path of the SV control block within the IED.

For SV type 9-2LE: Not applicable, field not used for this type.
For SV type IEC 61869-9: This field is non-editable.

The number of samples per cycle associated with the SV message. 

For SV type 9-2LE: This field is editable.
For SV type IEC 61869-9: This field is non-editable.

The power system frequency associated with the SV message.
This field is editable.

The name of the dataset used by the SV message.

For SV type 9-2LE: Not applicable, field not used for this type.
For SV type IEC 61869-9: This field is non-editable.

The full path within the IED of the dataset used by the SV message.

For SV type 9-2LE: Not applicable, field not used for this type.
For SV type IEC 61869-9: This field is non-editable.

The description of the SV message, retrieved from the SCL file.

For SV type 9-2LE: Not applicable, field not used for this type.
For SV type IEC 61869-9: This field is non-editable.

The configuration revision number of the SV message.

For SV type 9-2LE: Not applicable, field not used for this type.
For SV type IEC 61869-9: This field is non-editable.

The number of samples embedded in each packet of the SV message.

For SV type 9-2LE: The value updates based on the sampling rate: for 80 samples per cycle, the number of ASDU is set to 1; for 256 samples per cycle, it is set to 8. This field is non-editable.
For SV type IEC 61869-9: The value is defined in the SCL file. This field is non-editable.

For SV type 9-2LE: The publishing IED is selected manually according to the user's setup. The options offered are the elements of the interface's IED list. This field is not used in the real time simulation.
For SV type IEC 61869-9: This field is non-editable and it is necessary for the real time simulation. The information is extracted during the parsing of the SCL file.

The MAC multicast destination address associated with the SV message (e.g. '01-0C-CD-04-00-00'). It must respect the following format: 'xx-xx-xx-xx-xx-xx', where x represents a hexadecimal digit. 

For SV type 9-2LE: This field needs to be configured by the user. To simplify the process, the first 8 digits are provided. Nevertheless, the field can be changed entirely to suit the simulation needs.
For SV type IEC 61869-9: This field is initially filled based on information from the SCL file but it can be changed by the user as needed.

The App ID associated with the SV message.

For SV type 9-2LE: The App ID is set by default to the value 0x4000. This field is non-editable.
For SV type IEC 61869-9: The App ID is automatically filled based on information from the SCL file and it should be unique within the entire IEC 61850 network. This field is non-editable.

The VLAN identifier associated with the SV message. Along with the VLAN priority parameter below, it allows advanced configuration of smart switches to handle packet priorities on the network. 
This parameter is only taken into account if the Enable use of VLAN for SV and GOOSE telegrams checkbox in the General configuration is enabled.
For SV type IEC 61869-9, the field is initially filled based on information from the SCL file but it can be changed by the user as needed.
Values accepted are between 1 and 4095.

The VLAN priority associated with the SV message. Along with the VLAN ID parameter above, it allows advanced configuration of smart switches to handle packet priorities on the network. 
This parameter is only taken into account if the Enable use of VLAN for SV and GOOSE telegrams checkbox in the General configuration is enabled.
For SV type IEC 61869-9, the field is initially filled based on information from the SCL file but it can be changed by the user as needed.
Values accepted are between 1 and 7.

Defines the maximum number of clients that can connect to this report type.
This field is non-editable.

When reports are indexed, their names are built by appending a suffix from 1 to 99 (representing the instance index) to their name.
This field is non-editable.

This value is only relevant if the trigger option Periodic integrity is enabled. Reports containing all dataset members will be generated periodically at the interval (in milliseconds) dictated by the value in this field.
This field is non-editable.

Amount of time in milliseconds between the detection of a trigger and the transmission of a report. If multiple attributes generate a trigger during this interval, they will all be added in the same report.
This field is non-editable.

Trigger options section, it contains fields to configure when reports are sent. All items below are editable.

Triggers sending a report upon detecting a change in the dataset members' attributes.

Triggers sending a report upon detecting a change in the dataset members' quality attributes.

Triggers sending a report upon detecting an update in the dataset members' attributes. The report will be sent if the value written into the triggering attribute is the same as the previously stored one.

Enables sending a report periodically. The interval is dictated by the value in the Integrity period [ms] field.

Enables sending of reports at the client's request.

Optional fields section, enabling an element below will ensure that it will be included in the reports sent. All items below are editable.

When enabled, will include the sequence number in the reports sent.

When enabled, will include the entry time in the reports sent.

When enabled, will include the name of the dataset used by the report control block.

When enabled, will include the reason for creating the report. The reason is set according to the trigger that caused the report to be sent.

When enabled, will include the name of the data attribute that triggered the report transmission.

When enabled, will include the entry ID for the report.

When enabled, will include the configuration revision number of the report control block.

When enabled, will include information about any potential buffer overflow.