Honeywell ControlEdge 900R04-0200 Getting Started page 96

Chapter 6 - Communication
Namespace
Index
0
1
2
96
opc.tcp://192.168.2.10:4840
When both Ethernet ports are configured as shown in the example
above, the ControlEdge 900 controller OPC UA Server considers the
links to be redundant. In this case, the ControlEdge 900 controller
OPC Server is listening on both endpoints. When one link is lost,
clients can use the URL of the second link to connect to the Server. It
is worth noting that the ControlEdge 900 controller OPC UA Server
maintains the session created on the failed link until the session
timeout period expires after which the session will be deleted.
In the case of redundant ControlEdge 900 controller, the IP address
follows the primary CPM. Therefore, if a switchover occurs, the client
reconnects to the ControlEdge 900 controller OPC UA Server on the
new primary with the same URL that was used to connect to the
server on the failed primary.
Namespace
OPC UA uses namespaces to uniquely differentiate between the
names and IDs it defines and those defined by companion
specifications or the local server. The ObjectTypes defined in the UA
specification for IEC 61131-3 derive from the OPC UA Device
Integration Types which in turn derive from the OPC UA Core
ObjectTypes. Thus the ControlEdge 900 controller OPC UA Server
includes these 3 namespaces in addition to its own namespace. The
list of namespaces used in the Server is shown below:
Namespace
http://opcfoundation.org/UA/
URL:<IP Address>:
Honeywell:ControlEdgePLC:UAServer
where IP Address is the IP of the
Ethernet port that is bound to OPC UA
Server. If UA is enabled on both ETH1
and ETH2, then the IP of ETH1 is used
for IP Address.
http://opcfoundation.org/UA/DI/
Description
Namespace for NodeIds and
BrowseNames defined in the
OPC UA specification.
Namespace index 1 is reserved
for the local server, for nodes
specific to the server like those
shown in section 4.1. Note that
this URI is also the ServerURI
(appears in index 0 of the
ServerArray property). It is also
the ApplicationURI in the
subjectAltName field of the
server's certificate.
Namespace for NodeIds and
BrowseNames defined in [DI].