Control Software v7.1 Release Notes: Foxboro Evo Process Automation System

Foxboro Evo™
Process Automation System
Control Software v7.1

Release Notes
*B0750ST* *D*
B0750ST
Rev D
February 05, 2019
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 Schneider Electric
Systems USA, 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 Schneider
Electric Systems USA, Inc. The software described in this
documentation is furnished under a license or nondisclosure
agreement. This software is used or copied only in accordance with
the terms of these agreements.
©2018-2019 Schneider Electric.
All Rights Reserved.
Trademarks
Schneider Electric, EcoStruxure, Invensys, Foxboro, Foxboro Evo,
and I/A Series are trademarks of Schneider Electric, its subsidiaries
and affiliates.
All other brand names are trademarks of their respective owners.
iii
Contents
Safety Information.............................................vii
Before You Begin ...............................................ix

About This Book ................................................................................... ix
Revision Information............................................................................. ix
Purpose .................................................................................................. ix
Control Software Updates ...................................................................... x
Reference Documents ............................................................................ x
The Control Software v7.1, I/A Series Software v8.8, and Control
Core Services v9.x Documentation .................................................... x
Wonderware Software Documentation............................................. xii
The Control Software v7.1

Installation Overview ..........................................1
Product Contents .................................................................................... 1
The Control Software Updates............................................................... 6
Operating System Support ..................................................................... 6
Compatibility with Control Software v7.1 ......................................... 6
Upgrade Considerations ......................................................................... 6
The Control Software Updates............................................................... 7
The Control Software v7.1 Installation on Off-Control
Network Stations .................................................................................... 8
Network Configuration for Off-Control Network Stations ................ 8
New Features .......................................................9

New Features in Foxboro Evo Control Software v7.1 ........................... 9
ControlHMI v7.1 ................................................................................ 9
New Features in Foxboro Evo Control Software 7.0 ........................... 10
Control Editors v7.0 New Features .................................................. 10
Control HMI v7.0 ..............................................................................11
Field Device Manager v4.0 .............................................................. 14
Wonderware System Platform 2014 R3 New Features .................... 15
Restrictions .......................................................21
Access Manager v7.1 ........................................................................... 21
DI Object .......................................................................................... 21
Control Editors v7.1 ............................................................................. 22
Preventing Multiple Users from Performing Bulk Operations......... 22
Synchronizing Block and Compound Deployment Status ............... 22
Control Software v7.1 Release Notes – B0750ST Rev D

iv Contents
Synchronizing ArchestrA and Control Block

Deployment Statuses .........................................................................23
Deploying Platform Objects ..............................................................23
Integrated Control Configurator (ICC) and
Control Editors Tools Coexistence....................................................23
User Notes .........................................................25

General ..................................................................................................25
General Performance .........................................................................25
Verify NIC Card Binding Order ........................................................26
Virus Scanning Guidelines ................................................................26
Creating Virtual Memory Page Files ................................................27
Use of Non-ASCII Characters...........................................................27
FoxCTS v7.00.00 ..............................................................................27
Using the Control Software Without an
Active Network Connection..................................................................27
Install Microsoft Loopback Adapter .................................................27
The Control Software Installation v7.1.................................................28
Off-Mesh PDC/SDC Must Have Galaxy IP
Address in HOSTS File .....................................................................28
Control HMI v7.1..................................................................................29
Alarms not appearing in migrated HMI Alarm Panels......................29
Quality Style for OOS on Migrated Systems ....................................29
Managed Control HMI ......................................................................29
Control HMI Resolution....................................................................33
Platform Redeployment May Cause Control HMI InTouch to Not
Display Alarms..................................................................................33
Features Not Recommended for Use with
the Control Software..........................................................................33
General Notes ....................................................................................34
I/A Series/Control Core Services Alarm Field
Conversion to InTouch or Control HMI Alarm Format ....................40
Faceplates ..........................................................................................42
Framer Software ................................................................................43
Alarm Server .....................................................................................43
WindowMaker Software....................................................................44
Access Manager ....................................................................................45
I/A Series Alarm Provider .................................................................45
I/A Series Data Access Server...........................................................47
I/A Series Device Integration Object ................................................48
I/A Series History Provider ...............................................................49
Control Editors v7.1..............................................................................53
SFC Editor .........................................................................................62
Strategy Editor...................................................................................63
Execution Order.................................................................................63
HART ....................................................................................................63
ECB Period for HART FBMs............................................................63
FoxCom I.F.D Modem Support.........................................................64

Contents v
Foxboro Control Software Export plugin ......................................... 64

SaveAll Export/Import Operations Not Supported for HART ......... 64
Uninstalling Foxboro FoxCom DTMs ............................................. 64
FOUNDATION fieldbus ...................................................................... 64
FOUNDATION fieldbus Schedule
Deployment and Un-Deployment..................................................... 64
Single Block Deployment and Un-Deployment ............................... 65
SaveAll Import/Export Operations Not
Supported for FOUNDATION fieldbus Devices and Blocks........... 65
DTM Compatibility - HART, FOUNDATION Fieldbus and
PROFIBUS ....................................................................................... 66
PROFIBUS........................................................................................... 67
ICC and SMDH Support for the FBM222........................................ 67
FBM222 at Low Baud Rates ............................................................ 67
PROFIBUS FBM Editor................................................................... 69
SaveAll Import/Export Operations Not Supported for Profibus ...... 69
Galaxy Server....................................................................................... 69
Additional Steps Required on Galaxy Created Using
Galaxy Backup (.cab) File ................................................................ 70
Known Issues and

Workarounds .....................................................73
The Control Software v7.1 Installation ................................................ 74
Control HMI......................................................................................... 77
Faceplates ......................................................................................... 84
BlockSelect ....................................................................................... 84
Framer Software ............................................................................... 85
Trending............................................................................................ 85
Access Manager ................................................................................... 85
InFusionSyncService ........................................................................ 85
I/A Series Alarm Provider ................................................................ 87
I/A Series History Provider .............................................................. 87
Control Editors ..................................................................................... 91
Control Editors Multi-User Access ................................................. 91
General.............................................................................................. 94
Direct Access .................................................................................... 99
Bulk Data ........................................................................................ 102
Control Block Configuration ...........................................................110
Deployment .....................................................................................114
Pepperl & Fuchs Intrinsically Safe I/O Subsystem .........................119
Foundation fieldbus and PROFIBUS ..............................................119
Hardware Configuration ................................................................. 125
Import/Export ................................................................................. 131
Library Object................................................................................. 134
PLB Editor ...................................................................................... 134
HLBL Editor................................................................................... 136
SFC Editor ...................................................................................... 136

vi Contents
Strategy Editor.................................................................................138
Live Data Display............................................................................144
Field Device Manager .........................................................................144
Vendor DTM....................................................................................144
Issues Resolved ..............................................145

The Control Software v7.1 Issues Resolved .......................................145
The Control Software v7.0 Issues Resolved .......................................146
Historian Data Import Utility...........................149

Historian Data Utility..........................................................................149
Importing Data From CSV Files.........................................................150

Safety Information
Important Information
Read these instructions carefully and look at the equipment to
become familiar with the device before trying to install, operate, ser-
vice, or maintain it. The following special messages may appear
throughout this manual or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies
a procedure.
The addition of either symbol to a "Danger" or

"Warning" safety label indicates that an electrical
hazard exists which will result in personal injury if
the instructions are not followed.
This is the safety alert symbol. It is used to alert you to

potential personal injury hazards. Obey all safety messages
that follow this symbol to avoid possible injury or death.
DANGER
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.
WARNING
WARNING indicates a hazardous situation which, if not avoided, could
result in death or serious injury.
CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury.
Please Note
Electrical equipment should be installed, operated, serviced, and main-
tained only by qualified personnel. No responsibility is assumed by
Schneider Electric for any consequences arising out of the use of this
material.
A qualified person is one who has skills and knowledge related to the con-
struction, installation, and operation of electrical equipment and has
received safety training to recognize and avoid the hazards involved.
ix
Before You Begin
About This Book

This guide describes the new features, known issues, and workarounds for the
Foxboro Evo™ Control Software v7.1 (the Control Software), which contains
components including the following:
• Foxboro Evo Control HMI (Control HMI)
• Access Manager
• Foxboro Evo Control Editors (Control Editors)
Revision Information
For this revision of this document (B0750ST, Rev. D), this change was made:
Chapter 1, “The Control Software v7.1 Installation Overview”
• Updated Table 1-8.
Purpose
The purpose of these release notes is to document new features, user notes,
known issues and workarounds, and issues resolved for Control Software v7.1.
The restrictions are limitations, put in place temporarily, in order to address
incomplete functionality or features of the product. If these restrictions are not
understood, they could potentially allow you to access or generate corrupt data,
or result in abnormal installation or termination of Control Software v7.1.
User notes contain information on how the product functions and helpful hints
that may not be evident from the product’s associated user guide. User notes
can also contain issues that you need to be aware of when using the product.
Similar to restrictions, known issues represent temporary deficiencies in the
product. Frequently, these types of issues result from incomplete functionality
in the product.
Workarounds provide a means of bypassing a known issue and enabling you to
perform an operation that would otherwise be prohibited or difficult to execute.
For more information, please contact Global Customer Support at:
E-mail: [email protected]

x Before You Begin
Control Software Updates

Updates to Control Software are posted on the Global Customer Support web
site: https://pasupport.schneider-electric.com.
For Quick Fixes, log on to the Global Customer Support web site and go to the
Support tab to find the latest Control Software updates. Check this web site
periodically for the latest updates.
For accessing maintenance releases, log on to the Global Customer Support
web site and go to the Support tab.
For accessing security patch releases of Foxboro Evo Control Core Services,
ArchestrA, and Microsoft, log on to the Global Customer Support web site and
go to Support > Security.
Reference Documents
These sections list reference documents for Control Software v7.1, I/A Series®
software 8.8, Foxboro Evo Control Core Services software v.9x (hereinafter
referred to as Control Core Services software) and Wonderware® software.
The Control Software v7.1, I/A Series Software

v8.8, and Control Core Services v9.x
Documentation
For additional information on the Control Software v7.1, I/A Series® v8.8, and
Control Core Service v9.x, refer to the documents listed by category in the
following sections.
Installation and Getting Started

• Foxboro Evo Process Automation System Deployment Guide (B0750BA)
• Foxboro Evo Control Software Installation Guide (B0750RA, Rev. Z or
later)
• Hardware Configuration User’s Guide (B0750BB)
• Control Core Services v9.x Software Installation Guide (B0700SP,
B0700SS, B0700SU, B0700SW, B0700SX)
• Control Core Services v9.4 Release Notes (B0700SY)
• I/A Series V8.8 Software Installation Guide (B0700SF)
• I/A Series System V8.8 Release Notes (B0700SG)
System Development
• Control Processor 270 (CP270) and Field Control Processor 280 (CP280)
Integrated Control Software Concepts (B0700AG)
• Access Manager User's Guide (B0750AD)
• Appearance Object Editor User’s Guide (B0750AE)

Before You Begin xi
• Bulk Data Editor User's Guide (B0750AF)

• Common Graphical Editor Features User's Guide (B0750AG)
• Block Configurator User's Guide (B0750AH)
• Control Database Deployment User's Guide (B0750AJ)
• PLB Ladder Logic Editor (B0750AK)
• Sequence Block HLBL Editor User's Guide (B0750AL)
• Block SFC Editor User's Guide (B0750AM)
• Strategy Editor User's Guide (B0750AN)
• Configuration Utilities (B0750AZ)
• InSQL Legacy Servers User’s Guide (B0750BD)
Note The term “InSQL” has been replaced with “Wonderware Historian”.
• Logic Block Editor and Troubleshooting Tool User’s Guide (B0750BL)

• Scripting with Direct Access User’s Guide (B0750BM)
End-User Graphical User Interface Configuration and Operation

• System Manager (B0750AP)
• Control HMI Application User's Guide (B0750AQ)
• Framer and Alarm Management User’s Guide (B0750AR)
• Window Construction User’s Guide (B0750AS)
• Bulk Graphic Editor User’s Guide (B0750CT)
Field Devices
• Implementing FOUNDATION™ fieldbus in Foxboro Evo Core Services
Applications (B0750DA)
• Field Device Manager and Foxboro Instrument Workshop for
FOUNDATION fieldbus Installation Guide (B0750CK)
• Implementing PROFIBUS™ Networks in Foxboro Evo Control Software
Applications (B0750BE)
• 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)
• Foxboro Field Device Manager and Foxboro Instrument Manager for
PROFIBUS Networks Installation Guide (B0750CJ)
• Maintenance Response Center User's Manual (B0750CP)
• Maintenance Response Center Installation Guide (B0750CQ)

xii Before You Begin
• Asset Condition Monitoring Installation Guide (B0750CR)
Wonderware Software Documentation

For additional information on Wonderware software, refer to the following
documents:
• Application Server Scripting Guide
• Application Server User's Guide
• Creating and Using ArchestrA Graphics
• Galaxy Database Manager User's Guide
• Historian Client User Guide
• InTouch Alarms and Events Guide
• InTouch Application Management and Extension Guide
• InTouch ArchestrA Integration Guide
• InTouch Concepts and Capabilities
• InTouch Data Management Guide
• InTouch Documentation Guide
• InTouch ITModernApp Guide
• InTouch Protocol Guide
• InTouch Scripting and Logic Guide
• InTouch Smart Symbols Guide
• InTouch Supplementary Component User's Guide
• InTouch Visualization Guide
• InTouch XML Importer User Guide
• InTouchTagViewer
• Object Viewer User's Guide
• Platform Manager User's Guide

1
C H A P T E R 1
The Control Software v7.1

Installation Overview
This chapter gives an overview of the Control Software v7.1. installation.
Contents
• Product Contents
• Operating System Support
• Upgrade Considerations
• The Control Software Updates
• The Control Software v7.1 Installation on Off-Control Network Stations
1.1 Product Contents

The standard software media for this release of the Control Software v7.1
consists of the following components, including media kits, CD-ROMs, and
documentation.

2 1. The Control Software v7.1 Installation Overview
Table 1-1. Media Kit K0203BN-A Foxboro Evo™ Control Software
Part Number Description

K0203BP-A Foxboro Evo Control Software
Includes:
• Control Editors v7.1
• Access Manager v7.1
• Control HMI v7.1
Wonderware P/N 06-2740 Wonderware System Platform 2014 R3 and InTouch 2014 R3
Includes:
• Wonderware Application Server 4.2 P01*
• Wonderware InTouch 11.2 P01*
• Wonderware Historian Client 10.6
• Wonderware Historian Server 11.6 P01*
Note *Control Software installs additional patches on top of

Wonderware System Platform 2014 R3. The final installed version of
Application Server and InTouch is WSP 2014 R3 Patch 01 (v4.2 P01
and v11.2 P01) respectively. The final installed version of Historian
Server is 2014 R2 SP1 (v11.6 P01).
Wonderware P/N 06-2747 Wonderware Information Server 2014 R3

Wonderware P/N 06-2715 Wonderware Device Integration
Wonderware P/N 06-2541 Microsoft SQL Server® 2008 Standard Edition
Wonderware P/N06-2713 Microsoft SQL Server® 2014 SP1 64-Bit Standard Edition
K0200ZE-C Microsoft Office Visio® 2010 Standard Edition
Table 1-2. Foxboro Evo Field Device Manager for FOUNDATION™ Fieldbus
v4.1 DVD

K0203CK-A Foxboro Evo Field Device Manager for FOUNDATION Fieldbus
v4.1 DVD
Table 1-3. Media Kit K0203BQ-A - Foxboro Evo FOUNDATION Fieldbus Instrument v4.1
Workshop

K0203CN-A Foxboro Evo Field Device Manager Workshop for FOUNDATION
Fieldbus v4.1
K0203BN-A Foxboro Evo Control Software v7.1 kit
Wonderware P/N 97-1377 Foxboro FF Instrument Workshop, (WAS4.2/CntrlEd7.0)

1. The Control Software v7.1 Installation Overview 3
Table 1-4. Foxboro Evo Field Device Manager for HART v4.1 DVD

K0203CL-A Foxboro Evo Field Device Manager for HART v4.1 DVD
Table 1-5. Media Kit K0203BS-A - Foxboro Evo HART Instrument v4.1 Workshop

K0203CP-A Foxboro Evo Field Device Manager Workshop Software for
HART v4.1 DVD
K0203BN-A Foxboro Evo Control Software v7.1 Kit
Wonderware P/N 97-1377 Foxboro FF Instrument Workshop, (WAS4.2/CntrlEd7.0)
Table 1-6. Foxboro Evo Field Device Manager for PROFIBUS v4.1 DVD

K0203CM-A Foxboro Evo Field Device Manager for PROFIBUS v4.1 DVD
Table 1-7. Media Kit K0203BV-A Foxboro Evo PROFIBUS Instrument Workshop

K0203CM-A Foxboro Evo Field Device Manager for PROFIBUS v4.1 DVD
K0203BN-A Foxboro Evo Control Software v7.1 Software Media Kit
Table 1-8. Foxboro Evo for DeviceNet v1.1 Installation DVD

K0203BF-A Foxboro Evo for DeviceNet v1.1 installation DVD
Table 1-9. Asset Condition Monitor Installation DVD

K0203BZ-A Foxboro Evo Asset Condition Monitor v1.3 CD
Also refer to the following documents for the Field Device Manager and the
Control Software v7.1 Support for DeviceNet media kits:
• Field Device Manager and Foxboro Instrument Workshop for PROFIBUS
Networks Installation Guide (B0750CJ)
• Field Device Manager and Foxboro Instrument Workshop for
FOUNDATION fieldbus Installation Guide (B0750CK)
• Foxboro Evo for DeviceNet Installation Guide (B0750CL)
• Field Device Manager for HART Devices Installation Guide (B0750CN)

Note Wonderware System Platform2014 R3 is provided on a Dual Layer

DVD. There may be an issue installing the Dual Layer DVD on some older
Dell Server DVD drives. If this happens, you may need to use an external
DVD drive to install WSP R3.
The mixed mode systems supported include:
Table 1-10. Available Mixed Mode Systems Supporteda
Hardware/Software (Includes the Control Software CCS Local or

Type v7.1) Enterprise Edition
1 Servers - I/Av8.8 or Control Core Services v9.x on Windows Local
Server 2008 R2 Standard
Servers - Control Core Services v9.4 on Windows Server 2016
Workstations - I/A v8.8 or Control Core Services v9.x on

Windows 7
Workstations - Control Core Services v9.4 or above on Windows

10

Table 1-10. Available Mixed Mode Systems Supporteda
Hardware/Software (Includes the Control Software CCS Local or

Type v7.1) Enterprise Edition
2 PDC/SDC with Windows Server 2008 R2 Standard - Off-Control Enterprise Edition
Network or on The Control Network with I/Av8.8 or Control
Core Services v9.x Servers
PDC/SDC with Windows Server 2016 - Off-Mesh or on The

Mesh with Control Core Services v9.4 or above Servers
I/A v8.8 or Control Core Services v9.x Servers on Windows

Server 2008 R2 Standard, Control Core Services v9.4 or above
Servers on Windows Server 2016

Windows 7, Control Core Services v9.4 or above on Windows 10
3 PDC/SDC with Windows Server 2008 R2 Standard – Enterprise Edition
Active Directory Migrated from 2003, Off-Control Network or
on-Mesh with I/A v8.8 or Control Core Services v9.0, v9.1, v9.2
or v9.3
PDC/SDC with Windows Server 2016 –

Active Directory Migrated from 2003 and 2008 –
Off-Control or on-Mesh with Control Core Services v9.4 or
above
Servers - I/A v8.8 or Control Core Services v9.x Servers

on Windows Server 2008 R2 Standard or Windows Server 2003,
Control Core Services v9.4 or above Servers on Windows Server
2016, Off-Control on Windows Server 2008 R2 Standard or
Windows Server 2016

Windows 7 or Windows XP, Control Core Services v9.4 or above
on Windows 10, Off-Control on Windows 7 or Windows 10
a. For mixed mode installations on platforms with security enhanced I/A Series Control Core Services software, the
PDC must be upgraded from the lowest supported version of I/A Series software v8.8 to the highest supported ver-
sion of I/A Series software or Control Core Services software (v8.8 or v9.x). Clean (new) installations of Control
Core Services v9.x will not support stations with I/A Series software v8.7. Refer to the migration scenarios in “In-
stallation or Migration Scenarios for Security Enhanced I/A Series Software v8.8” in I/A Series System V8.8 Soft-
ware Installation Guide (B0700SF) or “Installation or Migration Scenarios for Security Enhanced Control Core
Services v9.x” in Control Core Services v9.x Software Installation Guide (B0700SP).
Also, the SDC must be upgraded to the same level as the PDC.

1.2 The Control Software Updates

Updates to Control Software are posted on the Global Customer Support web
site: https://pasupport.schneider-electric.com.
For Quick Fixes, log on to the Global Customer Support web site and go to the
Support tab to find the latest Control Software updates. Check this web site
periodically for the latest updates.
Installation and other user documentation can be found on the GCS website.
This documentation is also accessible on the Control Software media.
For accessing maintenance releases, log on to the Global Customer Support
web site and go to the Support tab.
For accessing security patch releases of Foxboro Evo Control Core Services,
ArchestrA, and Microsoft, log on to the Global Customer Support web site and
go to Support > Security.
1.3 Operating System Support

The Control Software v7.1 is qualified only for the following operating
systems:
• Windows 7 64-bit Service Pack 1
• Windows Server 2008 R2 Standard Service Pack 1
• Windows 10
• Windows Server 2016
1.3.1 Compatibility with Control Software v7.1

To help ensure compatibility with Control Software v7.1, upgrade the
following software to the specified versions.
• Control Core Services v8.8 through v9.4
• InBatch v11.5
• Unity Pro v8.1
Additionally, the following system requirement should be met.
• Running the Control HMI requires multiple cores. This is especially
important if you are running on virtual machines.
1.4 Upgrade Considerations

If the upgrade is to be performed on a running plant, the following conditions
must be considered and an upgrade plan needs to be developed.
Systems with Control Software v5.x or above can upgrade directly to the
Control Software v7.1 on a platform with the operating systems listed above in
“Operating System Support”.

Systems with earlier versions of InFusion or Foxboro Control Software must

first upgrade to Control Software v5.x before they can be upgraded to the
Control Software v7.1. You must follow the appropriate upgrade path,
depending on your version of InFusion or Foxboro Control Software.
For pre-Control Software v5.x systems, refer to the upgrade path diagrams in
I/A Series System V8.7 Release Notes and Installation Procedures (B0700SE).
Note Control Software v7.1 cannot be upgraded directly from InFusion CE

(v1.x and v2.x) or from Foxboro Control Software (v3.x and v4.x). When
upgrading from those systems, refer to the section “Guidelines for Upgrading”
in Foxboro Evo Control Software Installation Guide (B0750RA, Rev. Z or
later).
For upgrades to any of the Foxboro Control Software Packs on stations with
the Control Software v7.1, any Field Device Manager, Foxboro Instrument
Workshop, or the following other packages must be upgraded prior to Galaxy
Preparation:
• For information on upgrading previous versions of FOUNDATION
fieldbus, refer to Field Device Manager and Foxboro Instrument
Workshop for FOUNDATION fieldbus Installation Guide (B0750CK).
• For information on upgrading previous versions of PROFIBUS, refer to
Field Device Manager and Foxboro Instrument Workshop for PROFIBUS
Networks Installation Guide.
• For information on upgrading previous versions of HART, refer to the
Field Device Manager for HART Devices Installation Guide (B0750CN).
Note Any additional products that are part of the Galaxy can only be updated
after the Wonderware System Platform (WSP) has been updated.
1.5 The Control Software Updates

Updates to the Control Software are posted on the Global Customer Support
web site: https://pasupport.schneider-electric.com.
For Quick Fixes, once you log on to the Schneider Electric Global Customer
Support for Foxboro and Triconex web site, go to the Support tab.
For security patches and maintenance releases, once you log on to the
Schneider Electric Global Customer Support for Foxboro and Triconex web
site, go to the Support tab.
Security patches are accessed from the Support > Security menus. I/A Series,
Control Core Services, ArchestrA, and Microsoft security patches can be found
here.

1.6 The Control Software v7.1 Installation on

Off-Control Network Stations
The Control Software v7.1 needs special attention for Off-Platform
installations. Also, the host file needs to be modified in order for the Control
Software v7.1 to function correctly.
1.6.1 Network Configuration for Off-Control

Network Stations
When installing a Galaxy Repository on an Off-Control Network non-Foxboro
workstation with multiple CPUs, perform the following steps:
1. Provide the server IP address. This should be either a DHCP IP address or
a local hub address through which the client can communicate with the
server in a client machine’s host file. This file is located at:
C:\WINDOWS\system32\drivers\etc.
2. Provide the client IP Address in a Server machine’s host file. This file is
located at:
C:\WINDOWS\system32\drivers\etc.
3. Restart the InFusion Sync Service if you have proceeded with the Control
Software v7.1 installation to the configuration step/Galaxy preparation
tab.
4. Proceed with Galaxy Preparation in the client station as described in
Foxboro Evo Control Software Installation Guide (B0750RA, Rev. Z or
later).

9
C H A P T E R 2
New Features
This chapter describes the new features included in the Control Software v7.1
and v7.0.
To review a list of features released with the Control Software v6.3 or earlier
refer to the Control Software v6.3 Release Notes (B0750SM).
Contents:
• New Features in Foxboro Evo Control Software v7.1
• New Features in Foxboro Evo Control Software 7.0
2.1 New Features in Foxboro Evo Control

Software v7.1
2.1.1 ControlHMI v7.1

Note The Control HMI must be run on a multicore-enabled machine.
• Alarm Server startup and restart performance has been improved and
updates to the HMI are no longer delayed while the Alarm Server is
started.
• New Print Screen options have been provided and can be configured in
Framer. The Print Screen action can be configured to execute external
commands to do the screen capture. For example, a command can be
configured to use HyperSnap to do screen captures. See B0750AR > Print
Action for details
• The Control HMI provides better support for VM Thin clients and Alarm
Server Management. See B0750AS > Control HMI VM Thin Client
Environment for details.
• The Wonderware Alarm Printer utility has been enhanced to allow
"printing" of all the fields in an alarm record. This enables the block
descriptor to be included in the information that can be printed for a
control block alarm.

10 2. New Features
• The BIAS Block Detail display was updated to include the missing
UNCLMP setting. This setting can be found on the CNFG>OVRRD detail
view of the BIAS Block Detail Display.
• Control HMI InTouch applications that are deployed to a Remote Desktop
server with a read-only license need to be modified to support the read-
only license. Read-Only licenses are most often combined with
InTouch Access Anywhere, but any instance where an InTouch read-only
license has been installed is affected. Refer to SOL3270 on the GCS
website to make these changes (https://pasupport.schneider-
electric.com/km/index?page=content&id=SOL3270).
2.2 New Features in Foxboro Evo Control

Software 7.0
• Control Editors v7.0 New Features
• Field Device Manager v4.0
2.2.1 Control Editors v7.0 New Features

• Support for User Defined Block Attributes
• Control Software Activity Utility
2.2.1.1 Block User Attributes

A block user attribute is a custom parameter which can hold a string value, that
may be assigned to one or more block types. The attributes can hold any type
of data you want. For example, they can hold system information for a
particular device type, such as a device's manufacturer, type, and tag.
User attributes are discussed in detail in the "User Attribute Definition Dialog
Box" section in Configuration Utilities User's Guide (B0750AZ).
2.2.1.2 Control Software Activity

Control Software activity is an IDE view component that provides live
dynamic user interactions and Galaxy operations in Control Editors for the
connected Galaxy users.
Control Software Activity contains these features:
• Indicates users connected to the Galaxy.
• Measures the network round-trip performance and tracks values in the
Galaxy database.
• Enables interaction between users by broadcasting messages.
• Displays Galaxy operations in progress.
• Tracks analytics data into SQL for system and usage analysis, debugging
and investigating user workflows.

2. New Features 11
For more information about the Control Software Activity utility refer to
Configuration Utilities User's Guide (B0750AZ).
2.2.2 Control HMI v7.0
2.2.2.1 Access Manager v7.0

2.2.2.1.1 #FT extension
The I/A Series DI Object now supports the ability to drive the update of string
control block parameters based on a change-driven “trigger” parameter. The
trigger extension (#FT) includes two parameters: tag parameter and trigger
parameter. The DI Object places the trigger parameter on scan in an Object
Manager list, and then reads the tag parameter when the trigger parameter
either changes in value or in status. The extension can be used with non-
connectable parameters that dynamically change value (for example SN000x
parameters of Sequence blocks). This feature is most often used to more
efficiently update string values in the Control HMI.
2.2.2.1.2 #FC extension

When the #FC extension is used with non-connectable parameters, the DI
Object, after reading the parameter once, places the parameter on scan and
reads it every time the parameter status changes from out-of-service to good.
The change helps ensure that DI Object provides the correct parameter value
after block redeployment.
2.2.2.1.3 Object Manager List Scan Rate Default

DI Object OM List Scan Rate default setting changed to 1000 ms from 500 ms.
When upgrading to Control Software 7.0, this setting will be modified to
1000ms in all deployed DI Object instances, if the List Scan Rate in the
deployed DI Object instance is 500ms. If the List Scan rate has been modified
to another scan rate, the List Scan Rate will not be changed. When deploying
new instances of the DI Object, the List Scan Rate will be 1000ms in the newly
deployed DI Object.
2.2.2.1.4 Object Manager Deadband

DI Object OM Deadband default setting has been changed to 0.01 from
0.000001. During upgrade the setting of existing DI Object instances will not
be changed. In order to modify the Deadband setting in a deployed instance of
the DI Object, either modify each instance individually, or modify the value in
the DI Object template and redeploy.
2.2.2.2 Bulk Graphic Editor and Report Tool

The Bulk Graphic Editor (BGE) is a tool that can execute bulk operations on
ArchestrA Graphics through a scripting interface or through a dialog that is
accessed from ArchestrA IDE's Graphic Toolbox context menu.

12 2. New Features
This tool provides the ability to quickly modify animations, scripts and text
labels, as well as generate Tag reports of selected ArchestrA Graphics. The
functions include:
Function Description
Update Links Renames graphics by updating the internal
symbol links without the need to open and save
each individual graphic.
Export / Import Exports graphics to modifiable XML files.
These files contain the full content of the
graphic. Exported XML files can be renamed,
modified, and imported as new graphic symbols.
Dump/Upload Modifies bulk animations and text inside one or
more graphics. The Dump function is used to
extract all expressions, scripts, and text labels
and store them in a spreadsheet. The extracted
data is stored in an XML or Microsoft ® Excel
file that can be modified and uploaded back to
the Graphic Symbols.
Find Replace Provides the ability to search for occurrences of
(scripting only) tag names, expressions, labels and scripts, and
replace with alternate text.
Tag Reports Creates a report of all references that are
configured in the graphic. It also includes the
information on the references, such as, whether
they exist or not and where these have been
deployed. The report can also include
information about where in the graphic or
embedded child graphics the references have
been used.
Complete information on the Bulk Graphics Editor can be found in B0750CT.
2.2.2.3 Control Situation Awareness (CSA) Toolkit

Symbols
The System Platform 2014 R2 introduced a new set of Valve Symbols. Like in
the existing CSA Graphics provided in 6.0, these new symbols have many
options and properties that make them difficult to use and configure.
The Toolkit symbols provide sets of simplified components with very few
options. You can easily pick and configure the indicators you want to use in the
graphics. Indicators and labels can be moved to any location. This helps
eliminate the need to duplicate, break, or modify graphics.

2. New Features 13
CSA Toolkit Symbols include:
Symbols Description
Values Includes a variety of 2 port, 3 port, and 4 port
valve symbols.
Alarm Border Includes a new Alarm Border symbol that is
optimized for best performance.
Indicators Includes a set of common indicator symbols that
are found in many of the CSA Graphics.
Text Includes a set of common text symbols that are
found in many of the CSA Graphics.
PolarStar Provides a polar star spoke symbol that can be
used to create custom polar star indicators.
2.2.2.4 Connector Lines

The new and existing CSA Graphics have been updated with Connector Points
to support the new Graphic Connector tool. For more information see Creating
and Managing Graphics User's Guide (AAGraphics.pdf)
2.2.2.5 CSA Graphic Alarm Borders

Existing CSA Graphics have been optimized to reduce the number of IO
connections. Existing graphics that have been built with instances of the
previous set of CSA Graphics will not be updated and will not see the benefit
of this optimization. Instances of the Alarm Border symbols would need to be
reconfigured to get the improvement.
2.2.2.6 Support for System Auditor's Alarm Shelving

Utility (ASU)
Control HMI now supports alarm shelving through the System Auditor Alarm
Shelving Utility (ASU). Use the Framer to configure connection to ASU. Refer
to B0xxxxx for information on System Auditor and ASU. Refer to B0750xx
for information on configuring ASU in Framer for Control HMI.
2.2.2.7 Control HMI Menu Enhancements

A Framer setting has been added to adjust the length of time before a menu in
Control HMI is closed. This setting can be adjusted to help prevent the closing
of menus when the cursor is unintentionally moved off the menu.
Framer now has the ability to configure permissions on the following features
in Control HMI:
• Tools Menu
• Window Navigation
• Window Redirection
• Show Detail Display

14 2. New Features
• Show Source Info
2.2.2.8 Alarm DB Logger as a Service

Control HMI now supports the Alarm DB Logger running as a service. This
requires a change in the alarm query syntax. For existing systems, Control
HMI automatically updates the Alarm Queries that are configured in Framer.
New format:
\\<stationID>:0\<alarmprovider query>
Example:
• Legacy: \\AWWP01:\IASeries!$System
• New: \\AWWP01:0\IASeries!$System
If you are using the InTouch Almgrp.ini file to configure custom queries, you
need to update the custom alarm queries manually.
2.2.3 Field Device Manager v4.0

For v4.0, the Field Device Manager has been updated to support safety-related
HART field devices - that is, devices that are connected to a safety system
(such as Triconex) and support the directives in IEC61511-1 (2016) - as well as
providing new tools for HART device commissioning and replacement. These
include the Intelligent Commissioning wizard and HART device replacement.
2.2.3.1 FDT 2.0 Compliant Frame Application

The Field Device Manager Frame Application in FDM v4.0 is Field Device
Technology (FDT) v2.0 compliant, and supports FDT v2.0 Device Type
Managers (DTMs). FDM v4.0 provides the option to run FDT1.2.x DTMs and
FDT2 DTMs in a separate process from ArchestrA IDE or in the same process
as ArchestrA IDE. Refer to B0750CM for recommended settings.
2.2.3.2 Intelligent Commissioning

The Intelligent Commissioning wizard allows you to auto-detect HART
devices physically connected to an FBM and create and commission them
from a single wizard. The Intelligent Commissioning wizard centers on
improving the speed and quality of site commissioning activities. It reduces in
the level of manual checking and commissioning in plant setup, and improves
startup times and cost on greenfield projects. It can be used on both safety and
non-safety HART devices.
2.2.3.3 HART Device Replacement

Hart Device Replacement wizard allows you to upgrade a HART device
instance in the galaxy database to match the replaced physical device on the
channel without disrupting the process.
Template cloning allows copying a default set of parameters from an old
template to a new template to be used for like device replacement (upgrade to a
newer version of the same device) as well as for like-unlike device

2. New Features 15
replacement (replace a device from manufacturer A with a device from

manufacturer B).
This feature is described in detail in Using HART® Instrumentation with the
Foxboro Evo Process Automation System (B0750CM).
2.2.3.4 Safety Instrumented System (SIS) Write

Permission for HART Instruments
A new security user role and group called “SafetyInstrumentEngineer” is
added to manage HART instruments connected to safety systems. Only users
belonging to the “SafetyInstrumentEngineer” group or with the
“SafetyInstrumentEngineer” role are allowed to make changes to HART
devices marked as safety-related. Only these users are allowed to change a
device from safety to non-safety or vice versa. This is described in detail in
Using HART® Instrumentation with the Foxboro Evo Process Automation
System (B0750CM).
2.2.3.5 HART DD Library Install with Field Device

Manager
The HART DD library from HART Foundation is packaged with Field Device
Manager and installed on the system under the \HCF\DDL\Library folder
under the HART install location. Example:
D:\Program Files\Invensys\InFusion\HartSupport\HCF\DDL\Library
If the latest version of DD is not available on the local system, obtain the DD
files from the manufacturer or HART Foundation and copy to a readable drive.
2.2.4 Wonderware System Platform 2014 R3 New

Features
2.2.4.1 Advanced Number Format Styles

The Configure Galaxy Style Library dialog box includes the Format Styles tab
with options to individually configure Galaxy-wide number format styles for
common types of numbers used in industrial applications. The Format Styles
dialog box also includes fields to specify characters that appear during run time
that indicate bad quality data or data that exceeds a fixed width field. Based on
the selected number style, the fields appear on the Format Styles dialog box to
change the default properties of number styles.
Each global number style is assigned a unique name, which cannot be changed.
A number style can be applied by name in design time and run time for an
analog data type in User Input and Value Display animations. Also, grouped
elements support global number styles.ArchestrA Graphic Toolbox in
WindowMaker
InTouch WindowMaker incorporates the ArchestrA Graphic Toolbox
containing a full complement of ArchestrA symbols and Situational Awareness
Library symbols. To add a symbol to a Modern or managed InTouch

16 2. New Features
application, drag a symbol from the WindowMaker's ArchestrA Graphic

Toolbox and drop it into an InTouch window.
2.2.4.2 Modern InTouch Applications

Not compatible with Control Software.
2.2.4.3 Conversion of InTouch Windows to ArchestrA

Symbols
You can convert the windows of a managed InTouch application to ArchestrA
symbols. The converted ArchestrA symbols appear in the WindowMaker
ArchestrA Graphic Toolbox and the ArchestrA IDE Graphic Toolbox. In
addition to graphics that appear in windows, all InTouch animation links
embedded in windows are converted to the corresponding ArchestrA
animation.
After conversion, the original converted InTouch window is backed up. A new
InTouch window is created in the InTouch application, which embeds the
newly created ArchestrA symbols.
Note Conversion is not 100% and needs manual work to replace unsupported
functionality
Note Converted Graphics do not support the use of Quick Functions and
other native InTouch Functions.
Note Control HMI InTouch tags also are not converted properly. These tags
have dashes in the tag name which are interpreted as Math calculations.
Control HMI tags must be wrapped in the Attributes("") function. For
example: Attributes("InTouch:ZHMI-Select-IO-CBP")
Note Converted animations are one for one, and may not be the most efficient
way to implement the same functionality as a native ArchestrA Graphic.
2.2.4.4 Additional Situational Awareness Library

Symbols
System Platform 2014 R2 includes additional new Situational Awareness
Library symbols for alarms, trends, and valves:
• Alarms – Not compatible with Foxboro Evo Control Block Alarms
• SA_Alarm_Severity: Displays an alarm summary that includes Alarm
Border animation and alarm counts by severity and acknowledgement
status.
• SA_History_Alarm_Page: Provides a tabbed page to display
historical events or alarms by severity over a specified period.
• SA_Runtime_Alarm_Banner: Displays alarms by area and includes
buttons to acknowledge alarms.

2. New Features 17
• SA_Runtime_Alarm_Page: Provides a tabbed page to display current

events or alarms by severity.
• Trends
• SA_Trend: Displays a trend line of historical and current measured
values and provides Wizard Options to display a grid that includes X
and Y axes.
• SA_MultiTrend: Displays up to four simultaneous trend lines of
current and historical measured values.
• Valves – See Control Software Toolkits
• SA_Valves: Displays a valve symbol with Wizard Options to select
discrete or analog two way or three way valves.
2.2.4.5 Graphic Connectors

A new Connector tool has been added to the Symbol Editor Tools menu. A
connector is a line drawn between graphic elements. A connector starts at a
connection point on one graphic element and ends at a connection point on
another element.
Connectors are particularly useful for complex symbols containing many
connected elements like flow diagrams, industrial piping, or electrical wiring.
Connectors can change length or orientation in response to changes to the
positions of connected graphic elements. Using connectors, graphic elements
within a symbol can be moved, resized, or rotated and still maintain the
connector between elements.
The boundary border around each graphic element includes eight connection
points to attach a connector. The Tools menu includes a Connection Point tool
to add custom connection points on a graphic element. Also, the Tool menu
includes the Control Point tool to add control points on a connector to change
its shape. The shape of a connector can be changed by dragging a line segment
between control points to another position with your mouse.
Important Connector lines do not maintain their horizontal and vertical
orientation with 90 degree angles when connecting to Elements whose X, Y
coordinates are beyond 1280 by 1280 pixels. Instead, the connector reverts to a
straight line between connection points.
To work around the issue and create angled connectors beyond 1280 pixels, it
is possible to select the Elements that you want to connect and use the "Ctrl
Arrow" keys to move the objects below 1280 pixels. From there, add the
connector line and re-select the objects, including the connector, then use the
"Ctrl Arrow" keys to move the elements back to their original position.
2.2.4.6 Historical Statistical Summary Data

Not compatible with Control Software.
2.2.4.7 Alarm Shelving

Not compatible with Control Software Alarm Shelving Tools and Utilities.

18 2. New Features
An Alarm shelving property has been incorporated into Alarm Border

animations. The CSA Alarm border animations have a new property for
indicating if an alarm has been shelved. By default this property is False.
2.2.4.8 Trend Pen Enhancements

2.2.4.8.1 Run-time Scripting
A Trend Pen contains a collection of properties whose values can be modified
during run time to change the visual and functional characteristics of a trend.
The following properties can be modified in a script or User Input animation to
change the following characteristics of a Trend Pen during run time:
• MinValue
• MaxValue
• StartTime
• EndTime
• PlotType
• TimeMode
2.2.4.8.2 Fixed and Line Trend Plots

The Trend Pen control now includes the Plot Type configuration option to
display a trend line as either a Fixed or a Line plot. In Fixed mode, the trend
line is plotted as a horizontal line from a trend data point to the time of the next
data point on the trend's X-axis, and then the trend line is drawn as a vertical
line to the data point. In Line mode, the trend line is plotted directly to each
successive data point within the trend period.
2.2.4.8.3 Trend Time Periods

The Trend Pen control now includes the Time Period configuration option to
set the trend period as either Moving or Fixed. In a Moving trend period, the
start time of a trend period is the current time. The end time is the duration of
the time period from the start time. In a Fixed trend period, the StartTime and
EndTime properties do not change automatically. The default start time of a
trend period is the current time, but the StartTime property can be modified by
a script to set a start time of a trend time period.
2.2.4.9 Enhanced Support of ArchestrA Graphic Wizard

Options in WindowMaker
You can now access and modify ArchestrA Graphic Wizard options when
embedding Graphics in InTouch Windows.
2.2.4.10 Tag Rename Utility

The Historian Tag Rename Utility allows you to rename tags in Wonderware
Historian and preserve the historical data associated with the tags. After

2. New Features 19
renaming, data history of the old tag is linked to the new tag name that you
specify.
1. Before using Tag Rename Utility, verify that the tags are synchronized. If
needed, perform an Undeploy of the Deployed Tags and then perform
“Shutdown and Disable the Historian”.
2. Go To D:\Program Files\Wonderware\Historian\x64 and open
“aahTagRename.exe” using “Run As Administrator”. If you install CS in
C Drive, replace D Drive by C Drive in the file pathname.
3. In the “Connect To Historian Runtime Database”, select the SQL
Server Name and select Windows Authentication and click Connect. This
does not need username and password unlike SQL Authentication in the
drop down.
4. Click Add Tag to select the tag you want to rename and enter the Old Tag
Name and New Tag Name and then click Rename Tags as shown
Figure 2-1.
Figure 2-1. Rename Tags
5. If the tag renaming is successful, the results are displayed as shown in.
Figure 2-2. Tag Rename Results
6. Perform “Enable Historian”.

20 2. New Features

21
C H A P T E R 3
Restrictions
This chapter describes the restrictions while using the Control Software v7.1.
These restrictions are limitations put in place temporarily, to address
incomplete functionality or features of the product. If these restrictions are not
understood, they could potentially allow you to access or generate corrupt data,
or result in abnormal installation or termination of the Control Software v7.1.
Contents
• Access Manager v7.1
3.1 Access Manager v7.1

The restrictions while using Access Manager v7.1 are detailed in this section.
3.1.1 DI Object
The Device Integration Object installed by default does not support the OPC
and SuiteLink interfaces. The systems that require either the OPC or SuiteLink
interfaces additionally need the OPC Device Integration Object to be installed.
Refer to Access Manager User’s Guide (B0750AD, Rev. K or later) for more
information on this Device Integration Object.

22 3. Restrictions
3.2 Control Editors v7.1

This section presents a list of restrictions dealing with the Control Editors.
Some of these restrictions are further detailed as issues in Chapter 5, “Known
Issues and Workarounds”.
3.2.1 Preventing Multiple Users from Performing

Bulk Operations
The following bulk operations automatically prevent multiple users from
performing them concurrently:
• Bulk Generate
• Bulk Create
• Import/Export
• Cascade deployment and undeployment of entire controllers and
equipment units
• Refresh History and Security data
While these operations are in effect, no additional bulk operation is allowed to
be initiated. If a bulk operation is blocked, you have only the following
options:
• Cancel the bulk operation.
• Allow the bulk operation to begin automatically as soon as the current
bulk operation finishes.
Similarly, you are prevented from performing a deployment while the Refresh
History and Security function is being performed.
3.2.2 Synchronizing Block and Compound

Deployment Status
The Control Editors allow you to synchronize the deployment status of blocks
and compounds in the Galaxy with what is actually running on the control
station.
For additional details, Refer section “Synchronize DBs” under “Deployment
Utilities” in Control Database Deployment User’s Guide (B0750AJ, Rev. L or
later).

3. Restrictions 23
3.2.3 Synchronizing ArchestrA and Control Block

Deployment Statuses
The Control Editors allow you to set the ArchestrA and control block
deployment statuses in case the ArchestrA and control block deployment
statuses are not synchronized.
Under normal operating conditions, you need not use this utility. However,
under certain adverse conditions, such as a power failure during deployment or
undeployment, an out-of-synchronization condition can occur. In these
conditions, you are required to use this utility.
For instructions to use this utility, see the section “Synchronize Deploy Status
(Changing a Deployed State)” in Control Database Deployment User’s Guide
(B0750AJ, Rev. L or later).
This utility does not actually perform deployment or undeployment. It simply
changes the status of those operations to match the status you select.
3.2.4 Deploying Platform Objects

If any issues arise when deploying Platform objects, verify whether all the
Platform objects have been checked in. If necessary, you can override the
check-out operation in the Control Editors and redeploy the Platform objects.
3.2.5 Integrated Control Configurator (ICC) and

Control Editors Tools Coexistence
The Control Editors support the coexistence of ICC and Control Editors in the
same configuration. A controller that is being managed by the Control Editors
must not be modified by any other configurator, or database synchronization
issues may occur. To help prevent synchronization issues, a safeguard has been
implemented to help prevent the user from using the wrong configurator.
During installation, the program Safeguards.exe is installed on the Galaxy
Repository server in the directory location referenced by the environment
variable SGDBPATH, which is normally set to C:\Program
Files\Invensys\InFusion\CommonComponents\Safeguards\. This executable is
actually a service responsible for distributing information in the form of a file
to all workstations, allowing the ICC to know to which control stations it is
kept from deploying.
There are two files on the Galaxy Repository server in the C:Program
Files\Invensys\InFusion\CommonComponents\Safeguards directory that you
need to edit manually: IDE-CP and SGSettings.dat.

24 3. Restrictions
The IDE-CP file is transferred to the \usr\fox\sp\files directory of the CP host

specified in the IDE-CP file. Then, the file is renamed to “IACC-CP”. Each
line in this file consists of three tab-separated fields:
a. Controller letterbug
b. Controller host letterbug
c. Controller host IP address.
You can edit this file with the Notepad application, or a similar editing
mechanism. Lines in the file that begin with a pound sign (#) are taken as
comments, and ignored.
Example of the IACC-CP file:
IACC-CP is read by ICC, ICCAPI, and the ICCAPI driver task to help prevent
users from deploying to these controllers. This, in turn, helps prevent other
processes such as FoxCAE™ software and scripts from modifying control
logic on those control stations as well.
The SGSettings.dat file is used by Safeguards.exe to specify the time interval
that IDE-CP is to be distributed to the target workstations, and whether or not
messages generated by Safeguards.exe are logged. This file may also be edited
with the Notepad text editor.
The time interval should be specified in whole minutes on the line immediately
following the [INTERVAL] tag. When given, Safeguards.exe distributes the
IDE-CP every “n” minutes to each workstation specified in the file. Files are
distributed using File Replication Services (FRS).
The specification as to whether or not log messages from Safeguards.exe are to
be captured should be entered on the line immediately following the
[LOGMESSAGES] tag. If turned on, the messages generated by
Safeguards.exe are written to the file Safeguards.log.
Example of SGSettings.dat:

25
C H A P T E R 4
User Notes
This chapter presents user notes for the Control Software v7.1.
User notes contain information about how the product functions and other
helpful hints that may not be evident from the product’s associated user guide.
User notes also contain issues that the users need to be aware of when using the
products. These issues may be due to limitations in the functionality in this
release. If applicable, instructions to work around the issue are also provided.
For the user notes from releases prior to Control Software v7.1, refer to:
• Control Software v7.0 Release Notes (B0750SS)
• Control Software v6.3 Release Notes (B0750SM)
Contents
• General
• Using the Control Software Without an Active Network Connection
• The Control Software Installation v7.1
• Access Manager
• HART
• FOUNDATION fieldbus
• PROFIBUS
• Galaxy Server
4.1 General
4.1.1 General Performance

When running on a Windows 10 or Windows Server 2016 system, some
operations in Control Editors will experience performance degradation as
compared with earlier versions of Control Software. This degradation has been
confirmed with Microsoft, and is expected when combined with end point
protection.

26 4. User Notes
4.1.2 Verify NIC Card Binding Order

For any configuration installed, verify the NIC Card Binding Order.
For more information, refer to section “Off-ControlNetwork Control Software
Server Considerations” of Chapter 2: Sizing and Performance of Foxboro Evo
Process Automation System Deployment Guide (B0750BA)
4.1.3 Virus Scanning Guidelines

After installing Application Server, if ePO is not being used, you need to
configure your antivirus software to help prevent archive files from being
scanned. Unless you configure your antivirus software to help prevent it from
scanning the archive and other files, the performance of Control Editors may
be slower.
The antivirus software should not scan files in the following folders (verify
that subfolders of the listed directories are also excluded from the scan):
• <drive>:\Program Files\ArchestrA\
• <drive>:\Program Files\Common files\ArchestrA\
• <drive>:\Program Files\FactorySuite\ (may not exist in newer
installations)
• <drive>:\Program Files\Invensys\FieldDeviceManager\DDBin
• <drive>:\Program Files\Wonderware\
• <drive>:\InSQL\Data\
• <drive>:\Documents and Settings\All Users\Application Data\ArchestrA
• For Application Server Platform objects:
• History Store Forward directory (if not default or blank)
To find this directory, open each Application Server Platform editor and
look for the History Store Forward directory.
• For Application Server Engine objects:
• Checkpoint directory location (if not default or blank)
• InTouch Application folder path:
• <drive>:\Documents and Settings\All Users\Application
Data\ArchestrA\
• <SMCLoggerStoragefilepath>:
• The default is <drive>:\Documents and Settings\All
Users\Application Data\ArchestrA\LogFiles\. This value is
configured in the SMC Log Viewer.
• SQL Server database files of type:
• .mdf
• .ldf

4. User Notes 27
To exclude these files from antivirus (McAfee® is shown as an example)

scanning, follow these steps:
1. Click Start > Programs > McAfee > Virus Scan Console.
2. Right-click On-Access Scanner and select Properties.
3. Click All Processes, Detection, and Exclusions.
4.1.3.1 Disabling and Enabling McAfee Endpoint

Security (ENS) Software
To disable or enable the virus scanning software McAfee ENS, refer to
Appendix F of the Control Software Installation Guide (B0750RA, Rev. Z).
4.1.4 Creating Virtual Memory Page Files

For better performance of the Control Software, it is recommended that you
create a Windows Virtual Memory Paging file on the D: drive.
4.1.5 Use of Non-ASCII Characters

The Control Software does not support the use of non-ASCII characters. There
are several areas within the product where non-ASCII characters can be
entered, but the use of these characters is not recommended.
4.1.6 FoxCTS v7.00.00

You must install the FoxCTS quick fix QF1330385 to run FoxCTS v7.00.00
with Control Software v7.0.
If you are running FoxCTS v7.01.00 or later, no quick fix is required.
4.2 Using the Control Software Without an

Active Network Connection
The Control Software requires an active network connection to function
correctly. If it is used on a system without an active network connection
(connected to a working network), it is necessary to install the Microsoft®
Loopback Adapter to help ensure proper operation and access full
functionality.
4.2.1 Install Microsoft Loopback Adapter

1. Click the Start button and click Run…
2. In the Run dialog, type hdwwiz.exe and press Enter.
3. In the Add Hardware dialog box, click Next.
4. In the What do you want the wizard to do? list, click Install the hardware
that I manually select from a list (Advanced), and then click Next.

28 4. User Notes
5. In the Common hardware types list, click Network adapters, and then
click Next.
6. In the Manufacturer list, click Microsoft.
7. In the Network Adapter list, click Microsoft Loopback Adapter
(Win2008/7) or Microsoft KM-TEST Loopback Adapter
(Win2016/10), and then click Next twice.
8. If a message about driver signing appears, click Continue Anyway.
9. In the Completing the Add Hardware Wizard dialog box, click Finish,
and then click OK.
4.3 The Control Software Installation v7.1

This section contains installation user notes for the Control Software v7.1.
4.3.1 Off-Mesh PDC/SDC Must Have Galaxy IP

Address in HOSTS File
After the Control Software installation on an Off-Mesh PDC or SDC (that is,
installed on a network other than The Mesh control network), verify that the
PDC or SDC have the Galaxy Repository station’s IP address in their HOSTS
file. This file is located in %systemroot%\system32\drivers\etc\.
If you need to edit the HOSTS file to add this IP address, run Notepad or your
other text editor as administrator.

4. User Notes 29
4.4 Control HMI v7.1

This section contains user notes for the Control HMI Application.
4.4.1 Alarms not appearing in migrated HMI

Alarm Panels
Issue: The alarm query syntax supports Alarm DB Logger to run as a service
and receive both ArchestrA and InTouch Messages. Alarm queries that are
configured in the InTouch Almgrp.ini files do not return any alarms.
Description: Users that use the InTouch Almgrp.ini file to configure large
alarm queries, need to update the alarm queries in the ini file. Control HMI
updates all Framer configured alarm queries but does not have access to the
Almgrp ini file.
Workaround: Add the session 0 identifier to all alarm queries in the almgrp.ini
file
Example:
• Legacy: \\AWWP01:\IASeries!$System
• New: \\AWWP01:0\IASeries!$System
Refer to the Framer and Alarm Management User's Guide (B0750AR) for
more details.
4.4.2 Quality Style for OOS on Migrated Systems

The default ArchestrA Graphic Indicator for Out-of-Service does not match the
default InTouch Indicator of "*"
System Platform 2014 R3 supports advanced text formatting. On migrated

systems, the default Element Style settings are not imported as they can
overwrite user modified settings. For this reason, the default indicator for OOS
does not match the Control HMI InTouch setting for OOS.
You need to open the ArchestrA Style configuration Dialog and set the OOS
character. Refer to Control Software 7.0 Migration Considerations in the
Control Software Installation Guide (B0750RA).
4.4.3 Managed Control HMI
4.4.3.1 Bulk Graphics Editor (BGE) Default Workspace

Path has Changed
When updating from Control Software 7.0, the default workspace path has
changed from c:\Programdata\BGE to c:\Users\Public\BGE.In some cases the
access to files under the Programdata folder can be limited and the files made
READ-ONLY. This helps prevent BGE from properly creating or modifying
files in the folder.

30 4. User Notes
Users that currently use the Programdata folder can continue to do so, but be
aware that the folder can be made READ-ONLY by the operating system. The
recommendation is move files to the User\Public folder. This may require
existing BGE scripts to be modified. The alternative is to make sure the folder
is accessible by the current BGE user.
4.4.3.2 BGE Update Links shows SMC error messages

on Windows 10 and Server 2016 stations.
. When running Update Links within the BGE tool for a Galaxy installed on
Windows Server 2016 or Windows 10, several LMX errors may be logged in
the SMC log file. These errors from WWFS object and Proxy Manager Poll
Package have no impact on the system or the BGE Update Link operation and
can be safely ignored These errors and warnings have no impact on the system
or the BGE Update link operation and can be safely ignored.
4.4.3.3 Long Running Script Behavior on Windows 10

and Server 2016
The operating system treats an application as not responsive it does not receive
any updates from the application every 5 seconds. There are conditions within
Control HMI where the application may not respond to the operating system
within the 5 second limit. This causes the OS to mark the application as “non-
responsive”. If this condition occurs in Windows 7 or server 2008, the HMI
remains visible even though the application is not updating. For Windows 10
and Server 2016, the application window will become black until the
application returns to a responsive state. On all operating systems, when the
application returns to a responsive state, the window automatically, resumes
normal updates.
The Control HMI application has been modified to minimized these events.
There are several known conditions that may still cause the blackout event
(and there may be other conditions depending on the implementation of the
Control HMI):
• Very large HMIs with 1000's of windows may cause the Window
Browsers Refresh action to take longer than five seconds.
• Historian and Scratchpad Trends with Server connection timeouts that are
greater than 5 seconds will cause a blackout condition if the Historian
Server connection is lost while the trend being displayed or is opening.
Invalid server names will also cause the blackout.
The recommendation is to make sure that Historian Server connection timeouts
be set to 5 seconds. This should be done in Framer as well as any custom
scripts or configurations.
The Control HMI startup has also been modified to allow the end-users to
adjust the amount of time that it takes Windows 10 or Server 2016, to flag all
applications as not responsive. This only adjusts the amount of time before
Windows blacks out the screen. The current setting is 10000ms (10 Seconds).
Users can adjust the setting by modifying the HungAppTimeout setting that is
located in the InTouch Global Win.ini file:
C:\Programdata\Wonderware\InTouch\win.ini

4. User Notes 31
4.4.3.4 Users Denied Access to WindowMaker

Application Folder
There are occasions where files need to be added to the InTouch Application
Folder structure. WindowMaker provides a selection under the File menu to
open a File Manager window directly to this folder, so that files to be
associated with the applications can be managed. However, the security
settings on the workstation or sever may keep WindowMaker from opening the
file management window. If this happens you need to manage this folder from
the Galaxy Repository server using this procedure.
1. Make sure the application is Checked out by using an administrator
account with the proper privileges.
2. From the GR Server station, open Windows Explorer.
3. Browse to the Checked Out folder:
D:\Program Files\ArchestrA\Framework\FileRepository\<Galaxy
Name>\ObjectFileStorage\$ControlHMI_v71\CheckedOut
4.4.3.5 Control HMI Secured by Default

The Control HMI default security settings are enabled with Galaxy security set
as the default security mode. Users that migrate from Control Software v6.x or
earlier, may find that the security is now enabled. This happens if Framer
Configurations settings have never been modified. Users who have custom
Configuration settings are not affected.
To undo the security setting:
1. Open the Framer application from WindowMaker's Special drop-down
menu.
2. Navigate to Framer's Property Configuration view.
3. Clear ArchestrA Security Setting.
4. Set ArchestrA Security Authentication to None.
5. Click Save and exit Framer’s Property Configuration view.
4.4.3.6 Managed InTouch Application Deployment

Managed InTouch applications must be compiled when they are deployed to
workstations. This includes the need to be compiled the first time it is deployed
during installation. This is different from the standalone application where all
the windows are precompiled.
Deploying changes to the application instances may require re-compilation of
the application. To help prevent the entire application from a complete re-
compile, you should test the modifications by using the Runtime fast switch in
WindowMaker. This opens a local instance of the application and compiles all
the changes.
Note Do not log off or reboot the workstation when deploying the managed
Control HMI Application, until the application file transfer is complete.
Deploying the managed Control HMI application works differently than other
deployment workflows. The Control HMI deployment quickly reports that

32 4. User Notes
deployment is complete. However, there is a file transfer that must complete

before it is fully deployed. This file transfer can take several minutes
depending on the system and network performance. Any interruption to the file
transfer causes the deployment to abort and require a re-deployment of the
Control HMI application. The instance icon in IDE shows a clean deployment
icon when the file transfer is completed.
4.4.3.7 ArchestrA Graphic Alarm Border Aggregation for

Control Block State Alarms
ArchestrA Graphic Alarm Border Aggregation for control blocks do not show
the Inhibit status of state alarms. There are different types of control blocks
that can have one or more state alarms. The control blocks do not provide
enough details to identify which state alarm has the highest priority and which
state alarm is inhibited. To help prevent potentially hiding active alarms, the
alarm aggregation function does not process or display inhibit status of State
alarms.
4.4.3.8 Managed Control HMI Detail Displays

The managed Control HMI application contains three sets of Detail Displays.
This can be increased to eight sets. Refer to “Restoring Faceplates to Managed
Control HMI” section in the Windows Construction User’s Guide (B0750AS).
4.4.3.9 Managed Applications Do Not Use Network

Application Development
Network Application Development (NAD) is not used to deploy and create
Client or TSE client copies of the managed application. The managed
application is deployed to client stations using the ArchestrA deployment. TSE
client copies are automatically created when clients log into a Terminal Server.
Refer to the chapter “Managed Control HMI” in the Foxboro Evo Process
Automation System Deployment Guide (B0750BA) for more information.
NAD is still used to manage standalone applications.
4.4.3.10 References to IADAS

All runtime tag references within InTouch to Control blocks are prefaced with
“IADAS”. The keyword “IADAS” is an indication to InTouch and the
Message Exchange (MX) subsystem that the reference should be directed to
the I/A Series DI Object installed on the local workstation.
For references within InTouch Application windows, this reference looks like
this:
Galaxy:IADAS.COMP.BLK.PARAM
For references within ArchestrA Graphics or ArchestrA scripting, the
references looks like this:
IADAS.COMP.BLK.PARAM
In order to satisfy object reference validation within ArchestrA Graphics and
ArchestrA scripting, a placeholder DI Object named “IADAS” has been

4. User Notes 33
included in the Control Software Galaxy. This object should remain

undeployed.
4.4.4 Control HMI Resolution

Control HMI is shipped with Widescreen 1920x1080 resolution. It can also be
edited and configured to run in Legacy 1280x1024 resolution without forcing
the application to be converted to the lower resolution.There is a minor
performance impact when InTouch/Control HMI runs in a resolution that it is
not compiled to. For example, running the Widescreen application in Legacy
mode without first converting it to the new resolution, forces the runtime to
compile the windows each time they are opened in the lower resolution. This
can add a second to the time it takes to open the window.
4.4.5 Platform Redeployment May Cause Control

HMI InTouch to Not Display Alarms
There are situations where workstations do not process control block alarms.
Also, error messages are displayed when the WindowViewer and
WindowViewer are started.
Issue: Platform Redeployment may make InTouch the default Alarm Provider and
Control Core Service alarm message no longer appear in the HMI Runtime
Alarm Panels.
Description: When redeploying a workstation platform, reboot the workstation to help
ensure proper process startup.
4.4.6 Features Not Recommended for Use with

the Control Software
Do not use these InTouch features with the Control Software.
Issue: Application resolution scaling:

Description: InTouch allows you to configure application resolution scaling from within
WindowMaker. The Control HMI should always have the Lock Window
Size option selected. For more information, refer to page 19 in the InTouch®
HMI Documentation Addendum, ITAddendum.
Note Do not clear this option and rescale the Control HMI application, as all
InTouch windows will be rescaled. The only way you can restore the
application is by restoring your backup copy.
Note This setting does not keep you from changing the resolution of the
overall application. It only helps prevent the windows from rescaling when
the application resolution is changed.

34 4. User Notes
Issue: Run-time Tag Viewer:

Description: This is not recommended for Operators, as it allows full read and write access
to all InTouch tags used by the Control HMI. For information, refer to
InTouch® HMI Documentation Addendum.
Issue: WWheap /3GB switch for 32-bit Windows Operating system:

Description: This is not compatible with the I/A Series or Control Core Services systems.
Issue: WindowViewer Memory Caching of specific Windows, and ArchestrA

Graphics:
Description: This feature cannot be used with Control HMI, as ramping of control values
is not supported. The initial ramp action will drive the value to 0, regardless
of the actual current value.
In addition, cached runtime values are displayed when a cached window is

first opened. These values are not live and may cause an Operator to take
action that is not correct.
NOTICE
POTENTIAL DATA LOSS
The WindowViewer feature cannot be used with Control HMI. Data

values will be ramped incorrectly.
Failure to follow these instructions can result in data loss.
4.4.7 General Notes
Issue: AlarmDB login credentials

Description: The AlarmDB panel ignores the login and user actions for several minutes if
the login credentials for the AlarmDB panel are not configured properly with
the Framer software. The control takes several minutes to scan the network if
the ServerName does not exist or is disconnected from the network. This also
happens if the AlarmDB Logger Manager is not running on the configured
server.

4. User Notes 35
Issue: Data quality processing within the Control HMI windows (non-managed
Application)
Description: The standard WindowMaker primitives and wizards do not include data
quality handling. Initial data values for these objects are displayed as “0”,
until live data values are received from the field. This could cause confusion
if data entry or ramping operations are performed immediately when a
window is opened without waiting for data values to be received from the
field. The Control Edition SmartSymbols provided with the Control HMI
contain data quality handling that helps prevent data entry or ramping until
the data values are received from the field.
Workaround: To use these SmartSymbols, follow the required steps detailed in Window
Construction User’s Guide (B0750AS) concerning InTouch tag creation and
window scripting. You can also create customized SmartSymbols that
include data quality handling, using the Control Edition SmartSymbols as a
guide.
Issue: Reviewing the SMC log files to verify correct window configurations
Workaround: When validating configured windows, use the SMC Log Viewer to verify
correct window configurations. Verify that there are no misconfigured tag
names reported in the log.
Issue: Transitioning between runtime and development modes

Description: The recommended way to work with WindowViewer™ software and
WindowMaker software is to use the Runtime! and Development! buttons at
the top right section of the application windows. The Control HMI does not
contain the default Development! button, but instead provides a DEV button
to the left of the Minimize button that provides the same functionality as the
Development! button. Use the Runtime! and DEV buttons to fast switch
between WindowViewer software and WindowMaker software. When
returning from the development mode, the menu and status bars are missing
from the WindowViewer window. Select the RUN button in the same
location as the DEV button to open the menu and status bars again.
Workaround: If an error occurs in either WindowViewer software or WindowMaker
software, exit both WindowMaker and WindowViewer software and restart
WindowViewer.
Issue: Rotated text

Description: When building process graphic windows with the Control HMI
WindowMaker software, avoid having the dynamically updating objects
overlap or intersect with the rotated text objects as this may affect the overall
performance of WindowViewer.

36 4. User Notes
Issue: Multiple monitors

Description: If the InTouch software is running on a multi-monitor system, the Control
HMI must be displayed on the first monitor, which is generally the upper left
monitor.
Workaround: Refer to Foxboro Evo Process Automation System Deployment Guide
(B0750BA) for information on how to configure multiple monitors.
Issue: The spaces in the names of Alarm Object are not supported.
Description: When creating Alarm Object names, the IDE allows spaces in the name, but
this is not supported by InTouch software’s Alarm Viewer Control.
Issue: The permission configuration within the Framer software only applies when
ArchestrA security has been turned on.
Description: When ArchestrA security is turned on, the property Using ArchestrA
Security needs to be set to True (checked) in the Configurations Property in
order for the Permissions settings to take effect.
Workaround:
Issue: Changing passwords in Control HMI

Description: The Change Password dialog box in the InTouch software allows you to
enter a password that is greater than 14 characters. This password is accepted
in InTouch, but is not legal when logging into the Control Editors when
security is set to Galaxy.
Workaround: If an incorrect password is configured, log into InTouch and change the
password to conform to the 14-character limit. In addition, you need not
change a password in InTouch if the current password is blank. Use the
Control Editors to change blank passwords.
Issue: Entering passwords for Secured and Verified Write dialog boxes
Description: The maximum length of an ArchestrA password is 14 characters if the
Galaxy security mode has been selected. The Secured and Verified Write
dialog boxes accept more than 14 characters, even though passwords are only
14 characters in length.
Workaround:
Issue: Authentication mode changes

4. User Notes 37
Description: Authentication mode changes at the IDE do not take effect in the Control
HMI until the next user logs in.
Workaround:
Issue: Starting Windows Explorer software from the Control HMI on Terminal
Server
Description: When starting Windows Explorer from a Terminal Services or Remote
Desktop Services session, the Windows Manage Your Server dialog box
may appear.
Workaround: You need to exit the window and restart Windows Explorer.
Issue: Unsupported characters in user names

Description: The characters caret (^) and ampersand (&) are not supported within user
names in the Control HMI. User names with these characters cannot save
Favorites from the File menu and temporary alarm panel queries.
Workaround:
Issue: No InTouch feedback when compound on or off is rejected for security

Description: If you do not have permission to turn a compound on or off due to security
settings, no feedback is available in InTouch.
Workaround: Refer to the SMC Logger to view security information.
Issue: Large Fonts should not be used.

Description: If large fonts are configured in the Control Panel Display Properties of the
workstation, a gap between the Control HMI title bar and the menu windows
appears as the title bar is not displayed in its correct size.
Workaround:
Issue: Updating values are placed off scan when the Control HMI is minimized.
Description: The tags are taken off scan when the Control HMI is minimized. This means
that when the Control HMI is opened (restored), values may initially appear
as out-of-service until the tags are on scan again. This also means that trends
displaying real-time data does not update and the data value is ‘0’ for all trend
pens while the application is minimized.
Workaround:

38 4. User Notes
Issue: Wonderware Historian Client trend data may appear unreadable if the trend is
viewing data across a change to Daylight Saving Time (DST).
Description: A Wonderware Historian Client trend that is 10 minutes in length shows an
extra hour of data when looking at a 10 minute time range from 12:55 am to
1:05 am during the Daylight Saving Time change. There is an extra hour of
recorded data during this time range when the clock is cycled back an hour.
The Wonderware Historian Client trend does not write over the existing time
data, but creates a parallel set of time data.
Workaround:
Issue: The Control HMI cannot be opened if the software is minimized while the
Security dialog box is open.
Description: Do not minimize the Control HMI window while the Secured or Verified
Write dialog boxes are open. Under these conditions, the Control HMI
cannot be restored or maximized.
Workaround: If this situation occurs, terminate the Control HMI using the application:
C:\Program Files\Invensys\InFusion\View\Tools\viewRestart.exe.
Issue: Wizards and Window Controls such as the combo box control, reference
placeholder tags appear after Control HMI windows are imported into a new
Control HMI Application.
Description:
Workaround: To remove the placeholder tags do the following for each custom window
that contains these controls:
1. Open WindowMaker software.
2. Open the window(s) with Wizards or Window Controls.
3. Select all the objects (F2).
4. Edit all the tags (Ctrl-E).
5. In the Substitute Tagnames dialog box, click Convert.
6. Click Save and then close the window.
Issue: Control HMI windows shift after the software has been minimized.
Description: After the Control HMI has been minimized and restored, window locations
are shifted by a few pixels.
Workaround: On the menu bar click View and then select Restore Window Position to
restore window locations.

4. User Notes 39
Issue: When a large alarm database is restored and you use the default predefined-
query to view the alarms from last 30 or 90 days, Control HMI displays an
“Out of memory” error.
Description: In case a pre-defined query, such as “Last 30 Days” or “Last 90 Days”,
returns an “AlmDbView Control - Out of Memory” error.
Workaround: Edit the query dates in the editable time fields to reduce the query duration to
a period of 20 days or less.
Issue: WindowMaker requires users to have “Admin” privileges under Windows 7

and Windows Server 2008 R2 Standard operating systems.
Description: Wonderware InTouch supports User Account Control (UAC)-enabled run-
time operations without elevated privileges. For the configuration and
installation operations, including those called during run-time operations,
User Account Control must be disabled or privileges must be elevated to the
required level.
If WindowMaker is open and you start WindowViewer without
administrative privileges, WindowMaker and WindowViewer will crash with
OUT OF MEMORY error dialog boxes appearing multiple times.
Workaround: This means that WindowViewer does not require Admin privileges to run. If
you need to run WindowMaker or the InTouch Configuration Tool, you must
always invoke WindowViewer with the “Run as Administrator” option or
disable UAC.

40 4. User Notes
4.4.8 I/A Series/Control Core Services Alarm Field

Conversion to InTouch or Control HMI Alarm
Format
The following table lists the fields within an I/A Series/Control Core Services
alarm message, and the corresponding field within the InTouch or Control
HMI alarm record. As there are more I/A Series or Control Core Services
alarm message fields than InTouch/Control HMI fields, in some cases an
InTouch/Control HMI alarm field contains two I/A Series/Control Core
Services alarm message fields. Also note that in some cases, the column in the
Control HMI Alarm Panel has been changed to reflect the data this is contained
within the InTouch alarm record.
Operator Domaine
Alarm Comment
User Full Namef

Operator Node
Operatord
User 3g
Priority
Classb
Group
Timea
Name
Typec
Value
Limit
Alarm Fields
I/A Series/Control
Core Services alarm
fields
Type X
Date Time X
Letterbug X X
Compound Name X
Block Name X
Point Name X
Point Number X
Sct. Number X
Opr. Error X
Parameter Name X
Priority X
Step X
Subroutine X
Sbx. Number X
Alarm Value X
Alarm Limit X
Loop Id X
Block Description X

4. User Notes 41
Operator Domaine
Alarm Comment
User Full Namef

Operator Node
Operatord
User 3g
Priority
Classb
Group
Timea
Name
Typec
Value
Limit
Alarm Fields
Message Text All
except
noted in
State
Text
State Text STATE,
BAD,
TRIP
Units X
a. For SOE EVENT messages, the message time tag is preserved to millisecond resolution. This is done by extracting
the SOE time tag stored in the STATE_TXT field of the SOE EVENT message and using it for the message time tag
For other messages, time is accurate up to a tenth of a second.
b. Alarm Class determination is based on Alarm Class/Type table below.
c. Alarm Type determination is based on Alarm Class/Type table below.
d. Operator is the name of the logged-in operator for all messages. For an acknowledged alarm, it is the name of the
operator who acknowledged the alarm.
e. The data is found under the “Description” column in the Control HMI Alarm Panel.
f. The data is found under the “General” column in the Control HMI Alarm Panel.
g. The data is found under the “LoopID” column in the Control HMI Alarm Panel.
The following table lists the Alarm Class and Alarm Type text based on the
I/A Series/Control Core Services alarm type.
I/A
Series/Control
Core Services InTouch/Control InTouch/Control HMI
Message Type HMI Alarm Class Alarm Type
HIABS ANALOG HIABS
LOABS ANALOG LOABS
HHABS ANALOG HHABS
LLABS ANALOG LLABS
HIDEV ANALOG HIDEV
LODEV ANALOG LODEV
RATE ANALOG RATE
BADIO DIGITAL BAD
STATE DIGITAL STATE
INFO INFO MESSAGE SEQ1_INFO
MON MON MESSAGE SEQ2_MON
EXC EXC MESSAGE SEQ3_EXC
IND/DEP IND/DEP MESSAGE SEQ4_INDDEP
CONF CONF MESSAGE SEQ5_CONF

42 4. User Notes
I/A
Series/Control
Core Services InTouch/Control InTouch/Control HMI
Message Type HMI Alarm Class Alarm Type
SEQ6 MESSAGE SEQ6
TRIP DIGITAL TRIP
HIOUT ANALOG HIOUT
LOOUT ANALOG LOOUT
OUTOFRANGE DIGITAL OOR
SPCALM MESSAGE SPCALM
EVENT EVENT EVENT BLOCK SOE
4.4.9 Faceplates
Issue: Starting PLB monitor from faceplates

Description: When you start the PLB monitor from a faceplate window, the application
requires you to reselect the PLB Compound.Block. It does not open to the
ladder page for the selected Compound.Block. Type the name of the
compound in the Compound field to get a list of the blocks in the compound.
Select the requested block from the list.
Issue: Multiple compounds cannot be turned on or off if the.ON parameters have a

Secured or Verified Write status.
Description: If the ON parameter of a compound has been assigned to the Secured or
Verified Write security category, when these compounds are turned on or off,
the Secured and Verified Write dialog boxes are displayed. These dialog
boxes are displayed by the Control HMI. If the dialog box is not visible,
move the Block Select window to enter the authentication information.
Issue: Turning compounds on and off from a terminal server may not change the
state of all compounds.
Description: When turning a large number of compounds on or off from a terminal server
client workstation, not all the compounds may change state. Refresh the
Block Select window, and turn any remaining compounds on or off.
Issue: Downstream error status bit is not shown.

Description: The I/A Series Downstream error status bit is not represented in the display of
data quality information in updating text fields.

4. User Notes 43
Issue: Some boolean parameters that are set up with a secured or verified write
security configuration cannot be modified from faceplates.
Description: One method of changing the value of a boolean parameter in a Control HMI
faceplate is to select the boolean, which enables the Toggle button, then
select the Toggle button. If the selected boolean parameter has been
configured as a secured or verified write parameter, the Toggle button does
not work. This is not an issue for boolean parameters that are directly toggled
through a single button click, that is, selecting the Manual/Auto button will
work even if the corresponding parameter has been assigned a secured or
verified write security status.
Select the Boolean parameter to be toggled. This copies the parameter name
to the tag bar. Open the Watch Panel and assign the selected parameter to the
Watch Panel. Change the value of the parameter to the desired value, either 0
or 1. The Secured or Verified Write dialog boxes will be displayed.
4.4.10 Framer Software

Issue: Permission configuration starts with NoLogon
Description: When configuring Permissions with Framer software for access with Galaxy
Security turned on, the “initial” settings are read from the “NoLogon”
properties. If you have additional Roles configured in the Galaxy, the
properties in each of the configured Roles are added to the NoLogon settings.
If a property is allowed in any Role column for the logged on user, then the
property is allowed. This includes the NoLogon column. For example, if a
property is allowed in the NoLogon column, but not allowed in the Role for
the logged on user, then the property is enabled. If the user has two Roles and
if a property is not allowed in Role1 but allowed in Role2, then the property
is allowed for the user.
4.4.11 Alarm Server

Issue: Playing .wav files associated with a workstation horn to indicate an alarm
condition requires that the workstation is configured with speakers.
Description: If .wav files are to be played to indicate alarm conditions, the workstation
must have speakers (internal or external) for the sound to be heard.
Issue: Alarm tags assigned to navigation and annunciators are case sensitive.
Description: The Alarm Server handles alarm tags as case sensitive strings. When
assigning alarms to navigation and annunciators, the tag names must be
entered in the correct case. This means that I/A Series tag references must be
in capital letters, otherwise the expected alarm notification does not occur.

44 4. User Notes
Issue: AlarmServer default query does not include alarms from the DI Object.
Description: The default Process alarm query includes a reference to the DI Object on the
local workstation: Galaxy!IADI. The IADI portion of this alarm provider
string is replaced with the name of the local workstation’s Device Integration
object, for example, Galaxy!AW0001_IADI. This text replacement is not
done by the Alarm Server. If alarms from the local DI Object need to be
monitored by the Alarm Server, a separate Process Alarm query needs to be
configured for each workstation. Use the Framer software to configure this.
4.4.12 WindowMaker Software
Issue: Use the WindowMaker software Quick Functions Show and Hide or the
Quick Function hmiShowWindow when showing and hiding windows from
animation links. Do not use WindowMaker’s Show/Hide animation links.
Description: Do not use WindowMaker’s animation links Show window and Hide
window. These animation links are not portable between applications and
does not work correctly if the window is imported into another
WindowMaker Application. Show and Hide animation links on imported
windows show and hide an incorrect window within the new application.
Note Importing windows is a required part of the Control Software upgrade

process.
Instead, use the WindowMaker Quick Function Show and Hide or the Quick
Function hmiShowWindow when showing and hiding windows from
animation links.
Issue: SmartSymbol Manager is not displaying SmartSymbols.

Description: Sometimes the SmartSymbol Manager window is blank, even though there are
actually SmartSymbols within the Control HMI. This is caused by invalid
Registry entries. A .bat file can be run to correct this issue. Close the
WindowMaker software, and from Windows Explorer or a Command Tool
window, run the file D:\InFusion\View\Start\FixSymbolBrowser.bat. Start
WindowMaker software again. The SmartSymbols should appear in the
Symbol Manager window again.

4. User Notes 45
4.5 Access Manager

This section contains user notes for Access Manager.
4.5.1 I/A Series Alarm Provider
Issue: The Application Engine that hosts the AlarmProvider should not be modified.
(CAR:1010157)
Description: Do not modify the instance of AppEngine A (the application engine that hosts
the Alarm Provider) installed by the Galaxy Preparation Utility. Use
AppEngine A as an instance of the default application engine. The Alarm
Provider may not behave as expected if the Application Engine is modified.
By default, the Enable storage to Historian option is disabled for an
Application Engine. When this option is enabled, some of the Alarm Provider
installations may experience issues, including inability to operate. This
occurs due to an issue with shared memory related to the I/A Series system
Object Manager (OM) software.
If the Alarm Provider is not functioning due to Historian settings made for the
AppEngine A, follow the steps given below to resolve the issue:
1. Undeploy AppEngine A. The AppEngine A is the application engine
host of the Alarm Provider object.
2. Open the AppEngine A configuration in the ArchestrA IDE.
3. Make sure the Enable storage to Historian option is turned Off.
4. Redeploy AppEngine A.
5. Reboot the workstation. (This step may not be necessary in all cases.)
Issue: There should be at most one I/A Series Alarm Provider per platform. Never
deploy more than one I/A Series Alarm Provider to the same platform.
Description: If you instantiate an I/A Series Alarm Provider and deploy it on a platform
that already has an I/A Series Alarm Provider, the one deployed later is
unable to start up and must be undeployed and unassigned. For successful
undeployment, first reboot the workstation and then undeploy the additional
I/A Series Alarm Provider. After successful undeploy, delete (by pressing the
delete button) the object from the platform. Performing these steps and then
rebooting the workstation should put the workstation in the correct state.
This is by design and it reflects the fact that there may not be more than one
I/A Series Alarm Subsystem on an AW, WSTA70, or WSVR70. This install
process deploys one I/A Series Alarm Provider on every InTouch
workstation.

46 4. User Notes
Issue: The I/A Series Alarm Provider is deployed and the query given in the
InTouch Alarm Panel is correct, but alarms never show up in the InTouch
Alarm Panel.
Description: The APRINT task on a CP has dropped the workstation from its list of alarm
targets after being unable to reach it. In order to resolve the issue, perform the
following steps:
1. Verify that the AW’s, WSTA70’s, or WSVR70’s WP logical name is
specified correctly in the station block's device target list.
2. Reboot the workstation.
This usually resolves the issue. If it does not correct the issue, run
dm_recon.exe by performing the following steps:
1. Open a command prompt and navigate to the D: drive:
D:
2. Navigate to \usr\fox\cs:
cd \usr\fox\cs
3. Run dm_recon.exe:
dm_recon.exe
Alarms generated after the utility has been run should appear in the Alarm
Panel.

4. User Notes 47
4.5.2 I/A Series Data Access Server

Issue: Bit number referencing is inconsistent between the Control Editors and I/A
Series Data Access Server (IADAS).
Description: The Control Editors have to provide the control processor with configuration
information it can understand. All of the pick lists displayed by the Control
Editors, allowing a choice of bits, use the Boolean Connection number as
described in the I/A Series documentation, because this is how the controllers
are configured.
The IADAS uses the Bit Number as described in the I/A Series
documentation, not the Boolean Connection number. Bits are numbered 31 to
0 (MSB to LSB) which is the actual bit number as the I/A Series
documentation shows. No translation to Boolean Connection number is
necessary. However, an extension is required for parsing reasons and
compatibility with InTouch, so #B must precede the bit number.
The cases are:
I/A Bit Number 31 to 0
IADAS Bit Number #B31 to #B0
Boolean Connection B1 to B32
The I/A Series documentation has a table that shows a translation from actual
bit number (31 to 0) to I/A Series Boolean Connection (B1 to B32).
Boolean Connection numbering is not used by the IADAS for several
reasons.
1. ArchestrA/InTouch software uses bit notation 31 to 0 (MSB to LSB).
Since the IADAS is configured using ArchestrA/InTouch tools, IADAS
uses this standard bit notation.
2. The IADAS supports status bit addressing. I/A Series status bits are
addressed (15 to 0). This is consistent with #B bit addressing (the
IADAS also supports mnemonics for status bits, like #sBAD and
#sOOS).
3. The IADAS supports data masks. Bit addressing or masking can be used
and the notation is consistent across 8, 16, and 32 bit data types. The
mask is constructed with standard hexadecimal notation, so #M7 reads
the first 3 bits (LSB), regardless of the data type (8, 16, or 32 bit). In
contrast, if we had used the Boolean Connection numbering scheme,
#M7 would read B30, B31, B32 for 32-bit data types and B14, B15, B16
for 16-bit data types and B6, B7, B8 for 8-bit data types. In this case,
the engineer would have to know the data type (8, 16, or 32 bits) in order
to create the correct mask.
4. No translation from Bit number to Boolean Connection number is
necessary.

48 4. User Notes
Issue: Using the Secured tag extension

Description: When specifying extensions in tag names passed to the DAServer, the #AWS
and #AXS secured option causes all normally writable tags with the same
I/A Series full path name (that is, C:B.P, C.P, or shared variable) to be
“secured” and unwritable, except through the first tag that was added with
that option. Also, if one tag in an #AWS or #AXS group of tags is not
securable, none of the tags in that group receive data or are writable (if they
were not previously present in the IADAS). This is a limitation of the Object
Manager (OM).
Issue: When the I/A Series Data Access Server (IADAS) is stopped from System
Management Console (SMC), IADAS does NOT close the Object Manager
lists in the CPs. (CAR:1011257)
Description: Do not end the IADAS.exe process from the Windows Task Manager or
deactivate Foxboro.IASeries.DAServer.1 from the System Management
Console (SMC) DAServer Manager. Terminating the IADAS in this way
orphans any open Object Manager lists. Instead, to stop the IADAS service,
undeploy the I/A Series Device Integration Object from the Control Editors.
The IADAS service can also be stopped by stopping the “AppE” application
engine that hosts the I/A Series Device Integration Object from the SMC.
4.5.3 I/A Series Device Integration Object
Issue: SMC shows the following error message:

“Failed to convert VARIANT to IA buffer” after adding and deploying “DI”
Object instance under AppEngine.”
Description: The following messages could be generated after a workstation reboot.
“ConvertIATypeToVariantType Unsupported data type. type=0”
“ConvertVariantToIaBuffer Unknown type conversions are not supported.”
“ConvertVariantToIaBuffer Unknown type conversions are not supported.”
“Write to AWKE02ITCMD#FP500 failed. Failed to convert VARIANT to IA
buffer”.
Some of the Control Software components start before the I/A
System/Control Core software starts. Those components are continually
checking if I/A system has started by attempting to write to
<letter_bug>ITCMD shared variable.
When I/A System or Control Core starts up, it creates the shared variable, and
the messages would cease to appear.
Issue: There should be at most one I/A Series Device Integration Object per
platform. You should never deploy more than one I/A Series Device
Integration Object to the same platform.
Description: The I/A Series Device Integration object hosts the I/A Series Data Access
Server (IADAS) and only one IADAS is allowed per workstation.

4. User Notes 49
4.5.4 I/A Series History Provider
Issue: Sometimes the switch over to redundant history collector does not historize
all the history tags.
Description: When the history collector switches to the redundant mode, the number of
points subscribed from the CP is twice the number of points configured on
the primary history collector. This could cause the number of subscriptions to
a CP to exceed the limit on the number of points that can be subscribed from
a CP. For example, if you configure 8000 points on the primary history
collector, the primary requests 8000 points from the CP. When the history
collector switches to redundant mode, double the number of points are
subscribed from the CP, which in this case, is 16000 points. This exceeds the
numbers of points supported by the CP, keeping several points from getting
historized.
Therefore, when configuring the History collector in redundant mode, you

should design the system such that the number of points subscribed from a
single CP never exceeds the CP limit.
Issue: The Control Software does not provide full-featured support for Bulk
Generation of the History tag configuration.
Description: For example, Bulk Generation cannot populate the History configuration
fields with block descriptions, high and low ranges, and so forth.
As a workaround, do the following:
1. Create templates derived from the base templates for compounds and
various I/A Series block types.
2. Enable history for the desired parameters and specify history
configuration fields.
3. In BulkGenerate, import SaveAll data.
4. Click Compounds to display the compound view and change the
template in the Template column to the desired derived template.
Note You can also click Blocks to display the block view and change
template (s) in the Type column to the desired derived template (s).
5. Click Generate to create your objects. BulkGenerate specifies history

configuration according to your derived templates.

50 4. User Notes
Issue: History Object messages in the Properties dialog box on non-redundant App
Engine (History Object icon in the Control Editors has an orange square with
an exclamation mark, ‘!’)
Description: The History Object has input primitives for retrieving AppEngine
redundancy information. When the History Object is within a non-redundant
AppEngine, the Redundancy primitive does not exist on the AppEngine, so
the following messages are shown in the Properties dialog box for the
History Object in the Control Editors:
Could not resolve reference MyEngine.Redundancy.Identity in attribute
HistPrim._AppEngineRedundancyIdentity.InputSource.
Could not resolve reference MyEngine.Redundancy.Identity in attribute –
HistPrim._AppEngineRedundancyPartnerPlatform.InputSource.
You can safely ignore these messages.
Issue: History Object Editor General tab is blank

Description: This is by design. The History Object does not have any configurable
parameters in the Control Editors. The History Object receives its tag
configuration at runtime from the Sync Service running on the Galaxy
machine. The Sync Service receives the configuration information during
deployment and undeployment of I/A Series compounds and blocks. The
History Object saves the configuration in a retentive attribute for later use
during startup of the stop and restart of the AppEngine.
Issue: Never deploy more than one I/A Series History object to the same
workstation.
Description: This is by design. If attempted, the second deployed History Object (and all
subsequent History Objects) periodically logs the following message:
Another History object was already deployed on this workstation. This
object, ‘AWXP05_Hist2’,does not do anything.
Undeploy and delete all History object instances on this workstation except
one!

4. User Notes 51
Issue: The message, failed to connect to Historian appears.

Description: By default, the History Object is deployed at installation time. If you do not
have Wonderware Historian software or it is not running on the machine
indicated by the Historian field for the History Object’s application engine
(for example, AWXP05_AppH), you may observe this message:
HistorianPrimitive AWXP05_AppH failed to connect to
Historian HSTNOD.
If historization is not desired, undeploy the History Object, its area and its
Application engine. Additionally, you can move them to the “Unassigned
Host” area of the Control Editors or delete them.
If historization is desired, but to Wonderware Historian software on a
machine other than the one specified during software install, change the
Historian field to the desired machine name.
Note At the Control Software install, if the Historian machine name was not
entered, was blank, or was not a valid computer name, install defaults the
Historian machine name to enter_historian_hostname.
Issue: “MinThreshold for circular path too small to accommodate average history
block size” message may appear.
Description: This is an important Wonderware Historian software configuration issue that
is documented here for information. When the number of tags and changes is
high enough, you may observe a periodic message like the one above. To
resolve this, perform the following steps:
1. Increase the configured value of the Deletion threshold parameter for
the circular data path.
2. In SMC, call up Help > Help Topics.
3. Click the Search tab and enter Automatic Deletion of History Blocks.
4. Double-click on the Title of the same name.
Also, see the section titled “Editing History Block Storage Locations” in
Wonderware Historian Administration Guide for instructions on how to
make changes.

52 4. User Notes
Issue: Upon transition to On Scan, timestamp(s) may be overwritten.

Description: To help ensure that unchanging or slowly-changing tags get historized with
the latest value or quality on transition from Off Scan to On Scan, the
History Object overwrites the timestamp of the initial On Scan sample for
each tag with the current scan time of the collecting workstation. This is
required to help ensure that the timestamp is within the Wonderware
Historian’s “realtime window”; otherwise, the sample gets dropped by the
Wonderware Historian. A side effect of this is that a small number of
subsequent sample (s) may have their timestamp adjusted by the Wonderware
Historian to get them in sequence. This can be checked by using Wonderware
Historian Client Query and looking for samples with QualityDetail 704 with
QualityString “Good, timestamp overwritten; values out of time sequence”.
To minimize the number of these “timestamp overwritten” samples, keep the
machine clocks well synchronized.
Issue: OLE-DB provider error may appear regarding Wonderware Historian

software memory usage, preventing the retrieval of history data.
Description: At a computer running Wonderware Historian software, you may see
messages from aahEventSvc component, for example, “Database Error
(5;ExecuteDetectorSQL: The OLE DB provider “INSQL” for linked server
“INSQL” reported an error. The provider ran out of memory”.
This message is a result of the SQL server using too much memory. The
Maximum server memory (in MB) on the Memory page of Server
Properties in SQL Server Management Studio must be limited to help prevent
SQL Server from using too much memory. The recommended guideline is
using half the physical memory. For example, use 2000 MB for 4 GB of
physical memory.
Be sure Maximum server memory (in MB) is configured properly, and
restart SQL Server if a change is required.
Issue: Stop Wonderware Historian software before manually changing system

date/time.
Description: Wonderware Historian software supports the TimeSyncMaster configuration
parameter for automatic time synchronization. Refer to Wonderware
Historian software documentation (see “Reference Documents” on page x).
If you manually change the system date or time, be sure that you first stop
Wonderware Historian software. Otherwise, the Wonderware Historian
Server history blocks could get corrupted because of mismatched start and
end dates/times. This could exhibit itself as inability to retrieve data from the
history blocks.

4. User Notes 53
Issue: The HistPrim.SamplesPerSecond parameter does not function properly.

Workaround: After changing the simulation mode option of deployed DI Object or
deployed History Object, restart the Engine (AppEngine) that hosts the
object.
4.6 Control Editors v7.1

This section contains user notes for the Control Editors v7.1 software.
Issue: In the Import Preferences dialog box, the renaming mechanisms for the
“Rename” options of “Object Name Conflict, Different Base Template” and
“Object Name Conflict, Same Base Template” are different.
Description: For “Different Base Template”, the user-supplied string is appended to all
renames. For “Same Base Template”, the extension is always of the form
“_01”, using the first numeric value available.
Issue: Deployment issues with SFC blocks, for specific compound naming
scenarios
Description: The following list of names are NOT recommended to be used as compound
names:
• 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 results in deployment of any
sequence (HLBL/SFC) or PLB blocks under that compound to abort.
The unsuccessful deployment occurs in “Object Validations” Screen.

54 4. User Notes
Issue: During Control Editors installation, the Security Provider generates several
error and warning messages.
Description: The following messages are logged in to the SMC every minute during the
Galaxy preparation.
• Did not find the optional file at D:\Program
Files\ArchestrA\Framework\Bin\Invensys\Access\SyncService\SyncAg
entProxyConfig.xml. Attempting to obtain configuration information
from ArchestrA's Platform Mapping file.
• SyncComm::ReadPlatformMappingFile() failed attempt to get galaxy
platform name from PlatformMapping.xml file: Could not find file
'D:\ProgramFiles\ArchestrA\Framework\Bin\GlobalDataCache\Platform
Mapping\PlatformMapping.xml'.
• SyncClient::InitGalaxyMachineNameAndPort() Cannot obtain machine
name from Platform Mapping file. A Platform should be deployed on
this workstation
• SyncClient::InitServerConnectionString() Invalid Galaxy Machine
Name or Port Name
• SyncComm::RegisterClient() Value cannot be null.Parameter name:
appUrl
Workaround: The Security Provider stops logging these messages after it finds the
PlatformMapping\PlatformMapping.xml' file.
Issue: Opening the Bulk Create dialog for the first time can be slow.
Description: The first time the dialog box opens on a client, ArchestrA software pulls all
the DLLs of all the objects, regardless of whether you want to generate those
objects or not. This only occurs when you first open the dialog box on each
client.
ArchestrA software transfers the required DLLs for each application object
the first time it is queried for on a client machine. This DLL transfer is slow
and only takes place for the first query. Successive queries on the object do
not cause DLLs to be transferred over the network because they are now
present on the client machine. Since the Bulk Create dialog box queries for
many types of objects, this dialog box loads very slowly the first time it is
opened on each client.
Issue: The software package AICC7 is automatically installed during the I/A Series
Software/Control Core Services install process.
Description: Although the software package AICC7 does not show up on the list of
software packages available for an AW, it is automatically placed on the
Commit diskette for every workstation, and installed during the I/A
Series/Control Core Services Software Install process. Even though the
Control Editors do not rely on this software package, certain legacy software
and compilers require this package to be installed in order to function
properly.

4. User Notes 55
Issue: Performing a Find operation using the Find dialog box takes a long time.
Description: Performing a Find operation without specifying a Scope object can take
several minutes, depending on how many objects there are in the Galaxy.
You are notified when a Find operation is specified without declaring a
Scope object.
Whenever possible, perform a Find operation with a specified Scope object
to narrow down the breadth of the search.
Issue: Find/Replace can produce inconsistent results when switching views while
the Find/Replace dialog box is open in the Bulk Data Editor.
Description: When the view is switched while the Find/Replace dialog box is open in the
Bulk Data Editor, future Find/Replace operations may produce incorrect
results.
Workaround: Always close the Find/Replace dialog box before switching to a different
view.
Issue: Graphical changes to strategy template not propagated

Description: If an instance of a template is made, then a non-connection change is made to
the template (for example, updating an Appearance Object or moving lines to
make them appear neater) the change does not carry through each of the
instances of the template.
Modifying objects graphically, such as positioning blocks and connections in
a strategy template, does not result in those changes being applied to derived
templates and instances.
Issue: The Appearance Object Editor does not allow you to save an Appearance
Object with an “unfinished” frame.
Description: Always finish creating the Appearance Object’s frame before saving the
object.
Issue: Connection line to Output declaration is not automatically drawn

Description: When LiveData is on, adding a parameter to the appearance object does not
redraw the connection to the parameter.
Workaround: The user should refresh the connection using the menu option in the strategy
when LiveData is stopped.

56 4. User Notes
Issue: Nesting 10 or more strategy templates results in an error.

Description: ArchestrA software only supports 10 levels of containment in its object
model. If you nest strategy templates to 10 or more levels, and then create an
instance of that template and attempt to assign it to a compound, an error
results.
Do not nest strategy templates to more than nine levels deep. That way, when
an instance of the strategy template is made and assigned to a compound, the
compound becomes the 10th level.
Issue: The Control Editors do not import the system time settings from a SysDef
configuration.
Description: When you are configuring a system with System Definition software, you can
configure the system time format by setting the HPS System Time parameter
to either UTC or IATIME.
However, the Control Editors do not import the system time settings from a
SysDef configuration. After importing the configuration, the Control Editors
use the UTC time format, even if IATIME was originally configured in
SysDef.
After importing a SysDef configuration, perform the following steps to verify
that the Control Editors configuration is using the correct time settings. You
can manually edit the time settings if necessary:
1. Select Network > Options from the Control Editors top-level menu. The
Network Options dialog box appears.
2. Select the Options tab if not already selected.
3. In the System Time drop-down list, choose either UTC or IATIME. The
default value is UTC.
Issue: The name of an FBM can be displayed differently in the Network view
depending on whether or not the FBM is assigned to a controller/FCM.
Description: When an FBM is unassigned in the Network view (that is, the FBM is not
assigned to a controller or FCM) it displays its tag name. When an FBM is
assigned to a controller or FCM, it displays its contained name in the
Network view. The two names can be different, and either one can be viewed
depending on the assignment state of the FBM.
Issue: Under certain conditions, the Control Editors may assign FCM names that
are greater than six characters in length.
Description: If you are assigning an FCM to a controller, and an FCM with the same name
is already assigned to the controller, the Control Editors rename the second
FCM with a name that is more than six characters in length. For example, if
you drag and drop “F00200” to a CP, Control Editors change the name to
“F00200_1” if F00200 is already assigned to the controller.

4. User Notes 57
Issue: On rare occasions, the Fieldbus Session Manager (FSM) becomes

unresponsive when working with PROFIBUS objects in the Field Device
Manager (FDM).
Description: This condition is very difficult to reproduce but has occurred after doing
numerous operations such as undeploying and deploying blocks and devices,
exporting GSDs, associating GSDs, associating Vendor DTMs, pushing
inheritance, etc. Symptoms of the FSM becoming unresponsive include a
“Live List Timed out” message in the Communication Error Monitor and
devices not going online in the Field Device Manager (FDM).
Workaround: To recover, close and reopen ArchestrA IDE and call up a Live List. If the
FSM is still unresponsive, restart the FSM service.
To restart the FSM service, proceed as follows:
1. Close ArchestrA IDE.
2. Open the Microsoft Windows Services Management Console using
either of the following methods:
a. Click Start, click Control Panel, double-click Administrative
Tools, and double-click Services.
b. Click Start, click Run...., type “services.msc”, and click OK.
3. Locate and select the FSM Service “FSM_Serv”.
4. Restart the FSM service using the Restart the service link in the upper-
left corner.
5. Re-open ArchestrA IDE and call up the Live List to confirm that the
fault has been corrected.

58 4. User Notes
Issue: When performing the EEPROM UPDATE action for a redundant FBM228,
the pair may not be fully synchronized after the update of the first module.
Description: The FBM228 (with SWTYPE 128 or SWTYPE 228) supports the On-Line
Upgrade feature, allowing for software updates without process interruptions.
Operators invoke this feature by selecting the EEPROM UPDATE action for
only one of the modules (Main or Backup), and then wait for that operation to
complete, before updating the other module in a redundant pair.
However, care must be taken when perform the EEPROM UPDATE action
for a redundant FBM228, to make sure that the pair has fully synchronized
after the update of the first module, before updating the second module in the
redundant pair.
Workaround: Proceed as follows:
Note For a successful on-line upgrade it is important that no error or

warning conditions are reported in Equipment Information of the ECB202.
Any warning or error conditions must be corrected before the on-line upgrade
can start.
Bring up the System Manager or SMDH, select the FBM, and verify the
Software Revision. If the Software Revision shown matches the new version
of the FBM228 IOM File, no action should be taken; if it does not match,
proceed with the following:
1. Place the Tracker module in Off-Line mode.
2. Select the EEPROM UPDATE action for the Tracker Module (this takes
about five minutes).
3. Place the Tracker module in On-Line mode and let the Master and
Tracker modules synchronize (The “Main/Backup Not Init” for
SWTYPE 228 and “Redundancy Sync” for SWTYPE 128) Equipment
information is OK. Note that the ECB202 will report a “REV
MISMATCH FAULT”. This condition is normal since the revision
information in the redundant modules will be temporarily different
during the upgrade.
4. Press the SWITCH ROLES button. The module that was just updated
should take on the master role.
5. Place the module that has not yet been updated, which now has the
Tracker role, Off-Line.
6. Select the EEPROM UPDATE action for that module.
7. Place that module into On-Line mode and let the Master and Tracker
modules synchronize (No error or warning condition reported in
Equipment Information for the ECB202).
8. Press the SWITCH ROLES button. The Main module is now Master.

4. User Notes 59
Issue: Bulk generation of instance of Universal FBM (FBM247) and its associated
device specified in the Bulk Data Object throws Unhandled exception Error.
Description: When defining a device (DEV_ECB201) in the BulkData Hardware/Modules
view that will be assigned to an FBM247, the channel number used for
assignment is taken from the column “DVNAME”. Legal values for this ECB
parameter are “CH1” through “CH8”. If this column contains any other
values, or if the column is missing, the device will be assigned directly to the
parent FBM247 with no associated channel.
FBM247 channel configuration is described in “Configuring Blocks for
FBM247” in HART Communication Interface Modules User's Guide
(B0400FF).
To assign using specific channel numbers, the operator can enter “CH1”
through “CH8” into the DVNAME column to the BulkData table. Refer to
the Bulk Data Editor User's Guide (B0750AF) for information on how to add
this column if it does not already exist.
Issue: BulkData: Cannot create and assign a generic device to an existing FBM.
Description: On the Bulk Data Object Hardware tab page, “Modules” view, the “Parents”
column features a drop-down list that contains all CPs and FBMs which exist
in the Galaxy Repository and in the Bulk Data Object, as well as all FBMs in
the Bulk Data Object. FBMs existing in the Galaxy are intentionally not
included to keep this list at a manageable size. Text entry is provided for this
column to allow an FBM existing in the Galaxy to be entered for assignment
during bulk generation.
Issue: When bulk generating from a SaveAll, a warning is reported that indicates an
FBM240 is not valid with a GDEV block.
Description: When Bulk Generating from a SaveAll, the warning appears stating that an
FBM240 is not valid with a GDEV block. However, this is not correct. This
warning is also reported during Control Editors configuration if this
combination of FBM/Block is used. Using an FBM240 with a GDEV block is
a valid combination.
When connecting the I/O of a GDEV block to an FBM240 via bulk

generation or manually, a warning is reported, “Invalid IOM_ID
value: F00001 (I/O Block - ECB type mismatch)”. This
message can be ignored. This is not a recommended Block/ECB
combination, but the value is still set for the IOM_ID parameter and the I/O
connection is made.

60 4. User Notes
Issue: A deployed compound is shown as undeployed after deployment.

Description: A compound is shown as undeployed after deployment. The compound is
incorrectly reported when two clients are deploying the same compound. The
first deployment operation succeeds, but the second deployment operation
reports an error and sets the compound to an undeployed state.
Try to avoid deploying the same compound from two clients. If the situation
occurs, use Sync DBs to mark the compound deploy status correctly.
Issue: Prepare All does not re-validate the CP state.

Description: The Prepare All function in the Control Editors checks each object to
determine whether it can be deployed and displays the results in an output
window. If an object is checked out, the object cannot be deployed. However,
the Prepare All function is not revalidating the CP state and is reporting that
the object is still checked out even if it is not.
Reopen the IDE and try the deployment again.
Issue: A small delay was introduced for a standard installation of I/A Series.
Description: The file replication service (SFRS/FRS) was made more secure for I/A Series
8.8. In order to achieve this, a delay was introduced for a standard installation
of I/A Series. Therefore, the Control Software Deployment, which utilizes
SFRS, when executed on a standard I/A Series or Control Core Services
installation will be three to six seconds slower than FCS 3.x.
Issue: Input Strategy Declarations when using "Create Template from Instance" are
not cleared.
Description: Strategy Input Declaration values are not cleared during the conversion
process when the Create Template From Instance context menu item is
selected on a Strategy instance. These input declaration values will be
propagated to derived instances of the newly created template unless they are
first manually cleared in the template.
To manually clear the input declarations:

1. Open the created Strategy template.
2. Select each of the values associated with the input declarations and
delete the value.
3. Save the template.

4. User Notes 61
Issue: Opening the Device Browser from the Strategy Editor may report a System
Management Console (SMC) error about a SQL timeout, even if the browser
opens successfully.
Description: Opening the Device Browser from the Strategy Editor may result in the report
of a SMC error concerning a SQL timeout, even if the browser opens
successfully. However, I/O assignment can be successfully configured. This
only happens the first time after installing FCS v4.0.2 and the error will not
be reported for subsequent calls to open the Device Browser from the
Strategy Editor.
Issue: Unable to Print or Save FCP280 Channel Assignments Report. Unable to

print Reports when UAC settings are set to Default.
Description: Not able to print reports in the System editor reporting tool window when
UAC is ON.
Below are the steps to be followed to print successfully:
1. Turn the UAC OFF by following the below steps:
a. Go to Control Panel -> User Accounts
b. Select ‘Change User Account Control Settings’
c. In the ‘User Account Control Settings’ dialog, move the slider to
‘Never notify’
d. Restart the machine
2. Open the ArchestrA IDE & print report using Print button in the System
Editor Reporting Tool window
Issue: Import of a saved compound file to bulk data populates the CP field with the
directory name that contains the saved compound file.
Description: BulkData Import of SaveALL determines the CP name from the directory
chosen for save-all import as follows:
If the saveall import directory is exactly six characters in length, bulk data
import attempts to assign this name to the CP being generated. However if
the folder name is not six characters in length, it assigns a default name of
"C00100" (C00101, C00102 etc).

62 4. User Notes
Issue: BulkGen load of a Sysdef export reporting many errors.

Description: The parent column in the Network Dataview, Stations Dataview, Modules
Dataview needs to be filled for each hardware object being generated if the
assignment of the hardware object to the appropriate parent is warranted. If
the parent column is left "null" the bulk-generation process will generate that
hardware object and assign it to the "Unassigned Hardware" or "Unassigned
Host" nodes.
If at all the hardware object was already generated without filling the parent
column in the bulk data editor, then you need to manually assign the
generated hardware object to the appropriate parent.
4.6.1 SFC Editor

Issue: IACC Loop back equivalent in the SFC Editor.
Description: Whenever there is loop back code in SFC that is migrated from IACC to
Control Software, the SFC import converts the loop back to a label with a
jump to the label. This is logically equal to the loop back in IACC.
Issue: SFC Transitions show extra text in SFC Detail View.

Description: If the code, which uses variable names of reserved words in the language (for
example, TRUE or FALSE,) is deployed and viewed in the SFC Detail
Display, it may appear different than in the Control Editors (for example,
TRUEE).
Workaround: Do not name variables TRUE or FALSE.
Issue: For some specific compounds, SaveAll export fails with an Unable to
find Specified File message.
Workaround: Any sequence (SFC/HLBL) block that is not compiled is exported as an
HLBL block with default sequence code files during a SaveAll Export.
Issue: It can take up to 10 seconds to send an SFC source file to the host station.
During that time, the SFC Display Manager will not be able to display
block’s diagram.
Workaround: Wait until the SFC source file has been successfully sent to the host station.

4. User Notes 63
Issue: When block instantiation is invoked, the device reboots after a successful
block instantiation.
Description: During this time, when the device is rebooting, the connection requests from
the UDTM are unsuccessful and the errors received during these retries are
logged to the UDTM error monitor. These connection request errors are an
expected part of the block instantiation process.
4.6.2 Strategy Editor
Issue: Strategy template input declarations connected to instance objects are not
propagated correctly to derived objects.
Description: On a strategy template if a user connects a locked input declaration to a
compound/ecb/top level strategy instance, (For example,
“COMPOUND.PARAM”) then the value propagated to derived strategies is
“.PARAM”. The name of compound/ecb/top level strategy instance is lost
resulting in a broken connection.
Workaround: After the error occurs, you can add or delete the following from the strategy
template as a workaround:
• Another Declaration
• User attribute
• Block
If you add/delete block, declaration and user attribute in the same session as
the declaration change, the error is avoided completely.
4.6.3 Execution Order

Issue: Execution order of blocks may change without user direction.
Description: Changing the control zone of a block may change its execution order as well.
Workaround: If the control zone of a block is changed, the execution order of the block in
its strategy should be updated to return it to its original execution order.
4.7 HART
4.7.1 ECB Period for HART FBMs

The fastest allowed ECB period for the HART FBMs is 100 milliseconds
(PERIOD = 0). However, it is recommended that you refer to the appropriate
Sizing Guidelines and Excel Workbook for your Control Processor (such as the
Field Control Processor 280 (FCP280) Sizing Guidelines and Excel®
Workbook (B0700FY)) to determine the optimal BPC for this ECB, in order to
help prevent overloading.

64 4. User Notes
4.7.2 FoxCom I.F.D Modem Support

In Field Device Manager for HART v4.0 or later, with the “Run FDT1.2.x
DTMs in a separate process” option enabled under user preferences, the
FoxCom I.F.D modem is unable to connect to FoxCom devices. However, with
this option unchecked under User Preferences, FoxCom devices can connect
and work with the FoxCom I.F.D modem successfully.
4.7.3 Foxboro Control Software Export plugin

PACTware add-in “Foxboro Control Software Export” used to export HART
and FoxCom topologies from PACTware into Control Software is not
supported in PACTware v5.0.
This add-in is supported in PACTware v3.6 SP1 or PACTware v4.x
4.7.4 SaveAll Export/Import Operations Not

Supported for HART
If any HART devices are included in an I/A Series SaveAll file, any
export/import operations performed on this SaveAll file by the Control
Software does not support the importing/exporting of these devices.
SaveAll export/import operations in the Control Software cannot preserve the
HART object extensions. It is not recommended to use the SaveAll format to
export/import HART devices.
4.7.5 Uninstalling Foxboro FoxCom DTMs

Uninstalling Foxboro FoxCom DTMs may cause issues in using Foxboro Evo
Field Device Manager for FOUNDATION Fieldbus / Profibus /HART
packages.
Run FoxComVDTMFix.bat is located in the zip file:
\Redist\FoxComDTMLibrary_Patch\FoxComDTMLibrary_Patch.zip
This file is part of any Field Device Manager CD and is used to resolve issues.
The FoxComDTMLibrary_Patch.zip file contains the Read_first.txt file for
instructions on how to run the batch file.
Note For DTM compatibility issues see the table under “DTM Compatibility - HART,
FOUNDATION Fieldbus and PROFIBUS” on page 66.
4.8 FOUNDATION fieldbus
4.8.1 FOUNDATION fieldbus Schedule

Deployment and Un-Deployment
Each time the schedule for the block is deployed or un-deployed using the
Control Software tools, the schedule for the entire segment is re-calculated for

4. User Notes 65
all blocks on the segment. The schedule information is also deployed for all the
blocks on the segment. This includes the new, the modified, and the already
deployed blocks, that have not been changed.
The amount of time taken for this operation depends on the number of blocks
being used, the number of devices connected, and the available free time on the
segment.
You have to wait until all of the blocks have been updated by the FBM with the
schedule information before invoking a new deploy or un-deploy operation.
4.8.2 Single Block Deployment and Un-

Deployment
Single Block deployment is a powerful tool for block tuning. When it is used
with FOUNDATION fieldbus blocks, single block deployment and un-
deployment can trigger re-calculation and re-deployment of the entire segment
schedule (see “FOUNDATION fieldbus Schedule Deployment and Un-
Deployment” above). The list of user actions that can trigger a change in the
segment schedule includes:
• Assignment of a new FOUNDATION fieldbus-specific block to the
segment
• Un-deployment of a FOUNDATION fieldbus specific block
• Change of a block assignment
• Change block connections
• Change block execution order, etc.
The user must wait until all the blocks have been updated by the FBM with the
schedule information before invoking a new deploy or un-deploy operation.
For additional information, refer to FOUNDATION fieldbus Control in the
Field (CIF) Release Notes (B0750RW).
4.8.3 SaveAll Import/Export Operations Not

Supported for FOUNDATION fieldbus Devices
and Blocks
If any FOUNDATION fieldbus devices or blocks are included in an Control
Processor SaveAll file, any import/export operations performed on this
SaveAll file by the Control Software does not support the importing/exporting
of these devices or blocks. SaveAll import/export operations in the Control
Software cannot preserve the FOUNDATION fieldbus object extensions. It is
not recommended to use the SaveAll format to import/export FOUNDATION
fieldbus objects.

66 4. User Notes
4.8.4 DTM Compatibility - HART, FOUNDATION

Fieldbus and PROFIBUS
A number of DTMs have been tested in the latest software and have been
proven interoperable with the FDM software for FOUNDATION fieldbus,
HART and Profibus.
The FDT group maintains a list of DTMs (https://fdtgroup.org/products/fdt-
dtms) that have been certified. Sometimes the incompatibility is version
dependent. If you encounter issues with a DTM, we recommend that you
contact the DTM vendor and ask for the latest version of the DTM. In all cases
you can configure the instrument by using the standard DD or EDD file
technology.
Note Attaching DTMs to Field Device Manager templates is optional. It is

recommended that DTMs are used for providing diagnostic information, which
is above and beyond the DD files supplied for the instrument.
The following table lists DTMs that are not compatible with Field Device
Manager v4.0 software.
.
Table 4-1. DTMs with Known Compatibility Issues
DTM Instrument DTM Instrument

Manufacturer Type Version DTM Type Protocol Comment
Yokogawa EJA-NEXT in V1.7.75 Device DTM Profibus Incompatible to FDMv 4.0 due
DTMLibrary to invalid GSD produced by the
PROFIBUS DTM.
2016-3
Krone PA ESK3 (MBP- 3.0 Device DTM Profibus Incompatible to FDMv 4.0 due
SK2) DTM to invalid GSD produced by the
DTM.
Metso ND9000 1.20.4 Device DTM Profibus Incompatible to FDMv 4.0 due
to invalid GSD produced by the
DTM.
Foxboro SRD991 3.6.2 Device DTM Profibus Crash when more than 32
characters are entered in the
AutoStart screen Cal Info field
Foxboro FoxCom I.F.D. 2.6000.001 Communication DTM FoxCom Not compatible with "Run FDT
modem 1.2.x DTMs in a separate
process" option.
Yokogawa YokogawaDTM_ 6.4 Device DTM HART Some of the DTMs in

HART_2017-2 YokogawaDTM_HART_2017-3
library fail to load due to missing
DD files as part of the install.

4. User Notes 67
4.9 PROFIBUS
4.9.1 ICC and SMDH Support for the FBM222

FCS v4.0 or later and the Control Software v5.0 or later provide
comprehensive support for the FBM222 Redundant PROFIBUS Interface
Module, with the Control Editors and Field Device Manager providing device
configuration, device commissioning, and advanced troubleshooting
capabilities. Field Device Manager fully complies with the FDT standards, and
provides a universal device type manager (UDTM), while supporting optional
use of manufacturer-supplied DTMs.
Earlier I/A Series applications provided a more limited support for the
FBM222 as follows:
• FBM and Device Configuration: The I/A Series Integrated Control
Configurator (ICC) provides the same configuration support for the
FBM222 that ICC provides for the FBM223.
Refer to PROFIBUS-DP Communication Interface Module (FBM223)
User’s Guide (B0400FE) for information on setting up the FBM ECB.
Note the letterbug requirements for redundant and non-redundant FBMs
described in Chapter 4 of Implementing PROFIBUS Networks in Foxboro
Control Software Applications (B0750BE).
Add device ECBs (ECB201s) in ICC and then configure the device using
their GSDs and the port configuration software described in PROFIBUS-
DP Communication Interface Module (FBM223) User’s Guide
(B0400FE).
• Control Configuration: Configure the DCI blocks in ICC to access
PROFIBUS cyclic and acyclic data by manually entering the IOM_ID and
point number parameters, as described for the FBM 223 in PROFIBUS-
DP Communication Interface Module (FBM223) User’s Guide
(B0400FE). The FBM222 supports the basic point number configuration
syntax used by the FBM223, but also offers significant new features such
as access to PA status and better access to acyclic data. The expanded
point configuration string syntax is described in detail in Chapter 9 of
Implementing PROFIBUS Networks in Foxboro Control Software
Applications (B0750BE).
• System Management: There is SMDH support for the FBM222 on both
Solaris and Windows platforms. The FBM222 can be used to pull some
acyclic data from the PROFIBUS slave device using the DCI blocks and
the GSD file of the device itself.
4.9.2 FBM222 at Low Baud Rates

The FBM222 sizing calculations described in the CP 270 Sizing Guidelines
and Excel® Workbook documents (B0700FY, B0700AV, and B0700AW) apply
primarily to high PROFIBUS DP baud rates (500 kBaud and higher). At lower
baud rates, the actual transfer rate on the PROFIBUS DP segment may become
a limiting factor and must be considered in conjunction with the FBM222
spreadsheet. The FBM222 detects an I/O overload and set the “Port I/O Load
Fault” condition in SMDH/System Manager, but sizing estimations must be

68 4. User Notes
done to avoid this error condition. The most common reason for using lower
baud rates is the usage of the Pepperl+Fuchs SK-1 DP to PA segment coupler
operating at 93.75 kBaud.
In PROFIBUS documentation, the time it takes a slave to respond to a message
from the master is called the reaction time. Refer to the EN50170 standard for
a detailed description and calculation of reaction time, but this time is the sum
of all delays with sending a message to a PROFIBUS device and receiving a
response. At lower baud rates, the reaction time is normally dominated by the
bus transfer time of the message.
For example, assume a PROFIBUS slave has 10 bytes of output data and 20
bytes of input data to be transferred. A slave like this results in a request and
response transmission of (2 x 9 + 10 + 20) x 11 = 528 bits (9 character header
for request and response, 10 bytes output, and 20 bytes input. Each byte is
transferred using 11 bits). At a baud rate of 93.75 kBaud, just the transfer of
data takes approximately 6 milliseconds.
Note that the SK-1 segment coupler adds even more delay, and a single output-
input data exchange to a single PROFIBUS PA type device may take nearly 10
milliseconds. If the MIN_SLAVE_INTERVAL is configured to 130
milliseconds, the maximum recommended number of devices would be
approximately 10. Larger MIN_SLAVE_INTERVAL values would allow for
additional devices. The SK-1 has been superseded by newer products and is
not recommended for use with the FBM222. See the document Implementing
PROFIBUS Networks in Foxboro Control Software Applications (B0750BE),
section “PROFIBUS PA Considerations”, for recommendations on connecting
PROFIBUS PA devices to the FBM222.
The example above just serves as a simple example, but it indicates that care
must be taken when using low PROFIBUS DP Baud rates to avoid I/O
Overload conditions.

4. User Notes 69
4.9.3 PROFIBUS FBM Editor

Issue: Application Error after closing ArchestrA IDE with PROFIBUS FBM Editor
still open.
Workaround Always close the PROFIBUS FBM Editor (for FBM222) in the Control
Editors, saving changes as necessary, before closing ArchestrA IDE.
Otherwise, if you close ArchestrA IDE while the PROFIBUS FBM Editor is
open, ArchestrA IDE will experience an Application Error and you will not
be prompted to save any changes.
4.9.4 SaveAll Import/Export Operations Not

Supported for Profibus
Issue: If any Profibus devices are included in an I/A Series SaveAll file, any
import/export operations performed on this SaveAll file by the Control
Software does not support the importing/exporting of these devices.
SaveAll import/export operations in the Control Software cannot preserve the
Profibus object extensions.
Workaround It is not recommended to use the SaveAll format to import/export Profibus
devices.
Note For DTM compatibility issues see the table under “DTM Compatibility - HART,
FOUNDATION Fieldbus and PROFIBUS” on page 66.
4.10 Galaxy Server

The issues related to Galaxy Server are detailed in this section.
Issue: The clients cannot connect to the Galaxy Sync Service because of the security
messages in the SMC Log file.
Workaround: During migration, the sync service is stopped and the clients (Security and
History) try to connect to the sync service. After the service is stopped, the
security messages are generated for each client till the service is started. This
is an expected behavior.
SMC stops logging these messages once the InFusionSyncService is started.

70 4. User Notes
Issue: Historian related error occurs during the Galaxy preparation in a secured
migration test bed.
Workaround: During migration or initial installation of the Historian configuration service,
the following error messages could be displayed in the SMC:
• ERROR: StartDataRetrievalQuery failed (MDAS handle; Error code;
Tag count; Query handle) (1;90; 1; 1) [AWFI23; ??????; 325]
• ERROR: Failed to configure replication service (Error code; Response
error) (1460, This operation returned because the timeout period expired.
0) [AWFI23; aahCfgSvc.cpp; 1279].
If the above error messages occur during the installation or migration, it does
not cause any loss of functionality.
After you complete the installation or migration, verify that these errors do
not persist and data is historized during the normal operation of Historian.
Note It is recommended that you restart the History Server to reload the
database changes after the installation is completed. On restarting, verify that
this error is not further logged in the SMC and the points are being historized.
4.10.1 Additional Steps Required on Galaxy

Created Using Galaxy Backup (.cab) File
When a Galaxy is created using a pre-existing Galaxy .cab file, the user is
advised to perform the following steps before using the Galaxy:
1. Open ArchestrA IDE.
2. Select $FF_Device in the template toolbox.
3. Right-click $FF_Device and select Synchronize all DD Files.

4. User Notes 71
Figure 4-1. Template Toolbox - $FF_Device
The following dialog box appears.
Figure 4-2. Synchronize DD Files - $FF_Device
4. Select Yes.
This loads all the DDFiles associated with the configured FF Device templates
on the current system.

72 4. User Notes

73
C H A P T E R 5
Known Issues and

Workarounds
This chapter describes known issues and workarounds of the Control Software
v7.1.
Similar to restrictions, known issues represent temporary deficiencies in the
product. Frequently, these types of issues result from incomplete functionality
of the product.
When applicable, the workarounds are also given for the known issues in this
chapter. Workarounds provide a means of bypassing a known issue, enabling
you to perform an operation that would otherwise be prohibited or difficult to
execute.
Contents
• The Control Software v7.1 Installation
• Control HMIControl HMI
• Access Manager
• Control Editors
• Field Device Manager

74 5. Known Issues and Workarounds
5.1 The Control Software v7.1 Installation

The following are the known issues and workarounds for the installation of the
Control Software v7.1.
Issue SMC errors during upgrade from Control Software v5.0 to v7.1
Description During upgrade from the Control Software 5.0 to 7.1, the SMC has shown
error messages related to Fox-Remoting, IASeriesIntegrator Runtime, and
Securityprovider Service.
Impact No Functional impact. All error reported services are in running mode after
Upgrade.
Workaround • Verify Fox-Remoting (IA-Remoting service) service and Security
provider (InFusion Security provider) service are in running mode. If not
start the services manually.
• Proceed as follows to start the services manually:
• Select Run from Windows Start button.
• Type services.msc. The Services window is opened.
• Verify Fox-Remoting (IA-Remoting service) service and Security
provider (InFusion Security provider) service is in running mode.
• If the services are in stop mode, right-click the service and select
Start option.
Issue The SMC log reports error and warning messages regarding conflicting Excel
and Microsoft Access Database Engine applications.
Description If Excel 2016 is installed, Control Software requires Microsoft Access
database engine 2010 to be installed.
If Excel 2016 is installed after the Control Software is installed, you must
install Microsoft Access database engine 2010 manually by following the
below procedure.
Workaround Install Microsoft Access database engine 2010 (This process is described in
more detail in Appendix N of the Control Software Installation Guide
(B0750RA, Rev. Z).
1. Browse to:
C:\Program Files(x86)\Invensys\InFusion\Installer\WWPatches.
2. Double-click AccessDatabaseEngine.exe.
3. Click Next.
4. Read and accept the License Agreement. Then click Next.
5. Click Install.

5. Known Issues and Workarounds 75
Issue GR or Client Platforms does not connect.

Description If the system involves an off platform GR or client, it is possible that platform
deployment may be unsuccessful due to incorrect network binding.
Workaround Using ArchestrA IDE, open platform object editor and modify the Nodename
to IPAddress and perform manual deployment from IDE.
Issue SQL management studio is unable to connect to GR database using Windows

Authentication on Enterprise systems.
Workaround Open SQL Management Studio with elevated permission using Run as
Administrator.
Issue The security database of a client station and the security database of the
Master station get out of sync.
Description After restoring an image on a shadow workstation, making changes to the
image and then restoring a new image based on this workstation’s image,
back to the production workstation, may cause a security mismatch between
the newly-imaged station and the security database on server.
Workaround Use the Refresh History Security option on the GR Node.

Issue InTouch Access Anywhere does not connect to localhost as shown below.
Description InTouch Access Anywhere does not connect and the page cannot be displayed.
Workaround Open Control Panel > Administrative Tools > Services and disable the
Windows Firewall service.
Issue Report generated from v_AlarmEventHistoryInternal2 may report DateDiff

error.
Description When an alarm event report is generated from
v_AlarmEventHistoryInternal2, it may report a DateDiff error.
Workaround 1. Log in to a workstation containing Alarm database.
2. Open SQL Server Management Studio
3. Enter the Server Name and select Windows Authentication as
Authentication.
4. Click Connect to connect to the database.
5. In the Object Explorer treeview, expand Database.
6. Select the Wonderware Alarm Database, for example: "WWALMDB".
This database name is the name provided when the Alarm database was
created.
7. From the File menu, browse to the folder: <drive>:\program files
(x86)\Invensys\InFusion\Installer\WWPatches\L00145765
a. Select the query: v_AlarmEventHistoryInternal2.sql and execute it
using the F5 key.
8. Close the SQL Server Management Studio.

5.2 Control HMI

This section presents a list of known issues and workarounds within Control
HMI. If available, a workaround allowing the user to bypass the issue is
documented as well.
Issue Calling Live Data Viewer from HMI is unable to initially login when opened
Workaround When using ArchestrA Galaxy Security, Click OK on the invalid login
message, for the login dialog to appear.
Enter valid username and password information and click OK to start Live
Data Viewer.
When using OS User or OS Group based security, make sure User and
Password are empty and click OK to start Live Data Viewer.
Issue Situational Awareness KPI meters and Polar Star spokes can be scaled from 0
to 0.
Description If the Setpoint on KPI Meters and polar star spokes is 0, the Hi and Lo scales
calculate to 0.
KPI Meter can have scale of 0 to 0.
The KPI Range is KPITracker to KPITracker *2.
If my target is 0 dollars lost, then my scale is 0 to 0.
If my target is 25k, the tiny fillbar range is 25k-75k. Value changes cannot be
seen.
Polar Star spokes can have a 0/0 scale if the spoke is normalized and SP is 0.
Workaround Use CSA KPI Bar.
Do not use Normalize Spoke value if Setpoint is 0.

Issue Substitute tags do not work for references used as arguments to a third party
.Net function.
Description Substitute Tag Dialog is unable to Substitute IO References that are used as
argument in third party .Net functions.
Workaround Do not use .Net functions in Animations Expressions.
Create a Custom property and use it in the Animation Expression. Assign the
Custom Property to the .Net Function or set the custom property by using a
graphic script.
Issue ArchestrA Graphic Tag String references are converted to lower case.
Description ArchestrA Graphics tag references are converted to Lower case. This effects
string returned from DI Object when using $TAG$.
Workaround Use StringUpper() function to convert lower case strings to uppercase. There
is no workaround for strings that are mixed lower and upper cases.
Issue SMC error message is displayed when deleting InTouch Windows that
contain ArchestrA Graphics.
Description When deleting Intouch Windows from WindowMaker and they contain
ArchestrA graphics, an SMC error message is logged.
• Could not call
RemoveWindowEntriesFromInstancesMapFile
There is no lost functionality as a result of this message and it can be safely

ignored.
Workaround No Workaround. The error message can be ignored.
Issue: Some Fonts are lost while Importing Control HMI windows from a
workstation box to Server box.
Description This issue is caused by the original font used on the imported window is not
installed on the workstation. To reduce the occurrence of this issue:
• Use standard fonts available to all stations.
• Some third party software may install additional fonts do not use those
fonts.
Workaround: Install the missing Fonts on the workstation and re-import windows or
manually change the fonts used in the window to common fonts.

Issue: WindowViewer can crash, if a quick function that makes a set of very
specific calls, is used within the window's OnShow or WhileShowing
window script.
Workaround: Avoid using Quick Functions in a window's OnShow or WhileShowing
window scripts that meet the following conditions:
The OnShow or WhileShowing window script of a window, calls a Quick
Function that does the following:
• The Quick Function from Window1 opens a second window that causes
Window1 to close.
• Window2 must also contain an ActiveX® control.
• This same Quick Function from Window1 also calls a function of the
ActiveX control in Window2.
• An ActiveX dialog appears as a result of the function call.
When the ActiveX control dialog is closed, the Quick Function is complete
and it attempts to return to the Window1 window script, which is already
closed.
There are many ways to avoid this situation. The possible solution is to split
the quick function into 2 functions.
• Function1 - Opens Window2 and remains in the window scripts of
Window1.
• Function2 - Calls the ActiveX function and is placed in the window
scripts of Window2, or could be placed in a Condition or Data Change
script.
Issue: InTouch Advance Formatting shows improper Last Known Value.

Description Indirect Analog Value animation can show improper status if the indirect
reference is changed from a good point to a bad point without closing the
window first.
This mainly applies to stand alone advanced formatting animations with no
additional IO quality indicators. This is only seen in generic windows that use
IOSetRemoteReference or InDirect tags to change the connected IO points
shown in a window while the window remains open.
The issue only occurs when a good reference connection is changed to a bad
reference that has no last known value.
Workaround: Wherever possible, use HMI Control Edition symbols and animations. HMI
Control Edition Symbols and Faceplates include status indicators that
identify Bad and Out Of Service Io Points. Otherwise, Include quality state
indicators on generic windows where this condition can occur.

Issue: While using the Historian Client - Report Function via Microsoft Word, you
get the following error message:
"The file contains macros with an expired or revoked signature.”
Workaround: To determine the name and location of the add-in file that contains the
expired certificate, follow these steps:
1. On the Tools menu in Word, point to Macros, and then click Security.
2. Select the Medium security setting, and then click OK.
3. Quit Word. Quit Outlook if you are using Word as the e-mail editor.
4. Restart Word.
5. When the Macro Security dialog box appears, the first three lines
display the location, file name, and software vendor for the file that
contains the expired certificate. For additional information about the
expired certificate, click Details.
6. Click Disable Macros.
To restore the High macro security setting, follow these steps:
1. On the Tools menu, point to Macros, and then click Security.
2. Select the High security setting, and then click OK.
After you determine the source of the expired certificate, you may decide to
trust this software vendor. If that is the case, use one of the two following
methods to continue using the add-in file and to prevent the "expired or
revoked signature" message from appearing when you start Word.
Note Macros may contain viruses. If you do not recognize the software
vendor on the certificate, delete the add-in file to prevent the "expired or
revoked signature" message from appearing. For help with deleting the file,
click Help on the Start menu in Microsoft Windows, and search for the
"deleting files" topic.
Method 1: Change the Startup Path in Word to the Folder that Contains the
Add-in. Use the following steps to change the startup path in Word to the
folder that contains the add-in file:
1. On the Tools menu in Word, click Options.
2. Select the File Locations tab.
3. In the File types list, select Startup, and then click Modify.
4. In the Modify Location dialog box, select the folder that contains the
add-in file with the expired certificate, and then click OK.
5. In the Options dialog box, click OK.
6. On the Tools menu, point to Macros, and then click Security.
7. Select the Trusted Sources tab, and verify that the Trust all installed
add-ins and templates checkbox is selected.
8. Click OK and then restart Word to verify that the "expired or revoked
signature" message does not appear.

Issue: Data Entry boxes do not open on Secondary Monitor when InTouch is not
configured for Multi Desktop on multi Monitor stations.
Description: You can drag Popup windows such as Alarm Panels and Detail Displays.
These windows contain User Input Animations. When you select a field to
enter data, the Data entry box only appears on the Closest edge of the Primary
Monitor.
Workaround: For Data Entry Boxes to appear on the secondary monitors, the
Multi Desktop setting must be enabled in the win.ini file, as described in the
section “Multi Desktop setup” in Window Construction User’s Guide
(B0750AS).
Issue: The SMC Error messages are shown, if WindowMaker is running in the
background and the DEV button is pressed to start WindowMaker. The error
message reports that WindowMaker is already running.
Workaround: You can ignore these error messages.
Issue: The desktop font effect property may change from “Standard” to
“ClearType” during a Control Software installation, and may affect the font
size in the Control HMI displays.
Description: If the font property is set to “Standard” and you have performed a Day 0
software installation to upgrade to Control HMI, the property may have
reverted to “ClearType”.
If you plan to use remote desktop, check the Windows display settings on
each station after Control Software upgrade to help ensure that you are still
using the correct font settings.
Perform the following steps to help ensure that the font property is still set to
“Standard” after the upgrade:
1. Open the Display Properties dialog box by right-clicking on the Desktop
and selecting Properties.
2. Select the Appearance tab.
3. Click Effects.
4. Verify that Use the following method to smooth edges is selected, and
the drop-down list is set to Standard.
5. Click OK and close the Display Properties dialog box.
Workaround: If the setting has reverted to “ClearType”, change it back to the “Standard”
font setting after the upgrade.

Issue: An issue occurs when the Wonderware Historian Server is unavailable.

(CAR:1010580)
Description: If the Wonderware Historian server becomes unavailable, WindowViewer
software may freeze while trying to re-establish the connection to the server.
WindowViewer software recovers after 10 seconds. This occurs if any
connection has been established between WindowViewer software and the
Wonderware Historian server, even if windows with trend objects are not
currently opened.
Workaround: Before disconnecting the Wonderware Historian server, log off from the
server.
Using a Wonderware Historian Client trend, for example, a Scratchpad Trend
window, perform the following steps:
1. Right-click on the trend graph, and select Tools > Servers.
2. Select the connected Server, and click LogOff to log off from the
connected server.
In addition, use the settings in Framer software to configure the timeout
values used by the Wonderware Historian Client trend objects, if needed.
The default setting is 10 seconds, but this time can be increased or decreased
as necessary.
Issue: Setting alarm printers to print to a file causes CPU utilization issues.
Description: If you set an alarm printer to print to a file, the spool.exe process could use up
to 99% of the CPU usage.
Workaround: Avoid using the print to file option on alarm printers. If spoolsv.exe is causing
99% CPU usage, then there may be a corrupted print file stuck in the
system32 folder. To resolve the issue, perform the following steps:
1. Open Windows Control Panel > Administrative Tools > Services. Stop
the Print Spooler service.
2. Turn off the printer.
3. Navigate to C:\WINDOWS\system32\spool\PRINTERS and delete the
files there. You may find files similar to 00002.SHD or 00020.SPL, for
example.
4. Turn your printer back on and restart the print spool service.
5. Spoolsv.exe should be at 2% or less.

Issue: The Control HMI may shut down unexpectedly when restarting.
Description: Sometimes when restarting the Control HMI, the WindowViewer software
may shut down unexpectedly.
Workaround: In the Control HMI’s Restart dialog box that displays, perform the following
steps:
1. Select Restart Control HMI
2. Clear Terminate InTouch Processes, if WindowMaker™ software is
running.
3. Click Continue.
The Control HMI is restarted.
Issue: Momentary contact tags should already be on scan.

Description: The Quick Function hmiMomentaryContact provides an interface for setting
and resetting discrete values within a specified time limit. The tags that are
set using this Quick Function should already be on scan as part of a current
window. If not, the momentary contact does not work.
Workaround: Verify the tags referenced in the hmiMomentaryContact QuickFunction have
also been configured as tags in an updating animation link.
Issue: Opening Alarm Panel displays error message upon accessing an .XML file.
Description: If an alarm query string has been configured that is too long, the Alarm Panel
windows cannot load the named alarm query. An error message is displayed
by the Control HMI. Alarm Query strings need to be less than a total of 115
characters. Framer software incorrectly allows query strings of up to 132
characters.
Workaround: Use the Framer software to reduce the number of alarm providers listed in the
alarm query string. Restart the Control HMI after making edits in the Framer
software.
Issue: The default SQL login value for the software does not match the required
USERID for the SQL server. (CAR:1011216)
Description: When logging on to the MS SQL server on the AlarmDB panel, the login
times out and fail the first time because the SQL login default user IDs do not
match.
Workaround: Modify the USERID for the SQL login by editing the Framer software
settings. If you are using the AlarmDB panels, you need to set the Login Info
in Framer to match. Refer to Framer and Alarm Management User's Guide
(B0750AR) to edit the settings.

Issue: WindowMaker software cannot be reopened once it is opened and closed.

Description: WindowMaker creates a file appedit.loc when a user is editing an application.
This file is not deleted if WindowMaker exits abnormally. The next time
WindowMaker software is opened, this file keeps WindowMaker from
starting with a message that the application is already being edited.
Workaround: After verifying that nobody is editing the application from a remote station,
you can remove the appedit.loc file from the application folder. The
application folder is typically D:\InFusion-View.
5.2.1 Faceplates
Issue: Some Boolean parameters that are given Secured or Verified Write security
configuration, cannot be modified from Faceplates.
Description: One method of changing the value of a boolean parameter in a Control HMI
faceplate is to select the Boolean, which enables the Toggle button, then
selecting the Toggle button. If the selected Boolean parameter has been
configured as a Secured or Verified Write parameter, then the Toggle button
does not work. This is not an issue for Boolean parameters that are directly
toggled through a single button click, that is, selecting the Manual/Auto
button works even if the corresponding parameter has been assigned a
Secured or Verified Write security status.
Workaround: Select the Boolean parameter to be toggled. This copies the parameter name to
the tag bar. Open the Watch Panel, and assign the select parameter to the
Watch Panel. Change the value of the parameter to the desired value, either 0
or 1. The Secured or Verified Write dialog boxes are displayed.
5.2.2 BlockSelect
Issue: Multiple compounds cannot be turned on or off if the .ON parameters have a
Secured or Verified Write status.
Description: When selecting multiple compounds to turn on or off, if one of the .ON
parameters has a Secured or Verified Write status, than setting the .ON
parameter of subsequent compounds stop working.
Workaround: Select single compounds to turn on or off.

5.2.3 Framer Software

Issue: Alarm Query names must be unique.
Description: Within the AlarmQuery property configuration, up to 10 additional alarm
queries can be configured. The names for each of these queries must be
unique within the AlarmQuery column. Framer software does not enforce this
uniqueness.
Workaround: Verify that alarm query names are unique.
5.2.4 Trending
Issue: Trend line is flat when switching to updating mode.
Description: When switching Scratchpad trends from historical to updating mode, and
zooming to the current time, the trend line may go flat.
Workaround: Refresh the trend to display the current data.
Issue: Remote InFusion View fails for the option Automatic startup with out task
bar.
Description: When InTouch is installed at a location other than
C:\Program Files\Wonderware, remote InFusion View fails for the option
Automatic startup with out task bar.
Workaround: Open the file InFusionViewStartupService.bat located in the folder
C:\Program Files\Invensys\InFusion\View\Tools\
Modify the path in the following line to indicate the correct install path for
InTouch:
if exist “C:\Program Files\Wonderware\InTouch\view.exe”
5.3 Access Manager

This section presents a list of known issues within Access Manager software. If
available, a workaround allowing the user to bypass the issue is documented as
well.
5.3.1 InFusionSyncService
Issue: Deployment or Refresh of History/Security does not proceed.

Description: The deployment does not proceed and an error is returned indicating that
Deployment or Refresh cannot be done while Refresh of
History_Security is ongoing. workstation refreshing
Workaround: If a history security refresh is happening, wait for it to finish. If there is no
refresh currently running, verify that the “InFusionSyncService” is running on
the Galaxy Repository and try again. The “InFusionSyncService” might need
to be manually started.

Issue: IDE operations can become locked out on all workstations if a Control Editors
operation terminates abnormally.
Description: When an IDE abnormally terminates during any operation that uses the Sync
Agent mutex, such as a deploy, refresh of history and security data, bulk
generate or bulk import, the mutex remains locked until all instances of the
IDE on that workstation are shutdown and the IDE is restarted. This results in
all other IDE instances on other workstations being locked out until this is
done.
Workaround: Shut down all instances of the IDE on the workstation where the IDE
terminated abnormally while performing the operation that required the mutex
and then restart the IDE on that workstation.
If this cannot be done or does not allow locked operations from being
performed then shut down all instances of the ArchestrA IDE on all
workstations and then use the Sync Service utility to stop and restart the
service. After the service is restarted, instances of the ArchestrA IDE can be
restarted on the workstations.
Important Note: When stopping and restarting the Sync Service, if all
instances of the ArchestrA IDE on all workstations are not shut down and an
IDE is currently performing a Control Editors operation such as a deploy,
refresh of history and security data or a bulk operation, this could cause
instability in the system depending on the operation being performed. Be sure
to shut down all instances of the ArchestrA IDE before using the Sync Service
utility to stop and restart the service.
Issue: The InFusionSyncService utility is not working when a client station is

installed as Operator Station (FoxView)
Description: In some cases during deployment, the Deployment dialog box shows the
validation error “Check if Syncagent is running on Galaxy Server”.
Workaround: To fix the issue do the following steps:
1. Check if the InFusionSyncService service is running on the Galaxy
station. If service is not running, then manually start it.
2. If service is running, check if the client station has the D:\Program
Files\ArchestrA\Framework\Bin\GlobalDataCache\PlatformMapping\Pla
tformMapping.xml file. If it does not have this file, you can either
manually copy the file from the Galaxy station, or undeploy/redeploy the
platform.

5.3.2 I/A Series Alarm Provider

Issue: Alarm Provider is not receiving alarms in MM mode when the Message
Manager is recommitted/installed on the system after the Control Software
installation.
Description: The installation process disables the Message Manager. However, if the
Message Manager is installed on a system where the Control Software is
already present, then the Message Manager would interfere with the operation
of the Alarm Provider because the recommit process turns on Message
Manager processes.
Workaround: Open Windows Control Panel > Administrative Tools > Services console.
Select the service named MessageManager - Internal Monitor from the list
view and double-click on it to open the service panel. Set the startup-type to
“disabled” and reboot the workstation. This step is required for the Alarm
Provider to work correctly on workstations where the Message Manager is
configured/installed after the installation.
5.3.3 I/A Series History Provider

Issue: The values for I/A Series 32 bit Packed Boolean parameters (OM_L_PKBOL)
are not historized correctly within Wonderware Historian software.
(CAR:1008971)
Description: The ArchestrA MX protocol does not provide an unsigned data type.
I/A Series data types are converted to the best equivalent MX data type. In
this case, the closest type is an MxInteger (32-bit signed). Unfortunately, this
conversion from an unsigned value to a signed value can cause the data to be
misrepresented in Wonderware InSQLsoftware, when the sign bit is high.
Workaround: None
Issue: Unnecessary failover after reconnecting disconnected The Mesh network

cables
Description: When disconnecting The Mesh network cables from the primary collecting
workstation, the backup takes over as it should. However, after reconnecting
The Mesh network cables to the primary collecting workstation, the history
app engine (<letterbug>_AppH) transfers right back to the primary collecting
workstation instead of staying on the backup. This does not occur if the
primary workstation is rebooted. This does not occur if the redundant
workstations are directly connected by a dedicated Ethernet crossover cable.
Workaround: Use a crossover cable for the RMC (Redundancy Message Channel) between
the redundant workstation pair.

Issue: There may be a 3 to 4 minute delay before trend updates after the reboot of the
primary (active) then backup workstations.
Description: If a backup workstation reboots while it is currently active, it takes 3 to 4
minutes before the History app engine (that is, <letterbug>_AppH) reverts
back to the primary workstation. This causes a 3 to 4 minute delay before the
trend starts to update again.
Workaround: The easiest workaround is to avoid reboots. Alternately, before you reboot a
backup Historian collector in active mode, you can toggle the
LTRBUG_AppH.Redundancy.ForceFailoverCmd in the Primary collector
engine in the Object Viewer, or you can create an Control HMI display that
monitors the status of the Redundant Engine parameters and enable change-
over between Primary and Backup collector engine as required.
Issue: Wonderware Historian Client retrieval does not give Full retrieval mode for
forced storage data.
Description: To query forced storage data, the wwRetrievalMode must be set to Full.
However, Wonderware Historian Client software only offers Cyclic and
Delta. For example, in Wonderware Historian Client Query, with Query type
History values, in the Columns pane, the Mode option in the Retrieval tab
only shows Cyclic and Delta options.
Workaround: After retrieving the data in either Cyclic or Delta mode, go to the Results
pane and click the SQL tab. In the line with wwRetrievalMode, change the
Cyclic or Delta to Full and click the Data tab to refresh the data display. This
gives all values for the tag for the requested time range, including duplicate
values.
Issue: An aahMDAS message may appear: Adding tag <tag> failed

(database error).
Description: On rare occasions, the above message has been seen upon adding a tag to be
historized. The tag is added to the History object, opened in an OM list, and
registration with Wonderware Historian Server requested, but the above error
occurs, preventing the tag from being registered with Wonderware Historian
Server.
Workaround: In the Control Editors, make an innocuous change to a history field for the tag;
for example, add a space in the description, and redeploy the block. This
results in the History object receiving a modify request, which results in an
unregister and subsequent register of the tag with Wonderware Historian
software. Such modifies have resulted in successful registration with
Wonderware Historian software and subsequent historization of the tag’s
samples.

Issue: Trends flatline to non-zero values when app engine is unable to connect to
Wonderware Historian software. (CAR:1008547)
Description: This is seen on a redundant app engine. Example scenario: disconnect the
I/A Series Mesh network from the active engine. Standby takes over and trend
data during failover is <null> as expected. If you reconnect the network and
repeat with new active engine, this time the trend displays the last known
value as a flat line, instead of trending an <null> data value. If you repeat with
the same symptom, the trend flatlines and the active app engine is unable to
connect to Wonderware Historian software.
Workaround: None
Issue: After failover, the History app engine may occasionally remain in the Off
Scan state.
Description: If you perform a failover by powering off the active collecting workstation (or
by disconnecting The Mesh network cables), the standby workstation takes
over and becomes active, but sometimes the AppEngine remains in the Off
Scan state.
Note Be sure that for a redundant app engine the Restart the engine when it
fails checkbox is unchecked. When this option is checked, and the
workstation of the active engine is powered down, the standby has been seen
to take over, but then the app engine shows a status in the SMC of “Shutdown
(stop failed)”.
Workaround: None
Issue: If The Mesh network cables are disconnected from one collecting workstation
(of a redundant pair of collectors) to force a failover to the backup collector,
the new active application engine is unable to connect to the Wonderware
Historian software. (CAR:1008550)
Description: If you disconnect the active workstation from The Mesh network, the standby
workstation takes over, but sometimes the history app engine cannot connect
to the Wonderware Historian.
Workaround: Stop and restart the app engine and verify that it has connected to the
Wonderware Historian by looking for the appropriate MDAS entry in
DataAcquisition display in Management Console for the Wonderware
Historian in SMC.

Issue: The I/A Series History Provider may lose data during steady state collection,
during deployment of history configuration, and after recovery from store-
forward mode, if CPU utilization exceeds 90%.
Description: If a CPU intensive operation occurs on a collecting workstation, one or more
samples may be missed and is not historized. This issue also occurs between
the I/A Series Object Manager and the IADAS and between the IADAS and
the Wonderware DAS Engine. This is an issue related to process priorities of
application engines, and so forth. AppH stays running Off Scan after forcing
AppH to return to Primary collecting workstation after disconnecting
I/A Series cables from redundant collecting workstation.
Workaround: Avoid performing CPU-intensive operations on workstations collecting
historical data. This includes, but is not limited to, deploying objects to the
workstation or deploying I/A Series blocks in compounds with its “Collecting
workstation letterbug” of the workstation. Only perform the CPU-intensive
operations during non-critical periods of operation to avoid missing samples
during critical periods.
Issue: BulkHistory primitive may have different number of tags.

Description: The History object uses the BulkHistory primitive (BHP) to access the
Wonderware Historian. The BHP attributes are prefixed with
HistPrim.BulkHistory1 in the Object Viewer. After several power fails of
redundant workstations, it was observed that the BHP had more tags (as
evidenced by the _Tagnames, _TagKeys, and RegisteredAttrCnt attributes)
than the History object (HistPrim.TagCntTotal). The _Tagnames and
_TagKeys attributes are an optimization (to speed up registration on a restart)
and have no ill effects if there are too many (they are not referenced), and only
result in slower registration on startup if too few.
Workaround: None
Issue: Checkpoint causes periodic Historical data dropouts.

Description: The periodic checkpoint of the history application engine “AppH” can cause
Historical data dropouts during the time the checkpoint file is being written.
This can occur if the attribute with the BigString type in the I/A Series History
Provider is very large, because the Description and/or On/Off Message strings
are long and/or there are a large number of tags.
Workaround: Set the checkpoint period to be very long, so this issue does not occur often or
occurs at a non-critical point in the process. Do not use long strings in the
Description and/or On/Off Message strings when there are a large number of
history tags configured for a collector.

5.4 Control Editors

This section presents a list of known issues within the Control Editors v5.0 or
later subsystems. If available, a workaround to bypass the issue is documented
as well.
5.4.1 Control Editors Multi-User Access
5.4.1.1 Summary
The Control Editors can exhibit cases of data inconsistency under certain
situations. After multi-user access to the same CP, where the operations
involve the ECB Compound, it is possible to see a mismatch of ECBs in the
ECB Compound and the actual modules (FCMs, FBMs, or devices) assigned
to the CP.
5.4.1.2 Known Use Cases Exhibiting Behavior

1. I/O Assignment and Module Unassign/Delete/Assign/Bulk
Create/Rename Operations:
If one user is saving I/O assignment information from the CP Editor or the
Strategy Editor and at the same time another user is unassigning, deleting,
assigning or renaming modules from the same CP, then a data
inconsistency could occur. The users must be accessing the same
compound for the issue to manifest itself.
2. Moving ECBs and Module Unassign/Delete/Assign/Bulk Create/Rename
Operations:
If one user is moving ECBs from one compound to another (via the CP
Editor Move ECBs tab) and another user is unassigning, deleting,
assigning or renaming modules on the same CP, data inconsistency with
ECBs may occur. The users must be accessing the same compound in
order for the issue to manifest itself.
3. Import/Export and Module Unassign/Delete/Assign/Bulk Create/Rename
Operations:
If one user is importing modules into a CP and another user is
unassigning, deleting, assigning or renaming modules on the same CP,
data inconsistency with ECBs may occur. The users must be accessing the
same compound in order for the issue to manifest itself.

4. ECB Compound Editor usage and Module Unassign/Delete/Assign/Bulk

Create/Rename Operations:
If one user opens the ECB Compound editor while another user is
unassigning, deleting, assigning or renaming modules at the same time, on
the same CP, data inconsistency with ECBs may occur. The users must be
accessing the same compound in order for the issue to manifest itself.
5. Bulk Data Generation (Move ECBs and ECB Update Operations) and
Module Unassign/Delete/Assign/Bulk Create/Rename Operations:
If one user runs bulk generation updates (Move ECBs and ECB updates)
while another user is unassigning, deleting, assigning or renaming
modules on the same CP, data inconsistency with ECBs may occur. The
users must be accessing the same compound in order for the issue to
manifest itself.
5.4.1.3 Symptoms
If at the end of an operation, the ECB Compound of a CP is left in a checked
out state (red checkmark) and another user is in fact not editing it, then a issue
may have occurred. To verify, open the ECB Compound Editor and go to the
ECBs tab. The selected tabbed page may indicate an incorrect number of
ECBs related to the number of FBMs and devices hosted by this CP.
5.4.1.4 Workaround
There are many different workarounds to consider. During the workaround
procedures listed below, the following dialog box may appear.
Figure 5-1. ArchestrA IDE
If this dialog box appears, perform the following steps:

1. Exit all IDE sessions.
2. Stop the Galaxy Repository Service. On the Galaxy Repository Server,
open a command prompt window and execute the command net stop
aaGR.
3. Restart the IDE (restarts the Galaxy Repository Service automatically).

5.4.1.4.1 ECB Compound Left in a Checked Out State

The ECB compound must have one of the following operations applied:
Check-In or Undo Check-Out. In order to determine which operation to
perform, use the following logic.
1. Open the ECB Compound and other compounds hosted by the CP.
2. Match up the ECBs in the compound(s) to the modules
(FCM/FBM/devices) assigned to the CP.
3. If there are orphaned ECBs, then perform Undo Checkout on the ECB
Compound.
4. If there is a matching list of ECBs with Modules, then perform a Check-
In on the ECB Compound.
5. Proceed with the rest of this workaround section if you still have orphaned
ECBs after the operation.
5.4.1.4.2 Orphaned ECBs (ECBs without a Matching Module)

If the ECB Compound is left checked out after the operation is complete, the
compound must be in a checked in state in order to proceed with the
workarounds.
1. Export/Import CP to synchronize the FCMs/FBMs/devices and ECBs:
a. Using the Deploy Utilities > Synchronize Deploy Status context
menu of the CP, mark the entire CP hierarchy as undeployed (both
I/A Series/Control Core Services and ArchestrA).
b. If the ECBs need to be marked undeployed, use the Deploy Utilities >
Selective Upload/Deploy context menu of the CP, and mark all of the
ECBs as undeployed.
c. Export the CP. The contained FCMs/FBMs/devices also get exported
automatically.
d. Delete the CP/FCMs/FBMs/devices.
e. Import the CP. The contained FCMs/FBMs/devices also get imported
automatically.
f. Select the Deploy Utilities > Synchronize DBs context menu of the
CP, which synchronizes with the deployed ECBs in the imported CP.
2. Create a new CP:
a. Create a new CP.
b. Using the Deploy Utilities > Synchronize Deploy Status context
menu of the old CP, mark the entire CP hierarchy as undeployed (both
I/A Series/Control Core Services and ArchestrA).
c. If the ECBs need to be marked undeployed, use the Deploy Utilities >
Selective Upload/Deploy context menu of the old CP, and mark all of
the ECBs as undeployed.
d. Move the contents of the old CP to the new one.
e. Delete the old CP.

f. Rename the new CP to match the old one.

g. Select the Deploy Utilities > Synchronize DBs context menu of the
CP, which synchronizes with the deployed ECBs in the new CP.
5.4.1.4.3 Missing ECBs (Modules without Matching ECBs)

1. Unassign and then reassign the FCMs/FBMs/devices with missing ECBs
from the affected CP to synchronize the ECBs.
a. Unassign the FCMs/FBMs/devices with missing ECBs.
b. Reassign the FCMs/FBMs/devices.
5.4.2 General
Issue: The Enhanced Needs Redeployment indicators do not work for compounds
and ECBs.
Description: Compound parameters can serve as connection sources or connections sinks.
Similarly ECBs can serve as a connection source. The PRIMARY_ECB and
the STATION blocks can also have parameters that are sources.
ECBs themselves can be used as non-parameter connections. For example
they are used to form BLOCK - FBM links using IOM_ID. They can also be
used to establish Device-Module dependencies using the PARENT attribute.
For all these types of connections, when the source is modified, the sinks are
not marked as needing redeployment.
In addition, IOM_ID and PARENT parameter changes are not allowed if
there is an associated deployed sink.
Workaround You should manually identify the connections that start from a
compound/ECB or end in a compound/ECB and manually re-deploy them.
For the IOM_ID and PARENT attribute, the sink blocks need to be
undeployed before the associated module/ECB can be changed.
On Compound rename, all contained ECBs and blocks need to be identified
and their sinks listed and redeployed.
Issue: If the compiler's debug option is turned on, unsuccessful compiles are not
clearly identified
Description: The user can set the “NOCLEAN_ST_TEMP” flag to debug unsuccessful
compiles. The flag helps prevent the intermediate compile results from being
deleted. If this flag is used, the user should clear it after debugging.
Otherwise invalid temp files are used on subsequent compiles.
Workaround Clear the “NOCLEAN_ST_TEMP” flag after debugging is done.

Issue: When a compiled block template is instantiated on a strategy, the block has to
be recompiled.
Description Due to technical limitations, block templates are not notified when their
library include files are modified. So, when they are instantiated on a
strategy, the compilation may already be obsolete.
To avoid possible issues with out-of-date compile statuses, the system forces
the user to re-compile after the block is instantiated on a strategy.
Workaround: Compile after instantiating the block on a strategy.
Issue: Block deploy status is not refreshed until the strategy is re-opened.
Description Control Software allows the use of enhanced deploy indicators. When a
library include file is modified or a source connection is changed, deployed
sink blocks are marked as needing redeployment.
However Sink block deploy statuses are not updated when the strategy is
being edited and a source connection or an associated library include file is
concurrently modified in another session. The current edit session deploy
status is not refreshed till the strategy is closed and re-opened.
Workaround: Close the strategy and re-open to see the new block status.
Issue: In some cases, blocks are incorrectly marked as needing redeployment to be

marked as needing redeployment.
Description When a library or source is changed, sink blocks are marked as needing
redeployment. The following scenarios are exceptions:
• In an edit session, if a block was added and deployed using Strategy
Editor, it does not track source changes until the following checkin. Once
the block is checked in, it tracks the source changes.
• If the sink block connection is changed and deployed using Strategy
Editor, sources should only be changed after the strategy is checked in.
Workaround: Checkin the strategy as soon as possible after Strategy Editor deployment, if
there are many sources that could be modified.
Issue: LMX, BRO and CDI error associated with platform objects are being
reported into the SMC log.
Workaround: Undeploying the platforms that report the issue, and redeploying these
resolves the issue.

Issue: The IO assignment for ISCM FBMs generates a system message.

Description: The IO validation does not work for ISCM FBMs and the ISCM FBMs reject
IO assignments.
Workaround: Open the Block Editor and set the IOM_ID value manually.
Issue: Printing sequence block code generates exception error.

Description: Unable to print the sequence block code from the Control Editors, if Control
Editors are started from the Control HMI and the Control HMI is started
when the workstation is rebooted.
In contrast, the print function works correctly if the Control Editors are
started manually from the Windows Start menu.
Workaround: Start the Control Editors from the Start menu and not from the Control HMI
menu item.
Issue: The following message appears in the SMC log.

platform not responding
Description: If there are frequent time keeper updates, you may observe that Control
Software stations do not respond and the displays do not connect.
Workaround: To recover, reboot the workstations.
Issue: You can use the underscore character for LIKE syntax on the Find dialog box
when you search for Tagname Like and Hierarchical Name Like.
Description: Standard LIKE syntax (supported by ArchestrA software) supports the use of
a percent sign (%) or an underscore. The LIKE syntax also allows you to
escape the percent sign (%) and underscore (_) characters when specifying
search strings. To escape these characters, enclose each one within a square
bracket.
For example, to find all compounds beginning with an underscore, select the
Tagname Like field, select Compounds, and enter a search string of [_]%.
Workaround: Use the square brackets [] to escape an underscore or percent sign.
Issue: Performing an Assign To operation lists all applicable objects in the entire
Galaxy.
Description: The Assign To dialog box lists all applicable objects in the entire Galaxy,
resulting in an unusable list when several hundred objects might be involved.
A Scope field has been added to the dialog box to allow you to specify a
scope, largely reducing the number of entries that you need to look at. For
example, you can now limit the number of controllers to which you are
attempting to assign a compound by first picking the equipment unit to which
the desired controller is assigned.
Workaround: You should specify a Scope in order to speed up performance and reduce the
number of entries shown in the Assign To dialog box.

Issue: An unexpected termination of a bulk operation may leave the station in

indeterminate state.
Description: If the IDE shuts down unexpectedly while performing a bulk operation (bulk
create, bulk generate, import, export, cascade deployment of a controller or
equipment unit), the mechanism to help prevent multiple bulk operations will
remain in effect.
Users on other platforms may receive a message that a bulk operation is in
progress on the platform where the IDE shut down when, in fact, no bulk
operation is running.
Workaround: Shut down all instances of the IDE running on the platform and start up a
single instance of the IDE. This clears the mechanism helping to prevent bulk
operations.
Issue: Control Software tree views do not update

Description: After renaming or assigning objects, the tree views do not update. The only way to
see the results of these operations is to close the views entirely and reopen.
Workaround: This happens if there are licensing issues. If the following dialog box is seen
during the Control Editors startup, this issue is likely to occur:
The short-term solution is to answer Yes to view the license information, then
close the subsequent dialog box. The tree views operate properly. This must be
done every time the Control Editors are invoked and this dialog box appears.
The long-term solution is to correct the licensing issue. This dialog box indicates
that the system is running with insufficient licenses. Additional licenses need to be
added for proper operation.

Issue: In some cases, when a propagation operation (usually via a check-in

operation) is unsuccessful, there is no means for the user to know how many
strategies are unable to propagate, how many succeeded, and other similar
metrics.
Workaround: To help ensure that the user is informed of any unsuccessful propagations,
enable the “Trace” log flags in the SMC Log Flag Editor on the GR node as
follows:
• Open the SMC application. In the left-hand pane, open Log Viewer ->
Default Group and select the GR node.
• Open the Actions menu and click Log Flags. The Log Flag Editor opens
for your selected log file.
• In the left-hand pane, select BlockEventSupporter. The log flags for
BlockEventSupporter appear in the upper right-hand pane. Check the
“Trace” checkbox.
• In the File menu, click Apply. When prompted by a dialog box, click
Yes, and then click OK. Close the Log Flag Editor.
Subsequent propagation operations report the strategy instances that
propagated successfully and the strategy instances that failed on GR
node. It reports all the strategy names that are affected by the
propagation.
To resolve any propagation failures that occur, determine which strategies

were part of the check-in operation, and either undo or redo the check-in
operation, as follows:
• If you have the “Trace” flags enabled for the GR node, then the log file
contains a list of the checked-out strategies.
• Otherwise, you can compile a list of the checked-out strategies using the
Find dialog box. Specify the SEARCH CRITERIA equal to CHECKED
OUT.
For instructions on using the Find dialog box, refer to the chapter “Find
Dialog Box” in Configuration Utilities User’s Guide (B0750AZ).
• Once you have the list of checked-out strategies, you can resolve the
issue in one of two ways:
• To revert the database to its state prior to the propagation operation,
perform an “Undo Checkout” operation on the checked-out
strategies.
• To retry the propagation operation, verify that the “Trace” log flags
are enabled (as discussed above) and perform the propagation
operation again. If the operation is unsuccessful a second time, send
the log file to Invensys Global Customer Support (see “Purpose” on
page ix) and revert the database to its state prior to the propagation
operation as described above.

5.4.3 Direct Access
Issue: Direct Access Import/Export is unsuccessful on Off-ControlNetwork station.

Description Direct Access configuration files are not updated properly if Control
Software is installed in a non-standard location. The following files:
• Program
Files\Archestra\Framework\bin\Invensys\DirectAccess.exe.config
• Program
Files\Archestra\Framework\bin\Invensys\DirectAccess_Cmd.exe.config
Contain reference paths to D:\Program
Files\ArchestrA\Framework\Bin\IDEExtensions\ImportExport.dll
Workaround: Update the path, if the ArchestrA framework is installed in a different
location. Edit the file manually to update the path.
The DirectAccess.exe.config file as shipped is as follows:

<?xml version="1.0"?>
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="ImportExport"
publicKeyToken="d2d1064e7cd0412f" culture="neutral" />
<codeBase version="4.1.0.0" href="file:///D:\Program
Files\ArchestrA\Framework\Bin\IDEExtensions\ImportExport.dll" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
Update the path in the "codeBase" xml tag mentioned above to reflect the
actual installed path. Similarly, update the path for
DirectAccess_Cmd.exe.config.
Note that the Command prompt (cmd.exe) must be launched using the “Run
as Administrator” option (that is, right-click the cmd.exe executable and click
Run as Administrator). Any parent process using DirectAccess_Cmd.exe
must be launched with the “Run as Administrator” option as well.
Issue: If security is enabled for a Galaxy where there is a current Direct Access
session open, the change to security is allowed (even though Direct Access is
a second open session) and Direct Access is allowed to continue without
providing secure credentials.
Workaround: Close all Direct Access sessions before enabling security.

Issue: An issue exists when using the Direct Access MigrationFBM command and
existing Galaxy Objects. Renaming is unsuccessful when migrated FBM
tagname is in use.
Description: When using a Direct Access MigrateFBM command (<MigrateFBM
FBM100="FBMXXX" FBM200="FBMAAA"/>), the operation is
unsuccessful if an object exists in the Galaxy with the FBMAAA tagname.
Workaround Assume you have the following configuration:
FCP001
FBMXXX (100 Series, with ECB named MYECB1)
To perform the desired migration, migrate the 100 Series FBM to a
temporary, uniquely named 200 Series FBM:
<MigrateFBM FBM100="FBMXXX" FBM200="FBM444"/>
Then rename the resulting 200 Series FBM's contained name to the desired
name, “FBMAAA”. This can be done via the Control Editors or a Direct
Access command:
<RenameFBM OldName="FCP001.FBM444"
NewName="FCP001.FBMAAA" />
<RenameECB Compound="FCP001_ECB" OldName="FBMAAA"
NewName="MYECB1" />
The result of these commands is a 200-Series FBM, migrated from its
corresponding 100-Series FBM. The new FBM has a unique tagname, the
desired contained name, and the desired ECB name.
Issue: Exporting legacy (classic) I/A Series control station objects results in the
error “Object reference not set to an instance of an object.”
Workaround: When attempting a SQLTable export, the SQLExport operation is supported
only from the Galaxy Repository stations. Be sure to perform this operation
from a Galaxy Repository station.

Issue: Direct Access Script using BulkCompile command and subsequent

Deployment together in the same script is unsuccessful.
<?xml version="1.0" encoding="utf-8"?>

<DirectAccess>
<BulkCompile Strategy="COMPND11_001"/>
<DeployCompound Compound="COMPND11" Cascade="Yes"/>
</DirectAccess>
Workaround: Change the script to use a reset command between the BulkCompile of a
strategy and subsequent deployment. This checks in the strategy used by the
bulk compile.
<DirectAccess>
<reset strategy=”COMPND11_002”/>
<DeployCompound Compound="COMPND11" Cascade="Yes"/>
</DirectAccess>
5.4.3.1 Using Direct Access for Strategy Template

Distribution
Issue: Issues exist when using Direct Access for strategy template distribution.
Description: Running command file as it is: It is not recommended that the unedited,
exported command file be executed on Satellite Galaxies as it is. This
command file contains Create commands and Assignment commands that
fails if the objects already exist in the target Galaxy, causing some
undesirable results. For example, the script creates nested strategy
templates, then assigns them to the container strategy template. When the
script is run as it is and the nested strategy already exists, a new copy of the
nested strategy is created and then assigned to the container. The assignment
is unsuccessful and a copy of the nested strategy template is left in the
template toolbox.
Workaround: None

5.4.4 Bulk Data
5.4.4.1 General
Issue: Importing duplicate XML data into Bulk Data causes errors.
Description: When importing XML data with duplicate values for those already existing
in the Bulk Data object, the following error can appear in the Output
Window:
ERROR: Failed to enable constraints. One or more rows
contain values violating non-null, unique, or
foreign-key constraints.
One or more rows in the grid is marked with a red exclamation point. The
SMC log also contains the following messages:
Error BulkDataEditor BulkDataEditor Synchronize Views
Error: Key cannot be null. Parameter name: key
Workaround: The best way to avoid this situation is not to import XML data containing
duplicate values for data that is required to be unique (such as a compound
in the Compounds table or a strategy in the Strategies table).
Once duplicate values have been imported, you can either delete the
offending rows (rows with exclamation points) or close the Bulk Data Editor
without saving the data.
Issue: Regenerating nested strategies can fail when the base template for the nested
strategy has changed.
Description: If the base template of a nested strategy is changed and then the strategy is
regenerated, the following error occurs:
ERROR: Delete failed for strategy (Container object is
linked to its defining template
Workaround: To regenerate this strategy, it must be deleted first. Use the Delete feature of
Bulk Generation to delete the strategy first, and then regenerate it.
Issue: Connections to shared variables are not set during Bulk Generation.
Description: Block connections to shared variables are not set during Bulk Generation.
During the generation, the following message appears:
The string is not in a correct format
Workaround: Connections to shared variables must be configured manually in the
generated objects. Bulk Generation does not set these parameter values.

Issue: Bulk Generation does not set Compound Execution Order.

Description: Bulk Generation does not properly order compounds within a CP. This
information is also not extracted from either IACC or SaveAll imports.
Blocks are ordered properly within strategies and compounds. Strategies are
ordered properly within compounds.
Workaround: Bulk Generation does not set Compound Execution Order within the
controller. Blocks within the compounds are ordered properly, but the
compounds are not. Once Bulk Generation is complete for an entire
controller, you must manually adjust the execution order of the compounds
via the Compound Execution tab of the controller’s editor.
Issue: Occasionally, Bulk Generation does not include FBM228s from the
Hardware tab.
Description: The FBM drop-down selection list on the Field Device Instances tabbed page
can be missing valid FBM selections. This condition can occur if an FBM228
on the Hardware tabbed page Modules view lists in its Parent column an
FCP270 or FCM100 that exists in the Galaxy, but that parent is not defined in
the Hardware tabbed page Stations view, and the FBM228 is not yet assigned
to that parent.
Workaround: You can either add a row to the Hardware tabbed page Stations view to
define the parent, or assign the FBM228 to its parent.
Issue: ArchestrA names must be unique and do not allow a compound to have the
same name as an FBM.
Description: For example, consider a SaveAll on which the compounds have names
identical to FBM letterbugs, and you first generate the hardware, including
the FBMs, and then generate the Control database. During the generation,
you get an error message, the compounds cannot be created
because objects with the same names already exist.
You can resolve this by changing the actual name of the FBM and leaving the
contained name alone.
Workaround: ArchestrA does not allow any two objects in the Galaxy to have the same tag
name. In this case, compounds and FBMs have the same tag name defined in
Bulk Data. You need to change the Module column (Modules tabbed page)
to something unique in the Bulk Data grid but leave the Contained Name
unmodified. The only name I/A Series or Control Core Services software
uses for module names/letterbugs is its contained name under a controller.
This way the tag names are unique within the ArchestrA Galaxy however
within the control processor software the compound and FBM names are the
same.

Issue: Replace function pop-up message appears behind other windows in the
Bulk Data Control/Hardware tabs.
Description: When using the Replace function in the Bulk Data Editor (Hardware tab),
you can attempt to change a name to something more than six letters (or for
the Control tab, you can attempt to change the name to something long
enough to be invalid). Since this is a naming restriction, a pop-up appears
with the message that this action is not allowed. However, by default, the
pop-up appears behind the Replace window and takes screen focus.
When this happens, it may appear as if the Control Editors have frozen up
since there is no change when you click anywhere on the Control Editors
screen, in addition, the Cancel and X buttons for the Replace screen and the
Control Editors cannot be selected.
Workaround: In the Bulk Data Editor, if the string resulting from a Replace operation fails
cell validation, a system message could be displayed behind other dialog
boxes. This gives the impression that the Bulk Data Editor is not
responding. Look at the Windows Taskbar for additional dialog boxes that
may be displayed, bring them to the foreground, and acknowledge them to
continue.
Issue: When Bulk Generating from a SaveAll, a message is reported that indicates
an FBM240 is not valid with a GDEV block (this is incorrect).
Description: When you are bulk generating from a SaveAll, the message appears stating
that an FBM240 is not valid with a GDEV block. However, this is not
correct. This message is also reported during the Control Editors
configuration if this combination of FBM/Block is used. Using an FBM240
with a GDEV block is a valid combination.
Workaround: When connecting (via Bulk Generation or manually) the I/O of a GDEV
block to an FBM240, the following message appears.
Invalid IOM_ID value: F00001 (I/O Block - ECB type
mismatch).
This message can be ignored. This is not a recommended Block/ECB
combination, but the value is still set for the IOM_ID parameter and the I/O
connection is made.
Issue: In the Bulk Data Editor, the FCM field presents the default name instead of
the changed name even when the name of the FCM was changed.
Description: This issue appears when the Contained Name of the FCM is changed while
the tag name of the FCM remains unchanged. The Bulk Data Editor grids
display object tag names only, unless otherwise specified. The FCM can be
created with a tagname and a contained name having the same value, but
either can be changed independent of the other.
For example, the drop-down list could present the name F00400 (default
name) instead of F00004 (changed name).
Workaround: There is no workaround, but be aware of this issue when selecting from the
Bulk Data drop-down lists.

Issue: Bulk Data Copy/Paste does not add columns.

Description: When rows of data in the Bulk Data Editor are copied then pasted into a new
grid, columns from the original data source that do not exist in the target grid
are not added.
Workaround: When using the copy/paste function between Bulk Data objects, you need to
manually add missing columns to the target table before the paste operation.
Issue: The Bulk Generation restricts child device names to valid letterbug names.
Description: The Bulk Generation process incorrectly restricts child device objects
(DEV_ECBx) to valid letterbug names. Corresponding ECBs may still be
renamed to 12 character names.
Workaround: If a different name is desired, you can set the ContainedName in Bulk Data
for the child device.
Issue: The Find/Replace operation can produce inconsistent results when switching
views while the Find/Replace dialog box is open.
Description: When the view is switched while the Find/Replace dialog box is open, future
Find/Replace operations may produce incorrect results.
Workaround: Always close the Find/Replace dialog box before switching to a different
view.
Issue: When using the View Filter in the Bulk Data Editor, the Find/Replace
operation can produce inconsistent results.
Description: If the current Bulk Data grid view is being filtered via the Filter By option,
executing a Find/Replace operation may not work properly. This can result
in some text not being replaced as expected.
Workaround: Only execute text Find/Replace when View Filtering is disabled.
Issue: The first invocation of Bulk Data Editor on a newly installed station is slow.
Description: When the Bulk Data Editor initializes, it looks through the database for
available hardware and software types. This causes each of the objects to be
installed on the local system. This operation would normally occur at various
times as each object type is accessed via its own editor. This only happens the
first time the Bulk Data Editor is run from a newly-installed station.
Workaround: None. Wait for the operation to complete.

Issue: Placing multiple SaveAlls from the same configuration into separate Bulk
Data objects results in invalid peer-to-peer references.
Description: If multiple SaveAlls are imported into separate Bulk Data objects, peer-to-
peer connections which exist between the SaveAlls is not maintained
automatically.
Workaround: To retain correct connection references, all SaveAlls for the same
configuration should be imported into the same Bulk Data object.
Issue: The Bulk Data Editor cannot import values greater than 255 characters in
length.
Description: When importing into a Bulk Data object via Excel software or .CSV file
formats, individual cell values greater than 255 characters in length are
truncated to 255 characters.
Workaround: Cells with value lengths greater than 255 characters must be edited manually.
5.4.4.2 IACC Migration

This section describes issues you may encounter when migrating from IACC
and their workarounds.
5.4.4.2.1 Object Naming

Duplicate Names
IACC allows objects in different domains, or namespaces, to have the same
name. For example, IACC allows a compound to have the same name as a
strategy because they are in different namespaces. When these objects are
imported into Control Editors, one of the objects must be renamed because all
objects in the Control Software database must have unique names. To help
prevent this automatic renaming of objects, your IACC database should be
modified to remove these naming conflicts before migrating to Control
Software.
Illegal Characters
IACC also allows characters in object names that are not allowed in Control
Editors. The only allowable characters for object names in Control Editors are
letters, numbers, ‘$’, and ‘_’ (underscore). IACC objects using other characters
should be renamed before migration.
Devices (General)
Devices that are hosted by FBMs in the same controller that map to ECB201
blocks must have unique values for their device names, and therefore their
DVNAME parameter values. The DVNAME parameter is used to find the
matching ECB when bulk generating the migrated control scheme. If two
ECB201s in the same controller share a common DVNAME value, the ECBs
are not generated properly when migrated from IACC.

Issue: Migrated devices are not created correctly when migrated from IACC.
Description: When migrated IACC databases are Bulk Generated in Control Editors,
device ECB201s are matched by the value of the DVNAME parameter.
When an ECB is found under the same controller with a matching
DVNAME parameter, Bulk Generation assumes it is the ECB being
generated. It is then, as specified, move the ECB to a new compound,
rename it, and/or update its attribute values.
If two devices under the same controller share a common DVNAME
parameter value, Bulk Generation cannot distinguish between the two ECBs
and may update parameter values, rename the ECB, or assign it to a
compound incorrectly.
Workaround: Prior to migration, verify that no two devices under the same controller
share the same device name.
FF Devices
Control Editors restricts FF devices to have the same name as their
corresponding ECBs. IACC does not have this restriction. If an FF device does
not have the same name as its ECB, the Bulk Generation aborts after importing
the IACC database to Control Software.
Issue: Migrated FF devices are not created correctly when migrated from IACC.
Description: FF devices are required to have the same name for both the hardware and
related ECB. IACC does not place this restriction on these objects. When FF
devices with differently named ECBs are migrated from IACC, Bulk
Generation attempts to rename the ECBs and aborts.
Workaround: Prior to migration, rename the FF Device or ECB to match.
5.4.4.2.2 Strategies and Blocks

Blocks in Different Compounds
IACC allows you to assign individual blocks in a strategy to different
compounds from other blocks in the same strategy. Control Editors requires
that all blocks in strategy be in the same compound.
When strategies are imported into Control Editors via IACC export format,
these strategies are kept intact. All blocks in the strategy are assigned to the
default compound for the strategy as it was defined in IACC.
If the same control scheme were exported to the SaveAll format and then
imported into Control Editors, the blocks would remain in their respective
compounds, but all graphical strategy information would be lost.

Issue: Migrated IACC strategies do not assign blocks to the correct compounds.
Description: IACC allows individual blocks within a strategy to be assigned to a
compound different from the default compound for the strategy and other
blocks in the strategy. This is not allowed in Control Editors. The migration
from IACC through Bulk Data keeps the strategies intact and moves the
blocks in the strategy to the default compound of the strategy.
Workaround: Prior to migration, move blocks and/or break up strategies such that all
blocks in a strategy are assigned to the same compound.
Block Name Case Sensitivity

Blocks whose names differ only in case will not migrate properly.
Issue: Bulk Data IACC Import of duplicate named blocks

Description: Importing from IACC a strategy template containing 2 blocks whose names
differ only by case is not handled properly. Only one of the blocks is
imported. This is because all block names are in uppercase when imported
from IACC. One of the blocks must be renamed, and all references to it
must pick up the name change.
Workaround: Importing Strategies from IACC that contain blocks whose names differ
only by case produce invalid data in the Bulk Data tables.
For example, a Strategy containing blocks named Block1 and BLOCK1 are
defined in Bulk Data as BLOCK1 and BLOCK1 after import. These values
have to be manually changed via the Bulk Data Editor prior to Bulk
Generation.
Issue: Bulk Data IACC import does not handle some block connections. Only block
connections made in IACC that are “true” connections are migrated properly.
Connections that are entered as text or formula-calculated may not migrate
properly.
Description: Connections typed in as text in IACC are not translated to an appropriate
format for the Control Editors during Bulk Data import.
Workaround: When an IACC database is imported into Bulk Data, connections that are not
“true” IACC connections are not converted to ArchestrA format. These are
connections that may take the for C:B.P or :B.P but are entered as a text value
for a parameter in IACC. When imported into Bulk Data, they are not
converted to MyContainer.B.P, but are left as it is.

Input/Output Declarations
Issue: IACC allows different CSD instances derived from the same CSD template to
define different sets of external connection references.
For example, a template-derived CSD instance could reference two blocks
externally from parameters A and B. Another CSD instance derived from the
same CSD template could reference blocks externally from parameters
C and D.
Description: Control Editors restricts strategy templates and their derived instances to
have the same set of I/O declarations. These declarations are used to make all
external references from/to blocks in the strategy. When CSDs configured
this way are migrated to Control Software, the strategy instances are defined
in the Bulk Data object to have different sets of I/O declarations.
During bulk generation of the migrated IACC database, the user will see an
error message like the following:
ERROR: Strategy001: Input declarations do not match
template: Input2
Workaround: To correct this, the Bulk Data object containing the migrated IACC database
can be modified to define the missing declarations in the strategy template.
Issue: Input/Output declarations not built properly during IACC migration of CSD
template-derived strategy instances.
Description: Input/Output Declarations are used to make external references to/from
blocks in strategies. When strategies are derived from templates, the defined
set Declarations for the strategy must exactly match those of the template.
When these CSD template/CSD instance combinations are migrated from
IACC, the set of declarations for template and instance are not defined to be
the same. The Bulk Generation will generate errors like:
ERROR: Strategy_001: Input declarations do not match
template: Input2
Workaround: All declarations that are generated for instances must be added to the defining
template in Bulk Data before generation. For example, if the migration
created Input1 and Input2 on Strategy_001 and Input3 on Strategy_002, and
these strategies are both derived from $Template1, then Input1, Input2, and
Input3 must all be added to $Template1 in the Strategy I/O table of Bulk
Data.

FBM Assignments to ZCP270
Issue: IACC allows FBMs to be contained by FCM100s, which are contained in a

ZCP270, but Control Editors allows FBMs to be contained only by
FCM100s.
Description: IACC allows FBMs to be contained by FCM100s contained in a ZCP270, for
example:
ZCP100
FCM100
FBM101
or to be contained directly by a ZCP270:
ZCP100
FBM100
FBM101
However, Control Editors allows FBMs to be contained only by FCM100s. If
the second scenario above exists, that is, if an FBM is contained directly by a
ZCP270 in the migrated IACC database, assignment errors will occur when
bulk generating the migrated FBMs.
Workaround: To correct this, update the IACC database to follow the containment structure
in the first scenario above before migration.
Issue: Names over 32 characters are not allowed in Control Editors.

Description: XML files generated from an IACC database via ArchExport allow names
over 32 characters. However, because names over 32 characters are not
allowed in Control Editors, the Tools will not be able to import these objects.
Workaround: Go through all XML files and manually change the names to 31 characters or
less.
5.4.5 Control Block Configuration
Issue: For FBM214 and FBM215, the RIN/ROUT/ IIN/STRIN/PAKIN blocks are
treated as invalid assignments.
Description: When IO assignment for these block-FBM pairs is attempted from the IO tab
page, the device browser, or through bulk generation, errors/warnings are
raised. The message incorrectly indicates that this is an invalid assignment.
Workaround: The warning/error can be overridden by making the assignment directly in
the block editor (typing in the value or using the ECB connection browser).
You can also set it using direct access.
Issue: If multiple blocks are simultaneously deployed using Strategy Editor, sink
blocks may be incorrectly marked as needing redeployment.

Description If two blocks in a strategy are connected by a data declaration and they are
simultaneously deployed using Strategy Editor, sink blocks may be
incorrectly marked as needing redeployment on check in.
Workaround: Re-open the strategy and perform an Strategy Deployment on the Sink block
alone.
Issue: A compound can exhibit performance issues with a large number of ECBs.
Description: When compounds contain a large number of ECBs, they can begin to exhibit
signs of performance issues.
Workaround: Do not generate compounds containing more than 150 ECBs. If the number
of ECBs exceeds this number, performance will suffer, including the acts of
reassigning, deleting, or adding related hardware.
Reassign ECBs to other compounds before the compound gets too large. If
the configuration has a large number of devices, try to create an isolated
compound that has just the parent ECB and its children for better
performance. If the compound begins to grow over the recommended number
of ECBs, create another compound and move ECBs to the new compound to
split the loading.
Issue: Strategies can exhibit performance issues with a large number of blocks.
Description: When strategies contain many blocks, have custom Appearance Objects, and
are edited during heavy multi-user operations, they can begin to exhibit signs
of performance issues. Blocks may be deleted from the strategy upon save,
and the SMC log will report errors saving the strategy on the server.
Workaround: Do not generate strategies exceeding 50 blocks in size. If the number of
blocks exceeds this number, performance will suffer, including the acts of
editing and saving a strategy.
Note For purposes of this restriction, a child strategy counts as a single

block.
Care should be taken when using the option during an Import SaveAll that
places all of the blocks in the same compound into a single strategy. This may
result in a strategy exceeding the 50 block recommendation.
Issue: I/O assignment is not possible for certain blocks from device browser
window.
Description: I/O assignment is not possible for blocks, which have multiple I/O
parameters associated with them.
Workaround: The Device Browser does not allow dragging blocks that have multiple I/O
parameters, such as BOUT, BOUTR, ROUT, and so forth. I/O Assignment of
these blocks must be done through the CP I/O Assignment, ECB Browser
(Strategy Editor), or Bulk Data.

Issue: Unassign I/O Connection is not available in a valid situation

Description: After performing the following I/O assignments via FCP editors, the
Unassign I/O Connection is not available.
1. FCP1 > FBM228 > FFDEV1 -----> FCP1 > COMP1 > STRATEGY1 >
DI1
2. FCP1 > FBM228 > FFDEV1 -----> FCP2 > COMP2 > STRATEGY2 >
DI2
3. Open STRATEGY1 in its editor and invoke Device Browser.
4. Select FFDEV1 in the Device Browser window.
5. The I/O assignments for COMP1>DI1 and COMP2 > DI2 are shown.
6. Unassign I/O Connection menu is NOT available for COMP2>DI2.
There is no way to unassign COMP2 > DI2’s I/O assignment via Device
Browser window (although you can do it via FCP editor’s I/O Assignment
tab).
Workaround: When using the Device Browser, the Unassign I/O Connection menu option
is available only for connections within the strategy that is currently opened.
Issue: I/O connection is still in place after a software type change.

Description: I/O Assignment is still present after a software type changed. For example,
consider an FBM43 instance assigned to an FCP, iom 37, I/O Assignment,
connected to an AIN block. In the FBM43 editor, change the iom to 73 and
check in. This will replace the ECB with ECB73. The I/O connection is still
in place.
Workaround: It is possible to change the software type of an FBM resulting in replacement
of the ECB with a different type. This will not clear out any I/O connections
from the blocks to the FBM. Such a change could possibly result in an
undesired and invalid I/O connection. Please verify that I/O connections to an
FBM from I/O blocks are still valid after the SW type and ECB type change.
Issue: Selecting the Value-CP > Gateway selection in the PERIOD attribute drop-
down results in an unhandled exception error.
Description: Unhandled exception error occurs when you select Value-CP > Gateway for
Block Sample Time.
Workaround: When you select the invalid value of CP > Gateway in a control object
Period combo box results in an exception message appears with the options to
Continue or Quit. Select Continue and pick a valid period.

Issue: Annotation for the Main block is incorrect after I/O assignment with
DEV_ECB41.
Description: In the I/O Assignment tabbed page, dragging and dropping the Main block
works a little differently than the other blocks. If the Main block is dropped
on channel 2 of an FBM, it sets OCTNUM=2 and uses up channels 9-16. It
does not use channel 2.
Workaround: The Main block can be I/O assigned to a channel on an FBM in the CP I/O
tabbed page by dragging and dropping the block connection to a channel list
item. This results in setting the OCTNUM to the value that it was dragged to.
For example, dragging to list item 2 will set OCTNUM to 2 and use up
channels 9-16. It will not use channel 2.
Issue: Channels for parent Spectrum and Cluster ECBs during I/O Assignments
should be hidden.
Description: Channels for parent ECB I/O Assignments cannot be used. Even though
when you select the parent ECB (for Spectrum and Cluster) in the I/O
Connections tabbed page, you cannot assign any blocks to it.
Workaround: For I/O Assignment, channels are shown for Spectrum and Cluster FBPs.
However, no I/A Series blocks can have I/O assigned to them. I/O assignment
is only possible to the child devices of these FBPs.
Issue: The I/O tabbed page on the CP might prevent a valid I/O Assignment.
Description: The system might prevent a block from being assigned to an FBM or device
by disabling the hardware item on dragging or dropping.
Workaround: The I/O Assignment can be forced by setting the parameter (for example,
IOM_ID) on the block’s WinForm instead of using the CP I/O tabbed page.
Issue: Re-deriving an ECB from a different base template does not copy over the
default values if not locked.
Description: If an attribute is locked in the new parent, it is copied over. If it is not locked,
the previous value is retained.
Workaround: Before re-deriving an ECB, lock the attributes that you need copied over to
the new template.
Issue: Duplicate DEVID values for ECBs may be encountered during configuration
and deployment.
Description: The system does not validate DEVIDs for uniqueness during configuration,
or prior to deployment.
Workaround: The CP restricts ECBs with duplicate DEVIDs from being deployed, and an
error is returned during deployment if this is attempted.

Issue: There are issues with units in PIDA and PIDX blocks.
Description: In Integrated Control Block Descriptions (B0193AX), the PIDX block’s
HZONE parameter description incorrectly states that: “HZONE is expressed
as a percentage of the measurement span.”
Workaround: Please note that the PIDA and PIDX blocks differ on their implementation of
the HZONE, LZONE, and KZONE parameters. For these parameters, the
PIDA block uses percent of measurement span, while the PIDX block uses
engineering units for these parameter types.
For a complete explanation of the differences between the PIDA and PIDX
blocks, see Revision AA of Integrated Control Block Descriptions
(B0193AX).
5.4.6 Deployment
Issue: Using Deploy Utilities > UndeployDeploy option at the controller level
results in an inoperable CP.
Description Control Database Deployment User's Guide (B0750AJ) states that
UndeployDeploy option can be used to reset a compound or a block.
UndeployDeploy done at the compound or block level works as desired.
Workaround: If the UndeployDeploy option is used inadvertently at the CP level, you need
to undeploy, reboot, and redeploy the CP.
Issue: Strategy status is not updated when performing synchronized DBs.

Description Deploying blocks in a strategy marks the strategy as Deployed. However, any
sequence blocks within the strategy may later be edited such that block
compilation aborts marking the strategy "in error".
“SyncDBs” and “SyncDeployStatus” operations on such a strategy do not
mark the strategy as “Deployed”.
Workaround: This is due to the limitation of ArchestrA objects that cannot be marked
Deployed when “in error”. The only operation that can be done successfully
on a strategy in-error is to undeploy it. In order to mark it deployed, fix the
error in the block and then run “SyncDBs”.

Issue: Upon deployment, you may receive a message that the block could not be
added to CSA.
Description: When you are deploying a block, you may see a message in the Output View
and/or SMC which states Object - CMPD.STRAT.BLOCK,
DeploymentFailed - CSA could not add block BLOCK, ret =
NameInUse. This is because the Control Editors track block names by
Strategy, not by Compound. If another strategy in the same compound has a
block by the same name and it is already deployed, you will get this error
message.
Workaround: When you receive this message, you can either move the Strategy to a
different compound that does not have this block name, or rename the block.
Block names need to be unique under a compound to satisfy
I/A Series/Control Core Services software requirements.
Issue: Deploying changes to SFC blocks results in the error message E35 -
InSufficient Memory.
Description: The CSPACE value must be set before deploying SFC blocks to avoid
memory fragmentation on repeated deploys and undeployment of SFC
blocks.
Workaround: The user “fox” has an environment variable NOCLEAN_ST_TEMP”.
Verify this value is set to 0 on the Galaxy Repository station. With this
setting, the sequence compiler does not delete the temporary files that are
created during compilation.
If you compile a block or blocks, you will find these temporary files under
D:\opt\fox\ciocfg\SEQCOMPTEMP. Look for a file named “blockname.i”
and note the size in bytes. Then add 1352 bytes to the .i size and you will get
the CSPACE value. Enter this value into CSPACE for the block before
deploying.
To do the same on the clients, create the environment variable on each client
and then reboot. If you compile on the client, you will be able to view the .i
file as well. Clear the NOCLEAN_ST_TEMP flag and reboot after checking
the file sizes, to avoid invalid temporary files on subsequent compilations.
Issue: You may receive a CP error when deploying ECBs of Intrinsically Safe I/O
cards.
Description: You receive message of “E42 – INVALID/DUPLICATE DEVICE ID” when
deploying ECBS of Intrinsically Safe I/O cards despite the ECB being valid.
Workaround: Deploy all ISCM/R ECB200/ECB202 blocks first, then deploy all ISIO
ECBs.

Issue: Control Core Services workstation appears in an undeployed state.

Description: A Control Core Services workstation with control capability (known on
AW70P, unknown on WSTA70/WSVR70) types and switches are not
deployable objects in Control Editors. These types of objects will always
appear as undeployed.
Workaround: None
Issue: A deployed compound is shown as undeployed after deployment.

Description: A compound is shown as undeployed after deployment. The compound is
incorrectly reported when two clients are deploying the same compound. The
first deployment operation succeeds, but the second deployment operation
reports an error and sets the compound to an undeployed state.
Workaround: Use the Deploy Utilities > Synchronize DBs function to restore the Deploy
state.
Issue: Platform deployment halts when deploying redundant collecting

workstations.
Description: When you configure the IP addresses for both primary and secondary
networks, the system halts trying to resolve the configuration error.
Workaround: When setting up a redundant collecting workstation, a secondary network is
required and the IP addresses need to be unique.
Issue: ECB browser has a memory leak.

Description: Repeated use of the ECB Connection Browser button (Block Editor on I/O
blocks) can cause process memory to be allocated, but not released. Over
time, the memory used by the IDE will grow causing degraded performance.
Workaround: Exit the IDE to release the memory allocated by the ECB browser. This is
only necessary after using the ECB browser for long periods of time.
Issue: The Current Alarm Display (CAD) stopped refreshing alarm once the local
Network Interface Card (NIC) was moved to the top of the list.
Description: The Wonderware ArchestrA product documentation states that the NIC
communicating to the Galaxy Repository server machine should be placed at
the top of the network card list. When the Galaxy station is on The Mesh
network, there is no issue. However, when the Galaxy station is off-Control
Network (that is, ArchestrA communication is utilizing a non-Control
Network), the client stations must be connected to two networks
simultaneously.
Workaround: Verify the NIC used by ArchestrA to communicate to the Galaxy Repository
Server is first in NIC ordering.

Issue: FOUNDATION fieldbus (FF)-specific DCI block I/O Assignments can be

unassigned even though the blocks are deployed to CP.
Description: Unassigning FF DCI IO Blocks via the strategy’s Device Browser succeeds,
but making another assignment is unsuccessful if the block is currently
deployed. Modifying a deployed block’s ECB Connection parameter should
be allowed and cause the strategy to be marked as needing redeployment.
Workaround: For blocks that are currently deployed, modify the ECB connection
parameter via the block’s editor, from the strategy canvas. Saving and
checking the strategy in after this operation will mark the strategy as needing
redeployment.
Issue: Deployment unsuccessful due to a DATE/TIME set, but the Station

compound and ECB compound are marked as deployed.
Description: If deployment fails due to a System Manager DATE/TIME set, the
STATION compound and the ECB compound will be incorrectly marked as
deployed, and the parameters (DV1) are not downloaded to the CP.
Workaround: If the CP reports a failure due to a System Manager DATE/TIME setting
issue, you must first fix the date/time issue, and then undeploy and redeploy
the CP.
Issue: Undeploying a controller initializes that controller.

Description: Undeploying a controller results in the undeployment of all compounds,
strategies and blocks associated with that controller, resulting in the removal
of those control entities from the controller. The quickest way to accomplish
this for I/A Series/ Control Core Services is to initialize the controller.
Workaround: You must reboot the controller immediately after an undeployment of a
controller, or subsequent deployment of control to the controller will fail.
Do not undeploy a controller unless you expect the controller to be
initialized.
Issue: Host workstation must be installed completely prior to deployment.

Description: The Host workstation for a given controller is used for all deployment
operations. A remoting service must be installed and running on the
workstation or deployment will abort. Deployment will abort only after
trying to communicate to the host for an extended period of time (for
example, 10 minutes).
Workaround: Do not deploy to a controller whose Host workstation has not been
completely installed. In addition, make sure the Host workstation is up and
running.

Issue: Limiting unresolved connection messages on Deployment.

Description: Within the Control Editors, when a block parameter specifies a reference
connection, the software attempts to resolve the reference before the
deployment process starts. During deployment, if a Strategy instance has an
input declaration that points to another block parameter that cannot be
resolved, then a is displayed. If that Strategy is currently deployed, its
deployment state will be changed to “Needs to be Redeployed”.
Workaround: To avoid such (and the Strategy instance deployment status changing with
each deployment), change any block parameters with reference connections
that cannot be resolved to a value type until a proper connection can be
established
Issue: Sometimes, attempts to undeploy a control processor (Initialization of CP)

are unsuccessful due to issues related to the CC_Server.
Workaround: If attempts to undeploy a control processor are unsuccessful due to issues
related to the CC_Server, the following action should be taken:
Invoke the Task Manager (right-click the toolbar and select Task Manager)
on the host of the affected control processor and select the Processes tab.
If CC_SERVER.exe is in the list of processes, select it in the Task Manager
and click End Process to end the process. Use Windows Explorer to navigate
to D:\opt\fox\bin and manually start CC_SERVER.exe.
If CC_SERVER.exe is not running in the list of processes, reboot the control
processor’s host workstation and verify that CC_SERVER.exe is listed in
the process list after rebooting. If it does not appear in the process list after
reboot, use Windows Explorer to navigate to D:\opt\fox\bin and manually
start CC_SERVER.exe.
Issue: Redeploying a block after changing its execution order does not work.
Workaround: Undeploy the parent compound. Then, deploy the compound again.

5.4.7 Pepperl & Fuchs Intrinsically Safe I/O

Subsystem
Issue: Commissioning of Pepperl & Fuchs™ remote I/O may be unsuccessful.
Description: During the commissioning of the Pepperl & Fuchs LB/FB remote I/O, the
downloading of vendor DTM data may be unsuccessful.
Workaround: During the commissioning of the Pepperl & Fuchs LB/FB remote I/O, do not
select to download the vendor DTM. Instead, open the Device Editor Vendor
DTM tab and start the download in this tab.
5.4.8 FOUNDATION fieldbus and PROFIBUS
Issue: Vendor Comm. DTM Tab use is not documented correctly.

Description: Implementing PROFIBUS Networks in Applications (B0750BE) provides a
description of the “FBM222 Communication DTM” menu selection from the
Vendor Communication DTM Tab that does not appear.
Workaround: The user document will be updated to remove this option.
Issue: Deploying a compound/strategy with an invalid setting in a block shows the

following message:
“ALL FF blocks to be marked dirty”
Workaround: The FF deployment procedure is upgraded to handle errors detected during
FF 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 FF
blocks on the segment will be marked for re-deployment. You need to deploy
the blocks on the segment again. The FBM228 with IOM128 image version
6.0 or higher is required.
Issue: An exception and a red X appears in the Network View of the ArchestrA
IDE.
Description: Usually while importing a DD file, the Network View application tree in the
ArchestrA IDE shows a red X. An exception dialog box may also be seen.
Workaround: Close ArchestrA IDE and reopen it. You may also need to delete the device
template and re-import the DD file you were working with at the time of the
exception.
Issue: The parameters in the FF UDTM are not downloaded, when the user changes
them and directly clicks the Download All button.
Workaround: After changing a parameter Click the Return button and then select the
Download All button

Issue: Installation of Softing “Hardlock Device Driver” and PROFIdtm is

unsuccessful.
Description: The install program does not recognize that the already installed Microsoft
XML DOM Parser has a higher version than the version provided.
Workaround: In order to work around this install issue, please unpack the installation files
to a local directory on your machine and manually install the following
packages from this directory:
• instmsi.exe
• ipbrts_wxp.exe
• msxml3.msi
• SoMFC42MME.msi
• LicenseManagerE.msi
• hldrv32.exe
• SoPROFIdtmE.msi
• SETUP541.EXE
Issue: A system message may appear for all blocks on a segment.

Description: If a message appears for one block being prepared on a segment, the same
message will appear for all blocks assigned to any device on the same
segment.
Workaround: None

Issue: Link Master Device FF H1 Link Settings Considerations

Description: For proper CIF operations and especially for bumpless transfer of LAS
between the FBM and backup LAS device, link master (LM) enabled devices
require link settings configuration that are compatible to the current link
settings used by the FBM228 itself. The FBM228 automatically adjusts the
link settings for every field device configured to be backup LAS as soon this
device is connected to the segment. However, testing has shown that different
devices (from different device vendors) have certain limitations with respect
to link settings modifications:
• Some devices require a manual power cycle of the device to accept the
new setting.
• Other devices accept the modifications immediately but do not change
their default value for some parameters like time_sync_class.
If the FBM detects a difference between the operational link settings on the
bus and its own configured settings it will stop communicating on that port
and the “Invalid H1 Bus parameters” fault will be set in the System Manager
equipment information. To recover from this state, perform the following
steps:
1. Remove the current backup LAS device from FF segment
2. Make sure FBM228 is working properly. This may require an “Enable
Control” for the corresponding link.
3. Review if the selected device is a good choice for backup LAS.
Potentially change device configuration to “Basic Device” before
connecting back to segment.
General recommendations for enabling link master capabilities in a device:
1. After enabling the backup LAS capabilities in a device, manually power
cycle the device after it goes GOOD in System Manager.
2. Exercise the backup LAS capability by transferring the LAS to the
backup LAS device by rebooting the FBM or by executing
Disable/Enable port from System Manager.
3. If the FBM is not communicating after step 2, restore the FBM
communications (see above) and select different device as backup LAS
and try again.

Issue: Updating the Block Template Prefix does not update Block Template Name.
Description: When you modify a block template prefix in the Device Template Setup
dialog box, the block template names change accordingly. More precisely,
this regenerates the used block templates names with a new prefix for those
that have an old prefix.
If a used block template name does not have old prefix, its name will not be
regenerated.
This is required so that you cannot change block template names. Of course,
if the user entered name has old prefix its name will be regenerated with new
prefix.
When a block template is marked as not used, its name will be displayed as
“$Not Used”. However, its name will be preserved internally in order to
provide the same name when the user comes back and marks the unused
block template as used.
When you mark a block template as not used and modify the block template
prefix, it will not regenerate the preserved block template name. When you
come back and mark the unused block template as used, its name will be
displayed with the old prefix, which was the name of the block template
before it was marked as not used. As the block template name does not have
the current block template prefix if user changes the block template prefix,
the block template name will not be regenerated with new prefix.
Workaround: None
Issue: During commissioning, the download or upload of the vendor DTM data may
abort.
Description: Depending on the vendor DTM, a failure may occur during commissioning
when downloaded or uploaded the vendor DTM data.
Workaround: In this case, it is recommended that you download or upload the vendor DTM
data from the Vendor DTM tab of the PROFIBUS Device Editor.
Issue: If you access the Live List, you may be prompted to save changes when there
are no changes to be saved.
Description: After opening the Field Device Manager (FDM) for an FBM228 and right-
clicking to open the Live List, FDM prompts you to save changes even when
no changes were made. This also occurs when you open the FDM for the
FBM and close it without making changes.
Workaround: Either use the Save and Close button or ignore the Save dialog box.

Issue: If you cancel out of the UDTM of a device that is online, you may be
prompted to save changes when there are no changes to be saved.
Description: If the UDTM is open for an online capable device and you cancel out of the
UDTM by clicking Cancel (x), when selecting Galaxy > Close, or selecting
Windows > Close All, you are prompted to save changes even when no
changes were made.
Workaround: Either use the Save and Close button or ignore the Save dialog box.
Issue: For PROFIBUS PA devices, changing the device address over the
PROFIBUS network may not work or may not be reflected in the system.
Description: For PA devices that are connected to the PROFIBUS segment using a DP to
PA coupler, in some cases, changing the device address over the PROFIBUS
network may not work or may not be reflected in the system.
Workaround: If the address change is not reflected in the system, power cycling the DP to
PA coupler may fix the issue. But a better approach for such issues is to set
the device address in the workshop system and then connect the device to the
PA segment with the right address.
Issue: With the correct PD Tag in the device, FDM with DTM shows an error
stating “can’t find the device with address 0”.
Description: FF Instrument Workshop has NI-FBUS PCI card and Communication
Manager installed. When you open FBM228 and go to the Communications
DTM, showing the live list works and the PD Tag and PD Address can be
changed successfully. However, FDM for the device does not work. With the
correct PD Tag in the device, FDM with DTM cannot find the device, and
shows the error message described above. The FDM with DTM does not
resolve the PD address successfully with the correct PD Tag.
Workaround: For FCS InTouch Application v1.2, a workaround that allows you to
manually set a device address in the instrument workshop is provided in
FOUNDATION fieldbus Control in the Field (CIF) Release Notes
(B0750RW).
Issue: FOUNDATION fieldbus device compatible blocks are shown as disabled in the
Blocks window.
Description: When performing I/O Assignment through the CP editor, selecting an FF
Device will cause the supported blocks to be highlighted in the Blocks
window. The highlighted blocks will be those supported by the FF Device
itself and not necessarily those supported by an ECB201 block.
Workaround: To assign blocks that are not directly supported by the FF Device to the
ECB201 block, simply select the I/O Connections tab and drag the blocks
you wish to assign. The blocks will still be grayed out, but the assignment
will be allowed.

Issue: For an FF Device ECB, editing PORTNO in the WinForm or Bulk Data has
no effect.
Description: In the FF implementation PORTNO is stored in the SQL tables. Since the
table stores all values, there is no difference between a checked out version
of the ECB and a checked in version. This causes data loss.
For Bulk Data, any settings of the PORTNO parameter will be ignored. The
PORTNO value will be the same value as the segment number of the FF
device.
Workaround: The PORTNO parameter of an ECB201 (of an FF Device) is determined by
the FBM segment number the device is attached. In order to change the
PORTNO parameter, move the actual FF Device to the segment number of
the FBM you wish to change it to.
Issue: The icon indicating that you cannot drag and drop does not appear when
dragging and dropping a device template to an FBM or plant unit instance in
the Derivation view.
Description: For example, if you bind an FF template to a DD file and associate a GSD
with a PROFIBUS template, dragging an FF template and dropping it on an
instance of an FBM228 or plant unit in the Derivation view causes you to get
an unassigned device instance. Similarly, dragging a PROFIBUS template
and dropping it on an instance of FBM222 or plant unit in the Derivation
view causes you to get an unassigned device instance.
Workaround: There is no known workaround.
Issue: After having trouble calling up a SMAR Device Instance Vendor DTM tab
online and then exiting, issues may occur when renaming all the Control
Editors objects, and the application’s performance slows down.
Description: Renaming a block does not seem to take effect under these conditions. This
was seen for compounds, strategies, and PROFIBUS devices. For all
ArchestrA objects (not just PROFIBUS related objects), updates are slow,
and calling up and checking in blocks is slow. Stopping and starting the
Control Editors client fixes the issue. When you exit the Control Editors, the
aaIDE.exe process is still in the Task Manager.
Workaround: Exit the Control Editors, remove the aaIDE.exe process in the Task Manager
application, and start the Control Editors again.

5.4.9 Hardware Configuration

Issue: The CP remains checked out with parallel operations of bulk create and
deploy.
Description: If two users Bulk Create devices and deploy blocks from the same CP
concurrently, various issues related to checkout status and data integrity can
arise from this operation.
Workaround: Do not start any new operation on a CP (like bulk create, assignment, and so
forth) while a deployment to that CP is in progress. If two such actions like
Deployment and Bulk Create have been started concurrently, then there is a
chance that ECB and device data may be out of sync and CP may be checked
out at the completion of the operation. If the CP is checked out, restart the
Control Editors, undo the checkout, undeploy the devices that are out of sync,
and synchronize the DBs.
Issue: The Control Editors allow multiple ISCMs to be assigned to an FCM100.

Description: The Control Editors allow you to drag multiple ISCMs and drop them on a
single FCM100. However, assigning multiple ISCMs to an FCM100 is an
invalid configuration.
This is a invalid operation and the same will be validated during Hardware
validation
Workaround: This invalid operation is flagged during Hardware validation.

Issue: Duplicate IP addresses appear after merging multiple Galaxies.

Description: After merging multiple galaxies, it is apparent that there are IP address
conflicts, that is, the same IP address is assigned to more than one device.
Devices that are merged with duplicate addresses show as checked out and
the Control Editors do not allow you to change the address on the offending
device.
Workaround: The system assigns a unique IP and MAC address to each station that is
created in the database. It is likely that when merging two databases,
addresses will conflict between the two databases as the available address
pool does not currently span multiple databases. To identify possible
conflicts before merging, you can run a Hardware Detail report.
To run this report, select Network > Reports. Once the Report dialog box is
open, select the Hardware Detail report. This will give you the MAC and
TCP/IP addresses for each station in the Galaxy.
Once you have identified any potential conflicts, you can either change the
station’s addresses before you merge into a new database OR you can import
the stations first and then change their addresses. If you are unsure if a
merged database is free of addressing conflicts, you can run the Network >
Validate command which will alert you to any issues in the configuration.
While merging, you may also encounter issues with other pieces of hardware
data which are required to be unique in the database such as: WP logical
names, port logical names, Message Manager names, Historian names, and so
forth. These conflicts can also be identified easily using the Software Detail
report from the Network > Reports area on each database before you have
merged the databases. After you have resolved these conflicts and merged
your databases, you can be sure your configuration is valid by running
Network > Validate before you create an installation Commit diskette.
Issue: A workstation can be imported with a System Monitor package defined, but
not with System Monitor name.
Description: The System Monitor combo box in the Hardware Object Editors display an
exception Value cannot be null. This exception may also be encountered
through the Bulk Data Editor, where drop-down fields in the Hardware tab
are empty and a message in the SMC Logger is shown. The message reads
BulkData: Thread HWLoadLists1 error: Value cannot be null.
Workaround: Click Continue on the exception to select a System Monitor. To avoid the
exception and identify the station(s) which the missing System Monitor
names, run the Software Detail report from the Network Report dialog box
(Network > Reports menu). Click on the column Parameter Name to sort it
and look for IPCNAM (System Monitor Name). From here you can look at
the Parameter Value column to identify if any of the System Monitor names
are missing. After you have identified stations without System Monitor
names, you can open the stations and set names from the Software Editor.
You may also use Bulk Data/Bulk Generation to set these names.

Issue: Update Status Control window does not indicate that objects are being
checked in.
Description: Using the Update Software Install Status to set all software install statuses
to Not Yet Installed, the output window shows each status as updated, then
stops scrolling or indicating it is doing any work whatsoever. Meanwhile it
appears as though all the objects are checked out. Indication is needed that
check in is still ongoing, either device by device, or progress bar.
Workaround: To avoid issues while using this utility, please wait until the Output View
reports a message stating Update of all software statuses ended at
<timestamp>. This message means that the operation is completed and the
user can continue using the Control Editors normally.
Issue: Having an invalid software package affected other parameters during bulk
generation.
Description: An AW51M was bulk generated with a PPL6 package (physical properties
library). The PPL6 package was called out erroneously as invalid. The
workstation was built, but the WP logical name was flagged as not created,
and it aborted validation.
Workaround: The Physical Properties library for Solaris (APPL6) is not supported with
InFusion v1.1.
If a station that you are bulk generating has this package specified or another
package that is not valid for the station type you are generating, you are likely
to get into a condition where your logical names and software parameter
values are not saved to the object. In some cases, logical names are reserved
by the system but are not viewable in the station's editor. This scenario will
also be indicated with the following message in the Bulk Data Output View
messages:
Invalid software package <package_name> defined for
object
To recover from this scenario:
• In the Network View, delete the station(s) that have invalid software
packages defined in your Bulk Data table.
• Remove any invalid package instances from your Bulk Data Software
package table.
• Regenerate the deleted stations. The software parameter values and
logical names should now be correct.

Issue: Re-assigning a device with I/O Assignment to a deployed DCI block fails
without notice.
Description: With a ZCP, FCM, FBM, device, a compound assigned to the ZCP, and a
strategy containing a FF function block that is assigned to the device, and the
strategy is assigned to the compound, all deployed, undeploy the device.
This setup would look like this:
ZCP
Compound
Strategy
AI block (assigned to the device)
FCM
FBM
Device
Attempting to unassign will display a message. However, attempting to
assign it to a different FBM, either by using the Assign To dialog box or by
dragging and dropping onto another link, will fail.
Workaround: Unassigning or reassigning of hardware modules will fail, if there is a
deployed block I/O connected to the hardware module. If this happens, find
the connected I/O blocks from the CP I/O tabbed page, undeploy them, and
then unassign/reassign.
Issue: Bulk create of devices displays invalid choices.

Description: When adding a new device to a FBM228, the Bulk Create list contains
invalid selection for a FBM228.
When creating devices for an FBM228, the Bulk Create dialog box shows
all devices that use an ECB201, not just those that are FOUNDATION fieldbus
related. The system will not let you assign these invalid devices to the
FBM228, but they are shown in the dialog box incorrectly.
Issue: There is an issue renaming child ECBs in compound when you assign more
than one FBM to FCM in the Control Editors.
Description: There is a child ECB rename issue in the Primary_ECB when you assign
more than one FBM to an FCM. ECB names are updated correctly if FBMs
are assigned individually.
Workaround: When assigning multiple FBMs to an FCM, only the first or last ECB will be
automatically renamed to match the FBM. If you assign one FBM at a time,
the ECB names will be updated correctly. Alternately, you can manually
rename the ECBs to match. However, manually renaming the ECBs prevents
further automatic renames that keep the FBM-ECB names in sync.

Issue: FBM editor does not save when an ECB is modified and saved.
Description: FBM editor does not save when an ECB is modified and saved while the
FBM editor is open.
Workaround: To avoid this issue, edit the FBM and its corresponding ECB separately, not
concurrently.
Issue: The IOM type cannot be selected after creating an FBM241.

Description: After creating an FBM241, opening the FBM editor, and selecting the
Software tab, the IOM05 and IOM08 selections were not shown in the
Software tab and could not be selected.
Workaround: If you see this issue, create the IOM package from Bulk Data or Direct
Access
Issue: The same Message Manager Associated Logical Name can be selected
multiple times.
Description: The same Message Manager Associated Logical Name can be selected
multiple times from MDS tab drop-down list.
Workaround: Disregard Message Manager Associated Logical Names that are already in
use by the object. If you mistakenly select one name multiple times, the
Validation routine will alert you to this error before you create your Commit
Diskette.
Issue: Context-sensitive Bulk Create fails for Spectrum and Cluster devices.
Description: If you right-click an instance of an FBP10 and create a new DEV_ECB41,
you will create it successfully but will not be able to assign it because the
hardware type has not been specified. The Bulk Create dialog box should
allow for the specification of hardware type or the option to create these
devices from the New menu prompt should be removed. An error message
should be displayed (right now only the logger has the information).
Workaround: The Bulk Create dialog box can only be used to create Spectrum and Cluster
objects, not create and assign them to a fieldbus processor. This is because a
hardware type has not been specified for the new device and it is required for
creating its corresponding ECB. After creating the devices using the dialog
box, open their editors and set their hardware type before continuing to assign
them to FBPs.

Issue: Confusing error messages may appear when attempting to give an object an
invalid name. ArchestrA and the Control Software naming rules are distinct.
ArchestrA naming rules allow ‘$’ and ‘#’ in their tagnames, while
I/A Series/Control Core Services letterbugs do not.
Description: While renaming objects, you may receive messages telling you that ‘$’ and
‘#’ are valid naming characters. If you try to name your I/A Series/Control
Core Services letterbugs with these characters, you will receive an error
message saying the name is invalid.
Workaround: ArchestrA allows names of alphanumeric and “$”, “#” and “_” characters.
This naming scheme should be used for all of your non-I/A Series application
objects. Only alphanumeric and “_” characters are allowed for names of the
I/A Series/Control Core Services application objects.
Issue: While performing a Bulk Create in a multi-user environment, not all

selected objects may be created.
Description: When performing a Bulk Create within a multi-user environment, all
requested objects may not be created if a name conflicts with an object
created by another user.
You can simply run Bulk Create again to obtain the objects for which you
are looking. Also, these will be mostly created place during system
construction, which often occurs on a standalone engineering workstation.
Workaround: Run Bulk Create a second time to create any objects that may be missing.
Issue: Renaming an FCM100 with contained FBMs could be slow (depending upon
the number of FBMs) and might result in their corresponding ECBs not being
renamed.
Description: When an FCM is renamed, its corresponding FBMs must be renamed to
match the first four characters of the FCMs letterbug. Each contained FBM is
renamed first and then the FCM itself is renamed. In addition, each
corresponding ECB for each module could be renamed during the process.
Accessing each ECB’s compound during this operation may result in the
ECBs being unable to rename and/or the ECB’s compound not getting
checked in.
Workaround: Wait until the FCM and contained objects are renamed. If actions are
mistakenly performed during the rename of an FCM and contained
FBMs/ECBs, and the compounds containing the ECBs are left checked out
(or the ECBs are not renamed), there are two workarounds.
1) Undo the checkout of all affected objects and rename the FCM to a
temporary name while waiting for all FBMs to rename. Upon completion of
the FBM renames to the temporary name, rename the FCM back to the
desired name, or;
2) If the first workaround does not succeed, shut down the IDE. Reopen the
IDE and undo the checkout of all affected objects, create a new controller,
and reassign all FCMs to a new controller. Reassign all of the compounds to
the new controller. Delete the problematic controller, and rename the new one
to match the original.

5.4.10 Import/Export
Issue: When importing large *.aqPKG files from client workstations, network
issues may cause the import to abort, reporting the following error in the
SMC log:
“4878 3/8/2011 2:14:23 PM 5496 5320 Error WWPDFManager The
semaphore timeout period has expired. (80070079) raised at line 1501 in
PDFManager.cpp (in .\).”
Description If this error occurs, it will occur prior to any actual objects being imported.
So, the Galaxy will remain in its previous state
Workaround: If this error occurs, import the file from the Galaxy Repository station.
Issue: While importing an aqPKG file from InFusion v2.5 containing an FBM228
and an FF device, the device is not imported properly. Only the FBM228 is
imported.
Description Overwrite is not supported for objects that are being migrated from an earlier
version of Infusion or FCS.
Workaround: For cases like this where imported objects have Tagnames that match objects
existing in the galaxy but cannot be overwritten, the following workarounds
are possible:
1. Create a new galaxy in the FCS v3.0 (or later) system.
2. Import the pre-v3.0 .aqPKGs into this (empty) galaxy to migrate the
imported objects to FCS v3.0 (or later).
3. Export the objects from the Galaxy in FCS v3.0 (or later).
4. Import the (new) .aqPKGs from step 3 into the Galaxy in FCS v3.0 (or
later) where they are to be used. The objects being imported are now v3.0 (or
your current version of FCS) so the 'overwrite' option can be used, and the
'Rename Objects In Galaxy' option can be selected as needed.
The second option for a workaround is to rename any objects in the galaxy
with tagnames that match the objects being migrated. In the case of an FF
Device Template, each of its associated block templates must also have a
Tagname that does not match a Tagname in the galaxy.
The 'Block Template Prefix' for the FF Device Template also cannot already
be used in the galaxy. If necessary, you can modify this field on the existing
FF Device template using 'Device Template Setup'.
Issue: Out of memory during export, (CAR:1010653)

Description: While exporting an extraordinarily large CP, the Control Editors run out of
memory and the export does not complete.
Workaround: If this situation occurs, you must export your CP in smaller chunks of
compounds instead of all at one time.

Issue: The Compound Collecting Workstation field can get out of sync during
import.
Description: If you select a workstation for a Compound’s History Collector and then
export, delete, and reimport only the workstation, you will lose the link
between the compound and the workstation.
Workaround: If you have workstations defined within compounds as History Collectors,
export the compounds and the workstations in the same export file to retain
the link between them. If you do export compounds and workstations
separately, you will need to re-establish the workstation-compound link
manually after importing through the Compound Collecting Workstation
field.
Issue: When stations are imported with duplicate IP addresses, the user is not
informed in the output log.
Description: This is related to another issue whereby the user was unable to change a
duplicate IP address of an imported station. That issue is corrected, but the
user is still not adequately informed that there is an issue. The new CP will
remain checked out, but there should be an error or warning within the import
“output log”.
Workaround: Read the output of the Import dialog box and check the SMC Logger
following an import of an automation object. It is possible that the dialog box
will say the import completed when errors actually occurred. These errors are
spelled out either in the messages of the Import dialog box and/or the SMC
logger.
Issue: The Rename option does not work if an object name conflicts during import.
Description: When importing a hardware automation object, you have the option of
renaming any conflicting object. However, the import process skips over any
conflict and does not rename the objects using the suffix provided. This
happens because most hardware objects have a requirement of six-character
name. The import rename option would append something like "_new" to the
end of the name and the name validation would be unsuccessful.
Workaround: Overwriting is not supported for hardware objects. Conflicting hardware
must be renamed before importing.

Issue: Issue encountered during import.

Description: During the import of a “.aaPKG” file, a dialog box might be displayed from
Microsoft Visual C++ runtime. The SMC logfile will also contain an error
from mscorlib stating AppDomain cannot be unloaded during object
finalization unknown error 0x80131015.
Workaround: If this dialog box is displayed, do not click the OK button. Clicking the OK
button will cause the Galaxy Repository to shut down, resulting in a partial
import of objects into the Galaxy from the “.aaPKG” file. The import process
needs to finish importing all objects into the database. You will know once
this process has finished when the Close button is enabled and messages
stating Object <object name> is being checked-in appear in the Import
dialog box. Since clicking OK in the Microsoft Visual C++ runtime dialog
box will cause the Galaxy Repository to shut down, this should only be done
once all Control Editors clients have closed their sessions and have exited the
IDE.
Issue: Importing hardware data into a Galaxy with existing objects may result in
duplicate FTMAC addresses.
Description: If you import hardware data (SysDef, IACC, or Control Software into a
Galaxy which already has some hardware objects defined, you may end up
with duplicate FTMAC addresses.
Workaround: Validation of the configuration will expose all offending stations. You must
manually reconfigure the duplicate FTMAC addresses to a new FTMAC
address, and re-validate the configuration.
Issue: Unable to open Control blocks in Strategy Editor after importing strategy
instances.
Description: Be aware that while importing strategies derived from strategy templates that
already exist in the Galaxy, the link to the parent template must be broken if
the strategy that is being imported has been derived from a strategy template
that had changed in structure and the Overwrite option is not chosen to
overwrite the templates. A change in structure, for example, could mean that
blocks or strategies have been deleted from the template.
Workaround: When importing instance of strategy, user must enable the Break Link to
Defining Template checkbox available in the Import Preferences dialog box
if the strategy template has changed structure.

5.4.11 Library Object
Issue: The Library Editor should prevent the user from importing binary files into
SFC/HLBL libraries.
Description: The Library Editor does not prevent the user from importing binary files into
SFC/HLBL libraries.
Workaround: Avoid importing unsupported files (especially binary files) into Library.
5.4.12 PLB Editor
Issue: Repositioning a branch is not documented correctly.

Description: PLB Ladder Logic Editor (B0750AK) provides incorrect instructions to
change a branch type in the PLB Editor.
Workaround: To convert a regular branch, drag the left branch connection past the left rail
to create a left branch, or drag the right branch connection past the right rail to
create a right branch.
To convert a left or right branch to a regular branch, drag the left or right
branch connection back to the parent rail.
Issue: You cannot see PLB ladder display from the host workstation.
Description: By design, the station from which the PLB block was deployed will contain
the display file for the ladder logic diagram. You can deploy from a
workstation that is not the CP’s host, which is a departure from legacy
I/A Series convention. This means that if a deploy is performed on a station
that is not the CP host, you will not be able to access the recently deployed
PLB file on that host.
Workaround: If you are a legacy I/A Series software user and wish to see ladder logic files
on the CP host, you must perform the PLB block deployment from the host
station. Otherwise you must be aware that the station on which you initiated
your PLB deploy will contain the Ladder Logic Display.

Issue: You cannot open SFC block editors.

Description: After importing SFC and HLBL include files, importing a SaveAll into a
Bulk Data object, and generating a strategy, some SFC blocks (for example,
DEP) cannot be opened and modified. However, these blocks can be
compiled and deployed.
Workaround: This issue occurs when the graphics included in the SFC blocks are stored
internally in FoxSFC 1.0 format. The import into the Control Editors only
supports FoxSFC 2.0 formatted SFC logic. The blocks that do work correctly
were opened with FoxSFC 2.0 software and saved.
In order for the blocks to import correctly so that you can open and modify
them afterward using SFC block editors, perform the following steps:
1. Copy the contents of the SaveAll diskette to a machine that has FoxSFC
2.0 installed.
2. Verify that the necessary SFC include files that were imported into the
Control Editors libraries are in the proper location on that station. If not,
put them in the standard location, D:\opt\fox\ciocfg\sequenlibrary.
3. Open and save each of the SFC blocks exhibiting the issue in FoxSFC
2.0 within I/A Series system, directly in the SaveAll image. The files
will be stored using the block name in a folder matching the compound
name.
4. Copy the SaveAll image to the machine where Control Editors is
installed.
5. Open the Bulk Data object used to generate the blocks, that is, the Bulk
Data object where this SaveAll was already imported.
a. Open the Blocks view.
b. Right-click in the grid and select Attachments from the context
menu.
c. Check the Show All Blocks checkbox.
d. From the Blocks With Attachments list, select the
Compound:Block containing the SFC block in error.
e. Click Delete to remove the old version of SFC source. The contents
of the Attachments box will be cleared.
f. Click Add. In the Browse For Folder dialog box, navigate to the
containing compound folder in the SaveAll image, and choose OK.
The filenames are built from the block name, so only the folder
selection is required. The contents of the Attachments box will now
show SFC information.
g. Close the Attachments dialog box.
Re-generate the strategies containing the affected blocks.

5.4.13 HLBL Editor

Issue: When importing an HLBL include file, the appropriate files may not appear
in the Select File to the Import dialog box.
Description: When you try to import a previously exported HLBL Include file, your files
may not be visible in the Select File to Import dialog box.
Workaround: If exported files are not visible in the dialog box, enter “*.*” in the File
extensions field.
Issue: The Find command may not work in the HLBL Editor when HyperSnap®
software is installed. (CAR:1010871)
Description: In the HLBL Editor, you should be able to call up the Find function with the
CTRL+SHIFT+F keyboard shortcut. However, this shortcut may be currently
registered to capture full-screen images in HyperSnap software.
Workaround: Reconfigure HyperSnap software so that the keyboard shortcuts do not
conflict. For example, if you change the HyperSnap shortcut for full-screen
captures to CTRL+SHIFT+B, you will no longer see this issue.
5.4.14 SFC Editor
Issue: Unable to view the Print Preview of Main/Sub/SBX routine in the Print
Preview dialog box for the second time in the SFC-derived template
$DEP/$EXC/$IND having SFC program.
Description If Print Preview is used for certain printers, the dialog opens behind the
current active window and the user is not notified. This makes it look like the
application is hung.
Workaround: Press ALT+TAB to view the Print Preview dialog box.
Issue: Steps inside a Cascaded Divergence element could be collapsed.

Description: In some cases the steps inside a cascaded Divergence element could be
collapsed into a line. That only effects the visual representation of the
diagram. Rest of SFCDM functionality works properly. You are still able to
select the step and look at the steps’ logic. The execution of the diagram is
still shown correctly.
Workaround: None

Issue: Invalid Strategy is created

Description: Software required for creating strategies and deploying strategies may not be
completely installed. This situation is indicated by:
1. The Block's execution order is missing, i.e. the execution order is
indicated with “#”
2. A block is unable to deploy.
Using Windows Explorer, check for the existence of the following files:
• C:\Windows\Assembly\InteropFoxBtmParameterAccess20
• C:\Windows\Assembly\InteropFoxDtmParameterAccess20
If these files are missing, take the corrective action below.
Workaround: From the Control Editors CD, re-install the file InFusionEngineering.msi.
After inserting the CD in the drive, exit from the Installation dialog box that
may start up. Using Windows Explorer, navigate to the drive with the Control
Editors, and double-click on the InFusionEngineering.msi file.
1. Select Next on the first dialog box.
2. Select the Repair option on the installation dialog box.
3. Select Install to begin the installation.
4. Select Finish on the final dialog box.
Issue: The Control Editors appear to be hung after selecting the Print button from
the SFC canvas.
Description: If the Print button is selected from the SFC editor, and if there is no printer
selected, the default printer, Microsoft XPS Document Writer will be
selected. This printer will save the print output to a file. The dialog to specify
this filename may be displayed behind the editor. The editor is frozen until
this dialog is dismissed.
Workaround: To bring this dialog to the front of the SFC editor, press ALT+TAB buttons.
You can either dismiss the dialog or enter a filename for the print output. To
avoid this issue, select a valid printer as the default printer for the
workstation.

Issue: Format changes made in SFC editor cannot be saved.

Description: Formatting changes made in the SFC Editor cannot be saved. For example, if
you open the SFC Editor and apply a fill color to a rectangle, the Save button
is disabled. The Save and Close buttons do not save the changes while the
SFC Editor is closing.
Workaround: In Visio® software, changes to some shape properties (like font color, fill
color, and so forth) do not mark the diagram as being modified. If you make
such changes and want to save diagram, the simplest ways to mark the
diagram as being modified without actually modifying it are:
• Double-click on a step to open step editor, and the close step editor.
• Move the step to the open area. The step will snap back, but the diagram
will be marked as modified.
Issue: System variables are available for troubleshooting SFC and HLBL code.
Description: The system variables KG_FILES and NO_CLEANUP_TEMP are available
for troubleshooting SFC and HLBL code. From the currently edited SFC
within the Control Editors the variable KG_FILES creates a .k and .g file in
the root of the C:\ drive. The variable NO_CLEANUP_TEMP does not
cleanup compiler files in the directory D:\opt\fox\ciocfg\SEQTEMP.
Workaround: Use these two variables as needed to help troubleshoot SFC logic.
5.4.15 Strategy Editor
Issue: The bulk generation of strategies using SaveAll Import has the following
issue in FCS v3.0 (or later):
During the SaveAll, the import data is automatically extracted to make all
connected parameters visible on the generated strategy. This can cause the
strategy to open slowly the first time, especially if it has more than 50 blocks.
Workaround: If you do not require the automatically generated visible inputs and outputs,
delete the VisibleInputs and VisibleOutputs columns from the block table
after the Save All import. This allows generation of strategy with all the
default Appearance Objects for the blocks; and opening the strategy for the
first time will be faster.

Issue: When you clear the Insert Hyperlink Tool option, it does not function
properly in the strategy part of Graphical Editor.
Workaround: This version of Control HMI supports Visio 2010, which contains a new
hyperlink cursor feature. To see this feature, use the hyperlink tool on the
Strategy Editor.
To add a hyperlink to a Visio shape:
• In earlier versions of the FCS InTouch Application, the cursor would
revert to the default (arrow) after this operation.
• In Visio 2010, the hyperlink cursor is shown along with the arrow cursor
anytime you point the mouse over that shape.
A strategy can contain a large number of shapes, and the cursor change
makes it convenient for you to view which shapes contain the hyperlinks.
Issue: The Control Editors editor may be unable to open.

Description: The Galaxy database keeps track of the software that has been installed on
each server and client. This information may get out of sync with the actual
installed software on each machine. Indications of this mismatch include:
1. Strategy Editor cannot open.
2. SMC Log errors as:
Cannot find the assembly FoxObjects,
Version=4.1.0.2, Culture=neutral,
PublicKeyToken=d2d1064e7cd0412f
3. Opening a Block editor reports several SMC errors.
4. Strategy checkin aborts.
5. Importing old export files are unable to migrate (create new objects).
Workaround: If these conditions exist, contact Invensys Global Customer Support website
to correct the situation: [email protected].
Issue: Input Strategy Declarations when using the Create Template from Instance
function.
Description: Strategy Input Declaration values are not cleared during conversion process
when the Create Template From Instance context menu item is selected on
a Strategy instance. These Input Declaration values will be propagated to
derived instances of the newly-created template unless they are first manually
cleared in the template.
Workaround: To manually clear the input declarations, open the created Strategy template.
Select each of the values associated with the Input Declarations, delete the
value, and save the template.

Issue: Opening a compound’s editor and adding new blocks to a Strategy within the
compound does not refresh the compound’s Block Execution Order tabbed
page with the newly-added blocks.
Description: Performing the following sequence of steps does not show newly-created
blocks:
1. Create a new compound called COMP2.
2. Open COMP2’s editor.
3. Create a new strategy, Str2, within COMP2.
4. Create a few block instances (any type) within Str2, and close the
Strategy Editor.
5. Switch to COMP2’s editor page opened in step 2.
6. Go to the Refresh Strategy Exec Order tab of COMP2’s editor. The
newly created Str2 appears in the editor.
7. Go to the Refresh Block Exec Order tab of COMP2’s editor. The newly
created blocks do not appear in the editor.
Workaround: Close the compound’s editor and reopen it. The Block Execution Order
tabbed page will be refreshed with all newly-created blocks.
Issue: Print Preview is disabled in the Strategy Editor.

Description: The Print, Print Preview, and Page Setup buttons are disabled in the
Strategy Editor when there is no printer installed on the workstation.
Workaround: None
Issue: Changes made to unlocked Appearance Object within a parent strategy

template are propagated to existing customized children.
Description: Even if an Appearance Object is unlocked, it is propagated from the template
every time, unless you customize it in the derivation chain. This is different
from previous versions of Control Editors. Formerly, if the Appearance
Object was unlocked to start, it would never be kept synchronized with the
template after its creation, regardless of user customizations in the derivation
chain.
Workaround: None

Issue: You cannot place added parameters so that the connection point is facing in
the right direction.
Description: You cannot place an added parameter so that the connection point is facing in
the right direction on a Logic block SAMA symbol. It does not work properly
in the Strategy Editor or in the Appearance Editor.
Workaround: When you add a parameter to the Custom Appearance Object, the Control
Editors calculate the parameter’s direction based on the parameter’s location,
and Appearance Object’s location and size. If you rotate (flip) the
Appearance Object prior to adding a parameter, the calculation can go wrong
and parameter will be misdirected.
In this case, to direct the parameter properly, rotate the Appearance Object to
its original rotation, add the parameter, and then rotate the Appearance Object
back.
Issue: Selecting a FoxCom ECB38R for an AIN resulted in an unexpected

exception.
Description: While using the device browser for I/O connection, if you select a module in
the tree view and then incorrectly select an empty channel element in the list
view below, an exception message, Object reference not set to instance of
object, is displayed.
Workaround: Select Continue on the dialog box and proceed with I/O Assignment as
usual.
Issue: Occasionally, an insufficient memory error will occur.

Description: The message insufficient memory error may appear when you click Print
and then select Print Preview. This message appears when Print Preview is
displayed from within the Strategy Editor.
Workaround: Close and reopen the ArchestrA IDE.
Issue: Occasionally, you are unable to delete Appearance Objects from a strategy.
Description: At certain points while working, you may be unable to delete Appearance
Objects from a strategy (these objects are not deployed). The delete key does
not work and the right-click menu selection is disabled.
Workaround: While working in the Strategy Editor, occasionally blocks cannot be deleted
using either the delete key or Delete menu item. Save any modifications
made to the strategy and restart the IDE.

Issue: Strategy contained names can have the character #.

Description: In the strategy contained name validation, the character ‘#’ is allowed. This
will create resolution conflicts with extension connections. For example
Compound.X#.P could be a source strategy with name X# and declaration P
or could be a source compound with attribute X and extension .P. Connection
validation code is being updated to not allow connections to strategies with
the ‘#’' character in them.
Workaround: Strategy contained names should not contain the # character. The # character
conflicts with specifying extensions in a block parameter connection
reference. In a connection reference, an extension is preceded with the #
character.
This impacts the Strategy Editor in which the connection will not be drawn
graphically. Also, deployment will not translate the connection reference to a
Compound:Block.Parameter reference.
Issue: The appearance of an object on a deployed strategy cannot be updated.

Description: You cannot update an Appearance Object once it has been placed onto a
strategy. If you add a template to a strategy and deploy it, and then make a
second Appearance Object for that same template, you will observe that you
cannot change the Appearance Object of the template because the Update
button is disabled.
The Appearance Object for a contained strategy cannot be changed in the
canvas of its containing strategy. Its defining template may have multiple
Appearance Objects defined, but when the Appearance Object dialog box is
invoked for the contained strategy, the Update button is disabled.
Issue: Line connector is changing on strategy.

Description: Occasionally, while working on a strategy and adding new blocks, the default
connection setting for connecting attributes gets changed to curved
connectors instead of right angle connectors.
Workaround: While working in the Strategy Editor occasionally a connection might change
to “curved connector” instead of “right angle connector”. If this happens,
select the connection and pick “right angle connector” from its context menu.

Issue: Names of I/O Declarations are not propagated properly.

Description: The names of I/O Declarations are not propagated properly. For example, if
you add parameters to an object after making input/output declarations, and
then change the name of input/output declarations, you will see that the new
name of the input/output declarations do not carry through to the Appearance
Object parameters. To resolve the issue, you must delete all the existing
parameters from the object (which had the old input/output declaration
names), and then add the parameters with the new name again.
Workaround: Re-naming an input or output declaration will not update the name in the
strategy’s Appearance Object. The parameter displaying the old name of the
input or output declaration will need to be removed manually from the
Appearance Object. The parameter containing the new name can then be
added to the Appearance Object from the Select Parameter dialog box.
Issue: The connection type is not retained from input declaration.

Description: No matter the connection type (Boolean or real) out of a template Appearance
Object, the lines that come out are always solid. This has to do with
connecting through an input/output declaration and it seems that the
connection type is not passed through the declaration. This will also become
an issue with strategy to strategy connections as the connection type will not
pass through for this situation either.
Workaround: In the Strategy Editor, input and output, declarations do not keep track of
their connection reference type (Boolean, Real, or String). Connection
settings cannot be specified for connections to and from declarations. The
connection will appear as a solid black line.
Issue: Issues appear when copying and pasting in strategies.

Description: Some copy/paste operations involving nested strategies that are not derived
directly from the base template do not behave correctly. If you copy a nested
strategy containing an input declaration reference whose value is locked in
the parent, the reference will not be updated during the paste operation. In
addition, if you copy blocks along with the nested strategy, their connection
references may not be updated during the paste operation due to the finability
to update the strategy’s input declaration reference.
Workaround: After you paste the nested strategy, break the link to its defining template.
This will unlock the input declaration reference and allow you to update the
reference manually. In addition, if you pasted blocks along with the nested
strategy, select the Refresh Connections menu item from the strategy’s View
menu. This operation will remove any connections that were not updated, or
if the objects are pasted in the same strategy, the connections will be
reconnected to the original blocks and strategies that were copied. These
connections will need to be reconnected manually.

5.4.16 Live Data Display

Issue: Live Data Viewer may close unexpectedly.
Description: When using the Live Data Viewer, selecting and moving block connectors
may cause the viewer to close unexpectedly.
Workaround: Do not move block connectors in Live Data Viewer.
Issue: Under some circumstances the Live Data Viewer does not show the actual
Deployment status of the blocks.
Description: Nevertheless, the Live Data Viewer is functioning properly, using actual
block’s Deployment status.
5.5 Field Device Manager
5.5.1 Vendor DTM
Issue: The vendor DTM tab should not be shown in the editor for device template or
instance if the software is not installed on the workstation.
Description: Vendor DTM association to the parent template is done only once, and you
can do so from any Field Device Manager workstation where the DTM is
installed. Once the association is done, a vendor DTM tab will be available in
Field Device Manager. If the vendor DTM is not installed on the workstation,
the vendor DTM tab should not be shown in the editor for device template or
instance. For FDT2.0 based DTMs, the vendor DTM tab is shown even if the
vendor DTM software is not installed on the workstation. Opening the vendor
DTM tab will be unsuccessful with the following error "Initialize DTM. The
given key was not present in the dictionary."
Workaround: Vendor DTM software needs to be individually installed on all Field Device
Manager workstations where it is desired to use the software.

145
C H A P T E R 6
Issues Resolved
This section describes the issues resolved in the current Control Software v7.1
and the previous Control Software v7.0.
Contents
• The Control Software v7.1 Issues Resolved
• The Control Software v7.0 Issues Resolved
6.1 The Control Software v7.1 Issues Resolved
Schneider
Reference ID Issue Resolved
Case 38742889 Commit validation reports invalid errors.
Case 1330378 HART-FDM incorrectly prompts for additional Change Tracking reason
when closing the Device editor.
Case 43174703 SaveAll import and generate via BulkData is losing channel information.
Case 43068488 SaveAll import and generate via BulkData fails to set Compound parameter
connections.
Case 37712744 Strategy Editor LiveData does not start for CALCA blocks.
Case 1331308 Export of IACC FDM is failing to import in FCS.
Case 39865936 Deployment of FF device with large FDATA value may report Scheduling
error.
Case 38346778 Change Tracking file for HLBL code is missing #define and comment lines.
Case 38417277 Deployment of minor ControlHMI edits to an operator station is taking a long
time.
Case 37713333 Deployment Screen doesn't show modified objects when using filters.
Case 39001680 ControlHMI using multiple Graphics and scripts causes Graphic Object(GDI)
leaks and eventually causes ControlHMI freeze.

146 6. Issues Resolved
6.2 The Control Software v7.0 Issues Resolved
Case Number Description

1101684 Need report of logged in users need, and user Fox issued as user.
1126893 Highlight block when "found".
1184421 FRSExec stops when first user is logged out.
1222393 SFC .k file looking in wrong directory.
1227827 Smartsymbol edit propagation causes WM to crash.
1237756 GalaxyPrep on client modifies GalaxyStyle on all systems.
1247230 Off-Mesh galaxy with Windowmaker is missing Recipe Manager.
1252182 ArchestrA graphic text gets smaller each time ShowGraphic is called.
1245924 HMI Nut Cracker fatal error: Console initialization failed message.
1251470 Alarmserver lost communication with HMI after high CPU usage.
1269227 Fixed Decimal does not work with IO Tag reference values.
1277516 DI object reports Invalid tag name.
1281164 License warnings for IDE observed in SMC.
1289791 Store and Forward buffers not working in Historian.
1286715 HMI Dropdown menus are closed if the mouse cursor is slightly outside the
menus.
1296208 AlarmProv and hot backup manager issues.
1300854 Running IEW that uses DA is reporting an exception for large data set.
1301480 Install issue of SQL on secure system.
1302078 SEQ code compiler output different between IDE and ICC.
1302075 E&H DTM install failure.
1308110 Moveblock command has issues with declarations.
1309793 HMI AlarmDB Panel Reset button reports an error.
1313967 Saveall export strips of STA compound prefix.
1314303 AlarmDB logger doesn't function as expected when run as a service.
1313198 Assigning AI block to DEVICE using the device browser does not reflect the
customize parameters in AI block.
1316386 AI block template reports an error when saving parameters.
1316572 Export SaveAll of a large CP returns the following error "ArchestrA IDE has
stopped working".
1316928 Copy Strategy command not working when PNT_NO is locked in the source
strategy.
1317010 Comments missing in the Seq code after importing Saveall.
1315963 Calling several displays in sequence could cause InTouch to crash.
1317686 FBM is not able to push parameters into FF device.
1317859 FCS allows sink connections into output parameters.

6. Issues Resolved 147

1318018 Block description parameter is out of sync.
1317933 AlarmDB query issues fixed by WW HF L00133245 has messages missing
related to UNACK_ALM and ACK_ALM.
1318764 Deletion of a locked connection in template is not deleting from instances.
1255019 FCS deployment causes mismatch status while setpars is in progress.
1319544 Migration from FCS 4.0 to CS 5.0 fails for $EXC and $IND blocks.
1319028 GridEditor showing strange numbers instead of compound name in ID
column.
1321217 Vertical lines become invisible in ArchestrA Graphics.
1320080 FCS reports error when loading specific GSD file.
1321195 Editing Specific CALCA block causes IDE freeze.
1321719 Add_Cat block in the R430_Phase_Add_Cat compound cannot be deployed.
1322010 RefreshHistory tool is not populating data for backup collector.
1322011 ValidateSaveAll utility is not comparing the right fields.
1321976 Change Tracking reason text causes xml errors in System Auditor.
1321586 Database error with Infusion_block_data SQL View.
1322848 Trend Pen in Archestra Graphics is not working properly for historized
values.
1322833 DA ICCPRT report has incorrect values w.r.t CP.
1325169 SynchronizeDBs can put the CP data in a bad state if CP is not reachable.
1320640 Import client control dll sets random objects to "software_upgrade_needed"
state.
1325676 FDC280 IP address is set incorrectly when using DirectAccess.
1325715 Saveall import and BulkGen doesn't support same device names under two
CPs.
1297117 DA Saveall export failed with an error.
1325305 C:B.P update in a parameter value is not marking the block as modified.
1327090 Update B0750BA doc for multi-galaxy support.
1327292 Strategy open takes a long time compared to ReadOnly.
1326580 DVNAME value is lost.
1322412 CTS baseline is missing steps for logic block.
1326953 LIM block ROCOPT is incorrectly placed in the editor with incorrect text.
1328207 Fit-to-page is not utilizing the entire print area, but leaves out lot of white
space.
1328563 Saveall validation tool reports an error.
1312124 Upload compare reports unexpected differences.
1321872 CTS baseline reports parameters with blank values.
1330211 Block marked as modified when changing an include file that is not referred.
1330255 FD_Fail Map value parameter is getting erased from the device.
1330329 CFGOPT settings are not matching with user doc.

148 6. Issues Resolved

1329971 Strategy is marked dirty without any change.
1331473 DA fails to update attribute on UDO.
1328985 LiveData doesn't start for a deployed strategy.
1331906 Saveall export fails for specific compound.
1332520 Changes to Historian configuration causes invalid entries in FoxCTS.
1333000 Saveall export fails.
1332996 Strategy editor is not updated with new declaration.
1333368 Default password for Administrator is left blank.
1331480 ControlHMI fonts get smaller on every click.
1333547 Saveall export fails.
1334307 SEQ code fails to compile after migrating from ICC to FCS.
1334417 DA command leaves strategy in checked out state.
37711439 Galaxy Migration from FCS 3.1 to 4.0 failed.
37713126 BreaklinkToTemplate has propagation issues for CALCA blocks.
37713237 ControlHMI Alarmborder issues.
37713625 BreakLinkToTemplate fails without a preceding command.
37930147 AlarmBorder issues with controlhmi dll.
37713166 GDEV faceplate displays wrong information.
38096828 Moving one block causes connection lines to change orientation.
38173389 SFC code is not retained on closing the editor.
37711446 SQL 2008 SP3 fails to install during CS 6.0 install.
37713232 Find not working for Graphics.
38565918 Control HMI runtime connection lines are distorted.

149
A P P E N D I X A
Historian Data Import Utility
This section describes the Historian Data Import Utility
Contents
• Historian Data Import Utility
• Importing Data from CSV Files
A.1 Historian Data Utility

The Historian Data Importer (aahImport.exe) is a stand-alone utility to import
existing history data into the historian history blocks. You can import data into
the history blocks, as long as the data is formatted according to a specific
format like CSV.
1. Verify that there is a Historian Server in the Environment such as
AWSE03. Create two Analog Tags through SMC. For example, Labtag1
and Labtag2.
2. Create a CSV file with data in ASCII format as this:
ASCII
|
DescType|1|Server Local|1|1
Labtag1|1|2017/07/11|00:01:00.000|1|20|192
Labtag1|1|2017/07/11|00:02:00.000|1|30|192
Labtag1|1|2017/07/11|00:03:00.000|1|40|192
Labtag2|1|2017/07/11|00:04:00.000|1|50|192
Labtag2|1|2017/07/11|00:05:00.000|1|50|192
3. Save the file. For example, as “LabTags4.csv” in “D:\ASC5”
4. Navigate to Start>Programs>Wonderware>Historian>Data Import
and enter the relevant details and select the Browse options and click
Process.

150 A. Historian Data Import Utility
Figure A-1. Historian Data Importer
5. On successful import, you can view the tag information in SQL Server.
6. The file format for a CSV Import is shown in Figure A-2.
Figure A-2. CSV Import File Format
A.2 Importing Data From CSV Files

You can import data into the history blocks, as long as the data is formatted
according to a specific comma-separated values (CSV) format.

A. Historian Data Import Utility 151
To import data:
1. Configure the data import folder where you want to store the formatted
CSV files. For more information, see Predefined CSV File Import Folders.
2. Add tag definitions to the Wonderware Historian database for the data
values you plan to import. Importing data for a tag that is not defined
results in an error. If you are importing legacy InTouch data, you can use
the Tag Importer to import a tagname database, which contains the tag
definitions. Otherwise, you must manually add the tag definitions. For
information on importing an InTouch tagname database, see Importing
and Exporting Configuration Information. For information on adding tag
definitions manually, see Configuring Tags. In what manuals are these
sections documented.
3. Verify whether the type of import is “normal” or "fast load." For more
information, see About Normal CSV File Imports and About Fast Load
CSV File Imports.
4. Verify if you want to insert original data for I/O Server tags. By default,
the system does not insert original data for I/O Server tags by a CSV file.
However, you can change this setting by changing the value of
AllowOriginals system parameter to 1. For more information on editing
system parameters, see Editing System Parameters.
5. Format the CSV file according to the import type. For more information,
see Formatting the CSV File for a Normal Import or Formatting the CSV
File for a Fast Load Import.

Schneider Electric Systems, Inc.
38 Neponset Avenue
Foxborough, MA 02035-2037
United States of America
www.schneider-electric.com
Global Customer Support

https://pasupport.schneider-electric.com

Control Software v7.1 Release Notes: Foxboro Evo Process Automation System

Uploaded by

Copyright:

Available Formats

Control Software v7.1 Release Notes: Foxboro Evo Process Automation System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Control Software v7.1 Release Notes: Foxboro Evo Process Automation System

Uploaded by

Copyright:

Available Formats

Foxboro Evo™

Process Automation System

Control Software v7.1

Before You Begin ...............................................ix

The Control Software v7.1

New Features .......................................................9

Control Software v7.1 Release Notes – B0750ST Rev D

Synchronizing ArchestrA and Control Block

User Notes .........................................................25

Control Software v7.1 Release Notes – B0750ST Rev D

Foxboro Control Software Export plugin ......................................... 64

Known Issues and

Control Software v7.1 Release Notes – B0750ST Rev D

Issues Resolved ..............................................145

Historian Data Import Utility...........................149

Control Software v7.1 Release Notes – B0750ST Rev D

The addition of either symbol to a "Danger" or

This is the safety alert symbol. It is used to alert you to

Before You Begin

About This Book

Control Software v7.1 Release Notes – B0750ST Rev D

Control Software Updates

The Control Software v7.1, I/A Series Software

Installation and Getting Started

Control Software v7.1 Release Notes – B0750ST Rev D

• Bulk Data Editor User's Guide (B0750AF)

• Logic Block Editor and Troubleshooting Tool User’s Guide (B0750BL)

End-User Graphical User Interface Configuration and Operation

Control Software v7.1 Release Notes – B0750ST Rev D

• Asset Condition Monitoring Installation Guide (B0750CR)

Wonderware Software Documentation

Control Software v7.1 Release Notes – B0750ST Rev D

The Control Software v7.1

This chapter gives an overview of the Control Software v7.1. installation.

1.1 Product Contents

Control Software v7.1 Release Notes – B0750ST Rev D

Table 1-1. Media Kit K0203BN-A Foxboro Evo™ Control Software

Part Number Description

Note *Control Software installs additional patches on top of

Wonderware P/N 06-2747 Wonderware Information Server 2014 R3

Part Number Description

Part Number Description

Control Software v7.1 Release Notes – B0750ST Rev D

Part Number Description

Part Number Description

Part Number Description

Part Number Description

Table 1-8. Foxboro Evo for DeviceNet v1.1 Installation DVD

Part Number Description

Table 1-9. Asset Condition Monitor Installation DVD

Part Number Description

Control Software v7.1 Release Notes – B0750ST Rev D

Note Wonderware System Platform2014 R3 is provided on a Dual Layer

The mixed mode systems supported include:

Table 1-10. Available Mixed Mode Systems Supporteda

Hardware/Software (Includes the Control Software CCS Local or

Servers - Control Core Services v9.4 on Windows Server 2016

Workstations - I/A v8.8 or Control Core Services v9.x on

Workstations - Control Core Services v9.4 or above on Windows