This is the html version of the file https://www.honeywellprocess.com/library/support/Documents/Experion/SCN-TPN-Personalities-688-2.pdf.

Google automatically generates

html versions of documents as we crawl the web.
Tip: To quickly find your search term on this page, press Ctrl+F or ⌘-F (Mac) and use the find bar.

Page 1

TPS Process Network

R688.2
Software Change Notice

Revision Date: August 16, 2019

Document ID: TNDOC-X166-en-6882A

TPS Process Network R688.2 Software Change Notice 1

Page 2

Notices and Trademarks

© Honeywell International Sárl. 2019. All Rights Reserved.

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the

implied warranties of merchantability and fitness for a particular purpose and makes no express

warranties except as may be stated in its written agreement with and for its customer.

In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The

information and specifications in this document are subject to change without notice.

Other brand or product names are trademarks of their respective owners.

Honeywell International

Process Solutions

1860 West Rose Garden Lane

Phoenix, AZ, 85027, USA

+1 800-822-7673

www.honeywellprocess.com

TPS Process Network R688.2 Software Change Notice 2

Page 3

Support and other contacts

For support, contact your local Honeywell Process Solutions Customer Contact Center (CCC). To find your local CCC

visit the website, https://www.honeywellprocess.com/en-US/contact-us/customer-support-

 contacts/Pages/default.aspx.

TPS Process Network R688.2 Software Change Notice 3

Page 4

Symbol Definitions
The following table lists those symbols used in this document to denote certain conditions.

Symbol Definition

ATTENTION: Identifies information that requires special

consideration.

TIP: Identifies advice or hints for the user, often in terms of

performing a task.

REFERENCE - EXTERNAL: Identifies an additional source of

information outside of the bookset.

REFERENCE - INTERNAL: Identifies an additional source of

information within the bookset.
 CAUTION Indicates a situation which, if not avoided, may result in equipment
or work (data) on the system being damaged or lost, or may result in
the inability to properly operate the process.

CAUTION: Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury. It may also be used
to alert against unsafe practices.
CAUTION: symbol on the equipment refers the user to the product
manual for additional information. The symbol appears next to
required information in the manual.

TPS Process Network R688.2 Software Change Notice 4

Page 5

Contents
1 Introduction ............................................................................................................................... 6
1.1 About this Document ............................................................................................................................. 6
1.2 Limitations .............................................................................................................................................. 6

2 Contents of Release .................................................................................................................. 9

2.1 Software Media (CD-ROM).................................................................................................................... 9

3 Release Overview.................................................................................................................... 10
3.1 Experion LCN (ELCN) ......................................................................................................................... 10
3.2 UIS 2003 - Option to configure OP limits for HPM Regulatory Control points in MAN mode ............. 12

4 Software Compatibility ........................................................................................................... 14

Table 1 - TPN Software Release Matrix ...................................................................................................... 14
Table 2 - Triconex Compatibility/Validation with TPN ................................................................................. 15
Table 2 - Triconex Compatibility/Validation with TPN ................................................................................. 16
Table 2 - Triconex Compatibility/Validation with TPN ................................................................................. 17

5 Documentation Updates/Additional Information .................................................................. 18

6 Problems Resolved in R688.X ................................................................................................ 19

6.1 Problems Resolved in Release R688.2 ............................................................................................... 19
6.2 Problems Resolved in Release R688.1 ............................................................................................... 19

7 Special Considerations........................................................................................................... 20
7.1 General TPN System Operational Advisories ..................................................................................... 20
7.2 EUCN Known Issues ........................................................................................................................... 25
7.3 TCMI Known Issues ............................................................................................................................. 33
7.4 ELCN Known Issues ............................................................................................................................ 36
 8 Installation and Migration ....................................................................................................... 41
8.1 System Installation Advisories – General ............................................................................................ 42
8.2 Installation Instructions – R688.x Product Release ............................................................................. 44
8.3 Update System History Module with new &DSY Software .................................................................. 49

9 Appendix ................................................................................................................................. 51
9.1 R688.x Software Revision History ....................................................................................................... 51
9.2 R688.2 Release Revision History ........................................................................................................ 51
9.3 R6xx Personality Revision Level History (orientation) ......................................................................... 51
9.4 R6xx Generic Overlay (&OP1) Revision Level History ........................................................................ 52
9.5 R6xx Standard Back-Plane Module (&CUS, &OVG) Revision Level History ...................................... 53
9.6 R6xx Other Miscellaneous Software ................................................................................................... 55
9.7 Repeatable Special Software for R6xx ................................................................................................ 55

TPS Process Network R688.2 Software Change Notice 5

Page 6

1 Introduction

1.1 About this Document

This Software Change Notice documents the TPS Process Network Release of R688 software to
customers.

ATTENTION
SCN documents for prior releases are available from the Honeywell Online
Support web site (http://www.honeywellprocess.com), or they may be
requested from the Honeywell office that supplied your R688 software.

1.2 Limitations

1.2.1 Migration from TPN R600.X, R601.1 or R601.2 to R688 for Redundant PMMs

CAUTION
The following precaution must be followed when migrating redundant Process
Managers from R600.1 through R601.2 releases to R688. Failure to observe
this procedure could result in a loss of data and or control from the PMM.
If you have any questions regarding the PM migration procedure, please
contact your local Honeywell National Response Center (NRC), Technical
Assistance Center (TAC), or Customer Response Center (CRC).

If your PM is running below the minimum level shown below, you are at risk and must follow this special
procedure.

PM-cntrl (pmf) 60.05

PM-comm (pmc) 60.03

Note: TPN Release R601.3, R601.4, R601.5, all R61X.x, all R620.x, all R630.x and, all R64X.x (and
newer) releases already contain the PMM Box Timer fix so migrating from any of these TPN Releases to
R688 does not require this procedure.

All redundant PMMs not having box timer points in use and configured can migrate on-process to R688
PM Software with no restriction. Follow the upgrade procedure defined in the R688 Customer Release
Guide.

All redundant PMMs having box timer points in use and/or configured cannot migrate on-process to R688
PM Software. However, as explained in PN #9922A, customers using box timer points are at risk during
any failover or swap primary operations and are strongly urged to upgrade as soon as possible.
 TPS Process Network R688.2 Software Change Notice 6

Page 7

There are two cases:

1. All box timer points are “tagged”:

• Isolate and disable all points that reference box timer points and upgrade the primary and
secondary normally. After the migration, the box timer points must be reloaded from IDF,
and the points referencing box timer points re-activated.
OR
• Be aware that box timer points will lose their values, as explained above, and migrate on
line.
OR
• Idle the PM node. (NOTE: This step is done to ensure no process is running during the
upgrade). Shut down the secondary PMM and reload it with R688 PM Software. After
completion of the load, wait for 5 minutes before performing a swap operation. Reload
from IDF the configuration of all box timer points. Continue shutting down the new
secondary PMM and reloading it with R688 PM Software. After completion of the load,
verify everything is in proper state/mode before starting up the node.

2. Some or all box timer points are not “tagged”:

• Be aware that box timer points will lose their values, as explained above, and migrate on
line.
OR
• Shut down both PMMs and follow existing On-process upgrade procedure to reload the
redundant PMM with R688 software using most current checkpoint.

1.2.2 TPN System Installation & Migration Advisories:

CAUTION
Backwards Migration of Redundant On-Line NIMs after migrating to
R660 or later release can result in Secondary NIM failure
PAR # 1-16CPMP
The following caution should be followed when attempting to migrate
backwards On-Line redundant NIMs from any R660 or later release back to a
pre-R660 release. Failure to observe this procedure could result in a loss of
data and or control from the NIM.
If any R660 or later primary NIM has a secondary NIM on Pre-R660, any
update (operator, CL, schematic, DEB, etc.) to the newly added parameters
($REALARM, DLYOPT, DLYTIME, PVHIPR, PLVOPR, ALENBST,
$AUXUNIT, PVHITP, PVLOTP, PVALDBEU, $DLBADAL, $HISELCT,
$LOSELCT, $DLSELCT, $DHSELCT, $HHSELCT, $LLSELCT, $RPSELCT,
$RNSELCT, $OFSELCT) will cause the secondary NIM to fail.
If any R660 primary NIM has a secondary NIM on pre-R660, swapping xPMs
will also cause the secondary NIM to fail.
If you have any questions regarding the NIM migration procedure, please
contact your local Honeywell National Response Center (NRC), Technical
Assistance Center (TAC), or Customer Response Center (CRC).

TPS Process Network R688.2 Software Change Notice 7

Page 8
 CAUTION
Ensure Entire System is Upgraded to R688 Before Making Engineering
Changes to the Data Base or Attempting to Use the New CL Process
Change Journal Retrieval Function
Attempting to load/reload points using an R688 US/GUS/EST Native Window
with a data owner running pre-R688 software will produce undesired results,
including possible data-owning node failures, due to parameter additions
made as a result of added functional enhancements.

For CL Process Change Journal Retrieval to work, both the US and the AM
must be running R650 or newer.

CAUTION
CLM users MUST have CLM Platform Software Version 360.7 (or later)
for use with TPN R611 or later
Various problems can be encountered with earlier versions of CLM. For
example, CLM version prior to 360.4 will experience a secondary (backup)
CLM failure immediately upon startup using this TPN R611 or later software.
(PAR 1-1W4XL)
All CLM users (redundant and non-redundant) must install CLM Platform
Software Version 360.7 (or later).

ATTENTION
TPN Components’ Version. Revision
Beginning with TPN R684, TPN components such as personalities and
overlays etc will display revision numbers in 3 digits starting with 68.100. The
Software and displays have been updated to accommodate this change. In
case of mixed revisions across the network the displays and overlays will be
able to display over two digit revisions.

ATTENTION
Installers of GUS/ES-T and APP/EAPP/ESVT/ACE-T packages have
changed.
GUS/EST and APP/ESVT/ACE-T package installers have changed. Please
uninstall the installed packages before attempting to install the new
packages. The new personality installation packages constitute a .msi file as
opposed to the setup.exe in the previous packages.
Note: Failure to uninstall the installed package before installing the R688 or
later package will create a new entry to the “Add or Remove Programs” list
and will not remove the old installed package.

TPS Process Network R688.2 Software Change Notice 8

Page 9

2 Contents of Release

2.1 Software Media (CD-ROM)

Part Media Kit ID Title Internal Release Revision Release

Number Revision
Label

51156651 MP-TPN000-688 GUS TPN Software CD R688.1.13 R688.2

(Emulated &Z1, &Z6)
 51156652 MP-AM3000-688 TPN Application R688.1.13 R688.2
Module
(Emulated &Z3)

51156653 MP-SWS000-688 HPM/APM I/O R688.1.13 R688.2

Simulators
(Emulated &Z13)

51156654 MP-TSM000-688 Triconex Safety R688.0.12 R688.1

Manager
(Emulated &Z17)

51155871 N/A HVTS Off Line Test & 10.26 10.26

Verification
(Emulated &Z5)

51156655 N/A Utilities and Load R688.0.12 (&Z12) R301.20

Modules CD
R688.0.12 (&Z14)
(Emulated &Z12, &Z14) Firmware Manager: R110.5 (Build
2) (FirmwareManager_Setup.exe)

UEA: UEA R110.1-03-0 (Build 3)

(UEA_Release_Pkg_Signed_PRO
D.pkg)
R688.0.12

51156416 MP-TCMICD-687 EUCN - TCMI Software TCMI_100.3-05.0 (TCMI R100.3 R100.3

media Build 5)

Note: Starting with TPN Release R610 and later versions, the &KFO directory can now be found on
&Z6. The &Z11 media is no longer produced. The Kanji option and POK should still work in R610 and
later releases.

TPS Process Network R688.2 Software Change Notice 9

Page 10

3 Release Overview
This Software Change Notice documents the TPS Process Network Functional Release of R688 software
for general distribution to customers.

Note: Detailed functional descriptions are contained in the Customer Release Guide CRG-688 dated:
11/2018 (or newer) that is included with all TPN software shipments from Honeywell Software Delivery
Management.

3.1 Experion LCN (ELCN)

Introducing Experion Local Control Network (ELCN) with Experion R501.1 and TPN R687.1. The
ELCN is the Fault Tolerant Ethernet (FTE) version of the coaxial cable-based LCN, where LCN
communications are encapsulated on FTE. Each Experion LCN node has FTE cabling, but no LCN
cabling. There is no LCN coaxial cable or LCNI devices. The Experion LCN is one component of
Honeywell’s strategy to preserve the user’s investment in TDC 3000 (TDC, LCN, TPS, and TPN), while
providing the advantages of the Experion System, the Fault Tolerant Ethernet network, and virtualization
technology. All existing user-created LCN data objects (such as checkpoints, button configuration files,
display objects, and CL/AM objects) run on the Experion LCN platforms, without recompile, rebuild, or
reconstruction. For any given user-created data object source file, there is only one compiled object file.
A single image of each TPN/LCN personality (node) can execute on both the legacy platform and on the
ELCN platform.

Experion R501.4 and TPN R688.1 introduces UEA-based appliance redundant AM,
 redundant EPLCG, and redundant EHB (physical and virtual). Note that the Virtual EPLCG will not be
available for a production application, but only for Open VEP (Virtual Engineering Platform). The virtual
EPLCG may be used only for configuration or training purposes.

The ELCN Bridge is a key component in LCN to ELCN migration. The ELCN Bridge connects the coax-
based LCN to the FTE-based ELCN, creating a single logical hybrid network. The ELCN Bridge
translates LCN messages into Ethernet messages and vice versa, providing a means for legacy LCN
functions and the Experion version of those functions to coexist and interoperate while you migrate the
LCN nodes to the ELCN counterpart.
The ELCN Bridge is NOT required if performing an off-process migration of ALL LCN nodes to
Experion LCN. The ELCN Bridge IS required for the following migrations:

• If performing an on-process migration, the ELCN Bridge is required. After establishing the
ELCN Bridge, you migrate each coax-based LCN node to its Experion LCN node counterpart,
one at a time.
• If one or more coaxial LCN nodes are to remain on the coaxial LCN, then the ELCN Bridge is
required for data transfer to occur between the remaining coaxial LCN nodes and the Experion
LCN nodes – even if an off-process migration had been performed.

The ELCN migration may occur incrementally over time. After the last LCN node is migrated to ELCN
(no nodes remain connected to the LCN coaxial network other than the ELCN Bridge), the ELCN Bridge
can be removed.

TPS Process Network R688.2 Software Change Notice 10

Page 11

There are two general categories of ELCN Nodes: TPS Nodes and Appliance Nodes. ELCN TPS Nodes
are Experion nodes deployed on a physical Microsoft Windows-based platform or as a virtual machine.
You migrate legacy LCN user interface nodes (US, UxS, and GUS) to the ELCN as TPS Nodes. You also
deploy the ELCN History Module as a TPS node. You migrate LCN data owner nodes (such as the
ENIM, AM, EPLCG, and EHB) as ELCN Appliance Nodes or ELCN Virtual Nodes. ELCN Appliance
Nodes use the Honeywell Universal Embedded Appliance (UEA) hardware platform, as does the ELCN
Bridge.

The following figure illustrates a simple architecture of ELCN.

Benefits of ELCN are:

• Replacement of coaxial cables with superior Fault Tolerant Ethernet, which tolerates all single
faults and many multiple faults, and is much easier to maintain.
• Retaining intellectual property in legacy assets by conserving applications running on the
TPS/LCN.
• Increased plant longevity through Unified Control (Experion and TPS).
• Retaining point processing and checkpoints from classic nodes.

The following list identifies all documents that may be sources of reference for material discussed in this
 section.

Document Name Document Type Document Set

Planning and Design; Experion

ELCN Planning, Installation, and Service Guide
Troubleshooting

ELCN Overview and Implementation Guide Planning and Design Experion

Experion Migration User’s Guide (EMUGs) Installation and Upgrades Experion

TPS Process Network R688.2 Software Change Notice 11

Page 12

Document Name Document Type Document Set

ELCN Quick Start Guide Reference Experion

ELCN Upgrade Kit Instructions (51195195-415) Installation and Upgrades Release Independent

Customer Release Guide Installation and Upgrades TPN/TPS

Experion Software Installation User’s Guide Installation and Upgrades Experion

Control Building User’s Guide Configuration Experion

Integrated Experion-TPS User’s Guide Configuration Experion and TPN/TPS

Virtualization Planning and Implementation Guide Planning and Design; Experion

Installation and Upgrades

Server and Client Planning Guide Planning and Design Experion

Server and Client Configuration Guide Configuration Experion

Control Builder Parameter Reference Reference Experion

Control Builder Components Reference Reference Experion

Experion R501.4 Software Change Notice Reference Experion

TPN Personalities R688.1 Software Change Notice Reference TPN/TPS

3.2 UIS 2003 - Option to configure OP limits for HPM Regulatory Control
points in MAN mode

Beginning with TPN R686, you can additionally configure OP limits for HPM Regulatory Control
points in the MAN mode with the OPERATOR mode attribute, to clamp the OP value on the AO
channel.
The minimum and maximum system limits are -6.9 and 106.9, respectively.

Two new user configurable parameters are added for all HPM Regulatory Control algorithms (except
RAMPSOAK, POSPROP, PIDPOSPROP) to configure the output low limit manual ($MOPLOLM)
and output high limit manual ($MOPHILM). The new parameter definitions are as follows:

Parameter Default value Range

$MOPLOLM -6.9 (R686) -6.9% to OPLOLM and NaN
NaN (R688.2)
$MOPHILM 106.9 (R686) OPHILM to 106.9% and NaN
NaN (R688.2)

Note:
• After migrating from any pre-R686 release to R688.2, the $MOPHILM/$MOPLOLM
parameter values will be set to NaN.

TPS Process Network R688.2 Software Change Notice 12

Page 13

• After migrating from any previous applicable release R686.1-R686.4/R687.1-R687.3/R688.1

(which have the $MOPHILM/$MOPLOLM functionality), the existing
$MOPHILM/$MOPLOLM values will be retained. However, to disable this functionality, it
is recommended to change the $MOPHILM/$MOPLOLM values to NaN after migrating to
R688.2.
• Beginning with R688.2, the $MOPHILM and $MOPLOLM parameters will have a default
value of NaN.

$MOPHILM and $MOPLOLM values cannot be changed from AM/PM CL or peer controllers.

For more details, refer to the following documents:

• HPM Control Theory
• Customer-Release-Guide-CRG688
• HPM Parameter Pocket Guide
• XPM09 xPM Parameter Reference Dictionary

TPS Process Network R688.2 Software Change Notice 13

Page 14

4 Software Compatibility
 Table 1 - TPN Software Release Matrix

Product Description Minimum Revision Level Media Packaging

SOFTWARE

TPN Software R688.2 GUS TPN Software CD

TPSBuilder Software (Microsoft R430.1 TPSBuilder CD

Windows 7 platform)

GUS Software R421.3 TPS System Software CD

APP Software R421.3 TPS System Software CD

Utilities and Load Modules R301.20 Utilities and Load Modules CD

(GUS/APP/ES-T/ESVT load modules)

File Transfer R421.3 TPS System Software CD

Note: TPS System Software version qualified for TPN R688.2 is TPS R421.3.

TPS Process Network R688.2 Software Change Notice 14

Page 15

Table 2 - Triconex Compatibility/Validation with TPN

Tricon V8.2 V8.3 V9.0 V9.1 V9.2 V9.3 V9.4 V9.5 V9.6

Honeywell

R5XX Validated Validated

R61X Compatible Compatible Compatible Validated Validated Compatible Compatible

R62X Compatible Validated Validated Validated Validated Validated Validated Validated Validated
R63X Compatible Compatible Validated Validated Validated Validated Validated Validated Validated

R64X Compatible Validated Compatible Compatible Compatible Compatible Compatible Validated Validated
R65X Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Validated
R66X Compatible Validated Compatible Compatible Compatible Compatible Compatible Compatible Validated

R67X Compatible Validated Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R680 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R681 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R682 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
 R683 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R684 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R685 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R686 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R687 SMM Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R687 TCMI

R688 SMM Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R688 TCMI

TPS Process Network R688.2 Software Change Notice 15

Page 16

Table 2 - Triconex Compatibility/Validation with TPN

Tricon V9.7 V9.8 V9.9 V9.10 V10.0 V10.1 V10.2 V10.3 V10.4

Honeywell
R5XX

R61X

R62X Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R63X Validated Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R64X Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R65X Compatible Validated Compatible Compatible Validated Compatible Validated Compatible Compatible

R66X Compatible Compatible Compatible Compatible Validated Compatible Compatible Compatible Compatible

R67X Compatible Compatible Compatible Compatible Validated Compatible Compatible Compatible Compatible
R680 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Validated Compatible
R681 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Validated Validated

R682 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R683 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R684 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R685 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R686 Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible
R687 SMM Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R687 TCMI Compatible Compatible

R688 SMM Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible Compatible

R688 TCMI Compatible Compatible

TPS Process Network R688.2 Software Change Notice 16

Page 17
 Table 2 - Triconex Compatibility/Validation with TPN

Tricon V10.5 V10.6 V11.0 V11.1 V11.2

Honeywell
R5XX
R61X
R62X Compatible Compatible Compatible Compatible Compatible
R63X Compatible Compatible Compatible Compatible Compatible
R64X Compatible Compatible Compatible Compatible Compatible
R65X Compatible Compatible Compatible Compatible Compatible
R66X Compatible Compatible Compatible Compatible Compatible
R67X Compatible Compatible Compatible Compatible Compatible
R680 Compatible Compatible Compatible Compatible Compatible
R681 Compatible Compatible Compatible Compatible Compatible
R682 Validated Compatible Compatible Compatible Compatible
R683 Validated Compatible Compatible Compatible Compatible
R684 Validated Compatible Validated Validated Validated
R685 Validated Compatible Compatible Compatible Validated
R686 Compatible Compatible Compatible Compatible Compatible
R687 SMM Validated Compatible Compatible Validated Compatible
R687 TCMI Validated Compatible Compatible Validated Validated
R688 SMM Compatible Compatible Compatible Compatible Compatible
R688 TCMI Validated Compatible Compatible Compatible Validated

Compatible SMM is designed to work correctly in this configuration. Honeywell and Triconex do not know of any reason why this should not work.

Validated Either Honeywell or Triconex personnel carried out formal validation testing. Results were documented per existing QA procedures and both
Honeywell and Triconex agree that these versions are 100% compatible.

Currently not Validated. Both Honeywell and Triconex recommend customers implement combinations that are validated. Customers using
combinations not currently validated are at risk for encountering problems involving this interface and may not receive full technical support from
Honeywell and/or Invensys Triconex.

Should you require further information regarding the validation and compatibility between Honeywell and Triconex SMM products, please contact
your Honeywell or Triconex Sales Representative.

TPS Process Network R688.2 Software Change Notice 17

Page 18

5 Documentation Updates/Additional Information

All documentation that supports this release can be installed using Product Documentation & Customer
Resource Manual (CRM) DVD. To install Product Documentation & CRM, follow the installation
instructions in the Product Documentation & CRM SCN. The Installation instructions are also available
as help on installation splash screen.
Product documentation and CRM is a collection of PDF files of the end user documentation for a
Honeywell System or a product. The documents are categorized based on the nodes/network/engineering
tasks related to a product. PAR updates are available in the Product Documentation & CRM SCN PDF
collection set.
In addition to this SCN and the above electronic documentation DVD, a hardcopy of the Read Me First
document is provided with this release.
 TPS Process Network R688.2 Software Change Notice 18

Page 19

6 Problems Resolved in R688.X

• “US” means the problem affects Operator, Universal, UxS, GUS and ES-T Native
Window.
• “AM” means the problem affects TPN personality used by ACE-T, AM, AxM, APP,
EAPP, ESVT and Integration Node.

6.1 Problems Resolved in Release R688.2

PAR # Personality Function Summary Description

1-BAZOBWD SAFEOP value is changing from NaN to 106.9 after

HPM HPM
migration to TPN R687.3.

1-ANWMYKF Upon loading an ES-T, the HM node crashes if it is

HM HM
the only node running in the network.

The Clock master/slave nodes and the Cable master

RELCN-1134 ELCN ELCN nodes in the network should be mentioned in the
ELCN Bridge platform block.

6.2 Problems Resolved in Release R688.1

PAR # Personality Function Summary Description
The Data Entity Builder Online Help display for the
1-80OHUP7 HG HG EIPENB parameter states that the EIP can be disabled
by setting ALENBST to Inhibit, this is incorrect.
HPM HPM The OPHILM and OPLOLM parameters are giving
1-84LH6VT
control error with 106.9 and -6.9 values respectively.
OP value toggles between manual limits and SAFEOP
HPM
1-A8YFHFR HPM when viewing the REGCTL tag while in the
control
SHUTDOWN state.
 1-AIQUGSX HG HG Emulated HLPIU DISOE point not alarming on Server
and Flex station.

System The secondary ENB does not take over UCN/EUCN

1-A6Y7PE5 ENIM Managem network when Primary is powered OFF creating a LOV:
ent Reports “NODE ASN” for UCN & EUCN.
SMM checkpoint fails to restore digital composite
1-APJ1Y61 TCMI TCMI
points onto TCMI.
Occasionally, a TCMI node cannot be recovered from
1-8H1521R TCMI TCMI FAIL state using RECOVER target from Native
Window.
TPS Process Network R688.2 Software Change Notice 19

Page 20

7 Special Considerations

7.1 General TPN System Operational Advisories

CAUTION
In rare instances, it has been noticed that History Modules can report a
SEVERE status for history collection followed by that History Module
becoming unresponsive. PAR #1-BBWG4H
HMs with any type of drives, including Single Board History Modules
(SBHMs), under certain conditions may report a Severe status because data
is no longer being written to or retrieved from, its drive(s).
The Status Detail display for the HM could show any combination of the three
messages below:
HH:MM:SS NODE XX SEVERE HISTRY_JRNLS (OK
->SEVERE ):FUNCTIONALITY DISABLED 76
HH:MM:SS NODE XX SEVERE CONT_HISTORY (OK
->SEVERE ):FUNCTIONALITY DISABLED 76

HH:MM:SS NODE XX SEVERE ON_PROC_ANALS (OK

->SEVERE ):FUNCTIONALITY DISABLED 76
Configured history or/and journal collections will not function (even if the
affected HM is a non-System HM); possible loading failures when loading
nodes from NET; and it has also been observed that HM resident schematics
may not load, which could lead to a Loss of View (LOV) condition.
Workaround:
If the above mentioned circumstances are encountered, it is recommended
that the HM be shutdown and rebooted right away.

CAUTION
Two Clock Masters on a TPN network causing LCN Nodes to Isolate.
PAR #1-CDWRHW
It has been observed that when two clock sources specified in the NCF are
booted together or sometimes even when of the clock source LCN node is
booted, there is a possibility that both the LCN nodes start acting as clock
MASTER.
When two LCN nodes take mastership, there is a high possibility that LCN
nodes may be ISOLATED.
Workaround:
R620 introduced new CL based application to detect and manage Clocks
Masters and Slaves on TPN network. 4 new files (CLOKMON.CL,
CLOCKMON1.CL, CLOKMON1.EB and an instructions file CLOCKMON.XI)
were added to the &Z3 media, NET>TLK2. These CLs will help in identifying
when there are two Masters on a network.
The new functionality added in R682 (Change The Clock Source Node
(R1404 / #1940)) could be used to relinquish the mastership of one clock
master.

TPS Process Network R688.2 Software Change Notice 20

Page 21

ATTENTION
HWYREDST shown incorrect status of HG. PAR #1-9LQ0XD
Parameter HWYREDST is not displaying correct value of the HG status as
primary or secondary.

Workaround:
PSDP parameter $HGMODE can be used as an alternate of HWYREDST
parameter.

ATTENTION
Dissimilar alarms are reporting when ALFMT is changed. PAR # 1-
92EYT5
Changing the alarm format of HG secondary (with reference to contact
cutout) from ALFMT03 to ALFMT00 reports PVLO alarm and RTNs
simultaneously.

ATTENTION
EIPCODE might not be configured for the maximum 600 points. PAR #1-
7HTQ5I
600 points in an HG could be configured to have EIPCODE. When user
builds points from a blank checkpoint user is allowed to create 600 points
with EIPCODE enabled, whereas if user deletes any points configured with
EIPCODE or rebuilds any point that has been enabled for EIPCODE, then
user will be blocked even before the 600 limit is reached.

ATTENTION
UCNDEVUT display data may display invalid data for modules
configured as “REMOTNIM” in a logical UCN Networks. PAR #1-B8C471
UCNDEVUT display data may display invalid data if invoked from the NIM,
where is it is configured as “REMOTNIM”. UCN device utilization display &
XPM/LM Resource utilization displays may show different data for certain
UCN nodes when viewed from different UCNs.

ATTENTION
Hiway Gateway Regulatory point reports a false PVHH alarm journal
whenever PVHI alarm is re-annunciated due to change in alarm
configuration. PAR 1-96AYON
When both PVHI and PVHH alarm are present on Hiway Gateway Regulatory
point, changing the priority of PVHI alarm reports a false journal for PVHH
alarm with the timestamp as that of the PVHI alarm. This behavior is not
observed on the alarm summary; the alarm summary does not change the
time stamp of PVHH alarm when PVHI alarm is re-annunciated.

TPS Process Network R688.2 Software Change Notice 21

Page 22

ATTENTION
NIM reports nuisance errors UG$_DH_PSTP3, after migration from Pre
660 release to R660 or later. PAR #1-BMOZ7M
 NIM reports nuisance errors UG$_DH_PSTP3, after migration to R660 or
later. These system error messages are reported due to problem in syncing
between the NIM and the IOP DLYTIME when UCN is busy. A System Error
Journal is reported for every point when the value of DLYTIME between IOP
and NIM are synchronized.
The DLYTIME value in IOP and NIM are programmed to be synchronized
when migrated from Pre-660 release to a R660 or later. If the synchronization
does not happen during migration due to UCN being busy or other reasons.
The values get synchronized whenever DLYTIME parameter is fetched, and
System Error Journals is also reported conveying that the DLYTIME were
synchronized.

ATTENTION
Copying large file from the HM to a zip drive fails when zip is local to the
station requesting the copy. PAR #1-C5P596
On copying large file (50000 records, 5.5 Mb) from History Module to ZIP
drive on local Universal Station. After 10 minutes, the COMMAND
PROCESSOR window of the US issues a File Manager error - "No response
from Remote Node" and the copy aborts.

The US has a ten minute timeout for File Manager actions. When the file is
large enough that it takes longer than the ten minute timeout, the error
message is issued and the FM task aborts for that US. Since the HM is trying
to write to the ZIP drive on the local US, it can no longer get to the ZIP drive
since the FM task is aborted.
Workaround:

Use a ZIP drive that is remote to the US that you are initiating the COPY
command from to copy from the HM to a ZIP drive. This will allow the copy to
complete. Regardless of whether the error message is issued on the US or
not, the FM task will still abort in 10 minutes on the US that initiated the
COPY action, but since the ZIP drive is on another US, the FM task on that
US is not affected by the abort and is still operational.
Use below steps to know when the copy is complete after the FM task error is
already experienced.
• From the remote US, do an LS $Fx>dir>*.* (for example,
$F8>PGU4>baseline.xx) and check the record and block size.
• If the file(s) record size is still zero, then the copy of the file(s) did not
occur.
• Check periodically when the LS command actually shows data in the
record and block size fields, the copy is completed.

ATTENTION
In large network configuration a delay is observed when the LCN Cable
Overview Schematic $LNDGCBL is invoked. PAR #1-82RF2I
Due to the complex calculations involved and data that need to be fetched
from many nodes; A delay is observed for the values in the LCN Cable
Overview Schematic $LNDGCBL to appear on the screen. This PAR could be
observed only in large network configurations where the number of LCN
nodes is more than 40.

TPS Process Network R688.2 Software Change Notice 22

Page 23

ATTENTION
In case of dual IOL cable fault in both primary and secondary IOP
chassis, after recovering from dual cables faults secondary IOP may
remain in NR with sync error. Primary and Secondary IOP may be
displayed as OK/NR.
Workaround:
In such case perform HPM swap. Secondary IOP comes to BKP after HPM
swap.

CAUTION
On PCUS, the SET PATH in the MOUNT/DISMOUNT Emulated Disk does
not work. PAR 1-2DR5MUK
If you select the SET PATH option in the MOUNT/DISMOUNT Emulated
Disk, the message “Internal error in default path settings” appears.
NOTE: The following workaround is applicable only for PCUS.
Workaround:
 1. In the path HKLM\Software\Honeywell\TDC Emulators\Media”, create a
new string value with the Value name “DefaultEDPath” and in the Value
data type “C:\ProgramData\Honeywell\EngineeringData”.
2. From the PCUS, select Start > All Programs > Honeywell Experion
PKS > TPS Applications > LCNP Status 0 and then select Reset
LCNP.
3. Select Yes and then wait for the LEDs port to indicate the configured
PCUS LCN node address.

4. At the bottom of the Native Window display, select the LOAD button.
5. Type “N” and then press ENTER.

6. Type “U” for Universal Personality or “O” for the Operator Personality and
then press ENTER.

Wait for the System Status display to appear on the screen.

ATTENTION
Do not configure GUSALA or GUSALAG load modules on an ES-T node.
Configuring either GUSALA or GUSALAG load module on an ES-T is an
illegal configuration.
Starting with EST load module version 68.6 and later, upon ES-T start-up, the
EST load module will check to see if either GUSALA or GUSALAG load
modules are configured in the NCF for the local ES-T node. If so, the LCNP
node will be forced to fail. Directly before the failure, a new auxiliary status
message will be sent to the History Module which reads “GUSALA/G Load
Module Not Compatible With EST. Modify NCF.”
You must modify the NCF to remove the GUSALA and/or GUSALAG load
modules. These two load modules interfere/compete with the EST load
module’s ability to receive LCN events.

TPS Process Network R688.2 Software Change Notice 23

Page 24

ATTENTION
In a particular scenario, the removal of alarm cutout (Contact Cutout
functionality) fails to rebroadcast that process alarm. PAR # 1-6A8Q5LQ
This scenario occurs when the CONTCUT parameter value is changed
through a logic point/CL in a particular sequence only, as follows:
1. While a point is in alarm, the CONTCUT parameter is set to TRUE.

2. Alarm returned to normal (RTN) due to process conditions.

3. Alarm occurred again due to process conditions.
4. Change the CONTCUT parameter value in the following order.
a) FALSE
b) TRUE
c) FALSE.
5. Observe that the process alarm is not reported on the alarm
summary.

Workaround: To recover;
• Set the alarm enable state (ALENBST) to INHIBIT and then back to
ENABLE.
Or
• Change the priority of the process alarm to NOACTION and then
back to the original priority.

ATTENTION
After US/GUS/ES-T load/reload operation, the node fails to
differentiate between HG & EHB and ETN & classic T-nodes in the
network. PAR 1-7BQXWDY
During migration from any prior TPN release to TPN R686.3, after
US/GUS/ES-T load/reload operation, occasionally, the node fails to
differentiate between HG & EHB and ETN & classic T-nodes in the
 network.
Workaround: Reload the US/GUS/ES-T node.

ATTENTION
When you load clock source nodes in a quick sequence, then both
the clock source nodes may get loaded as clock masters. PAR 1-
V3KG0Y
This creates multiple clock masters situation in the network that can
cause node such as, NIM or AM or HG to get isolated or fail.
Workaround: It is recommended to load/reload the second clock
source node only after 1st source node is loaded.
Note: In addition, if the LCN network is divided in segments separated
by TPN bridge or F/O LCN extenders then you must have both the
source nodes in a single segment. If you have clock source nodes in
different segments, then this might cause slave to become master in
during transient cable problems. This leads to multiple clock masters
condition in LCN network.

TPS Process Network R688.2 Software Change Notice 24

Page 25

ATTENTION
If the HPM REGCTL points’ OUTIND parameter is set as REVERSE,
then SAFEOP, OPHILM, and $MOPHILM parameter values storing
the maximum limits may fail resulting in an error. PAR 1-BI3LW3D

Workaround:
Storing any other valid values will be successful.

ATTENTION
This is expected due to precision errors in the data conversion of
the $MOPHILM/$MOPLOLM values. PAR 1-BI3LW3M
When $MOPHILM is set to 106, the OP value can be set up to 106.013.
The LMT OR RANGE ERR is reported only if the OP value is set
beyond 106.014.
Similarly, when $MOPLOLM is set to 0, OP value can be set up to
-0.013. The LMT OR RANGE ERR is reported only if the OP value is
set beyond -0.014.

ATTENTION
If the HPM REGCTL points’ OUTIND parameter is set as DIRECT and
OPLOLM value is set to NaN (----), then $MOPLOLM parameter
values can be set to a value which is higher than OPLOLM.
Similarly, if the HPM REGCTL points’ OUTIND parameter is set as
REVERSE and OPHILM value is set to NaN (----), then $MOPHILM
parameter values can be set to a value which is lower than OPHILM.
PAR 1-BJ9L59H
Workaround:
If it is required to set the OPHILM/OPLOLM to the extreme system limits,
then set them to 106.9/-6.9 respectively, instead of NaN.

7.2 EUCN Known Issues

ATTENTION
EUCN nodes are not coming to PWR_ON (ENIM) or ALIVE (EHPM) state,
after flashing new firmware using the EPA tool followed by a power re-
cycle. PAR #1-YMVH8U
Workaround:
After flashing new firmware and performing a power re-cycle to the EUCN
nodes, a second power re-cycle must be performed to return the EUCN
nodes to PWR_ON (ENIM) or ALIVE (EHPM) state.
 TPS Process Network R688.2 Software Change Notice 25

Page 26

ATTENTION
Stress testing of an EHPM “Swap Primary” functionality may cause a
failure of a redundant EHPM, resulting in the need for power re-cycle
recovery. PAR #1-YMZ0MX

This failure has only been observed to occur after a very high number of
continual swaps between primary and secondary EHPM using the “Swap
Primary” target, and does not occur during normal operation. This failure
does not result in a loss of view or loss of control.
The failure results in the secondary EHPM showing “OFFNET” on the UCN
status display, as well as showing a blank screen on the front panel LED of
the EHPM Comm/Control board.
Workaround:
If you have any questions about this procedure, contact Honeywell TAC.
This failure does not occur during normal operation. Use caution when
performing a “Swap Primary” operation. If this failure occurs after a “Swap
Primary” command, and the “OFFNET” status is shown on the UCN status
display:
To recover, power re-cycle the EHPM Comm/Control board to return it to the
ALIVE state.

TPS Process Network R688.2 Software Change Notice 26

Page 27
 ATTENTION
Stress testing of an EHPM “Swap Primary” functionality may cause an
error code of “0A20” on a redundant EHPM. PAR # 1-ZPX00D
Note: This error scenario is also possible with the HPM.
This failure has only been observed to occur after a very high number of
continual swaps between primary and secondary EHPM using the “Swap
Primary” target, and does not occur during normal operation. This failure
does not result in a loss of view or loss of control.
This failure results in the redundant EHPM going to the FAIL state, as well as
the front panel LED of the EHPM Comm/Control board showing an 0A20
error code.
Workaround:

If you have any questions about this procedure, contact Honeywell TAC.
This failure does not occur during normal operation. Use caution when
performing a “Swap Primary” operation. If the 0A20 error code occurs, the
0A20 error is fully recoverable from the UCN status display.

To recover:
1. Select EHPM node that has failed.

2. Select “RUN STATES” target.

3. Select “RECOVER” target.

4. Press Enter.
Result: The EHPM node will return to the BACKUP state automatically.

ATTENTION
Redundant Private Path Init Error” during switchover is noticed very
rarely. PAR 1-13TBNIV
This soft failure is rare. This is a soft failure during initialization. It appears to
be a hardware related issue during initialization, and seems to have no effect
on redundancy functionality.
Workaround:

To remove the soft fail, perform a "Swap Primary" command.

ATTENTION
INVALID DATA TYPE is displayed for LM displays, when Node is in
Offnet. PAR 1-2GRHEOV
When the LM node is in Offnet the US displays are showing INVALID DATA
TYPE at top of the screen.
Workaround:
There is no workaround.

TPS Process Network R688.2 Software Change Notice 27

Page 28

CAUTION
SM Display, media type entity not updated. PAR 1-25I55MJ
For SM 160 or later version, the media type need to be updated as
“FTE”. Currently, it is displayed as TBC.
Workaround: There is no workaround.

ATTENTION
 LADDER SAVE and LADDER LOAD options are displayed on the
UCN Status display for LOAD/SAVE RESTORE option while
performing Checkpoint Restore of ELMM. PAR 1-3H3RK01
LADDER SAVE and LADDER LOAD options are displayed even though
they are not applicable for ELMM. During the Checkpoint Restore
operation, these targets are disabled.
Workaround: There is no workaround.

ATTENTION
A system error is reported on the SEJ whenever an ELMM node
comes up. PAR 1-3E3ZGDR
A system error is reported on the SEJ whenever an ELMM node comes
up. This is due to the mismatch in the event packet format between the
NIM and ELMM. No functional impact.

Workaround: There is no workaround.

ATTENTION
NIM fails to recognize the secondary ELMM module during the
double FTE cable fault scenario. PAR 1-3IJNSZY
NIM fails to recognize the secondary ELMM module during the double
FTE cable fault scenario.
Workaround: Reboot the Secondary ELMM.

ATTENTION
Non-redundant ELMM is displayed as primary on the UCN Status
Display which causes several no-response errors. PAR 1-
3L9N8CP
The Non-redundant ELMM is displayed as primary instead of non-
redundant on the UCN Status Display and hence it attempts to
communicate with the secondary ELMM which does not exist. This
results in several no-response errors.
Workaround: There is no workaround.

TPS Process Network R688.2 Software Change Notice 28

Page 29

ATTENTION
A loss of control and/or loss of view may occur on running EUCN
nodes if the Device Index ($DEVIDX) of an existing node is used
while loading the EUCN node specific configuration to a newly
configured EUCN node. PAR 1-3DOP3HB
For example, on a running ELMM (for example, EUCN=04, ELMM=07,
$DEVIDX=33), if the user reconstitutes the UCN configuration on the
ELMM, and changes the ELMM node number (for example, 07), but
retains the same $DEVIDX value (for example, 33) on the same UCN
number (for example, 04), and then loads this configuration, this may
result in a loss of control and/or loss of view for all the EUCN nodes.
While reconfiguring an EUCN node, if there is a change in the Device
Index of a running EUCN node, DEB throws a warning indicating that a
loss of control and/or loss of view may occur on an EUCN node. Use
caution while reconfiguring an EUCN node.
Workaround:
If you have need assistance to perform this procedure, contact
Honeywell TAC.

Use caution when making ONLINE changes to the Device Index

($DEVIDX) value on a running EUCN system. This may result in loss of
control and/or loss of view for the EUCN nodes if the same Device
Index and the EUCN node numbers are used that exist on a pre-
existing EUCN (only the EUCN node number is different).
If this accidentally occurs, to recover:
 • Reload the original EUCN’s UCN Device Specific configuration.
• Configure a unique Device Index for the new EUCN node.
• Re-flash the firmware on the EPNI2 board and then reboot ENIM.

A unique Device Index is required for each and every node in the FTE
Community. If you attempt to configure a duplicate Device Index, then
the last one loaded replaces the original.

ATTENTION
For AM points, on the Data Entity builder (DEB), If you select Brief
as the entry for the point disclosure parameter instead of Full, it
causes default values to be entered for those parameters not
displayed by DEB. PAR 1-QNWZED
Though the parameters which are not displayed on DEB can be
currently changed using Point details display, during point reload or
back build, the values of these parameters will be set to default values.
Workaround: Do not use point disclosure as brief if you are planning to
use all point parameters and specifically those which are not displayed
on DEB. It is recommended to use point disclosure as Full when you
are planning to use all the point parameters.

TPS Process Network R688.2 Software Change Notice 29

Page 30

ATTENTION
Primary HPM/EHPM is displayed as OFFNET on the UCN Node
Status Display. PAR 1-57B0YDL
if the secondary shows BACKUP the primary is really okay, even
though it says OFFNET.
Workaround: Wait for 5 minutes to see if the value updates. You can
then issue a “SWAP PRIMARY” command (even though the primary
shows OFFNET), and the backup HPM/EHPM will take over as primary
and the status will change to OK/BACKUP.

ATTENTION
xPMs CLs that send read/write requests to other ENB-resident
EUCN nodes may fail with COMM Error. PAR 1-5B2ZYQX
If the xPM CLs encounters a communication error while performing
peer-to-peer communication with other ENB-resident xPMs, and the
xPM CL is not already coded with the “WHEN ERROR” error clause to
take corrective action, then the CL may fail with COMM ERROR status.
Workaround: xPM CLs can be coded with the “WHEN ERROR” error
clause in the READ/WRITE and SET statements to take program action
when an error condition occurs. Refer to the following Control Language
Reference Manuals for description and syntax:
• Control Language Process Manager Reference Manual (PM27-
510)
• Control Language Advanced Process Manager Reference
Manual (AP27-610)
• Control Language High-Performance Process Manager
Reference Manual (HP27-610)

ATTENTION
During ENB failover, the peer-to-peer communication between
classic UCN and EUCN nodes breaks for a short duration. PAR 1-
4IPUPFZ
During ENB failover, the peer-to-peer communication between classic
UCN and EUCN nodes breaks for a short duration. This results in a
BAD VALUE which may cause mode shedding.
 Workaround: Set the SHEDTIME parameter to a higher value,
preferably > 5 seconds.

ATTENTION
During HPM/EHPM swap over, the peer-to-peer communication
between UCN or EUCN nodes breaks for a short duration. PAR 1-
5IYPBUD
During HPM/EHPM swap over, the peer-to-peer communication
between classic UCN and EUCN nodes breaks for a short duration.
This results in a BAD VALUE which may cause mode shedding.
Workaround: Set the SHEDTIME parameter to a higher value,
preferably > 5 seconds.

TPS Process Network R688.2 Software Change Notice 30

Page 31

ATTENTION
Loading an EHPM fails infrequently with MOD ACTV error. PAR 1-
5AMQ157
When an EHPM, which is in the ALIVE state, is loaded from the Native
Window, the load operation fails infrequently with MOD ACTV error.
Recovery:
1. Reload the EHPM from the Native Window.
Note: If the load operation is not successful, then perform the
following steps.
2. Power recycle the EHPM.
3. Reload the EHPM again from the NET using the Native
Window.

ATTENTION
A loss of view may occur in the ENB network when both FTE A and
FTE B cables of the Primary ENB have a problem. PAR 1-5HGKFPD
When a double FTE cable failure occurs on a Primary ENB, the
Secondary ENB takes over as the primary node, but it may result in a
loss of view in the ENB network. After sometime, UCN/EUCN nodes
show NODE ASSN error.
Recovery::
1. Shut down the new Primary ENB from the Native Window.
2. Load the new Primary ENB from the NET using the Native
Window.
3. Rectify FTE cable issues on the original Primary ENB (in the
FAIL state).
4. Power recycle the original Primary ENB.
Note: Verify that the FTE cable status indicates OK on the
$FTESTS2 schematic.
5. Load the original Primary ENB from the NET using the Native
Window.
Result: The original Primary ENB transitions to the BACKUP
state.

ATTENTION
Loading an ENB from the QUALIF state does not work
occasionally. PAR 1-4FPSVDP
Loading an ENB from the QUALIF state does not work occasionally and
also issues an error “Error found checking data”.
Note: For an ENB (or ENIM) node, during on-process migration to a
newer TPN software release (including point releases), you must either
load the ENB (or ENIM) node from the FAIL state or PWR_ON state
(preferred). Do not load from the QUALIF state. Within the exact same
software release, you may load ENB (or ENIM) from the QUALIF state,
but wait for at least one minute before attempting the load.
Recovery:
1. Shutdown the ENB in the QUALIF state to place it into the FAIL
state.
 TPS Process Network R688.2 Software Change Notice 31

Page 32

Note: PWR_ON state is preferred.

2. From the FAIL state, wait for at least one minute and then load
the ENB from the NET using the Native Window. There is no
need to wait when in the PWR_ON state.

ATTENTION
Performing DEB operations on a busy system with ENB nodes
may cause a DEB error which would require the DEB operation to
be repeated. PAR 1-4RU7WT7

Performing DEB operations, such as Alter Parameters or Point Builds,

on a busy system with ENB nodes may cause a DEB error which would
require the DEB operation to be repeated.
Workaround: If the DEB error occurs, repeat the DEB operation.

ATTENTION
Overloaded ENB may cause a Primary ENB failure with the Task
Name of UG$_MISTY. PAR 1-5XG462Z
When a redundant ENB is overloaded, that is, the cross peer-to-peer
traffic levels between the coaxial-based UCN and FTE-based EUCN
crosses the threshold limit of 140 cross peer-to-peer messages/second
for a sustained period of time, this condition may cause a Primary ENB
failure with the Task Name of UG$_MISTY, and the Secondary ENB
takes over as the primary node.
For more information on ENB redundancy communications, refer to
section “EUCN On-Process Migration” in the UCN Guidelines (UN12-
610) document.
Workaround: Ensure that the cross peer-to-peer traffic levels between
the coaxial-based UCN and FTE-based EUCN does not cross the
threshold limit of 140 cross peer-to-peer messages/second for a
sustained period of time. You may need to gather peer-to-peer data
using the $UCNP2P schematic as described in the section “Use the
UCN Peer-To-Peer Traffic Analysis Tool” in the Engineer’s Reference
Manual (SW09-605).
If you need assistance to analyze the data gathered, please contact
Honeywell TAC.

ATTENTION
After double FTE cable fault, occasionally, an EHPM can't be
recovered from FAIL state using RECOVER target from Native
Window. PAR 1-5AYNEOV
In rare conditions, after a double FTE cable fault, occasionally, an
EHPM can't be recovered from the FAIL state using RECOVER target
from Native Window. EHPM failover occurs normally (no loss of
view/control).
Workaround: Power re-cycle the EHPM and then load from the ALIVE
state.

TPS Process Network R688.2 Software Change Notice 32

Page 33

ATTENTION
In an ENB network where TCMI and EHPM have peer connections
 if TCMI is in ALIVE state, EHPM may run into UCN overruns. PAR
1-8ODZWEQ
If the EHPM point database has any pre-fetch peer requests from a
TCMI which is in the ALIVE state, then EHPM may start showing UCN
access overruns until TCMI transitions to IDLE/OK state.
Workaround: There is no workaround. It is recommended not to keep
TCMI in the ALIVE state for an extended period of time when the
system is on-process.

7.3 TCMI Known Issues

ATTENTION
Time Synch status shows as INITIAL for both Primary & Secondary
TCMI nodes. PAR 1-8550X1L
Time Synch status shows as INITIAL for both Primary & Secondary
TCMI nodes on the SMM Detail Status Display and UCN Statistics
schematic.

Workaround: For the actual Time Synch status, refer to the new
diagnostics schematic TCMI DIAGST and/or the $FTESTS schematics.

ATTENTION
Occasionally, loading an SM results in an error for “$TRPLOPT”
Parameter. PAR 1-8NCMTQK
With TPN R687.1, occasionally, when the Node Specific Configuration
for SMM_Tricon is loaded/reloaded, it may result in an error.

Also, this impacts the HMIWeb display which blinks for a moment during
TCMI communication loss under the ENB network and then recovers
automatically.
Workaround: To overcome the load/reload error, repeat the operation.

TPS Process Network R688.2 Software Change Notice 33

Page 34

ATTENTION
For an Analog Input point, the PVTEMP value is not stored as
DEGC. PAR 1-8NZ8XEZ
For an Analog Input point, the PVTEMP value is not stored as DEGC.
This applies to Analog Input point connected to TC_RTD type.
Workaround: If you intend to modify/set the PVTEMP value to
DEGREEC from PED, then after loading the point successfully with the
new configuration, perform a manual swap over (SWAP PRIMARY)
operation for the new values to take effect. If the intent is to store
DEGREEF to PVTEMP, then this workaround is not required.

ATTENTION
Secondary TCMI comes back to ALIVE state on a manual swap
over if a valid time source does not exist in the ENB network. PAR
 1-9VHF7CU
In the ENB network, if the time source for ENB shows NONE and the
operator triggers a manual swap over operation from the Native
Window, then the secondary TCMI switches over to primary
successfully and the new secondary comes back to ALIVE instead of
BACKUP state.
After reboot, the Secondary TCMI does not account for the timeout on
non-availability of a valid time source.

Workaround: There is no workaround, you must download the TCMI

personality onto the Secondary TCMI module.

ATTENTION
When a DOWNLOAD ALL operation is performed on the TriStation,
the connected TCMI node transitions to IDLE state and fails to
startup SOE reporting when moved to RUN state. PAR 1-9ANKJPZ

Whenever you perform a DOWNLOAD ALL operation for configuration

changes on the TriStation, if the TCMI is in RUN state, it transitions to
IDLE state. When you run the TCMI again after the DOWNLOAD ALL
operation is complete, SOE fails to report.
Workaround: Either swap the TCMI or shutdown and reload the
Primary TCMI module.

TPS Process Network R688.2 Software Change Notice 34

Page 35

ATTENTION
Illegal OPFINAL value on TCMI Digital Composite point results in
Experion Detail Status Display showing “UNDEF”. PAR 1-AB6O0R1
An illegal OPFINAL value on the TCMI Digital Composite point will result in
Experion Detail Status Display showing “UNDEF”.
Workaround: Update the sysdtltpsdigcomp.htm to force bOPONLY to true
always, in the page onComplete event, as follows:
Sub Page_onpagecomplete
on error resume Next
Set objExternal = window.external.parentdocument.parentwindow.external

If objExternal is nothing then

Set objExternal = window.external.Parent.RuntimeStatus

End if

secLvl = objExternal.SecurityLevel
if false then ‘ sd.QualityConfigError("CurrentPoint.OPFINAL") then

bOPOnly = true
combo_OP.style.visibility = "inherit"

combo_OP.hostpopulation = false

combo_OPFINAL.style.visibility = "hidden"
else

bOPOnly = false
combo_OP.style.visibility = "hidden"

combo_OPFINAL.style.visibility = "inherit"
combo_OPFINAL.hostpopulation = false
end if
document.title=cstr(alphaTagName.value)

End Sub
 TPS Process Network R688.2 Software Change Notice 35

Page 36

7.4 ELCN Known Issues

Some of the ELCN issues in this section are tagged with RELCN/RELCNTN-<unique identifier>
indicating that they are tracked in JIRA database as opposed to PARs in Siebel database.

ATTENTION
LCN Ping functionality on the Native Window does not work reliably.
RELCN-1026 and RELCN-1027

If the LCN has been integrated with the ELCN, the Ping command does not
work reliably using the $LNDGPNG schematic when LCN and ELCN nodes
(LCN-ELCN ping and ELCN-LCN ping) are communicating through the ELCN
Bridge.

Also, the Ping command does not work on Cable B for ELCN nodes.
Workaround: There is no workaround.

ATTENTION
LCN crossed cable indications on the Native Window does not work
reliably. RELCN-919
If there are LCN crossed cables on the ELCN Bridges, then the existing LCN
Cable Diagnostics schematic’s "Crossed Cable Message Totals" does not
give any indication of a problem. Also, all ELCN nodes will show a count of
N/A on the LCN Cable Diagnostics schematic.

Workaround:
If there are crossed cables on the ELCN Bridge itself, then you must compare
the Experion Detail Display with the Native Window's aggregate LCN cable
status to troubleshoot any crossed cables.
On the ELCN Bridge Experion Detail Display, If the ELCN Bridge Experion
Detail Display’s “Active LCN Cable” does not match the Native Window’s
LCN Cable Status as shown on the Native Window’s System Status Display,
this may be a result of crossed cables on the ELCN Bridge itself.
 TPS Process Network R688.2 Software Change Notice 36

Page 37

ATTENTION
For EHPMs on the EUCN network (having ENIMs and/or ENBs with
classic EPNI2 boards), the TIME SYNCH STATUS may sometimes show
“FAILED” or “DEGRADED” or “INITIAL”. PAR 1-8PD0FRN
On the EUCN network (having ENIMs and/or ENBs with classic EPNI2
boards), if you have enabled the SOE Time Synchronization, then the TIME
SYNCH STATUS (CURRENT STATE) on PAGE 2 of the UCN STATS
Display may show “FAILED” or “DEGRADED” or “INITIAL” for an EHPM.
Note that this does not impact the LCN Time Synchronization across
LCN/ELCN network and may affect only the precision of the SOE Time
Synchronization of the EUCN network.
This problem is not present on UEA-based ELCN-ENIMs.

Recovery: None
Workaround: None. This fix will be available in a future TPN release.

CAUTION
Use caution while performing the following procedures. RELCN-1171
and RELCNTN-443
Assigning or changing a LCN node number

When assigning or changing an LCN node number of any LCN or ELCN

node, it is imperative that the intended node number is not already in use by
another running LCN or ELCN node. If a duplicate node number situation is
encountered, the invalid duplicate node will fail, and the existing running node
may become ISOLATED from some LCN and ELCN nodes.
Recovery: To recover from this situation, power-off the invalid node, change
its LCN node number to an unused LCN address, power it back on, and
reload the existing running node which may have become ISOLATED.

Decommissioning a LCN node

When decommissioning a LCN-connected node, be sure to completely
disconnect it from the LCN network and clearly label it as being
decommissioned.
In case of a Dual Node Card File (DNCF), you cannot disconnect the LCN
cables, because there may be another running LCN node in the other card
file. To disconnect this node from the LCN network, you should consider
either removing the individual node’s power supply or slightly pull-out the
K4LCN card from the chassis.
This step is to prevent the situation that the node may inadvertently be
powered-on later and may contain the same LCN node number as a running
LCN or ELCN node. If this is the case, then the running LCN/ELCN node may
become ISOLATED from some LCN and ELCN nodes.
Recovery: To recover from this situation, power-off the invalid node and
reload the existing running node which may have become ISOLATED.

TPS Process Network R688.2 Software Change Notice 37

Page 38

ATTENTION
CLKSWTCH fails to switch clock source nodes when you try to switch
from ELCN nodes to LCN nodes. RELCNTN-404 and RELCNTN-408
CLKSWTCH fails to switch clock source nodes when you try to switch from
ELCN nodes to LCN nodes.
Workaround: There is no workaround.

ATTENTION
ELCN nodes shows CLK_MOD as LOCAL on the CLOKSTAT schematic
when LCN node is the Clock Master. RELCNTN-421
ELCN nodes shows CLK_MOD as LOCAL on the CLOKSTAT schematic
when LCN node is the Clock Master.
Workaround: None. Note that until the Clock Master node is migrated from
LCN to ELCN, any node that has completed migration from LCN to ELCN will
show Clock Mode (CLK_MOD) as Local.

ATTENTION
Occasionally, LCN dump from the Native Window does not work for
ELCN AM and ENIM nodes. RELCN-1030 and RELCN-1182
Occasionally, you will not be able to take a dump of the ELCN AM and ENIM
nodes from the Native Window.

Workaround: Beginning with Experion R501 and TPN R687, the ELCN Node
Automatic Dump feature is available.
For information on the ELCN Node Automatic Dump feature, refer to the
ELCN Overview and Implementation Guide and Firmware Manager User’s
Guide.

TPS Process Network R688.2 Software Change Notice 38

Page 39

ATTENTION
Loading a Classic ENIM from the QUALIF state does not work
occasionally. PAR 1-91XQXYP
Loading a Classic ENIM from the QUALIF state occasionally does not work.
Workaround:
Load from FAIL:
 1. Shutdown the ENIM in the QUALIF state to place it into the FAIL
state.
Note: PWR_ON state is preferred.
2. From the FAIL state, wait for at least one minute and then load the
ENIM from the NET using the Native Window. There is no need to
wait when in the PWR_ON state.
OR
Load from PWR_ON:
1. Power-off the ENIM by placing the LCN chassis power supply switch
in the OFF position.

2. Wait for at least 5 seconds.

3. Power-on the node by placing the LCN chassis power supply in the
ON position.
4. Verify that the node is in the PWR_ON state and then load it from
the NET using the Native Window.

ATTENTION
An ELCN Experion TPS Node reports a random maintenance alarm on
hardware slots on the Native Window Maintenance Display. RELCNTN-
578
This maintenance alarm can be safely ignored as it has no impact on the
system.
Recovery: None
Workaround: None

ATTENTION
EHB box status transitions from OK to HWY ERR on the Native
Window’s Hiway Status Display due to FTE Yellow Cable breakage.
RELCNTN-862
On the Native Window’s Hiway Status Display, all EHB box statuses
transition from OK to HWY ERR for three seconds due to FTE Yellow Cable
breakage and then return to OK state.
Note that this does not impact data access or control.
Recovery: All EHB boxes recover after three seconds and transition to OK
state.

Workaround: None

TPS Process Network R688.2 Software Change Notice 39

Page 40

ATTENTION
In rare conditions, on an ELCN ES-T, the LCN Cable Overview
schematic "LCN CBL OVERVIEW" may show an ELCN node as the
cable master. However, other nodes in the network will show correct
information. This issue does not impact cable master algorithm or cable
operations. RELCN-1371
Workaround:
Restart the ELCN ES-T node that is showing incorrect information.
 TPS Process Network R688.2 Software Change Notice 40

Page 41

8 Installation and Migration

REFERENCE - EXTERNAL:
For installation of R688 or migration from pre-R6xx to R688, refer to the
Customer Release Guide (CRG-R688).

ATTENTION
If you have Experion-integrated (BOOT and APP) firmware, make sure
that you upgrade the firmware for ENIMs/ENBs/EHPMs with every new
Experion release.
If you have standalone firmware (BOOT-only), make sure that you are
using the latest firmware from the ULM media of the respective TPN
release.
For more information on ENIM/ENB/EHPM firmware upgrade, refer to the
Customer Release Guide (CRG-R688).
Additionally, you may refer to the Experion Update Matrix's "EUCN" tab
for the most up-to-date compatibility information, this can be found on
http://www.honeywellprocess.com (Support section).

The Honeywell Technical Assistance Center can help you with the instructions and answer questions
regarding upgrade scenarios not specifically covered by these documents.

CAUTION
It is not recommended to change the $MOPHILM and $MOPLOLM parameter
values during migration from any previous applicable releases (R686.1-
R686.4/R687.1-R687.3/R688.1) to R688.2 when the redundant controller pair
is in a mixed release. Changing values during the migration will limit the
capability to return to the previous release.

CAUTION
Prior to migrating from earlier applicable releases (R686.1-R686.4/R687.1-
 R687.3/R688.1) to R688.2, it is recommended to run a doctool query for
$MOPHILM/MOPLOLM and save it. If you have to migrate back due to an
unanticipated situation, then restore the $MOPHILM/MOPLOLM limits after the
back migration.
After migrating from earlier applicable releases (R686.1-R686.4/R687.1-
R687.3/R688.1) to R688.2, the $MOPHILM/$MOPLOLM parameters will retain
their existing values. If you are not using the Manual OP limit function, it is
recommended to change the $MOPHILM/$MOPLOLM parameter values to
NaN after migration.

TPS Process Network R688.2 Software Change Notice 41

Page 42

8.1 System Installation Advisories – General

ATTENTION
On-Line Migration of REDUNDANT AMs
Refer to the TPN R688 Customer Release Guide (CRG-688) for specific
details as to the On-line migration of Redundant AM configurations with
respect to the installation of this TPN software release.
Typical behavior when upgrading redundant AMs:
The first AM loaded with updated software will come up in "WARNING"
status. The Detailed Status Display will show: “WARNING – SECONDARY
IS AN UPGRADE". This warning is expected. After the second AM is loaded
with updated software the AM status should go to OK.
Note: For redundant AMs using HMPU processor: The Redundant HMPU
AM processors were corrected for upgrade problem #1-168033 in 660.0.20.
Verify the redundant HMPU AM is at a minimum revision 66.2 before
attempting an upgrade, otherwise shutdown both AM’s and load each with
TPN R688 software.

ATTENTION
Special Note for GUS/Integration Node/ES-T/ESVT Node Users
The following load modules for TPS and Experion PKS nodes will be supplied
on a separate CD named “Utilities and Load Modules CD (R301.20)”. TPN
R688 requires a minimum revision of these load modules.
MINIMUM VERSIONS FOR TPN R688:
disk_&z12.lcn EST.LO (tsp) 68.11

ESVT.LO (esvt) 68.03

GUSALA.LO (gus_alarm) 68.81 (for GUS only)
GUSALAG.LO (gus_alarm) 68.81 (for GUS only)
YGOCX.LO (ygocx) 65.01 (for GUS and ES-T)
disk_&z14.lcn CSCHEM.LO (csb) 68.91
MSCHEM.LO (xal) 68.84
You are encouraged to update your TPN system HM with the latest versions
of load modules as supplied with the “Utilities and Load Modules CD
(R301.20)”.
 TPS Process Network R688.2 Software Change Notice 42

Page 43

ATTENTION
Load Module Memory Needs To Be Reviewed
Load modules used by TPN nodes may have increased in size compared to
the version of load modules you are currently using. Tool-kit schematic
CBREV may be used to list the load modules used by a node and display
their revision level. If TPN R688 provides newer revisions than those
currently used, you may assume that the modules have increased in size.
Ensure that your NCF configuration has allowed sufficient space for back-
plane software. If not, make the appropriate NCF changes for your custom
configuration. For Experion EST and GUS nodes, please make sure that
the "MAXIMUM EXTERNAL MODULE MEMORY (WORDS)” under “UP" is
at least 20,000 above the value in "TOTAL (MODULES PLUS
ADDITIONAL MEMORY)” under “UP”. For US/UxS the MAX should be at
least 10,000 words above the TOTAL.

ATTENTION
TPN R688 US Personalities (OPR, UNP, GUS, ES-T, and UxS) require
R688 version &DSY files
Attempting to load a R688 US with R60x/R61x &DSY files will result in a node
failure shortly after the System Status display appears.
The reverse is also true. Attempting to load a R60x/R61x US with R688
&DSY files will result in a node failure shortly after the System Status display
appears.
Refer to section “Backing Out of R688” of the TPN R688 Customer Release
Guide (CRG-688) for more information.

TPS Process Network R688.2 Software Change Notice 43

Page 44
 8.2 Installation Instructions – R688.x Product Release

8.2.1 Update History Modules with New HM Personality Software

Updating the HMs with new personality software requires some advance planning. Please read and
understand the following instructions before proceeding.

TIP
A History Module can be successfully updated with the HM on-line
and off-line personalities while it is running its on-line personality.
The comments in EC file LOC_VOLZ.EC say that the HM must be
running the off-line personality in order to run LOC_VOLZ.EC. This
comment can be ignored.

Upgrade the History Module(s) by performing the following steps for each HM.

From the Command Processor, key in:

EC $Fn>&EC>LOC_VOLZ.EC $Fs xx yy

where: $Fn = drive on which the EC command file exists.

xx = physical node number of the HM to be copied to
yy = node pair number of the HM.
$Fs = drive on which the files to be copied reside.
Respond to the prompts (refer to the chart you filled in above).

When the EC completes, go to the System Status Display and:

1. Shutdown the HM. Wait for the HM to go to the QUALIF state.

2. Shutdown the HM again and wait for FAIL.
3. Physically go to the HM and turn off the power and wait 15 seconds and
power it back on.
4. Wait for the HM to go to the OK state.
5. Verify that history collection status is set to ENABLE.
To assist you when running the LOC_VOLZ.EC file, complete the following chart for each HM on
your system.

Note: Once the Chart is populated with the HM's configuration, run the LOC_VOLZ.EC on each
HM as described in the steps above.

TPS Process Network R688.2 Software Change Notice 44

Page 45

HM Node HM Node Pair 68020 HM Configured to System

No. No. Processor? Contain the HM HM?
(01 - 64) (01 - 20) (Yes / No) Initialization Program? (Yes / No)
(Yes / No)
 TPS Process Network R688.2 Software Change Notice 45

Page 46

8.2.2 Updating TPN-resident nodes

➢ TPN-resident nodes: OPR, GUS, UNP, NM, UxS, ES-T

➢ UCN-resident nodes: EHPM, HPM, HPM Simulator

1. If you use 68020 processors, run PRS2VOLZ.EC. If you use 68040 processors, run
PRS4VOLZ.EC. If you have both types on the same LCN run both EC files.

From the Command Processor, key in:

EC $Fn>&EC>PRS2VOLZ.EC $Fs
EC $Fn>&EC>PRS4VOLZ.EC $Fs

where $Fn = Drive containing the EC command file.

$Fs = Drive containing the &Z1 disk.
Note: For PRS2VOLZ.EC, the system will not ask for GUS or (&UxS). It does ask for APP.
Question from PRSxVOLZ.EC Response Response
to 1st EC to 2nd EC
Copy &OPR to net (YES/NO)? Yes Yes
Copy GUS personality files (&UXS) on NET (YES/NO)? Yes Yes
Copy &UNP to net (YES/NO)? Yes Yes
Copy &OP1 to net (YES/NO)? Yes No
Copy &OVG to net (YES/NO)? Yes No
Copy &HGO to net (YES/NO)? Yes Yes
Copy &NMO to net (YES/NO)? Yes Yes
Copy &UCN to net (YES/NO)? Yes Yes
Copy &NGO to net (YES/NO)? Yes Yes
 Copy &CIO to net (YES/NO)? Yes Yes
Copy &CUS to net (YES/NO)? Yes Yes
Do you wish to copy DIA1 on NET (YES/NO)? Yes Yes
Do you wish to copy TLK1 on NET (YES/NO)? Yes Yes
Copy &AMO to net (YES/NO)? Yes Yes
Copy APP personality files (&AXM) on NET (YES/NO)? Yes Yes
Copy AM Sets (&CUS and &CLX) to net (YES/NO)? Yes Yes
Do you wish to copy TLK2 on NET (YES/NO)? Yes No
Note: Answer “No” if your system is not configured for the node type in question.

2. For TPS / Experion PKS users: Update the System History Module with the correct version of
Load Modules. If required, adjust your NCF configuration to accommodate larger Load Module
size. Note: This step requires the use of a GUS/ES-T with CD drive and the Utilities and Load
Modules CD, refer to the following attention.

ATTENTION
If your system includes a GUS, ES-T, E-APP, ESVT, ACE-T, and APP node
types, you are encouraged to update your TPN system HM with the latest
versions of compatible load modules as supplied with the “Utilities and Load
Modules CD (R301.20)”. Run file MSCHEMZ.EC to do this.

TPS Process Network R688.2 Software Change Notice 46

Page 47

3. From the Command Processor, key in: EC $Fn>&EC>MSCHEMZ.EC $Fs.

Note: To install the TPS / Experion PKS Load Modules using the Utilities & Load Modules CD
(R301.20).

4. Shut down and reload each TPN-resident node with the updated software. Do the US/GUS nodes
first. APP, AxM, ES-T, ESVT, GUS, Integration and UxS nodes require that their local hard
drives be updated with the latest TPN personality files before the reload. Perform the following
procedures depending on the node type:
GUS/EST Procedure
a. Log in as a TPN Administrator to allow the Personality to be installed.
b. Choose Start > Control Panel > Programs and Features.
c. Select TPS – UNPW.
d. Click Uninstall and answer the prompts to remove it.
e. Insert the GUS TPN Software CD (R688) into the DVD drive.
f. Open Explorer and navigate to the DVD drive and double-click the GUS folder.
g. Double-click tps – unpw.msi and follow the on-screen prompts and use DEFAULT for
the destination to complete the installation.
h. After the installation is complete, call up the LCNP Status Display,
i. Click Details.
ii. Click Reset LCNP
iii. Click Yes.
Note: If the Enable LCNP Auto Restart option is checked, the machine should
automatically load the new personality.
i. Perform this task for each additional GUS/EST node type.

APP/EAPP/ESVT/ACE-T Procedure
a. Log in as a TPN Administrator to allow the Personality to be installed.
b. Choose Start > Control Panel > Programs and Features.
c. Select TPS – amw personality (AM).
d. Click Uninstall and answer the prompts to remove it.
e. Insert the TPN Application Module CD (R688) into the DVD drive.
f. Locate the DVD within Explorer.
g. Open Explorer and navigate to the DVD drive and double-click the APP folder.
 h. Double-click tps – amw personality (AM).msi and follow the on-screen prompts and
use DEFAULT for the destination to complete the installation.
i. After the installation is complete, on a Station’s Native Window, shutdown the node (that
was upgraded with TPN personality) TWO times to place it into the FAIL state.
j. Shutdown the machine.
k. Power-off the machine.
l. Shutdown the node from the Native Window for the third time so that the node transitions
from the FAIL state to the OFF state.
TPS Process Network R688.2 Software Change Notice 47

Page 48

m. Disconnect the electrical power cord(s) from the machine.

n. Leave the machine(s) for at least 30 seconds.
o. Plug the electrical power cord(s) and then reboot the machine.
p. Log in as a TPN Administrator and call up the LCNP Status Display and verify that the
state shows “OK”.
q. On a Station’s Native Window, verify that the node is showing the correct node type.
Note: If ESVT, it should show “ESVT”. All other node types will show “APP”.
r. Perform this task for each additional APP/EAPP/ESVT/ACE-T node type.
5. Checkpoint all LCN/UCN (PM/APM/SMM/LMM/AM/HG/CG/NG/PLCG/EPLCG) node(s)
databases.
6. Installation of the LCN/UCN (PM/APM/SMM/LMM/AM/HG/CG/NG/PLCG/EPLCG) node(s)
for R688.
Refer to the Customer Release Guide (CRG-R688) for specific instructions for each LCN/UCN
(PM/APM/SMM/LMM/AM/HG/CG/NG/PLCG/EPLCG) node type.

TPS Process Network R688.2 Software Change Notice 48

Page 49

8.3 Update System History Module with new &DSY Software

The comments in EC file SYS_VOLZ.EC say that the System HM must be running the off-line
personality in order to run SYS_VOLZ.EC. You can ignore this comment and save yourself a lot of time
if you observe the following conditions:

Update the System History Module with the new GDF files.

TIP
Possible WARNING Condition After Upgrade
The Data Access version for R688 has been updated to “880”. This Data
Access version had been implemented in the R688 version and a warning
should exist only if running LCN nodes remain on an older release. It is
possible that certain nodes may display a WARNING status after upgrade.
The Detailed Status for the node would show:
Custom/Standard parameter duplicate XRef created, NNNN – R880
If this occurs, STOP the upgrade and resolve the issue before continuing.

When a US/GUS/EST or AM/APP/ESVT is loaded with R688, the load of that

node will recreate the DUPLICAT.SP file with the correct version.
If you should have to load a station back to the previous release, when it
loads, it will recreate the DUPLICAT.SP file so this is where an issue could
occur. If you now load an AM/CG/NG from the OLD station, the AM/CG/NG
being loaded will indicate the WARNING. TO correct the issue, shutdown the
AM/CG/NG that was just loaded and reload a station with THE CURRENT
UPGRADE release and the DUPLICAT.SP will be recreated with the correct
version, now you can load the AM/CG/NG without receiving a WARNING.

TIP
The System History Module can be successfully updated with &DSY and
GDF Software while the System HM runs its on-line personality. However,
you must observe the following cautions while running EC file
SYS_VOLZ.EC:
Do not perform any Data Entity Builder actions. (The DEB requires access to
GDF files.)

Do not load US, UxS, ES-T or GUS nodes. (These nodes require &DSY
files.)

Note: The HM Status Display TYPE will show:

•
"HMON" for HM loaded with the on-line personality (HMO) ← correct personality
• "HMOF" for HM loaded with the off-line personality (HMI)
From the Command Processor, key in:
EC $Fn>&EC>SYS_VOLZ.EC $Fs xx
where $Fn = Drive containing the EC command file.
$Fs = Drive containing the &Z1 disk.
xx = Two-digit physical node number of the System HM.

TPS Process Network R688.2 Software Change Notice 49

Page 50

Question from SYS_VOLZ.EC Response

Copy volume &ASY (YES/NO)? No

Do you wish to skip &DSY or any of the optional directories (Y =skip; N = copy Yes
all)?
 Copy volume &DSY (YES/NO)? Yes
Copy optional volume &HGG (YES/NO)? Yes

Copy optional volume &AMG (YES/NO)? Yes

Copy optional volume &ARG (YES/NO)? Yes

Copy optional volume &NMG/&NM2 (YES/NO)? Yes

Result: Upgrade is complete!

TPS Process Network R688.2 Software Change Notice 50

Page 51

9 Appendix

9.1 R688.x Software Revision History

Software Component changes from prior releases are highlighted in ‘bold’ text.

9.2 R688.2 Release Revision History

Release Name Release Notes

R688.2 TPN R688.2 – Maintenance release – August 2019

9.3 R6xx Personality Revision Level History (orientation)

Release
Personality TPN R686.3 TPN R686.4 TPN R687.1 TPN R687.2 TPN R688.1 TPN R688.2
 AM (am) 68.166 68.166 68.213 68.217 68.235 68.238

AxM/APP/AMW (axm) 68.166 68.166 68.213 68.217 68.235 68.238

CG (ur) 68.168 68.168 68.213 68.217 68.235 68.238

HG (hg) 68.168 68.168 68.213 68.217 68.235 68.238

HMI – off-line (ho) 68.165 68.165 68.213 68.217 68.235 68.238

HMO – on-line (hs) 68.165 68.165 68.213 68.217 68.235 68.238

NG (ngp) 68.165 68.165 68.213 68.217 68.235 68.238

US – OPR (mf) 68.172 68.172 68.216 68.222 68.235 68.239

US – UNP (usp) 68.172 68.172 68.216 68.222 68.235 68.239

UxS/UNPW-GUS (usx) 68.172 68.172 68.216 68.222 68.235 68.239

TPS Process Network R688.2 Software Change Notice 51

Page 52

Release
Personality TPN R686.3 TPN R686.4 TPN R687.1 TPN R687.2 TPN R688.1 TPN R688.2

NIM (nmo) 68.182 68.182 68.218 68.225 68.236 68.239

APM-comm (umc) 68.101 68.101 68.200 68.200 68.200 68.200

APM-cntrl (umf) 68.101 68.101 68.101 68.101 68.101 68.101

APM I/O Simulator (asim) 68.101 68.101 68.201 68.201 68.234 68.234

HPM-cntrl (hmf) 68.159 68.159 68.202 68.202 68.234 68.236

HPM-comm (hpmc) 68.158 68.160 68.200 68.201 68.234 68.234

HPM I/O Simulator (hsim) 68.161 68.162 68.201 68.202 68.235 68.237

LM (lmc) 68.125 68.125 68.125 68.125 68.125 68.125

PM-comm (pmc) 68.101 68.101 68.200 68.200 68.200 68.200

PM-cntrl (pmf) 66.0 66.0 66.0 66.0 66.0 66.0

FSMM (fsc) 53.6 53.6 53.6 53.6 53.6 53.6

SM (smc) 68.0 68.0 68.0 68.0 68.0 68.0

9.4 R6xx Generic Overlay (&OP1) Revision Level History

Toolkit schematic CBREV can be used to determine generic overlay revision. Since only one generic overlay is active in a US at time, CBREV
can display only one overlay revision. To determine the revision of the other generic overlays simply call the appropriate function from the target
US. The desired overlay will be loaded and CBREV will display its name and revision.

Release Name
-------------------------------------
Overlay Name TPN R686.3 TPN R686.4 TPN R687.1 TPN R687.2 TPN R688.1 TPN R688.2

AUDIT - System Audit Tool (audit) 68.158 68.158 68.202 68.203 68.234 68.234

BTNCN – Button Config. (bc) 68.152 68.152 68.201 68.201 68.234 68.234

CL - CL Compiler (cl) 68.152 68.152 68.200 68.201 68.234 68.234

TPS Process Network R688.2 Software Change Notice 52

Page 53
 Release Name
-------------------------------------
Overlay Name TPN R686.3 TPN R686.4 TPN R687.1 TPN R687.2 TPN R688.1 TPN R688.2

CONFG - NCF Configuration (cn) 68.152 68.152 68.200 68.200 68.234 68.234

DEB - Data Entity Builder (de) 68.152 68.152 68.200 68.202 68.234 68.234

FNAME - Find Names (fn) 68.151 68.151 68.203 68.205 68.234 68.234

LBC - Logic Block Config. (lb) 68.151 68.151 68.200 68.200 68.234 68.234

LN - Load Node Overlay (ln) 68.150 68.150 68.200 68.200 68.234 68.234

PICED – Picture Editor (mb) 68.153 68.153 68.202 68.202 68.234 68.234

SDT – System Doc. Tool (sdt) 68.152 68.152 68.200 68.200 68.234 68.234

SMCC – System Maint. CC (smcc) 68.152 68.152 68.200 68.200 68.234 68.234

TRANS - Data Base Translators (dt) 68.153 68.153 68.200 68.201 68.234 68.235

9.5 R6xx Standard Back-Plane Module (&CUS, &OVG) Revision Level History
Toolkit schematic CBREV can be used to determine back-plane module revision.

Release Name
------------------------------------------------
Back-plane Module Name TPN R686.3 TPN R686.4 TPN
TPN R687.1 TPN R687.2 TPN R688.1 R688.2

CGBASE - CG Custom SW Base 68.89 68.89 68.90 68.90 68.91 68.91

(csb)

OPBASE - US Custom SW Base 68.89 68.89 68.90 68.90 68.91 68.91

(csb)

UPBASE - US Custom SW Base 68.89 68.89 68.90 68.90 68.91 68.91

(csb)

ELB - Equip. List Builder (yhelb) 68.150 68.150 68.200 68.200 68.234 68.234

MSF - Equip. List Builder (yhmsf) 62.0 62.0 62.0 62.0 62.0 62.0

TPS Process Network R688.2 Software Change Notice 53

Page 54

Release Name
------------------------------------------------
Back-plane Module Name TPN R686.3 TPN R686.4 TPN
TPN R687.1 TPN R687.2 TPN R688.1 R688.2

OPEQLT – Equip. List Actors (yheqa) 65.0 65.0 65.0 65.0 65.0 65.0

UPEQLT – Equip. List Actors (yheqa) 65.0 65.0 65.0 65.0 65.0 65.0

OPLVR – Version/Revision Tool 68.157 68.157 68.202 68.203 68.234 68.234

(aplvr)

UPLVR – Version/Revision Tool 68.157 68.157 68.202 68.203 68.234 68.234

(aplvr)

XACCES – UxS & AxM (lca) 68.150 68.150 68.150 68.150 68.150 68.150

FILE - AM (sets/frw) 68.155 68.155 68.201 68.202 68.234 68.234

CONV - AM (sets/ncnv) 68.155 68.155 68.201 68.202 68.234 68.234

AMCL01 – AM Options (sets/amcl) 68.155 68.155 68.201 68.202 68.234 68.234

AMCL02 – AM Options (sets/amcl) 68.155 68.155 68.201 68.202 68.234 68.234

AMCL03 – AM Options (sets/amcl) 68.155 68.155 68.201 68.202 68.234 68.234

AMCL04 – AM Options (sets/amcl) 68.155 68.155 68.201 68.202 68.234 68.234

AMCL05 – AM Options (sets/amcl) 68.155 68.155 68.201 68.202 68.234 68.234

AMCL06_2 – AxM R200/300 68.155 68.155 68.201 68.202 68.234 68.234

(sets/amcl)
 XOPTN (sets/xop) 68.155 68.155 68.201 68.202 68.234 68.234
OPFNAM – Point Interconnection (fn) 68.151 68.151 68.203 68.205 68.234 68.234

UPFNAM – Point Interconnection (fn) 68.151 68.151 68.203 68.205 68.234 68.234

ENIM – ENIM Load Module (eucn) 68.154 68.154 68.201 68.201 68.201 68.201

ENIM – ENAME Load Module (eucn) 68.154 68.154 68.201 68.201 68.201 68.201

Note: Refer to the Utilities and Load Modules SCN for revision history of UxS, GUS, ES-T, ESVT and Integration Node load modules.

TPS Process Network R688.2 Software Change Notice 54

Page 55

9.6 R6xx Other Miscellaneous Software

Release Name
---------------------------------------------
--- TPN R686.3 TPN R686.4
Name TPN R687.1 TPN R687.2 TPN R688.1 TPN R688.2

&DSY 68.150 68.150 68.150 68.150 68.150 68.150

Toolkit 1 – TLK1 (tk) 68.156 68.156 68.203 68.204 68.235 68.235

Toolkit 2 – TLK2 (tlk2) 68.153 68.153 68.153 68.153 68.153 68.153

&EC (ce) 68.125 68.125 68.125 68.125 68.125 68.125

GDFs 68.159 68.159 68.206 68.209 68.235 68.237

9.7 Repeatable Special Software for R6xx

Toolkit schematic CBREV can be used to determine repeatable special back-plane module revision. These Repeatable Specials are not supplied
on the standard TPN distribution media. They may be ordered separately from Software Delivery Management.
No. Name of Repeatable Special Current Back-plane Module Name(s)
Revision

R01 Alarm / Message Window (ms2win) 68.0 msgwin.lo

----------------------------------------------------- ------------ -------------------------------------

Alarm / Message Window for UxS (msgwin) 68.0 msgwin.lo , msgwinx.lo

R02 Key Card Access System (apcr) 60.1 opcr.lo, opca.lo, opcafl.lo
upcr.lo, upca.lo, upcafl.lo

R03 AM Steam Tables (apst) 60.2 st_s.lo, st_d.lo

R04 AM Steam Tables SI Units (apstsi) 60.2 stsis.lo, stsimod.lo

R05 XY Plot (apxyplt) 60.1 opxypt.lo,upxypt.lo

R14 Computer Link Module (CLM) 60.12 clm.lo

TPS Process Network R688.2 Software Change Notice 55

Page 56

The following Repeatable Specials have been withdrawn from sale and are no longer available (June, 1999).

No. Name of Repeatable Special Current Back-plane Module Name(s)

Revision

R06 Demand Update/US Schem. (apdmdup) 60.1 Opupd.lo, upupd.lo

R07 Free Format Log Printer Plot (apptrp) 60.1 Opptrp.lo, upptrp.lo
 R08 Large Character Phantom (aplrgc) 60.1 Uplrgc.lo, oplrgc.lo

R09 Sequence Download - AM (apseq) 68.125 sdll_e.lo, sdll_s.lo

R10 LCN Time Sync. (aptsync) 60.1 timmod.lo, tammod.lo

R11 VAX/LCN Time Sync. (apvaxts) 60.1 vtsmod.lo

R12 AM File Print (apamprnt) 60.1 amprint.lo

R13 Text File Display/Print (aptxtdp) 60.1 opdfil.lo, updfil.lo, xpdfil.lo

TPS Process Network R688.2 Software Change Notice 56

Page 58
57
Honeywell Process Solutions
1860 W. Rose Garden Lane
Phoenix, AZ 85027 USA