Download / Deploy / Checkpoint

Download is the process of updating the CP database to the controls configuration that was saved during the last checkpoint operation. Compounds and blocks are downloaded or deployed to the CP. On completion of the download, the CSA and the checkpoint file on the CP’s host workstation are updated. Selecting Checkpoint from the Configurator downloads controls changes in the Configurator to the CP database.

The downld.exe process runs for a short time after a CP starts up, then stops. It establishes communication with the host WSTA (SMDH turns from red to yellow or white). On a real self-hosting CP, the CP requests a copy of the checkpoint file from the download server (the host WSTA). This file is then copied into the control station’s flash memory. The same behavior occurs with SCP.

Deploy is valid for IACC and Foxboro Evo environments. As with ICC, compounds and blocks are downloaded. For Foxboro Evo, two additional targets are updated: Security access settings and Wonderware History application objects. If an object is later modified in Foxboro Evo, re-deploy implements the changes in the runtime environment and only modified parameters are downloaded. Foxboro Evo provides flexibility to deploy just a strategy, just a compound, or, with cascade deploy, an entire controller.

No underlying mapping updates are needed to deploy to an SCP application. A Galaxy with multiple CPs can be used as is and deployed in to the SCP computer under each individual CP.

SCP software operates under two use cases:

For Standalone mode, which would be typical for a Foxboro Delivery engineer, treat SCP as a real CP270 / CP280 / FDC280. No special provision is required.

For OTS Engine mode, if the simulation is frozen when Deploy/re-Deploy occurs, blocks will not process and the Checkpoint file will not be valid. Typical feedback for unprocessed blocks might include cyan-colored blocks in the Detail Display that have no warning messages, or a large number of blocks in Manual in a refreshed FoxSelect/BlockSelect. Run the simulation, freeze, and re-Checkpoint each CP where the controls have changed.