Echelon LonMaker - Manual (Page 22)

6 Introduction
You can also set the initial values of device-specific configuration properties when commissioning or
replacing a device, loading a new application image into the device, or resynchronizing configuration
properties. For example, when commissioning or replacing the thermostat in the previous example,
you may load the configuration property value from the LNS network database to assign the initial
setpoint.
See Chapter 5, Installing Networks, for more information on managing device-specific configuration
properties.
Passive Configuration Mode
You can now manually propagate configuration property value changes to one or more devices without
affecting the network configuration of the devices. You can use this feature to enable a plug-in to
operate as a passive configuration tool, which allows you to use plug-ins on devices installed by
network tools not based on LNS. To use this passive configuration mode, attach the LonMaker tool to
the network, keep it OffNet, and then recover the network. You can then configure any device in the
network using plug-ins, and apply configuration property value changes to these devices by right-
clicking a device (or selecting multiple devices and right-clicking one of the devices), pointing to
Commissioning, and clicking Propagate CP Values to Device on the shortcut menu.
Enhanced Subsystem Recovery
You can now store subsystem data in application devices and routers. This improves the network
recovery process (see Recovering a LonMaker Network in Chapter 7, Maintaining Networks), as the
LonMaker tool can use the saved subsystem data to place application devices and routers in their
correct subsystems.
To enable subsystem data to be stored in devices, select one or both of the options in the network
properties: Recovery options category (see Appendix A). The options consist of storing the subsystem
ID in the location property of application devices and routers and storing the subsystem path in the
SCPTlocation configuration property of application devices.
• If you select the Set Location Property to Subsystem ID option, the LonMaker tool stores the
subsystem ID in application devices or routers when they are commissioned. This subsystem ID
appears as a 6-character ASCII or 12-digit hex string in the Location field of the Basic Properties
dialog box. The LonMaker tool automatically updates the subsystem ID when you move the
device, and when you move or rename its subsystem and the Update all Devices when
Subsystem Name is Modified option in the network properties: Recovery options category is set
to Yes.
• If you select the Set SCPT Location Value to Subsystem Path option, the LonMaker tool stores
the subsystem ID in the SCPTlocation configuration property of application devices when they
are commissioned. The LonMaker tool automatically updates the subsystem path stored in the
SCPTlocation configuration property when you move the application device, and when you move
or rename its subsystem and the Update all Devices when Subsystem Name is Modified option
in the network properties: Recovery options category is set to Yes.
Active Device Template and Resource File Updates
You can now update the device interface (XIF) file or the resource files for a device template currently
being used by devices in the network. To update the XIF file or resource files of a device template,
open the Network Explorer, click the new Device Templates tab, right-click a device template, point
to Import XIF or Resync to Resource Files, and then select whether to update the device template
and all the devices using that template, or just the device template.
See Network Explorer in Chapter 4, Designing Networks, for more information on updating device
templates and resource files.