Control Database Deployment User's Guide: Foxboro Evo Process Automation System

Foxboro Evo™
Process Automation System
Control Database Deployment

User’s Guide
*B0750AJ* *M*
B0750AJ
Rev M
January 30, 2014
All rights reserved. No part of this documentation shall be
reproduced, stored in a retrieval system, or transmitted by any means,
electronic, mechanical, photocopying, recording, or otherwise,
without the prior written permission of the Invensys Systems, Inc. No
copyright or patent liability is assumed with respect to the use of the
information contained herein. Although every precaution has been
taken in the preparation of this documentation, the publisher and the
author assume no responsibility for errors or omissions. Neither is any
liability assumed for damages resulting from the use of the
information contained herein.
The information in this documentation is subject to change without
notice and does not represent a commitment on the part of Invensys
Systems, Inc. The software described in this documentation is
furnished under a license or nondisclosure agreement. This software
may be used or copied only in accordance with the terms of these
agreements.
© 2006–2014 Invensys Systems, Inc. All Rights Reserved.
Trademarks
Invensys, ArchestrA, FoxView, Foxboro, Foxboro Evo, Foxboro Evo
logo, InTouch, InFusion, I/A Series, Invensys logo, and Wonderware
are trademarks of Invensys plc, its subsidiaries and affiliates.
All other brand names may be trademarks of their respective owners.
iii
Contents
Before You Begin ................................................v
About This Book .................................................................................... v
Revision Information.............................................................................. v
Reference Documents ............................................................................ v
Documentation Specific to the Foxboro Evo Control Software......... v
CHAPTER 1: Deployment ...................................1

Introduction ............................................................................................ 1
Deploying Control Objects..................................................................... 8
Select Objects for Deployment......................................................... 10
System Validations ........................................................................... 15
Object Validations............................................................................. 17
Deployment Progress........................................................................ 21
Redeploying Modified Compounds and Blocks............................... 26
Redeploying Foundation Fieldbus Blocks........................................ 27
Strategy Editor Deployment of the Blocks....................................... 31
Undeploying Control Objects............................................................... 35
Undeploying a Controller ................................................................. 36
CHAPTER 2: Deployment Utilities ...................39

Bulk Upload ......................................................................................... 39
Resetting Compounds and Blocks........................................................ 40
Selective Upload/Deploy...................................................................... 41
Checkpointing ...................................................................................... 43
Synchronize DBs.................................................................................. 43
Synchronize Deploy Status (Changing a Deployed State) ................... 44
Upload Compare .................................................................................. 45
CHAPTER 3: Change Tracking.........................47

Overview .............................................................................................. 47
Tracking Deployment Events ........................................................... 48
Tracking Field Device Manager Downloads .................................... 49
Setup at the FoxCTS Server ................................................................. 50
FoxCTS Directory for Event Files.................................................... 50
Authorize User Access ..................................................................... 51
Foxboro Evo Control Software Setup .................................................. 52
Specify the FoxCTS Server .............................................................. 52
Start the FoxCTS Transfer Service ................................................... 53
Enable Change Tracking................................................................... 53
Start the FoxCTS Transfer Monitor.................................................. 55
Control Database Deployment User’s Guide – B0750AJ Rev M

iv Contents
Monitoring Transfers ............................................................................56
CHAPTER 4: Control Processor Memory

Management ......................................................59
Memory Preservation Bit Configuration...............................................59
Use of Sequence Block CSPACE Parameter ........................................62
Deploy Options Dialog Box ..............................................................63
Messages Related to CSPACE/Sequence Block Deployment...........67
Setting “Deploy Options” using Direct Access.................................73
CHAPTER 5: Additional Management

Procedures ........................................................75
Checkpoint Failure After Large Deployment of Sequence Blocks.......75
Concurrent Deployment Workflow.......................................................76
Additional SMC Log Messages/Descriptions.......................................77
Control Processor Timing Out...........................................................77
Network Interruption During ArchestrA Operation ..........................77
Deployment or Undeployment of Multiple
Compounds from Multiple Workstations ..........................................77
Deployment of PLB Blocks ..................................................................77
Index ..................................................................79

v
Before You Begin
About This Book

This guide describes how to deploy control strategies developed using the
Foxboro Evo™ Control Editors (hereinafter referred to as Control Editors) to a
controller.
Revision Information
For Revision M of this document, the following changes were made:
Chapter 4, “Control Processor Memory Management”
• Updated the Ignore CSPACE option under “Deploy Options Dialog Box”
on page 63.
Chapter 5, “Additional Management Procedures”
• Added section “Concurrent Deployment Workflow” on page 76.
Reference Documents
Since Foxboro Evo Control Software (hereinafter referred to as the Control
software) provides additional and customized features for the ArchestrA®
System Platform, which incorporates Wonderware® products, much of the
documentation written by Wonderware is relevant. In addition, there are
documents that describe features specific to the Control software. Below is a
list of documents that can provide additional information that is beyond the
scope of this document. These documents can be accessed from the Invensys
Global Customer Support Web site:
http://support.ips.invensys.com
Documentation Specific to the Foxboro Evo

Control Software
During the Control software installation, the documents associated with the
software components being installed are also installed. These documents can
be viewed from the Start > Programs > Invensys > InFusion
Documentation menu. These documents are also provided on the Control
software installation media.
The guide assumes that you are already familiar with the Strategy Editor, the
Block Configurator and the other Control Editors. Refer to the following
documents for specific information about related configurators and editors:

vi Before You Begin
• Appearance Object Editor User's Guide (B0750AE)

• Block Configurator User's Guide (B0750AH)
• Bulk Data Editor User's Guide (B0750AF)
• Common Graphical Editor Features User's Guide (B0750AG)
• PLB Ladder Logic Editor (B0750AK)
• Sequence Block HLBL Editor User's Guide (B0750AL)
• Sequence Block SFC Editor User's Guide (B0750AM)
• Strategy Editor User's Guide (B0750AN)
• Implementing FOUNDATION™ fieldbus User’s Guide for InFusion v1.x
(B0750BC) or Implementing FOUNDATION fieldbus in Foxboro Evo
Core Services Applications (B0750DA)
• FOUNDATION™ fieldbus Control in the Field (CIF) Migration
(B0750CA)
• Field Device Manager and Foxboro Instrument Workshop for
FOUNDATION fieldbus Installation Guide (B0750CK)
• Implementing PROFIBUS™ Networks in Foxboro Evo Control Software
Applications (B0750BE)
• Field Device Manager and Foxboro Instrument Workshop for PROFIBUS
Networks Installation Guide (B0750CJ)
• Implementing a DeviceNet™ Network on the Foxboro Evo Core Services
(B0750CH)
• Foxboro Evo for DeviceNet Installation Guide (B0750CL)
• Using HART Instrumentation with the Foxboro Evo Process Automation
System (B0750CM).
• Field Device Manager for HART Devices Installation Guide (B0750CN)
For additional information about Wonderware Historian and Control Editors
Security, refer to Access Manager User's Guide (B0750AD).
For information on setting up and using FoxCTS, refer to FoxCTS Change
Tracking Software Configuration and Administration Guide (B0193VV).
In this guide the terms controller, control processor, and CP are used
interchangeably.

1
C H A P T E R 1
Deployment
This chapter describes how to deploy equipment units, controllers, compounds,

strategies, and blocks to the Control Processors.
Contents
• Introduction
• Deploying Control Objects
• Undeploying Control Objects
Introduction
Control logic is developed in the Control Editors with the creation of strategies
in the Strategy Editor. A strategy consists of interconnected control blocks and
I/O variables that enable connection of the strategy to other control elements.
A strategy can also include other strategies connected to blocks or other
embedded strategies via their I/O variables.
When a strategy is first created, it is displayed in the Deployment view either
under the Unassigned Host node or under the compound to which it is
assigned. The strategy must be assigned to a compound, the compound to a
control processor, and the control processor to an equipment unit, before the
blocks in the strategy can be deployed. The strategy can be assigned to a
compound using the strategy’s context menu or by a drag-and-drop move.
Similar methods are used to assign the compound to a control processor, and
the control processor to an equipment unit.
Note You cannot deploy an unassigned object. For a selected compound, if

the control processor is unassigned, you cannot select anything in the IDE tree
in the Select Objects for Deployment (Step 1 of 4) dialog box. If a control
processor or a compound is unassigned and if you select either of them, the
IDE tree in the Select Objects for Deployment (Step 1 of 4) dialog box shows
only the ALL node.
For information on the development of strategies, compounds, and control

processors (CPs), refer to the documents listed on page v.
After a control object is correctly assigned, it can be deployed using commands
selected from the context menu of the object in the Deployment view or other
application views. You can continue working in the Control Editors while the
deployment takes place in the background.

2 1. Deployment
Figure 1-1. Modeless Deployment Dialog Box
There are three targets updated in the deployment:

• Compounds and blocks are downloaded to the CP. On completion of the
download, the Compound Summary Access (CSA) and the checkpoint file
on the CP’s host workstation are updated.
• Security access settings for compound and block attributes are loaded into
InFusion™ Security.
• Compound, Block, and ECB parameters configured for History collection
are distributed and sent to InFusion Security.
When a deployed object is modified in the Control Editors, it must be
redeployed to implement the changes in the run-time system. When an object
is redeployed, only the modified parameters are downloaded for CP
deployment, Security, and History changes.
A yellow marker is used with an equipment unit, CP, compound, or strategy
icon to indicate that it is not yet deployed. A black and yellow marker is used
when the object must be redeployed, as illustrated by the three strategies in
Figure 1-2.

1. Deployment 3
This strategy is undeployed.
The strategy has been deployed.
The strategy is deployed, but its

configuration has been modified
since the deployment. The strategy
must be redeployed to implement
the changes in the run-time system.
Figure 1-2. Deployment Status in the Application Views
Blocks are not displayed in the Deployment view. However, when a strategy is
opened in the Strategy Editor, the deployed state of each block is identified by
a letter in the upper right corner of the block appearance object, as shown in
Figure 1-3.
This block is undeployed. The block

is not in the run-time system.
The block has been deployed. Its

configuration in the Galaxy has not
changed since the deployment.
The block is deployed,
but its configuration
has been modified
since the deployment.
The block must be
deployed again to
implement the changes
in the run-time system.
Figure 1-3. Identifying the Deployment Status of a Block
The deployment-related actions can be initiated from the context menu of the
following objects in the Deployment view:
• Equipment Unit
An equipment unit, which is a container object in the Control Editors and
is not actually downloaded to a CP, must be marked as deployed before
any contained object can be deployed. You can initiate an action only for
the selected equipment unit, if it does not contain any IA objects during
deployment. The equipment unit must be marked as deployed before any
of its CPs can be deployed.
• Controller
Deployment of a controller involves downloading the station’s ECB
compound and station compound to the CP. You can also select a cascade
deployment in which all compounds assigned to the controller and their

4 1. Deployment
blocks are downloaded to the CP. To initialize a control processor, reboot

it after undeploying it.
• Compound
Deployment of a compound can involve just a download of the compound
itself so that contained strategies and blocks can be selectively deployed at
a later time, or a cascade deployment in which the assigned strategies are
marked as deployed and all contained blocks are downloaded to the CP.
• Strategy
A strategy itself is not downloaded to the controller but it is marked
deployed to enable contained blocks to be deployed.
Do not use the following names for a compound:
• CON
• PRN
• AUX
• NUL
• COM1
• COM2
• COM3
• COM4
• COM5
• COM6
• COM7
• COM8
• COM9
• LPT1
• LPT2
• LPT3
• LPT4
• LPT5
• LPT6
• LPT7
• LPT8
• LPT9
Using any of the above names for a compound will result in deployment failure
of the sequence or PLB blocks under that compound. The deployment failure
occurs in Object Validation (Step 3 of 4) dialog box.
Figure 1-4 shows deployment-related commands that are available when the
context menu of an object is selected in the Deployment view (controller

1. Deployment 5
CPFP23 in Figure 1-4). The commands are described in Table 1-1 after the
figure.
Figure 1-4. Context Menu in the Deployment View

6 1. Deployment
Note If you select dissimilar objects (for example, a compound and a

strategy) in the Control Editors, and then select Deploy from the context menu
(Figure 1-4), the Select Objects for Deployment (Step 1 of 4) dialog box does
not appear. The selection of the identical objects in the Control Editors is
necessary for Select Objects for Deployment (Step 1 of 4) dialog box to
appear.
The Control Software Database Deployment provides a wizard-based

workflow. The new workflow is modeless, which means there is no need to
manually quit deployment to do other tasks on the Control Editors. In other
words, you can do other tasks when deployment is in progress. In addition,
significant changes are made to improve the time taken for deployment.
Figure 1-5 illustrates the new wizard-based workflow.

1. Deployment 7
Figure 1-5. The Control Software Control Database Deployment

Workflow

8 1. Deployment
Deploying Control Objects

Table 1-1. Deployment Actions
Menu Selection Description

Deploy For undeployed objects, it adds the objects to the CP
database, updates CSA, Security and History, and marks
the objects as deployed in the Galaxy. For deployed
objects, it updates the CP database and other affected
targets with attribute values that have been modified
since deployment. See “Deploying Control Objects” on
page 8.
Undeploy Removes the selected objects from the CP database,
updates the other targets, and marks the objects as
undeployed in the Galaxy, as described in “Undeploying
Control Objects” on page 35.
Upload Runtime Changes Extracts the values of all configurable and settable
parameters from the CP database and writes those values
to the Galaxy. See “Bulk Upload” on page 39.
Deploy Utilities > UndeployDeploy Resets the selected compounds or blocks by deleting the
objects from the CP and immediately reloading them, as
described in “Resetting Compounds and Blocks” on
page 40.
This option should not be used to reset a compound or a
block at the CP level. If this option is used at the CP
level, it puts the CP database in an unusable state, as the
station block is incorrectly undeployed.
Deploy Utilities > Selective Provides a tool for aligning the CP database with the
Upload/Deploy Galaxy by uploading and deploying selected parameters.
Refer to “Selective Upload/Deploy” on page 41.
Deploy Utilities > CheckPoint CP Saves a CP database to a file on the controller’s host
workstation, as described in “Checkpointing” on page 43.
Deploy Utilities > Synchronize DBs Aligns the CSA and the Galaxy with the CP database, as
described in “Synchronize DBs” on page 43. This utility
is only available from the context menu of a CP.
Deploy Utilities > Synchronize Deploy Allows you to change the deployed status of selected
Status... objects in the Galaxy and/or the CSA, as described in
“Synchronize Deploy Status (Changing a Deployed
State)” on page 44.
Deploy Utilities > Upload Compare Reads the parameter values in the control processor and
identifies those that differ from the parameters in the
Galaxy, as described in “Upload Compare” on page 45.
This section describes how controllers, compounds, and blocks are deployed,
and redeployed to the controllers. The instructions use an example in which the
Deploy action is selected from a controller (CPFP23) that has already been
deployed. The control compounds (C001, C002, C0021, C0022, C0023,
C0027, C003, and C007) assigned to the CP have not been deployed. The only
deployed compounds in the CP database are the ECB and station compounds
(CPFP23_ECB and CPFP23_STA in Figure 1-6).

1. Deployment 9
Figure 1-6. Controller Selected in the Example
Note The Station block and the sequence blocks (i.e. DEP, IND, EXC and
MON) have features which allow them to help manage the amount of memory
used in a control processor. Before deploying the Station block or any
sequence blocks, be sure to configure them to support these control processor
memory management features, as discussed in Chapter 4, “Control Processor
Memory Management”.

10 1. Deployment
Select Objects for Deployment

To deploy the control compound in the example (Figure 1-6):
1. Right-click the controller (CPFT23) and click Deploy to open the Select
Objects for Deployment (Step 1 of 4) dialog box (Figure 1-7).
Note Incorrect selection of objects in the Select Objects for

Deployment (Step 1 of 4) dialog box is not allowed and will notify you of
errors in the same screen. For example: If you select a strategy when a
compound is in undeployed status, you will see an error message in the
Select Objects for Deployment (Step 1 of 4).
Figure 1-7. Select Objects for Deployment (Step 1 of 4) Dialog Box
In this example, the command is selected from the CP to illustrate certain

features of the Select Objects for Deployment (Step 1 of 4) dialog box.
However, the command could have been selected from the compound
itself.
You need to deploy the equipment unit first, before deploying the
controllers. You cannot select more than one controller for deployment. In
other words, you need to deploy each controller individually. However,
you can select multiple compounds or strategies within the same controller
for deployment.The selection of multiple compounds or strategies from
different controllers does not open the Select Objects for Deployment
(Step 1 of 4) dialog box.
Note You cannot see either checked-out objects or objects with errors in
the Select Objects for Deployment (Step 1 of 4) dialog box.

1. Deployment 11
Click one of the following buttons in the Select Objects for Deployment
(Step 1 of 4) dialog box:
• Click Refresh to retrieve the hierarchy by clearing the list and starting
the process again. It updates the list in the IDE tree with the objects
added or removed in the Control Editors. It also updates the change in
the deployment status.
• Click Compile Blocks to compile the blocks that need compilation.
The Sequence and PLB blocks are compiled during object validation
(Figure 1-8). The Deploy wizard compiles the blocks and displays the
compilation results in the Object Validation (Step 3 of 4) dialog box
(Figure 1-9).
Note The blocks that are not compiled and those that need to be
recompiled can undergo Auto Compilation. Avoid using Compile Blocks
option in Step 1 of the deployment while deploying large CPs, as it might
lead to memory constraints.
• Click Finish to deploy the blocks directly by skipping Steps 2 and 3.

It takes you to the Deployment Progress (Step 4 of 4) dialog box
directly. At this point, no warnings are shown for skipping Steps 2 and
3. It will only show error messages caused out of Steps 2 and 3.
Note The Next or Finish buttons are enabled only when you make at
least one valid selection in the IDE tree in the Select Objects for
Deployment (Step 1 of 4) dialog box.
• Click Cancel to stop the deploy process.
Figure 1-8. Select Block for Compilation

12 1. Deployment
Note Do not modify the objects that are selected for deployment from the
same machine or from a different machine connected to the same Galaxy
database.
Figure 1-9. Compilation Results of Compilation Blocks
Note Cascade Selection, Compile Blocks and Checkpoint are toggle

buttons that can turn on or off the cascade selection, automatic block
compilation, and automatic checkpoint features, respectively during
deployment.
Note For each CP, a checkpoint file containing the CP’s control database is
maintained in its host workstation. When the CP is rebooted, the checkpoint
file is read to reload the control database. Checkpointing, that is uploading the
database from the CP, is usually performed after a deployment to the CP in
order to make sure that the checkpoint file and the Galaxy are aligned.
For information on system-level validations performed on the System

Validation (Step 2 of 4) dialog box, refer to “System Validations” on page 15.
Deploy Type Filter and Strategy Filter

In the Select Objects for Deployment (Step 1 of 4) dialog box, the view
of selected objects can be modified based on the deploy status of the
blocks. In the Deploy Type Filter area of the dialog box, select any of the
following options:
• Show Deployed Items - Clear the check box to hide the deployed
items and show the undeployed and modified items.

1. Deployment 13
• Show Undeployed Items - Clear the check box to hide the

undeployed items and show the deployed and modified items.
• Show Deployed Items Pending Changes - Clear the check box to
hide only the modified items and show the fully deployed and fully
undeployed objects.
All the above options are shown during deployment.
Note A selected object in the Select Objects for Deployment (Step 1 of

4) dialog box will be hidden from your view as a result of changing the
default selection of the filters. This object appears unselected upon
restoring the filters back to the default status. If a strategy is hidden as a
result of changing the default selection of the filter Show Strategies (that
is, unselecting the Show Strategies check box in Step 1 of deployment),
any selected blocks under that strategy appear unselected.
In the Strategy Filter area, clear the Show Strategies check box to hide
strategies (Figure 1-10).
Figure 1-10. Strategy Filter
2. The deploy status of each object in the tree is displayed on the left of the
object name as icons. An object cannot be deployed if its parent or host is
undeployed.
Perform one of the following actions to view the entire hierarchy:
• Click to the left of the controller name to expand the object and
display its assigned compounds and strategies, and then expand a
strategy to display its blocks.
• Click to the left of any object to collapse its display.
• Click Expand All to view the entire hierarchy.

14 1. Deployment
• Click Collapse All to collapse the entire hierarchy if it is already

expanded.
Note After you click Refresh, you can view the correct set of objects, if
all the options in Deploy Type Filter and Strategy Filter panes are
selected.
If any one option in either of the panes is deselected, click Expand All to
view the correct set of objects.
3. The following deployment target for each partially deployed object (a

compound, a block, and an ECB) is displayed in the Select Objects for
Deployment (Step 1 of 4) dialog box (Figure 1-11).
• (IA) - This target indicates that the CP must be updated with the
changes done to the object.
• (S) - This target indicates that the Security must be updated with the
changes done to the object.
• (H) - This target indicates that the Wonderware Historian Server must
be updated with the changes done to the object.
Note All the three targets (IA, S, and H) of any combination are possible for a
single object.
Figure 1-11. Deployment Target
4. Perform one of the following actions for selecting the objects for
deployment (Figure 1-12):
• Click Cascade Selection to clear the option and click on the check
boxes corresponding to all the objects that are to be deployed.

1. Deployment 15
• Click the check box next to the object for which the entire hierarchy
has to be deployed.
Figure 1-12. Cascade Selection
5. Click Next to open the System Validation (Step 2 of 4) dialog box.
System Validations
System-level validations are performed on the System Validation (Step 2 of 4)
dialog box. The Next > and Finish >> buttons are not active until system-level
validations are performed successfully, that is, until the deployment process
has verified the following:
• CSA is running on the network.
• IA Remoting, InFusion Sync, and InFusion Deploy services are running.
• Controller is reachable.
• Host Station is reachable.
When there are any validation errors, they are displayed next to the respective
controller in the System Validation (Step 2 of 4) dialog box. Deployment will
not proceed until these errors are resolved (Figure 1-13). After resolving the
errors, click Validate Again to revalidate the System Validations. In
Figure 1-14, CP is not reachable.

16 1. Deployment
Figure 1-13. CP not Assigned to Proper Host
Figure 1-14. Unreachable CP
In Figure 1-15, CPFT23 and AWSE23 are validated and their respective
validation status is displayed as Validation Successful.

1. Deployment 17
Figure 1-15. Successful System Validation
Click Next. The Object Validation (Step 3 of 4) dialog box appears.
Object Validations
Object-level validations are performed and the results are updated on the
Object Validation (Step 3 of 4) dialog box. The Finish >> button is not active
until all objects in the dialog box have been validated, that is, until the
deployment process has verified the following:
• Blocks are given unique names with their compounds, and compounds are
given unique names within the Galaxy.
• The parent or host for each object is already deployed or, in case of a
cascade selection, will be deployed with the object.
• Block types and parameters are valid for the target CP revision level.
• Compounds identify a workstation for History data collection.
The deployment process checks each object to determine if it can be deployed,
and displays the results in the Object Validation (Step 3 of 4) dialog box. If
the object fails the validation, the reasons are listed in the dialog box.

18 1. Deployment
Figure 1-16 shows a completed validation of the example compound, its

contained strategies, and their blocks.
Figure 1-16. Validation of all Objects Selected for Deployment
The Finish >> button is active when the validation of the objects is completed.
Click one of the following buttons in the Object Validation (Step 3 of 4)
dialog box to select the messages to display:
• Errors - This button is always selected by default (Figure 1-16). You can
cancel the selection to turn off the Errors button as shown in (Figure 1-17).

1. Deployment 19
Figure 1-17. Object Validation Dialog Box - Errors Button Turned Off
• Warnings - This button is selected by default (Figure 1-16). You can

cancel the selection to turn off the warning messages.
• Information - This button is not selected by default (Figure 1-16). You
can select it if you want to display the information messages in the dialog
box.
Note If you double-click a row in the Object Validation (Step 3 of 4), you
can see an appropriate editor for each row. For example, if the message is about
a strategy or a block, then it opens the Strategy Editor. Similarly, if the
message is about a compound or an Equipment Control Block (ECB), then it
opens the respective editor.
Figure 1-18 shows a block that cannot be deployed because a sequence code in
the block has failed compilation and should be fixed before it can be deployed
again. The errors for the block are listed in the Object Validation (Step 3 of 4)
dialog box.

20 1. Deployment
Figure 1-18. Unfiltered Screen
Type Filter
Specific types of message can be displayed using the Type filter located at the
top right corner of the Object Validation (Step 3 of 4) dialog box
(Figure 1-19). Selecting the type will display type-specific errors, if any.
The Type filter can categorize the messages into four types:
• Data
• History
• Connection
• Compilation

1. Deployment 21
Figure 1-19. Type Filter
Deployment Progress
To complete the deployment of successfully prepared objects:
1. Click Finish>> in the Object Validation (Step 3 of 4) dialog box to
download the objects that have successfully passed object validations to
the controller, and update CSA, Security, and History.
If change tracking is enabled, the deployment process displays the
Change Tracking dialog box (Figure 1-20). Deployment does not
proceed until you make an entry in the dialog box.

22 1. Deployment
Figure 1-20. Change Tracking Dialog Box
• Enter a reason in the dialog box and click OK.

For information on setting up and using change tracking, refer to
Chapter 3, “Change Tracking”.
The Deployment Progress (Step 4 of 4) dialog box lists the individual
transactions (Figure 1-24). Errors reported during the deployment
progress are displayed in the dialog view along with any configuration
errors that result from the deployment (Figure 1-23).
Click Cancel to cancel the deployment of successfully validated objects as
shown in Figure 1-21. Cancel button is enabled only when the actual
deployment or undeployment starts in Deployment Progress (Step 4 of 4)
dialog box.

1. Deployment 23
Figure 1-21. Cancel Deployment
Click Yes in the Confirm dialog box that appears, if you want to quit the
deployment process, else click No as shown in Figure 1-22.
Figure 1-22. Cancel Deployment - Confirm Dialog Box
Note If you clicked Cancel when a block is being deployed, it allows the
block to be deployed and its status updated before cancelling the deployment
process. The cancellation process ensures that the status of the deployed block
is updated in both Galaxy database and the CP database before aborting the
deployment progress.

24 1. Deployment
Figure 1-23. Errors in Deployment Progress
Note Errors such as E35 (maximum memory reached) and E43 (maximum
number of blocks reached) automatically cancel the deployment process.
2. Click Close when the Deployment Progress (Step 4 of 4) dialog box

indicates that the deployment is complete. All the messages displayed in
the Deployment Progress (Step 4 of 4) dialog box will be copied to the
Output view.
3. Review the messages in the Output view for any logs during the
download.
Note If the deployment or undeployment operation is cancelled (either

manually by an operator or triggered by CP errors such as E35 or E43), the
checkpoint operation is not performed. A corresponding message will appear
in the Output View and System Management Console (SMC) log to explain
this.
Note After undeploying or deploying multiple compounds from multiple

workstations, messages may appear in the SMC log which include the
following text: “The ‘configuration’ element is not declared.” These messages
are for informational purposes only; they have no bearings on whether or not
the desired undeploy/deploy operation was completed.

1. Deployment 25
Figure 1-24. Deployment Progress (Step 4 of 4)
Note During the deploying or undeploying of a controller, you can disable its
checkpoint. If a checkpoint is disabled during a deployment to a CP, the
Checkpoint Alert dialog box (Figure 1-25) appears upon exiting the Control
Editors that a reboot of the CP will result in loss of data as the CP has not been
checkpointed. You can checkpoint at that time. The Control Editors will close
after the checkpoints are performed.
Figure 1-25. Checkpoint Alert

26 1. Deployment
Redeploying Modified Compounds and Blocks

Changes made to a compound or block are not implemented until the object is
redeployed. The procedure for redeploying a modified control object is the
same as the original deployment, except that the Control Editors only deploy to
the targets affected by the change and only downloads the modified
parameters.
Note You can also redeploy blocks from the Strategy Editor as described in
“Strategy Editor Deployment of the Blocks” on page 31.
Figure 1-26 shows the Select Objects for Deployment (Step 1 of 4) dialog
box opened for a deployed compound that has two strategies that need to be
deployed or redeployed. The strategies and their blocks have been prepared for
deployment.
Figure 1-26. Main Window for Deploying Modified Blocks
In the example, strategy LEAD_001 contains the block AIN_003 whose

parameters have been modified and is thus marked (IA). Only the changed
parameters will be downloaded to the CP.
Objects that have errors cannot be redeployed.
When the objects are successfully redeployed, they will be marked
appropriately in the application views and on the block appearance objects (M
will be changed to D) within the strategy.

1. Deployment 27
Redeploying FOUNDATION Fieldbus Blocks

Note For additional information on implementing FOUNDATION™ fieldbus,
refer to Implementing FOUNDATION™ fieldbus User’s Guide for InFusion
v1.x (B0750BC) for InFusion v2.0 and earlier systems, or Implementing
FOUNDATION fieldbus in Foxboro Evo Core Services Applications
(B0750DA) for Foxboro Control Software (FCS) v3.0 to v4.x and Foxboro
Evo Control Software v5.0 or later.
When one of the eight FOUNDATION fieldbus-specific DCI blocks (AI, AO, DI,
DO, MAI, MAO, MDI, or MDO) is deployed, the parameter values in the
control block (the FF block) are downloaded to a function block of the same
type in the H1 device. Depending on the parameters involved in the download,
the device function block must be either out of service (OOS mode) or
operating in Manual mode. Among the parameters that are downloaded to the
device function block are those that specify the block’s permitted and target
modes (MODE_P and MODE_T).
For the initial deployment of an FF block, the current mode of the device
function block is typically not an issue, as that block is un-initialized and not in
service. However, if an FF block must be redeployed to implement
configuration changes, the FF block must be set to the appropriate mode,
which in turn sets the device function block mode so that the device parameters
can be modified.
The Object Validation (Step 3 of 4) dialog box checks for FF blocks and
verifies that the blocks are in the appropriate mode given the parameters to be
downloaded to the device function block. If the block modes are correct, the
deployment can go forward. If the deployment is being made from a client on a
Control Core Services workstation with either Foxboro Evo Control HMI or
FoxView™ software installed, the dialog box also includes a link to a Control
HMI faceplate or a FoxView detail display for each block that must be
changed.
Note The FOUNDATION fieldbus deployment software has been upgraded to

handle errors detected during Foundation fieldbus block deployment. If an
error is detected during the deployment and the integrity of the schedule in the
devices on the segment is broken, all FOUNDATION fieldbus blocks on the
segment will be marked for redeployment. The blocks must be redeployed on
the segment again. The FBM228 with IOM128 image version 6.0 or higher is
required.

28 1. Deployment
Figure 1-27. DCI Block Deployment Mode Preparation Dialog Box
In the example, the block AO_1 is currently in Auto mode and must be
changed to OOS before the deployment can continue.
If the plant is not running, you can turn off the containing compound
(CPDW_AIAO in the example) using the Control HMI or FoxView software,
which in turn will take the blocks out of service.
If the plant is running, do the following to deploy one block at a time, as
suggested in the dialog box:
1. Click Cancel in the DCI Block Deployment Mode Preparation dialog
box (Figure 1-27) to return to the Object Validation (Step 3 of 4) dialog
box.
2. Click Back button in the Object Validation (Step 3 of 4) dialog box. The
System Validation (Step 2 of 4) dialog box appears.
3. Click Back button in the System Validation (Screen 2 of 4) dialog box.
The Select Objects for Deployment (Step 1 of 4) appears.
4. Unselect every object in the Select Objects for Deployment (Step 1 of 4)
dialog box. Select only one FF block.
5. Click Next button. The System Validation (Step 2 of 4) dialog box
appears.
6. Click Next button. The Object Validation (Step 3 of 4) dialog box
appears. The background process in the Object Validation (Step 3 of 4)

1. Deployment 29
dialog box results in the DCI Block Deployment Mode Preparation

dialog box (Figure 1-27) if the required conditions are met.
7. Click the link in the DCI Block Deployment Mode Preparation dialog
box to display the block in the Control HMI (Figure 1-28) or FoxView
software.
If the block path is not displayed as a hyperlink, you must turn off the
block using the Control HMI or FoxView software on another
workstation.
Current mode
Mode switches
Figure 1-28. Changing the Block Mode
8. Click OOS_SW in the display to change the block mode.

The MODE_T parameter is changed to OOS, which in turn changes the
device function block MODE.Target parameter and then MODE.Actual to
OOS.
9. Return to the Control Editors when the mode change is reflected in the
faceplate.
10. Click Continue when the DCI Block Deployment Mode Preparation
dialog box indicates that the mode is correct (Figure 1-29).

30 1. Deployment
Figure 1-29. Block Mode is Correct
11. You will now return to the Object Validation dialog box (Screen 3 of 4).
Click Finish button to continue with the FF block deployment.
When the deployment is finished, the Control Editors present a reminder
to restore the block mode (Figure 1-30).
Figure 1-30. Reminder to Restore the Block Mode
12. Switch to the Control HMI faceplate or FoxView detail display, and click
appropriate mode switch.
13. Deploy any additional blocks, as needed.
Note After the validation phase of the FF blocks’ deployment, the Object
Validation (Step 3 of 4) dialog box may show the FF blocks as not assigned to

1. Deployment 31
any device. This is incorrect - the FF blocks are assigned to their appropriate
devices.
If you click Cancel in the DCI Block Deployment Mode Preparation dialog
box (Figure 1-29), the Control Editors present a warning dialog box
(Figure 1-31) indicating that the block mode should be returned to its original
mode.
Figure 1-31. Warning Dialog Box
Strategy Editor Deployment of the Blocks

The Strategy Editor enables you to deploy, undeploy, and redeploy blocks
without closing the editor and checking in the strategy. You can then observe
the changes in the system using the Live Data Mode, as described in Strategy
Editor User's Guide (B0750AN), make further adjustments if needed, and then
redeploy the blocks.
Perform Strategy Editor Deployment from the context menu of one or more
selected blocks or from the View menu in the Strategy Editor. Strategies can
use the Strategy Editor Deploy feature only if you open this from the IDE tree.
The Strategy Editor Deployment takes place only when a strategy is already
deployed.
To deploy blocks from the Strategy Editor:
1. Expand the Galaxy node in the Deployment view to display the equipment
unit, host control processor and its compound and strategy, and then
double-click the strategy to open it in the Strategy Editor.
The Deploy function prompts you to save the changes and alerts you to
any errors and warnings resulting from the Save action (Figure 1-32).
However, you can validate and save changes (Figure 1-33) before
initiating deployment as follows:
• Click Galaxy > Save from the IDE main menu to validate and save
the block modifications.

32 1. Deployment
If the validation results in errors or warnings, the editor displays the Save
Confirmation dialog box (Figure 1-32), which enables you to cancel the
save so you can repair the errors.
Figure 1-32. Save Confirmation Dialog Box
2. Do one of the following:

• Click View > Deployment > Deploy from Strategy tab toolbar.
• Right-click an individual block in the strategy diagram and click
Deploy on the context menu.
Deploy options are available on the context of a block or the View
menu if its deploy status is M or U. The functions are available for
one or more selected blocks.
The Strategy Editor displays a confirmation dialog box (Figure 1-33, left
side). If changes made to the block have not been saved, the dialog box
also prompts you to save these changes to the block (Figure 1-33, right
side).
Figure 1-33. Prompt to Save and Deploy Changes
Note If you open a child Strategy Editor from its parent strategy, both the
context menu and the View menu will be disabled for the child strategy. But,
you can select options from the View menu of the parent strategy. This action
closes all the child and block editors except the parent Strategy Editor. Then
the Strategy Editor Deployment starts.
3. Click OK in the dialog box (or Cancel to not deploy the blocks).
If a save is required, the Strategy Editor validates all blocks in the strategy.
If there are errors or warning conditions associated with any of the blocks,
a confirmation dialog box lists the errors and warnings, and prompts you
to save the strategy anyway (Figure 1-32).

1. Deployment 33
• Click Yes to save the strategy with the warnings and errors and
proceed with deployment of blocks that can be deployed.
• Click No to cancel the save and the redeployment.
• If one or more FOUNDATION fieldbus-specific DCI blocks (AI, AO,
DI, DO, MAI, and MAO) are selected, the Control Editors display the
DCI Block Deployment Mode Preparation dialog box
(Figure 1-29).
• If FF blocks (Figure 1-31) are selected for deployment, the Warning
dialog box offers two buttons: Resume Preparation and Cancel
Preparation and abort deployment of block modifications.
• If non-FF blocks are included in the selection, the Warning dialog
box (Figure 1-31) offers two buttons: Resume Preparation and
Cancel Preparation and proceed with deployment of other block
modifications.
In either case, click Resume Preparation if the blocks are in the correct
mode; otherwise, click Cancel Preparation... button.
If change tracking is enabled, the Control Editors display the Change
Tracking dialog box (Figure 1-20 on page 22. For information on setting
up and using change tracking), refer to Chapter 3, “Change Tracking”.
Deployment does not proceed until you make an entry in the dialog box.
If the deployment continues, the deployment process checks for errors and
warnings in the blocks to be deployed. If none are found, the Deploy
dialog box (Figure 1-34) and the Output view display status messages as
the deployment proceeds.
Figure 1-34. Deployment Complete
Note After undeploying or deploying multiple compounds from multiple

workstations, messages may appear in the SMC log which include the
following text: “The ‘configuration’ element is not declared.” These messages
are for informational purposes only; they have no bearings on whether or not
the desired undeploy/deploy operation was completed.

34 1. Deployment
4. Review the messages in the Deploy dialog box and the Output view for
any errors or warnings from the deployment itself, and then click Close in
the Deploy dialog box.
The deploy status of modified blocks that were successfully redeployed
changes from M to D. Deploy status of the undeployed blocks that were
successfully deployed changes from U to D. However, the blocks that have
warnings even after being successfully deployed will remain in M.
Error Handling
You cannot deploy a block that has validation errors, while you can deploy a
block that has warning messages. In the following description of how the
Control Editors handle blocks with errors and warning conditions, the term
target blocks refers to:
• All blocks in the strategy with the deploy status M or U when Deploy is
invoked from the View menu on the Strategy tab toolbar.
• The selected block (the target blocks) when the deployment/ redeployment
is initiated from a block’s context menu.
When the target blocks have no errors or warning messages, the Control
Editors display the Deploy dialog box (Figure 1-34) and proceeds as described
above.
When there are errors and/or warnings associated with the target blocks, with
the condition that at least one block is error-free, the Block Errors Warnings
dialog box displays the error and warning messages. It gives you the option of
deploying the target blocks that have no errors. In Figure 1-35, the block
DEP_1 has a warning but can still be deployed, as it has no errors. The block
AOUT_1 has a validation error and cannot be deployed.
Figure 1-35. Block Errors Warnings Dialog Box
• Click OK in the dialog box to proceed (or Cancel to not deploy the
blocks).
The Deploy dialog box and the Output view list the deployment actions
and any errors and warnings.

1. Deployment 35
The deploy status of blocks that had no warnings changes from M to D.

The deploy status of blocks that had warning messages at the time of
deployment/ redeployment remains M.
When all the target blocks have errors, the Control Editors stop the deployment
as shown in the Deploy dialog box in Figure 1-36.
Figure 1-36. Deployment Stopped
Note When block modifications have been deployed from the Strategy Editor,
the Undo Check-Out and Override Check-Out commands cannot be performed
for the strategy.
Note When Strategy Editor Deployment is performed with a strategy that has
errors in one or more of its blocks, the Save Confirmation dialog box
(Figure 1-32) is shown twice, that is before and after the deployment. You must
click Yes in the dialog box each time to successfully deploy the modified
blocks.
Undeploying Control Objects

The Undeploy command opens a dialog box similar to that opened by the
Deploy command. The Select Objects for UnDeployment (Step 1 of 4) dialog
box (Figure 1-37) is used to specify objects to be removed from the controller,
validate that the actions can be taken, and then initiate the undeployment.

36 1. Deployment
Figure 1-37. Undeploying a Strategy
As with Deploy, you can select individual objects contained or hosted by any
object in the dialog box.
All objects under the object selected for undeployment are also removed from
the CP. For example, if you undeploy a compound, the contained strategies are
marked as undeployed in the Galaxy and their blocks are removed from the CP,
and marked as undeployed within their respective strategies. Thus, when you
select the compound in the dialog box and click Next, a Cascade Add is
performed, that is, add the compound and all the strategies and blocks it
contains for undeployment. Clear the compound check boxes in the dialog box
that are not targeted for undeployment.
Note The checked-out objects in the Select Objects for Undeployment

(Step 1 of 4) dialog box will be hidden.
The undeployment action also removes compounds and blocks from the CSA,
and updates ArchestrA Security and History as appropriate.
Note You cannot unselect Cascade Selection during undeployment.
Note Show Undeployed Items check box is hidden during undeployment.

You can see only Show Deployed Items and Show Deployed Items Pending
Changes check boxes under Deploy Type Filter.
Undeploying a Controller
Undeploying and subsequent rebooting of a control processor initializes the
control processor. This removes all compounds including the ECB and station

1. Deployment 37
compounds, and rewrites the initial checkpoint file over the current checkpoint
file in the host workstation.
To initialize a CP:
1. Right-click the controller in the Deployment view and click Undeploy on
the context menu.
2. Select the CP in the Select Objects for Undeployment (Step 1 of 4)
dialog box and click Next button. The System Validation (Step 2 of 4)
appears.
3. Click Next button in the System Validation (Step 2 of 4) dialog box. The
Object Validation (Step 3 of 4) dialog box appears.
4. Click Finish in the Object Validation (Step 3 of 4) dialog box.
If change tracking is enabled, the Control Editors display the Change
Tracking dialog box (Figure 1-20 on page 22). For information on setting
up and using change tracking, refer to Chapter 3, “Change Tracking”.
Undeployment does not proceed until you have made an entry in the
dialog box.
Note Cancel button is disabled when you undeploy CPs.
The Control Editors display a dialog box that lists the transactions
(Figure 1-38).
Figure 1-38. Undeploying a Controller
5. Click Close when the dialog box indicates that the station has been
undeployed, and then reboot the CP.

38 1. Deployment

39
C H A P T E R 2
Deployment Utilities
This chapter describes deployment-related utilities available in the Control

Editors to manage the alignment of the Galaxy with the deployed control
database.
Contents
• Bulk Upload
• Resetting Compounds and Blocks
• Selective Upload/Deploy
• Checkpointing
• Synchronize DBs
• Synchronize Deploy Status (Changing a Deployed State)
• Upload Compare
Bulk Upload
The Upload Runtime Changes command extracts the values of all settable
parameters from a CP database and writes those values to the Galaxy. The
command overwrites changes made in the Control Editors that have not been
deployed to the CP. The affected objects are marked as deployed. Bulk Upload
can be initiated from the context menu of a control processor, compound or
strategy to update all objects contained in the selected item.
Upload Runtime Changes is a blind upload of all parameter values in the CP.
• Before performing a bulk upload, you may want to compare the two
databases by using the Upload Compare utility described in “Upload
Compare” on page 45.
• Use the Selective Upload/Deploy command in the Deployment Utilities
(described on page 41) to view parameter values in both the CP and the
Galaxy and then decide which should be uploaded and which should be
deployed.
To perform a bulk upload:
1. Right-click the controller (or any compound or strategy under it) and click
Upload Runtime Changes on the context menu.
The Upload dialog box prompts you to confirm the action (Figure 2-1).

40 2. Deployment Utilities
Figure 2-1. Confirming a Bulk Upload Action
2. Click OK to proceed with the upload. The Upload Runtime dialog box
lists the transactions (Figure 2-2).
Note Click Cancel to stop uploading.
Figure 2-2. Upload Runtime Changes Dialog Box
3. Click Close when the dialog box shows that the upload is complete.
Note Use Selective Upload/Deploy to write only selected values from

the controller).
Resetting Compounds and Blocks

Use the Undeploy Deploy command to reset a compound or block that is not
performing correctly. (This command is similar to performing a
Delete/Undelete using earlier control configurators.)
To reset a compound:
1. Right-click the compound in the Deployment view and click Deploy
Utilities > Undeploy Deploy on the context menu. The Control Editors
open the Undeploy Deploy dialog box.
2. Select the compound, click Add to move it and all its contained objects to
the Objects to be processed pane, and then click Prepare All.
3. Click Undeploy Deploy.

2. Deployment Utilities 41
The action deletes the selected compound and all of its assigned blocks
from the CP and immediately reloads them from the Galaxy. Only
deployed parameter values are loaded into the CP. The object is not
changed in the Galaxy.
Selective Upload/Deploy
Changes made to a deployed compound or block result in differences between
the CP database and the Galaxy. For example, when a compound COMP1 in
the Galaxy is deployed to the CP and if you make changes such as:
• Modifying COMP1 in the Galaxy by changing the DESCRP parameter of
COMP1
• Modifying COMP1 in the CP by changing the DESCRP parameter of
COMP1 using the Integrated Control Configurator (ICC) or OMSET
(Object Manager SET) commands
Note ICC and OMSET are different applications that can also modify the
CP.
In both the above cases, you have an option to save the changes made in the
Galaxy or in the CP using the Selective Upload/Deploy dialog box.
To save the changes made in the Galaxy:
1. Right-click a CP in the Control Editors. Select Deploy Utilities option and
Selective Upload/Deploy option from the context menu. The Selective
Upload/Deploy dialog box appears as shown in Figure 2-3.
2. Select COMP1 in the tree structure in the Selective Upload/Deploy dialog
box and select the DESCRP parameter.
3. Click Update CP button and then click Perform Updates and Close
button. The changes that are made in the Galaxy will be deployed to the
CP and the compound goes into a fully deployed state.
To save the changes made in the CP:
1. Repeat steps 1 and 2.
2. Click Update Galaxy button and then click Perform Updates and Close
button to execute the updates made. The changes that are made in the CP
will be overwritten to the Galaxy and the compound goes into a fully
deployed state.
The Selective Upload/Deploy dialog box enables you to compare values in the
two databases for selected compounds and blocks, and then align the databases
by uploading and/or downloading individual parameters.
Note The Selective Upload/Download dialog box does not support selective
upload of port settings (which are encapsulated in the FDATA1 through
FDATA4 parameters) from a PROFIBUS device or its host FBM222. Selective
downloads of the FDATA1 through FDATA4 parameters are supported.

Note Use Field Device Manager rather than the Selective Upload/Download
dialog box to upload individual parameters from a FOUNDATION fieldbus H1
device attached to an FBM228.
To compare and align the two databases:

1. Right-click the affected compound or strategy in the Deployment view
and click Deploy Utilities > Selective Upload/Deploy on the context
menu to display the Selective Upload/Deploy dialog box (Figure 2-3)
The object is displayed in a navigation pane on the left side of the dialog
box.
2. Click in the navigation pane to expand the object as necessary to
display the contained compounds, strategies and blocks.
3. Click a compound or block in the navigation pane to compare values in the
Galaxy and the CP.
A table to the right of the navigation pane highlights those parameters
where the Galaxy and the CP differ. The right column shows the action to
be taken when you click Perform Updates. The default action is None.
4. Select a parameter to be aligned and click one of the buttons in the
Selected Parameter Operations group:
• Update CP to deploy the change from the Galaxy (LOCSW in
Figure 2-3)
• Update Galaxy to upload the value from the controller (LR in
Figure 2-3)
• Remove Action to set the Action on Update to None.
Figure 2-3. Aligning Databases for a PID Block
5. Click Perform Updates to implement the specified uploads and

deployments.

If change tracking is enabled and the updates include an Update CP action,

the Change Tracking dialog box is displayed. (Figure 2-4). The download
does not proceed until you make an entry in the dialog box.

For information on setting up and using change tracking, refer to
Chapter 3, “Change Tracking”.
Note Uploads to the Galaxy are not tracked by FoxCTS. Only downloads
to the control processor are tracked.
6. Make updates to other blocks and compounds as necessary, and then click
Close to exit the utility.
Checkpointing
Checkpointing saves a CP database to a file on the controller’s host
workstation. The checkpoint file is the database saved in a form that is loaded
from the host to the control processor when that station is rebooted.
The CP is automatically checkpointed after each deployment and
undeployment (if the checkpointing was not disabled in the Deploy or
Undeploy dialog box).
Checkpointing is also available on demand in addition to the automatic
checkpointing. Checkpoint CP can be invoked from the CP itself or from any
of its compounds or their strategies.
To checkpoint a CP:
• Right-click the CP (or one of the objects hosted by the CP) in the
Deployment view and click Deployment Utilities > Checkpoint CP.
While the controller is being checkpointed, you can perform other tasks in
the Control Editors except deployment actions that involve the CP.
Synchronize DBs
The Synchronize DBs utility, which is only available from the context menu of
a CP, reads the CP control database to identify the compounds and blocks in

the CP and then updates the deployed status of compounds and blocks in the
Galaxy. Compounds and blocks that are actually in the CP are marked as
deployed in the Galaxy; and compounds and blocks that were marked as
deployed to the CP but were not present in the CP database are marked as
undeployed.
The utility also updates the CSA, and can be used to recover the CSA if its host
workstation has been out of service.
The utility only deals with the deployed status of the compounds and blocks.
Use Selective Upload/Deploy to align parameter values in the two databases.
To synchronize the Galaxy and the CSA with a CP database:
1. Right-click the CP and click Deploy Utilities > Synchronize DBs on the
context menu.
2. Click OK in the dialog box that states the synchronization is completed.
Synchronize Deploy Status (Changing a

Deployed State)
The Set Deploy Status utility enables you to change the deploy status of
selected objects in the Galaxy database only. This utility does not perform any
actual deploy/undeploy operations on the CP. Use the utility with caution and
only when consulting with an Invensys service representative, as it may result
in the Galaxy being out of alignment with the CP database.
To access the utility:
1. Right-click on an equipment unit, CP, compound, or strategy and click
Deploy Utilities > Synchronize Deploy Status on the context menu.
A dialog box lists the selected objects and their contained objects
(Figure 2-5).
2. Select the objects whose status you want to change by checking the boxes
next to the desired items.
If you want to make multiple selections, you can use the Include
Children on Selection option in the Selection Options group. For
example, if you select Include Children on Selection and click on the
root node {ALL}, all items on the tree will become selected, as shown in
Figure 2-5.
3. Click either Set to Deployed or Set to Undeployed in the Status to Set
group.
4. Click OK. The selected items are set with the deployed or undeployed
status in the Galaxy database.

Figure 2-5. Set Deploy Status Utility
The navigation tree on the left side of the dialog box shows only objects for
which you are able to set the deployment status. For example, the tree view
does not display objects that currently have errors, or that are unassigned.
Additionally, the navigation tree will not display compounds, blocks, or
strategies if the host CP is checked out.
After using this utility, deploy statuses change according to expected Control
Editors operations. For example, if all blocks within a strategy are deployed,
the strategy is set to the deployed state. On the other hand, if at least one block
within the strategy is undeployed, the strategy is marked as needing to be
deployed. Additionally, a strategy cannot be marked deployed if the compound
is not selected and is still in an undeployed state.
Note Use Synchronize DBs for synchronization of the deployment states

between the CP and the Galaxy database.
Upload Compare
The Upload Compare utility identifies parameter values in the control
processor that differ from the values in the Galaxy without changing values in
either database.
Use this function to preview the results of using the Upload Runtime
Changes command (as described in “Bulk Upload” on page 39) or determine
whether a bulk upload is necessary.

To perform an Upload Compare:

1. Right-click the control processor or one of its compounds or strategies in
the Deployment view, and click Deploy Utilities > Upload Compare on
the context menu.
For each compound and block in the selection, the CP is queried for the
run-time values and lists the differences in the Output view.
The Upload Runtime Changes dialog box displays each step in the
process (Figure 2-6).
Figure 2-6. Dialog Box Displays Queries of the CP Database
2. Click Close in the Upload Runtime Changes dialog box when the dialog
box displays Operation Complete, and review the results in the Output
View (Figure 2-6).
Figure 2-7. Results of the Upload Compare

47
C H A P T E R 3
Change Tracking
The Control Editors provide a link to FoxCTS Change Tracking software

(FoxCTS) so you can automatically record control configuration changes for
OSHA 1910 and 21 CFR Part 11 compliance. This chapter deals with setting
up and using the Control software interface to a FoxCTS application.
Contents
• Overview
• FoxCTS Directory for Event Files
• Authorize User Access
• Specify the FoxCTS Server
• Start the FoxCTS Transfer Service
• Enable Change Tracking
• Start the FoxCTS Transfer Monitor
• Monitoring Transfers
Overview
When change tracking is enabled, the Control Editors display the Change
Tracking dialog box each time you initiated a Deploy or Undeploy action.
Deployment or undeployment does not proceed until you make an entry in the
dialog box.

48 3. Change Tracking
When the deployment is complete, the FoxCTS Transfer Service on the Galaxy
server, creates a deployment event file with the following information:
• Affected control processor and compounds
• New parameter values
• Originating workstation
• Time and type of deployment
• Reason for the deployment as given by you in the Change Tracking
dialog box (Figure 3-1).
The service sends the deployment event file to the FoxCTS server monitoring
the affected control processors, as configured in the I/Series Monitor host
workstation. The transfer service maintains the file until it verifies that the
transfer to the FoxCTS sever was successful.
The FoxCTS Transfer Monitor service, which operates on the Galaxy server
and client workstations, alerts you when a transfer to the FoxCTS server has
not been successful within a user-specified period.
For additional information on configuring and using FoxCTS, refer to FoxCTS
Change Tracking Software Configuration and Administration Guide
(B0193VV).
Tracking Deployment Events

Table 3-1 describes the deployment events that are tracked by FoxCTS, and
those that are not tracked.
Table 3-1. Deployment Action Tracked for FoxCTS
User Initiated Change

Action CP Control Database Actions Tracked
Deploy/Cascade Add Yes
Deploy
• Add a control block
• Add a compound to the controller
• Add an ECB to the controller
Deploy/Cascade Modify Yes
Deploy
• Modify the STA block in a control processor
• Modify Primary ECB in a control processor
• Modify a control block in a control processor
• Modify _STA compound parameters
• Modify _ECB compound parameters
• Modify parameters for a compound

3. Change Tracking 49
Table 3-1. Deployment Action Tracked for FoxCTS (Continued)
User Initiated Change

Action CP Control Database Actions Tracked
Deploy/Cascade Move No
Deploy
• Move ECBs to change the ECB execution order
• Move a control block to change the block execution order
• Move a compound to change the compound execution order
Re-install • Delete/Undelete a compound, preserving current compound No
execution order in the control processor
• Delete/Undelete a block, preserving current control block
execution order in the control processor
Undeploy • Delete a block from controller Yes
• Delete an ECB from controller
• Delete a compound from controller
Upload • Upload settable and configurable parameters from the CP No
• Copy selected block and compound parameters from the
control processor to the Galaxy
Tracking Field Device Manager Downloads

The Control software link to FoxCTS also creates event files for downloads to
FBMs and field devices initiated from Field Device Manager for FOUNDATION
fieldbus and Field Device Manager for PROFIBUS. Field Device Manager
uses the audit trail option specified in the Field Device Technology (FDT)
standard to capture the events for change tracking.
The following Field Device Manager session events are tracked and sent to the
FoxCTS server:
• Download of FBM or device configuration parameters from the FBM
instance, such as changes to an H1 segment schedule or PROFIBUS port
settings
• Changes to the field instruments from the communication components,
such as a device address change or device tag change.
• Download of device and device block configurations delivered by Field
Device Manager from the device instance
• Download of device and device block configurations delivered by a
Commissioning wizard from the device instance
• Changes in the function blocks delivered by the Field Device Manager
pass-through connection to the field instruments
• Changes in the device initiated as a result of method execution in the
device block
• Events reported by the third-party device type manager (DTM) or block
type manager (BTM) that is associated with a device if the DTM/BTM
supports the audit trail option in the FDT standard

• Changes made to HART devices through their associated vendor DTMs

and the Universal DTM.
For additional information on the content of these event files, refer to the
appropriate document:
• Implementing FOUNDATION fieldbus User’s Guide for InFusion v1.x
(B0750BC) for InFusion 2.0 and earlier systems
• Implementing FOUNDATION fieldbus in Foxboro Evo Core Services
Applications (B0750DA) for Foxboro Control Software 3.0 to 4.x and
Foxboro Evo Control Software v5.0 or later systems
• Implementing PROFIBUS Networks in Foxboro Evo Control Software
Applications (B0750BE)
• Implementing a DeviceNet Network on the Foxboro Evo Core Services
(B0750CH)
• Using HART Instrumentation with the Foxboro Evo Process Automation
System (B0750CM).
The components of the change tracking link to FoxCTS are standard features
of the Control software and Field Device Manager software. The following
sections describe the steps required to enable the link to FoxCTS.
Setup at the FoxCTS Server

The FoxCTS Server software accommodates the receipt and processing of
change tracking data without any user intervention. The change tracking data is
transferred by the FoxCTS Transfer Service to a pre-defined location on the
FoxCTS server’s hard drive. From there the data is automatically processed by
FoxCTS and inserted into the FoxCTS database.
If you want to view the change tracking data after it has been inserted into the
FoxCTS database, your FoxCTS access must first be authorized by the
addition of a FoxCTS user account as described in FoxCTS Change Tracking
Software Configuration and Administration Guide (B0193VV).
FoxCTS Directory for Event Files

During installation of the FoxCTS application the following directory is
created on the FoxCTS server to receive the deployment event files from
change tracking:
D:\opt\foxind\cms\srvr\data\iee
The data sent by change tracking contains a folder for each control processor.
Within the control processor folder, a separate folder is created for each
transfer from the Control Editors concerning that control processor
(Figure 3-2).

Figure 3-2. FoxCTS Directory for a Control Processor
Authorize User Access

The use of login accounts is vital to the secure and traceable operation of both
the Control Editors and FoxCTS.
When the FoxCTS link is enabled, FoxCTS accepts the information from any
deployment and associates that information with the Control Editors user
name. If the user name is to be allowed login access to the FoxCTS system, set
up a login account in FoxCTS with the same user name before that user
performs any deployment operations.
The login accounts are separately managed by the Control Editors and
FoxCTS, and each application has its own rules for defining login accounts.
For example, FoxCTS supports periodic password expiration and has a 12-
character limit for the user name. For information on setting up user accounts,
refer to FoxCTS Change Tracking Software Configuration and Administration
Guide (B0193VV).
If the Control Editors user name is not defined in FoxCTS at the time of
deployment, FoxCTS accepts the deployment information but does not allow
you to access the information.

Foxboro Evo Control Software Setup

Four steps are required in the Control Editors to take advantage of the change
tracking link to FoxCTS:
1. Specify the FoxCTS server to receive and maintain the deployment event
files
2. Start the FoxCTS Transfer Service on the Galaxy server
3. Enable change tracking on the Galaxy server or client workstations
4. Start the FoxCTS Transfer Monitor Service on the Galaxy server and
client workstations.
You can perform these actions only if you have administrator privileges.
Specify the FoxCTS Server

The FoxCTS server must be identified in the configuration of the host
workstation for the affected control processors.
To specify the FoxCTS server:
1. Double-click the host workstation in the Derivation view to open the
workstation in the Control Editors Hardware Editor.
The editor opens to the Hardware tab (Figure 3-3).
2. Use the pull-down list in FoxCTS Server field to select the letterbug of
the server.
3. Make other configuration changes as needed, and then click in the

editor title bar to save the changes, close the editor and check the
workstation into the Galaxy repository.
Figure 3-3. Setting the FoxCTS Server Attribute

Start the FoxCTS Transfer Service

The FoxCTS Transfer Service Utility is responsible for the transfer of the
deployment event files to the FoxCTS application. You must start this service
on the Galaxy server before any deployment operation is performed.
To start the utility:
1. Click Start > Programs > Invensys > InFusion Change Tracking >
FoxCTS Transfer Utility to open the FoxCTS Transfer Service dialog
box (Figure 3-4).
Figure 3-4. FoxCTS Transfer Service Dialog Box
2. Enter the following information in the fields provided:

• Galaxy node
• Galaxy name
• User name
• Password
3. Click Start.
The utility Status changes to Started and the Stop button becomes active.
4. Click to close the FoxCTS Transfer Service dialog box.
Enable Change Tracking

The next step is to enable change tracking.
If the configuration is deployed when change tracking is turned on, it creates a
database for each control processor with the current compound, block and field
device parameters, and sends this baseline information to the FoxCTS server.
To enable change tracking on the Galaxy server or a client workstation:
1. Click Galaxy > Configure > Change Tracking on the IDE main menu to
open the Change Tracking dialog box (Figure 3-5).
Change Tracking is shown only if you have administrator privileges.

Figure 3-5. Enabling Change Tracking in the Control Editors
2. Click Enable Change Tracking in the dialog box to toggle the check box
on or off.
Note Once you have enabled change tracking for a Galaxy, it is strongly
recommended that you not disable change tracking.
3. Click OK to set the option and close the dialog box (or click Cancel to
close the dialog box without changing the option).
If the configuration is deployed, the Control software displays the Base
Line FoxCTS Database dialog box (Figure 3-6) as it creates a baseline
XML file for each deployed control processor in the Galaxy.
Figure 3-6. Baseline Created

4. Click Close when the dialog box indicates that the baseline has been
created and sent to the FoxCTS server.
When change tracking is enabled, <username> Change Tracking is displayed
at the bottom of the IDE window to the left of the Galaxy name and
workstation (Figure 3-7).
Figure 3-7. Change Tracking is Enabled on the Workstation
When FoxCTS tracking is enabled, the Control Editors display the Change
Tracking dialog box (Figure 3-1 on page 47) each time one or more objects
are deployed or undeployed.
Start the FoxCTS Transfer Monitor

FoxCTS Transfer Monitor Service is responsible for notifying you of any
deployment event file that was not successfully transferred to the FoxCTS
server within the time specified by you.
You need to start this service on the Galaxy server and the client workstations
before any deployment operation.
To start the monitor service:
1. Click Start > Programs > Invensys > Change Tracking > FoxCTS
Transfer Monitor Utility to open the FoxCTS Transfer Monitor dialog
box (Figure 3-8).
Figure 3-8. FoxCTS Transfer Monitor Dialog Box
2. Click Login in the dialog box to open the Fox Transfer Monitor Log In
dialog box (Figure 3-9).
3. Enter the Galaxy Node, Galaxy Name, User Name and Password in the
fields provided, and then click OK.

Figure 3-9. Login Dialog Box for the Monitor Service
4. Specify a warning period for verification of the file transfer to FoxCTS.

The warning period can be set from 10 to 120 minutes. The default is 30
minutes. If transfer of a deployment event file is not successful within the
period, the transfer is considered failed.
5. Click Minimize To Tray to keep the service running and to hide the
dialog box.
An icon for the monitor appears in the tool tray (Figure 3-10).
Figure 3-10. Monitor Tool Tray Icon
• Click to restore the CTS Transfer Monitor dialog box.
Monitoring Transfers
When there is a failed transfer to the FoxCTS application, FoxCTS Transfer
Monitor dialog box pops up automatically to display the information related to
the failed transfers (Figure 3-11). The dialog box is displayed on both the
server and the client workstations.

Figure 3-11. Dialog Box Shows Failed Transfers
To retry a failed transfer:

1. Click the FoxCTS Server cell in the dialog box to enable the Update
button (Figure 3-12, left), and then click Update to open a FoxCTS
Transfer Monitor dialog box for the controller (Figure 3-12, right).
Figure 3-12. Updating FoxCTS Server Information
2. Enter the FoxCTS server name in the new dialog box and click OK to
retry the file transfer to that server.


59
C H A P T E R 4
Control Processor Memory

Management
This chapter deals with the features provided by the Control Editors in FCS
v3.1 to v4.x and Foxboro Evo Control Software v5.0 or later, which help users
manage memory usage in control processors, to prevent insufficient memory
from being available during normal operations.
Contents
• Memory Preservation Bit Configuration
• Use of Sequence Block CSPACE Parameter
Memory Preservation Bit Configuration

The Control Editors allow the user to switch the “memory preservation-bit” of
the CFGOPT parameter of Station block on and off. Any changes to this bit
can then be deployed to the Control Processor. This bit can be set in the
Configuration tab in the station block’s editor as shown in Figure 4-1.
Be aware that, as shown in Figure 4-1, when this bit (“B6 - Enable memory
preservation”) is set, the Configuration Option value 1024 (or 0x400) is
displayed.
Refer to the “Station Block” chapter of Integrated Control Block Descriptions
(B0193AX) for more information on configuring the Station block.

60 4. Control Processor Memory Management
Figure 4-1. Memory Preservation Bit
Additional checks are introduced during the deployment to display a warning

when the “B6 - Enable memory preservation” checkbox is not set. This
warning appears in Object Validation dialog box during a deployment
operation. This warning does not prevent you from proceeding with the
deployment operation.
The warning message is shown in Figure 4-2.

4. Control Processor Memory Management 61
Figure 4-2. Object Validation Warning
If the user sets this bit in the Station block and the Station block is included for
deployment, the warning message will not be displayed.
For Strategy Editor deployments, the message is shown as information, as
shown in Figure 4-3.
Figure 4-3. Deploy Dialog Box

Use of Sequence Block CSPACE Parameter

For sequence blocks (i.e. DEP, IND, EXC and MON), the CSPACE parameter
can be configured in the Control Editors to define the amount of memory (in
bytes) required for the sequence block in the control processor. Figure 4-4
shows the CSPACE parameter (CODE SPACE) in the block editor.
Figure 4-4. General Tab - Color Space
The CSPACE parameter is an integer type, non-connectable parameter for

sequence blocks. The CSPACE value must be in the range of 0 to 32000. Any
value less than zero (0) and greater than 32000 is not a valid value for
CSPACE.
The default CSPACE value for a sequence block is zero (0) which means that
the control processor calculates the memory required for the sequence block
being deployed, and allocates the required amount of memory for the block
and its code.
The control processor uses CSPACE to control the memory allocated for the
sequence block which includes the memory for the block itself and for its
associated sequence code. As such, any non-default value should be greater
than the block size and sequence code size added together (in bits).
Each time a sequence block is deployed (or redeployed), the Control software
reads the CSPACE value and if the deployed CSPACE value is zero, the
Control software calculates the memory requirements of the block, and
allocates (or re-allocates) the memory to hold the deployed block.
If the CSPACE value is non-zero and the sequence block is compiled or
deployed (or redeployed), the Control software checks the CSPACE value and
deploys the block only if the memory size equal to the CSPACE value is large
enough for installing the block into the control processor. As a result, the

memory is not reallocated for redeployment operations if the CSPACE

specified during the first deployment of the block is large enough to
accommodate the sequence code size changes since the first deployment of the
block.
CSPACE may be used to optimize the memory allocations (and reallocations)
made for sequence blocks in the control processor. By setting the CSPACE to a
reasonable value that includes the room for the future growth in the block
sequence code, the amount of controller memory fragmentation can be
minimized.
Deploy Options Dialog Box

The CSPACE options can be set to minimize memory fragmentation in control
processors. The Deploy Options dialog box provides the options to manage the
sequence block CSPACE values. The Deploy Options dialog box settings only
apply to sequence blocks and have no bearing on deployment of other blocks.
This dialog box can be accessed using the Control software menu Galaxy ->
Configure… -> Deploy Options …
Figure 4-5. Deploy Options Dialog Box
The options in this dialog box are explained below:

• Ignore CSPACE. This option lets the control processor calculate the
memory needed for successful deployment of the sequence block. The
Control software deployment operation ignores the configured CSPACE
value set by the user for the memory allocation calculations and a
CODESPACE value of zero (0) is sent to the control processor. The user
configured CSPACE parameter is sent to the controller as configured. This
is the same as the default deployment behavior for FCS v3.0 and earlier.
• Use block CSPACE as specified. In this option, the user-configured
CSPACE value is sent to the control processor. The user must be sure that
the configured value of CSPACE is large enough for the sequence block’s

code. Otherwise, the control processor may reject the block from
deployment. This is the standard CP behavior.
• Auto-expand CSPACE as needed and reserve [x] additional bytes.
This option directs the control processor to auto-expand the value of
CSPACE only when the value is insufficient for a successful sequence
block deployment. This option provides the operator with additional
control over the sequence block’s deployment operation, as described
below.
When the configured CSPACE value is sufficient to ensure a successful
deployment, the configured CSPACE value is sent to the control
processor. However, during the validation of sequence blocks, if the
Control software determines the configured value of CSPACE to be
insufficient and thereby would result in a failed sequence block
deployment, the Control software recalculates the required CSPACE value
and automatically increases the CSPACE parameter value to
accommodate the large sequence code and adds the configured “additional
bytes” to the recalculated value. This includes all blocks having
insufficient CSPACE, including blocks with CPSPACE equal to zero. In
doing so, the Control software changes the CSPACE value to a new value
large enough to ensure a successful deployment, including any additional
bytes set in the “additional bytes” field for future sequence block code size
increases.
This calculated CSPACE value is sent to the CP and committed to the
Galaxy upon a successful deployment operation.
Guidance on Configuring CSPACE

The following recommendations should be taken as guidance when
configuring the CSPACE parameter.
Note The user should always be careful when configuring the CSPACE
values when the Deploy Options dialog box is open, as users are prevented
from initiating deployment operations to any control processor from any client.
Similarly, if a deployment operation to a control processor is in progress, the
Deploy Options dialog box cannot be opened.
Also, the following scenarios provide recommended solutions for certain

configuration situations.
Scenario 1
No blocks are deployed to the controller, and the user does not want to
configure CSPACE.
Solution:
Select the Ignore CSPACE option in the Deploy Options dialog box. With this
selection, the controller will calculate the exact amount of memory required for
each block. Any subsequent change in sequence code size will trigger a
reallocation of that block in the controller.

Scenario 2
No blocks are deployed to the controller, and the user wants to configure
CSPACE.
Solution:
The user has following options in the Deploy Options dialog box:
• Use Block CSPACE as specified - This option does not modify the
CSPACE for blocks having insufficient CSPACE. For insufficient
CSPACE value, this option gives a warning.
• Auto-expand CSPACE as needed and reserve [x] additional bytes -
This option automatically modifies CSPACE for blocks having
insufficient CSPACE.
Scenario 3
The user has sequence blocks already deployed to the controller. These
sequence blocks do not use CSPACE, i.e. the CSPACE value is 0. Now the user
wants to take advantage of CSPACE.
Solution:
It is possible that after the upgrade to FCS v3.1, the user may want to start
using CSPACE. The user needs to analyze the existing configuration to ensure
that the database will continue to fit the existing controller's memory. When
using CSPACE values, it is recommended that the user should be deploying
individual compounds so that the controller memory usage may be monitored.
When using the option of Use Block CSPACE as specified, the Control
software will use the configured CSPACE values without any modification and
deploy blocks to the controller. For example, if a block has a CSPACE value of
0 and the block-size including the sequence code is 2000 bytes, then the
deployment will succeed and will cause an allocation of 2000 bytes. If the user
has a non-zero CSPACE value which is sufficient for deployment, the
deployment will succeed. For example, if a block has a CSPACE value of 2500
and the block-size including the sequence code is 2000 bytes, then the
deployment will succeed and will cause an allocation of 2500 bytes. On the
other hand, if the user has a non-zero CSPACE value that is insufficient for
deployment, the user will get a warning to increase the CSPACE during
compilation. For example, the user configures the CSPACE value of 1500 and
the block size including the sequence code is 2000 bytes; the block will fail to
deploy to the controller. It is recommended that the user should configure the
CSPACE value to be larger than the code-size so that future coding changes
will continue to fit in within the configured CPSPACE value. This will prevent
frequent memory reallocations in the controller. As explained, this option does
not change any CSPACE value automatically and gives control to the user to
specify a desired CSPACE value.
When using the Auto-expand option, all blocks having an insufficient
CSPACE value will be modified to a new value where the CSPACE is xxx
bytes more than that required to successfully deploy block. These xxx
additional bytes are to prevent memory reallocation in the controller due to
future coding changes. For example, if a block has a CSPACE value of 100 and
re-compilation recommends a CSPACE value of 2000. Now choosing an
Auto-expand option of 250 bytes, the block will be deployed with a CSPACE
of 2250. If the block did not exist in the controller, the controller will allocate

2250 bytes for the block. However, in the same example if the block was
already deployed in the controller and the sequence code was modified, the
subsequent deployment will cause a reallocation of 2250 bytes in controller. In
this example, even if the configured CSPACE was initially zero, the Control
software will modify the CSPACE to deploy with the new value of 2250 bytes.
This CSPACE modification is made in the controller as well as in the Galaxy
database.

Messages Related to CSPACE/Sequence Block

Deployment
The following message may appear during the deployment of a sequence block
using the Control Editors:
• Invalid CSPACE parameter value in block editor
The message displayed in Figure 4-6 is displayed when an operator
attempts to configure a value outside the valid CSPACE range of
0-32000.
Message: “Attribute CSPACE: Attempt to set the value to xxx; Valid
range: 0-32000 Parameter name: CSPACE, Actual Value=xxx”
Figure 4-6. CSPACE Configured Outside Valid Range

• Object Validation Messages for “Ignore CSPACE” Deploy Option

The following message (see Figure 4-7) is shown in Object Validation
dialog box when the Ignore CSPACE option is selected in the Deploy
Option dialog box and the operator attempts to deploy a sequence block
with a CSPACE value greater than zero.
Message: “Configured CSPACE is not being used for memory allocation
of XXX Sequence block. If you wish CSPACE to be considered, use
Deploy Options with appropriate selection.”
Figure 4-7. CSPACE Value Not Being Used in Memory Allocation -

Object Validation

• Strategy Editor Deployment Messages for “Ignore CSPACE” Deploy

Option
Figure 4-8 shows the messages that appear during the Strategy Editor
Deployment when the Ignore CSPACE option is selected in the Deploy
with a CSPACE value greater than zero.
Message: “Configured CSPACE is not being used for memory allocation
of XXX Sequence block. If you wish CSPACE to be considered, use the
Deploy Options with appropriate selection.”
Figure 4-8. CSPACE Value Not Being Used in Memory Allocation -

Strategy Editor

• Object Validation Messages for “Use block CSPACE as Specified”

Deploy Option
Figure 4-9 shows the message that appears during the Object validation
screen when the Use block CSPACE as specified option is selected in the
Deploy Option dialog box and the operator attempts to deploy a sequence
block with a CSPACE value which is less than the byte size of the
sequence block.
Message: “CSPACE entered is smaller than the actual block size. During
deployment, block may be rejected by the CP, due to error E3-
EXCEEDED SEQUENCE CODE SPACE”
Figure 4-9. CSPACE Value Smaller Than Sequence Block Size -

Object Validation

• Messages for “Use block CSPACE as Specified” Deploy Option in

Strategy Editor Deployment
The following message is shown during Strategy Editor Deployment
operations when the Use block CSPACE as specified option is selected in
the Deploy Option dialog box and the operator attempts to perform a
Strategy Editor Deployment operation for a sequence block with a
CSPACE value which is less than the byte size of the sequence block. See
Figure 4-10.
Message: “CSPACE entered is smaller than the actual block size. During
deployment, block may be rejected by the CP, due to error E3-
EXCEEDED SEQUENCE CODE SPACE”
Figure 4-10. CSPACE Value Smaller Than Sequence Block Size -

Strategy Editor

• Messages for “Auto-expand CSPACE as needed” Deploy Option in

Object Validation
The following message is shown in the Object validation dialog box when
the Auto-expand CSPACE as needed option is selected in the Deploy
and the deployment process finds that the CSPACE value is less than the
byte size of the sequence block. This warning message also indicates the
deployment operation has auto-calculated the required CSPACE value.
See Figure 4-11.
Message: “CSPACE entered is smaller than the actual block size.
Calculating CSPACE based on DEPLOY OPTION Settings. Configured
CSPACE = XXX, Calculated CSPACE = YYY”
Figure 4-11. CSPACE Value Smaller Than Sequence Block Size and To
Be Auto-Calculated - Object Validation

• Messages for “Auto-expand CSPACE as needed” Deploy Option in

Strategy Editor Deployment
The following message is shown during Strategy Editor Deployment
operations when the Auto-expand CSPACE as needed option is selected
in the Deploy Option dialog box and the operator attempts to deploy a
sequence block and the deployment process finds that the CSPACE value
is less than the byte size of the sequence block. The warning message also
indicates the deployment has auto-calculated the required CSPACE value.
See Figure 4-12.
Message: “CSPACE entered is smaller than the actual block size.
Calculating CSPACE based on DEPLOY OPTION Settings. Configured
CSPACE = XXX, Calculated CSPACE = YYY”
Figure 4-12. CSPACE Value Smaller Than Sequence Block Size and To
Be Auto-Calculated - Strategy Editor
Setting “Deploy Options” using Direct Access

You can also set the sequence block deployment options in the Deploy Options
dialog box using Direct Access with the following command:
<SetDeployOption Option=“value” CodeGrowthFactor=“factor”>
• Option is a required attribute whose value “value” should be one of the
following:
• CP
• USER_CONFIGURED
• IEE_CALCULATED
• CodeGrowthFactor is a required attribute when
Option=IEE_CALCULATED. The value of this attribute “factor” must be
within the range of 0 to 30000.

Note This command can be executed in Direct Access only when the user
specified in the Direct Access application has administrator privileges in the
Control software.

75
C H A P T E R 5
Additional Management
Procedures
This section describes all additional procedures required to manage the Control
Database Deployment.
Checkpoint Failure After Large Deployment of

Sequence Blocks
When you deploy a large number of sequence blocks (with the checkpoint
option enabled), the checkpoint operation may sometimes fail after the
deployment is done.
You must perform a manual checkpoint to the CP as follows:
• Select a CP in the Control Editors. Select Deploy Utilities option > choose
Checkpoint CP option from the context menu as shown in Figure 5-1.
Figure 5-1. Performing Manual Checkpoint

76 5. Additional Management Procedures
Concurrent Deployment Workflow

The Control Editors monitor deployments in progress in the Galaxy and ensure
a robust workflow by allowing multiple workstations to deploy concurrently
based on block and CP counts.
• By default, up to five workstations can initiate deployments concurrently.
• If the concurrent deployment threshold is reached, the Control Editors will
queue the new deployment requests until system resources become
available again. The Control Editors will display a dialog initiating the
deployment, and prompt you to cancel or wait:
a. If you select to wait, the Control Editors automatically re-attempt the
deployment every 15 seconds until you explicitly cancel the
deployment operation.
b. If you select to retry, the Control Editors immediately re-attempt the
deployment without waiting.
c. If you cancel, you must manually restart deployment later.
Figure 5-2. Deployment Progress

5. Additional Management Procedures 77
Additional SMC Log Messages/Descriptions

The following messages from the SMC log are explained below.
Control Processor Timing Out

The following message may appear in the SMC log if the control processor
timed out on the current call on a compound or block:
.........c_worevent failed: Event=31, ErrorCode=-4 (CEW101, CEW102, &
COW06A)
This is not an error. The client will retry contacting the CP to find the result of
the operation after some time.
This client may have to retry this several retries. Every time it finds the
controller is busy, a warning is logged to the SMC log.
After several timeouts have completed, the compound/block deploy/undeploy
operation must succeed, so it is assumed that the operation completed
successfully.
Network Interruption During ArchestrA Operation

The following message may appear in the SMC log if a network error occurred
while ArchestrA was performing the operation indicated in the log file.
Archestra Undeploy Failed:07MCS2_IO. Check for bulk operations in
progress or hosted Compound/Strategy checkouts.
Restart ArchestrA IDE and/or the aaGR process and this issue should be
resolved.
Deployment or Undeployment of Multiple

Compounds from Multiple Workstations
The following message may appear in the SMC log after undeploying or
deploying multiple compounds from multiple workstations:
Error at line number = 2, position = 2. The 'configuration' element is not
declared.
This message is for informational purposes only, and has no bearings on
whether or not the desired undeploy/deploy operation was completed.
Deployment of PLB Blocks

For PLB deployments, all strategies that contain PLB blocks connected to the
same FBM must be checked-in and closed. This is required for a correct PLB
binary to be set in the controller.
However, for Strategy Editor deployment of PLBs, the strategy being deployed
remains open but other strategies that have PLB blocks connected to the same
FBM must be closed.

78 5. Additional Management Procedures

79
Index
A
aligning the CP database with galaxy 41
ArchestrA
History 2
Security 2
authorize user access
FoxCTS server 51
B
baseline
control database sent to FoxCTS when change tracking enabled 53
blocks
identifying the deployed state of blocks 3
Undeploy Deploy to reset a block 40
bulk upload 39
C
change tracking 47
authorizing you to access FoxCTS information 51
creating a directory on the FoxCTS server 50
deployment events tracked with FoxCTS 48
enabling change tracking on a workstation 53
Field Device Manager downloads tracked with FoxCTS 49
link to FoxCTS Changing Tracking software 47
monitoring failed transfers 56
setup on the FoxCTS server 50
specifying the FoxCTS server 52
starting the FoxCTS Transfer Monitor on a workstation 55
starting the FoxCTS Transfer Service on the galaxy server 53
Checkpoint CP 8, 43
comparing the control processor database with the galaxy 45
Compound Summary Access (CSA) 2
compounds 4
Undeploy Deploy to reset a compound 40
controllers
deployment 3
undeploying a CP 36
CPs 3
D
DCI Block Deployment Mode Preparation dialog box 27
delete/undelete 40
Deploy command 8
Deploy dialog box 8
Deploy Utilities
Checkpoint CP 8
Selective Upload/Deploy 8
Synchronize DBs 43
Synchronize Deploy Status 8, 44
Undeploy/Deploy 8
Upload Compare 8, 45
Deployment 76
deployment 26
commands in the context menu 4
concurrent workflow 76
identifying undeployed objects in the Deployment view 2
modified objects 27
overview 1

80 Index
targets 2
description of the link to FoxCTS 47
E
equipment units 3
F
Field Device Manager
change tracking of downloads 49
Foundation fieldbus
change tracking of Field Device Manager downloads 49
redeploying function blocks 27
FoxCTS
deployment events tracked by FoxCTS 48
directory for deployment event files 50
enabling change tracking on a workstation 53
Field Device Manager downloads tracked by FoxCTS 49
monitor service on workstations 55
monitoring failed transfers 56
specifying the FoxCTS server for deployment event files 52
starting the transfer service on the galaxy server 53
FoxCTS Changing Tracking software 47
FoxCTS server
authorizing you to access change information 51
setup for change tracking 50
I
initializing a CP 36
K
known issues 75
M
modified objects 26
P
PROFIBUS
change tracking of Field Device Manager downloads 49
R
redeployment 26
Foundation fieldbus redeploying function blocks 27
reference documents v
Revision information v
S
Selective Upload/Deploy 8, 41
strategies 4
Synchronize DBs 43
Synchronize Deploy States 44
T
targets 2

Index 81
U
Undeploy command 8, 35
Undeploy dialog box 35
Undeploy/Deploy 8
Upload Compare 45
Upload Runtime Changes 8, 39
uploading
entire CP database 39
selected parameters 41

Invensys
10900 Equity Drive
Houston, TX 77041
United States of America
http://www.invensys.com
Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Website: http://support.ips.invensys.com

Control Database Deployment User's Guide: Foxboro Evo Process Automation System

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Control Database Deployment User's Guide: Foxboro Evo Process Automation System

Загружено:

Авторское право:

Доступные форматы

Foxboro Evo™

Process Automation System

Control Database Deployment

© 2006–2014 Invensys Systems, Inc. All Rights Reserved.

CHAPTER 1: Deployment ...................................1

CHAPTER 2: Deployment Utilities ...................39

CHAPTER 3: Change Tracking.........................47

Control Database Deployment User’s Guide – B0750AJ Rev M

Monitoring Transfers ............................................................................56

CHAPTER 4: Control Processor Memory

CHAPTER 5: Additional Management

Control Database Deployment User’s Guide – B0750AJ Rev M

Before You Begin

About This Book

Documentation Specific to the Foxboro Evo

Control Database Deployment User’s Guide – B0750AJ Rev M

• Appearance Object Editor User's Guide (B0750AE)

Control Database Deployment User’s Guide – B0750AJ Rev M

This chapter describes how to deploy equipment units, controllers, compounds,

Note You cannot deploy an unassigned object. For a selected compound, if

For information on the development of strategies, compounds, and control

Control Database Deployment User’s Guide – B0750AJ Rev M

Figure 1-1. Modeless Deployment Dialog Box

There are three targets updated in the deployment:

Control Database Deployment User’s Guide – B0750AJ Rev M

This strategy is undeployed.

The strategy has been deployed.

The strategy is deployed, but its

Figure 1-2. Deployment Status in the Application Views

This block is undeployed. The block

The block has been deployed. Its

Figure 1-3. Identifying the Deployment Status of a Block

Control Database Deployment User’s Guide – B0750AJ Rev M

blocks are downloaded to the CP. To initialize a control processor, reboot

Control Database Deployment User’s Guide – B0750AJ Rev M

Figure 1-4. Context Menu in the Deployment View

Control Database Deployment User’s Guide – B0750AJ Rev M

Note If you select dissimilar objects (for example, a compound and a

The Control Software Database Deployment provides a wizard-based

Control Database Deployment User’s Guide – B0750AJ Rev M

Figure 1-5. The Control Software Control Database Deployment

Control Database Deployment User’s Guide – B0750AJ Rev M

Deploying Control Objects

Menu Selection Description

Control Database Deployment User’s Guide – B0750AJ Rev M

Figure 1-6. Controller Selected in the Example

Control Database Deployment User’s Guide – B0750AJ Rev M

Select Objects for Deployment

Note Incorrect selection of objects in the Select Objects for

Figure 1-7. Select Objects for Deployment (Step 1 of 4) Dialog Box

In this example, the command is selected from the CP to illustrate certain

Control Database Deployment User’s Guide – B0750AJ Rev M

• Click Finish to deploy the blocks directly by skipping Steps 2 and 3.

• Click Cancel to stop the deploy process.

Figure 1-8. Select Block for Compilation

Control Database Deployment User’s Guide – B0750AJ Rev M

Figure 1-9. Compilation Results of Compilation Blocks

Note Cascade Selection, Compile Blocks and Checkpoint are toggle

For information on system-level validations performed on the System

Deploy Type Filter and Strategy Filter

Control Database Deployment User’s Guide – B0750AJ Rev M

• Show Undeployed Items - Clear the check box to hide the

Note A selected object in the Select Objects for Deployment (Step 1 of