When you select a download option, the system evaluates the data in the database for possible errors or omissions to determine if it can be downloaded. For example, if you have a module referencing I/O from a different controller node, the system displays a dialog that informs you of that fact. In the same way, the system displays a dialog if function blocks in a fieldbus module have not been assigned to fieldbus devices. The dialog has the following buttons: Download Anyway, Print, Cancel. The user selects one of these in order to cancel or proceed with the download.
If any online parameter changes have been made since the previous download, the DeltaV system stores these changes in a temporary file. When you download a controller or a module for a controller, the DeltaV system compares the temporary file with DeltaV database and presents these changed parameters in an Upload dialog.
It is possible for a DeltaV user to make online changes between the time a user requests the download and the time the system transfers the data. Online changes made within this window of time are not displayed as uploadable parameter changes. For this reason, it is important for users performing downloads to coordinate the downloads with those who have permission to make online parameter changes.
If you decide to continue downloading, the system downloads the data to the appropriate nodes and stores a copy of the data on the ProfessionalPLUS workstation in the DeltaV\DVData\POWERUP directory. If the download includes controllers (partial or total), the system also transfers the downloaded information to controller flash memory. This enables the controller to perform a cold restart and download itself if power fails and is restored.
The download progress log is saved to DeltaV\DVData by default for workstations in the control network. It is saved to DeltaV\DVData\RemoteSystems\identifier for Remote Operator Stations.
CAUTION!For blocks assigned to non-bus I/O cards (excluding Provox and RS3 I/O), only the channels that have been modified will be affected by a download. All other channels will hold their values and status during the download to prevent disruption to the I/O. For blocks tied to bus cards (AS-I, DeviceNet, H1 fieldbus, Profibus DP, Serial), a download can potentially bump the I/O and cause the controller to hold values. To prevent bumped I/O or held values during a download, place the block producing the output in Manual mode before downloading. Be sure 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.
Alarm parameter fields all get initialized to their default (or configured) value as is appropriate, the first execution cycle of the module establishes the initial alarm state for it's alarms. In practice, this means that inactive, unacknowledged alarms appearing in the alarm list prior to a download will not be in the list after the download because they are initialized to acknowledged by the download.
Downloading large modules to a controller can use a large amount of system resources. Exact amounts vary depending on the module being currently run by the controller and the size of the module being downloaded. To ensure that you do not have a problem with system resources, place the running block in manual mode before you download.
Large databases require significant amounts of free disk space in order to download successfully. Make sure that there is a least half the size of the database in free disk space before downloading the database.