DataLogPro editor properties

TIP:
If you have enabled HTTPS using a self-signed certificate created in IIS, the DataLogPro editor will not work. To avoid this problem, use a CA-signed certificate, or create a self-signed certificate through PowerShell, using the following command:
New-SelfSignedCertificate -FriendlyName
.Any_Cert_Name
-DnsName Your_Server_PC_Name
-CertStoreLocation Cert:\LocalMachine\My -KeyUsage DigitalSignatureThe following table shows the properties in the
DataLogPro
editor.Property | Description |
---|---|
1 - Menu bar | |
New Group | Creates a log group. |
Save | Saves the current data log configuration. |
Export | Exports the entire data log configuration in a CSV file, including all log groups, tags, and trigger properties.
It always exports the entire configuration no matter which group or tag is selected. |
Import | Imports an existing data log configuration. |
Setting | Configures which database to log the historical data and the storage duration.
Select Local database to log the data in the built-in InfluxDB and select Remote database to log the data in the external InfluxDB.To use an external InfluxDB, make sure to create a database connection first in FactoryTalk View Studio > System > Connections > Databases , and then select the database definition name here. The address and organization will show for the external InfluxDB.Storage duration defines how long the data logging records are stored. When the number of days, weeks, or months has elapsed, the older logs are deleted. By default, all data will be stored without being deleted. To avoid consuming disk space, set a proper time span for data storage. |
Migrate | Migrate data log model's historical data that's stored in file sets to DataLogPro.
Before the migration, make sure to add the list of tags to DataLogPro first. |
2 - Log groups | |
All tags | Lists all the tags in the editor, including all the grouped and ungrouped tags. |
Ungrouped tags | Lists all the tags in the editor that are ungrouped. |
User created groups | Lists all the created log groups.
This is where you configure group properties, that is how to trigger logging for this group. A small icon on the group indicates its trigger property, periodic ![]() ![]() ![]() When you delete a group, you can remove tags in it or keep them as ungrouped tags. |
3 - Table in the workspace | |
Columns | The columns are properties associated with the selection in the Log groups pane. The columns vary depending on your selection. |
Search by tag name | Filters the tags with the string you enter. |
4 - Database connection status | Shows whether it's connected to the local or external InfluxDB database. |
Side bar | |
5 - Tag Browser | Opens the Tag Browser.
You can drag and drop tags or click + to add one or more tags for logging. |
6 - Properties | Opens the Group properties or Tag properties pane. This is where you configure the trigger properties for log groups or tags. |
The following table shows the options if you select
Periodic
as the trigger property.Option | Description |
---|---|
Periodic | Select this option to log tag values periodically. |
Interval | Type a number and select a time unit to specify how often tag values are logged. All tags are logged each time this interval expires. The default interval is 10 seconds. |
The following table shows the options if you select
OnChange
as the trigger property.Option | Description |
---|---|
OnChange | Select this option to only log tags whose values have changed. |
Maximum update rate | Type a number and select a time unit to specify the maximum rate at which tags are updated. The default maximum update rate is 1 second. |
Deadband mode | Select one of the options:
|
Deadband value | Only applicable when Percentage or Absolute is selected as the deadband mode. |
Heartbeat | Type a number and select a time unit to specify how often tag values are logged even if no change has occurred. The heartbeat ensures that the logged data is current. The heartbeat rate must be equal to or greater than the update rate.
Whenever there is a tag value change, a new heartbeat starts at that moment, and a new value is logged. If that value remains by the end of the heartbeat, that new value will be logged again. The heartbeat value will automatically approximate to the nearest integer multiple of the maximum update rate. For example, if the maximum update rate is 3 seconds and heartbeat is set to 10 seconds, the actually heartbeat rate is 9 seconds. Specify 0 for the heartbeat if you do not want to use it. Tag values will be logged only when they change. The default heartbeat is 0 seconds. |
The following table shows the options if you select
OnDemand
as the trigger property.Option | Description |
---|---|
OnDemand | Select this option to log tag values when the FactoryTalk View command DataLogSnapshot is issued.
This command can be issued anywhere that other FactoryTalk View commands and macros can be. For example, you can type it in the command line or specify it as the action for an event. If you specify Periodic or On Change , you can still use On Demand logging whenever it is appropriate. |
Maximum update rate | Type a number and select a time unit to specify the maximum rate at which tags are updated. The default maximum update rate is 1 second. |
Provide Feedback