• Manual: Starting and stopping the recording is done manually, through the API.
• Automatic: Logging starts automatically at the load of the model and stops at reset.

Choice for the format of the file containing the recorded values of the monitored signals:

• OPREC (native format)
• CSV (EXCELComma-Separated Values)
• MATLAB

If selected, the name of the output file will be automatically generated. Naming collisions are therefore avoided as name uniqueness is ensured by appending the timestamp to the filename.
The automatic file name is a combination of the model name, the subsystem name, and the date and hour.

Note that the seconds in the generated file name correspond to the time at which the DataLogger prepares the recorded/saved file. This may occur just before the recording starts, or at some time before when a trigger is configured.

To provide a custom name for the file, the field must be unchecked. As a result, the Output file name and Append Timestamp fields are made available.

Activate this to append the timestamp to the end of the filename in the following format: <Year>-<Month>-<Day>-<Hour><Minutes><Seconds>.
Appending a timestamp ensures that files will not be overwritten for each simulation run.
This field is only visible if the Output file auto naming field above is unchecked.

Specifies the logging frequency based on a factor of the simulation time step.
For instance, with a decimation factor equal to 1 the data is saved every step. If the decimation factor is 2, the data is saved every 2 steps.

The Frame length parameter specifies how many steps are to be recorded without any data loss.

A frame corresponds to the number of consecutive steps without loss. Depending on the hardware configuration, some steps may be lost between two frames.
This zone of possibly lost data is called the blind area. This area is not visible and is thus not captured by the data logging system. Because the data are stored in a file, users may see missing samples between these frames. 
The size of the blind area depends on many factors such as the number of signals stored, the sampling frequency, the speed of the simulator, the disk speed, etc.

Specifies when a trigger event is generated, depending on the Trigger level or Trigger polarity fields.

• Edge: recording starts as soon as the signal moves into the polarity region specified in the Trigger polarity field (which takes place, conceptually, in an instant)
• Level: recording starts when the signal crosses the value set in the Trigger level field (which will be true over a period of time)

Recording starts when the trigger signal is greater (Positive) or less (Negative) than the parameter Trigger level.

Together with the Trigger function and Trigger level, this parameter determines the trigger condition:

When the Trigger function is set to Edge:

• Positive polarity: the trigger condition is met when the trigger signal becomes higher or equal to the value in the Trigger level field
• Negative polarity: the trigger condition is met when the trigger signal becomes lower or equal to the value in the Trigger level field

When the Trigger function is set to Level:

• Positive polarity: the trigger condition is met whenever the trigger signal is higher than the value in the Trigger level field
• Negative polarity: the trigger condition is met whenever the trigger signal is lower than the value in the Trigger level field

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.

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.

0-1

TRUE

TRUE

TRUE

TRUE

TRUE

TRUE

TRUE

TRUE

10

TRUE

TRUE

TRUE

Data

From model

Data (write)

If an attribute:

• is enabled in the IED tree
• is not part of any data sets used by reports
• has functional constraint (FC) equal to SP, SV, CF, DC , SE or BL or it is one of the attributes mentioned above part of a controllable object

→ then it will also provide a connection point from the driver to the model.
Its format represents its full path within the IED with the suffix that denotes it being written externally:
IED / Access point / Logical device / Logical node / Data object / Data attribute (write)

To model