Downloading data

The workstations and controllers in your DeltaV system require configuration data from the DeltaV database in order to operate. Initially, the DeltaV database stores all of the configuration data. You make changes to the configuration in the database without affecting the operation of the controllers and workstations. When the configuration is complete, you download that information to the workstations and controllers.

The data that you download allows the DeltaV system to manage your control strategy. For example, workstations need to know all of the other nodes in the system as well as which areas to monitor and where to record events. Likewise, controllers must have their assigned modules downloaded so that the modules can run in the controller. You must also download the I/O card data so that the controller knows the type and enabled status of the channels and the Device Tag associated with each channel.

You can download any data from within the DeltaV Explorer application. It is possible to download the entire configuration (entire database) or small parts of the configuration by making the appropriate selections within Explorer. For example, the Explorer lets you download a single controller, setup data, I/O card, or module by right-clicking the icon for that item and selecting Download on the context menu. In addition, you can download individual modules from within Control Studio.

A download temporarily disrupts the part of the operation of the controller or workstation that is being downloaded. Care must be taken to determine if the process can withstand this temporary disruption. To ensure the safety of the process, it might be necessary to delay the download of the configuration changes until the process can be shut down. To minimize the effects of such disruption, it is recommended that only those parts of the configuration that have changed be downloaded. This is particularly important in the case of controllers.

Download Physical Network

To download the entire configuration, perform the following steps:

1. Download the physical network.

2. Right-click the Physical Network icon, and then select Download → Physical Network.

   The workstation downloads all of the configuration data for all of the nodes in the system.

Download Control Network

Downloading the control network is the same as downloading the physical network. To download the control network, right-click the Control Network icon, and then select Download → Control Network. The workstation downloads all of the configuration data for all of the nodes in the system.

Full (Total) Download (Workstation or Controller)

To download the entire configuration of a workstation or controller, right-click the item you want to download, and then select Download from the context menu. This downloads the entire configuration for the node selected (workstation or controller) and is called a full (total) download.

Use a full download when the node has not yet been downloaded or has no configuration. Total controller downloads should be avoided when the process is running. If there is already configuration present in the controller, a total download will generally cause parameter values in the controller to be replaced with those from the configuration database. There are some exceptions where matching behavior occurs, such as in controller function blocks directly connected to output channels and for fieldbus shadow blocks. Depending on your configuration you could experience an output disruption on a total controller download.

DeltaV software has a Restore parameter values after restart feature.

Partial Download

If only part of the configuration has changed since the last full (total) download, a partial download may be the best download option. A partial download minimizes disruption to control strategies that are currently running. A partial download occurs when you select one or more modules and initiate a download.

For partial downloads, the software provides the following check box: Review list of fieldbus dependent downloads. Select this check box for items that are associated with fieldbus (for example for a module with blocks running in a fieldbus device). When this check box is selected prior to a download, the software displays a dialog that enables you to select related fieldbus items for download as well. Note that the items are not necessarily listed by device. Rather, the software lists the object by module. Blocks shown at the end of the list may not be associated with the device that precedes them in the list.

When you initiate a partial download, the system sends the module changes to the appropriate controller. However, the new modules will not execute until the running module completes its execution scan. When the scan of the current module is complete, the controller copies the parameter value/function blocks combinations, as defined in the following table. For MODE parameters the system copies the Target Mode field to the new module. The block calculates the Actual Mode field when it begins to execute. Output and control blocks generally start in OOS mode on the first execution after a download (partial and total, and on the first execution after a controller switchover), then climb to their target mode. This provides proper re-initialization and handshaking with other blocks. The mode change is expected and has no adverse effect on control.

On a partial download loops initialize to the current setpoint value regardless of whether setpoint ramping is on.

The system checks for insufficient controller memory. The system displays a warning if there is insufficient memory. Note that the system does not perform this check if you download from the Area folder.

When you perform a partial download from the controller’s Assigned Modules subsystem, the system checks the existing configuration (not the pending download configuration) for the following:

• Insufficient memory

• Module slippage for the assigned modules. If module slippage is present, the system displays a warning.

Note that the system does not perform the insufficient memory or module slippage checks if you download from the Area folder

If the partial download fails because of a controller switchover, the controller that becomes the standby due to the switchover will have a status of No configuration.

The partial download function matches function block parameters (in the old and new versions) by function block name and type. User-defined parameters are matched by name and type. The partial download copy function supports module-level, user-defined parameters for both modules and composites.

You can determine partial download behavior on a module-by-module basis using the Parameter download behavior field on the General tab of the Module Properties dialog. Select one of the following options:

• Preserve critical block values — The controller copies critical function block values from the executing module to the new module during a download. This selection typically minimizes disruption to the process. Critical function block parameters are defined in the table below. 

• Preserve user-defined and critical block values — The controller copies user-defined parameter values from the completed scan of the current module to the new version of the module during a download . When the new module executes its first scan, it uses the copied values in order to minimize process disruption. As shown in the table, only a single field is copied for some of the function block parameters. This is the case because the other fields (for example, Actual Mode) are recalculated on block execution. For user-defined parameters, the entire parameter is always copied.

• Use configured values — The controller does not copy any parameter values from the executing module but uses the values from the configuration database.

Instances when the Parameter Copy function does not occur:

• The function block type is changed.

• The data type of the user-defined parameter is changed. For example, the INPUT1 parameter is changed from type float to type integer.

• The dimension of an array parameter is changed.

• There is no matching parameter or function block.

• Empty dynamic reference - $REF string is empty.

Types of user-defined parameters that do not support the copy behavior:

• External/Internal references - These are always set to the configured value.

• User-defined parameters that are not at the top-level of modules or composites (for example, user-defined parameters that are associated with SFCs or phases inside PLM, SFC, and unit modules).

SFCs do not support the copy behavior for user-defined parameters.

Setup Data Download

You can also download a subset of configuration data that is not directly related to a module. This data is called setup data. Setup data includes named sets, parameter security, cold restart information, redundancy information, alarm preferences, and Event Chronicle definitions. A download of the setup data sends these changes to all the workstations and controllers.

You can download setup data alone or with the configuration data. To download setup data alone, right-click the object in DeltaV Explorer (for example, a controller) in the left pane. Then, select Object → Download → Setup Data. To download setup data along with all other configuration data, select Object → Download → Selected Object.

Delete Unused Assigned I/O Reference Configuration

When the Assigned I/O subsystem is selected, this option appears on the Download menu. It applies to CHARM I/O cards (CIOCs) and CHARMs. After you delete CHARM or CIOC assignments, select this download option to update the configuration in the database.

Delete Unused Configuration

When the Assigned Wireless I/O subsystem is selected, this option appears on the Download menu. It applies to Wireless I/O cards (WIOCs). After you delete WIOC assignments, select this download option to update the configuration in the database.

Delete Unused Card Configuration

When you delete an I/O card using DeltaV Explorer, you must download this change to the controller. The Delete Unused Card Configuration command downloads the deleted card information to the controller configuration without disrupting control or requiring a download of the I/O subsystem. To use this command, right-click the I/O Subsystem for the controller in DeltaV Explorer, and then select Download → Delete Unused Card Configuration.

Resending Successful Downloads

The Resend Last Known Good Download function sends the last successful total download to a node without going to the database. If you have performed a total download followed by one or more partial downloads, this function resends all of the information contained in the total download as well as the partials. For controllers, the function sends the same download script that would be sent to a controller that restarts after a power failure.

This function is especially useful for situations where a workstation fails due to a disk error. It enables you to bring the new or repaired node up to the previous operational status without downloading recent edits to the configuration. Do not use the Resend Last Known Good Download function after decommissioning a controller. Perform a full download after recommissioning a controller.

Downloading Values Referenced from OPC Mirror

Control modules support references to values derived from OPC Mirror. If a module references a value from OPC mirror (for example, using an external reference parameter), the parameter value may change to the default configured value after a download rather than using the value from OPC Mirror. To prevent this, make sure that the Parameter download behavior on the module properties is set to Preserve user-defined and critical block values. Otherwise, you must refresh the associated OPC Mirror pipe in order to restore the value in the module.