AK-1700-0079 DeltaV v14.3 Release Notes PDF

Knowledge Base Articles
DeltaV v14.3 Release Notes
Article ID: AK-1700-0079

Publish Date: 20 Dec 2018
Article Status: Approved
Article Type: Product Revision/Release
Required Action: Information Only
Recent Article Revision History:

Revision/Publish Description of Revision
20 Dec 2018 Modified to include details about Feature Pack 1, correct Hardware Compatibility Charts,
and update Known Issues section.
(See end of article for a complete revision history listing.)
Affected Products:
Product Line Category Device Version
DeltaV General Workstation Workstation General Workstation Products v14.3
1 Installation and Migration Notes
1.1 Read Me First
1.1.1 DeltaV Migration Paths
1.2 Pre-Upgrade Considerations
1.2.1 Supported Operating Systems
1.2.2 Batch and Advanced Unit Management Licensing
1.2.3 Operating System Upgrade Kits
1.2.4 Upgrade Kits for computers that are not licensed for Windows 10
1.2.5 Obtaining Operating System Images for computers that are licensed for Windows 10 and Windows Server
2016
1.2.6 Windows Operating System Installation and Configuration Instructions
1.2.7 Installation Instructions for Operating Systems Supported on DeltaV Releases
1.2.8 Workstation Requirements
1.2.9 ValveLink SNAP-ON Fieldbus
1.2.10 DeltaV Event Chronicle
1.2.11 Legacy Continuous Historian Upgrade
1.2.12 DeltaV Operate User Settings file
1.2.13 DeltaV Simulate
1.2.14 Manual Data Backup of DeltaV Add-in Products
1.2.15 Remote Workstation Connections to Multiple DeltaV Systems
1.3 Controller and I/O Requirements
1.3.1 DeltaV Controller Firewall and DeltaV SIS IPD Firewall
1.3.2 PK Controllers, EIOC and SZ Controllers
1.3.3 Hardware Replacement
1.3.4 Supported Controllers
1.4 Post-Upgrade Considerations
1.4.1 Alarm Enable (Enab) Check Box
1.4.2 Data Restore
1.4.3 I/O Card Upgrades
1.5 Controller Switchover Tips
1.6 Network I/O Card (CIOC, WIOC, EIOC, etc.) Switchover Tips
2 New Products and Features in DeltaV v14.3
2.1 Complementary Products
2.2 Controller Support
2.3 DeltaV PK Controller
2.3.1 Features and Enhancements
2.3.2 DeltaV Functional Areas Modified to Support this New Product
2.3.3 Impact for Users Upgrading to v14.3
Page 2 of 140
2.3.4 Impact for Users Upgrading from v14.3 to v14.3 Feature Pack One
2.3.5 Suggested Areas for Validation
2.4 Cybersecurity Considerations
2.4.2 DeltaV Functional Areas Modified to Support this Feature
2.4.3 Impact for Users Upgrading to DeltaV v14.3
2.4.4 Impact for Users Upgrading from v14.3 to v14.3 Feature Pack 1
2.5 Independent DeltaV Domain Controller
2.6 Secure File Open/Save Dialogs
2.7 DeltaV Live
2.7.5 DeltaV Live operations using Remote Clients
2.8 Memory Requirements for Dell Workstations, Servers, and Virtual Host Servers
2.9 Operating System and Dell Workstations and Servers
2.10 Virtual Studio
2.11 Process History View Enhancements
2.12 Graphic Deletion Improvements
Page 3 of 140
2.13 OPC UA
2.14 Scalable EIOC
2.15 EIOC PRP Redundancy
2.16 DeltaV Alarm Management Improvement
2.17 DeltaV Batch List View
2.17.2 DeltaV Functional Area Modified to Support this Feature
2.18 New SIS Function Blocks
2.19 Major Revisions for SIS Modules
2.20 Major Revision for CSLS
2.21 SIS Alarm Groups
Page 4 of 140
2.22 SIS I/O Simulation
2.23 Smart Commissioning for HART Devices
3 Improved Functionality in DeltaV v14.3
3.1 Partial Stroke Test Improvements
3.2 Status Propagation Enhancements in SIS Modules
3.3 SIS Security Enhancements
3.4 New Function Blocks
3.5 Blue Triangle Contributors
Page 5 of 140
3.6 Product System Warnings
3.7 Configurable Area Index
3.8 Upload Enhancements
3.9 Controller Switchover Enhancements
3.10 EtherNet/IP Control Tag Integration
3.11 DeltaV v14.3 Simulate Enhancements
3.11.3 Impact for Users upgrading to v14.3
3.12 New CHARMs I/O Card 2 (CIOC2)
Page 6 of 140
3.13 M-Series Controllers can have I/O Assigned from CIOCs and WIOCs
3.14 Distributed CHARMs
3.15 LS DI 120V AC Isolated Plus CHARM
4 Resolved Issues
4.1 Resolved Issues for Controller and I/O
4.2 Resolved Issues for Workstation
4.3 Resolved Issues for Batch
5 Known Issues in DeltaV v14.3
5.1 General
5.2 PK Controller
5.3 Smart Commissioning for HART devices
5.4 OPC UA
5.5 Batch Analytics
5.6 Connection Handling
5.7 Independent Domain Controller
5.8 DeltaV Live
5.9 Windows 10 or Windows Server 2016 Support
5.10 DeltaV Security Hardening
5.11 Secure Open Save Dialog
5.12 Cybersecurity
6 Compatibility
Page 7 of 140
6.1 Supported Workstation Components and Functionality
6.2 DeltaV-Supported Virtualization Hardware and Software
6.3 Hardware Compatibility Charts
6.3.1 M-series Hardware
6.3.2 S-series Hardware
6.3.3 S-series Traditional I/O
7 DeltaV SIS
7.1 Installation and Migration Notes for DeltaV SIS in v14.3
7.1.1 Pre-Upgrade Considerations
7.2 Resolved Issues in DeltaV SIS in v14.3
7.3 Tips for DeltaV SIS in v14.3
7.4 Known issues in DeltaV SIS in v14.3
7.4.1 SIS IO Simulation
7.4.2 Device Centric SIS Alarming
7.5 Compatibility Charts for DeltaV SIS v14.3
8 Obtaining the Latest Information
9 Registering your DeltaV System with Emerson
10 Product Technical Support
11 Controller Performance and Loading
12 Supporting Applications and Documentation
12.1 \DV_Extras (found on DVD 1)
12.2 \_Support (found on DVD 1)
12.3 Documentation Library DVD
13 Media Pack Information
13.1 DeltaV v14.3 Media Set
13.1.1 DeltaV v14.3 Feature Pack 1 DVD Media Shipments
13.1.2 DeltaV v14.3 Feature Pack 1 Installer Upgrade DVD Media
13.1.3 DeltaV v14.3 Feature Pack 1 PK Standalone Engineering USB Media and Virt ual Machine
13.1.4 DeltaV v14.3 Feature Pack 1 PK Local Panel New USB Media
13.1.5 DeltaV v14.3 Feature Pack 1 PK Standalone Engineering Upgrade USB Media and Virtual Machine
13.1.6 DeltaV v14.3 Feature Pack 1 PK Local Panel Upgrade USB Media
Page 8 of 140
1 Installation and Migration Notes
Thank you for purchasing a DeltaV Digital Automation System. You will find the DeltaV system functionally powerful and
flexible while being easy to learn and use.
This Knowledge Base Article, AK-1700-0079, contains the latest release information on DeltaV v14.3.
DeltaV v14.3 can be downloaded from the DeltaV Guardian website or its DVD media requested through the Guardian
Website. Specific installation and upgrade instructions are available in the downloaded files and the DVD. Upgrade and
migration instructions for DeltaV v14.3 are in the DVUpgrade.chm file located at the root of DVD1.
1.1 Read Me First
Important: You must first read the DeltaV Release Notes and understand all pertinent information regarding
upgrading your system before performing the upgrade.
For DeltaV v14.3.0.6843 systems, you must install the DeltaV v14.3.0.6984 Feature Pack 1 for DeltaV and
PK Standalone systems. Refer to section 13 Media Pack Information for the details about the recently
released DeltaV v14.3 installation media and its applicability. DeltaV v14.3.0.6984 Feature Pack 1 is also
discussed in the Mandatory Updates section in KBA AK-1700-0081: DeltaV v14.3 Software Updates.
Furthermore, for DeltaV v14.3.0.6843 systems, before you install the DeltaV v14.3.0.6984 Feature Pack 1 for
PK Standalone system, refer to the DeltaV Installation instructions located in the Documentation Library
DVD.
Not following the upgrade procedure provided in the links in the reference documents may result in lost and
unrecoverable work. Refer to KBA NK-1800-0972: DeltaV v14.3 Feature Pack 1 Implementation on PK
Controller Engineering Software for more information.
Moreover, after installing DeltaV v14.3.0.6984 Feature Pack 1 and before replacing a failed redundant
controller partner (PK, EIOC, and SZ), refer to KBA NK-1800-0983: Hardware Replacement of PK, EIOC,
and SZ Controllers on DeltaV v14.3 Feature Pack 1 for more information and the procedure to avoid the
issue of replacement controllers not being automatically commissioned.
1.1.1 DeltaV Migration Paths

Please refer to the recommended migration paths listed in the following table for upgrades to v14.3.
Earlier DeltaV Release Notes document optional intermediate paths. Upgrades to the current DeltaV version are
supported only from certain earlier releases. The DeltaV Upgrade Wizard will not permit an upgrade to begin from a
release that is not supported.
For important guidelines and information for users to consider before performing and during DeltaV system upgrades,
refer to KBA AP-0600-0101: Important Recommendations for DeltaV System Upgrades .
v1.x Contact Emerson Process Management Global Service Center
v5.x (excluding
Upgrade to 5.3 SP2, then 7.4.2, then 10.3, apply SP1, then 12.3.1, and then 14.3*
5.3 SP2)
v5.3.2 or v5.3
Upgrade to 7.4.2, then 10.3, apply SP1, then 12.3.1, and then 14.3*
SP2
Page 9 of 140
v6.1 through
Upgrade to 6.3.4, then 8.4.2, then 10.3.1, then 12.3.1, and then 14.3*
6.3.2
v6.3 SP3 Upgrade to 6.3.4, then 8.4.2, then 10.3.1, then 12.3.1, and then 14.3*
v6.3.4 or v6.3
Upgrade to 8.4.2, then 10.3.1, then 12.3.1, and then 14.3*
SP4
v7.1 Upgrade to 7.4.2, then 10.3, apply SP1, then 12.3.1, and then 14.3*
Apply SP1, then apply SP2, then upgrade to 10.3, apply SP1, then 12.3.1, and then
v7.4
14.3*
v7.4.1 Apply SP2, then upgrade to 10.3, apply SP1, then 12.3.1, and then 14.3*
v7.4.2 Upgrade to 10.3, apply SP1, then 12.3.1, and then 14.3*
v8.3 Upgrade to 8.4.2, then 11.3, apply SP1, and then 14.3*
(A) Apply SP1, then SP2, then upgrade to 10.3.1, then 12.3.1, and then 14.3*
v8.4 Or
(B) Apply SP1, then SP2, then upgrade to 11.3, apply SP1, and then 14.3*
(A) Apply SP2, then upgrade to 10.3.1, then 12.3.1, and then 14.3
v8.4.1 Or
(B) Apply SP2, then upgrade to 11.3, apply SP1, and then 14.3*
(A) Upgrade to 10.3.1, then 12.3.1, and then 14.3*

v8.4.2 Or
(B) Upgrade to 11.3, apply SP1, and then 14.3*
v9.3 Apply SP1, then upgrade to 11.3.1, and then 14.3*
v9.3.1 Upgrade to 11.3.1, and then 14.3*
v10.3 Apply SP1, then upgrade to 12.3.1, and then 14.3*
v10.3.1 Upgrade to 12.3.1, and then 14.3*
v11.3 Apply SP1, and then upgrade to 14.3*
v11.3.1 Upgrade to 14.3*
v11.3.2 Upgrade to 14.3*
V12.3 Apply SP1, and then upgrade to 14.3*
V12.3.1 Upgrade to 14.3*
V13.3 Apply SP1, and then upgrade to 14.3*
Page 10 of 140
V13.3.1 Upgrade to 14.3*
Table 1-1: DeltaV Migration Path
Important: *For DeltaV v14.3.0.6843 systems, it is mandatory to install DeltaV v14.3.0.6984 Feature Pack 1
update. Refer to section 13 Media Pack Information for the details.
1.2 Pre-Upgrade Considerations
Important: If you are performing a time-critical or online upgrade, please call the Global Service Center or
your local support company for assistance before making the upgrade. This enables Emerson Process
Management to better assist you during the upgrade.
At least one DeltaV workstation connected to the DeltaV network must remain running in the previous version of DeltaV
until all controllers have been upgraded. Otherwise, controllers that have not been upgraded may not be able to resolve
external references with other nodes. This last workstation may then be upgraded to v14.3 after all of the controllers have
been upgraded.
DeltaV v14.3 may require the upgrade of complementary products, such as DeltaV Analyze, PlantWeb M essenger, and
Plantwide Event Historian, to ensure compatibility. Refer to section 6 Compatibility for more information.
1.2.1 Supported Operating Systems

 Windows 10 Enterprise 2016 LTSB and Windows Server 2016 (64-bit)
Note: Installing DeltaV on a 32-bit OS will generate the following message:
Figure 1-1: Error message when installing DeltaV on a 32-bit OS
Note: Installing DeltaV on a 64-bit OS that is not supported will generate the following message:
Figure 1-2: Error message when installing DeltaV on an unsupported 64-bit OS
Page 11 of 140
1.2.2 Batch and Advanced Unit Management Licensing
The DST-based batch licensing in place for DeltaV releases v11.3.1 and earlier will no longer function in v12.3 or later;
thus, users will not be able to download and run their Batch configurations after an upgrade.
Prior to upgrading to DeltaV v12.3 or later, systems with DST-based Batch and/or AUM licenses must have the system
configuration assessed using a Configuration Assessment Utility provided by Emerson Process Management.
KBA NK-1300-0067: DeltaV Batch/VCAT and Insight Licensing Changes Introduced starting DeltaV v12.3 provides
detailed information on the purpose and use of the Configuration Assessment Utility, and the process for obtaining the
replacement licenses from Emerson Process Management.
When the new, unit-based Batch and/or AUM licenses are issued, customers must load the licenses on their DeltaV
system before upgrading to DeltaV v14.3. After upgrading to DeltaV v14.3, run the DeltaV Licensing Report to check that
the assigned Batch licenses are sufficient for the Units configured. Ensure that the system’s Batch and/or AUM
functionality is operating as expected using the new, unit-based licenses.
1.2.3 Operating System Upgrade Kits

Emerson provides operating system upgrade kits to allow the quick and correct installation of the new Windows 10 64-bit
operating systems on DeltaV computers that were originally purchased from Emerson with Windows XP.
Server class machines supported for v14.3 have a Windows Server 2016 OS license and COA; thus, no upgrade kits are
required.
1.2.4 Upgrade Kits for computers that are not licensed for Windows 10
If you wish to upgrade an existing system to v14.3, but the system does not currently have computers licensed for
Windows 10, you must purchase an upgrade kit for every computer that will be upgraded.
The following table lists the Dell computers that are supported for operating system upgrade. Items included in the
Operating System upgrade kits are also listed.
Dell computers with upgrade kits that are not included in the table do not support upgrades to Windows 10.
Computer Operating System Package Contents
 Dell Precision R5500XL

 Dell Precision T3600XL
 Dell Precision T5810XL  Operating System Media
 Dell Precision T5820XL  End-User License Agreement
 Dell Precision R7910XL Upgrades Windows 7 (64-bit)
operating system to Windows 10  Includes Operator Multi-lingual
 Dell Precision R7920XL (64-bit) User Interface Media
 Dell Optiplex 7010  Certificate of Authenticity (COA)
 Dell XE2 Label
 Dell Optiplex 3020
 Dell Optiplex 3050
Table 1-2: Dell computers supported for OS upgrade
1.2.5 Obtaining Operating System Images for computers that are licensed for Windows 10 and Windows Server
2016
Customers can contact Emerson to order the following:
 Image DVDs to install Windows 10 (64-bit) on existing computers that were shipped from Dell with a Windows 10
COA, whether they have been downgraded to XP or running Windows 10 (32-bit). You will need only one image
DVD per type of computer.
Page 12 of 140
1.2.6 Windows Operating System Installation and Configuration Instructions
 On workstations and servers shipped with Dell OEM license – For the appropriate installation instructions,
refer to KBA AP-1000-0015: Installation Instructions for Operating Systems Supported on DeltaV Releases .
 On workstations and servers shipped with Embedded OS license – For the appropriate installation
instructions, refer to KBA NK-1300-0132: Installation Instructions for Windows 7 64-bit and Windows 2008 R2
Operating Systems on Supported DeltaV Computers.
1.2.7 Installation Instructions for Operating Systems Supported on DeltaV Releases

The following KBA contains links to installation instructions for the operating systems supported on DeltaV-released
systems:
 AP-1000-0015: Installation Instructions for Operating Systems Supported on DeltaV Releases
The tables in this KBA defines which operating system is supported for each DeltaV release, starting with DeltaV v7.4.x,
and provides link to the following instructions:
 Windows XP and Server 2003 Installation Instructions for DeltaV Systems
 Windows Vista and Server 2008 Installation Instructions for DeltaV Systems
 Windows 7 and Server 2008 Installation Instructions for DeltaV Systems
 Windows 7 and Server 2008 Operating System Manual Installation Instructions
 Installation Instructions for Embedded Operating Systems Supported on DeltaV Releases
 Installation Instructions for 64-bit Embedded Operating Systems on Supported DeltaV Computers
 Windows 10 IoT Enterprise (64-bit) Windows Server 2016 (64-bit)
1.2.8 Workstation Requirements

 Workstation Name
The workstation name should be in UPPERCASE. If it is in lowercase, DeltaV Workstation Configuration forces
the change, but this could cause issues with the Windows OS as it does not recognize the name change.
When naming a Redundant Batch Executive Application Station, the following names are reserved and should not
be used: DLE, DLINK, NAM, RBEX, RCON, RDN, RED, RMIR, ROPC, TYPE, and UBT. In addition, the name of
the Batch Executive should not contain the characters “_S” (e.g. BATCH_SERV, DVAPP_STA, etc.). Note that
the characters “_S” are automatically appended to the preferred standby node. (Ref TFS202559)
 Keyboard Requirements for DeltaV
Only an English language keyboard should be used on an English Language DeltaV Release. Any other
combination is regarded as untested and not supported. This is true for all previous releases of DeltaV and all
languages. DeltaV is only supported with a keyboard that matches the DeltaV software language (e.g. English
keyboard on English DeltaV system, Chinese keyboard on Chinese DeltaV system, etc.).
 Domain Name
DeltaV supports an underscore (_) in the domain name. Thus, do not be concerned when you receive a message
that indicates that some DNS server products may not support that character. You can proceed with the
installation.
However, if the DeltaV system will be used with a web service (for example, DeltaV Web Server or DeltaV
Analyze), the domain name must not contain an underscore.
Page 13 of 140
1.2.9 ValveLink SNAP-ON Fieldbus
ValveLink SNAP-ON for DeltaV is not supported with DeltaV v9.3 and later. DeltaVFOUNDATION™ Fieldbus customers
must use the AMS ValveLink SNAP-ON in conjunction with AMS Device Manager.
Customers using existing ValveLink SNAP-ON for DeltaV can import their historical data to the AMS Device Manager
database for use with the AMS ValveLink SNAP-ON application.
Before upgrading the current DeltaV software version, please refer to the Migrating AMS ValveLink SNAP-ON Data
section of the AMS Suite: Intelligent Device Manager System Planning Guide for Use with DeltaV documentation for
a more detailed procedure.
1.2.10 DeltaV Event Chronicle

Due to improvements made to the DeltaV Event Chronicle database in v9.3, upgrading a pre-v9.3 system to v14.3
requires the DeltaV Batch Historian to collect any and all “migrated” chronicle events before it starts collecting events fro m
the new Event Chronicle database.
When the DeltaV Batch Historian is started for the first time after the upgrade, it will automatically detect migrated Event
Chronicle databases in all workstations that were originally enabled for Alarms and Events, and collect all the data found
in them.
The user can verify the status of data collection for each workstation using the DeltaV Batch Historian Administration
application. A node collection status of “Idle” would signify that the transfer of events is complete. Once all nodes show a
status of “Idle”, the DeltaV Batch Historian can be manually stopped and then restarted. This action will tell the DeltaV
Batch Historian that all migrated history has been collected; thus, it can begin collecting data from the new event chronicle
database.
1.2.11 Legacy Continuous Historian Upgrade

 Starting with DeltaV v12.3, the Legacy Historian is no longer available. Users have the option to migrate to an
Enterprise Historian, the DeltaV Continuous Historian or the new Advanced Continuous Historian.
If you choose to upgrade your existing Legacy Historian to an Enterprise Historian, migrate the Legacy Historian
data properly by following the procedure provided by OSIsoft.
If you choose to upgrade your Legacy Historian to DeltaV Continuous Historian, references have been added
about the DeltaV™ Historian Upgrade Planning Guide white paper in the DeltaV Upgrade Wizard help topics.
 For more information about planning an upgrade from the Legacy Historian, refer to the DeltaV™ Historian
Upgrade Planning Guide, which is also available from your Emerson Process Management field sales office or
local business partner.
1.2.12 DeltaV Operate User Settings file

If you have created a custom UserSettings file that replaced the standard User_Ref file, a special procedure must be done
before upgrading.
If upgrading from DeltaV v8.4 (through an approved migration path), you can continue to use that file version of
UserSettings; however, you will not be able to make use of any newer functionality. Therefore, we strongly recommend
moving to the newer file version.
However, if upgrading from versions earlier than DeltaV v8.4 (through an approved migration path), you must rename
your UserSettings files. DeltaV Operate in v9.3 and later will not function with the older UserSettings files. Rename the
files after backing them up.
Refer to Migrating DeltaV Operate Settings Files to the Current DeltaV Version in the DVUpgrade.chm file on DVD 1
for specific instructions.
Page 14 of 140
1.2.13 DeltaV Simulate
When upgrading a workstation installed as DeltaV Simulate, check to see if the folder DeltaV\DVData\POWERUP exists
before selecting YES to Restore the DeltaV Data. The Restore step will not be completed successfully without a
POWERUP directory, even though it is not used on a Simulate workstation.
If this folder does not exist, create a POWERUP folder in DeltaV/DVData. Using Notepad or a similar application, create a
blank text file, save it in the POWERUP folder, and then proceed with the Restore step.
1.2.14 Manual Data Backup of DeltaV Add-in Products

All data files created using any of the DeltaV Add-in products (e.g. DeltaV OPC Excel Add-in) must be manually backed
up as they can exist anywhere and will not be backed up by the DeltaV Upgrade Wizard. It is your responsibility to be sure
you have backed up all the non-DeltaV data you want to keep.
1.2.15 Remote Workstation Connections to Multiple DeltaV Systems

For Remote Workstations, the DeltaV Upgrade Wizard backs up and restores the data files associated with the current
active connection only (i.e. the DeltaV system that the remote workstation is currently set up to communicate with).
For Remote workstations configured to connect to multiple DeltaV systems, you must use the Re mote Access Control
application to configure the connection to other DeltaV systems after these have been upgraded. Only the active remote
connection will be restored when the Remote Workstation has been upgraded.
1.3 Controller and I/O Requirements
1.3.1 DeltaV Controller Firewall and DeltaV SIS IPD Firewall

When upgrading from versions prior to v14.3 and the DeltaV system being upgraded contains the Controller and/or SIS
IPD Firewalls, an update to the firewall firmware must be performed. If not upgraded first, the firewall will block the
new Multicast address causing all controller-to-controller module level references to not resolve.
The Multicast address for the DeltaV system was changed in v13.3. Because of this change, if a system contains
firewalls, they must be upgraded first. Refer to the DeltaV Upgrade Wizard for further information on systems containing
firewalls that must be upgraded prior to performing an online upgrade (Ref: TFS167093).
The following KBAs can also be reviewed for more information on configuring and upgrading:
 AP-0600-0127: Using the DeltaV Controller Firewall
 AP-0800-0061: Using the DeltaV SIS Intrusion Protection Device
1.3.2 PK Controllers, EIOC and SZ Controllers

Upgrading existing v14.3.0.6843 systems to DeltaV v14.3.0.6984 requires a mandatory firmware upgrade to existing
hardware. Prior to applying mandatory Feature Pack 1 firmware to PK, SZ controllers and EIOCs, refer to the DeltaV
installation instructions located in the Documentation Library DVD. Not following the installation procedure could disrupt
ACN and device network communication.
Important: Online upgrade of PK Controller is not supported.
1.3.3 Hardware Replacement

After installing DeltaV v14.3.0.6984 Feature Pack 1 and before replacing a failed redundant controller partner (PK, EIOC,
and SZ) refer to KBA NK-1800-0983: Hardware Replacement of PK, EIOC, and SZ Controllers on DeltaV v14.3 Feature Pack
1 for more information.
It is recommended to flash upgrade all replacement hardware in a non-production environment to match the software
version of the existing hardware before placing them in production system.
Failure to update the software version will result in the standby replacement not being automatically commissioned as
expected, and the red LED error light on the hardware will begin to flash. Also, the hardware will not appear under the
Decommissioned Nodes tab in DeltaV Explorer.
Page 15 of 140
1.3.4 Supported Controllers
MD controllers are not supported in v14.3 systems. You must upgrade to a supported controller prior to starting the DeltaV
upgrade.
MD Plus controllers are supported with v7 and later systems. MX controllers are supported with v10.3 or later. MQ
Controller is supported with v10.3.1 and above by applying a Hotfix to earlier DeltaV Systems.
SDPlus, SX, and SQ controllers are supported with v11.3 or later.
SZ controllers are supported starting with v12.3.
If you have previously upgraded your controllers to MQ or SQ controllers, verify that the controller model is correct based
on the DeltaV Explorer controller's properties page. If the controllers' model in DeltaV Explorer has not been updated to
MQ or SQ, download the Setup Data for the controller. Otherwise, the affected controller and its ass ociated configuration
will not be imported, resulting in a failed upgrade.
1.4 Post-Upgrade Considerations
1.4.1 Alarm Enable (Enab) Check Box

Starting in DeltaV V14.3, the Alarm Enable (Enab) check box is read-only in out-of-box detail displays, allowing the user to
view but not change the enabled alarm state. A new alternative feature in v14.3 allows users with the required field
permission to remove or restore an alarm to service using the Out -Of-Service (OOS field) check box in the out-of-box
detail displays. OOS is a form of alarm suppression.
DeltaV system owners that use (reference in configurations) out -of-box detail displays and wish to continue allowing users
to write as well as read to the ENAB field, will need to save a copy of their pre-migration detail displays, which are located
in the files folder DeltaV\DVData\Graphics-iFix\Pic\Detail and DetailFB. After migration, the original files can then be
recopied to the folders, replacing the v14 out-of-box displays.
1.4.2 Data Restore

If you have a custom schedule for DeltaV Operate, you must manually copy the schedule from the
DeltaV\DVData\Graphics-iFix\PDB folder on the ProfessionalPLUS to all Operator Stations after the upgrade.
If you use custom alarm sound files (*.wav), you must manually copy these files from the ProfessionalPLUS server to all
other workstations after the upgrade. The files are in the DeltaV\DVData\sound folder. Copy them from the
ProfessionalPLUS station to all other DeltaV workstations accessing DeltaV Operate.
Important: If you have custom alarm sound files that are unique for each workstation, you must manually
copy these files from the DeltaV\DVData\sound folder on the source workstation. Copying the files from the
ProfessionalPLUS server will cause all workstations to use the same .wav files.
1.4.3 I/O Card Upgrades

I/O firmware does not require flashing when DeltaV software is upgraded (unless you are experiencing I/O issues that
were resolved in this version of the DeltaV software).
Important: If PROVOX I/O is installed on a system being upgraded, ensure that the I/ O Interfaces are
flashed as part of the v14.3 installation.
Please see section 4 Resolved Issues to check if any of the issues you were experiencing previously have been
resolved.
If the issue(s) has/have been addressed, you should flash the I/O cards, if possible.
Important: We recommend not upgrading Series 1 8-channel AI/AO v2.25 and v2.32. During the migration
process, these revisions will not be automatically selected for upgrade. However, manually selecting and
flashing these revisions may cause a small percentage to experience an issue during the flash upgrade
process.
Page 16 of 140
While the current revision being shipped is v2.42, the firmware changes will apply to only a few users. If you
think that you need to upgrade, please contact the Global Service Center for assistance.
1.5 Controller Switchover Tips

When performing a controller switchover as part of an Online Upgrade, the older controller software revision may have
issues that must be considered to ensure a bump-less switchover.
It is strongly recommended the Controller Redundancy Analyzer (CRA) utilit y be used on the controller FHX file. The utility
reads an exported FHX file and identifies configuration practices that may cause an output disruption on a controller
switchover.
Important: We strongly recommend that you use this standalone utility prior to running the DeltaV Upgrade
Wizard.
Documentation and the Utility are included with the DeltaV release software.
When flash upgrading redundant controllers online, do not perform a controller switchover until the “PAVAIL” parameter
on the Redundancy Subsystem is "YES", the “FreTim” parameter on the Standby Controller is 100% for 60 seconds, and
the FreMem parameter on the Standby Controller stops decreasing.
1.6 Network I/O Card (CIOC, WIOC, EIOC, etc.) Switchover Tips
When flash upgrading redundant network I/O cards online, do not perform a switchover until the “PAVAIL” parameter on
the Redundancy Subsystem is "YES", and the Redundancy Subsystem’s Status parameter is “GOOD” (which might take
about 2 additional minutes).
Page 17 of 140
2 New Products and Features in DeltaV v14.3
This section outlines the new products and features that come with DeltaV v14.3.
2.1 Complementary Products

Some complementary products will be supported in the DeltaV v14.3 release.
KBA AK-1600-0076: Complementary Software List for DeltaV will be updated with the complimentary products supported
in DeltaV v14.3.
Note that the following products will not be supported after v13.3.1:
 DeltaV Operate for PROVOX
 Plant Messenger (replaced by DeltaV Mobile)
 Executive Portal (replaced by DeltaV Mobile)
 OPC Pager (replaced by DeltaV Mobile)
2.2 Controller Support

Compatible controllers in v14.3 include MD Plus, SD Plus, MX, SX, MQ, SQ, PK, and PROVOX and RS3 migration
controllers, as well as the SZ controller for DeltaV SIS.
The MD controller is not supported in v14.3.
2.3 DeltaV PK Controller

The following are the features of DeltaV PK Controller in DeltaV v14.3:
 In v14.3, we are introducing the new DeltaV PK Controller, which can be implemented as standalone (e.g. not
part of a DeltaV system) or integrated with a DeltaV system.
 The DeltaV PK controller is compatible with v14.3 and greater. It is not backward-compatible with previous DeltaV
software versions. However, the DeltaV PK controller can be deployed standalone on v14.3, at a site with an
existing DeltaV system that is running an earlier version of DeltaV, and then later be integrated into the DeltaV
system after the DeltaV system has been upgraded to v14.3 or greater.
 The DeltaV PK Controller provides a control solution for smaller-scale applications such as skid units or small unit
operations. It is designed to operate in a standalone fashion, meaning that it runs without requiring a connection
to a server, panel HMI, or other typical DCS elements.
 Any time after being configured to run in a standalone fashion, the standalone DeltaV PK Controller may be
merged into a larger DeltaV system. The merging process incorporates the database from the standalone PK
Controller into the larger DeltaV Database, resulting in a single, native database and system. This process
addresses potential conflicts with tags, thereby eliminating the pains associated with mapping two systems
together.
 DeltaV PK Controller offers the following benefits in v14:
o Runs standalone or as part of a DeltaV system
o Seamless merging into DeltaV
o Easily swap and restart a standalone simplex controller
o Easy redundancy
o Flexibility in I/O
o Integrated safety
o Easily connect third-party devices
Page 18 of 140
o Faster module execution
2.3.2 DeltaV Functional Areas Modified to Support this New Product

None.

To take advantage of DeltaV PK Controller, users must have DeltaV or DeltaV PK Standalone Software Version 14.3.
DeltaV PK Controller is not backward-compatible with any version of DeltaV prior to v14.3.
2.3.4 Impact for Users Upgrading from v14.3 to v14.3 Feature Pack One
Applying the 14.3 FP1 firmware to online PK controllers is not supported as it can disrupt communication.

None.
2.4 Cybersecurity Considerations

The following are the features of DeltaV Cybersecurity in DeltaV v14.3:
 Workstation’s hardening to address the CIS Benchmarks regarding Microsoft Windows, Microsoft SQL, and
Microsoft IIS settings on DeltaV workstations and servers
 Achilles Communications certification – the following devices are Achilles Level 1 certified in DeltaV v14.3: MD+
and SD+ Controllers. The following devices are Achilles Level 2 certified: MQ, MX, SQ, SX, PK and SZ
Controllers, EIOC, WIOC, and CIOC (hardware v.2)
 All embedded devices’ firmware included in the DeltaV v14.3 media are digitally signed and the DeltaV Controller
Upgrade Wizard is checking the file integrity (validating the digital signature of the firmware files) before sending
to the embedded devices.
 The Network Device Command Center has been enhanced to allow SecureShell access (SSH) to DeltaV Smart
Switches using the application menu. DeltaV Smart Switch ports are identified with symbols depending when they
are identified as: uplink ports (U), open/ignored from the locking algorithm (O), or mirroring probe ports (P).
 HART-IP communications in the DeltaV Wireless I/O Card (WIOC) can be managed to allow: enable/disable
options, selection of HART-IP port from a drop-down list, and definition of an access control list based on IP
addresses that will be allowed to use the selected HART-IP port. All settings are available in DeltaV Explorer
when setting up WIOCs.
 Support for Microsoft Credential Guard and Device Guard security features
Microsoft Credential Guard and Device Guard are designed to protect machines and credentials from possible
cyber-attacks. In DeltaV v14.3, two new features are introduced to address the minimum requirements of
Microsoft Credential Guard and Device Guard. Credential Guard and Device Guard will not be enabled by default,
and users who want to implement these features will need to follow instructions that will be provided in an
upcoming Knowledge Base Article. For more information please refer to the Credential Guard and Device Guard
for DeltaV Systems whitepaper.
Page 19 of 140
 Operating system, SQL, and IIS Settings
 Embedded devices firmware
 DeltaV Controller Upgrade Wizard
 Network Device Command Center and the DeltaV Smart Switches
 DeltaV Explorer menus specific to WIOC configuration
 DeltaV workstations and servers, DCOM settings, operating system configuration to allow users to enable
Microsoft Credential Guard and Device Guard

Workstation’s hardening is automatically deployed once DeltaV installation is performed. The same applies to Achilles
certification once the embedded devices are also upgraded with the files available in the DeltaV v14.3 media.
The enhanced DeltaV Controller Upgrade Wizard in DeltaV v14.3 will not allow unsigned files or tampered with files to be
sent to embedded devices.
To take advantage of new features available in the DeltaV Smart Switches, users are required to upgrade the DeltaV
Smart Switches to firmware version 9.0.12 at least and enable SSH communications in the switch following instructions
from KBA AK-1000-0022: DeltaV Smart Switch and Safety Switch Software Release Information.
To take advantage of the HART-IP access control list, WIOCs must be upgraded to the latest firmware version available in
the DeltaV v14.3 media.
To take advantage of Credential Guard and Device Guard, a comprehensive instructions list must be followed by users.
This list includes supported workstations and servers that will need to have a Trusted Platform Module (TPM) v2.0,
changed system settings and the adoption of the Independent DeltaV Domain Controller feature in the system.
None.

More intrusive changes to the DeltaV system such as: adding a new server role, or enabling two-factor authentication,
among others, may require additional steps to be completed based on new hardening settings recommended by the CIS
Benchmark. Please consult the Guardian Support for additional information or reach out to the Global Service Center in
case any issues are encountered after upgrading to DeltaV v14.3.
A plan is required before enabling Credential Guard and or/Device Guard. Please consult KBA with instructions to get this
protection feature enabled (it is optional and turned off upon DeltaV system installation).
2.5 Independent DeltaV Domain Controller

The independent DeltaV Domain Controller is an optional feature in DeltaV v14.3 and greater. Domain controllers are
typically installed on nodes in locations with restricted access and with very few peripherals attached to them. The primary
goal of this isolation is to prevent credentials and/or the domain controllers from being improperly accessed. The main use
cases for the Independent DeltaV Domain Controller based on DeltaV system applications are as follows:
 Domain Controllers’ isolation
 Support for Microsoft Credential Guard deployment
 Release the ProfessionalPLUS station from running the domain controller role in domain environments
 Simplify upgrades
Please refer to the Independent DeltaV Domain Controller whitepaper for additional information.
Page 20 of 140
 New Independent DeltaV Domain Controller Setup App
 Additional offering of DeltaV servers to be used as Independent DeltaV Domain Controllers
 DeltaV installation and upgrades

The Independent DeltaV Domain Controller is an optional feature that is selected during DeltaV installation, or an upgrade
to DeltaV v14.3. The minimum requirement to enable Independent DeltaV Domain Controllers is to have additional
servers (provided by Emerson: SE2708C01 and/or SE2709C01) that will be used to run as domain controllers in a DeltaV
domain environment.
This feature allows segmentation of the domain controllers in the network (using DeltaV Firewall-IPD running a specific
configuration to address domain controller functions).
Segregation of duties is also easier to configure when there are servers dedicated to domain administration (Independent
DeltaV Domain Controllers) and DeltaV administration (ProfessionalPLUS).
To fully support Credential Guard deployments, the Independent DeltaV Domain Controller is an important feature as the
new Microsoft protection feature is not supported on domain controllers ; hence, ProfessionalPLUS stations shall be
configured to run DeltaV functions only using the Independent DeltaV Domain Controller.
None.

This is a new feature in the release, and the impact is applicable during installation and upgrades. The feature is optional,
so users much decide to implement the Independent DeltaV Domain Controller and account for the additional servers to
add to the system before enabling this feature.
Emerson recommends a thorough system architecture and documentation review before performing the upgrade to a
system with Independent DeltaV Domain Controllers. The DeltaV upgrade process has changed for the Independent
DeltaV Domain Controller and it is automating many of the manual steps required for upgrades, but the upgrade order
must be respected, and some manual steps are still required (e.g. operating system installation is always required when
upgrading to a DeltaV system with Independent DeltaV Domain Controllers.).
2.6 Secure File Open/Save Dialogs

Further harden the DeltaV workstations by ensuring that the DeltaV Basic Operator Role (aka. “restricted user”) is locked
out of access to the Windows operating system file structure as much as possible and that the NTFS file security settings
are all correctly configured for this user role to the most restrictive security settings possible of these functions (the us er
has “least privilege” to the file system).

 Some DeltaV Application dialogs (Process History View, Batch History View, etc.)
 Operating System file and folder permissions with DeltaV workstations and servers
 DeltaV applications access control list
 DeltaV Operate standard toolbar
 Print-to-file function
Page 21 of 140
Some DeltaV applications were changed to limit access to the Windows directory and desktop access by means of
custom dialogs, or in certain cases via UI automation. The biggest impact was done on applications exposed within
DeltaV Operate, e.g. the DeltaV Explorer launch button is now hidden when Basic Operators are logged on. Basic
Operators are not allowed to print to file in DeltaV v14.3.
DeltaV file and folder permissions were revisited to make sure the DeltaV Basic Operator, DeltaV Basic Configure, and
DeltaV Windows groups are configured in the system correctly to set the right privileges to users that join each of these
groups. The same applies to the access control list applied to system applications which was hardened to respect the
least privileged approach. Books Online has been updated to explain the specific privileges allowed per restricted users
group.
DeltaV User Manager was also changed to prevent assignment of configuration keys to Basic Operators. This change
applies to new users created in the system with DeltaV v14.3, so existing users before an upgrade to DeltaV v14.3 are not
impacted by this change, although Emerson recommends that users manually remove configuration keys from Basic
Operators to attain a better security posture, and to make sure users do not run into access mismatches when launching
applications.
None.

Revisit the list of DeltaV users upon upgrade to DeltaV v14.3 to make sure the privileges set to them is aligned with the
new least privilege users approach. This is even more important if any existing Basic Operators were assigned
configuration keys before the upgrade to DeltaV v14.3, or users assigned to the Basic Configuration group were assigned
any administrative privileges in previous versions of DeltaV.
Review the new access control list settings of DeltaV applications described in Books Online to understand the limitations
that restricted users will experience when using DeltaV systems. Some applications, especially the ones that require
administrative privileges or configuration rights can no longer be launched by Basic Operators and/or users in the B asic
Configuration group.
DeltaV Basic Operators cannot print to file (PDF, XML, TXT, etc.) in DeltaV v14.3. Access to the print to file dialogs are
controlled by the underlying Microsoft Windows operating system and can provide access to the Windows direc tories
even for restricted users; therefore, upon installation of DeltaV v14.3, users assigned to the Basic Operators group will not
be allowed to print to file in this release. These restricted users can still print using regular printers configured in th e
system and Emerson recommends that to be the case for Basic Operators to comply with the latest cybersecurity best
practices.
2.7 DeltaV Live

Note: DeltaV Live is included in DeltaV v14.3.0.6984 Feature Pack 1. Feature Pack 1 can only be installed
on systems already installed with DeltaV v14.3.0.6843. Refer to section 13 Media Pack Information for
details on the different released DeltaV v14.3 installation media and their applicability.

Emerson’s brand new, built-for-purpos e operations experience. DeltaV Live is full of new features that are aimed to
reduce complexity, increase efficiencies, and provide operators with state-of-the-arts graphics that allow them to make
better and quicker decisions. Its design utilizes Human Centered Design principles from the ground up, making the
software intuitive and easy to use.
Some of the new features in DeltaV Live include:
 Operator Interactive Areas: Monitor parameters in Operator-specific Watch Areas
 State-of-the-Art Class-based reusable objects, known as GEMs
Page 22 of 140
 Built-in Support for Industry Standards (ISA-101.01) and Best Practices (Center for Operator Performance)
o Display Hierarchies
o Alarm Rollups
o Coordinated Navigation
 Native HTML5 graphics
o Ready for Mobility and included in the DeltaV Mobile road map
 Engineering Efficiency – Ease of configuration
o Smart line intersections
o Use of graphical standard values
o Use of Functions to convert values of one type into values of a different type
 Multiple Language Support
 No dependency on display resolution
 Search with thumbnails
o Search by name, title, description
 Switch themes on the fly

Multiple new applications were introduced for this brand-new operations experience in v14.3. Among the new
applications, users will find:
 DeltaV Live: Runtime environment for the operator interface
 Graphics Studio: Configuration environment for the operator interface
 Workstation Management: Centralized location for workstations configuration assignments once configuration has
been competed in Graphics Studio

Reduced complexity, increased efficiency for graphics project development. State-of-the-arts graphics that allow operators
to make better and quicker decisions. Enhanced graphics lifecycle maintenance supporting class-based graphical objects.
None.
2.7.5 DeltaV Live operations using Remote Clients

DeltaV Remote Client is a thin-client application that provides full remote capability to all DeltaV applications that are
configured for remote access. The remote workstations are physically connected to a Remote Desktop Server through the
L2.5 network.
A Remote Desktop Server can serve both DeltaV Operate and DeltaV Live sessions with the limitations outlined below:
 DeltaV v14.3 and earlier Remote Desktop Servers running DeltaV Operate:
o Maximum of 15 concurrent operator and/or engineering sessions per server licensed as an Operator or Base
Station
o Maximum of 7 concurrent sessions per server if licensed as a ProfessionalPLUS
o Individual remote session monitor configurations, including alarm and event area assignments, number of
monitors, etc.
o Limit of 12,000 datalinks across all screens from all remote sessions
Page 23 of 140
 DeltaV v14.3 Remote Desktop Servers running DeltaV Live:
o Maximum of 15 concurrent engineering sessions per server licensed as an Operator or Base Station
 2 of the 15 can be DeltaV Live operator sessions.
o Maximum of 7 concurrent sessions per server if licensed as a ProfessionalPLUS
 2 concurrent DeltaV Live operator sessions and 5 concurrent engineering sessions
o Individual remote session monitor configurations are not yet supported; each remote session will inherit the
host monitor layout configuration.
o Limit of 12,000 datalinks across all screens from all remote sessions
 If more than 2 concurrent remote DeltaV Live operator sessions per Remote Desktop Server are required, these
are the options:
o Wait for DeltaV v14.3.1, which will address this initial limitation. This is currently the only solution for
virtualized Remote Desktop Servers.
o Upgrade the Remote Desktop Server to the High-Performanc e server (Model SE2712C03) to allow 5
concurrent DeltaV Live remote operator sessions. This solution only applies to physical Remote Desktop
Servers.
2.8 Memory Requirements for Dell Workstations, Servers, and Virtual Host Servers
The memory requirements for all workstations increases from 4 GB to 8 GB in v14.3. Older workstations in the field that
have less than 8 GB of memory and that are upgradable to Windows 10 will need to be upgraded with additional memory
before upgrading the DeltaV system to v14.3. Additional memory can be ordered directly from Dell.
2.9 Operating System and Dell Workstations and Servers

Version 14.3 is built on Windows 10 and Windows Server 2016. Dell workstations and servers sold by Emerson are
installed with these operating systems. The next generation of Dell workstations and servers to be released will have
Windows 10 and Windows Server 2016 installed.
Virtualized DeltaV systems migrating to DeltaV v14.3 will require more host server memory because the memory
requirement for DeltaV v14.3 virtual machines has increased from 4 GB to 8 GB for workstations, and 8 GB to 16 GB for
servers. Customers who currently have host servers with 128 GB (and 13G Intel processors) will need to increase their
memory to a minimum of 192 GB for a fully loaded system. Additional memory can be ordered directly from Dell. New
host servers (with 14G Intel processors) are now available with 192 GB to support DeltaV v14.3 and earlier versions.
2.10 Virtual Studio

DVS 3.3 is not compatible with v14.3. DVS 3.3.1 will be compatible with v14.3.
2.11 Process History View Enhancements

The following enhancements were added to Process History View in DeltaV v14.3:
 Participation in themes: Now PHV will also change its color scheme according to the selected Theme, including
background and pen colors.
 Statistics per pen. Statistics are calculated based on the data set loaded in the visible time range of charts. Each
pen can individually show its statistics:
o Min and Max: Indicated by pointers on the trend
o Time Weighted Average: Indicated as a dotted line of the same color as the pen driving the average
o Accumulated total: Shown in the legend for each pen with statistics enabled
 Data Sources in PHV supported includes DeltaV Continuous Historian, Advanced Continuous Historian , and
Enterprise PI.
Page 24 of 140
Improved theme compatibility with more DeltaV tools, creating a consistent environment for Control rooms under different
lighting conditions.
None.

For systems leveraging standard PHV charts, the updated v14.3 PHV application has been modified to support standard
themes and will appear differently when different themes are applied to the system.
2.12 Graphic Deletion Improvements

DeltaV v14.3 introduces a brand-new utility to manage the deletion of DeltaV Operate displays and Process History View
charts including a Recycle Bin utility to restore erroneous deletions.
 New Utility to easily select graphics and PHV trends for deletion, accessible from DeltaV Operate and from PHV
 Deletions will propagate to nodes without workstation downloads .
 Deleted files are managed in a centralized location which allows restoring files to its original location or discarding
them all together.
 Restoring files to nodes is done without requiring downloads.

DeltaV Operate (Configure) and DeltaV Process History View

New buttons added to the tool bars of each application mentioned above, in order to have access to the delete graphics
utility, as well as new options in the context menu for DeltaV Operate (Configure), in order to have access to this utility.
Users no longer have to depend on Yellow Pages to update graphics or charts deleted from the system, as the utility
manages the deletion process.
None.
Page 25 of 140
2.13 OPC UA

OPC UA is an interoperability standard that allows for a secure and reliable exchange of real -time and historical data
between the DeltaV system and other systems, applications and enterprise users. DeltaV has added the following OPC
UA functionality:
 OPC UA server in the workstation
o Provides connectivity between OPC UA clients and the DeltaV system to read and write data. Support Real-
time Data (DA), Historical Data (HAD), and Alarms and Event Data (A&E)
o Supported in the Application station and ProfessionalPLUS
o OPC UA coexists with OPC Classic and OPC.Net in the same workstations .
o No Redundancy is supported.
 OPC UA clients in the Ethernet I/O card (EIOC) and workstation
o Provides connectivity with third-party OPC UA servers to bring only Real-Time data (DA)
o It is supported in the EIOC as another protocol, it can be mounted in the field and provides redundancy for
more critical applications.
o The OPC UA client is also supported in the Application Station and Professional PLUS workstations, but no
redundancy is supported.
 OPC UA server in the PK controller
o It is the first embedded OPC UA server in a DCS controller, providing only Real-Time data (DA) from control
modules running in the PK controller.
o Main purpose is to provide connectivity with the PK controller for HMI and system connectivity .
 All the OPC UA server and client are compliant with OPC UA standard 1.02.

 DeltaV Explorer
 Ethernet I/O card (EIOC)
 PK controller
 Application station
 ProfessionalPlus
2.14 Scalable EIOC

The scalable EIOC introduces a new licensing scheme to provide a more flexible and affordable solution for customers
with smaller Ethernet Device Networks:
 In v14.3, customers can now buy the EIOC Simplex or Redundant hardware, at a heavily discounted price.
Protocol license needs to be purchased as well as the “Device Licenses” for every physical device that will be
connected to the EIOC. This is a difference from v13.3.1, where customers are required to buy EIOC Simplex or
Redundant hardware and a Protocol license. The EIOC had no restrictions and customers could configure up to
256 devices.
 Same benefits of the EIOC but now the capacity can be scaled from 1 to 256 devices. Allowing customers with
just a few devices to take advantage of the EIOC by just paying for the capacity they use, and just adding more
device license to increase the capacity.
Page 26 of 140

If customers have an EIOC in v13.3.1, they must apply the new Device Licenses when moving into v14.3 in order to
continue its operation.
None.

 EIOCs connected to the system
2.15 EIOC PRP Redundancy

The Parallel Redundant Protocol (PRP) has been implemented in the EIOC to improve availability on the Device Ethernet
Networks:
 Enables communications in both ports at the same time
 Provides a zero-network switchover time
 Eliminates any single point of failure in the Device network
 Native PRP implementation on all supported protocols in the EIOC
 It is optional and needs to be enabled at the port level.
 For PRP to work, the Ethernet Devices need to support PRP as well.
 Support for Non-PRP Devices is through a redundancy box (RedBox) attached.


If customers have an EIOC in v13.3.1 and like to use this functionality, they would have to enable it and change their
networking architecture to comply with PRP.
None.

 EIOCs connected to the system
Page 27 of 140
2.16 DeltaV Alarm Management Improvement

The following enhancements were added to the DeltaV Alarm Management environment in v14:
 Multi-selection of areas/units/modules within the DeltaV System Alarm Management (SAM) application
 SAM context menu-launch for multi-selections in Explorer
 SAM context menu-launch for Network Nodes in Explorer
 Editing enabled conditioning properties (e.g. on-delay) in SAM
 Module name and description in the SAM to XML file

 DeltaV Explorer
 DeltaV System Alarm Management application
2.17 DeltaV Batch List View

The following enhancements were added to the Batch List View environment in v14:
 Batch list sorting by either state or batch ID
 Batch list color-coding according to the state of the batch
 Batch list filtering including wildcard capability, by Batch ID, Area, Process Cell, or Unit
 Alternating light/dark row background color variation in the batch list to make reading wide rows easier
2.17.2 DeltaV Functional Area Modified to Support this Feature

 DeltaV Operate
 DeltaV Live
2.18 New SIS Function Blocks

Two new SIS function blocks were added to DeltaV to support the development of Cause and Effect Matrices larger than
16x16:
 Monitor block
The LSMON function block generates as many as eight Boolean outputs based on the states of as many as 32
Boolean inputs. Typically, the LSMON block provides inputs to an LSEFFECT block or to another LSMON block .
 Effect block
The LSEFFECT function block is used in combination of monitor blocks, voter blocks , or inputs blocks to define
interlock and permissive logic.
Both the LSMON and LSEFFECT function block are only supported in SIS Modules revision 2.
Page 28 of 140
 CSLS firmware
 DeltaV Database Server
 DeltaV Explorer
 DeltaV Control Studio
 DeltaV Operate

There is no impact to users upgrading to v14.3. The monitor and effect blocks are new function blocks not available in
previous releases. The existing LSCEM function block was not modified.
None.
2.19 Major Revisions for SIS Modules

A major revision property has been added to SIS Modules. In DeltaV v14.3, the possible options are:
 SLS1508
 CSLS Major Revision 1
The module version declares the intended logic solver revision and determines the functionality available for the SIS
module. The following new functionalities introduced in DeltaV v14 is only available with SIS modules major revision 2:
 Effect and monitor blocks (new function blocks)
 Positive logic on voter blocks (new function block revision)
 Enhanced status handling on secure parameter references, non-secure parameter references, and voter blocks
(new functionality)
 Write access control for internal read parameters (new functionality):
o Writeable
o Not Operator Writeable When Locked
o Not Writeable
 Configurable PST timeout and new PST_RESULT parameter on LSDVC bloc ks (new function block revision for
LSDVC)
The following function blocks have a major revision 2 which is only available within a SIS module revision 2:
 LS Analog Voter
 LS Discrete Voter
 LS Discrete Valve Controller
The revision 1 of the above function blocks is not available within an SIS module revision 2. Function blocks revision 2
cannot be used with an SIS module revision 1. The revision 1 function blocks are not modified and they correspond to the
function blocks in previous DeltaV versions.
Page 29 of 140
SIS modules can be assigned to logic solvers as follows:
SIS Module Major Revision Logic Solver Assignment
SLS1508 SLS1508, CSLS revision 1, or CSLS revision 2

CSLS revision 1 CSLS revision 1 or CSLS revision 2
CSLS revision 2 CSLS revision 2

 DeltaV Explorer

There is no impact to users upgrading to v14.3 as long as the major revision of SIS modules is not manually updated. All
SIS modules assigned to an SLS1508 will be set to an SLS1508 major revision which preserve existing behavior. All SIS
modules assigned to a CSLS will be set to a CSLS Major Revision1 which preserve existing behavior.
To access the new functionality, you must upgrade the logic solver firmware to major revision 2, and then manually
change the major revision for each SIS module that requires the new functionality. Voter blocks revision 2 have different
status handling. Please consult Books on-line before upgrading the SIS modules to version 2.
Note: Changing the SIS module revision to major revision 2 will automatically upgrade all voter blocks and
DVC blocks to function block revision 2. It is not possible to downgrade the SIS module back to revision 1,
unless all function block at revision 2 are manually converted to revision 1.
None.

None for users staying the current SIS module major revision. User upgrading SIS modules to major revision 2 will need
to compare the CRC before and after and evaluate the need for a functional test.
2.20 Major Revision for CSLS

A major revision property has been added to CSLS to indicate the associated firmware revision. This is not a hardware
revision; all existing CSLS hardware can handle both revision 1 or revision 2.
In DeltaV v14.3, the possible options for major revision are:
The major revision determines the functionality that logic solver supports. The following new functionality introduced in
DeltaV v14 is only available with CSLS Major Revision 2:
 Logic solver lock improvement
o Enhanced access control for function block parameters
o Timed unlock command
o Single unlock functionality
Page 30 of 140
 CSLS firmware
 DeltaV Explorer

There is no impact to users upgrading to v14.3. All CSLSs will be set to as CSLS Major Revision 1. To access the new
enhanced access control functionality, you must upgrade the logic solver firmware to major revision 2, and then manually
enable the functionality at the CSLS property window and download the logic solver.
Important: Enabling the enhanced access control might impact existing configuration using CALC function
block to programmatically change parameters. It can also impact writes from the user interface. It is
recommended to understand the impact before enabling enhanced access control.
None.

None for users staying at the current logic solver major revision. User upgrading to major revision 2 will need to compare
the CRC before and after the firmware upgrade, and then evaluate the need for a functional test.
2.21 SIS Alarm Groups

SIS alarm groups allow to group SIS alarms within a single module. It is possible to create several alarms groups for a
SIS module and assign function blocks and user-defined parameters within the module to a given alarm group. For
example, an alarm group can contain all the function associated with a voter function (such as a voter function block and
the associated analog input blocks) or with a valve (for example, a discrete output block for the solenoid and a DVC block
for the positioner). For each alarm group, the user can specify a set of displays (primary control, detail, and faceplate), as
well as a description.

 Controller firmware
 DeltaV Explorer
 DeltaV Operate
2.22 SIS I/O Simulation

I/O simulation is now available for virtual CSLS without the need to use the SIMULATE_IN parameter within input function
blocks. The user can manipulate simulated values via the new Device Signal Simulator application or via OPC.

 Virtual CSLS
 New Device Signal Simulator software application
Page 31 of 140
2.23 Smart Commissioning for HART Devices
Note: DeltaV Smart Commissioning is included in DeltaV v14.3.0.6984 Feature Pack 1. Feature Pack 1 can
only be installed on systems already installed with DeltaV v14.3.0.6843. Refer to section 13 Media Pack
Information for details on the different released DeltaV v14.3 installation media and their applicability.

Smart Commissioning is a technology-enabled approach for streamlining the commissioning of HART instrumentation
connected to DeltaV Electronic Marshalling and Wireless I/O cards. It reduces the effort and time for commissioning
HART devices by automating most the associated tasks. Smart Commissioning focuses on keeping the commissioning
activities off the critical path of projects as well as reducing the trips.
Smart Commissioning is a combination of system software capabilities, tools , and procedures to automatically:
 Sense devices for a complete I/O node (CIOC, CSLS, or WIOC)
 Identify devices via the field device tag
 Configure devices via AMS Device Manager Bulk Transfer. Note: The use of AMS Device Manager bulk transfer
requires proper AMS Device Manager licenses.
 Loop test
 Documentation (loop test results and as-build device connection information)

 New I/O Studio application
 New DeltaV Device Commissioner application
 DeltaV Explorer
Page 32 of 140
3 Improved Functionality in DeltaV v14.3
3.1 Partial Stroke Test Improvements

The Partial Stroke Test (PST) Functionality was improved as follows:
 Configurable PST timeout value
The PST timeout is now configurable. The default value is the same as prior vers ions to preserve existing
behavior.
o For SLS1508, the PST timeout is defined at the logic solver property window and is applicable to all Fisher
DVC devices connected to that logic solver.
o For CSLS, the timeout is defined at the DVC function block (only available within an SIS module revision 2).
 Visual indicator on the DeltaV DVC faceplate to display PST status provided in new firmware version of Fisher
DVC6200 (only available within a SIS module revision 2)

 Logic Solver firmware
 DeltaV Explorer

None. The timeout value is the same as in the previous version. To access the new PST functionality, you must upgrade
the logic solver firmware to major revision 2, and then manually upgrade the SIS module to version 2.
None.

None.
3.2 Status Propagation Enhancements in SIS Modules

The following improvements were introduced to better handle bad status due to both communication failures and status
propagation from downstream logic.
 Enhanced Status Handling on both secure parameter references and non-secure parameter references (only
available on SIS modules major revision 2)
 A trip-inhibited status will not immediately generate bad status on the output of voter block revision 2. On the
previous revision of the voter blocks, a bad status was reported immediately after the block enters the trip-
inhibited state. The voter block revision 2 has a timeout parameter TRIP_INH_DELAY that delays the bad status
propagation by a predefined time (default value of 8 hours). Setting this delay parameter to zero will replicate the
behavior of the voter block revision 1. Existing users should consider the impact on the safety logic due to the
new status propagation behavior before upgrading SIS modules to revision 2.
 With the original voter block revision 1, the output for a MooM voter reported bad status when an input had bad
status and the status options were set as vote to trip if bad. The same configuration with a voter block revision 2
will not generate bad status. Existing users should consider the impact on the s afety logic due to the new status
propagation behavior before upgrading SIS modules to revision 2.
Page 33 of 140
 DeltaV Explorer

There is no impact to users upgrading to v14.3 as long as the major revision of the SIS modules is not manually updated.
All SIS modules assigned to an SLS1508 will be set to an SLS1508 major revision which preserve existing behavior. All
SIS modules assigned to a CSLS will be set to a CSLS Major Revision1 which preserve existing behavior.
To access the new functionality, you must upgrade the logic solver firmware to major revision 2, and then manually
change the major revision for each SIS module that requires the new functionality. Voter blocks revision 2 have different
status handling. Please consult Books on-line before upgrading the SIS modules to version 2.
Note: Changing the SIS module revision to major revision 2 will automatically upgrade all voter blocks and
DVC blocks to function block revision 2. It is not possible to downgrade the SIS module back to revision 1,
unless all function block at revision 2 are manually converted to revision 1.
None.

None for users staying at the current major revision. User upgrading SIS modules to major revision 2 will need to compare
the CRC before and after and evaluate the need for a functional test.
3.3 SIS Security Enhancements

Multiple security improvements are included in v14:
 Central location for managing the locking and unlocking of CSLS (key switch on SZ controller carrier). This
functionality requires new Ethernet Isolation Ports (EIP) for the SZ controller.
 Hardening the lock behavior to prevent on-line changes that could impact the safety logic via the enhanced
access control functionality (available only on CSLS major revision 2).

 DeltaV Explorer
 New Ethernet Isolation Ports for SZ controller

There is no impact to users upgrading to v14.3. All CSLSs will be set to as CSLS Major Revision 1. To access the new
enhanced access control functionality, you must upgrade the logic solver firmware to major revision 2, and then manually
enable the functionality at the CSLS property window and download the logic solver.
Page 34 of 140
Important: Enabling the enhanced access control might impact existing configuration using CALC function
block to programmatically change parameters. It can also impact writes from the user interface. It is
recommended to understand the impact before enabling enhanced access control.
None.

None for users staying the current SIS module major revision. User upgrading SIS modules to major revision 2 will need
to compare the CRC before and after and evaluate the need for a functional test.
3.4 New Function Blocks

Users will see two new function blocks on the Analog Control Palette in Control Studio, the ERAMP (Enhanced Ramp)
and ECTSL (Enhanced Control Selector).
 Enhanced Ramp (ERAMP)
The ERAMP function block makes it simple for process ramps to be performed by both operators and automated
logic, utilizing the same configuration. The ERAMP supports ramping target function blocks, such as the PID, in
MAN, AUTO, RCAS, ROUT, and Local Override (LO) modes. It supports ramping values up, down, or both, at a
specified rate or over a specified time, to variable or static endpoints.
A module faceplate and detail is available and dynamo updates were made to existing PID dynamos to support
adding an ERAMP block to existing PID modules. A module template is available for using the ERAMP with the
PID function block. It can be found in the DeltaV Explorer Library  Module Templates  Analog Control
category, and is called PID_ERAMP.
 Enhanced Control Selector (ECTSL)
The ECTSL function block is an enhanced version of the existing control selector (CTSL) function block,
increasing the available inputs from 3 to 16. Control selection can be done via operator/logic manual selection, or
automatically based on high, middle, and low select logic. The currently selected input is shown as an output of
the block, for display on faceplates and operator displays.
A function block faceplate is available in DeltaV Operate and DeltaV Live, named ECTSL_fp.

 Control Studio
 DeltaV Explorer
 DeltaV Operate
 DeltaV Live

None.
None.
Page 35 of 140
None.
3.5 Blue Triangle Contributors

Blue Triangle contributors enhance DeltaV Explorer with a new option to “Show Details” on a given node, which will
display the contributors to a pending download. The various subsystems contributing to a download will be identified, as
well as whether the subsystem properties have been modified, added, or deleted. This option is found on the right-click
context menu on supported nodes, under “Download Status ”  “Show Details”.

 DeltaV Explorer

None.
None.

None.
3.6 Product System Warnings

A new option has been added to the DeltaV System Preferences to enable “Production System Warnings”. When
selected, users will see additional warnings when performing operations that could have an adverse effect on a running
production system. Some of the actions that will lead to this additional warning include:
 Rebooting and shutting down workstations
 Stopping the Batch Executive
 Decommissioning nodes
 Deleting nodes
 Disabling I/O Channels
 Moving module assignments
 Moving alarms and event assignments

 DeltaV Explorer

None. These warnings are disabled by default and must be enabled in System Preferences to take effect.
None
Page 36 of 140
None.
3.7 Configurable Area Index

Users will now be able to configure a unique index value for all areas in their control strategy configuration. These indices
can be used to provide logical grouping and ordering for areas in the DeltaV Operate and DeltaV Live Alarm Filter display.

 DeltaV Explorer
 DeltaV Operate
 DeltaV Live

None. Users can add area indices from the area properties dialog if they choose after upgrading. Otherwise, the DeltaV
Alarm filter display will behave the same as in previous versions, with areas shown in the order they were added to the
control strategies configuration.
None.

None.
3.8 Upload Enhancements

Various upload enhancements have been made in DeltaV v14.3. Users can now configure the upload behavior for
parameters in their configuration, to omit parameters that they do not want to be shown on the upload dialog. Similar to
configuring the security lock for individual parameters, you can also configure whether individual parameters are allowed
for upload.
Enhancements have also been made to the upload dialog. You can now sort columns and filter based on the parameter
security lock. The ability to fetch the current online value for parameters is also available, as well as the ability to save the
upload data to XML.
Lastly, for systems with Configuration Audit Trail enabled, a new label will be added to history when upload actions occur.

 DeltaV Explorer
 Configuration Audit Trail

None. By default, all parameters will be set to allow upload. Users can configure parameters to be excluded from upload
by clearing the “Allow Upload” value for the desired parameters in the Parameter Security dialog box, found in DeltaV
Explorer in Setup  Security.
None.
Page 37 of 140
None.
3.9 Controller Switchover Enhancements

Various updates were made to enhance controller switchover robustness including:
 Configuration Analysis
A new configuration analysis utility is available from the right-click context menu of objects in DeltaV Explorer and
from the Control Studio menu options. This will analyze the selected module(s) for configuration practices that
could cause a disruption on a controller switchover, including:
o Instances where function block execution order does not match the function block wiring order, which could
affect first-time module execution following a switchover. The analysis results will omit configuration where
this mismatch is expected such as the wiring of BKCAL_OUT parameters to BKCAL_IN or wiring bloc k
outputs to feedback parameters such as CMD_IN_D or FDBK_IN.
o SFC action confirm expressions hardcoded to “TRUE”. Hardcoding SFC confirms to “TRUE” will bypass the
retry mechanism if a write fails for any reason, for example if a write is done to a control ler at the moment it is
undergoing a switchover. The analysis results will omit any actions that do not contain external references.
Users should analyze any configuration found by the utility to determine if it is configured as intended. For more
details, please refer to the help topic that can be accessed from the Configuration Analysis dialog box.
 Function Block Order Analysis
Incorrect function block execution order can impact the first-time module execution following a controller
switchover. New methods have been added to identify modules where function block order does not match
execution order. In addition to the above-mentioned configuration analysis tool, you can also search for function
block execution and wire order mismatches on module import, by selecting a check box on the import dialog.
A new option to “Force Module Execution Order” is also available in Control Studio to force function block
execution order to match wiring order. This will overwrite any user edits of function block execution order.
 Non-Secure Parameter Statuses
Non-secure parameter references in logic solvers will now hold their last status when the referenced parameter’s
controller undergoes a switchover. The status value will hold until the reference is reestablished. If the reference
cannot be reestablished, the non-secure parameter status will go to BAD.

 DeltaV Explorer
 DeltaV Controllers

None.
None.

None.
Page 38 of 140
3.10 EtherNet/IP Control Tag Integration

A new protocol has been added to the EIOC named EtherNet/IP Control Tag Integration. This protocol allows for
communication with tag-based PLCs (ControlLogix and CompactLogix) using tag names, as opposed to register locations.
A new folder is available in the DeltaV Library named PLC Tag Definitions, where users can define signal properties for
tags. 4 definitions are included out-of-the-box, TAGAI_MONITOR, TAGAO_MONITOR, TAGDI_MONITOR, and
TAGDO_MONITOR.
5 new function blocks are available in the I/O Function Block palette in Control Studio, for use in modules assigned to an
EIOC utilizing the EtherNet/IP Control Tag Integration protocol.
 TAGAI (Tag Analog Input) – Used to read the signals from a tag configured using the TagAI_Monitor PLC tag
definition
 TAGAO (Tag Analog Output) – Used to read the signals from a tag configured using the TagAO_Monitor PLC tag
definition
 TAGDI (Tag Discrete Input) – Used to read the signals from a tag configured using the TagDI_Monitor PLC tag
definition
 TAGDO (Tag Discrete Output) – Used to read the signals from a tag configured using the TagDO_Monitor PLC
tag definition
 TAGIO (Tag I/O) – Will convert to the appropriate TAG function block (TAGAI, TAGAO, TAGDI, TAGDO) when a
control tag is assigned, based on the tag definition type
Module templates have been added in the DeltaV Explorer Library  Module Templates  Tag Integration folder, called
TAGAI_MONITOR, TAGAO_MONITOR, TAGDI_MONITOR, and TAGDO_MONITOR. These templates include module
faceplates and details and have dynamos/GEMs available in DeltaV Operate and DeltaV Live.

 DeltaV Explorer
 Ethernet I/O Card (EIOC)
 DeltaV Operate
 DeltaV Live

None. EtherNet/IP Control Tag Integration must be enabled in the “Network” section of System Preferences to be used
and make the new configuration elements available in DeltaV Explorer and Control Studio.
None.

None.
Page 39 of 140
3.11 DeltaV v14.3 Simulate Enhancements

The following enhancements were made to DeltaV Simulate:
 Support for Batch simulation including save/restore of the Batch Executive
 Improved simulation of batch control including support for save and restore at any time in a batch operation,
including in the middle of Phase operations
 Robustness improvements for easier maintenance of simulation systems when configuration changes are made
 Simulate Conversion utility enhancement to preserve class-based modules after conversion
 Faster OPC data transfer that will in turn allow the user to speed up external process simulators (e.g. MiMiC) to
get to a determined process state faster.

Applications modified to support this feature include:
 DeltaV v14.3 SimulatePro – New save/restore options are now available.
 DeltaV Simulate Conversion – Retains class-based modules and includes I/O references
 Sim_Request calls via OPC – New options are available to support save/restore enhancements.
3.11.3 Impact for Users upgrading to v14.3

DeltaV Simulate creates new initial condition save files in both the traditional binary data format (for fastest restore) and a
new XML format (for flexibility and robustness after configuration changes). Users migrating to v14.3 may use existing
v13.3.1 save files to restore initial conditions in v14.3.
None.

Users upgrading to v14.3 should restore legacy v13.3.1 save files to confirm proper initialization. After restoring, it is
recommended to create a v14.3 save file for all subsequent restore operations.
3.12 New CHARMs I/O Card 2 (CIOC2)

The CIOC2 is a new hardware platform created to meet new Cybersecurity requirements:
 Will be Achilles Level 2 certified
 Is only compatible with v14.3 and later

 DeltaV Explorer
 Diagnostics

None.
None.
Page 40 of 140
None.
3.13 M-Series Controllers can have I/O Assigned from CIOCs and WIOCs

Version 14.3 will allow I/O from a CHARMs I/O Card (CIOC) to be assigned to an MQ or MX controller. DeltaV Smart
Switches are required for systems with Electronic Marshalling, and this same requirement applies to DeltaV systems that
now allow CIOCs to be assigned to M-series Controllers. The same network equipment that can be used today to build
DeltaV networks can also be used if CIOCs are assigned to Controllers, and the network equipment includes:
 DeltaV Smart Switches
 DeltaV Firewall-IPD
 Specific Cisco switches sold by Emerson (available with an Emerson part number with licensed/approved
firmware)
M-Series controllers behave the same as S-series controllers with respect to CHARM I/O and Wireless I/O assignments.

 DeltaV Explorer
 Diagnostics

Please see the whitepaper Network Considerations for M-series with Electronic Marshalling for more detailed information.
None.

None.
3.14 Distributed CHARMs

Note: Distributed CHARMs are included in DeltaV v14.3.0.6984 Feature Pack 1. Feature Pack 1 can only be
installed on systems already installed with DeltaV v14.3.0.6843. Refer to section 13 Media Pack
Information for the details about the different released DeltaV v14.3 installation media and their applicability.

Electronic Marshalling with Distributed CHARMs enables you to install CHARMs even closer to field devices and can
eliminate costly engineering and installation efforts.
The Distributed CHARMs hardware includes:
 The CHARM I/O Gateway connected to the CIOC or CSLS carrier or t o a CHARM baseplate under the CIOC or
CSLS carrier
 The CHARM I/O Block that includes 12 CHARM slots and can be installed close to the field devices
Both the CHARM I/O Gateway and the CHARM I/O Block have Scanner Modules and Ethernet I/O Ports (IOP) that
facilitate communication between the CIOC or CSLS and each CHARM over full duplex 100BASE -TX Ethernet. These
products support star and a fault-tolerant ring topology using copper Ethernet.
Page 41 of 140
 DeltaV Explorer
 Diagnostics

None.
None.

None.
3.15 LS DI 120V AC Isolated Plus CHARM

An isolated, 120 V Digital Input Characterization Module (CHARM).

DeltaV Explorer

None.
None.

None.
Page 42 of 140
4 Resolved Issues
4.1 Resolved Issues for Controller and I/O
Incident TFS317498
EIOC and Toshiba VFD (Variable Frequency Drive) MV2, unable to

Description
communicate when using Ethernet/IP protocol.
Current Status This issue has been resolved in DeltaV v14.3.
Incident TFS332389
Cannot flash upgrade Series 2 Serial Card with firmware 1.55 with other
Description
firmware.
Incident TFS367546
16CH AI Plus IO Card reports good status when all channels are -25%
Description
(Open loop).
Incident TFS369857
Description AT block FIRST_OUT is intermittently resetting to “0”.
Incident TFS374150
BOL Documentation EIOC: Does not communicate with absolute Modbus

Description (absolute 0 or generic 1 based) addressing. Only Devices using Modicon
PLC addressing.
Incident TFS378873
EIOC: Modbus TCP Devices do not recover communication to the EIOC

Description
after power cycling the slave units.
Page 43 of 140
Incident TFS302692
EIOC 61850: Origin Category of "Not Supported" in write requests is

Description
rejected by some MMS devices.
4.2 Resolved Issues for Workstation
Incident TFS273388
Description Database gives server busy when creating new user in UserManager.
Incident TFS297215
Description Users need a way to count the number of unique datalinks on a display.
Incident TFS299204
DVOP: Workspace Application – Method WindowName of object

Description
IFixDocFrame failed.
Incident TFS300405
Administrator-type user cannot download ProfessionalPLUS after

Description
workstation configuration.
Incident TFS301007
Description DvdbServer crash Encountered During System Capacity Testing.
Page 44 of 140
Incident TFS301364
VCAT: Got error validating VCAT database schema. Invalid object name
Description
'VCSchema' after renaming the default DeltaV_System database.
Incident TFS303099
USERT.scr (download script) gets corrupted when rerunning DeltaV

Description Workstation Configuration on LGTEST ProfessionalPLUS and only 2
users out of many display on DeltaV Logon drop-down menu.
Incident TFS305538
FileRemoteCopy.exe when executed on a Mobile Worker to communicate

Description with RAS server generates “The ordinal 85 could not be located in the
dynamic link library D:\FileRemoteCopy.exe” error message.
Incident TFS306577
Description OPC Collect in Entech Toolkit fails to connect to non-DeltaV OPC servers.
Incident TFS316421
Fix to TFS incident 156775 introduces an issue with enable/disable of

Description
simulation in input function block in virtual CSLS.
Incident TFS324656
Workspace.exe crashes intermittently with PEGRP32D.dll as the faulting

Description
module when opening displays with embedded trends.
Page 45 of 140
Incident TFS325319
DeltaV Insight application would not launch on non-domain controller

Description
workstations after upgrading from v13.3 to v13.3.1.
Incident TFS326327
Opening DeltaV User Manager in DeltaV v.13.3.1 frequently shows

Description
'Server Busy' with 'Switch to', 'Retry', and 'Cancel' (greyed out).
Incident TFS332335
Description Books Online Update – Typo errors in Serial Dataset Syntax Table.
Incident TFS332546
WorkSpace randomly crashes (VBE6.dll, unknown, FixFileLinkDLL.dll)

when PROVOX Alarm Direct Access opens the Control Display and the
Description
PROVOX Faceplate when the Main Picture's Close event closes
PROVOX Faceplates.
Incident TFS332710
WorkSpace randomly crashes (VBE6.dll, unknown, FixFileLinkDLL.dll)

when DeltaV/PCSD Alarm Direct Access opens the Control Display and
Description
the DeltaV/PCSD Faceplate when the Main Picture's Close event closes
DeltaV/PCSD Faceplates.
Incident TFS339396
Master Time Server is replaced by the PROPLUS name when running

Description
Workstation Configuration.
Page 46 of 140
Incident TFS340091
After a system upgrade, the administrator account gets all SIS keys
Description
including SIS No Access key.
Incident TFS341666
Screen flickers (momentary black screen) when DeltaV Screensaver

Description
starts in Windows 10 and Windows Server 2016.
Incident TFS344765
Multiple unassigned CIOCs cause a workstation process crash and

Description
workstation reverts to a NO-COMM state.
Incident TFS345609
Verify.log file does not contain all necessary information following a BEX
Description
download.
Incident TFS348053
“User Can't Change Password” option in DeltaV User Manager remains

Description
unchecked after enabling.
Incident TFS353699
Recycle bin icon on desktop and several Start menu items seen on 13.3.1
Description
Windows 10 when Basic Operator is logged on to Windows.
Page 47 of 140
Incident TFS358908
Opening different Faceplates in Succession is Causing Workspace to

Description
Crash.
Incident TFS360515
Bulk Edit – DeltaV Explorer crashes when performing a user-defined

Description
export using ODBC.
Incident TFS362543
[v13.3.1 Russian Control Studio] Error during module download when

Description decimal values are set to certain function block parameters in Control
Studio.
Incident TFS368906
Description User Manager export is taking a long time to complete.
Incident TFS369056
Description Cannot change password for any user via Flexlock.
Incident TFS373643
Database clients get stuck with "Server Busy" dialog displayed, making
Description
clients unusable.
Page 48 of 140
Incident TFS373850
Multiple licensing issues being encountered on the ProfessionalPLUS

Description
after installing WS_07 on a v13.3.1 DeltaV Discovery setup.
Incident TFS320779
In Process History View, the calendar in the date/time select window is

Description
cut off on both sides, making some dates unreadable.
Incident TFS330814
Enabling VCAT on ProfessionalPLUS may generate the error “The FRSI

Description
Component does not function properly”.
Incident TFS334134
Inconsistencies in DeltaV Security Administration report for Services

Description
versus what is shown in Windows Services
Incident TFS344140
DUW Laundry list has “Advanced Continuous Historian detected” item on

Description the checklist when upgrading an application station that does not have
Continuous Historian enabled.
Incident TFS364647
Description High Performance dynamos should work with the Dynamo Update Utility.
Page 49 of 140
Incident TFS368669
The Master Time Server is not set after rerunning DeltaV Workstation
Description
Configuration.
Incident TFS413852
Description Security hardening
4.3 Resolved Issues for Batch
Incident TFS384235
The recipe details window does not match with the selected operation
Description
recipe when using the DeltaV Operate Batch Control PFC View.
Incident TFS385807
Failed to enable VCAT due to the error: Unable to open security object
Description
after upgrading from v11.3.1 to v13.3.1.
Incident TFS394410
Description BEX – DVBManager.log being filled with nuisance entries every second.
Incident TFS202011
Batch Analytics cannot write the model info to the batch if the Batch
Description Historian is very busy and has not yet processed the batch monitored by
Batch Analytics.
The diagnostic message in DeltaV v14.3 includes more information about

the batch including its unique ID and why it could not be written to the
Current Status
Batch Historian (which is either the Batch Historian is stopped or too
busy).
Page 50 of 140
Incident TFS308713
After installation of Batch Analytics which applies IIS security hardening

Description settings, and rebooting the machine, Batch Historian Admin Tool and
Event Chronicle failed to connect, and the Batch Historian service crashed.
Incident TFS233542
Description Batch Analytics passwords can be recovered.
Incident TFS135329
Batch analytics Operations information Web Server (BOWS) – Cannot

relaunch Batch Analytics Website if mini-BOWS is also launched (with
Description
both signed on) – Get blank IE with "No Data" in the dialog box – until you
clear the xbap cache
Page 51 of 140
5 Known Issues in DeltaV v14.3
5.1 General
Incident TFS395781
Dell Latitude 7480 hosting Virtual Box VM with the .OVA Engineering
Description station requires user to change from Bridged adapter, and then back again
if you unplug the network cable from the DeltaV LAN connection.
User Scenario Not applicable
Prevention None.
Go into the host settings and remove the bridge connection for the
Recovery Network adapter, and then save. Go back into the settings, and then add
the bridge connection for the Network adapter.
Incident TFS387101
BH: Batch Historian Admin Auto Archive Maintenance Feature Logs

Description
appears to randomly skip the hourly Auto Archive schedule.
Prevention None.
If user noticed that the auto archive job did not actually happen for a
certain schedule, they can manually archive the batches. Alternately, they
Recovery
could wait for the next auto archive job to happen and check if the batches
were successfully archived.
Incident TFS330774
OPCAE Subsystem node not visible under DeltaV Diagnostics after

Description
workstation restarted.
Prevention None.
If OPCAE Subsystem is not visible in DeltaV Diagnostics when DeltaV

OPC A&E Server is licensed and enabled, try un-assigning and
Recovery
reassigning OPC Alarms and Events License to the workstation and
rescanning workstation node in DeltaV Diagnostics.
Page 52 of 140
Incident TFS382951
OPC Mirror: Error in installing Crypkey License Service during OPC Mirror
Description
Installation when McAfee is also installed.
Prevention None.
Disable the McAfee Endpoint Security during installation, and then enable
Recovery
it after.
Incident TFS395785
OPC Mirror – Unable to synchronize the OPC Mirror databases between

Description the active and standby application stations. Standby has error "An OPC
Server on the standby Application Station has bad communications" .
Prevention None.
Recovery None.
Incident TFS381890
OPCMirror: OPC Mirror Service Install can be executed even with OPC
Description
Mirror Service is Running.
Prevention None.
Recovery Rerun the Mirror Service Install.
Page 53 of 140
Incident TFS395946
OPC Mirror: Text cut off in installer dialog when specified account is not a
Description
DeltaV account and custom path is used.
When the service account specified to be used by OPC Mirror is not a

DeltaV account, the installer raises a dialog box with options to enter a
new account name, exit service install, or continue service install.
User Scenario The text within that dialog box is cut off, making the instruction to rerun
OPC Mirror Service install unreadable. This occurred when the path
entered for OPC Mirror install was customized to use "Emerson" instead of
"FRS".
Use the following recommended OPC Mirror path:

Prevention
C:\Program Files (x86)\FRS
Recovery None.
Incident TFS380292
OSI: After installing PI SDK Utility to connect to multiple historical servers,

Description
Embedded Trend for ACH or Enterprise PI in DeltaV Operate crashes.
A user cannot add additional historical server for Embedded Trend in

DeltaV Operate to connect to multiple historical servers. This also means
that DeltaV Live cannot retrieve historical data from both ACH and
User Scenario Enterprise PI.
This is expected as PISDKUtility has no capability to connect to multiple
historian servers.
Prevention None.
Recovery None.
Incident TFS348687
USB Dongles and devices cannot switch ports after the USB storage
device policy, according to KBA NK-1600-0336: ICS-CERT
Description
ADVISORY ICSA-16-334-02 - Managing USB Storage Devices on DeltaV
Computers Using Group Policy, is enabled.
After disabling USB storage devices and after restarting the

ProfessionalPLUS, the operating system does not recognize a dongle,
User Scenario Keyboard, and mouse if plugged to a different port. This is as expected for
IDDC setup.
Prevention None.
Recovery None.
Page 54 of 140
Incident TFS395605
Description Winupgrade could not find the image file to upgrade LSNB or LSNG.
With DeltaV 14.3 RCA build on ProfessionalPLUS or Operator station,

running winupgrade and browsing to an assigned or decommissioned
User Scenario
LSNB or LSNG. A message box would show up saying that the image file
does not exist in the default folder.
Prevention None.
Workaround is to copy the LSNB upgrade file to C:\DeltaV\ctl\CSLS\Rev2:

 InstallR_LSNB.udf
 InstallR_LSNB.udf.dvmanifest
 LSNB-AppR.cksum
Recovery  LSNB-AppR.cksum.dvmanifest
 LSNB-IPL.cksum
 LSNB-IPL.cksum.dvmanifest
 LSNB-OSR.cksum
 LSNB-OSR.cksum.dvmanifest
Incident TFS395514
PCInstall – Getting "DeltaV Live Initialization Failed" warning dialog using

Description
DeltaV 14.3 RC-A build on PK.
Installing DeltaV 14.3 Release Candidate A (build 6828) on a PK

standalone system using the OVA for the release candidate build a DeltaV
User Scenario
Live Initialization Failed dialog appeared during PCInstall process after
setting the DeltaV Administrator password.
Prevention None.
Delete the corrupted OVA from the machine, and then reimport the OVA
Recovery
file.
Page 55 of 140
Incident TFS363286
Cannot install ACH 2016 on an application station which is also a domain

Description
controller.
When ACH is selected, installation tries to install it but fails with an error.
After the PowerShell application window is closed, the installation finishes
User Scenario
but the machine's installation is incomplete since it does not have any
Continuous Historian installed.
Prevention None.
Installation of Advanced Continuous Historian on a Windows Server 2016

domain controller is not supported. See KBA NK-1600-0074: Installing
DeltaV v13.3.1 Advanced Continuous Historian or Enterprise Historian on
Windows Server 2016.
Undo changes to the dlls that sets the CH type to ACH.
Copy
 c:\DeltaV\bin\RtPHistoryConfig.dll
 c:\DeltaV\bin\RtPHistoryConfig_PI.dll
Recovery Copy
 c:\DeltaV\bin\DvCHMgmt.dll
 c:\DeltaV\bin\RtPHistoryConfig.dll
REG ADD
HKLM\SOFTWARE\Wow6432Node\FRSI\ DeltaV\CurrentVersion\HawkSer
vice\RtPHistoryScan /v Enabled /t REG_DWORD /d 0 /f
REG ADD
HKLM\SOFTWARE\Wow6432Node\FRSI\ DeltaV\CurrentVersion\HawkSer
vice\RtPHistoryWork /v Enabled /t REG_DWORD /d 0 /f
Incident TFS395644
DUW: DV Web Server Remnants from lower DeltaV Version Prevents

Description
"Restore Configuration" to Succeed.
During the “Restore Configuration” stage of DUW, a prompt indicating that

the Restore procedure finished UNSUCCESSFULLY was observed. This
User Scenario
issue hinders the DUW to proceed to the next stage or to complete
(restarting the machine yielded to same issue).
Prevention None.
Recovery Rename or delete the SaveDVWconfig folder from the BackUp DVData.
Page 56 of 140
Incident TFS336643
The DeltaV v13.3, v13.3.1, and v14.3 DVD2 "_Support" folder contains the
Description
wrong "SystemTree.csv" file.
Using the "SystemTree.csv" file from the DVD2 "_Support" folder to unlock
the System Tree and when Unlocked the Projects frsDevAlm and
SIGlobals are not visible when WorkSpace is opened in Configure mode.
User Scenario
In Run mode, the SIGlobals variables initialized in PCSD's UserSettings
file sometimes do not get set correctly. Also, when they are set correctly ,
"Reset Layout" resets them to their default values.
Prevention None.
Unlock the System Tree, make the changes, and then lock the System
Recovery
Tree before testing your changes.
Incident TFS342011
Operator station installation failed. Error in setting ACL entries for

Description
MACHINE\SOFTWARE\FRSI\DeltaV\CurrentVersion.
Ran an installation of local operator station which failed with an Error in

setting ACL entries for
MACHINE\SOFTWARE\FRSI\DeltaV\CurrentVersion. After acknowledging
User Scenario
the error, a new error "An error occurred while setting up the windows NT
registry for HAWK services" appeared, and then the configuration cannot
be completed.
Prevention None.
Remove the workstation from the Domain, rejoin it back into the domain,
and then rerun PCInstall.
1. Fully exit the domain, join a Workgroup, delete the workstation record
Recovery from Active Directory (AD) Users & Computers, and then perform a
reboot.
2. Manually rejoin the domain, and then perform a reboot.
3. Restart PCInstall.
Incident TFS396883
DUW: Cannot start MSSQLSERVER services after upgrading

Description
ProfessionalPLUS from v11.3.1 to v14.3.
During restore process, VCAT reattachment failed. Cannot manually run

User Scenario
MSSQLSERVER.
Prevention None.
Temporarily remove the ProfessionalPLUS Primary Domain Controller

Recovery
(PDC) from the network, and then rerun PCInstall.
Page 57 of 140
Incident TFS396882
SOFTPHASEUSER password is not set properly during installation

Description
causing Softphase batches to get stuck in connecting state.
Batch executive started in Batch Application Manager (BAM) and in DeltaV

Operate runtime mode switched to Batch List View. Adding and starting
User Scenario
batch of the softphase recipe. Then switched to Batch PFC View, it will be
observed that the batch gets stuck in 'Connecting' state.
Prevention None.
Recovery Rerun servpwd utility in ProPlus node, and then restart the machine.
Incident TFS194000
Description 10.3.4 RC-C India: User Manager – Missing Alarm Key in User Manager
Cannot assign Alarm key to user because it is missing in the list of keys in
User Scenario User Manager. Furthermore, a key named System Maintenance was found
which is not present in other versions.
Prevention None.
Recovery Rename the System Maintenance lock to Alarms in User Manager.
Incident TFS247242
DeltaV Upgrade Wizard – Logbooks Laundry List is missing for

Description
workstations with Logbooks installed.
Running DeltaV Upgrade Wizard on machines with Logbooks installed

(Server or Client) will not show the Logbook item in the DUW laundry list.
The location where the Logbooks server is installed will need to have the
User Scenario
Logbooks database backed up manually. The other workstations where
the Logbooks Client is installed will require Logbooks Client to be
reinstalled.
Prevention None.
Recovery None.
Page 58 of 140
Incident TFS361896
DUW – Upgrade Wizard is unable to migrate any database that contains

Description
spaces in the file path.
After DUW completes the "DeltaV Uninstall" step, the user will be
prompted to import the default database or browse for a different
database. Clicking "Browse" and locating a .fhx database that contains
User Scenario spaces in the file path will cause the migration to fail. Notice that each
space in the file path causes DUW to think it is a separate file. After
clicking "OK" to the "All DeltaV Migration Complete" dialogue box, DUW
will freeze and must be force closed using task manager.
Prevention None.
Force close DUW using task manager. Rename the folders and .fhx file
name so that the file path does not contain any spaces. For example,
Recovery
rename the path from "D:\Installation Files\DeltaV_System – Copy.fhx" to
"D:\InstallationFiles\DeltaV_System_Copy.fhx", and then relaunch DUW.
Incident TFS297982
DUW: PI_OPC_Int and PIDeltaV_ACtr services are not automatically

Description
stopped during DeltaV uninstallation phase.
During v12.3.1 to v13.3.1 upgrade of Application Station which is

configured as Advanced Continuous Historian, the PI_OPC_Int_SC and
User Scenario PIDeltaV_Actr services are not automatically stopped during DeltaV
uninstallation phase. This eventually results to failure in renaming DVData
folder or loss of DVData during DeltaV uninstallation.
Prevention None.
Recovery Manually stop PIDeltaV_ACtr and PI_OPC_Int_SCxx services .
Incident TFS386584
Intools SPI: Controller Type under DCS panels should be updated. MQ,
Description
SQ, and PK controllers must be included.
User Scenario MD/MD PLUS is no longer supported in v14.3.
Prevention None.
Recovery None.
Page 59 of 140
Incident TFS306131
BA Model Builder – Model DTW tab – Entering Decimal first in DTW

Description Weight field crashes the User Interface (immediately on French/Russian;
intermittently on English).
User Scenario Issue is experienced when using the DTW.
Avoid entering decimal first. If user enters number-decimal-number, it

Prevention
seems to be OK; issue is just with decimal first.
Recovery None.
Incident TFS389816
System Preferences: Enabling or Disabling of "Batch Control" does not

Description
enable/disable DVBatchAdmin and SOFTPHASEUSER accounts.
DVBatchAdmin and SOFTPHASEUSER accounts only follow the

User Scenario configuration setup by the user in system preferences during installation of
ProfessionalPLUS (i.e. get enabled or disabled).
Prevention None.
Recovery Manually enable or disable the accounts.
Incident TFS396271
Unable to import C:\DeltaV\samples\BatchTutorial\Complete.fhx due to

Description
CTLR1 is configured as MD Series 2.
Migrate (should be necessary), and then import

User Scenario C:\DeltaV\samples\BatchTutorial\Complete.fhx. Observe that import is not
complete – CTLR1 is missing.
Prevention None.
Open Complete.fhx, and then replace CTLR version from:

VERSION { VERSION="MD Series 2" MAJOR_REV="7" MINOR_REV="3" }
Recovery
To:
VERSION { VERSION="MD Plus" MAJOR_REV="14" MINOR_REV="3" }
Page 60 of 140
Incident TFS278178
Batch Analytics Model Building user Interface – when a unit's BATCH_ID

and BA_STAGE are historized using Compression ON (due to String data
Description
type to save space), the Retrieve Stages failed to get the stages for the
batches and no error message.
User Scenario User turns the compression ON for the string data types.
Prevention Use manual stages or change the Compression = OFF.
Recovery None.
Incident TFS396138
VCAT: With VCAT preferences set to Auto, when user decommissions any
embedded node that is checked out by other user, node is not being
Description
decommissioned with no warning or error. It went to red X then to
unconfigured state.
Prevention Manually check in the node first, and then check out.
Recovery None.
Incident TFS393153
[DUW] Application timeout during installation encountered during

Description
installation of DUW from 11.3.1 to 14.3 Upgrade.
Upgraded Application Station from 11.3.1 to 14.3. The installation stopped

User Scenario
at Windows Powershell installation.
Prevention None.
Recovery Rerun the installer.
Incident TFS368189
Description Some DeltaV items are not displayed in the Windows Start menu.
Installed DeltaV 14.3.

User Scenario At finish, clicked on the Start Menu button in Windows. Noted that some of
the expected DeltaV items are missing.
Prevention None.
Items can be launched from the folder

Recovery
C:\ProgramData\Microsoft\Windows\Start Menu.
Page 61 of 140
Incident TFS309101
SBU: Fails to manually compress DVData file due to .wav files in sound
Description
folder containing invalid "©" characters.
System Backup Utility (SBU) from DVD1 was ran to upgrade the
User Scenario
ProfessionalPLUS from v13.3.1 build to another v13.3.1 build.
Rename all .wav files containing the invalid character and manually rerun
Prevention
compression.
Recovery Same as Prevention
Incident TFS376208
DVInstall\DUW: Unable to install DeltaV because DUW and manual

installation kept asking to reboot the machine during pre-Install (preparing
Description
the InstallShield wizard) even though ProfessionalPLUS has already been
rebooted more than 4 times.
During installation shield wizard preparation while upgrading

ProfessionalPLUS using DUW, a prompt 'Setup has determined that your
User Scenario
computer needs to reboot' appears. The message was persistent even
when the machine has been rebooted several times.
Prevention None.
Before continuing, restart your computer up to two times to ensure all

pending operations have completed. After restarting, run the installation
again. If the issue persists, you can modify or delete the registry keys
referenced below, which may contain orphaned values that are preventing
you from installing.
To delete the orphaned PendingFileRenameOperations registry key:
Recovery 1. Open a registry editor, such as Regedit.exe or Regedt32.exe.
2. Navigate to HKLM\SYSTEM\Current Cont rolSet\Control\Session
Manager\.
3. In the right navigation pane, right-click the
PendingFileRenameOperations key, and then click Delete.
4. Close Registry Editor.
Page 62 of 140
Incident TFS249044
DUW: Information in using PV IGNORED ALARM or any user defined

Description parameter that will have a conflict during Upgrade should be documented
somewhere in DVUpgrade.chm.
Import during an upgrade failed due to having a custom alarm type named
User Scenario PV IGNORED ALARM in the departure version. In v13, PV IGNORED
ALARM was added as a pre-defined system alarm type.
Prior to upgrade, users will need to change the configuration in the earlier
Prevention release to rename this alarm type to something that does not conflict with
the pre-defined system alarm type.
Incident TFS324131
Upgrade: Error “Unable to migrate DVHisDB to current version” after

Description
upgrading Batch Historian Server to v14.3.
User reinstalls Batch Historian after upgrading Batch Historian Server to

User Scenario
v14.3.
Prevention None.
Click OK to proceed with the Batch Historian installation, and then restore
Recovery the Archive database(s) by copying the two files back onto the workstation
and using the Batch Historian Administration Tool to reattach them.
Incident TFS329896
History Analysis pages failed to load after installing History Web Service
Description
on the History Analysis Server Application Station.
User installs History Web Service (HWS) on a working History analysis

User Scenario
server and changes IIS settings as specified in the installation procedure.
Prevention None.
Uninstall History Web Service, and then revert the IIS settings. Reinstalling
Recovery
History Analysis may also be needed.
Page 63 of 140
Incident TFS353466
Description Upgrade: DeltaV Upgrade Wizard exits after rebooting the workstation.
User runs Upgrade Wizard and is prompted to reboot the workstation.

User Scenario
Upon restart, DeltaV Upgrade Wizard starts but exits after a few seconds.
Prevention None.
Recovery Manually launch the Upgrade Wizard.
Incident TFS341728
OPC Remote Ping: Default computer name is set to “V” after launching
Description OPC Remote Ping and “Server Busy” dialog box appears when entering
an incorrect computer name.
User Scenario User tests connection to another OPC server.
Prevention None.
Click Switch to.. on the “Server Busy” dialog box, and then relaunch OPC
Recovery
Remote Ping.
Incident TFS370073
ASCO 32 coil version and 48 coil version CHARM are not differentiated in
Description
the Controller and I/O Upgrade Utility.
User Scenario User performs a firmware upgrade on the ASCO CHARM.
Prevention None.
Recovery Click each CHARM instead of selecting all for upgrade.
Incident TFS368337
Description DeltaV Database server is terminated when deleting 2000 modules .
User Scenario None.
Prevention None.
Restart Database Server from Database Administration or relaunch DeltaV

Recovery
Explorer.
Page 64 of 140
Incident TFS372220
Errors related to SCU path when running workstation configuration on the

Description
Standby Application station
User installs DeltaV v14.3, runs workstation configuration to set the

Application station as the Standby, and then gets the following error
messages when DeltaV services is being restarted:
The Pic_Path \\PHTE6-570\DVDATA\GRAPHICS-IFIX\PDB is
invalid
User Scenario
The Sched_Path \\PHTE6-570\DVDATA\GRAPHICS-IFIX\PDB
is invalid
The PDB_Path \\PHTE6-570\DVDATA\GRAPHICS-IFIX\PDB is
invalid
Prevention None.
Run c:\DeltaV\bin\Ifixscufilefixup.exe, and then restart the DeltaV

Recovery
service.
Incident TFS376989
Description Unable to join domain during Workstation Configuration
User runs workstation configuration, and then gets an error message when
joining the network:
User Scenario An error occurred while attempting to enter the
domain/workgroup Domain_Name…The specified domain
either does not exist or could not be contacted.
Run ipconfig from the command line to check for duplicate DeltaV ACN
address.
Prevention
The workstation will report an IP address 169.x.x.x if a node with the same
ACN address exits.
Recovery Correct the IP address in the NIC settings.
Incident TFS378737
Description Fatal error when launching OPC Mirror Tray from Windows Shortcut
User Scenario User attempts to launch OPC Mirror tray from Start  OPC Mirror.
Prevention None.
Recovery Launch OPC Mirror Tray from System tray (beside the time and date).
Page 65 of 140
Incident TFS383891
DeltaV OPC .NET Server service does not start automatically after
Description
installing Excel Add-in Runtime Tool.
User follows instructions to install the Excel Add-in Runtime from

C:\DeltaV\bin\ExcelAddInRuntime, and then gets the following error when
User Scenario attempting to read a DeltaV OPC parameter:
“Unable to browse runtime server. Verify DeltaV OPC..
NET services are running.”
Prevention None.
Recovery Reboot the workstation.
Incident TFS392357
Description AMS installation fails on a DeltaV workstation installed with OPC Mirror.
DeltaV v14.3 and OPC mirror are already installed on the workstation, and
User Scenario the user installs AMS v14. AMS installation fails with error related to
MSVC++ Redistributable file version 14.0.23506.
Install AMS prior to OPC Mirror so correct VC++2015 redistributable

Prevention
version is installed.
Recovery None.
Incident TFS392658
Description “Obsoletectrldetect - System error” when running Upgrade Wizard
User runs Upgrade Wizard to upgrade v12.3.1 or v13.3.1 workstation with

Microsoft Update KB2999226 to v14.3. The following error message
User Scenario appears:
“The program can't start because api-ms-win-crt-
runtime-l1-1-0.dll is missing from your computer” .
Prevention None.
For v13.3.1:
1. Uninstall KB2999226 from Installed Updates, and then reboot.
2. Manually run the Windows6.1-kb2999226-x64_Sep2015 MS update
Recovery from DVD2  OSHotfixes  x64.
For 12.3.1:
1. Uninstall VC++ 2012, 2015 Redistributables, and DUW.
2. Rerun DUW.
Page 66 of 140
Incident TFS393346
When launching Upgrade Wizard, the following message appears:

Description “The upgrade procedure can be performed only by users
with administrator privileges”
User Scenario None.
Prevention Disable UAC before running Upgrade Wizard.
Relaunch Upgrade Wizard with elevated privileges:

1. Right-click the Upgrade Wizard icon.
Recovery 2. Select Run As Administrator. A User Account Control (UAC) warning
appears.
3. Type the administrator's password or click the Yes or Continue button.
Incident TFS371638/TFS394361/ TFS394643
Workstation Configuration does not prompt for domain credentials before

Description
attempting to join the domain.
User upgrades the workstation with OS change or fresh installs v14.3, runs
User Scenario workstation configuration, and then gets an “Access is denied” error
message when attempting to join domain.
Prevention None.
Click OK on the error, and then enter the domain credentials when
Recovery
prompted.
Incident TFS396056
Security Update Manager cannot be cancelled without completing the

Description
Microsoft Updates.
User fresh installs or upgrades the workstation and skips installation of

Microsoft Updates in DVD2. User then runs SecurityUpdateManager from
C:\DeltaV\bin but decides to click “Cancel” because MS Updates folder is
not available.
User Scenario
The following message appears repeatedly regardless of the button
selected:
“OSHotfix folder was not found. Please browse DVD2”
Prevention None.
Recovery Stop SecurityUpdateManager from Windows Task Manager.
Page 67 of 140
Incident TFS370427
Prompts the user to enter DeltaVAdmin user password during workstation

Description
configuration on an Inter-Zone server newly installed with DeltaV
User runs workstation configuration for the first time on an Inter-Zone

server workstation, and then logged off as part of the process. When
Windows starts again, the user is prompted to enter DeltaVAdmin
password:
User Scenario
“The DeltaVAdmin password has been changed from the
original installation value. Please enter the current
DeltaVAdmin password to continue.”
Prevention None.
Password for DeltaVAdmin is entered during the installation of DeltaV. If

you know the password, enter the correct password.
Recovery Otherwise, click OK. A message "The DeltaVAdmin password that
was entered is incorrect" will appear. The prompt will be repeated 3
times until it is fully dismissed.
Incident TFS400022
ACH Backup fails due to Disabled Microsoft Software Shadow Copy

Description
Provider service.
User performs ACH backup via Backup and Recovery or manual backup
User Scenario following instructions in KBA NK-1400-0212: Back ing Up and Restoring
DeltaV Advanced Continuous Historian Data.
Set the Microsoft Software Shadow Copy Provider service Startup type to
Prevention
Manual, and then start the service.
Recovery None.
Incident TFS336859
Flexlock message reports that user with Administrative privileges is not an

Description
Administrator when the domain controller cannot be contacted.
Likely to be observed when attempting to switch from DeltaV to Windows

Desktop which prompts user for User Name and password. The following
User Scenario message appears:
User:USER_NAME is not an Adminstrator on
Computer:COMPUTER_NAME
Check connection between the DeltaV workstation and the domain

Prevention
controller.
Recovery None.
Page 68 of 140
Incident TFS388531
Integrated Enterprise PI tag names with"$" and "-" prefix are replaced by
Description
one tag with prefix "_" after the upgrade.
Observed when upgrading Integrated Enterprise PI from V13.3.1 to v14.3.

User Scenario For example: $SGN1\OUT.CV and the other one is -SGN1\OUT.CV will
change to _SGN1\OUT.CV
Prevention None.
Recovery Rename the tags with the same name before upgrading.
Incident TFS281961
Smart Switch Control Module MGINFO string is not retained during a

Description
DeltaV Upgrade when custom DDs are imported.
Network Device Command Center shows “???” on all commissioned Smart

User Scenario Switch’s parameter values after an upgrade, from v12.3.x and lower, to
v13.3 and higher. Custom DDs were imported during the upgrade.
Prevention None.
Perform one of the following recovery actions:

1. Recommission the Smart Switches by decommissioning it from NDCC,
deleting the Smart Switch control module from DeltaV Explorer, and
then commissioning the Smart Switch using NDCC.
Recovery
2. Restore the MGINFO string by writing it to the Smart Switch control
module in Control Studio Online, and then uploading the change
followed by a download of the switch module. The MGINFO string can
be found on the migrated FHX file.
Incident TFS152654
Description Cannot get any trend tags using “GetTrendTags” web method
History Web Service client does not return any result using the
“GetTrendTags” web method for Continuous Historian. Any wildcard
entered will give a non-informative error message.
User Scenario
The error prevents the user from getting the information this web method
provides but does not hinder the user from running the entire History Web
Service client app.
Prevention None.
Recovery One-time work-around is to enable 32-bit applications on IIS settings.
Page 69 of 140
Incident TFS238973
Description DeltaV Executive Portal is not included in DUW Laundry List.
DUW does not detect Executive Portal nor instruct the user to uninstall
User Scenario
Executive Portal or Communicator before installing DUW.
Prevention None.
Recovery Make sure you uninstall the DeltaV Executive Portal before upgrading.
Incident TFS240003
Displays are not being propagated correctly on large batch systems

Description
through workstation download.
Downloading the DeltaV workstations should propagate all displays from

the ProfessionalPLUS. On those nodes which are not getting updated, the
User Scenario
yellowpages log shows the workstation is requesting for the displays , but
the request is never answered.
Prevention None.
Recovery Manually copy the displays over to target workstations.
Page 70 of 140
Incident TFS243185
Windows Firewall Rules do not get re-added when using the "Reinstall
Description
OS" option in DUW.
After upgrading DeltaV using the DUW option to Reinstall OS, the Firewall
User Scenario
rules are not applied.
Prevention None.
Use DSASetup.exe to apply the rules manually.

Or
Perform the following steps:
1. On an old workstation, backup the firewall rules:
netsh advfirewall export
C:\WindowsFirewallSettingsBackup.wfw
2. On a new workstation, turn off firewall profiles.
Run the following on the command line:
Recovery Netsh advfirewall set AllProfiles state off
Netsh advfirewall set CurrentProfile state off
Netsh advfirewall set DomainProfile state off
Netsh advfirewall set PrivateProfile state off
Netsh advfirewall set PublicProfile state off
3. Copy the backup of firewall rules (from step 1) to the new workstation,
and then restore the firewall rules:
netsh advfirewall import [Location of firewallrules
backup file xxxx.wfw]
Incident TFS280184
Description Master time server reverted to ProfessionalPLUS after upgrading DeltaV.
Master time server reverted to ProfessionalPLUS after upgrading DeltaV.

User Scenario
The Backup Time Server setting is unaffected.
Prevention None.
Recovery Manually reset the Master time server in DeltaV Explorer.
Page 71 of 140
Incident TFS302968
VCAT Warnings were received for instances not assigned to the Batch
Description
executive when downloading the Batch Executive (related to TFS32470).
When downloading the Batch Executive, VCAT warnings appeared

because of items that need to be checked in to download. However, the
User Scenario
items listed are not part of the equipment or recipes assigned to the Batch
Executive.
Prevention None.
Recovery Download with the "Download with items checked out" check box selected.
Incident TFS370773
Deletion and Restoration of 500 graphics or more takes more than 10

Description
minutes with VCAT enabled.
Deletion and Restoration of 500 graphics or more takes more than 10

User Scenario
minutes with VCAT enabled. This is considered a rare scenario.
Prevention None.
Recovery None.
Incident TFS382054
Laundry List on DeltaV Upgrade Wizard on non-ProfessionalPLUS stations

Description
shows "Verify DNS settings before upgrade”.
Laundry List on DeltaV Upgrade Wizard on non-ProfessionalPLUS stations

User Scenario shows "Verify DNS settings before upgrade", which should only be on
ProfessionalPLUS.
Prevention None.
The message "Verify DNS settings before upgrade" can be ignored if it

Recovery
shows up on non-ProfessionalPLUS.
Page 72 of 140
Incident TFS394038
After running the Workstation Configuration on a redundant application

Description station with DLINK, DNS setting on the DLINK has two addresses that do
not exist.
After running Workstation Configuration on a redundant application station

with DLINK, DLINK DNS has settings: 10.12.0.x (preferred) and 10.12.0.y
User Scenario (alternate). Neither of these addresses exist on the system.
Since DLINK is a direct connection to its partner, there is no need to have
anything in DLINK DNS fields.
Prevention None.
Recovery Ignore DNS settings for the DLINK.
Incident TFS395357
Adding DeltaV Users to DeltaV Groups may fail in Workstation

Description
Configuration in an application station in a domain environment.
In Workstation Configuration, the user may encounter error prompts which

include the following:
“NTSetup Error
User Scenario NTSETUP.AddGlobalGroupsToLocalGroups: Error adding
<DeltaV User name> to the Domain <User Group>.
No mapping between account names and security IDs was
found.”
Prevention None.
Perform the following steps as a work-around:

1. Record the User name and Group name specified in each of the error
Recovery prompts.
2. Acknowledge the error prompts.
3. Manually assign the User to the respective Domain DeltaV group.
Page 73 of 140
Incident TFS396271
Unable to import C:\DeltaV\samples\BatchTutorial\Complete. fhx because

Description
the CTLR1 is configured as MD Series 2
Importing the test database for Batch is incomplete due to having

User Scenario
Controller version which is not supported in v14.3.
Prevention None.
Open Complete.fhx, and then replace the CTLR version

From
VERSION { VERSION="MD Series
Recovery 2" MAJOR_REV="7" MINOR_REV="3" }
To
VERSION { VERSION="MD
Plus" MAJOR_REV="14" MINOR_REV="3" }
Incident TFS397395
There are 1120 empty folders created under c:\DeltaV; 1050 of these
Description
folders are left behind after the uninstallation.
There are 1120 empty folders created under c:\DeltaV; 1050 of these
User Scenario
folders are left behind after the uninstallation.
Prevention None.
Run "rmdir C:\DeltaV /S" and "rmdir D:\DeltaV /S" in cmd with
Administrator privileges to delete most of the DeltaV subfolders.
Recovery For the remaining folders not deleted by the command, modify the ACL
and grant FULL CONTROL to the current Administrator, and then delete
each folder manually.
Incident TFS393153
The message “Application timeout during installation” appeared during the

Description
installation of DeltaV Upgrade Wizard.
When upgrading a workstation station during DUW installation, it stops

responding and shows the following message prompt during the Windows
User Scenario Powershell installation part:
“Application timeout during installation”
Prevention None.
Recovery Rerun the installer.
Page 74 of 140
Incident TFS376208
Unable to install DeltaV because DUW and manual installation kept asking
to reboot the machine during pre-installation (preparing the InstallShield
Description
wizard), even though the machine has already been rebooted more than 4
times.
The installer shows the following message when the issue occurs:
“Setup has determined that your computer need to
reboot before running the DeltaV Upgrade Wizard.
User Scenario
Click YES to reboot, then run setup.exe again from
MigrationUtilities/UpgradeWizard
Click yes to reboot now, click NO to exist instead.”
Prevention None.
Before continuing, restart your computer up to two times to make sure all
pending operations have completed. After restarting, run the installation
again.
If the issue persists, modify or delete the registry keys referenced below,
which may contain orphaned values that are preventing the installation.
Warning: Incorrect changes to registry settings can cause serious system
problems that may be irreversible without reinstallation of the operating
system. It is recommended to back up your Windows Registry before
Recovery making changes to it.
To delete the orphaned PendingFileRenameOperations registry key:
1. Open a registry editor such as Regedit.exe or Regedt32.exe.
2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session
Manager\
3. In the right navigation pane, right-click the
PendingFileRenameOperations key, and then click Delete.
4. Close the Registry Editor.
Incident TFS24996
When installing DeltaV Simulate, the InstallShield “1628: Failed to

Description complete installation” error message appeared, and the installation was
aborted. The error appeared every time Windows was restarted.
When installing DeltaV Simulate, the InstallShield “1628: Failed to

User Scenario complete installation” error message appeared, and the installation was
aborted. The error appeared every time Windows was restarted.
Prevention None.
Log on using an account with administrator privileges, and then complete

Recovery
the installation task.
Page 75 of 140
Incident TFS312053
Unable to get the License Manager for Entech toolkit to register the license
Description
even though the user had admin privileges.
This issue will occur when another application is using TCP port 1947,
which is used by the Sentinel Messenger Dongle that contains the license
number.
User Scenario The following error is logged in Windows System when the issue occurs:
“Error: Failed to open server TCP port 1947. Maybe LM
is already running.”
Prevention None.
Make sure that the TCP port 1947 is available before running the Entech
Recovery License Manager. Entech Troubleshooting application was modified to
include this step.
Incident TFS401886
All nodes went Red X on a large batch after downloading the virtual
Description
operator stations and 2 Batch executive nodes altogether.
On large batch systems, all nodes went Red X after performing “download
all nodes”. This occurred in a system with 60 operator stations, 3
User Scenario application stations, and 42 controllers (40 real, 2 virtual).
After approximately 40 minutes, everything started communicating again.
Prevention Download the workstations in batches of 10, not all together.
Recovery Wait for the communication to normalize.
Incident TFS408365
Verification Rules in ER-2 builds allow Function Rules like “Bool_var == 0”

Description and “Bool_var == 1”, but these expressions are no longer allowed and
cause Verify Errors.
Migrating scripts from earlier releases may become invalid type

User Scenario
assignments, getting flagged with verification warnings.
Prevention None.
You must manually change all Function rules to use "true" and "false"
Recovery
instead of 1 and 0 when doing operations with Boolean values.
Page 76 of 140
Incident TFS409283
DeltaV Explorer's workstation Properties dialog box has expanded and is

Description now too tall to fit on a 1024 x 768 screen resolution—cannot see or click
the OK button anymore.
User Scenario Error occurs in Windows 10 dynamic resolution settings at 150% .
Prevention None.
Press Enter on the keyboard to exercise the default-selected button, which

Recovery
is the OK button.
Incident TFS411280
Remote Operator Station – CIF Logs are no longer located in the correct
Description
directory (registry key is pointing to the wrong directory).
User Scenario All Remote Operator Stations
Prevention None.
Logs can be found in

Recovery DVDATA(D:)\DeltaV\ProgramData\Emerson\RemoteSystems\{a43cbd0
c-4a3c-4daf-9b99-03eeaccf0d7d}
Incident TFS411763
DeltaV Explorer crashed when right-clicking on the right pane without

Description
selection in the left pane.
User Scenario Performing a right-click in New Signature Policy
Prevention None.
Recovery Reopen DeltaV Explorer.
Page 77 of 140
Incident TFS414243
Upon FP1 hotfix installation on ProfessionalPLUS, DeltaV service does not

Description
shut down automatically.
User Scenario Installation of Feature Pack 1
Prevention None.

1. Go to services.msc.
2. Right-click the DeltaV service, and then click Properties.
Recovery 3. Click Dependencies. You will find all the dependency services under
the box labeled “This service depends on the following system
components”.
4. Stop all services that are in this list.
Incident TFS414674
Live\ACH: Emerson user got an error message "Error retrieving

mapping list from server. RPC Invoke failed. No Read Access-
Description
Secure Object" in PI SMT after applying HB1. The user must be a
piadmin.
Emerson user who had access to create mappings and trusts, got access
denied doing anything related to Mappings and Trusts in PI SMT after
User Scenario applying HB1.
Before applying HB1, Emerson was in piadmin group. After applying HB1,
Emerson became PIOperators, PIWorld.
Prevention None.
Perform the following workaround:

1. Open the AboutPI-SDK application.
2. Click Connections  select your pi server.
Recovery
3. Click Connections  options.
4. Move PI Trust up to the top of the Protocol order.
This would force the PI to authenticate using trust first and then mapping.
Page 78 of 140
Incident TFS415413
When enabling System Preference = Batch after Workstation

Configuration is already run for the first time, the DVBOpcSvr.exe crashed
Description
with error “RtSession::LogOnUser returns RT_ITEM_NOT_FOUND
(DvBatchAdmin user is disabled by cybersecurity project)”
The issue is encountered when Batch is enabled in the System Preference

User Scenario only after the running Workstation Configuration for the database with
batch configuration.
Make sure to select Batch on system preferences before the initial

Prevention
Workstation Configuration.
Recovery None.
Incident TFS416437
HWS/IIS benchmark – After installing History Web Services which applies

Description IIS security hardening settings, and then rebooting the machine, Batch
Historian Admin Tool failed to connect.
This issue may occur when History Web Services is installed in Batch
User Scenario
Historian node.
Prevention None.
The workaround is to enable these protocols TLS 1.0 by running the

following commands from the command line, and then reboot the machine:
Recovery reg add

"HKLM\SYSTEM\CurrentControlSet\Control\SecurityProvid
ers\SCHANNEL\Protocols\TLS 1.0\Server" /v "Enabled"
/t REG_DWORD /d 0xffffffff /f
Incident TFS416427
Custom Client application utilizing the Recipe Exchange Control will get
Description
“Access Denied” message when executing the Connect Method.
Custom Client application utilizing the Recipe Exchange Control will get
User Scenario
“Access Denied” message when executing the Connect Method.
With the increased security implemented on version 14.3, clients utilizing

Prevention the Recipe Exchange Control would have to be digitally signed before it
can successfully connect to DeltaV.
Recovery None.
Page 79 of 140
Incident TFS416789
Description DvExp: DeltaV crashes when creating a new electronic signature policy .
The issue occurs when selecting Security in the hierarchy, and then right-
User Scenario
clicking the electronic signature in the content view to create a policy.
Prevention None.
The user can get to electronic signature policies by selecting the Security
node in the hierarchy, and then double clicking the electronic signature
Recovery node in the content view. This drills in and reveals the electronic signature
policies in the content view. If the user performs these steps, they can
create new policies without the issue.
Incident TFS374615
WIOC – Receiving hardware alarms as "Unidentified device on network"

Description
when using THUM
An Unknown device is also showing in the DeltaV Explorer list of

User Scenario decommissioned devices and also causes the hardware alerts when
connecting the THUM adapter to the WIOC’s network.
Prevention None.
Recovery The hardware alert goes away when disconnecting the THUM adapter.
Incident TFS304587
IFIX: Operate Run will crash immediately upon launch if a variable or

Description
threshold table (aka color table) was added to frsVariables.fxg.
Users can add variables or threshold tables to frsVariables.fxg as there is

no error message in doing so. However, frsVariables.fxg is full, and
User Scenario
adding anything to this will cause DeltaV Operate to crash when going to
runtime.
Customers should not be adding anything to frsVariables or frsVariables II.

If new variables or tables are being created, these should be added to
Prevention
either SIGlobals.fxg or User.fxg files. In addition, these files should not be
customized as these can be replaced by some hotfixes.
Transfer all customized variables or threshold tables to SIGlobals.fxg or

Recovery
User.fxg files.
Page 80 of 140
5.2 PK Controller
Incident TFS381012
Because of the PKID GUID, two laptops with the "same" project can get
out of synch with PK controller simply by decommissioning and
Description
recommissioning. It would be useful to list the PKID in the Project
Administration tab, so users are aware when in this state.
Prevention Not applicable
Recovery Not applicable
Incident TFS387032
OPC UA: DeltaV Clients (EIOC and Workstations) with blocks referencing
Description signals (where PK is the OPC UA Server) are bumping to BAD during a
PK switchover. AI blocks going to status 0 and DI block to status 12.
If the customer is using our OPC UA client (workstation or EIOC)

User Scenario monitoring data from the OPC UA server on the PK, the signals could be
bad for several seconds while the PK is switching over.
Prevention None.
Recovery None.
Incident TFS393829
PK: OPC UA – Disconnecting device network cable while monitoring items

Description with a python test client is causing controller to crash as a result of no
memory.
Prevention None.
Recovery None.
Page 81 of 140
Incident TFS387811
PK: Diag – OPC UA Server has a red X and status shows NOT
Description
CONNECTED after performing repeated connect and disconnect sessions.
Prevention None.
Recovery Close and reopen Diagnostics.
Incident TFS364739
DeltaV Operate paths get corrupted after rebooting PK Laptop several

Description
times, preventing DeltaV Operate from launching.
User will encounter several errors because the DeltaV Operate paths in
User Scenario the DeltaV_Operator_System_Configuration application were reverted to
the original OVA/Virtualbox VM Template’s PK Laptop name.
Prevention None.
Launch DeltaV Operator System Configuration and fix the paths for the
Recovery Database and Picture section to the actual PK Laptop name, and then
reboot the PK Laptop.
Incident TFS395781
Dell Latitude 7480 hosting Virtual Box VM with the .OVA Engineering
Description station requires user to change from Bridged adapter, and then back again
if the network cable is unplugged from the DeltaV LAN connection.
Install Virtual Box on a host PC with the Extension pack. Create a VM

using the .OVA PK Engineering station template. Issues with the DeltaV
network connection will be observed when the network cable is unplugged
User Scenario
and reconnected to the same or different skid. The network connection will
not work until the network adapter settings is changed from Bridged
adapter and settings changed back to Bridged adapter.
Prevention None.
Go into the host settings and remove the bridge connection for the
Recovery Network adapter, and then save. Go back into the settings, and then add
the bridge connection for the Network adapter.
Page 82 of 140
Incident TFS391948
PK Assistant – backup includes 2 SIS Alarm Help files generated by

Description
download (each system will generate its own).
If user enables SIS Alarm Help on some of their SIS alarms, and total
download SIS Alarm Help, 2 files are generated in the
User Scenario D:\DeltaV\DVData\AH:
 SisAlarmHelp.dat
 SisAlarmHelp.map
Prevention Do not perform a PK merge.
Recovery None.
Incident TFS387283
Merge Utility of standalone system failed due to "change from normal"

Description
alarm type.
The item was successfully renamed from "change from normal" to

"JP_change from normal" but was actually skipped on import. This caused
User Scenario
a cascade of import errors and ultimately the PK controller itself failed to
import.
Prevention None.
Recovery None.
Incident TFS395959
Standalone License Manager executed on HMI machine shows 'Historian

Description
scale-up +1000 tags Standalone License' when the historian is enabled.
Prevention None.
Recovery None.
Page 83 of 140
Incident TFS339187
DeltaV Diagnostics is sluggish when logged on to Windows with a non-

Description Emerson account and accessed through DeltaV Operate, on a non-
ProfessionalPLUS machine.
User Scenario Opening DeltaV Diagnostics on a non-ProfessionalPLUS machine.
Prevention None.
Log on to Windows with the emerson/administrator account, and then log

on with the required user with FlexLock, without the need to access
Windows Desktop.
Recovery
Or
Log on to the ProfessionalPLUS with any account, and then launch
Diagnostics as desired.
Incident TFS397073
Merge Utility – Merging standalone system fails due to changing alarm

Description
type name.
If the standalone system has a module with an alarm type that was derived
from the PCSD library and the BOP also has the same alarm type, there
will be a conflict. User may think that the conflicted Alarm types can be
renamed and reflected in any modules that use the same alarm type.
These PCSD alarm types cannot be renamed (on the standalone, which is
User Scenario essentially what is done in a temporary database).
1. Load an exported project from a standalone project.
2. Rename all files when the conflict list appears.
3. Attempt a load.
4. The load will fail because certain alarm types cannot be changed in the
final step.
Export the modules with the alarm types reflected in the modules, and then
Prevention
import them before the decommission (final step) in the Merge process.
Incident TFS387283
Merge Utility of standalone system failed due to "change from normal"

Description
alarm type.
Prevention None.
Recovery None.
Page 84 of 140
Incident TFS381012
Because of the PKID GUID, two laptops with the "same" project can get
out of synch with PK controller simply by decommissioning and
Description
recommissioning It would be useful to list the PKID in the Project
Administration tab, so users are aware when in this state.
Prevention None.
Recovery None.
Incident TFS403165
Feature Pack 1 could not be installed on PKRuggedLaptop because the

Description
DeltaV Service was not stopped.
Upon installation of Feature Pack 1, the following warning message is

encountered:
User Scenario “StopService Warning
Service DeltaV could not be stopped. Error = 0”
Prevention None.
Recovery Manually stop the DeltaV Service.
Page 85 of 140
Incident TFS405252
PK services are not stopped by the FP1 installer on PK Standalone

Description
system.
In the middle of applying Feature Pack 1 on a PK Standalone system, after

all applications are closed, and DeltaV services were stopped, the
following message will appear:
“File in Use
Some files that need to be updated are currently in
use
The following applications are using files that need
to be updated by this setup
ConfigExchangeService
User Scenario DeltaV API Broker Services

PK Project Service
PKAssistant
Selection: Automatically close and attempt to restart
applications.”
In the Local Panel, the message prompt is about:
DeltaV API Broker Services
In Balance-of-Plant, message prompt is about:
ConfigExchangeService and DeltaV API Broker Services
Prevention None.
In the message prompts, make sure that the radio button Automatically
Recovery close and attempt to restart applications is clicked. Then, acknowledge
the message prompt to stop the services.
Incident TFS408894
Description After applying FP1, Standalone PK with HMI cannot publish to HMI.
OPS station will not publish from DVA/WM after an upgrade from RCB to
User Scenario
DeltaV Live/HBZ.
The issue can be avoided by making sure there are no "Invalid IP config"
Prevention
issues before staring HB1 installation.
Recovery None.
Page 86 of 140
Incident TFS412894
DeltaV did not remove IFIX completely when DeltaV was uninstalled
Description during an upgrade of PK Standalone workstation to FP1; the next DV
installation failed.
User Scenario Uninstallation of DeltaV will leave 2 font files inside IFIX folder.
Prevention None.
Recovery Rename the files that were not deleted or move to another folder.
Incident TFS415010
PK: Making Port-to-Port communications changes with any assigned IO or

Ethernet IO causes a total download to fail and leaves the PK red X. This
Description
crash is due to a loss of communications with the IO subsystem; therefore,
the PK crashes due to IO being not available RT_ERROR.
Additionally, the new active card does not receive the new VLAN settings;
therefore, the PK is permanently red X until the IOPs are reset. Blue
download triangles persist at this point. Partial download to each
subsystem does not work.
User Scenario
The use case for making this change in the standalone is if the customer
wants to add an HMI or other ACN node to the Skid later on. Making these
changes can be problematic for the user, in both resolving and avoiding
the issue.
In order to make port-to-port changes online while avoiding the red X issue
requiring manual IOP reset, the user must do one of the following:
 Disable the IO subsystems, and then download them individually before
downloading P2P changes.
Prevention
 Perform a partial download of each subsystem after making the P2P
change, wait for controller to crash due to IO being not available,
reauthenticate, and then perform setup data download at PK-level to
restore communications to ethernet IO subsystem.
If the customer performs a total download under these conditions, the user
must first manually reset the IOPs, and then do one of the following:
 Decommission the PK (which requires decommissioning all the nodes in
the standalone system and rerunning PCInstall on the HMI), and then
Recovery
recommission and download the desired changes.
 Disable each of the IO subsystems, download them individually, and
then perform the setup data download to the PK node before re-
enabling the IO subsystems.
Page 87 of 140
Incident TFS414377
PK Controller: External Reference to parameters in SZ controller modules

Description does not always recover communication after a Redundancy Switchover
on the PK until the PK controller is authenticated.
The reference does not always resolve until the PK controller is

User Scenario
authenticated.
After applying the pre-release hotfix (which is automatic when installing

DeltaV v14.3.0.6984), customers must back up their projects and retrieve
into a new active card; this is necessary to get the global table added to
the controller’s download scripts.
1. Back up any projects that you wish to preserve.
2. Run Feature Pack 1 installer.
3. For each backup:
Prevention a. Perform a Retrieve to New Active.
b. Download the ProfessionalPLUS.
c. Delete the pre-hotfix project that the backup was created from.
This step is necessary, as new objectivity database needs to be
created in order to pick up the change. If you do not perform this step,
the module table will not be downloaded.
4. Flash-upgrade the PK and SZ controllers.
Perform downloads and check that the module table is downloaded to the
PK and SZ controllers on standalone system.
Recovery Same with Prevention.
5.3 Smart Commissioning for HART devices
Incident TFS382379
IO Studio/Asset Studio: Device configured to use a Controller's DST does

Description
not appear in IO Studio.
Page 88 of 140
Incident TFS381508
Wireless device with a publish rate exceeding 5 minutes is sent to the

Description
punch list with the error "One or more test steps failed”.
When a wireless device has a publish rate (broadcast rate, update rate)
exceeding 5 minutes, it should be sent to the punch list with an error
User Scenario
referring to this. Instead, the device is put through the test and ends up in
the punch list with the “One or more test steps failed” error.
Prevention None.
Recovery None.
Incident TFS382379
IO Studio/Asset Studio: Device configured to use a Controller's DST does

Description
not appear in IO Studio.
Prevention None.
Recovery None.
Incident TFS404971
In DeltaV Device Commissioning when VCAT is enabled, several devices

in CSLS failed to bind with punch list issue “Referencing controller not
Description
checked out by current user” even if the SZ controller is already checked
out by the current user.
In DeltaV Device Commissioning when VCAT is enabled, users may

User Scenario encounter an issue where almost all devices fail at Bind phase. Issue from
punch list shows “Referencing controller not checked out by current user”.
Prevention None.
Check in the SZ controller in VCAT using the option “Keep checked out”,
Recovery
and then retry commissioning.
Page 89 of 140
Incident TFS404986
In DeltaV Device Commissioning, when a module is not assigned to the

Description correct SZ controller, punch list bind issue and suggested resolutions are
not indicating the actual module name.
DeltaV Device Commissioner shows the issue “SIS Device is referenced

User Scenario by module with incorrect assignment” and the suggested resolutions are
not stating which module is affected.
Prevention None.
Add "Referencing Modules" column to the punch list grid. This column will
Recovery
indicate the actual module name.
Incident TFS 405172
DeltaV Device Commissioning: When an SIS module referencing SIS DVC

Description output devices is not assigned to the correct CSLS, punch list bind issue
and suggested resolutions are not indicating the actual SIS module name.
DeltaV Device Commissioner shows the issue “SIS 2-State DVC output
User Scenario device is referenced by a SIS module assigned to a different CSLS” and
the suggested resolutions not stating which SIS module it is.
Prevention None.
Add “Assigned to Controller" and "Referencing Modules" columns to the

Recovery
punch list grid. These columns will indicate the actual SIS module name.
Incident TFS407579
DeltaV Device Commissioning: After reassigning an SIS module from one

Description CSLS to another CSLS within the same SZ controller, Binding failed with
“Download failed” issues.
Launch DeltaV Explorer. Under SZ1 controller with 2 CSLSs, drag-and-

drop the SIS module from CSLS-3 to CSLS-2. Do not download CSLS-2.
User Scenario Launch DeltaV Device Commissioning. Select auto-commissioning policy.
Acquire CSLS-2. Start auto-commissioning. Go to punch list. Take note of
the “Download Failed” Bind issues and the suggested resolutions.
Prevention None.
In DeltaV Explorer, the user gets a message indicating that the module
"will not remove the SIS module from any previously assigned Logic
Recovery
Solver". This also indicates that user will need to download both CSLS in
DVExplorer, and then retry binding in DeltaV Device Commissioning.
Page 90 of 140
Incident TFS413179
Device Commissioning Report: If device passes Configure and fails Test,

Description Commissioning State displays with a white background/white text instead
of a black background/white text.
User Scenario This may occur when generating a Device Commissioning Report.
Prevention None.
Please note that a white configuration box next to a failed (i.e. red) test box
Recovery
in a report means the configuration phase passed.
Incident TFS377791
In DeltaV Device Commissioning, devices sometimes remain in Ready for

Description
Binding list during both automatic and manual commissioning.
Devices sometimes remain in Ready for Binding list during both automatic
User Scenario and manual commissioning, while the expectation is that all devices in
ready for binding will move through binding steps.
Prevention None.
Recovery Bind the devices manually.
Incident TFS382698
In IO Studio, creating an SIS device from Master with the same name as
Description an existing Unassigned I/O Reference shows "In Progress" after
completion.
Progress bar shows 100% and "Done!", but the Status shows "In
User Scenario
Progress" when creation is complete.
Prevention None.
Recovery None.
Page 91 of 140
5.4 OPC UA
Incident TFS375721
OPC UA: EIOC/Workstation OPC UA Client PDT connecting to

Workstation UA Server with User Authentication: Anonymous logon shows
Description
good in Diagnostics though the option Anonymous logon is uncheck ed in
the UA Server.
This is observed when no LDT is configured. This is expected because

User Scenario when no LDTs are downloaded, no data is reported, so the PDT status
defaults to GOOD.
Incident TFS377461
OPC UA – EIOC "hosts" file is not updated if the IP address in the

Description
endpoint URL is changed.
Prevention None.
Manually delete the contents of the "hosts" file in the 18550 maintenance
port of the EIOC. Add the new IP address to the hosts file, reboot the
Recovery
server, and then redownload the port. Verify the OPC UA traffic is now on
the newly specified network.
Incident TFS379562
OPC UA – Multiple downloads are required for a DeltaV client to establish

Description
30,000 signals with a single workstation server.
Prevention None.
Perform repeat downloads of the PDT's that failed to connect until all of
Recovery
the signals are connected and show "GOOD" status in Diagnostics.
Page 92 of 140
Incident TFS391194
After reenabling the OPC UA Client subsystem of a workstation UA Client,

Description PDTs that had status "Device No Comms" show and are stuck with a
status of "OPC UA Client is Disabled".
If you disable, and then enable the OPC UA Client, you could get the PDT
User Scenario
status into this state.
Incident TFS395159
OPC UA – Signals on a DeltaV OPC UA client fail to update when the data
Description
quality becomes "BAD".
This is an enhancement request. It was not intended to support bad data

User Scenario
quality status in the client.
Incident TFS359755
WS OPC UA Server Performance: Create monitor service fails when

Description
loading a subscription of 1000 opc data items using https endpoint .
While running performance test on WS OPC UA Server, loading a UAP file

User Scenario in UA Expert client with 1000 configured and monitored data items failed
with error “CreateMonitoredItems failed [ret = BadRequestHeaderInvalid]”.
Prevention Reduce loading from 1000 to600 OPC data items.
Recovery Same as Prevention.
Page 93 of 140
Incident TFS393245
BOL – Need to document that an exported FHX does not include any
Description certificates. Certificates must be manually reimported. This also applies in
PK merge.
An exported FHX does not include any certificates. Certificates must be

manually reimported. This also applies in PK merge. This behavior is
intended to protect the security of the certificates. Users will need to be
User Scenario aware that the configuration can be transferred via FHX, but any OPC UA
certificates (self-signed, clients, issuers, revocation lists, etc.) will all need
to be reimported into the new system manually. This is true for all DeltaV
OPC UA nodes (workstation server, workstation client, PK, and EIOC).
Prevention None.
Recovery Certificates must be manually reimported.
5.5 Batch Analytics
Incident TFS247975
Batch Analytics server user that is part of local group still will not have
Description access to Batch Analytics Operations Information Web Server (BOWS),
after the group is added in the User access for Batch Analytics Server.
Prevention None.
Recovery Add each user one by one to the User Access List.
Incident TFS194537
Batch Analytics – Web view client gives error messages for unprivileged
Description
user during setup but seems to connect OK anyway.
Prevention None.
Recovery Ignore the dialog boxes and connect anyway.
Page 94 of 140
Incident TFS249736
Batch Analytics Viewer/Multichart – When Quality Prediction trend for 2

Description PQPs on one batch are added to Multichart, while batch is Running, one
trend will be skewed (they are fine if batch is Complete).
Prevention None.
View the PQPs on the actual QP view or wait to view on Multichart until
Recovery
they are Complete.
Incident TFS246700
BA Viewer – Viewing a parameter in Fault Detection view while batch is

Description running sometimes does not keep updating with current stage (parameter
not monitored in later stages).
Prevention None.
Close that parameter trend, and then select that parameter again—it will
Recovery
show all stages (to date) when it relaunches.
Incident TFS59715
Batch Analytics Model Builder: Sample Density Ratio is always zero

Description regardless of the configured continuous historian sampling period of the
parameter.
In Product  Batches  Availability tab, “Data Availability Ratio” is always

User Scenario zero regardless of the configured continuous historian sampling period of
the parameter.
Prevention None.
Recovery None.
Page 95 of 140
Incident TFS233265
Some batches were not calculated correctly after RBEX switchover, no

Description
data for QP and FD after switchover.
First switchover: RBEX-T620L3 to RBEX-T620L3_S => Batch List was OK

(updated), but the QP and FD are incomplete.
User Scenario
Second switchover: RBEX-T620L3_S to RBEX-T620L3 => batches were
not updated in Batch List, QP and FD are also incomplete.
Prevention None.
Recovery Restart the BA Monitoring Service.
Incident TFS229448
Batch Analytics Monitoring Service – After deploying 2 projects, and then

Description un-deploying 1 project, the un-deploy does not release the OPC
connections.
User Scenario OPC connections still exists after un-deploy either of the 2 projects.
Prevention None.
Recovery Un-deploy the second project and all the OPC connections are closed.
Incident TFS248692
Batch Analytics Manager Diagnostics – When the HDA tags are retrieved
Description from PI and user did not write the correct DA path for DeltaV parameters,
all parameter readings are 0s and no error generated.
When user did not specify the correct parameter name in DA column, and
deployed the project, the Calc server tried to read the parameter value,
and it failed and returned 0. Even though the reading failed, it never
User Scenario returned the error, there was no error message generated in the Batch
Analytics Manager Diagnostics Event Log for "parameter not found" error.
The number Connections did show the number of bad
connections/parameters.
Prevention None.
Stop campaign (for new batches) and un-deploy the project. Open project
in Batch Analytics Model Builder add the correct name for all the
Recovery
parameters in Equipment  Parameters page, and then save, generate
modules, redeploy the project. Start campaign (to add new batches).
Page 96 of 140
Incident TFS218657
Batch Analytics Model Builder – Equipment  Parameters – after

Description importing Parameters, then saving-closing-reopening Batch Analytics
Model Builder, the ExtInitialCondition type was changed to InitialCondition.
User Scenario Equipment parameters change in BAMBI after import.
Prevention None.
Recovery Change manually after import and reopen.
Incident TFS235558
BA Manager – found error when adding OPC Data Server manually from
Description Batch Analytics Administration application, and then stopping restart BA
Monitoring Service: "Object reference not set to an instance of an object".
Prevention None.
Recovery Delete and re-add the OPC DA server to avoid repeated error messages.
Incident TFS251862
Batch Analytics Model Builder – some issues when remote users do not
Description have access to BA Monitoring Service folder  \BAData\Deployed
Projects.
User Scenario Remote connection to BA Monitoring Service folder.
Prevention None.
In BA Monitoring Service node, add local user BATCHUSER to the

Recovery
Administrators group. Reopen BA Model Builder.
Page 97 of 140
Incident TFS211017
In Batch Analytics, Retrieve Stages do not support pulling stages from

Description
multiple OPC HDA sources
Retrieve Stages only retrieve stages from Primary OPC HDA source. The
following error is received for each affected batch:
“Retrieve Stages Error
User Scenario Unable to locate the BA_STAGE tag associated with one
of configured units.
See the Windows event viewer for more details”
Store all stages in a single historian rather than splitting them across
Prevention
multiple historians.
Recovery Use manually entered stages.
5.6 Connection Handling
Incident TFS259446
Remote BA server – When BA Monitoring Service is shut down (no

Description
connection), the error message says that user is not authorized.
In Remote BA server, when BA Monitoring Service is shutdown, and user

tried to launch Batch analytics Operations information Web Server, this is
the message that appears:
"You are not authorized to view this page. Please
User Scenario contact your System Administrator to grant you access
to <BA Server node name>."
The idea is that the message would say that BA server cannot
communicate to BA Monitoring Service node and specify the BA
Monitoring Service node name for the user to take action accordingly.
Prevention None.
Find BA Monitoring Service node name from BA server configuration, ping

Recovery
it, and notice that it cannot ping the node.
Page 98 of 140
5.7 Independent Domain Controller
Incident TFS384928
System Registration does not correctly report that the system is using an
Description
IDDC.
Ran System Registration Utility and reviewed the content. In the content , it
User Scenario
does not correctly report that the system is using an IDDC.
Prevention None.
Recovery None.
Incident TFS387129
PCInstall of ProfessionalPLUS joining an IDDC network crashes during

Description
Configuring Control Network.
The PCInstall crashes during Configuring Control Network process. A

User Scenario
Faulting application has been logged in the Windows Event logs.
Prevention None.
Recovery Set the DNS to automatic and rerun the pc-install.
Incident TFS390685
IDDC: DVPEHAdministrator is unexpectedly set up to be a member of the

Description
Domain DeltaV Admins group.
The DVPEHAdministrator user should only be in the following groups:

 Domain DeltaV
 Domain DvPEHAdmin
User Scenario
 Domain Admins (no IDDC)
 Domain DeltaV Local Win Admins (w\ IDDC but only on member
stations not on the IDDCs or Backup IDDCs)
Prevention None.
Manually remove the DVPEHAdministrator account from the Domain

Recovery
DeltaV Admins group.
Page 99 of 140
Incident TFS388423
IDDC Set Up App – failed to join 2nd IDDC to domain due to being slightly
Description
out-of-time sync.
Attempt was made to join a second IDDC with a server that was 2 minutes
User Scenario out of sync with the primary domain controller. ErrorNumber: -2146233079
was encountered.
Prevention None.
On the error dialog, press OK to cancel out of the IDDC Set Up App,
launch a Command Promptwindow and manually issue anet time
Recovery
\\<DC_name_or_IP> /set /y command, and then relaunch the IDDC Set Up
App to try again.
Incident TFS392978
IDDC/DUW – if member of domain cannot contact the domain, error 'You

must be an Administrator to run this application' will appear. The error
Description
does not prevent anything, a 'Run-time error -2147023541 (8007054b)
Automation error'.
Upgraded a member of the domain without the machine being connected

User Scenario
to the domain.
Prevention None.
After encountering the error, press OK to close the dialog and abort the
Recovery
DUW. After reestablishing the connection to the domain, restart the DUW.
Incident TFS380689
IDDC: Setup tries to make Administrator (a disabled account with non-

Description
complex/blank password) become the domain admin.
Installing the first IDDC on a fresh OS where the local admin account
User Scenario named “Administrator” is disabled and a new admin account named
“Emerson” was created.
Setup a password for the local Administrator account (even if it is disabled)

Prevention
that meets password complexity requirements.
Page 100 of 140

Incident TFS393042
DUW – when running PCInstall on the first non-ProfessionalPLUS

Description machine and choosing the DevData.cfg file created in prior version, no
workstation names appear in the list to select.
1. Had a running system, with a DevData.cfg file already created (e.g. on

the ProfessionalPLUS' drive D) from the older version
2. Performed a DeltaV Upgrade Wizard (DUW) upgrade of the system. At
the point of running PCInstall on the first non-ProfessionalPLUS
User Scenario
machine, selected the DevData.cfg created with the older version of
DeltaV.
3. Though it allowed to be selected, there was nothing in the Workstation
Names list from which to select.
Recreate DevData.cfg from the current version and proceed PCInstall with
Prevention
that file.
Incident TFS395350
[IDDC] There is a third DNS IP listed in the NIC cards of the upgraded
Description
station even if that third IP is not a DNS Server.
User Scenario Upgraded system from 13.3.1 to 14.3.
Prevention None.
Recovery Manually remove the IP address.
Incident TFS359315
IDDC: Error message “NTSetup Error…Error adding user to

Description 'Domain Admins' group” occurs when creating an IDDC Backup
Domain Controller.
User Scenario None.
Prevention Make sure that the current user is a member of Domain Admins group.
Add user in the Domain Admin group via the Active Directory. Close the
Recovery
dialog box, and the setup will continue.
Page 101 of 140

Incident TFS391543
Description Preferred DNS Addresses of the IDDC PDC are being set incorrectly.
Preferred DNS Addresses of the IDDC PDC are being set incorrectly,
User Scenario because they are pointing to the IDDC PDC NICs. This is because, when
the IDDC PDC was set up, the IDDC BDC had not been created yet.
Prevention None.
After setting up the IDDC BDC, change the preferred DNS addresses of
Recovery
the IDDC PDC to point to the IDDC BDC.
Incident TFS414333
DeltaV groups may not be created on the domain when running IDDC
Description
autorun setup.
After running DVAutorun.exe from DeltaV Media on a machine to be set up

as Domain Controller primary and secondary nodes, selecting “Setup
Independent DeltaV Domain Controller”, and then completing the setup,
none of the DeltaV groups exist in Windows Administrative Tools  Active
Directory Users and Computers.
User Scenario Running IDDC setup on a backup domain controller failed with the
following error:
“CNTSetUp.AddCurrentUserToDomain: Error adding
xxxxxxx (user name) to the Domain DeltaV Admins
group. The local group specified by the groupname
parameter does not exist.”
Prevention None.
Rerun IDDC setup (run DVAutorun.exe, and then select “Setup

Recovery
Independent DeltaV Domain Controller”).
Page 102 of 140

5.8 DeltaV Live
Incident TFS409765
Unexpected behaviors in Graphics Studio when users name, title custom

Description properties, or custom property expanders are the same name as built -in
properties/expanders.
If the user has a Custom Property Expander on a GEM class named

"Geometry" or "Visibility", or any other expander that is collapsed by
default, those Custom Property Expanders would also be collapsed by
User Scenario default.
In general, GS tries to manipulate custom properties and custom property
expanders as if they were their built-in counterparts with the same display
name. This can result in things being hidden, etc.
Prevention None.
As a work-around, perform one of the following:

 Do not use the names "Geometry" or "Visibility" or "GEM Information" as
Recovery custom property expander names/titles.
Or
 Click the expander to expand it.
Incident TFS405123
DeltaV Live Diagnostics on some workstations does not show all DeltaV
Description
Live-enabled workstations.
Users may encounter that DeltaV Live Diagnostics running on different

User Scenario
workstations in the same system show different data.
Prevention None.
Restart the operator workstation not showing up on the other machine’s

Recovery
DeltaV Live Diagnostics.
Incident TFS407066
Description Migrated displays in DeltaV Live are not linked to correct image standards.
After importing displays to Graphics Studio and publishing them, and then
User Scenario migrating the library objects along with the displays, the displays in DeltaV
live are mapping to the wrong standard.
Prevention None.
Recovery Manually link to the correct standards.
Page 103 of 140

Incident TFS410080
Live – One CefSharp.BrowserS ubprocess gets up to 1.1 GB memory

Description usage (Working set – private) (from ~200 MB three days ago) soaking
PT_OVRVW (static soak)
User Scenario Soak test of graphics migrated from DVOperate
Prevention Do not set the blink rate exceeding exceed 250 ms.
Recovery Restart DeltaV Live.
Incident TFS410200
DL – User cannot change parameters of the EDC block across a zone

Description
when the module name contains "EDC".
Error is encountered when the block type is in the module name (e.g.
User Scenario
“EDC_TEST”).
The issue is caused by decoding of special URL Encoded characters (see

https://www.degraeve.com/reference/urlencoding.php), which means any
module that starts with 08, 09, B1, B2, etc. would have issue on remote
Prevention zones.
The work-around is to avoid naming modules with the special URL
encoded characters.
Recovery None.
Incident TFS403248
DeltaV Live OOB/OH: High Performance GEM (Level-1/2): Right-click pop-

Description
out Context menu (Chart Builder) but overlapped by Hover InfoWindow.
User Scenario High Performance Window overlaps the Chart Builder in DeltaV Live.
Prevention None.
Recovery Wait for about 1 minute for the hover window to disappear.
Page 104 of 140

Incident TFS411188
GS: GEM Instances (Linked and Unlinked) cannot be relinked to GEM

Description Classes directly in the GEM Classes library—the target GEM Class must
be inside a folder.
User Scenario GEM classes cannot be found under <LibraryName>/GEM Classes .
Prevention None.
Move the GEM class to be relinked to, into a folder (and then move it back,
Recovery
if desired).
Incident TFS413151
ACH: Unable to get historical data on DeltaV Live Charts when coming
Description
from ACH historian Virtual Machine.
User Scenario No mappings or trust can be seen in ACH machine.
Prevention None.

1. On ACH node, open PI-System Management Tools (PI-SMT).
2. Under the list of Servers, select 143SV16A (VM template name), right-
click, and then click Remove Server. Click Yes to confirm.
3. Open PI-SDK Utility. Under Tools  KST Cleanup, select all 3 Cleanup
Options. Click Clean button.
Recovery 4. Back in the PI-SMT, select the check box next to the remaining valid
Server. Under the System Management Tools pane  Security 
Mappings and Trusts.
5. Create a new Mapping:
a. Windows Account: Browse for and select the DeltaV group.
b. PI Identity: Browse for and select PI Operators.
c. Click the Create button.
Incident TFS414142
DV Live Admin | Export Database – Export DB does not include

Description
Languages and Themes.
User Scenario Exporting database will not include user-created Language and Themes.
Prevention None.
Perform the export in Graphics Studio, from root folder to export

Recovery
everything, including Languages and Themes.
Page 105 of 140

Incident TFS414317
DeltaV Live: Web Browser PDE's "Can only navigate within itself" Property
Description
Logic is Reversed at Runtime.
If the property is checked, top-navigation is allowed. If it is unchecked, top-

User Scenario
navigation is disabled. It should work the opposite way.
Prevention None.
Recovery None.
Incident TFS414337
Graphics Studio: Error Generating layout when configuring a Custom

Description
Button that is not Button 1 first.
Configuring a custom button on a layout other than button 1, with button 1

User Scenario
still disabled, results in an Error Generating after publishing.
Prevention None.
Recovery Always configure Button 1 first.
Incident TFS414363
Graphics Studio: "Publish all pending" failed for unsaved display with PDE
Description
"Object reference not set to an instance of object.”
“Publish all pending” fails with the following error message:
User Scenario “Failed to Publish. Please make sure necessary

servers are running. Object reference not set to an
instance of object.”
Prevention None.
Recovery Perform "Publish" instead of "Publish all pending".
Page 106 of 140

Incident TFS414576
DVL: Write Value to Destination does not work if the Destination's

Description
expression contains a single term reference.
Write Value to Destination interaction does not work if its Destination's

expression contains a single-term reference such as DLSYS[Dsp.String1]
User Scenario
(String1 is a display variable) or DLSYS[Dsp.Context1] (Context1 is an
input in a contextual display).
Prevention None.
Configure Destination as a multi-term expression such as: DLSYS["" +

Recovery Dsp.String1], which means there should be no quotes around the
Dsp.String1 reference.
Incident TFS414657
DeltaV Live – GS: After “Retrieve to New Active from Drive” on PK

Description Standalone system, Graphics Studio initially shows no publish is required
for DVL files.
After “Retrieve to New Active from Drive” on PK Standalone system, and

User Scenario download of ProfessionalPLUS, Graphics Studio initially shows no publish
is required for DVL files on the ProfessionalPLUS.
Prevention None.
Select “Publish All Pending” for the publish status to slowly start getting
Recovery
updated.
Incident TFS415808
In DeltaV Live Administration, after switching the database, the utility ask s
Description
to "Relaunch" the application although the application is already Open.
The “Switch Database" utility to switch active database will ask to

User Scenario
“Relaunch" the application.
Prevention None.
Recovery Relaunch the application as it is a required action.
Page 107 of 140

Incident TFS416720
After making a change on the named state, DeltaV Live does not
Description
immediately reflect that change.
DeltaV Operate immediately picks up that change. One would expect the
User Scenario
same in DeltaV Live.
Prevention None.
The work-around is to reboot the machine as the DeltaV Live services

Recovery
would have to be restarted to pick up that change.
Incident TFS416919
DeltaV Live: SIS parameter does not resolve in runtime unless the user
Description manually edits the Data Source in Graphics Studio adding suffix specifying
data type (.NUM, .STR).
A user may expect that there is no need to manually add a suffix to each
Data Source in the display after configuring each Data Source using
User Scenario
Graphics Studio browser since the Data Type is already specified in the
Graphics Configuration pane.
Prevention None.
User is required to manually add the Data type by adding suffix to the SIS
Recovery parameter path browsed through Graphics Studio, i.e. adding .NUM or
.STR to parameter path.
Incident TFS416910
DeltaV Live has inconsistent behavior in retrieving history data for

Description
diagnostics parameters.
There is inconsistent data shown in DeltaV Live for history data on DeltaV
User Scenario diagnostics parameters when the History Server Preference is not
specified Graphics Studio.
Prevention None.
Recovery Specify the historian in the History Server Preference.
Page 108 of 140

5.9 Windows 10 or Windows Server 2016 Support
Incident TFS287300
Windows 2016: Privacy configurations are different for the same domain
Description
user account if logged on to domain controller or domain member.
In the ProfessionalPLUS, privacy and security settings was changed for a

certain user after promoting to a domain controller. In the application
station the privacy and security settings for the same user was also
User Scenario changed prior to joining to the domain. After the Application station has
been joined to the domain and rebooted and logged in the domain with the
same user. The privacy and security settings is not inherited from the
domain controller and needs to be tweaked on each node.
Prevention None.
Recovery None.
Incident TFS286120
When a machine is joined as a new member to the Windows Server 2016

Description domain, all the Settings  Privacy configurations get unexpectedly reset
to factory defaults.
The following settings returned to default:

 Settings  Devices  AutoPlay configuration back to factory default
(On).
 Settings  System  Notifications & actions  Turn system icons on
User Scenario or off configuration back to factory default (On).
Windows Store, Edge, Task View pinned to taskbar which were previously
unpinned.
Server Manager's option of "Do not start Server Manager automatically at
logon" back to the factory default (unchecked).
Prevention None.
Recovery None.
Page 109 of 140

5.10 DeltaV Security Hardening
Incident TFS243185
Windows Firewall Rules do not get re-added when using "Reinstall OS"
Description
option in DUW.
Ran DUW going from v13 RC_D to v13 RC_F. Used the "Reinstall OS"
User Scenario option in DUW. When DUW finished it was noticed that all Windows
Firewall rules for DeltaV were never added back after being reimaged.
Prevention None.
User will have to use DSASetup.exe to apply the rules manually.

Or
1. Backup firewall rules on old workstation by running the following the
command line:
netsh advfirewall export
C:\WindowsFirewallSettingsBackup.wfw
2. Turn off firewall profiles on new workstation by running the following on
the command lines:
Netsh advfirewall set AllProfiles state off
Recovery
Netsh advfirewall set CurrentProfile state off
Netsh advfirewall set DomainProfile s tate off
Netsh advfirewall set PrivateProfile state off
Netsh advfirewall set PublicProfile state off
3. Copy backup of firewall rules created in step 1 to the new workstation
and restore firewall rules by running the following on the command line:
netsh advfirewall import [location of firewall rules
backup file xxxx.wfw]
Incident TFS269143
Description IPV6 and Windows Defender are not disabled during DeltaV installation.
User Scenario User installs DeltaV v14.3 on a Windows 10 workstation.
Prevention None.
Manually set the registry key:

1. Run the following from the command line:
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows
Defender\Real-Time Protection" /v
Recovery DisableRealTimeMonitoring /t REG_DWORD /d 1 /F
REG ADD
"HKLM\System\CurrentControlSet\Services\Tcpip6\Parame
ters" /v DisabledComponents /t REG_DWORD /d 0xFF /F
2. Reboot the workstation.
Page 110 of 140

5.11 Secure Open Save Dialog
Incident TFS389697
Custom user cannot export to xml in SAM application. Throws an irrelevant

Description
error.
Error message: "Error Opening output file, assure you have enough disk
User Scenario space or check if the file is open."
When logged as Emerson, you can Export to Xml without any error.
Prevention None
Recovery None
5.12 Cybersecurity
Incident TFS393306
Additional instructions needed for Smart Card configuration and Web

Description
Services and Remote Desktop Services.
With the CIS security hardening, the setting Computer Configuration 

Administrative Templates  Windows Components  Windows Remote
Shell  Allow Remote Shell Access is disabled. This causes Windows
User Scenario 2016 Server Manager to lose the ability to add roles, which is needed to
configure Smart Cards. We need to augment current documentation to
include instructions for temporarily enabling the policy setting, allowing for
Server Roles to be added.
Prevention Temporarily enable the policy setting.
Incident TFS388508
Description Documentation: OPC .NET installer Operating System check is missing.
Requesting additional documentation for OPC .NET RemoteInstaller.

There will not be an Operating System check for 14.3 release. Potentially,
User Scenario
user could install on Windows 7 and Windows Server 2008 without
warning.
Prevention None.
Recovery None.
Page 111 of 140

Incident TFS417035
Smart Card: Unable to install Certification Authority because WS-

Description
Management service cannot process the request.
Users will encounter the following error message when installing the
“Active Directory Certificate Services: Certification Authority” role, which is
needed to add the use of a smart card.
User Scenario “One or more predeployment tasks failed.

The WS-Management service cannot process the request.
The service is configured to not accept any remote
shell requests.”
Prevention None.
Edit group policy setting: Allow Remote Shell Access

1. Launch Group Policy Management Editor.
2. Find Forest: domain name  Domains  domain name  Domain
Controllers  Default Domain Controllers Policy, and then right click it.
3. From the menu, click Edit.
Recovery 4. Go to Computer Configuration  Policies  Administrative Templates:
Policy definitions  Windows Components  Windows Remote Shell
5. On the right, find Allow Remote Shell Access, and then edit the policy
from Disabled to Enabled.
6. Reboot to save the policy.
7. Complete the other steps for smart card setup.
Page 112 of 140

6 Compatibility
Important: Ensure that you have the appropriate hardware before upgrading to DeltaV v14.3.
6.1 Supported Workstation Components and Functionality

The complete list of compatible Dell workstations and servers across different DeltaV versions are available in KBA AK-
1000-0070: Dell and Stratus Machine Compatibility Chart for DeltaV Implementation.
Note: Table in KBA AK-1000-0070: Dell and Stratus Machine Compatibility Chart for DeltaV Implementation
will be updated as information becomes available.
PCs Precision
Servers
(Optiplex) Workstation
Windows 10 IoT
X X
Enterprise 2016 LTSB
Windows Server 2016

X
Standard Embedded
ProfessionalPLUS X X
App Station X X
Professional Station X X X
Operator Station X X X
Maintenance Station X X X
Remote App Station X X
Remote Workstation X X X
DeltaV
InterZone Server X
Functionality
Remote Client Host
X
Server
Simulate X X X
Obsolete Server
Replacement (Virtual X
Host)
Batch Executive Max

15K 30K 30K
DSTs
Page 113 of 140

6.2 DeltaV-Supported Virtualization Hardware and Software
DeltaV v14.3 must use DVS 3.3.1.
For more information, refer to KBA NK-1300-0155: DeltaV Virtualization Planning and Installation Guide.
The complete list of supported virtualization hardware and software across different DeltaV versions are available in the
following KBAs:
 For software: AK-1600-0076: Complementary Software List for DeltaV
 For hardware: NK-1600-0402: Virtualization Hardware Compatibility
6.3 Hardware Compatibility Charts
6.3.1 M-series Hardware
M-series Hardware Controller
Description Part Number Firmware Hardware
MDPlus 12P3439 14.3.0.6984.xr Rev 5.50 or greater
MX 12P4375 14.3.0.6984.xr Rev 7.1 or greater
MQ 12P6381 14.3.0.6984.xr Rev 10.0 or greater
PK100 12P8931 14.3.0.6987.xr Rev 1.01 or greater
DeltaV Controller
Interface for 12P2690 14.3.0.6984.xr Rev 3.20 or greater
PROVOX I/O
DeltaV Controller
Interface for RS3 I/O 12P2740 14.3.0.6984.xr Rev 5.11 or greater
[1]
Page 114 of 140

Analog Out
AO 4-20 mA 12P0683 Rev 2.42 Rev 1.2 or greater
AO 4-20 mA, HART 12P0682 Rev 2.42 Rev 1.0 or greater
AO 4-20 mA, HART

12P2531 Rev 2.53 Rev 1.2 or greater
Series 2
AO 4-20 mA, IS,

HART
AO 4-20 mA, IS 12P1864 Rev 2.01 Rev 0.1 or greater
AO 16 CH, 4-20
HART, Series 2 Plus
AO 4-20 mA, IS
Series 2
Analog In

[7]
AI 4-20 mA, HART 12P0680 Rev2.53 Rev 0.1 or greater
AI 4-20 mA, HART

12P2532 Rev2.53 Rev 1.2 or greater
Series 2
AI 4-20 mA 12P0681 Rev 2.42 Rev 1.1 or greater
AI 1-5 VDC 12P1033 Rev 2.42 Rev 1.1 or greater
AI 4-20 mA, HART, IS 12P1863 Rev 2.40 Rev 0.1 or greater
AI 16 CH 4-20 mA,
HART Series 2
AI 16 CH, 4-20 HART

Series 2 Plus
Page 115 of 140

RTD, Thermocouple, mV, Volt Input
RTD, 8 Ch. 12P1732 Rev 1.14 Rev 0.1 or greater
RTD, 8 Ch., Series 2 12P4174 Rev 1.35 Rev 20.1 or greater
Thermocouple/Millivolt
Input, 8 Ch.
Thermocouple/Millivolt,
8 Ch., Series 2
Isolated Input, 4 Ch.,

Series 2
Multifunction I/O 12P2180 Rev 1.13 Rev 1.1 or greater
Multifunction I/O
Series 2
Pulse Count Input Card

(formerly referred to as Multifunction)
Pulse Count Input 12P2180 Rev 1.13 Rev 1.2 or greater
Pulse Count Input,

Series 2
Page 116 of 140

Discrete In
12P0551 Rev 0.27 or Rev 1 Rev 0.1 or greater

120 VAC 8 CH ISO
12P3902 Rev 2.83 Rev 20 or greater
12P0552 Rev 0.27 or Rev 1.1 Rev 0.1 or greater

120 VAC 8CH DRY
CONTACT
230 VAC ISO 12P0553 Rev 0.27 or Rev 1.1 Rev 0.1 or greater
230 VAC DRY

CONTACT

24 VDC ISO
24 VDC DRY
CONTACT
24V DRY CONTACT,

Series 2
16 CH, IS 12P1866 Rev 1.21 Rev 0.1 or greater
24 VDC 32 CH DRY
CONTACT
24 VDC 32 CH Dry
[2] 12P3270 Rev 2.29 Rev 11.1 or greater
Contact, Series 2
24 VDC 16 Ch. SOE 12P2293 Rev 1.12 Rev 1.3 or greater
24 VDC 16 Ch. SOE

Series 2
24 VDC 16 Ch. SOE

Dry Contact
24 VDC 32 CH Dry
Contact PLUS
Page 117 of 140

Discrete Out
24 VDC HIGH SIDE 12P0555 Rev 0.27 or Rev 1.1 Rev 0.1 or greater
24 VDC, HIGH SIDE,

SERIES 2

120/230 VAC HS

24 VDC ISO

120/230 VAC ISO
4 CH, IS 12P1865 Rev 1.20 Rev 0.1 or greater
24 VDC 32 CH HI
SIDE
24 VDC 32 CH HI
SIDE, SERIES 2
24 VDC 32 CH HI
SIDE PLUS
Zone 1 I/O
Analog Input/Output,
4-20 mA HART
Discrete Input/Output 12P3154 Rev 1.16 Rev 0.1 or greater
Serial
Serial, 2 Ports,
RS232/RS485
Serial, 2 Ports,
RS232/RS485, Series 12P2506 Rev 1.55 Rev 1.1 or greater
2
Page 118 of 140

FOUNDATION™ Fieldbus
Fieldbus H1 Card 12P1064 Rev 1.80 Rev 0.1 or greater
Fieldbus H1 2 Ports
Card Series 2
Fieldbus H1 4 Ports
Card Series 2
Fieldbus Devices and Ancillary Equipment
See the EasyDeltaV website for a current list of compatible devices with DeltaV.
http://www2.emersonprocess.com/en-US/brands/delt av/alliance/Pages/ vendors.aspx
Other Buses
AS-i Bus Card 12P2047 Rev 1.24 Rev 1.1 or greater
AS-i Bus Card Series

2
Profibus DP Card 12P2062 Rev 1.22 Rev 1.1 or greater
Profibus DP Series 2 12P2830 Rev 2.71 Rev 10.1 or greater
Profibus DP Series 2
Plus
[3]
DeviceNet card 12P2514 Rev 2.14 Rev 1.1 or greater
DeviceNet card Less than Rev 11.3

12P2843 Rev 3.13
Series 2 Rev 11.3 or greater
Remote I/O Scanners
Zone I CPU 12P3153 14.3.0.6984.xr Rev 6.6 or greater
Zone 2 RIU 12P2890 14.3.0.6984.xr Rev 4.11 or greater
Page 119 of 140

6.3.2 S-series Hardware
S-series Hardware Controller
SDPlus 12P4686 14.3.0.6984.xr Rev 45.61 or greater
SX 12P4688 14.3.0.6984.xr Rev 47.1 or greater
SQ 12P6383 14.3.0.6984.xr Rev 50.0 or greater
SZ 12P6190 14.3.0.6985.xr Rev 1.03 or greater
DeltaV Controller
Interface for Provox 12P5808 14.3.0.6984.xr Rev 3.21 or greater
I/O
CHARMs I/O Card
CIOC1 Card 12P4987 14.3.0.6986.xr Rev 8.00 or greater
CIOC2 Card 12P8775 14.3.0.6984.xr Rev 1.01 or greater
Page 120 of 140

CHARMs
AI 4-20 mA HART 12P4628 1.65 Rev 1.00 or greater
AO 4-20 mA HART 12P4629 1.65 Rev 1.00 or greater
DI 24 VDC Low-Side
12P4632 1.60 Rev 1.00 or greater
(DI Dry)
DI NAMUR 12P4626 1.60 Rev 1.00 or greater
DO 24 VDC Isolated 12P4633 1.73 Rev 1.00 or greater
DO 24 VDC High-
Side
RTD/Resistance Input 12P4630 1.76 Rev 1.00 or greater
Thermocouple/mV
Input
DO VAC Isolated 12P5347 1.71 Rev 1.00 or greater
AI 0-10 VDC Isolated 12P5348 1.57 Rev 1.00 or greater
DO 100 mA Energy
Limited
DI 24 VDC Isolated 12P5344 1.60 Rev 1.00 or greater
DI 120 VAC Isolated 12P5345 1.59 Rev 1.00 or greater
DI 120 VAC Isolated

PLUS
DI 230 VAC Isolated 12P5346 1.59 Rev 1.00 or greater
24VDC Power Charm 12P5957 1.59 Rev 1.01 or greater
Page 121 of 140

IS CHARMs
IS AI HART 12P5542 1.76 Rev 1.03 or greater
IS AO HART 12P5543 1.80 Rev 1.03 or greater
IS DI NAMUR 12P5544 1.64 Rev 1.03 or greater
IS DO 45 mA 12P5545 1.75 Rev 1.03 or greater
IS Thermocouple/mV
Input
IS RTD/Resistance
Input
Wireless I/O Card
WIOC Card 12P5030 14.3.0.6984.xr Rev 8.2 or greater
6.3.3 S-series Traditional I/O
Analog Out
AO 4-20 mA, HART 12P4704 2.53 Rev 41.1 or greater
AO 16 CH 4-20 HART
PLUS
Analog In
AI 4-20 HART 12P4705 2.52 Rev 41.1 or greater
AI 16 CH, 4-20 HART 12P4706 2.35 Rev 41.1 or greater
AI 16 CH, 4-20 HART

Plus
Page 122 of 140

RTD, Thermocouple, mV, Volt Input
Thermocouple/Millivolt
Input 8 CH
RTD 8 CH 12P4708 1.34 Rev 41.1 or greater
Isolated Input 4 Ch. 12P4709 2.36 Rev 41.1 or greater
Discrete In
24VDC Dry Contact 12P4692 2.38 Rev 41.1 or greater
24VDC Isolated 12P4696 2.83 Rev 41.1 or greater
120VAC Isolated 12P4697 2.83 Rev 41.1 or greater
120VAC Dry Contact 12P4698 2.83 Rev 41.1 or greater
24VDC 32 CH Dry
Contact Plus
24 VDC 32 CH Dry
Contact
Discrete Out
24 VDC High Side 12P4693 2.38 Rev 41.1 or greater
24VDC Isolated 12P4699 2.83 Rev 41.1 or greater
120/230 VAC Isolated 12P4700 2.83 Rev 41.1 or greater
120/230 VAC High

Side
24 VDC 32 CH High
Side
24 VDC 32 CH High
Side PLUS
Page 123 of 140

S-series Ethernet I/O Card
Ethernet I/O Card

[4] 12P7256 14.3.0.6984.xr Rev 1.06 or greater
(EIOC)
Serial
Serial, 2 Ports,
RS232/RS485
FOUNDATION™ Fieldbus
Fieldbus H1 Card 12P4711 4.91 Rev 41.1 or greater
Fieldbus H1 4 Port
PLUS Card
Other Buses
DeviceNet Card SSR

version
Profibus DP Card 12P4691 1.50 Rev 41.1 or greater
AS-I Bus Card 12P4712 1.24 Rev 41.1 or greater
Pulse Count Input
Pulse Count Input 12P4703 3.31 Rev 41.1 or greater
Remote I/O Scanners
Zone I CPU 12P3153 14.3.0.6984.xr Rev 6.6 or greater
Page 124 of 140

DeltaV Controller Interface for PROVOX I/O Compatibility
Model Number Description SW Rev.
CL6721 Discrete Input/Output Card P1.2, P1.3, P1.4, P1.5
P1.2, P1.3, P1.4, P1.5,

CL6821 Analog Input/Output Card
P1.5.1, P1.5.2
CL6824 Analog Input P1.0, P1.0.1
CL6825 Smart Input P2.0.2, P2.1, P2.2

[5]
CL6827 Smart Input P3.0, P3.1, P3.2
CL6826 Smart Output P2.0.2, P2.1, P2.2
CL6822 Smart Transmitter Interface P1.1.2, P2.0, P2.1

[6]
CL6828 Smart Device Output P3.0, P3.1, P3.2, P3.3
External Interface Card with

CL6921 P1.1, P1.3
Weigh scale software
CL6921 External Interface Card Not supported
Distributed Serial Buffer

CP6601 P2.1, P2.2
Interface Card
DM6361, DM6362, DM6363 Distributed DI cards All versions
DM6371, DM6372, DM6373 Distributed PCI cards All versions
DM6461, DM6462, DM6463 Distributed DO cards All versions
DM6431 Distributed TPO cards All versions
DM6331 Distributed RTD cards All versions
DM6351, DM6352, DM6353, Distributed Thermocouple

All versions
DM6354, DM6355 cards
DM6341 Distributed mV Cards All versions
DM6311, DM6312, DM6321, Distributed Analog Input

All versions
DM6322 Cards
Distributed Analog Outputs

DM6411, DM6421 All versions
Cards
DM6381 Distributed Weigh scale card All versions
Page 125 of 140

DeltaV Controller Interface for RS3 I/O Compatibility
Model Number Description SW Rev FW Rev.
6600FAC302 Analog FIC cards 1.6, 3.8, 4.7, 4.8 1.0, 2.1
6600FAC402 Analog FIC HART cards 4.8 2.1
6000FTC102 Analog FIC TC/RTD Cards 2.11, 3.1 1.8
6600FIM001 (Low side)

MDIO FIM Cards 3.0, 3.1, 3.2, 3.4, 4.0 1.1, 6.6, 6.7
6600FIM002 (High side)
6000FCC001 Contact FIC cards Not applicable 2.0, 3.1
6600FPC202 Pulse FIC cards Not applicable 2.4, 2.7
6600FIM100 MAI-16 FIM card 2.2, 2.4, 3.4 1.1, 4.0, 4.1, 5.0
6600FIM300 MAI-32 FIM card 3.4 5.1
6600FIM200 MAO-16 FIM card 2.2, 2.6, 3.4 4.1, 5.1
Footnotes
[1] The DeltaV Controller Interface for RS3 I/O is only supported with M Series Controllers.
[2] Can be used to replace the same type of card that is not a series 2 card. However, functionality of card is limited to th e
functionality of the non-series 2 card it is replacing.
[3] DeviceNet devices must support polling messaging in order to communicate with DeltaV DeviceNet card.
[4] Ethernet I/O Card (EIOC) is supported only on DeltaV version 13.3 and future releases.
[5] Smart input card P3.1 has k nown issues in both PROVOX and DeltaV Controller Interface for PROVOX I/O.
[6] Smart output card P3.2 has k nown issues in both PROVOX and DeltaV Controller Interface for PROVOX I/O.
[7] Please refer to KBA AUS1-132-010807173536: Revision to Bulletin: Safety Related Issue - Channel Circuitry of Analog
Input with Hart Cards may be Damaged By Transient Voltages in excess of 1000 Volts. for Hardware revisions that may
have safety recall information.
Page 126 of 140

7 DeltaV SIS
This section contains information on the DeltaV hardware and software used in DeltaV SIS.
7.1 Installation and Migration Notes for DeltaV SIS in v14.3
7.1.1 Pre-Upgrade Considerations

Diagnostics cannot display runtime information related to the DeltaV SIS network during an online upgrade while the
ProfessionalPLUS workstation is being upgraded.
7.2 Resolved Issues in DeltaV SIS in v14.3

Issues resolved in lower versions including respective hotfixes are already part of DeltaV v13.3.1. Only the resolved
issues in v13.3.1 that may not be documented anywhere else are listed below.
Incident TFS294722
Redundant CSLS report “Partner Comparison Error” after performing a

Description
change download.
7.3 Tips for DeltaV SIS in v14.3

If a CSLS cannot be detected in the unassigned folder in DeltaV Explorer, address this issue by referring to the v13.3.1
Books Online topic Reset Safety Network Ports and follow the steps detailed therein.
7.4 Known issues in DeltaV SIS in v14.3
7.4.1 SIS IO Simulation
Incident TFS382974
Device Signal Simulator: SZ Controllers and CSLS disappear in Controller

Description Selector after downloading CSLS. Needs to do a refresh to show SZ and
CSLS.
User Scenario
Prevention None.
Recovery Refresh controllers or F5.
Page 127 of 140

Incident TFS385109
DSS – after Loading Simulate data, right pane does not show multiple
Description
module references.
User Scenario
Prevention None.
Recovery Click other nodes in the left pane and back.
7.4.2 Device Centric SIS Alarming
Incident TFS362809
Alarm groups are not showing in alarm banner/list when using Simulated
Description
SLS.
With an SIS module assigned to Simulated SLS (commissioned on

ProfessionalPLUS or Application station), saved, and downloaded. And
User Scenario with its function blocks assigned to alarm groups and alarms added. When
the associated alarms are triggered the alarm, groups will not show up in
the alarm banner and alarm list of DeltaV Operate.
Prevention None
Recovery None
7.5 Compatibility Charts for DeltaV SIS v14.3
SIS
Logic Solver (SLS

12P3162 3.3.4.2.cr Rev 0.1 or greater
1508)
SIS Net Repeater 12P3232 2.1.4.2.cr Rev 0.1 or greater
CHARMs Smart Logic

Solver
SZ Controller 12P6190 14.3.0.6985.xr Rev 1.03 or greater
Local Safety Network

Bridge
LSNG 12P7254 1.1.2.1.cr Rev 1.06 or greater
Page 128 of 140

DeltaV SIS Smart Switches
EMERSON Product EMERSON Module EMERSON Part EMERSON VE Order

Name Number Number Number
LSN20-6TX2TX KJ1614X1-BA1 12P7104X012 SS6041F01C1
LSN20-6TX2TX-ES KJ1614X1-BA2 12P7104X022 SS6041F01C2
LSN20-6TX2MM KJ1614X1-BB1 12P7105X012 SS6041F05C1
LSN20-6TX2MM-ES KJ1614X1-BB2 12P7105X022 SS6041F05C2
LSN20-6TX2SM KJ1614X1-B C1 12P7106X012 SS6041F06C1
LSN20-6TX2SM-ES KJ1614X1-B C2 12P7106X022 SS6041F06C2
SRM100 Base SS6048R2P1 (US

KJ1614X1-CA1 12P7107X012
Module-RP Power cord = P1)
Note: SZ controllers are required to be used with CHARMs Smart Logic Solvers.
Logic Solver (LS) CHARMS
LS VDC HART DTA

CHARM
LS DO 24V DTA
CHARM
LS DO 24V ETA
CHARM
LS RTD/Resistance
CHARM
LS DI 24 VDC Low-
Side CHARM
LS IS
RTD/Resistance 12P6555 1.96 Rev 1.03 or greater
CHARM
LS Thermocouple/MV
CHARM
LS IS
Thermocouple/mV 12P6551 1.99 Rev 1.03
CHARM
LS IS DI NAMUR
12P6547 1.12 Not applicable
CHARM
Page 129 of 140

Logic Solver (LS) CHARMS
LS IS AI 4-20 HART
CHARM
LS AI 4-20 mA HART
CHARM
LS DI NAMUR
CHARM
LS DI 24 VDC
Isolated CHARM
LS DI 120 VAC
Isolated CHARM
LS DI 120 VAC
Isolated CHARM 12P9370 1.14 Rev 1.01 or greater
PLUS
LS DI 230 VAC
Isolated CHARM
LS AI 0-10 VDC
Isolated CHARM
LS 24 VDC Power
CHARM
Page 130 of 140

8 Obtaining the Latest Information
Knowledge Base Articles (KBAs) are frequently added and updated on the Guardian Support site:
https://guardian.emerson.com
Note: Visit this website frequently to check for an updated version of this document before proceeding with a
DeltaV upgrade or installation.
DeltaV KBAs, such as this one, are available only to registered DeltaV Guardian Support customers.
9 Registering your DeltaV System with Emerson

Important: Registration of your DeltaV system is required to access the Guardian Support website and
Technical Support. Registering your system also allows Emerson Process Management to provide critical
information to you in a timely manner.
Access to the Knowledge Base Articles through the support site (https://guardian.emerson.com) is available only if your
system has been registered and you have purchased Guardian Support.
You may submit the registration file to Emerson Process Management by uploading to the website or by making a local
copy to send as an email attachment.
To register your system, perform the following steps:
1. Install and configure your DeltaV hardware and software.
TM
2. Run Start  DeltaV  Installation  SureService Registration. The utility gathers identification data from
connected DeltaV Workstations, Controllers and I/O, types. This data may include specifications, functionalities
enabled, and the License information entered while configuring your software.
TM
Important: If additional nodes were added or new functions enabled, please re-run the SureService
Registration to collect the new data.
3. An encrypted report containing information about your system will be sent to Emerson Process Management
using an internet connection. However, if an internet connection is not available, the registration utility will ask for
email connection information.
If the utility is unable to send the file successfully, save the encrypted system information to a file, and then upload it to
Guardian (https://guardian.emerson.com) or email it as an attachment to Emailregistration@emerson.com.
Page 131 of 140

10 Product Technical Support
The Emerson Process Management, Process Systems Group (Emerson) provides engineering services and consultation
for all Emerson products. Emerson performs extensive tests and interoperability checks on all standard products. Support
of third-party hardware, software, and networking solutions, whether off-the-shelf or custom developed, is not a standard
provision of Emerson Guardian Support service. The use of third-party products (including hardware, software, and
networking solutions) is undertaken at the user's risk. Emerson does not guarantee the interoperability of third-party
products.
Emerson Technical Support provides reasonable efforts to support the Emerson product content. However, if Emerson
Technical Support suspects that a third-party product may be causing an issue, the user may be required to comply with a
standard supported configuration and products before further troubleshooting can proceed. Note that custom scripting
within the operator interface application is considered to be a custom integrated solution.
In addition to the Current Product software release, technical phone support and remote diagnostic services will be
provided for Active Product and Supported Product releases of software, with the understanding that it may become
necessary to upgrade to the current release in order to satisfy some requests for assistance. Technical phone support and
remote diagnostic services are available with enrollment in Guardian Support service or on-demand at current rates.
Conventional Software Support (CSS) is the time period that Emerson offers software hotfix support for a specific lifecycle
version of the DeltaV software. The CSS period is five years, beginning with the release of Service Pack 1 for the major
TM
version. Refer to the DeltaV Software Life Cycle Status Listing sheet for details. This change in policy is effective with
DeltaV v11 and forward.
Emerson recommends that all DeltaV customers subscribe to Guardian Support. For information regarding Guardian
Support, you may visit http://www.Emerson.com/GuardianSupport or you may contact your local representative. Please
visit our website at http://www3.emersonprocess.com/systems/reach to find the representative nearest you.
Expert Technical Phone Support 24x7: Emerson will provide product technical phone support 7 days/week , 24 hours/day,
365 days/year through its Global Service Center (GSC). This support includes assistance for questions or concerns
regarding how the product works and what it will do, product issue resolution, locating technical information and advice
that can be based on non-application-specific product and system knowledge.
Contact information for the Emerson Global Service Center can be found at http://www2.emersonprocess.com/en-
us/brands/sureservice/pages/technicalsupport.aspx .
At the customer’s request, Emerson’s Technical Specialists will establish a secure connection to the customer’s
equipment to perform online troubleshooting.
Emerson supports WebEx connections to DeltaV computers for remote troubleshooting via the Internet. The current
version of the WebEx client may be obtained from WebEx. In most cases, DeltaV computers do not have direct access to
the Internet. In this situation a WebEx session may be established on an intermediary computer that has network
connectivity to both the Internet and the DeltaV computer. A WebEx meeting is established on the intermediary computer.
Then connection from the intermediary computer to the DeltaV computer can be established.
Beginning in Windows Server 2008, remote connections to the DeltaV computer require Del taV Remote Client sessions to
be able to use Remote Desktop software (mstsc). For further details, see KBA NK-1100-1110: Remote Desk top
Connections to DeltaV Systems Installed on Windows Server 2008 and Windows Server 2016.
Note: This KBA will be reviewed again for Windows Server 2016 and Windows 10 once the required
information becomes available.
For DeltaV computers that do not have DeltaV Remote Client sessions configured, the Remote Assistance application
may be used to connect the intermediary computer to the DeltaV computer. For instructions on setting up Remote
Assistance on the DeltaV machine, see KBA NK-1100-0133: Setting Up Remote Desk top and Remote Assistance Modem
Connections for DeltaV Systems Running Windows Server 2008 and Windows 7 (see Section A, subsection I, steps 1–
5 to enable services required to use Remote Assistance and see Section B, subsections I, II, and III for instructions on
installing Remote Assistance on the host (DeltaV) computer, creating a Remote Assistance Invitation, and connecting to
the host computer from a remote computer).
Page 132 of 140

11 Controller Performance and Loading
A tool for estimating controller loading is included on DeltaV v14.3 DVD 1. To install it, run
_Support\Tools\LoadEstimator\Setup.exe.
DeltaV v14.3 supports DeltaV Load Estimator version 3.3. The loading estimation tool estimates controller loading based
on configuration parameters that you supply. The estimated results for batch configurations may not be as accurate as
those for continuous systems because batch configurations have a greater variability. However, the loading tool will help
to predict how many controllers are needed to implement a configuration.
Controller free time should be at the minimum 20%. For controllers communicating with CIOC, the recommended
minimum controller free time should be 28%. Maintaining the free time above this level ensures overhead to handle plant
upsets, alarm bursts, and so forth.
Controller recommended free memory is no less than 10% of the total user memory. The minimum FREMEM or
Performance Index >=2 per controller type are as follows:
 MDPlus and SDPlus – 4.8 MB
 MQ and SQ – 4.8 MB
 MX and SX – 9.6 MB
 PK – 70 MB
The DeltaV Installation DVDs contain additional information about DeltaV. Look through the DVD folders listed in the
following section for additional support documentation.
Page 133 of 140

12 Supporting Applications and Documentation
12.1 \DV_Extras (found on DVD 1)
 Batch Analytics (\DV_Extras\Batch Analytics)
Batch Analytics provides online decision support to batch operations, predicts product quality, detects process
faults while providing the reasons for deviation, thus allowing the operator the ability to take action in real time.
The end results are batch-to-batch, variation is minimized, process understanding is increased, and lost and
reworked batches are minimized.
 Batch Historian Server (\DV_Extras\BH_Server)
Refer to Batch Historian Installation topic for more information. This application is used to store data from the
Batch Executive and from the DeltaV Event Chronicle into an SQL database.
 Campaign Manager Operator Interface (\DV_Extras\Campaign Manager Operator Interface)
Campaign Manager is a tightly integrated component of the DeltaV Batch product suite and provides an easy -to-
use interface for creating, modifying, and executing campaigns.
In order to ensure proper and complete installation of Campaign Manager Operator Interface, the DeltaV software
should already be installed on the workstation. The Batch Executive and Campaign Manager servers must be
running for the Campaign Manager Operator Interface to be operable.
 DeltaV Reporter (\DV_Extras\DeltaVReporter)
DeltaV Reporter is a Microsoft Excel Add-in that allows data from the Continuous Historian and Event Chronicle to
be read into the Excel spreadsheet for further analysis and/or the creation of reports.
DeltaV Reporter can be installed on a non-DeltaV node with, Office 2010 SP1, or Office 2013 SP1 Professional
Plus (all 32-bit).
There are two Reporter installers:
o Setup.exe – installs either Office 2013 SP1, Office 2010 SP1, or Office 2007 SP2 depending on the Microsoft
Office version installed
o DeltaVReporterSetup.Office2003.msi – installs the Office 2003 SP3 version
 EntechToolKit (\DV_Extras\EntechToolkit)
The EnTech Toolkit is proven technology for tackling the most difficult control loop performance problems. Now
available as a standard DeltaV product, the EnTech Toolkit is available as an add-on license for DeltaV InSight
v14.3, and as a standalone product that can be used on legacy DeltaV systems and non-DeltaV systems.
 HistoryAnalysi s (\DV_Extras\HistoryAnalysis)
History Analysis provides remote viewing and analysis of DeltaV historical data in a Web browser. The History
Analysis server has access to all batch, continuous, and event data in a DeltaV system. History Analysis enables
users to easily search for and find historical data and identify relationships and correlations in this data by
providing data comparison and analysis capability.
 IDDC (\DV_Extras\IDDC)
Independent DeltaV Domain Controller provides an option to install the domain controller functionality in different
servers than the ProfessionalPLUS (as the primary domain controller) or the Application Station (as a backup
domain controller). This media is a free-standing installer is available to configure the server machine to be an
Independent DeltaV Domain Controller. This installer does not add any DeltaV application to the server machine,
but instead, it sets up any server machine running Windows Server 2016 OS with the expected IP addresses,
server hardening, user group settings, NTP and DNS settings as expected to support Active Directory for Del taV
systems.
Page 134 of 140

 OPC .NET Remote (\DV_Extras\OPC .NET Remote)
OPC .NET, formerly known as OPC Express Interface (OPC.Xi), is a client -server architecture based on the latest
Microsoft communications technology that provides secure and robust real-time and historical data transfer
between OPC .NET clients and servers regardless of where the clients and servers reside in your network
architecture.
 OPC Mirror (\DV_Extras\OPCMirror)
OPC Mirror connects OPC servers on multiple control systems and enables two-way data traffic from one system
to another. This linkage can be between DeltaV OPC servers, DeltaV and PROVOX servers, or several other
OPC server combinations. Any data item that an OPC server accepts when adding items is also acceptable in
OPC Mirror.
 OPC Remote (\DV_Extras\OPCRemote)
This application is required for establishing a client connection, remote to DeltaV OPC Server. An OPC client
should be able to connect to DeltaV OPC server remotely after the OPC Remote is installed on the client
machine.
 Secure SOA Server (\DV_Extras\Secure SOA Server)
DeltaV software uses Services Oriented Architecture (SOA) web services to provide access to DeltaV
functionality, such as Campaign Manager and Recipe Exchange, from client applications outside of the DeltaV
system. The web services are built with the Windows Communication Foundation (WCF) programming
framework. Use the web services to integrate Enterprise Resource Planning (ERP) systems with the process
control system in conjunction with Manufacturing Execution Systems (MES).
The web services are Recipe Exchange, Campaign Manager, Mynah Integration, and Monitor. The Monitor
service is used internally and has no interface. The Mynah Integration service exists solely to support the Mynah
Mimic application. You cannot write applications that access this service.
 Soft Phase Templates (\DV_Extras\SoftPhaseTemplates)
This application includes the templates and command files that are needed to develop External Phases, to be run
as executables on a workstation instead of within a controller.
 System Registration (\DV_Extras\System Registration)
DeltaV System Registration utility allows collection of information from non-DeltaV nodes. You can view and print
the report before sending the report to Emerson. All information is encrypted when sent.
 VIMNet Explorer (\DV_Extras\VIMNetExplorer)
The VIMNet Explorer utility is used to configure the plant Ethernet network. Graphical, drag-and-drop functionality
makes setting up the plant Ethernet network quick and easy.
VIMNet Explorer is integrated with DeltaV Explorer to make setup of the EIOC easy and intuitive.
 WebServices (\DV_Extras\WebServices)
The History Web Service, included in DeltaV Web Services, provides a set of web methods that client applications
can use to interact with the DeltaV Batch Historian.
DeltaV Web Services no longer contain the Campaign Manager Web Service (CMWS). This is now an SOA web
service which is installed with DeltaV. It is enabled on an application station from DeltaV Explorer and will start
when the application station is downloaded.
Page 135 of 140

12.2 \_Support (found on DVD 1)
This folder contains DeltaV add-ons, support files, and drivers needed for DeltaV-supported hardware and software, in
addition to the following:
 Tools (Support\Tools)
o Batch Analytics Process Data Export
o Load Estimator
o OPC Test Clients
12.3 Documentation Library DVD

This DVD contains the following electronic books in PDF format:
Documentation Library DVD
Book Part Number
Fieldbus Installation.pdf D800003X212
Getting Started.pdf D800002X192
M-Series Hardware.pdf D800001X262
S-Series Hardware Install.pdf D800041X082
S-Series Hardware Reference.pdf D800040X082
SIS Install.pdf D800025X102
SIS CHARMs Hardware Installation.pdf D800056X052
SIS CHARMs Hardware Reference.pdf D800057X052
DeltaV Power and Grounding.pdf D800118X022
Independent_DeltaV_Domain_Controller.pdf D800120X012
P-series_Hardware_Reference.pdf D800121X012
Standalone_DeltaV_PK_Controller. pdf D800122X012
Note: These documents are also available in DeltaV Books Online.
This DVD also contains following folders:

 ATEX Instruction Sheets
 Engineering Documents
 EU Declarations of Conformity
Page 136 of 140

13 Media Pack Information
The installation media for DeltaV v14.3 can be downloaded from the Guardian website. On the Support tab, click
Installation Media, and then in the Software Version field, select DeltaV v14.3.
13.1 DeltaV v14.3 Media Set

This section has the complete information on the latest media pack available for DeltaV v14.3. Emerson is offering various
options for a new DeltaV v14.3 installation and for the existing 14.3 customers that are required to perform the Feature
Pack 1 mandatory upgrade. For convenience of future workstation installations, existing 14.3 customers will be provided
with full installation media with Feature Pack 1 included, in addition to the Feature Pack 1 upgrade media.
Important: DeltaV Live, DeltaV Smart Commissioning, and Distributed Charms are included in DeltaV
v14.3.0.6984 Feature Pack 1 and on the full installation media.
13.1.1 DeltaV v14.3 Feature Pack 1 DVD Media Shipments

This installation media is for full installation of DeltaV v14.3.0.6984 which includes the DeltaV Live, DeltaV Smart
Commissioning, and Distributed Charms.
Description Volume Label ISO File Name
DVD ASSY, DELTAV V14.3 FP1

12P9824B_DVD1 DeltaV14.3_DVD1_12P 9824B_DeltaV.iso
ENGLISH DISC 1
DVD ASSY, DELTAV V14.3 ACH 12P9827A DeltaV14.3_DVD2_12P 9827A_A CH.iso
DVD ASSY, SQL SERVER 2016 STD

12P9830A DeltaV14.3_DVD3_12P 9830A_SQL.iso
X64
DVD ASSY, DELTAV V14.3 ENGLISH

12P9833B DeltaV14.3_DVD4_12P 9833B_DOC.iso
DOC LIBRARY
DVD ASSY, AMS DEV MGR V14.0

10P6020E011 DeltaV14.3_DVD5_10P 6020E011_AMS 1.iso
DISC 1
DVD ASSY, AMS DEV MGR V14.0

10P6020E021 DeltaV14.3_DVD6_10P 6020E021_AMS 2.iso
DISC 2
Page 137 of 140

13.1.2 DeltaV v14.3 Feature Pack 1 Installer Upgrade DVD Media
For the systems installed with the DeltaV v14.3.0.6843 which is the previous ly released build, it is mandatory to apply the
Feature Pack 1. DeltaV Live, DeltaV Smart Commissioning, and Distributed Charms are installed on these systems only
after applying the Feature Pack 1.
Moreover, this mandatory upgrade is required prior to applying the software updates that will be released in KBA AK-
1700-0081: DeltaV v14.3 Software Updates. After implementing the Feature Pack 1, the software build indicated in the
machine would be DeltaV v14.3.0.6984.

12P9824B_DVD1 DeltaV_14.3_DVD1_12P9824B _DeltaV.iso
DISC 1
DeltaV v14.3 FP1 UPDATE INSTALLER 13P0337A DeltaV_14.3_FP1_13P0337A_DeltaV.iso

12P9833B DeltaV_14.3_DVD4_12P9833B _DOC.iso
DOC LIBRARY
13.1.3 DeltaV v14.3 Feature Pack 1 PK Standalone Engineering USB Media and Virtual Machine
Commissioning, and Distributed Charms for PK Standalone Engineering Station.
The virtual machine PK Standalone Engineering workstation indicated in the following table is also installed with the new
release build, DeltaV v14.3.0.6984.
Description Volume Label ISO/OVA File Name
DELTAV V14.3 PK ENGLISH DISC 1 12P9914B DeltaV_14.3_PKDVD_12P9914B_PK.iso
DELTAV V14.3 ENGLISH DOC

LIBRARY
AMS DEV MGR V14.0 DISC 1 10P6020E011 DeltaV_14.3_DVD5_10P6020E 011_AMS1.iso
PK STANDALONE ENGINEERING
12P9975B 14310ENTPK_12P9975B.OVA
VIRTUAL OVA MASTER MEDIA
13.1.4 DeltaV v14.3 Feature Pack 1 PK Local Panel New USB Media
Commissioning, and Distributed Charms for PK Local Panel.
DELTAV V14.3 LP ENGLISH DISC 1 12P9925B DeltaV_14.3_LPDVD_12P9925B_LP.iso
DELTAV V14.3 ENGLISH DOC

LIBRARY
SQL SERVER 2016 STD X64 12P9830A DeltaV_14.3_DVD3_12P9830A _SQL.iso
Page 138 of 140

13.1.5 DeltaV v14.3 Feature Pack 1 PK Standalone Engineering Upgrade USB Media and Virtual Machine
For the PK Standalone Engineering Station installed with the DeltaV v14.3.0.6843 which is the previ ously released build, it
is mandatory to apply this Feature Pack 1. DeltaV Live, DeltaV Smart Commissioning and Distributed Charms are
installed on these machines only after applying the Feature Pack 1.
Moreover, this mandatory upgrade is required prior applying the software updates that will be released in KBA AK-1700-
0081: DeltaV v14.3 Software Updates. After implementing the Feature Pack 1, the software build indicated in the machine
would be DeltaV v14.3.0.6984.
The virtual machine PK Standalone Engineering workstation indicated in the following table is already installed with the
new release build, DeltaV v14.3.0.6984.
Description Volume Label ISO/OVA File Name
DELTAV V14.3 FP1 Installer

13P0338A DeltaV143_FP1PKStandalone_13P0338A _PKStandalone.iso
for PK Standalone and LP
DELTAV V14.3 PK ENGLISH

12P9914B DeltaV_14.3_PKDVD_12P9914B_PK.iso
DISC 1
PK STANDALONE
ENGINEERING VIRTUAL 12P9975B 14310ENTPK_12P9975B.OVA
OVA
DELTAV V14.3 ENGLISH

DOC LIBRARY
13.1.6 DeltaV v14.3 Feature Pack 1 PK Local Panel Upgrade USB Media
For the PK Local Panel installed with the DeltaV v14.3.0.6843 whic h is the previously released build, it is mandatory to
apply the Feature Pack 1. DeltaV Live, DeltaV Smart Commissioning, and Distributed Charms are installed on these
systems only after applying the Feature Pack 1.
Moreover, this mandatory upgrade is required prior to applying the software updates that will be released in KBA AK-
1700-0081: DeltaV v14.3 Software Updates. After implementing the Feature Pack 1, the software build indicated in the
machine would be DeltaV v14.3.0.6984.
DELTAV V14.3 FP1

Installer for PK Standalone 13P0338A DeltaV143_FP1PKStandalone_13P0338A _PKStandalone.iso
and LP
DELTAV V14.3 LP
12P9925B DeltaV_14.3_LPDVD_12P9925B_LP.iso
ENGLISH DISC 1
SQL SERVER 2016 STD

12P9830A DeltaV_14.3_DVD3_12P9830A _SQL.iso
X64
DELTAV V14.3 ENGLISH

DOC LIBRARY
Page 139 of 140

Contact Information
Services are delivered through our global services network. To contact your Emerson local service provider, click Contact
Us. To contact the Global Service Center, click Technical Support.
Complete Article Revision History:

Revision/Publish Description of Revision
20 Dec 2018 Modified to include details about Feature Pack 1, correct Hardware Compatibility Charts,
and update Known Issues section.
04 Oct 2018 Removed the tentative-release-date information for DeltaV Live
25 Sep 2018 Added support status for MD Plus controller in Section 1.3.2. Deleted the minimum
password length under Section 1.2.8 Workstation Requirements.
11 Sep 2018 Added DeltaV v14.3 Media Set Information in Section 13.1. Added Known Issues in Section
5.
25 Jun 2018 Added more information for Configuration Analysis under Section 3.9
13 Jun 2018 Added Migration Path from v13.3 in Section 1.1.1 and MQ controller in Section 2.2 Controller
Support. Added Notes on DeltaV Live and Smart Commissioning release date.
12 Jun 2018 Original Release of Article
©Emerson Automation Solutions 2009-2018. All rights reserved. For Emerson Automation Solutions trademarks and service marks, click this link to
see trademarks. All other marks are properties of their respective owners. The contents of this publication are presented for informational p urposes
only, and while every effort has been made to ensure their accuracy, they are not to be construed as warrantees or guarantees, express or implied,
regarding the products or services described herein or their use or applicability. All sales are governed by our terms and co nditions, which are
available on request. We reserve the right to modify or improve the design or specification of such products at any time without notice.
View Emerson Products and Services: Click This Link
Page 140 of 140

AK-1700-0079 DeltaV v14.3 Release Notes PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

AK-1700-0079 DeltaV v14.3 Release Notes PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Knowledge Base Articles

DeltaV v14.3 Release Notes

Article ID: AK-1700-0079

Recent Article Revision History:

1.1 Read Me First

1.1.1 DeltaV Migration Paths

v1.x Contact Emerson Process Management Global Service Center

v2.x Contact Emerson Process Management Global Service Center

v3.x Contact Emerson Process Management Global Service Center

v4.x Contact Emerson Process Management Global Service Center

(A) Upgrade to 10.3.1, then 12.3.1, and then 14.3*

v9.3 Apply SP1, then upgrade to 11.3.1, and then 14.3*

v9.3.1 Upgrade to 11.3.1, and then 14.3*

v10.3 Apply SP1, then upgrade to 12.3.1, and then 14.3*

v10.3.1 Upgrade to 12.3.1, and then 14.3*

v11.3 Apply SP1, and then upgrade to 14.3*

v11.3.1 Upgrade to 14.3*

v11.3.2 Upgrade to 14.3*

V12.3 Apply SP1, and then upgrade to 14.3*

V12.3.1 Upgrade to 14.3*

V13.3 Apply SP1, and then upgrade to 14.3*

Table 1-1: DeltaV Migration Path

1.2 Pre-Upgrade Considerations

1.2.1 Supported Operating Systems

Note: Installing DeltaV on a 32-bit OS will generate the following message:

Figure 1-1: Error message when installing DeltaV on a 32-bit OS

Figure 1-2: Error message when installing DeltaV on an unsupported 64-bit OS

1.2.3 Operating System Upgrade Kits

Computer Operating System Package Contents

 Dell Precision R5500XL

Table 1-2: Dell computers supported for OS upgrade

1.2.7 Installation Instructions for Operating Systems Supported on DeltaV Releases

1.2.8 Workstation Requirements

1.2.10 DeltaV Event Chronicle

1.2.11 Legacy Continuous Historian Upgrade

1.2.12 DeltaV Operate User Settings file

1.2.14 Manual Data Backup of DeltaV Add-in Products

1.2.15 Remote Workstation Connections to Multiple DeltaV Systems

1.3 Controller and I/O Requirements

1.3.1 DeltaV Controller Firewall and DeltaV SIS IPD Firewall

1.3.2 PK Controllers, EIOC and SZ Controllers

Important: Online upgrade of PK Controller is not supported.

1.3.3 Hardware Replacement

1.4 Post-Upgrade Considerations

1.4.1 Alarm Enable (Enab) Check Box

1.4.2 Data Restore

1.4.3 I/O Card Upgrades

1.5 Controller Switchover Tips

2.1 Complementary Products

2.2 Controller Support

2.3 DeltaV PK Controller

2.3.1 Features and Enhancements

2.3.2 DeltaV Functional Areas Modified to Support this New Product

2.3.3 Impact for Users Upgrading to v14.3

2.3.5 Suggested Areas for Validation

2.4 Cybersecurity Considerations

2.4.1 Features and Enhancements

2.4.3 Impact for Users Upgrading to DeltaV v14.3

2.4.5 Suggested Areas for Validation

2.5 Independent DeltaV Domain Controller

2.5.1 Features and Enhancements

2.5.3 Impact for Users Upgrading to DeltaV v14.3

2.5.5 Suggested Areas for Validation