Echelon LNS DDE Server - Manual (Page 65)

Standard Topic Format
The standard topic format specifies a network, subsystem, and topic type.
Ose this format except when you are using custom topics as described in
the next section. To use a standard topic format, specify a topic with the
following three components:
Network_name.Subsystem_path.Topic_type
Each component is separated from the other by a single period ("."). The
Subsystem_path component may consist of multiple subsystems, each also
separated by a period. Following is a description of the three components
(all three components must be specified):
Network_name
The name of the network as defined in the LNS database.
The Network_name is case sensitive.
Subsystem_path
The full path to the subsystem containing the device to be
accessed, as defined in the LNS database. The subsystem
path in itself may consist of one or more components. For
example, Building-A54.Level-B.Section-K is the
subsystem path for a Section-K subsystem within a Level-B
subsystem within a Building-A54 subsystem. The
Subsystem_path is not specified for the system topic. The
Subsystem_path is case sensitive.
Topic_type Specifies the type of information required. The topic type
must be one of the following: Netvar, DevNV, NV,
LMNV, LMCP, NVCP, DevCP, DevNVCP, LMNVCP, LM,
MsgTag, MT, Dev, or System. These types are described
later in this chapter under Topic types. The Topic_type is
not case sensitive.
The LNS DDE Server folder and detail panes can be used to find the name
of the network and subsystem path. If accessing a remote network, the LNS
Server must be running on the host PC.
Examples
Below are a few examples of correctly formatted topics:
Network1.Subsystem 1.Netvar
NetX.SubystemY.SubsystemZ.MsgTag
Building-A54.Level-B.Section-K.LMNVCP
Network.System
LNS DDE Server User's Guide 4-3