Be sure you have navigation buttons to get to and from this display. Add the object as large as possible onto this display.
On a new display, go to Objects | Trending | Trend. Create the FactoryTalk View SE TrendsĪt last, we’ll add the trend chart. Close your macro, and save it as “Startup”. Right-Click Macros, and add a new macro.Īdd the command as shown below. In this case, though, we’ll create a new startup macro. Where MyDataLog is the name of the data log you just created. If you are modifying an existing project, just add the command “DataLogOn MyDataLog”. A startup macro allows us to do this, and many other commands we might wish to run at startup.
We need the data log model to run at startup. In this example, I’ll name it “MyDataLog”. Be sure to hit the “Add” button after selecting your tag, so the tags appear under “Tags in Model”.
It’s most important to go to “Tags In Model”, and add the tags you wish to log. This is not the amount of time from left to right across the trend chart. Go to Log Triggers, and define how often you need to sample the tag. In this case, we will leave the settings at default, but you could choose when you would like to start a new log file on your storage device. Conversely, you could log to an SQL Server using an ODBC connection.Īt this time, let’s leave the paths at their default location. For example, we’ll just log to a file set. In the general tab, we will obviously put in a description of our chart. Create the Data LogĪt first, we’ll right click the data log models, and add a new data log. Altogether, we’ll have a trend chart where the operator can view data from any point in time. We’ll run the data log in a startup macro, and associate the data log to a trend chart.
FactoryTalk View SE Trends and Data Logīasically, we’ll walk through how to create a data log.Beginning a FactoryTalk View SE Project.Derivative Settings for ControlLogix PID Enhanced.Integral Settings for ControlLogix PID Enhanced.Proportional Settings for ControlLogix PID Enhanced (PIDE).Proportional, Integral, Derivative (PID).For the logical view and for comparisons, the project data in the local working directory is used and not the centrally stored data of FactoryTalk View Studio.versiondog does this using the Application Manager’s restore. The APA files will only be transferred back to the FactoryTalk View Studio central data bank if the editor is installed. On Check-Out or when copying a version to a directory, versiondog checks whether FactoryTalk View Studio is installed on the client.versiondog does this using the Application Manager’s Backup function. However, if the editor is installed, the working directory is also automatically updated with a new APA. If the editor is not installed, a straightforward comparison between the contents of the working directory and the previous version will be made. Prior to a comparison, versiondog checks to see if FactoryTalk View Studio is installed on the client.For this reason, you need to be aware of the following: To create a base version of a versiondog FactoryTalk View component, you need to create the APA file using the Application Manager then copy it into the working directory.
The FactoryTalk View Studio software stores project data centrally. Key features Custom component type for FactoryTalk View ME and SEįactoryTalk View project tree supported by the Logical viewĬlear presentation of complete change history The SQL Server version needs to be compatible with the data bank version of the FactoryTalk View project. The versiondog comparator for FactoryTalk View requires a valid installation of SQL Server (at least Express Edition). It is currently not possible to create a restorable backup using an upload job. The versiondog system supports the management of Rockwell FactoryTalk View Machine Edition (ME) and Rockwell FactoryTalk View Site Edition (SE) projects. Versiondog 7.5.1: Rockwell FactoryTalk View ME/SE