Commissioning phase – Echelon LNS User Manual

Page 95

LNS Programmer's Guide

The following properties cannot be read while the LNS Object Server is in engineered

mode:

• AppDevice.SelfDocumentation
• AppDevice.State
• AppDevice.DetailInfo
• NetworkVariable.SelfDocumentation
• Router.State
• RouterSide.State
• RouterSide.DetailInfo
• NetworkVariable.Value

Commissioning Phase

During the commissioning phase, the configuration information defined during the

definition phase is loaded into the devices on the network. The LNS Object Server must
be attached to the network during this phase, meaning that the application must specify

a network interface. The application used for this phase can be different than the

application used for the definition phase. For example, the application used for the
definition phase may provide a more functional user interface than the application used

for the commissioning phase. In fact, the application running the commissioning phase

could be completely automated. If a different PC is used for the commissioning phase, the
network database must be transferred to the new PC and imported into its LNS Object

Server. For instructions on this, see Moving Network Databases on page 256.

It is common, but not required, for the commissioning phase to be performed locally. A

local commissioning tool allows for easy on-site trouble-shooting. However, the
commissioning phase can be performed remotely when using network interfaces such as

the SLTA-10, the

.LON 10 Ethernet Adapter or the

.LON 100 Internet Server.

Alternatively, you can connect locally to a network containing distant devices using an
Internet router such as the

.LON 600 L

ORKS

/IP Server or the

.LON 1000 Internet

Server. If you plan to commission your network remotely, it is recommended that you
assign each device its Neuron ID during the definition phase.

The methods and tasks you need to perform to accomplish each task in the

commissioning phase are shown in figure 5.3.