| Experion HS R530.1 User Assistance

# About configuring history backfill

Most of the configuration tasks associated with using the HC900 Hybrid controller. history backfill functionality must be performed at the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. level using the HC (Hybrid Control) Designer software. This involves configuring a Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. Rate function block Also known as FB. An executable software object that performs a specific task, such as measurement or control, with inputs and outputs that connect to other entities in a standard way. They can be connected and grouped together to construct simple or complex control strategies. You can view function blocks as a symbol, configuration form, as part of a strategy, or as a user-defined view in an operator schematic. See also: function block configuration form, function block faceplate, function block symbol. and several Trend Point function blocks on the controller. Refer to the HC (Hybrid Control) Designer documentation for further details.

After you have assigned points to the Trend Point function block A unit of data and operation within Experion. Experion uses blocks as the component from which control strategies are built. The two categories of blocks are hardware entities and functional entities. in the controller, these points must also be assigned to standard history The type of history that collects one-minute snapshots of point parameter values, as well as a number of averages based on those one-minute snapshots. Compare: exception history, extended history, fast history. See also: history, point parameter. on the server The computer on which the Experion database software and server utilities run. See also: Experion server TPS.. This can be done using Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. (recommended) or directly in Station Experion's main operator interface. Station presents information using a series of displays. See also: display. via the History Assignment displays. You can optionally configure History Archiving (see the topic "History Archiving" in the Server and Client Configuration Guide).

## Configuring history backfill

To allow the history backfill process to operate, you need to change some server settings. Use Station to make these changes.

ATTENTION: Selecting to enable history backfill using the steps below does not trigger a backfill of history; it only enables the history backfill option.

To trigger a backfill of history for a particular controller, go to that controller’s status display and clear the Enable History Backfill check box for at least one minute. Then, select the Enable History Backfill check box. This will trigger history backfill for that controller.

In HC (Hybrid Control) Designer, when configuring Trend Backfill Log Point Selection, you must select Use Modbus Address.

To configure history backfill:

1. From the Station menu, choose ConfigureSystem HardwareServer Wide Settings.

2. Select the History Backfill tab.

3. Select the Enable history backfill check box to enable history backfill.

4. In the Maximum number of days to backfill box, enter the maximum number of days that history can be backfilled (23 recommended).

   Any event data older than this number of days will be discarded and will not be inserted into history. This maximum number of days must not exceed the number of days of standard history snapshots that is configured for the system.