
Product Overview – Distributed Communication (HCI/OPC)
46
TPS System Overview
11/98
Honeywell Inc.
R100
ServerSpecificName
is the object name within the HCI server. It may be a
multipoint name, indicating structure of the component objects, such as “F100.PV”.
TPS Network parameters such as PV, SP, Mode, etc. are modeled as objects within the
TPN Server. In general, however, object names are not limited to two parts.
Various levels of name aliasing, indirection, and indexing are also available, as
provided by the given HCI server (see the detail specifications).
Currently the following conventions apply to TPS system naming.
• Names are case insensitive and Unicode based
• Access to data in a different TPS Domain is not available; therefore, the
TPSDomainName need not be used (‘//’ indicates TPS domain name)
• TPS Configuration allows the size of TPSDomainNames and HciComponentNames
to be up to 255 characters
• GUS displays limit the size of the total name form to 80 characters for any HCI data
source access and includes a prefix to identify HCI versus HOPC connection
• The HCI PHD Server limits the size of the ServerSpecificName portion to 32
characters
• The HCI TPN Server limits the size of the ServerSpecificName portion to that of
the TPS Networksize which is 31 characters (16 for the tagname, 8 for parameter
name, 4 for the index plus 3 for the delimiters)