Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Select [Tools] - [Data Logger] from the main toolbar to open the [Data Logger] window. From this window, users can configure new data loggers, edit existing data loggers, and attach tags to data loggers. Users can create a new data logger by pressing the (blue star) icon or by right-clicking and selecting [New Data Logger].

(1) Logger Settings

Once a new data logger has been created, the user is presented with the above [Logger Settings] tab. The features in this tab are explained in further detail in the following table.

Item

Description

Logging Model Name

Enter the name of the Data Logging model. You may use alphanumeric characters, Korean alphabets, and special characters as the model name. You cannot use a duplicated model name.

Max Logs

The maximum number of rows for the data logger. If the data logger hits the set maximum value in operation, the data logger continues to operate by discarding the oldest logged value for a new value.

Time Stamp Format

Allows the user to customize the formatting of timestamps for the data logger’s data points.

Start Options

Start Up

Enables the data logger on device start up.

Manual

Enables the data logger on execution of a 'datalog.start(“Insert Logging Model Name”)' command.

Condition

Enables the data logger when the [Trigger Tag] or address value meets the conditions specified by the [Comparison] and [Value] fields. When this option is used, the comparison condition is structured as follows: [Trigger Tag] [Comparison] [Value].

Example: For a Trigger Tag ‘Celsius’, a greater than comparator, and a value of 5, the comparison would be structured as follows:

‘Celsius’ > 5

Trigger Tag

Tag referenced by the [Comparison] operator.

Comparison

Allows the user to select from six possible comparators: equal [=], does not equal [!=], greater than [>], greater than or equal to [>=], less than [<], and less than or equal to [<=].

Value

A numerical value or tag to be compared to the [Trigger Tag].

Logging Options

Allows the user to modify when a new row is added to the data logger. Note that the data logger must be started before a new row can be added.

Periodic

Adds a row to the data logger at a set interval. Users can adjust this interval using the [Hours], [Minutes], [Seconds], and [Milliseconds] command.

Tag Value Change

Adds a row to the data logger upon a change in the [Trigger Tag]'s value.

Manual

Adds a row to the data logger upon execution of a ‘datalog.addrow(“Insert Logging Model Name”)' command.

Condition

Adds a row to the data logger when the [Trigger Tag] or address value meets the conditions specified by the [Comparison] and [Value] fields. When this option is used, the comparison condition is structured as follows: [Trigger Tag] [Comparison] [Value].

Example: For a Trigger Tag ‘Celsius’, a greater than comparator, and a value of 5, the comparison would be structured as follows:

‘Celsius’ > 5

Trigger Tag

Tag referenced by the [Comparison] operator.

Comparison

Allows the user to select from six possible comparators: equal [=], does not equal [!=], greater than [>], greater than or equal to [>=], less than [<], and less than or equal to [<=].

Value

A numerical value or tag to be compared to the [Trigger Tag].

2) Tag List

This tab of the [Data Logger] menu allows the user to assign multiple tags to a Data Logging Model. A new tag can be added by pressing the (blue star) icon, or right-clicking and selecting [Add Tag(s)]. After selecting this option, users will be presented with a new pop-up window that functions similarly to the [Tag Browser]. Users can add selected tags by checking the box next to the tag, then pressing the [Select] button. Users can also remove tags from the Data Logging Model by pressing the (blue star) icon or right-clicking and selecting [Delete].

(blue star)

  • Since the data is logged in the block unit, the block must be created in advance.

  • If a block is full, you must create a new block to continue the data logging.

  • If the number of blocks reaches the maximum, the next block will be created after the deletion of the oldest block.

  • Before saving the CSV file, check the volume of the storage. It is recommended to save the files in USB or SD memory.

  • If the configuration of the data logging model has changed and the project is written to the Xpanel, the former project’s entire blocks will be deleted. (CSV files are not deleted.) Thus, back-up is needed when updating.

  • The data log file is stored in the Xpanel in the following location: \Xpanel\Log\“LogModelName”

  • No labels