# Conditions for Collecting Data

In the Logging Group properties, set the condition for collecting data.

[Value Change] | Use these options to collect data whenever there is a change in the variable value. ### [Execution Condition]
[ON] | Data is collected when the value of the variable set as the [Trigger Variable] turns ON.
[OFF] | Data is collected when the value of the variable set as the [Trigger Variable] turns OFF.
[On Change] | Data is collected when the value of the variable set as the [Trigger Variable] changes.
[Periodic] | Use this option to collect data at regular time intervals. Set the frequency and unit in the [Frequency] and [Units] fields. You can stop collecting data by turning ON the variable set as the [Interlock].
[Script] | Use this option to collect data based on the condition set in a script. In the script editor, set the script to start and stop collecting data. Data Logging

Note:

- The display unit reads values stored in device addresses of associated external variables at the interval set in the scan rate. For example, if the data logging collection cycle is shorter than the scan rate, the same values keep getting collected until the next scan by external variables for device address values.
  For information about scan rate, refer to the following.
  Setting the Interval for Reading External Variable Values (Scan Rate)
- Even if the [Condition Type] is set to [Value Change] or [Periodic], if there is a script that collects data in a [Data Logging] operation, data will be collected when the script is triggered. Note that when data is collected by the script, data is also collected at the [Periodic] or [Value Change] timing.
  Data Logging
  Example: Script is triggered while data is collected every 5 seconds
  : Data collected every 5 seconds
  : Data collected by the [Data Logging] operation

## Maximum Number of Records for Logging Data

As the number of records increase, collecting data at the set timing may not be possible and drawing trend graphs may take more time.

When setting the [Max Record], refer to Guideline for Maximum Number of Records, and verify operations at run time.

Note:

- Plotting many channels and data in trend graphs will reduce performance of the display, even if the number of records is below the guideline.
  About Display Performance of Trend Graphs

- When there are a large number of records, erase logging data to improve run-time performance.
  Data Logging

### Guideline for Maximum Number of Records

#### SP5000 Series Power Box, SP5000X Series

| Number of Variables in Logging Groups
16 | 32 | 64 | 128 | 256 | 512 | 1024
Logging Frequency | 100 ms | 128,000 | 64,000 | 32,000 | 16,000 | 8,000 | – | –
200 ms | 128,000 | 64,000 | 32,000 | 16,000 | 8,000 | 4,000 | –
500 ms | 128,000 | 64,000 | 32,000 | 16,000 | 8,000 | 4,000 | –
1 s | 128,000 | 64,000 | 32,000 | 16,000 | 8,000 | 4,000 | 500

Note:

- The logging frequency in the table refers to the frequency of data collection, regardless of the [Condition Type] setting.
- Combinations that show "-" as a guideline value identify cases that may cause delays in data collection and plotting of trend graphs.

#### SP5000 Series Open Box (Windows 10 IoT Enterprise Model)

| Number of Variables in Logging Groups
16 | 32 | 64 | 128 | 256 | 512 | 1024
Logging Frequency | 100 ms | 640,000 | 320,000 | 160,000 | 80,000 | 40,000 | 20,000 | –
200 ms | 640,000 | 320,000 | 160,000 | 80,000 | 40,000 | 20,000 | 10,000
500 ms | 640,000 | 320,000 | 160,000 | 80,000 | 40,000 | 20,000 | 10,000
1 s | 640,000 | 320,000 | 160,000 | 80,000 | 40,000 | 20,000 | 10,000

Note:

- The logging frequency in the table refers to the frequency of data collection, regardless of the [Condition Type] setting.
- Combinations that show "-" as a guideline value identify cases that may cause delays in data collection and plotting of trend graphs.

#### ST6000 Series or STM6000 Series

| Number of Variables in Logging Groups
16 | 32 | 64 | 128 | 256 | 512
Logging Frequency | 100 ms | 160,000 | 80,000 | 40,000 | 20,000 | 10,000 | –
200 ms | 160,000 | 80,000 | 40,000 | 20,000 | 10,000 | 5,000
500 ms | 160,000 | 80,000 | 40,000 | 20,000 | 10,000 | 10,000
1 s | 160,000 | 80,000 | 40,000 | 20,000 | 10,000 | 20,000

Note:

- The logging frequency in the table refers to the frequency of data collection, regardless of the [Condition Type] setting.
- Combinations that show "-" as a guideline value identify cases that may cause delays in data collection and plotting of trend graphs.

#### GP-4100 Series

| Number of Variables in Logging Groups
16 | 32 | 64 | 128 | 256 | 512
Logging Frequency | 100 ms | 32,000 | 16,000 | 8,000 | – | – | –
200 ms | 32,000 | 16,000 | 8,000 | 4,000 | – | –
500 ms | 32,000 | 16,000 | 8,000 | 4,000 | – | –
1 s | 32,000 | 16,000 | 8,000 | 4,000 | 100 | –

Note:

- The logging frequency in the table refers to the frequency of data collection, regardless of the [Condition Type] setting.
- Combinations that show "-" as a guideline value identify cases that may cause delays in data collection and plotting of trend graphs.

#### IPC Series or PC/AT

| Number of Variables in Logging Groups
16 | 32 | 64 | 128 | 256 | 512 | 1024
Logging Frequency | 100 ms | 1,280,000 | 640,000 | 320,000 | 160,000 | 80,000 | 20,000 | –
200 ms | 1,280,000 | 640,000 | 320,000 | 160,000 | 80,000 | 20,000 | 20,000
500 ms | 1,280,000 | 640,000 | 320,000 | 160,000 | 80,000 | 20,000 | 20,000
1 s | 1,280,000 | 640,000 | 320,000 | 160,000 | 80,000 | 20,000 | 20,000

Note:

- The logging frequency in the table refers to the frequency of data collection, regardless of the [Condition Type] setting.
- Combinations that show "-" as a guideline value identify cases that may cause delays in data collection and plotting of trend graphs.