### Trends for Exec 4 and 6 controllers This topic applies to the following hardware: You can trend input/output points and other wire values that are attached to Trend microblocks on all Exec 6 and some Exec 4 controllers’ GFBs. All trend graph parameters are included from the SuperVision® system during a conversion. Use this procedure if you need to change any of the values. Each trend object can hold 288 samples in the controller. (Historical trends allow the system to extend beyond this limit by transferring trend data to the server.) If you are using an older trend type (such as if all of the options below are npt visible), see Trends for Exec 3 and 4 controllers. To configure trends for Exec 4 and Exec 6 controllers Click the Trends button drop-down arrow, then a trend item. Click the Enable/Disable tab to allow the controller to collect trend data. Type information in the appropriate fields. See below. Click the Configure tab to access the trend graph’s display properties. NOTE Autoscaling selects the most appropriate display range as defined on the equipment Parameters page for each point on the graph. Click Accept. Click the View tab to see the trend graph.
Field | Notes
log interval _:_ | Records (samples) the point's value at the time interval you define. Can be set to a value from 1-255. TIP Since the controller stores 288 samples, you can hold trends in the controller for a 24-hour period by setting the interval to 5 minutes.
Interval in seconds | Changes the log interval from minutes to seconds. NOTE Trend intervals in function blocks in TNI or UNI controllers should be set to one minute or greater. These controllers are not suited to very short trend intervals.
Enable Historian | Select to have the trend data saved to the server database. NOTE An Alarm microblock using the Event ID of "TREND" is required in the function block if you want historical trends from Exec 4 or 6 controllers.
Delete | Deletes the trend’s historical data from the server database.
Keep historical trends for __ days | Type the number of days the database should store a point's data before automatically deleting it. Even if you disable a trend, the data still remains in the database until its age exceeds the number of days defined. NOTE If you type a zero, the WebCTRL® application uses the System Settings page’s Keep historical trends for __ days field to determine the value.
NOTE Multiple trends on a graph are viewed and configured the same as they are in a native WebCTRL® system.
#### Configuring historical trends for Exec 4 and 6 controllers You can save trend data from controllers to the WebCTRL® database. These historical trends can be viewed on the trend graph like any other trend. See To collect trend data for a point. Exec 4 and 6 trends using a Trend microblock must be configured for the point on the Enable/Disable tab of the Trends page by enabling the Enable Trend Log and Enable Trend Historian fields. Each function block with trends that you want stored in the database must also contain trend reporting logic. See Historical trend reporting logic. For Exec 4 and 6 trends, you can also enable the point for reporting by setting the Report field on the Parameters tab of the Properties page to Yes after setting All Options to Yes.