Rockwell Automation FactoryTalk View Machine Edition Users Guide - Manual (Page 529)

26 • Set up data logging
26-5
•
•
•
• •
4. Create the run-time application. See Chapter 14.
5. Transfer the run-time application to the run-time platform.
For information about transferring applications to:
 A personal computer, see Chapter 15.
 A PanelView Plus or PanelView Plus CE terminal, see Chapter 16.
6. Run the new application.
Show data logs using the trend graphic object
You can use the trend graphic object to show the data that you’ve logged. At run time,
when the operator opens a graphic display containing a trend, the trend shows values from
the data log file for the data log model that is running. The data log model specifies which
data to collect in the data log file.
In addition to showing historical values from the data log file, trends can show current
values for the tags in the model. Trends can also show current values for tags or
expressions that are not in a data log model. For more information about trends, see
Chapter 28.
Problems with data logging
Problems with data logging occur under these circumstances:
 When your application starts at run time, if any of the tags specified in the current data
log model do not exist, an error message is sent to FactoryTalk Diagnostics.
 If the data log file is corrupted or invalid, the file is deleted and recreated, and an error
message is sent to FactoryTalk Diagnostics.
 If logging to a folder on a networked computer, and the run-time computer is not
logged in to the Windows domain of the network computer, the log folder cannot be
created. An error message is sent to FactoryTalk Diagnostics.
 If logging to an invalid path, the log folder cannot be created. An error message is sent
to FactoryTalk Diagnostics. One of the reasons that the path might be invalid is that
the top-level folder of the path is not shared.
 When the application starts, FactoryTalk View checks whether there is disk space to
store the data log model’s data. If there is not enough space, an error message is sent to
FactoryTalk Diagnostics and data logging does not start.