### Trends for Exec 3 and 4 controllers This topic applies to the following hardware: When working with Exec 3 or early Exec 4 controller function blocks that do not have the Exec 4 or 6 type trends under each point, you can use standard trends to trend up to two points in a function block. If you use standard trends and need to configure additional trends, you can use extended trends. For limitations, see To configure Exec 3 and 4 controllers with extended trends. Some Exec 3 controllers support enhanced trends which allow more items to be trended and more flexibility. For more details, see To configure Exec 3 controllers with enhanced trends using XF2 function blocks. For details on configuring historical trends, see Configuring historical trends for Exec 3-style controllers. To configure standard trends for Exec 3 and 4 controllers Click the Trends button drop-down arrow, then a trend item. Click the Enable/Disable tab. 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. The remaining parameters are configured in the same manner as for ExecB trends. Click Accept. Click the View tab to see the trend graph.
Setting | Details
Log Interval | Set the interval value from 1 to 255 minutes. You can show a 24-hour period on a trend graph if you set the interval to 24 minutes for one trend or 48 minutes for two trends. (A controller stores 60 samples for one trend or 30 samples each for two trends.) NOTE Any changes to this value also appear on the equipment's Parameters page.
Enable Historian | Select to have the trend data saved to the server database. NOTE A daily trend report must be configured by enabling Message bit 7 to keep historical trends from Exec 3 controllers. This allows controllers to try to deliver the trends to the server at 1:00 am. See Configuring historical trends for Exec 3-style controllers.
Delete all historical data for this trend log? | 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. The data remains in the database until its age exceeds the number of days defined in this field even if you stop trending a point. NOTE If you type a zero, the WebCTRL® application uses the System Settings page’s Keep historical trends for __ days field.
Inactive Text and Active Text | Type the text you want to appear on the trend graph for the inactive and active (on/off) state of the item being trended.
Click for details below Determining a trend code To configure Exec 3 and 4 controllers with extended trends To configure Exec 3 controllers with enhanced trends using XF2 function blocks Configuring historical trends for Exec 3-style controllers
#### Determining a trend code This topic applies to the following hardware: You must know the available trend codes when configuring Exec 3-style trends. For example, if you want to add a trend in one of the two available trend logs or you want to add a trend log as an enhanced trend, you must know the appropriate trend code. On the Geographic tree, select the equipment. Click Properties. Verify that the Parameters tab is displayed. Click , then select Manual Command. Type `console`, then click OK. Type `cmnet connect`, then press Enter. Type `cmnet iocodes`, then press Enter. Select an available trend code from the list that contains the MbCodes, trend names, point types, and trend codes. For example, the fan start/stop has an MbCode of "fan" and its trend code is 235.
6. #### To configure Exec 3 and 4 controllers with extended trends This topic applies to the following hardware: Extended trends allow up to 2 additional trends per controller for the following situations: When Exec 3 and 4 controllers that have already used both of the trends available in the equipment’s function block need additional trends When the trend code in the equipment’s function block is greater than 255 For limitations, see Trends for converted SuperVision® systems. On the Network tree, select the driver for the device that contains the Equipment Definition that has the point you wish to trend. Click Properties. Verify that the Parameters tab is displayed. Set All Options to Y. Scroll to the bottom of the page. If you have Exec 4 controllers and need to use Exec 3 trends, set This module should display old-style trends to Yes. To obtain the extended trend code, type the following parameters:
   Parameter | Details
   In FB - Type the number of the function block that contains the point to be trended. | This point must be in the same controller as the driver. You can find the function block number at the top of every equipment Parameters page.
   Code - Type the trend code as it would be at the equipment itself to configure the trend. | To obtain this code, see Determining a trend code.
   Type - Type the Type number from the Extended Trend table. | Extended trend types are based on the "type" per the CMnet iocodes output list used to determine a trend code. See Determining a trend code.
The extended Trend Code is calculated and displayed. This code is unique to all points in the controller. Scroll back to the top of the page and enter the Trend Code in the Code field. Click Accept to transfer the changes to the controller.
#### To configure Exec 3 controllers with enhanced trends using XF2 function blocks For some Exec 3 controllers, enhanced trends are used for the following situations: When you need more trends than allowed with standard and/or extended trends To store more than 60 samples per trend You must configure an XF2 function block in the controller as function block number 14 to use enhanced trends. You can then view this function block or piece of equipment from the WebCTRL® Geographic or Network tree. On the Geographic or Network tree, navigate to the function block’s trend information. Click Properties. Toggle any of the channel fields in the Daily Trend Reports section to Yes if you want to enable a trend to log alarms. NOTE These changes also appear on the trend’s Configuration tab. Click Trends, then select one of the trends. Click the Enable/Disable tab. The Log Enable check box reflects your setting from Step 3. Set the remaining trend properties as needed. Click the Configure tab to change the graph’s display settings as needed. NOTE Autoscaling selects the most appropriate display range as defined on the equipment Properties page for each point on the sub-graph.
#### Configuring historical trends for Exec 3-style controllers You can configure Exec 3 standard, extended, and enhanced trends for historical trending. NOTE See To collect trend data for a point. On the Network tree, select the driver. Click Properties. Verify that the Parameters tab is displayed. Set All Options to Y. Type`x` in message bit 7. An Eikon GFB must contain a Message microblock that will generate trend data whenever the microblock is tripped; these messages are treated as critical alarms. A pre-Eikon function block has this functionality built into it. NOTE Pre-Eikon function blocks automatically deliver historical trends at 1:00 a.m.